Official CyanogenMod 10.1 P880 FIXED Flashable - LG Optimus 4X HD

CyanoGen Mod 10.1 LG Optimus 4x HD
21.05.2013 CyanogenMod 10.1 Official Nightly
cm-10.1-20130521-NIGHTLY-p880.zip (163.4 MB)
https://mega.co.nz/#!GV9hVJxY!aY3rIic4cKCc_IeNp47LtXkFPhQBX4ufsHY0t67-Tmk
___________________________________________________________________________________________________________________________________
GAPPS
BUILD - 01.03.2013
GAPPS Jelly Bean 4.2.2 20130301.zip (91.0 MB)
https://mega.co.nz/#!LhAlSLxK!dFZfhUQSclmpiS4Rwf5banSIDt5OMGgzzjoCEIcqsh8
___________________________________________________________________________________________________________________________________
USE KERNEL WerewolfJB Kernel v005 to get best out of your phone
I dont post a link because its not my kernel but you will find it in Android Development
How to Enable USB Debugging and Developer Options on CM10.1
Go to – Settings > About phone.
Then move on to Build number option
Tap on Build number repeatedly about 7 times.
This is enough.
After touching 7th time you will see a message that, “you are now a developer”.
___________________________________________________________________________________________________________________________________

how did you fix the problem?

nbock97 said:
how did you fix the problem?
Click to expand...
Click to collapse
yeah how DID you fixed it
Sent from my LG-P880 using xda app-developers app

he changed the update script. the official cm flashable zip checks for the codename "p880". since its not the correct codename for our phone ("x3" is correct) and all our recoveries use that codename "x3" its not flashable. what he did is changing "p880" to "x3" in the update script (in the first line) or he completely removed that check

Wasn't easier to just use the official CWM from the CM team? Unless you use twrp ofcourse
Sent from my LG-P880 using Tapatalk 2

gordon0001 said:
he changed the update script. the official cm flashable zip checks for the codename "p880". since its not the correct codename for our phone ("x3" is correct) and all our recoveries use that codename "x3" its not flashable. what he did is changing "p880" to "x3" in the update script (in the first line) or he completely removed that check
Click to expand...
Click to collapse
NO dude i Removed the Line , and not changed it to x3 , because some recoverys find it as p880 and other as x3 , so now if you remove it it works all time on every recovery
Anyway did someone test Works ?
On my Phone Works :laugh:

what recovery did you use..?? And Is this the newest cm??

New updates will come every day, so I think people should beter flash newest cwm.

No ill update right now with the latest its like 1 hour old Update
i use CWM 6.0.2.8 from Dexter

Please help
i've tried to flash CM and followed instructions in this order:
1. Place cm-10.1-20130416-NIGHTLY-p880.zip and gapps-jb-20130301-signed.zip in to your internal sdcard
2. BACKUP ALL YOUR DATA with CWM Recovery
3. In CWM Recovery make wipe data/factory reset, wipe cache partition, wipe dalvik cache, format system
4. Flashcm-10.1-20130416-NIGHTLY-p880.zip from sdcard
But i've got an error status 7 . Now my phone wont boot, and i can't copy this fixed zip file. What can i do?

