http://download.cyanogenmod.org/?device=togari_gpe
Thank you! I've been looking for this. My Z Ultra GPE arrives in the mail today I'll give it a try. In the end though, I think I'll be sticking with pac-man. We'll see.
PR0XIDIAN said:
Thank you! I've been looking for this. My Z Ultra GPE arrives in the mail today I'll give it a try. In the end though, I think I'll be sticking with pac-man. We'll see.
Click to expand...
Click to collapse
How are you liking it so far compared to Pac-man?
any screenshots mate?
madsponge26 said:
any screenshots mate?
Click to expand...
Click to collapse
It's CM11, so it looks pretty much like the GPe ROM you're running now.
LordManhattan said:
It's CM11, so it looks pretty much like the GPe ROM you're running now.
Click to expand...
Click to collapse
so how's the nightly mate?
madsponge26 said:
so how's the nightly mate?
Click to expand...
Click to collapse
I have the regular Ultra and running the GPe ROM, so I can't really give you an answer.
Sent from my C6806_GPe using Tapatalk
Is anyone running the CM11 nightlies on an actual GPE device?
If so, what works and what doesn't?
Crickets................
unlocked bootloader. flash boot.img still in bootlogo in latest nightly.
madsponge26 said:
unlocked bootloader. flash boot.img still in bootlogo in latest nightly.
Click to expand...
Click to collapse
You should probably PM Kali or someone else on the FXP team.
No matter what, I cannot get this CM11 to flash on my GPE...
Nor, have I seen/read anyone that has been able to... Can someone prove me wrong?
Everything is working here.
Please be more specific as to what did you do to get this running on your device.
And make sure you don't flash togari builds, as that won't work.
cdesai said:
Everything is working here.
Please be more specific as to what did you do to get this running on your device.
And make sure you don't flash togari builds, as that won't work.
Click to expand...
Click to collapse
Well, basically I'm getting status 7 aborts in CWM when flashing this rom.
CCJ22 said:
Well, basically I'm getting status 7 aborts in CWM when flashing this rom.
Click to expand...
Click to collapse
can you try from TWRP?
blueether said:
can you try from TWRP?
Click to expand...
Click to collapse
I'll try that next....
during my status 7 it states your phone is a GPE c6806 device, you're flashing for honami. Abort.... I read someone had this same issue some days ago, I'll find that thread and link it here for future people like me
---------- Post added at 01:02 AM ---------- Previous post was at 12:57 AM ----------
Post 21 is the EXACT problem I'm facing right now.
http://forum.xda-developers.com/showthread.php?t=2643616
I get stuck on Google logo (again I have GPE device, non GPE devices would see Sony logo)
And When I get into CWM I have that exact problem as post 21 in above thread.
CCJ22 said:
I'll try that next....
during my status 7 it states your phone is a GPE c6806 device, you're flashing for honami. Abort.... I read someone had this same issue some days ago, I'll find that thread and link it here for future people like me
Click to expand...
Click to collapse
odd, I thought the error was the other way around?
anyways I'm building carbon for the GPe if you want to be a guinea pig
I should say this:
I have no idea how I got CWM & TWRP working on the device to begin with...
But somehow it's working with the vol up for CWM vol down for TWRP
Now, with quickimg I have removed the boot.img from CM11 (after unzipping it) and placed it in the correct folder for quickimg.
I flashed the boot.img while in fastboot on the phone, via quickimg program.
Seems to have worked as the response is:
Flashing, please wait...
sending 'boot' (11654 KB)...
OKAY [ 0.484s]
writing 'boot'...
OKAY [ 0.767s]
finished. total time: 1.251s
Done. Please check log for errors.
And finally, I wipe dalvik, cache, etc...
And boom, it's working now.
I have no idea what the heck was wrong earlier.
IT's frustrating cause I am the type that likes to know what I did wrong.
---------- Post added at 01:21 AM ---------- Previous post was at 01:20 AM ----------
blueether said:
odd, I thought the error was the other way around?
anyways I'm building carbon for the GPe if you want to be a guinea pig
Click to expand...
Click to collapse
Yes, I'd have no problem beta testing for carbon
---------- Post added at 01:31 AM ---------- Previous post was at 01:21 AM ----------
well now that I have CM11 on, I can tell ya that com.android.phone has stopped working message will not go away. After I click on it pops back up after 3 seconds.
Driving me crazy.
CCJ22 said:
I should say this:
I have no idea how I got CWM & TWRP working on the device to begin with...
But somehow it's working with the vol up for CWM vol down for TWRP
...
well now that I have CM11 on, I can tell ya that com.android.phone has stopped working message will not go away. After I click on it pops back up after 3 seconds.
Driving me crazy.
Click to expand...
Click to collapse
So that you have it installed, although not working it should be simple to try liquid
Did you wipe data and both caches?
It might be a few hours before carbon is built and uploaded, and I have to get to bed early tonight as I have to get up for work at 3am
blueether said:
odd, I thought the error was the other way around?
anyways I'm building carbon for the GPe if you want to be a guinea pig
Click to expand...
Click to collapse
blueether said:
So that you have it installed, although not working it should be simple to try liquid
Did you wipe data and both caches?
It might be a few hours before carbon is built and uploaded, and I have to get to bed early tonight as I have to get up for work at 3am
Click to expand...
Click to collapse
I figured out the problem with the com.process... I cleared cache and data on the dialer app, restarted phone and all is well.
SO far this rom is smooth.
The dpi seems greater then then stock GPE rom. Everything on the screen seems smaller yet I can see more on the screen then before.
No rush on carbon. Whenever you have it up, I'll give it a whirl for ya.
Related
http://forum.xda-developers.com/google-nexus-5/general/rom-unofficial-cm12-5-0-rom-myfluxi-t2934548
You guys think that maybe it's portable to our device?
And the developers who are maybe working on a port - I hope it helps somehow...
Oh, and this too: http://forum.xda-developers.com/optimus-4x-hd/general/dev-unofficial-cm12-p880-t2934360/post0
must be buggy as hell. would be cool to try it but whats the point of doing all the work when it 90% sure wont be daily driver capable anyway
metteduch said:
must be buggy as hell. would be cool to try it but whats the point of doing all the work when it 90% sure wont be daily driver capable anyway
Click to expand...
Click to collapse
I don't know, posted it just in case
The creator said it was stable enough to use as a daily... I'm almost done creating a flashable zip based on it, but there's probably about a 90% chance of it not working... Is someone willing to test it?
I am warning that this is the first port I have done. I used CM11 11/10 Nightly as the base and the posted ROM as the Port, and followed the instructions
HTML:
here
with minor adjustments to allow ART to run. At the very least, I could post it and someone more experienced than me could look at it and tell me what they think?
mjoecarroll said:
The creator said it was stable enough to use as a daily... I'm almost done creating a flashable zip based on it, but there's probably about a 90% chance of it not working... Is someone willing to test it?
I am warning that this is the first port I have done. I used CM11 11/10 Nightly as the base and the posted ROM as the Port, and followed the instructions
HTML:
here
with minor adjustments to allow ART to run. At the very least, I could post it and someone more experienced than me could look at it and tell me what they think?
Click to expand...
Click to collapse
I'd be happy to test. But if something goes wrong I can go back with backup from recovery, right?
mjoecarroll said:
The creator said it was stable enough to use as a daily... I'm almost done creating a flashable zip based on it, but there's probably about a 90% chance of it not working... Is someone willing to test it?
I am warning that this is the first port I have done. I used CM11 11/10 Nightly as the base and the posted ROM as the Port, and followed the instructions
HTML:
here
with minor adjustments to allow ART to run. At the very least, I could post it and someone more experienced than me could look at it and tell me what they think?
Click to expand...
Click to collapse
Yup, happy to test it too. I doubt it'll work due to kernel issues but its worth a shot!
Any word if he got it booting
mjoecarroll said:
The creator said it was stable enough to use as a daily... I'm almost done creating a flashable zip based on it, but there's probably about a 90% chance of it not working... Is someone willing to test it?
I am warning that this is the first port I have done. I used CM11 11/10 Nightly as the base and the posted ROM as the Port, and followed the instructions
HTML:
here
with minor adjustments to allow ART to run. At the very least, I could post it and someone more experienced than me could look at it and tell me what they think?
Click to expand...
Click to collapse
Willing to test too
Sent from my LG-D802 using XDA Premium 4 mobile app
When I get back to my room, I will try. Recovery shouldn't be hurt, but just in case, you should reflash it after installation. I am warning, this is my first time working on something like this and preferably, someone with more experience than me should take a look at it before the ROM is flashed.
---------- Post added at 10:04 PM ---------- Previous post was at 09:24 PM ----------
I'm back. I forgot to mention previously, this is for the D801 model. I could attempt to create other ROMs for other devices, but I will need to do some checking first.
Vs980 will test if u can get it to boot
mjoecarroll said:
When I get back to my room, I will try. Recovery shouldn't be hurt, but just in case, you should reflash it after installation. I am warning, this is my first time working on something like this and preferably, someone with more experience than me should take a look at it before the ROM is flashed.
---------- Post added at 10:04 PM ---------- Previous post was at 09:24 PM ----------
I'm back. I forgot to mention previously, this is for the D801 model. I could attempt to create other ROMs for other devices, but I will need to do some checking first.
Click to expand...
Click to collapse
I'm here when you'll build something for the D802, I don't know anyone with D801 so I can't really help... /:
And even L9 joins. http://forum.xda-developers.com/optimus-l9/development/android-5-0-lg-optimus-l9-aosp-t2937142
I have a D801
Never going to work... Sorry but it's true, You need a custom kernel built on the Lollipop source for it to work.
OMG guys even little L9 got 5.0 -.-
KiaTheKing said:
OMG guys even little L9 got 5.0 -.-
Click to expand...
Click to collapse
Hold your horses. It'll happen when it happens. Let the devs do their thing (side note running an almost completely stable build of Lollipop on my brick of a tablet Asus TF300T).
In development for the Galaxy S4 too: http://forum.xda-developers.com/galaxy-s3/development/wip-cyanogenmod-12-t2936990
Can someone maybe explain to me the issue with the kernel? I mean, if other devices (from LG and other OEMs) can boot this ROM, why can't we?
fma965 said:
Never going to work... Sorry but it's true, You need a custom kernel built on the Lollipop source for it to work.
Click to expand...
Click to collapse
Trying to make a Port of Stock Android Lollipop right now, actually, just got the bootanimation \o/ .
I hope you are really trying, not trolling us)
A guy in this community said that he'll port L preview, but it actually wasn't țhe case at all and he was banned.
Thank you for your work. I hope I will not be misunderstood.
NEO2598 said:
I hope you are really trying, not trolling us)
A guy in this community said that he'll port L preview, but it actually wasn't țhe case at all and he was banned.
Thank you for your work. I hope I will not be misunderstood.
Click to expand...
Click to collapse
Hahahahaha, Don't worry, i am not trolling you guys, i love this forum, and i really hope to be like all the great developers from here...
I am trying to port it, but i don't guarantee anything, it can fail, and i can give up, but, i will try, as far as i can. Sorry for the bad English.
I'm just going to go ahead and leave this here. I have yet to test it since I no longer own the device but it's the same thing as my 5.0.2 stock ROM so I see no reason why it shouldn't work. Reason I started new thread just for this is because bigxie's thread was closed sadly .
Features (Not Really, Just Stock Crap)
Odexed
NO ROOT (Want it? Download THIS and flash it afterwards)
100% Stock - No modifications
Can flash over existing stock 5.0.2 ROM
Want to update from 5.0.2 to 5.1? Follow these steps.
Download this ROM and go into your recovery.
Flash this ROM WITHOUT WIPING ANYTHING!
If you want to root or keep your root flash over the file above next to the "NO ROOT" text.
Then click Wipe Cache/Dalvik and slide.
Reboot.
.....
Profit?
Want a fresh new start on android 5.1?
You guys already know the drill its a nexus for ****s sake. Download ROM, Reboot to recovery, wipe everything except internal sd card, and OTG, flash ROM. Profit? Not hard
Now to the good stuff:
LMY47D Android 5.1 - Broken for now.
Credit
Bigxie - For his original updater script
Google - Yeah, yeah..
Me
Other (DISCLAIMER - READ)
Oh yeah did I mention that this is just a test and the first few people are basically guinea pigs. I am not RESPONSIBLE FOR WHAT HAPPENS TO YOUR DEVICE, YOU ARE FLASHING UNDER THE CONSENT THAT IT CAN POSSIBLE BREAK YOUR DEVICE (EXTREMELY UNLIKELY). If people report that is working then its all good if not then I will make a few adjustments and it should be fine and all. Worst thing that can happen is Google Play Services crashing upon setup (For clean flashes of course).
Thanks!!!!!
Gapps included?
Sent from my Nexus 5 using XDA Free mobile app
smalss said:
Gapps included?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Yepp.
Thanks a bunch for this.
New radio and bootloader included?
Gaffadin said:
Thanks a bunch for this.
New radio and bootloader included?
Click to expand...
Click to collapse
Look in the zip.
dEris said:
Look in the zip.
Click to expand...
Click to collapse
I wouldn't know what to look for, hence the question.
Gaffadin said:
Thanks a bunch for this.
New radio and bootloader included?
Click to expand...
Click to collapse
No.
usually i have no issues, but this one freezes right before it gets installed in recovery. :[
t00dumb said:
usually i have no issues, but this one freezes right before it gets installed in recovery. :[
Click to expand...
Click to collapse
Sometimes it just takes a while to install that it looks like it froze.
Sent from my Nexus 5 using XDA Free mobile app
Yup, it flashes successfully after awhile. Stays at boot animation for quite a bit on first boot. Reverts to boot animation at end of optimizing apps (where it says starting apps), happened for 3 times before I gave up and flashed something else.
loop at optimizing apps 3-5times...lol
Can not get passed boot animation
Sent from my Nexus 5 using XDA Premium 4 mobile app
great. this is what i want~
---------- Post added at 07:18 PM ---------- Previous post was at 06:42 PM ----------
I flashed this rom with SuperSU and double wipe. When I boot into the system, I could not jump out of the "Optimizing apps" loop.
After 4 times of loop, I gave it up.
Same problem for me too - boots, updates apps, gets to "starting", then just reboots and starts updating apps again.
Was this even tested?!
Shame as I find it handy to have an installable version of the vanilla ROM to hand.
PugRallye said:
Same problem for me too - boots, updates apps, gets to "starting", then just reboots and starts updating apps again.
Was this even tested?!
Shame as I find it handy to have an installable version of the vanilla ROM to hand.
Click to expand...
Click to collapse
You obviously didn't read the first line of the OP.
iamterence said:
You obviously didn't read the first line of the OP.
Click to expand...
Click to collapse
You're right I didn't.
But what's the point in putting up something that's completely untested (and apparently doesn't even work)?
Pointless waste of time IMO
PugRallye said:
You're right I didn't.
But what's the point in putting up something that's completely untested (and apparently doesn't even work)?
Pointless waste of time IMO
Click to expand...
Click to collapse
Guess you didn't read the 'Other (DISCLAIMER-READ)' part of the OP then.
Big thanks for carrying on Bigsys work. I was going to put my phone to stock uprooted to get the update. He did a lot for us here and I'm glad you are carrying on where he left off. Very good job, BTW)
---------- Post added at 06:00 PM ---------- Previous post was at 05:53 PM ----------
Stop slagging the guy. God some pple. He said the first few are testing it. I wouldn't blame him if he doesn't, you ingreats..
Guys, just go to Google page and download official 5.1 update and flash it with fastboot.
Yes guys, it's here. I have ported Cyanogenmod 11 to our Desire 610. Just flash it normally through TWRP and you should be find. BTW, I ported it using slimkat. Thanks Zihan!
FLASH AT OWN RISK
BUG LIST:
Front+Rear Cameras not working
You tell me!
This rom needs testers so anyone please give it a shot and update that buglist please!!!
DOWNLOAD LINK BELOW: (ITS THROUGH MEGA)
https://mega.nz/#!lY9g1JYL!bjndT25FD-BiBgaDx5iyV_gwiUXQrKHCaBuDZvXfeYc
To download to phone storage, on your browser, go to settings, or 3 little dots and check desktop view. (transfer to sd or keep on internal but don't wipe internal mem before flashing)
If the rom at least works, I'll try building CM12.1, so test it people!
UPDATE: 11/8/15
Hey guys, just ported the rom again.
Hopefully bootloop is fixed. Its on mega again and I think it may work. I modified boot.img so it will probably work.
Please test!
LINK BELOW:
https://mega.nz/#!gQsjGBDT!KqWeNTO8hExnStEY7U5IHpdqqwnZhyZ67LmlnbOknsU
I'm getting bootlooped after installing it on my european a3ul. :/
Great work though, this phone is in dying need of dev support.
Bootloop
Okay, I'll look at the port and I'll probably re port it again with a different method
Thats nice guys, will flash this If u fix the bootloop.
But can we expect maybe cm12?
Best reagrds.
Next Weekend Maybe will fix bootloop
termiator said:
Thats nice guys, will flash this If u fix the bootloop.
But can we expect maybe cm12?
Best reagrds.
Click to expand...
Click to collapse
Hey guys,
I have school tomorrow. If I have extra time during these 5 days, I will look into the bootloop. But the updated rom will probably be released on the weekend, when I have the time to port it again.
And yes, you could expect CM 12.1 soon, as I probably will build from source, but right now I'm focusing on CM11. But CM 12.1 will be coming in about 2-3 months or less.
Magicstick5
What about the system, we want to wipe that right
Sent from my HTC Desire 610 using XDA Free mobile app
then the rom works for AT & T? Or have bootloop for all?
CM11 and if it works
Hi guys,
So, CM11 for the Desire 610 needs testers. I have not tested yet because for some schoolwork, I need a camera, and the camera is obviously not working, as I stated because the port rom had camera issues too AND ALSO MOBILE DATA ISSUES. The rom could work on the US and other regions versions of this phone too. So if it works for your phone, just post on this thread. And you could also test it to see for yourself.
I will probably test tommorow though
MGfusion said:
What about the system, we want to wipe that right
Sent from my HTC Desire 610 using XDA Free mobile app
Click to expand...
Click to collapse
Yes, wipe system too. If you need more help, just google how to flash a rom highonandroid
Bootloop
Next weekend bootloop will be fixed
btw You can also try slimkat, its not very buggy, only speaker phone issues and camera, but just use a 3rd part camera app
I was getting text messaging issues, it the only reason I stoped using the slimkat Rom
Sent from my HTC Desire 610 using XDA Free mobile app
---------- Post added at 11:18 PM ---------- Previous post was at 11:17 PM ----------
Also this Rom does not work on us variant, i tested it and got the cm boot screen, and nothing else. It is good progress tho, I wouldn't even know where to start
Sent from my HTC Desire 610 using XDA Free mobile app
MGfusion said:
I was getting text messaging issues, it the only reason I stoped using the slimkat Rom
Sent from my HTC Desire 610 using XDA Free mobile app
---------- Post added at 11:18 PM ---------- Previous post was at 11:17 PM ----------
Also this Rom does not work on us variant, i tested it and got the cm boot screen, and nothing else. It is good progress tho, I wouldn't even know where to start
Sent from my HTC Desire 610 using XDA Free mobile app
Click to expand...
Click to collapse
I had a quick try of this last night. Turns out it has the same bootloop problems I had when I ported cm11 over slimkat a couple of months ago. When I tried, I fixed the bootloop OK but then kept getting system ui force close because of some problem with surface flinger. After some research I came to the conclusion that to successfully port other roms we first need a cm base built from source. Hopefully @magicstick5 can work some magic that I could not. In the meanwhile I will keep trying to build it from source(I've got it booting but not much working yet).
MiniBlu
MiniBlu said:
I had a quick try of this last night. Turns out it has the same bootloop problems I had when I ported cm11 over slimkat a couple of months ago. When I tried, I fixed the bootloop OK but then kept getting system ui force close because of some problem with surface flinger. After some research I came to the conclusion that to successfully port other roms we first need a cm base built from source. Hopefully @magicstick5 can work some magic that I could not. In the meanwhile I will keep trying to build it from source(I've got it booting but not much working yet).
MiniBlu[/QUOTE
I can try to port agilain next weekend. I read that you just need a already built tom for your phone which for us, is slimkat
Click to expand...
Click to collapse
Just wondering has anymore progress been made yet? Just curious cause I really want to use the cyanogenmod
Sent from my HTC Desire 610 using XDA Free mobile app
boot.img contains kernel and others files needed to startup our device, right? How about changing the boot.img from stock to the rom? Mb this will help fix the bootloop?
termiator said:
boot.img contains kernel and others files needed to startup our device, right? How about changing the boot.img from stock to the rom? Mb this will help fix the bootloop?
Click to expand...
Click to collapse
This rom is ported from slimrom which already contains stock kernel(boot.img).
Yea same, even the apps don't work, when I copy the apps from /priv-app and /app to a slimkat rom.
magicstick5 said:
MiniBlu said:
I had a quick try of this last night. Turns out it has the same bootloop problems I had when I ported cm11 over slimkat a couple of months ago. When I tried, I fixed the bootloop OK but then kept getting system ui force close because of some problem with surface flinger. After some research I came to the conclusion that to successfully port other roms we first need a cm base built from source. Hopefully @magicstick5 can work some magic that I could not. In the meanwhile I will keep trying to build it from source(I've got it booting but not much working yet).
MiniBlu[/QUOTE
I can try to port agilain next weekend. I read that you just need a already built tom for your phone which for us, is slimkat
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Stay tuned. Real cm11 built from source coming soon.
Darrennchan8 said:
Yea same, even the apps don't work, when I copy the apps from /priv-app and /app to a slimkat rom.
Click to expand...
Click to collapse
Ported againg
magicstick5 said:
MiniBlu said:
I had a quick try of this last night. Turns out it has the same bootloop problems I had when I ported cm11 over slimkat a couple of months ago. When I tried, I fixed the bootloop OK but then kept getting system ui force close because of some problem with surface flinger. After some research I came to the conclusion that to successfully port other roms we first need a cm base built from source. Hopefully @magicstick5 can work some magic that I could not. In the meanwhile I will keep trying to build it from source(I've got it booting but not much working yet).
MiniBlu[/QUOTE
I can try to port agilain next weekend. I read that you just need a already built tom for your phone which for us, is slimkat
Click to expand...
Click to collapse
Okay guys, I got some free time and ported again. It successfully booted! But....it's not usable As soon as it got into the home screen, the systemui started crashing preventing me from doing anything. I had to reboot and flash slim again. I'll try porting with a different method though. Stay tuned
Click to expand...
Click to collapse
Nevermind
Guys, theres an update on my first post for the rom. Try that one out. Just ported it again on Sunday
here is a link !
https://www.androidfilehost.com/?fid=24269982086992417
who tested this rom , please leave a review
dowloading...
Edit: Boots correctly, but when the Welcome screen appears it reboot... How do I log that?
Just be careful when it comes to bootloaders etc
Not working on 802 stuck. Restart automatically when arrive to the first configuration screen.
Uechy said:
dowloading...
Edit: Boots correctly, but when the Welcome screen appears it reboot... How do I log that?
Click to expand...
Click to collapse
How did you install it? I did a clean install with lollipop base but it's stuck on CM logo for 5 minutes...
For the welcome screen, what gapps did you try? I read that on G4 and G3 OpenGApps had problems...
ferap said:
Not working on 802 stuck. Restart automatically when arrive to the first configuration screen.
Click to expand...
Click to collapse
i've same problem. :c
Callintz96 said:
How did you install it? I did a clean install with lollipop base but it's stuck on CM logo for 5 minutes...
For the welcome screen, what gapps did you try? I read that on G4 and G3 OpenGApps had problems...
Click to expand...
Click to collapse
I first try with DeltaDroidGapps. I see the stuck on the config scrren and i reinstall (always with all wipes) without any gapps. I search on dev/log to see if there is any log but nothing...
I have the lollipop Hybrid bootstacks and I was on exodus ROM
So it's better to wait a stable Build
Good to see the progress though, even if the majority of it doesn't work
---------- Post added at 02:52 PM ---------- Previous post was at 02:46 PM ----------
Uechy said:
I first try with DeltaDroidGapps. I see the stuck on the config scrren and i reinstall (always with all wipes) without any gapps. I search on dev/log to see if there is any log but nothing...
I have the lollipop Hybrid bootstacks and I was on exodus ROM
Click to expand...
Click to collapse
I don't think it has to do with the bootloader then, cause then it would keep boot looping and never reach the configuration screen
Will work on HTC One M9 pw?
JuanKca said:
Will work on HTC One M9 pw?
Click to expand...
Click to collapse
Are you lost?
Finally good news! @JuanKca do not try this one on your M9!
Someone posted a fixed gapps package for 6.0 on the AICP Google+ page choose arm nano or pico depending on what apps you want.
It's not working - I got a reboot after welcome screen. With and without GApps. So it's probably bad build or it's not ready yet.
This is only for D802? I have a D801 (T-Mobile).
I'm gonna flash this on my vs980 wonder how well that'll go
zmankiller said:
I'm gonna flash this on my vs980 wonder how well that'll go
Click to expand...
Click to collapse
Please don't.
any one knows what bootstacks or bootloader should we flash before flashing this rom?
errikosd said:
Please don't.
Click to expand...
Click to collapse
Ha I didn't work but I edited the updater script and then I had the same problems the other people were having
First of all i've searched everywhere in the last 2 days but found nothing, i have a Xiaomi Redmi Note 3 Pro and i've installed the cm-13.0-20161117-NIGHTLY-kenzo(latest) everything is working fine, flashed the Xposed framework and installed the apk and again everything is fine but when i decide to install any module no and i reboot to activate it i just get stuck at the Android robot face animation.. can i get somehelp somewhere?
What robot face??...do you mean the boot logo..or the something else?
hitesh1792 said:
What robot face??...do you mean the boot logo..or the something else?
Click to expand...
Click to collapse
Yep i mean the bootlogo animation
Paura7 said:
Yep i mean the bootlogo animation
Click to expand...
Click to collapse
Go to twrp recovery and clean install the ROM
---------- Post added at 08:18 PM ---------- Previous post was at 08:16 PM ----------
You might have installeded an xposed module which is either not compatible with your device or the os version hence you are experiencing bootloop...
hitesh1792 said:
Go to twrp recovery and clean install the ROM
Click to expand...
Click to collapse
Tried several times but i just can't get xposed to work as it should, everytime when i install whenever module and reboot it just get to that point.. i just wanted to fix the issue
Paura7 said:
Tried several times but i just can't get xposed to work as it should, everytime when i install whenever module and reboot it just get to that point.. i just wanted to fix the issue
Click to expand...
Click to collapse
which xposed framework are u flashing?
hitesh1792 said:
which closed framework are u flashing?
Click to expand...
Click to collapse
I've installed the latest .apk (XposedInstaller_3.1.1.apk) and ofcourse the latest framework (xposed-v86-sdk23-arm64.zip)
Also i've used CM13 some months ago and Xposed worked like a charm.. i don't know why this time it's giving so much problems
Paura7 said:
I've installed the latest .apk (XposedInstaller_3.1.1.apk) and ofcourse the latest framework (xposed-v86-sdk23-arm64.zip)
Also i've used CM13 some months ago and Xposed worked like a charm.. i don't know why this time it's giving so much problems
Click to expand...
Click to collapse
Try may b a diff rom...like RR..
hitesh1792 said:
Try may b a diff rom...like RR..
Click to expand...
Click to collapse
I'm not interested so much in changing room because i've always been a fan of CM..
Same problem was with me, did a clean install without xposed and everything's good. (I'm on cm14 atm)
Paura7 said:
I'm not interested so much in changing room because i've always been a fan of CM..
Click to expand...
Click to collapse
Try using some earlier nightly..
balazs312 said:
Same problem was with me, did a clean install without xposed and everything's good. (I'm on cm14 atm)
Click to expand...
Click to collapse
As far as i know there is no official Xposed for cm14 but if anyone has my problem i found this that should be the fix
http://forum.xda-developers.com/xposed/announcement-cm-bootloop-issues-xposed-t3501945
Seems you need to flash a nightly that was pushed before november and everything should be good to go, ill try it later and let u know
Paura7 said:
As far as i know there is no official Xposed for cm14 but if anyone has my problem i found this that should be the fix
http://forum.xda-developers.com/xposed/announcement-cm-bootloop-issues-xposed-t3501945
Seems you need to flash a nightly that was pushed before november and everything should be good to go, ill try it later and let u know
Click to expand...
Click to collapse
Yes, it is being fixed atm, we also found a temporary solution http://forum.xda-developers.com/redmi-note-3/how-to/fix-fix-bootloop-issues-xposed-roms-t3503184