batinjo said:
i've tried to flash CM and followed instructions in this order:
1. Place cm-10.1-20130416-NIGHTLY-p880.zip and gapps-jb-20130301-signed.zip in to your internal sdcard
2. BACKUP ALL YOUR DATA with CWM Recovery
3. In CWM Recovery make wipe data/factory reset, wipe cache partition, wipe dalvik cache, format system
4. Flashcm-10.1-20130416-NIGHTLY-p880.zip from sdcard
But i've got an error status 7 . Now my phone wont boot, and i can't copy this fixed zip file. What can i do?
Click to expand...
Click to collapse
Restore the backup you made in step 2, install newest official CWM via ROM Manager (download it from play store if you don't already have it) then boot back into CWM and install CM again.
---------- Post added at 08:38 PM ---------- Previous post was at 08:37 PM ----------
Also I honestly don't see any real benefit to this thread when installing official CWM solves the status 7 issue and allows for OTA updating of CM instead of having to wait for the OP of this thread to upload a fix every single day...

argh
AlderCass said:
Restore the backup you made in step 2, install newest official CWM via ROM Manager (download it from play store if you don't already have it) then boot back into CWM and install CM again.
---------- Post added at 08:38 PM ---------- Previous post was at 08:37 PM ----------
Also I honestly don't see any real benefit to this thread when installing official CWM solves the status 7 issue and allows for OTA updating of CM instead of having to wait for the OP of this thread to upload a fix every single day...
Click to expand...
Click to collapse
tnx so much for your answer, but what if i don't made backup in step 2?
Any chance to do anything by some command line or something?

batinjo said:
tnx so much for your answer, but what if i don't made backup in step 2?
Click to expand...
Click to collapse
I was afraid you were gonna say that! You can still boot into CWM though right? If you can, and your computer has an SD slot, just take out your external SD card and put it into an adapter and put the fixed version from this thread on that, then you can just install it from the external SD in CWM.

batinjo said:
tnx so much for your answer, but what if i don't made backup in step 2?
Any chance to do anything by some command line or something?
Click to expand...
Click to collapse
from CWM you can install via sideload ...
or harder way- reflash stock, root it, download rom manager, install newest cwm via it, copy files, flash in recovery

won't work
AlderCass said:
I was afraid you were gonna say that! You can still boot into CWM though right? If you can, and your computer has an SD slot, just take out your external SD card and put it into an adapter and put the fixed version from this thread on that, then you can just install it from the external SD in CWM.
Click to expand...
Click to collapse
can't mount /external_sd
When i connect phone to computer, driver is missing, it is named lgp880. I've installed all the drivers that came on my mind, and nothing.
So i'm not sure how to use the sideload command...
NIGHTMARE!!!

Bugs? And best feature?

bugs :
no mass storage mode
and some little things
best feature: Its cyanogenmod - says everything there are so much nice functions! e.g. skipping track with volume rocker, close apps with long prrss back, theme support , .... Go ahead and try it
Sent from my LG-P880 using xda app-developers app

batinjo said:
i've tried to flash CM and followed instructions in this order:
1. Place cm-10.1-20130416-NIGHTLY-p880.zip and gapps-jb-20130301-signed.zip in to your internal sdcard
2. BACKUP ALL YOUR DATA with CWM Recovery
3. In CWM Recovery make wipe data/factory reset, wipe cache partition, wipe dalvik cache, format system
4. Flashcm-10.1-20130416-NIGHTLY-p880.zip from sdcard
But i've got an error status 7 . Now my phone wont boot, and i can't copy this fixed zip file. What can i do?
Click to expand...
Click to collapse
Download the new Update and use CWM 6.0.2.8 Try that

x0BlackTeresis0x said:
Download the new Update and use CWM 6.0.2.8 Try that
Click to expand...
Click to collapse
NOT 6.0.2.8 CWM 6.0.3.1 is compatible with cm10
Sent from my LG-P880 using xda app-developers app

Sorry didnt saw that there is a newer version for clockworkmod
right use that 6.0.3.1

Related

Can`t install any ICS ROM

I tried to install several ICS ROMs on my Galaxy s, but none of them worked. I did all wipes like 3 times before any rom install... I only managed to boot up SGS2 ICS rom, wich was extremely laggy and etc:L Any advices of what i can do?
Flash back to gb with this kit (unzip, read .txt first)
http://db.tt/MOGZx01S
Then go to slim website and read the installation instructions(use a nightly, not a kernel where you see the choice)
Re read, make sure you are clear what to do, make sure you have all that you need on your internal sd (nightly/i9000 file/ common file/ modem from here http://forum.xda-developers.com/showthread.php?t=1158783
[CM7/MIUI/ICS/CM9][06.01.12] Modems + Bootloaders(MD5)
Proceed, take your time, be near a computer, breath deeply, don't panic of things go wrong, post on thread of they do.
Try this.
Download the latest CM9 nightly (you will find it if you Google it)
Go to recovery
Wipe
Format system (mount and storage)
Flash in this order
CM9
Reboot recovery
Modelxxx.xxx
Slim common
Reboot.
Then enjoy
Sent from my GT-I9000 using Tapatalk 2
trying to install AOKP, it gives me error:
assert failed: run_program("/tmp/updater.sh") == 0
Click to expand...
Click to collapse
let me try install other ICS rom.... all life of my galaxy s it was on stock roms.now i decided to update to ICS. first time trying to upgrade to ICS (only used to flash GB roms before)
What exactly is your process in flashing ics, (from gb)
Sent from my GT-I9000 running remICS-UX using XDA premium
calum96 said:
What exactly is your process in flashing ics, (from gb)
Sent from my GT-I9000 running remICS-UX using XDA premium
Click to expand...
Click to collapse
Here is it:
1) get into recovery
2)Data / cache / dalvik-cache wipe
3) format /system
4)again wipes
5)mount everything i can
6) go and install file
it opens aroma installer...
pick needed items and press "install" after that it gives me error
foggydisaster said:
Here is it:
1) get into recovery
2)Data / cache / dalvik-cache wipe
3) format /system
4)again wipes
5)mount everything i can
6) go and install file
it opens aroma installer...
pick needed items and press "install" after that it gives me error
Click to expand...
Click to collapse
Unless the ROM you are installing is specifically telling you to "mount everything", do not do it. Try it again, but this time do not mount anything manually, installing from Zip should do it automatically. If it still doesn't work, make sure the ROM you are trying to install is supposed to be installed from Recovery, some do also provide files for flashing through Odin/Heimdall
EDIT: I do recommend flashing CM9 first, get the newest nightly from here: http://get.cm/?device=galaxysmtd and google apps (if you want them) from here: http://goo.im/gapps/gapps-ics-20120429-signed.zip which is the recommended one for usage with CM9 ICS.

Help, please: Boot loop during Cyanogenmod zip install

Hello,
I'm not gonna panic, as I think Ive not bricked my phone YET.
Here is what I have done, I have a GALAXY S I9000.
Have been using it for quite some time now. 2 years ago, I have flashed it with - hardcore's kernel with the ClockworkMod Recovery - using Odin.
Today I decided to give Cyanogenmod a go, followed the steps here. - http://wiki.cyanogenmod.com/wiki/Samsung_Galaxy_S:_Full_Update_Guide
Since I have the hardoce's kernel, I skipped this Installing the ClockworkMod Recovery - and moved on to - Flashing CyanogenMod.
I will go step by step from here.
Download the latest version of CyanogenMod.
Optional: Download the Google Apps for the device.
Place the CyanogenMod update.zip file on the root of the internal memory.
Optional: Place the Google Apps .zip on the root of the internal memory also.
Boot into the ClockworkMod Recovery.
Once the device boots into the ClockworkMod Recovery, use the side volume buttons to move around, and either the power button or the trackball to select.
Select the option to Wipe data/factory reset.
Then select the option to Wipe cache partition.
Select Install zip from sdcard.
done these, no problem so far.
[*]Select Choose zip from sdcard.
when I chose this, phone rebooted, it was so fast something may have come up and I didnt see.
Now I am stuck in a boot loop:
- Galaxy S I9000 samsung screen comes up, goes away for a second, comes up again.
- A page with code appearing from the bottom comes up really fast ( logo in the middle changes quickly) then it disappears.
- whole thing starts again.
UPDATE: I got a picture of the fast screen that comes up. : http://localhostr.com/files/b5NzFRy/2012-08-27 05.07.32.jpg
Some observations.
- I can go into download mode when opening it with the key combo.
- loop only stops when I unplug the battery
I need advice on what caused this and how to fix this, please help me.
edizarca said:
I need advice on what caused this and how to fix this, please help me.
Click to expand...
Click to collapse
Just flash it again ...see quick fix and solutions link below
xsenman said:
Just flash it again ...see quick fix and solutions link below
Click to expand...
Click to collapse
I cannot see what will help me on this page, but I understand how flashing again could work.
But how with the situation I have?
edizarca said:
I cannot see what will help me on this page, but I understand how flashing again could work.
But how with the situation I have?
Click to expand...
Click to collapse
are you not able to get into recovery? If only download than you need to get back to GB and than do a progressive update from GB to ICS to JB
Flash it again. From what I've heard, it only flashes the kernel the first time.
I had the same problem today with CM7 today. Just reboot in recovery and flash again cm zip, form there on everything is gonna run smooth!
edizarca said:
Hello,
I'm not gonna panic, as I think Ive not bricked my phone YET.
Here is what I have done, I have a GALAXY S I9000.
Have been using it for quite some time now. 2 years ago, I have flashed it with - hardcore's kernel with the ClockworkMod Recovery - using Odin.
Today I decided to give Cyanogenmod a go, followed the steps here. - http://wiki.cyanogenmod.com/wiki/Samsung_Galaxy_S:_Full_Update_Guide
Since I have the hardoce's kernel, I skipped this Installing the ClockworkMod Recovery - and moved on to - Flashing CyanogenMod.
I will go step by step from here.
Download the latest version of CyanogenMod.
Optional: Download the Google Apps for the device.
Place the CyanogenMod update.zip file on the root of the internal memory.
Optional: Place the Google Apps .zip on the root of the internal memory also.
Boot into the ClockworkMod Recovery.
Once the device boots into the ClockworkMod Recovery, use the side volume buttons to move around, and either the power button or the trackball to select.
Select the option to Wipe data/factory reset.
Then select the option to Wipe cache partition.
Select Install zip from sdcard.
done these, no problem so far.
[*]Select Choose zip from sdcard.
when I chose this, phone rebooted, it was so fast something may have come up and I didnt see.
Now I am stuck in a boot loop:
- Galaxy S I9000 samsung screen comes up, goes away for a second, comes up again.
- A page with code appearing from the bottom comes up really fast ( logo in the middle changes quickly) then it disappears.
- whole thing starts again.
UPDATE: I got a picture of the fast screen that comes up. : http://localhostr.com/files/b5NzFRy/2012-08-27 05.07.32.jpg
Some observations.
- I can go into download mode when opening it with the key combo.
- loop only stops when I unplug the battery
I need advice on what caused this and how to fix this, please help me.
Click to expand...
Click to collapse
Installation Procedure for CM9
If you have CWM Recovery
Copy both zip files int internal SDCARD
Boot into recovery
Do a full wipe (data/factory,cache, dalvik)
Install zip from sdcard
Choose zip from sdcard
Select the ROM
You will get boot loop
Again boot into recovery
Install the same zip file one more time
Install google app
Do a full wipe again (data/factory,cache,dalvik)
Reboot your phone
Enjoy...
Hi,
I had the same pb coming from a GB
I think this pb is very common
1) DON'T WORRY !
2) Unplug the battery when bootlooping
3) Put the SGS in Recovery Mode (the CWM's version has changed)
4) Select the CM .zip and flash it AGAIN
5) When it's done, reboot system
This time, everything shoot be OK
Just be carefull with your IMEI (always have a backup of EFS folder !)
anukilimanoor said:
Installation Procedure for CM9
If you have CWM Recovery
Copy both zip files int internal SDCARD
Boot into recovery
Do a full wipe (data/factory,cache, dalvik)
Install zip from sdcard
Choose zip from sdcard
Select the ROM
You will get boot loop
Again boot into recovery
Install the same zip file one more time
Install google app
Do a full wipe again (data/factory,cache,dalvik)
Reboot your phone
Enjoy...
Click to expand...
Click to collapse
Thanks!, this method worked a treat :highfive:
Anyone have a trick yet for CM 10.1 v.22 Nightly, I keep getting a bootloop on all their versions except the original one. This is so frustrating because I have to keep going back to stock and then update to ICS.
kvarug01 said:
Anyone have a trick yet for CM 10.1 v.22 Nightly, I keep getting a bootloop on all their versions except the original one. This is so frustrating because I have to keep going back to stock and then update to ICS.
Click to expand...
Click to collapse
Same here, after the Samsung and CM logos, and splash animation, it says :
"Encryption unsuccessful.
Encryption was interrupted and can't complete. As a result, the data on your phone is no longer accessible.
To resume using your phone, you must perform a factory reset...."
After I tap Reset phone, it goes to CWM recovery.
Do the factory reset and the same thing occured in loop.
I came from JVU and CF root.
anukilimanoor said:
Installation Procedure for CM9
If you have CWM Recovery
Copy both zip files int internal SDCARD
Boot into recovery
Do a full wipe (data/factory,cache, dalvik)
Install zip from sdcard
Choose zip from sdcard
Select the ROM
You will get boot loop
Again boot into recovery
Install the same zip file one more time
Install google app
Do a full wipe again (data/factory,cache,dalvik)
Reboot your phone
Enjoy...
Click to expand...
Click to collapse
How long should the first boot take after following these steps? And does it have to be from SDCARD, because I can't get the rom onto my sd card, I can only do it via usb otg cable
---------- Post added at 05:11 AM ---------- Previous post was at 04:34 AM ----------
anukilimanoor said:
Installation Procedure for CM9
If you have CWM Recovery
Copy both zip files int internal SDCARD
Boot into recovery
Do a full wipe (data/factory,cache, dalvik)
Install zip from sdcard
Choose zip from sdcard
Select the ROM
You will get boot loop
Again boot into recovery
Install the same zip file one more time
Install google app
Do a full wipe again (data/factory,cache,dalvik)
Reboot your phone
Enjoy...
Click to expand...
Click to collapse
Does it have to be from the sdcard or can you do it from a flash drive via usb otg. I cannot get the rom onto my sd card
paradiselost28 said:
Hi,
I had the same pb coming from a GB
I think this pb is very common
1) DON'T WORRY !
2) Unplug the battery when bootlooping
3) Put the SGS in Recovery Mode (the CWM's version has changed)
4) Select the CM .zip and flash it AGAIN
5) When it's done, reboot system
This time, everything shoot be OK
Just be carefull with your IMEI (always have a backup of EFS folder !)
Click to expand...
Click to collapse
The same thing happend to me.
Just plug out the battery and flash again on cwm recovery.
Sent from my GT-I9000 using XDA Premium 4 mobile app

[Q] Jelly Bean Mini Project Noob

Hi all,
First I must point out I'm a bit of a noob at this flashing kernels/roms etc. I want to install Jelly Bean Mini Project | Android 4.1.2 on my xperia x8.
I rooted it ages ago with superoneclick. I got the rom here in the download section of this post and got the kernel here. Not sure how to proceed do i unzip the rom folder called "X8_JBMP-Release4"? I need a tutorial on what programs to use etc. step by step would be handy. I did look did look am continuing to look. Thanks in advance and sorry.
first of all you have installed nAa's jb kernel right?
---------- Post added at 06:27 PM ---------- Previous post was at 06:21 PM ----------
if not, download Flashtool from here
then do the following steps
1. go here and find the "Flashing custom kernel" step
2. Flash the kernel, beforehand, be sure to have the proper drivers installed, go to the flashtool directory, drivers, execute the .exe file then choose drivers for x8, fastboot and flashmode
3. You are ready to flash a kernel, just follow the instructions on the thread I pointed out to you
4. No need to unzip the ROM file as it is a flashable zip, after flashing the kernel power up your device and click the back button a couple of times
5. You are now in the CWM recovery, go to mounts and storage and select: format /system, /data, /cache and then back to the CWM main menu, select Wipe data/factory reset, Wipe cache partition, and to the advanced option, wipe dalvik cache
6. Now you have just performed a full wipe, go to install zip from sd card, find the ROM zip file you just downloaded and install it
7. Then install the GAPPS needed to work with JBMP
8. Reboot and Enjoy
op didn't mention if
a. he already has recovery installed
b. if his bl is unlocked
Just because i don't doesn't mean i can't.
many tairsai
cascabel said:
op didn't mention if
a. he already has recovery installed
b. if his bl is unlocked
Just because i don't doesn't mean i can't.
Click to expand...
Click to collapse
Bootloader is unlocked sorry didn't mention. Titanium back up installed but not sure if that is the backup you are asking about.
Yanisirl said:
Bootloader is unlocked sorry didn't mention. Titanium back up installed but not sure if that is the backup you are asking about.
Click to expand...
Click to collapse
titanium backup is good. :thumbup: you can also enter cwm and make a backup there. otherwise, follow mass's instructions. don't forget to format system cache data in cwm after flashing kernel and before flashing rom. have fun with jb. :thumbup:
Just because i don't doesn't mean i can't.
MassStarvation said:
first of all you have installed nAa's jb kernel right?
---------- Post added at 06:27 PM ---------- Previous post was at 06:21 PM ----------
if not, download Flashtool from here
then do the following steps
1. go here and find the "Flashing custom kernel" step
2. Flash the kernel, beforehand, be sure to have the proper drivers installed, go to the flashtool directory, drivers, execute the .exe file then choose drivers for x8, fastboot and flashmode
3. You are ready to flash a kernel, just follow the instructions on the thread I pointed out to you
4. No need to unzip the ROM file as it is a flashable zip, after flashing the kernel power up your device and click the back button a couple of times
5. You are now in the CWM recovery, go to mounts and storage and select: format /system, /data, /cache and then back to the CWM main menu, select Wipe data/factory reset, Wipe cache partition, and to the advanced option, wipe dalvik cache
6. Now you have just performed a full wipe, go to install zip from sd card, find the ROM zip file you just downloaded and install it
7. Then install the GAPPS needed to work with JBMP
8. Reboot and Enjoy
Click to expand...
Click to collapse
I have correct kernel and the JBMP not sure what GAPPS is.
Yanisirl said:
I have correct kernel and the JBMP not sure what GAPPS is.
Click to expand...
Click to collapse
google apps. i'm not sure about jbmp but naa's minicm10 has a zip file. flash it after flashing the rom.
Just because i don't doesn't mean i can't.
one more noob question
I was wondering about unlocking this phone from the network it is on. Should I get the code and do it first of will I still be able to do it if I wish after the upgrade. Sorry for the noob questions. Thanks for all the other help I have an idea of what to do now.
Sucess!!
Thanks a million guys got it up and running jellybean. First flash of kernel was just sticking on CWM recovery screen no buttons working. flashed back to a stock 2.1 (rom not my original one) and flashed the new kernel again and all went fine. Thank you so much for all this help and thanks to the folks who worked in the release of jellybean. I just need to figure out how to store apps on sd card. time for research.
Option to move apps to sd card is Greyed out in settings/apps section. Any ideas how i might get my apps to move to sd card?
U can odex to get more space..find it in android development, made by TeamMex..
If u're DRAGONFORCE lovers please hit THANKS button,,
Yanisirl said:
Option to move apps to sd card is Greyed out in settings/apps section. Any ideas how i might get my apps to move to sd card?
Click to expand...
Click to collapse
maybe the ROM is missing the 10apps2sd module in the init.d...
you can download App managers from the play store
MassStarvation said:
maybe the ROM is missing the 10apps2sd module in the init.d...
you can download App managers from the play store
Click to expand...
Click to collapse
No, it not missing,
strange...
Looking around on web it seems apps cant be moved after 4.0. Don't know why google did that it was one of the features I most wanted. I guess I could go to something earlier but I like jelly bean :crying:
Yanisirl said:
Looking around on web it seems apps cant be moved after 4.0. Don't know why google did that it was one of the features I most wanted. I guess I could go to something earlier but I like jelly bean :crying:
Click to expand...
Click to collapse
try a clean flash. i'm on 4.1 and i cam move apps fine. though i don't use the native app2sd.
Just because i don't doesn't mean i can't.
Will a reflash do it? do I need to flash back to a stock rom first? Or is there something I need to do to let a2sd work like give it a partition somehow?
Yanisirl said:
Will a reflash do it? do I need to flash back to a stock rom first? Or is there something I need to do to let a2sd work like give it a partition somehow?
Click to expand...
Click to collapse
just format system cache amd data after a full wipe (wipe cache amd dalvik too) and reflash rom.
Just because i don't doesn't mean i can't.
Thanks for the reply. I will try it in a couple of days as I'm busy with work and will post back here with the result.
moving apps
I booted into CWM recovery and used the advanced section to create a 1gb partition left swap size setting at 0 and that fixed the issue. I guess if I wasnt a noob I would have made a partition on the card in the beginning. Apps can now be moved except those that dont allow movement but I am using link2sd for those. Its cool to see jellybean on this phone. I get quite a few hangs/crashes using the browser, bluetooth earpiece connects fine but I cant hear calls on it and the countdown timer is erratic closing by itself quite often. Maybe there are some settings I need to tweak to get the best performance? Thanks again for all the help and replies by the way.

Cannot install gapp in [ROM][JB][4.2.2][JDQ39E] CyanogenMod 10.1

I writing in this thread, because I'm a new user, and haven't access to write in properly thread.
I have a problem with install gapp in
[ROM][JB][4.2.2][JDQ39E] CyanogenMod 10.1 by ADC Team - Release 5 - Kernel 3.4.x
Click to expand...
Click to collapse
rom on S9001.
Rom is install good, everything work, but I haven't google play. I try install gaps a few time, but it still doesn't work.
Mayby I do something wrong...
What I did:
wipe data/factory reset
wipe cache partition
apply update from sdcard -> select rom zip
apply update from sdcard -> select gapp zip
reboot system now
sami_10 said:
I writing in this thread, because I'm a new user, and haven't access to write in properly thread.
I have a problem with install gapp in rom on S9001.
Rom is install good, everything work, but I haven't google play. I try install gaps a few time, but it still doesn't work.
Mayby I do something wrong...
What I did:
wipe data/factory reset
wipe cache partition
apply update from sdcard -> select rom zip
apply update from sdcard -> select gapp zip
reboot system now
Click to expand...
Click to collapse
Which recovery have you got?
First, install TWRP or CWM .
TWRP 2,6 is the best, imho.
Then repeat the operations, you'll success
Dari78 by Tapatalk 2
remember THANKS button!
dari78 said:
Which recovery have you got?
First, install TWRP or CWM .
TWRP 2,6 is the best, imho.
Then repeat the operations, you'll success
Dari78 by Tapatalk 2
remember THANKS button!
Click to expand...
Click to collapse
TWRP 2.6 put on SDcard and install from reboot?
sami_10 said:
TWRP 2.6 put on SDcard and install from reboot?
Click to expand...
Click to collapse
Yes, on sd card, then reboot in recovery and apply update from sd card, then reboot again
Dari78 by Tapatalk 2
remember THANKS button!
Thanks a lot, it's work

How to dualboot KitKat and Android 5.0 Lollipop on Nexus 5

This is a guide of how to dualboot KitKat and Android Lollipop on a Nexus 5. This will allow you to test out Lollipop while keeping a stable ROM to run as a daily driver. I am running CM11, but you can do this with any KitKat ROM, even stock.​
REQUIREMENTS
Nexus 5
Root
Unlocked bootloader
MultiROM
A brain
At least 1 GB of free space (I recommend 4 GB though)
1. Setting up.
I'm assuming you are already rooted if you are planning on doing this. If not, follow this guide to root and unlock the bootloader. http://forum.xda-developers.com/google-nexus-5/orig-development/nexus-5-cf-auto-root-t2507211
1. After verifying you have root on your phone, download MultiROM Manager off Google Play: https://play.google.com/store/apps/details?id=com.tassadar.multirommgr&hl=en
2. Install and open MultiROM Manager and install MultiROM, Recovery and the patched kernel.
Here is what the following is...
MultiROM: This boots before the system and gives you the option of what system you want to boot. When you select the system, it then hands it off to boot. This will not overwrite your current ROM, but make a backup to be safe
Recovery: This is a custom TWRP recovery with options to install a secondary system
Kernel: This will patch your kernel with kexec-hardboot patch which is requires to dualboot in general.
2. Installing Android Lollipop
1. After you install and verify that MultiROM is installed on your phone, download the Android 5.0 flashable zip from the downloads section at the bottom
2. Reboot into the recovery and go to Advanced> MultiROM> Add ROM
3. When you get there, set ROM type to Android and select "Dont share" for kernel sharing and then press next
4. select ZIP file and install "N5_L_PREV_LPX13D.zip" you downloaded earlier and flash it.
If you wish to not root L, you can go ahead and reboot your phone into Lollipop (The first boot will take several minutes). If you do want to root, go on to the next step. Your primary ROM won't be touched as your primary ROM and its root status won't be affected when using MultiROM.
3. Rooting Android Lollipop (optional)
Rooting is completely optional and is not required for it to run. You need to install root if you do plan on using root apps or busybox on Android 5.0.
As of the LPX13D build, there have been changes made in the bootloader that will prevent SuperSU or root from working. If you want to root on the LPX13D build, you will need to flash this bootloader: http://www.reddit.com/r/Nexus5/comments/2jkx7a/
1. Download the SuperSU zip in the downloads section and save it to your phone.
2. Boot into recovery and go to Advanced> MultiROM> List ROMs and select the L ROM you installed earlier (unless you renamed the zip file or the system name, it should show"N5_L_PREV_LPX13D")
3. Select flash zip and flash the SuperSU zip you downloaded.
4. Reboot and you should now be rooted.
Updating Android Lollipop
As of right now, there are issues if you try to do a dirty flash from DP1 to DP2 (These are issues with Android L and not MultiROM). These issues include home button not working, quick settings pulldown not working, no lockscreen when there is one and data issues (at least with Sprint). If you are coming from LPV79 and updating to LPV81C or LPX13D, it is recommended to do a clean install to avoid these issues. If you are doing a fresh install, you don't have to worry about this issue
Android Lollipop Bugs
These are issues with Android Lollipop and not MultiROM
-The issues stated above when certain things don't work after a dirty flash
-During the inatial setup, the phone may freeze and require reboot when trying to connect to wifi (seems like a new bug with LPV81C). The phone will say Connecting and show a white box before it freezes
-Some apps will crash or be buggy (this is to be expected though with the transition to ART)
-More bug reports can be found [Here]
-A list of apps that have issues with working with Android L can be found [Here]
Downloads
Android Lollipop flashable zip: http://forum.xda-developers.com/showpost.php?p=56112246&postcount=5498
L Root: http://download.chainfire.eu/578/SuperSU/UPDATE-SuperSU-v2.14.zip
Thanks
Chainfire for CF Autoroot and SuperSU
Tasssadar for MultiROM to make this dualboot possible
davy917 for posting a solution for people having internal storage issues with L
For more information and general use of how MultiROM works, go to its main thread [here]
Also if you do have the issue where your internal storage doesn't mount, follow this solution found [here]
Thanks! First time trying multiROM & working great
In Android L I can't seem to download anything and all the folders in sdcard directory is empty.. Is there something I'm missing?
davy917 said:
In Android L I can't seem to download anything and all the folders in sdcard directory is empty.. Is there something I'm missing?
Click to expand...
Click to collapse
Strange. I didn't have that problem but I will look in to it. I recommend going to advanced> MultiROM> list ROMs and perform a wipe of the cache and dalvik of your L system. I was able to download without problems and the internal storage worked fine. Also, how much space was there on your phone before doing this
Sent from my Nexus 5 using Tapatalk
I can't boot to L. Says I need a kexec-hardboot enabled kernel.
Sent from my Nexus 5
Elisha said:
I can't boot to L. Says I need a kexec-hardboot enabled kernel.
Sent from my Nexus 5
Click to expand...
Click to collapse
Yeah, you need a kernel that has that patch included to be able to use MultiROM. There are a few of them if you look around.
---------- Post added at 01:53 AM ---------- Previous post was at 01:53 AM ----------
davy917 said:
In Android L I can't seem to download anything and all the folders in sdcard directory is empty.. Is there something I'm missing?
Click to expand...
Click to collapse
L does sdcard differently
ThatGuy94 said:
Strange. I didn't have that problem but I will look in to it. I recommend going to advanced> MultiROM> list ROMs and perform a wipe of the cache and dalvik of your L system. I was able to download without problems and the internal storage worked fine. Also, how much space was there on your phone before doing this
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I had about 11gb of space before doing this. I just wiped cache and dalvik but still same issue, no files in sdcard folders and can't seem to download anything
---------- Post added at 12:22 PM ---------- Previous post was at 12:21 PM ----------
Lethargy said:
L does sdcard differently
Click to expand...
Click to collapse
Do you know how I can access the files in my sdcard?
davy917 said:
I had about 11gb of space before doing this. I just wiped cache and dalvik but still same issue, no files in sdcard folders and can't seem to download anything
---------- Post added at 12:22 PM ---------- Previous post was at 12:21 PM ----------
Do you know how I can access the files in my sdcard?
Click to expand...
Click to collapse
You'll have /system/sdcard/0/ and /system/sdcard/
davy917 said:
I had about 11gb of space before doing this. I just wiped cache and dalvik but still same issue, no files in sdcard folders and can't seem to download anything
---------- Post added at 12:22 PM ---------- Previous post was at 12:21 PM ----------
Do you know how I can access the files in my sdcard?
Click to expand...
Click to collapse
Just wondering, what is your baseband version. I'm just thinking if it may be a firmware issue for some reason. Also try ES File Explorer to see if your files show up in it because my files in sdcard appeared with it
Sent from my Nexus 5 using Tapatalk
Lethargy said:
You'll have /system/sdcard/0/ and /system/sdcard/
Click to expand...
Click to collapse
I don't see such directories.. No sdcard folder in system
---------- Post added at 01:50 PM ---------- Previous post was at 01:49 PM ----------
ThatGuy94 said:
Just wondering, what is your baseband version. I'm just thinking if it may be a firmware issue for some reason. Also try ES File Explorer to see if your files show up in it because my files in sdcard appeared with it
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I am using ES Explorer but no luck
My baseband is M8974A-2.0.50.1.13
When I tried to take a screen shot, I got an error saying cannot save screenshot, storage may be in use. Any idea what the deal is?
davy917 said:
I don't see such directories.. No sdcard folder in system
Click to expand...
Click to collapse
In KitKat, try to find /mnt/shell/emulated/0 or /sdcard in L
Sent from my Nexus 5 using Tapatalk
I can find both, but in L the folders in /sdcard are all empty
davy917 said:
I can find both, but in L the folders in /sdcard are all empty
Click to expand...
Click to collapse
Are they empty if you try to open them in KitKat? Also it looks like your baseband is out of date. I have the baseband M8974A-2.0.50.1.16. I recommend updating your baseband to see if it fixes it. Also what is your primary ROM
Sent from my Nexus 5 using Tapatalk
ThatGuy94 said:
Are they empty if you try to open them in KitKat? Also it looks like your baseband is out of date. I have the baseband M8974A-2.0.50.1.16. I recommend updating your baseband to see if it fixes it. Also what is your primary ROM
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It's not empty when I open in KK.. I'm running SlimKat
I'll try updating my baseband and see if it helps. Thanks for all the suggestions!
davy917 said:
It's not empty when I open in KK.. I'm running SlimKat
I'll try updating my baseband and see if it helps. Thanks for all the suggestions!
Click to expand...
Click to collapse
If all else fails, I recommend just trying to reinstall MultiROM and the patched kernel and remove and reinstall L. Also select CM11 when you install the patched kernel since the CM11 kernel should be compatible with slimkat
Sent from my Nexus 5 using Tapatalk
ThatGuy94 said:
If all else fails, I recommend just trying to reinstall MultiROM and the patched kernel and remove and reinstall L. Also select CM11 when you install the patched kernel since the CM11 kernel should be compatible with slimkat
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yeah I think I'll just try starting over.. Nothing seems to work. I basically don't have any access to storage when on Android L as my secondary. I can't even take photos lol it takes a pic and can't save anywhere
davy917 said:
Yeah I think I'll just try starting over.. Nothing seems to work. I basically don't have any access to storage when on Android L as my secondary. I can't even take photos lol it takes a pic and can't save anywhere
Click to expand...
Click to collapse
There have read people in the Android L thread that have had this same issue. That's why I always thought dual booting with Android L wasn't a good idea.
Got some help from the multirom thread.. Followed the below and it worked fine. Had to reinstall Android L afterwards tho.
1. Install terminal from play store in Android L ROM.
2. In terminal: "su" *enter*
3. In terminal: "restorecon -FR /data/media/0" *enter*
4. Wait.*
5. Reboot.
*If it doesn't boot anymore, delete Android L as ROM, and flash it again trough multirom.
ThatGuy94 said:
If all else fails, I recommend just trying to reinstall MultiROM and the patched kernel and remove and reinstall L. Also select CM11 when you install the patched kernel since the CM11 kernel should be compatible with slimkat
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Slimkat is AOSP/stock kernels.... Not CM11/caf. ?
KJ said:
Slimkat is AOSP/stock kernels.... Not CM11/caf. ?
Click to expand...
Click to collapse
Thanks for the correction. I don't use slimkat so I thought it was using the cm11 kernel.
Sent from my Nexus 5 using Tapatalk

Categories

Resources