Hi guys!
Recently i buy this Photon Q 4G LTE Sprint to my wife's birthday.
It's a wonderfull device with a nice hardware, but the best is the external keyboard (She likes it, because his old device was Motorola dextr, and she was used to), but we're from brazil and my first difficulty was to find a rom that support drivers without bugs.
So here i was: My first try was MIUI. I unlocked my bootloader, rooted and installed TRWP. Didi Backup, formated and installed MIUI, :good:
First i tryed with Kernell the UFO developed for it, and the device don't boot. After i tryed just the rom, but it has no modem or wifi. So i flashed up the stock rom modem img and worked fine.
But apks like "retrica" doesn't work with it, bringing black photos and others apks made for instragram. I love this rom and i have installed in my Xperia Play. It works perfect, but in this device have a lot of bugs, so i give up.
I know how to use it with bugs, but not my wife. Then i had to try another one.
I downloaded Cyanogenmod CM10.1, CM10.2, CM11 nightly, snapshot. Then after try all "Xt897" roms, i tryed all "moto_msm8960".
I can't get in any of this roms make my wifi or 3G work. I believe that modem is not compatible. Even if i tryed to flashed stock modem after, i still had no signal at all. No IMEI, no MAC Address, nothing. :crying:
This device have few alternative roms, so i decided try to translate the rom with less bugs at all. I picked up the stock rom JellyBeans 4.1.2, but this was my second failure. A language patch is something that you don't find in market, and to disassembly entire rom and work in a translate is something beyond my knowledges.
So i have an answer to someone that know how to do a fix patch to wifi in cyanogenmod(Specific "cm-11-20140518-NIGHTLY-moto_msm8960.zip" ), or someone good in translate rom, or input a language in stocked rom, like The Solutor did in " [Full ICS ROM] Multilanguage/Toggle2g /STK/Tethering" (but the rom he used was 4.0.4 and it have bugs).
I will be grateful for any help. :fingers-crossed:
Hmm, what's the language you want (CM11 already have lots of them - not in the list?), and what WiFi/3G problem are you having? And you also failed to RSD the phone back to stock?
My recommendation is you first sort the RSD thing out and get the phone back to stock 4.1.2, and flash everything from that onwards. Assuming that you don't do anything wrong in the process, you should have no quirks with WiFi/3G.
Sent from Google Nexus 4 @ CM11
Try MoreLocale2 for the stock ROM language issues.
As for the CM issues... I agree with Andy, if it works in stock form, it "should" work on CM - at least that has been my experience.
You are clean wiping / factory resetting before or after flashing CM yes? I see you have done this step for MIUI, so I am thinking that you have already done this step...
If you have, can you provide logs from CM if the wiping/RSD'ing doesn't work?
Thx for help guys...
AndyYan - The language i need is Portuguese(Brasil) and it has on CM 11 and MIUI.
I did it as you said. I downloaded stock from here:
http://sbf.droid-developers.org/phone.php?device=3
Rom version: Android 4.1.2 - Blur_Version.98.10.5.XT897.Sprint.en.US)
And flashed by RSD.
Everything ok till here. No errors, nothing wrong. Wifi working as well, and the network.
My MIUI was taken from here: http://forum.xda-developers.com/showthread.php?t=2444449 (GSM one).
Cool rom, it has wifi and network, but camera bugs with some apks. For me ok, but not for my wife. So this rom was discarded.
CM i dwonloaded from here: http://download.cyanogenmod.org/?device=moto_msm8960
The last one was: cm-11-20140521-NIGHTLY-moto_msm8960.zip (i tryed all of then "XT897" and "moto_msm8960", but none of them could get my network working. No wifi, no IMEI, no MAC, no wifi).
CM was my hope, because it has my language, but in all tries i did the wipe in cache, dalvik, system, factory, even internal memory, before installing, and cache or dalvik after flash. I tried this in all (tried not wiping too) and still has no modem.
After this, just for try, i flashed stock modem "NON-HLOS.bin". Still got no modem in any CM roms.
arrrghhh - i did try "MoreLocale2" for the stock rom, and "Set Locale and Language" (and more). This softwares did a nice job for keyboards and apks, but system stays intact in english. It need to be a real translation for my wife.
My guess is that this issue can be easily solved.
If all JB roms have the same system(at least for "moto_msm8960" processor kind ).
This ROM is generic for Motorola Atrix HD, Electrify M, Photon Q, RAZR HD, and RAZR M right?
Razr HD is a type of phone that came to my country.
Is it possible compile a system from Brasil career stock, for this phone with modem and anything else from my stock rom? Does it will crash my phone?
Please provide logs from the latest build of CM after booting and attempting to engage/connect to wifi.
Logs??
Sotty about my doubt, but i don't know what kind of logs do you want(i'm not used to).
Logs from TWRP in instalation?
This is easy. Installation was made with no errors and succesfully.
Does CM made logs itself??
If does, i dont know how to get them. Please send me a link.
Skymidt said:
Sotty about my doubt, but i don't know what kind of logs do you want(i'm not used to).
Logs from TWRP in instalation?
This is easy. Installation was made with no errors and succesfully.
Does CM made logs itself??
If does, i dont know how to get them. Please send me a link.
Click to expand...
Click to collapse
CM does create logs. If you're not familiar with them, the easiest way is to use an app from the Play Store... which I'm not sure how you will manage without wifi or mobile data, and I assume you are not familiar with adb.
I can go thru the detail, but it's a bit involved. Perhaps this thread will help you?
Once you know how adb works, there's actually an easier method than using adb logcat to output to a file - there are logs stored in '/data/logger'. So:
Code:
adb root
So you can have the permissions to pull the files, then pull them:
Code:
adb pull /data/logger
Will pull all of the log files to wherever your command prompt is. If you 'cd' (change directory) to your desktop, doing the adb pull will send all the log files to your desktop.
Let me know if you have any questions, good luck.
Logs from Adb
Yeap! I'm familiar with ADB!!
(i'm not expert in it, but i already did something with that...)
I don't know exactly what are you lookin for, so i did two logs.
First a complete boot:
Code:
adb reboot system
adb logcat -v long > boot_log.txt
And one for especific modem log from boot
Code:
adb reboot system
adb logcat WifiStateMachine:E *:S -v long > just_wifi_error.txt
(I believe this this won't help u a lot?!)
The first one is the most complete solution for this and have all the boot infos, errors and other things.
If am i wrong please say the correct command to use.
I forgot something...
In filemanager i can't access internal storage.
It shows /storage/emulated/0, and points to nothing.
If i'm right, this was a well know bug on CM 10.2, which supposedly been fixed in CM 11 right?!
I think that information can help to solve this bug...
Please try the adb pull command I sent... Those logs are not very helpful, and quite difficult to read.
However, I have a feeling if you use RSD Lite to flash everything back stock, confirm it works, then start with the latest CM, I'd be curious if it works.
Also, someone mentioned they needed to install the CM10.2 snapshot before going to CM11 - or else BT and wifi did not work.
Eureca...
That is something that i didn't tried! I'd never flashed CM 10 in first!!!
I'm downloading "cm-10.2-20131102-SNAPSHOT-M1-xt897.zip ".
Fisrt i'll flash stock "Blur_Version.98.10.5.XT897.Sprint.en.US" with RSD.
Then fastboot "logo.bin" (to avoid warning unlocked), and TRWP(my stock have a original recovery that can't install CM. I can edit XML, but to cleanse my conscience i'll let this way).
After i'll install "cm-10.2-20131102-SNAPSHOT-M1-xt897.zip" with TRWP and boot with this one.
Then i'll flash "cm-11-20140526-NIGHTLY-moto_msm8960.zip ".
But i'll have to do this at night(it's 12pm here), because i'm working today.
If that don't work i'll pull the log that you said here, but I come back to thank.
Same problem
I confess I was hopeful in that case you said to flash first the CM 10.2.
But again failed. I tried two ways:
In both I tried to install the Snapshot CM 10.2, then the CM 11.
There is no way that cell boot with "CM 10.2" in any case. That saty on boot animation for several time(i waited 30 minutos each).
In the first I downgraded to version 4.0.4 stock to see if the modem worked.
After that i flashed CM 10.2 that stood in boot animation, then CM 11 booted without modem signal (no wi-fi, no signal).
I taked the log for that version (attachment named log_4.0.4.7z)
On the second attempt, I used the default stock 4.1.2.
After CM 10.2 which was stucked on boot animation again, then CM 11 again booted without modem signal (no wi-fi, no signal).
I taked the log for that version (attachment named log_4.1.2.7z)
Strange thing happened on both CM 11 boot. When the system's load, it shows a message "The clock stopped". This is strange thing for me.
Can you wait for CM10.2 to boot...? There is a fsck process which sometimes takes quite a long time to boot.
Also, for your FC issue - you are clean flashing the ROM everytime? You are doing a factory reset everytime you flash a new ROM?
Edit - looking at your logs, I don't think the fsck is the issue... something is causing the CM10.2 boot to die over and over. Please try clean flashing...
I clean everything before.
Yeap. What do you call a clean flashing?
Everytime i flash some ROM, i do factory reset, clean cache and dalvik.
The ROM is flashed on a clean state of the stock one. Is this the clean you are talking about?
CM was taken about 30 minutes to boot, and yet don't load system.
This is why i stop that and flash CM 11 over it.
Is this time bigger than that? How long your cell take to boot this CM 10.2?
Skymidt said:
Yeap. What do you call a clean flashing?
Everytime i flash some ROM, i do factory reset, clean cache and dalvik.
The ROM is flashed on a clean state of the stock one. Is this the clean you are talking about?
CM was taken about 30 minutes to boot, and yet don't load system.
This is why i stop that and flash CM 11 over it.
Is this time bigger than that? How long your cell take to boot this CM 10.2?
Click to expand...
Click to collapse
Yes, factory reset == clean flash.
As for the long boot, I'm not sure the fsck is your issue - basically there is a process which runs a disk check, and sometimes this will make the boot take quite longer than usual. I can't say how long, I've never personally experienced the issue.
However, the fact that CM10.2 isn't booting is a little disturbing. I've heard some people report 45-60 mins... can you do me a favor, charge up the phone, and try to let it boot for at least 90 minutes?
If at the 90min mark it still hasn't booted, pull logs and post them.
Thanks.
The logs contain references to apps that are present only in stock firmware.
That means the CM boot is actually not happening in a clean environment (the data wipe/factory reset in TWRP hasn't worked as it should?).
Please try to use OpenRecovery 2.09 instead of TWRP (as OR is the recovery I personally use and watch for possible bugs) to wipe the device and to install CM11 - http://forum.xda-developers.com/showthread.php?t=2211579&page=10
When installing CM in recovery, you will probably also want to install the gapps package - http://wiki.cyanogenmod.org/w/Google_Apps
Btw., CM11 expects the baseband (modem) and other partitions the be at the 4.1.2 stock level. Experiments with 4.0.4 are useless.
Please post the logs from CM11 boot.
You will need to enable the logger under CM11 by
Code:
su
setprop persist.log.aplogd.enable 1
in Terminal app or ADB shell, it's not enabled on CM11 by default.
Links are broken
Hi... My TRWP version is "openrecovery-twrp-2.7.0.1-asanti_c.img".
Something is not ok with this one. Sometimes this one format the cache, sometimes not.
I have to do it a lot of times and when i try to format data partition, this just reload the TWRP.
I want to install this one that you said, but those links in the post you sent are broken.
Can you please send me another one?
Skymidt said:
Hi... My TRWP version is "openrecovery-twrp-2.7.0.1-asanti_c.img".
Something is not ok with this one. Sometimes this one format the cache, sometimes not.
I have to do it a lot of times and when i try to format data partition, this just reload the TWRP.
I want to install this one that you said, but those links in the post you sent are broken.
Can you please send me another one?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=48551561&postcount=75
I'm on an older version of TWRP, and it has never failed me... that's a shame really. I'll try to update and see what's what. In the meantime, flash OpenRecovery I linked above ^^.
Skymidt said:
I have to do it a lot of times and when i try to format data partition, this just reload the TWRP.
Click to expand...
Click to collapse
TWRP 2.6.3.x should also work properly.
@arrrghhh, so you see it's not just me having the "wiping /data reboots the recovery" problem... I've already sold my PQ (might buy a new one in the future), but please do help let this problem be known to whoever's developing TWRP for us
Sent from Google Nexus 4 @ CM11
I can't believe it works
Unbelievable! :laugh:
This very simple solution worked for me.
My TRWP did not work right.
He said he had done successfully in cleaning the cache and manufactures, but did not.
I downloaded the link you guys sent me and it worked on the first try.
Not needed before installing CM 10.2. Already installed in the first CM 11, has worked with modem and everything. Now I can configure the GSM network my country and language of the country for my wife (PR-BR).
I want to thank the efforts of user @ AndyYan to respond, the attention given by the user @ Arrrghhh teaching me with patience, and the solution given by the user @ kabaldan. :victory:
You are awesome for this forum. Thanks for everything.
If you still want the log I get, but I think with everything working, you guys should already know the outcome.
Related
Since I can not post here:
[rom] Unofficial CyanogenMod 10 for many AllWinner A10 tablets
because no matter I'm in IT over 15 years I have no 10 posts here, which is quite uncool from XDA, I have to ask here:
I have an Elf, started to hack from with the latest factory firmware (updated with LiveSuit).
Then I decided to have Christian Troy's JellyBean.
I had trouble to get ClockWorkMod running, for example Novotools_v1.0.apk said not enough Internal storage. Finally I managed with
Terminal Emulator_1.0.41.apk and a10_recovery.zip 3 files with these two commands:
su install-recovery.sh
su reboot-recovery.sh
After rebooting to CWM I made a full wipe, than installed these in order:
cm10_a10_20120913.zip
gapps-jb-20120726-signed.zip
elf_compatibility_1.2.0.zip
After rebooting I see the animated CyanogenMod 10 logo, than I should choose language onscreen.
Though hardware keys work (power, volume), touch screen is not responding!
Actuall I dropped it as well after the last reboot, so now I'm not sure if this touch problem is related to CM10 or the drop.
Do you have any ideas what to do?
Flash back to stock to verify if your touchscreen is working. If yes, make sure you don't need to flash a different kernel for your device.
Also, try flashing like you did before, but without gapps. Possibly, your /system partition gets full, so the elf_compatibility thing fails.
-- Sent from my TouchPad using Communities
post-mortem said:
Flash back to stock to verify if your touchscreen is working. If yes, make sure you don't need to flash a different kernel for your device.
Also, try flashing like you did before, but without gapps. Possibly, your /system partition gets full, so the elf_compatibility thing fails.
-- Sent from my TouchPad using Communities
Click to expand...
Click to collapse
I am in the no touch screen boat too. I'm running an elf, but thought I'd try the aurora compatibility files too. Unfortunately, no dice. Flashing back to 4.0.4 stock firmware brings the touchscreen back. More installs of the cm10 for a10 don't help...
Anyone that successfully flashed Christian troy's cm10 build into Ainol Elf 1 care to say which rom they upgraded from? That would be awesome...
Same problem here with Aurora 1 with nightly CM10: no touch
Success!
jan99 said:
Same problem here with Aurora 1 with nightly CM10: no touch
Click to expand...
Click to collapse
OK, managed to trouble-crash my way through to a solution - hopefully it'll help you get to where you were going too...
The first thing I did was try to find the Feiyu ICS *LIVESUIT* image dated 0429. I also downloaded the compatibility patch for the elf - Aurora users won't need this, obviously.
I'm pretty sure this gives you a big enough /system partition, even though using the latest Ainol 4.0.4 firmware allegedly gave me enough.
Anyway, boot into CWM and do a Factory reset *twice*. I then did a cache format, dalvik wipe, battery stats wipe just for good luck. Fix permissions too - who knows why, I just do these things.
I installed the earliest preview release of the ChristianTroy cm10 for a10, installed the compatibility file for the elf (1.2...) , did a cache format, dalvik wipe, reboot... and... touch screen worked! I then installed the *final* cm10 from the ChristianTroy thread.
seems pretty nice, although trebuchet keeps crashing along with lots of my apps. Might use a different launcher.
perhaps cm9 is better? I'll give it a go...
TL;DR - install the livesuit image of the Feiyu ICS rom 0429. Then flash the other things you need. Worked for me, but, as ever, YMMV
post-mortem said:
Flash back to stock to verify if your touchscreen is working. If yes, make sure you don't need to flash a different kernel for your device.
Also, try flashing like you did before, but without gapps. Possibly, your /system partition gets full, so the elf_compatibility thing fails.
-- Sent from my TouchPad using Communities
Click to expand...
Click to collapse
Seems like HW problem, went back to Elvish 0.4, still no touchscreen...
DoubleDroz said:
OK, managed to trouble-crash my way through to a solution - hopefully it'll help you get to where you were going too...
The first thing I did was try to find the Feiyu ICS *LIVESUIT* image dated 0429. I also downloaded the compatibility patch for the elf - Aurora users won't need this, obviously.
I'm pretty sure this gives you a big enough /system partition, even though using the latest Ainol 4.0.4 firmware allegedly gave me enough.
Anyway, boot into CWM and do a Factory reset *twice*. I then did a cache format, dalvik wipe, battery stats wipe just for good luck. Fix permissions too - who knows why, I just do these things.
I installed the earliest preview release of the ChristianTroy cm10 for a10, installed the compatibility file for the elf (1.2...) , did a cache format, dalvik wipe, reboot... and... touch screen worked! I then installed the *final* cm10 from the ChristianTroy thread.
seems pretty nice, although trebuchet keeps crashing along with lots of my apps. Might use a different launcher.
perhaps cm9 is better? I'll give it a go...
TL;DR - install the livesuit image of the Feiyu ICS rom 0429. Then flash the other things you need. Worked for me, but, as ever, YMMV
Click to expand...
Click to collapse
I am facing same problem with Elf1, touch not working after installing CM10. Mouse works just fine. ^^Was this on ELF1 or Aurora?
DoubleDroz said:
OK, managed to trouble-crash my way through to a solution - hopefully it'll help you get to where you were going too...
The first thing I did was try to find the Feiyu ICS *LIVESUIT* image dated 0429. I also downloaded the compatibility patch for the elf - Aurora users won't need this, obviously.
I'm pretty sure this gives you a big enough /system partition, even though using the latest Ainol 4.0.4 firmware allegedly gave me enough.
Anyway, boot into CWM and do a Factory reset *twice*. I then did a cache format, dalvik wipe, battery stats wipe just for good luck. Fix permissions too - who knows why, I just do these things.
I installed the earliest preview release of the ChristianTroy cm10 for a10, installed the compatibility file for the elf (1.2...) , did a cache format, dalvik wipe, reboot... and... touch screen worked! I then installed the *final* cm10 from the ChristianTroy thread.
seems pretty nice, although trebuchet keeps crashing along with lots of my apps. Might use a different launcher.
perhaps cm9 is better? I'll give it a go...
TL;DR - install the livesuit image of the Feiyu ICS rom 0429. Then flash the other things you need. Worked for me, but, as ever, YMMV
Click to expand...
Click to collapse
Would appreciate if you could share those image files that you used...
nevermind
vipulpradhan said:
I am facing same problem with Elf1, touch not working after installing CM10. Mouse works just fine. ^^Was this on ELF1 or Aurora?
Click to expand...
Click to collapse
It was the Elf 1
---------- Post added at 02:47 AM ---------- Previous post was at 02:08 AM ----------
vipulpradhan said:
Would appreciate if you could share those image files that you used...
Click to expand...
Click to collapse
The files can be found at *double u, double u, double u dot* ainol-forum.de *slash* ainol-novo-7-aurora-1-i-2-ii *slash* roms-novo-7-aurora-1-i *slash* 302-rom-aurora-v1-feiyu-mod-0429 *slash*
Don't download from the 115 links - they're all locked up. The mirrors work, however.
If you have an Elf, get the Aurora v1 rom. Get the Livesuit Version, and install using... Livesuit.
If you have an Elf, you must also download the Elf Patch, which you install using CWM once you've installed 0429 through LiveSuit.
Give it a shot.
Sorry for the delay - been doing other things!
PS I can't directly put in a link because XDA won't let me - I don't have enough posts - but I've changed it so you can pretty obviously work out the url. Okie dokes?
Same problem? anyone found solution
hi,
i am also lost touch screen.
Has anyone found solution??
DoubleDroz said:
OK, managed to trouble-crash my way through to a solution - hopefully it'll help you get to where you were going too...
The first thing I did was try to find the Feiyu ICS *LIVESUIT* image dated 0429. I also downloaded the compatibility patch for the elf - Aurora users won't need this, obviously.
I'm pretty sure this gives you a big enough /system partition, even though using the latest Ainol 4.0.4 firmware allegedly gave me enough.
Anyway, boot into CWM and do a Factory reset *twice*. I then did a cache format, dalvik wipe, battery stats wipe just for good luck. Fix permissions too - who knows why, I just do these things.
I installed the earliest preview release of the ChristianTroy cm10 for a10, installed the compatibility file for the elf (1.2...) , did a cache format, dalvik wipe, reboot... and... touch screen worked! I then installed the *final* cm10 from the ChristianTroy thread.
seems pretty nice, although trebuchet keeps crashing along with lots of my apps. Might use a different launcher.
perhaps cm9 is better? I'll give it a go...
TL;DR - install the livesuit image of the Feiyu ICS rom 0429. Then flash the other things you need. Worked for me, but, as ever, YMMV
Click to expand...
Click to collapse
Please can you explain how you managed to boot it recovery? i am not able to reboot in recovery. it starts the new rom & stuck as no touch screen.
Q&A for [ROM][5.X][XT1028/XT1031] CyanogenMod 12.1 for Moto G [METICULUS]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][5.X][XT1028/XT1031] CyanogenMod 12.1 for Moto G [METICULUS]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
no calls or data
I have an xt1031 flashed to page plus. I have bootloader 41.19 from a failed lollipop update attempt. I flashed the 4/8 build and I can't make calls and do not have 3g. The network shows as 31000. What should I do?
I have been trying each of his builds and anything newer than 4/8 data hasnt worked I'm on boost if that makes any difference
Verizon?
Good morning,
I'm on an XT1028 still with service through Verizon Prepaid; my bootloader is unlocked and I'm on an optimized KK stock ROM at the moment. I've been following the development of Meticulus' CM12.1 through the primary thread and there has been a lot of discussion as to problem solving and issues on the XT1031 and various carriers but little mention as to the status of the latest weekly builds on the XT1028 still on Verizon in terms of functionality or hiccups from users. Does anyone have the latest versions running on their 1028? Are any of the data or service issues present when running it on Verizon?
Thanks.
Followup: Installed the latest 4/25 weekly on my XT1028 on Verizon Prepaid. Installed fine, got phone and SMS, but the network is identified as Boost Mobile and I have no mobile data. Is there a fix? Is a build.prop edit necessary for Verizon? Thanks.
Reboot then bootloop
Hi, I've been trying to get my installation of this ROM working for two days now, but keep running into an issue that I cannot seem to solve
My device is a 2013 Moto G XT1031 (Boost Mobile) with Bootloader version 41.05 and the latest CWM recovery.
The issue has been occurring on build 4/8, 4/25, and 5/2.
The exact steps I have been taking to install this ROM (for all builds) and then what happens:
Bootloader is unlocked
Going into recovery and wiping dalvik cache then factory reset (wipe)
Installing CM11 (latest snapshot) [on my first attempts only, not afterwards since it made no difference anymore]
Factory reset again (just to be certain)
Installing the zip for a build specified above
Installation always succeeds with no errors
Installing gapps-L-3-28-15 with success
Reboot into android
First boot always succeeds (and takes appropriate length of time)
Set up the phone (connect to wifi, google account, restore my apps [18 of them, just common popular ones, mostly Google actually], and apply a theme
Use it for a couple minutes (enable root and usb debug in Developer Settings, set my apps up, etc)
Restart two or three times without any hiccups
Suddenly, after a random reboot, the boot animation happens twice (instead of only once how it supposed to be)
Phone boots and shows "Android is starting..." and optimizes the apps (104 of them) one by one
Goes to "Starting apps..." and succeeds
The phone shows the lockscreen, but only for approximately 1-2 seconds
Phone reboots
CM boot animation runs twice, once for a long time then again for a shorter period of time
Phone goes through process described above (Android is starting, optimizes, then flashes lockscreen)
This just happens again and again and again
Steps I've taken to try and remedy the issue:
Run: "adb reboot" from computer while phone is optimizing apps
Hard reset the phone by holding the power button for 15 seconds
Run: "adb reboot bootloader" from computer when possible, then go into recovery and wipe both dalvik and normal cache
Swipe on the lockscreen as soon as I see it to see if I can get in (lockscreen does not respond though)
Go into recovery and shut the phone off, then start again
Let it loop for about 2 hours
I had also tried leaving the phone overnight looping, and when I woke, it was still looping, but after a eight or so more hours, I came back and found that it had booted and stayed on (and was working completely normally).
The phone was running stock 4.4.2 completely fine before this (with no reboot issues). I attempted installing the latest version of BlissPop, which exhibits a similar but still different issue (it would always boot into android [and not loop], but after a couple restarts, it showed an error about the System UI crashing that would pop up every time I dismissed it, and continued doing so after each restart after that). CM11 seems to be running well on the phone (but only in my very limited test while transitioning between ROMs and such).
I unfortunately cannot provide a log due to not being able to run any logging app during bootup, but hopefully I have provided enough details above to allow understanding of the issue and maybe bring suggestions on how to fix it. I can provide any more information needed on request. I really would like to get this phone back up and running (and especially on this ROM as I do love the work the creator has put into it).
Sorry for the very large wall of text :| Thank you in advance for any suggestions on how to proceed from here
tartilc said:
My device is a 2013 Moto G XT1031 (Boost Mobile) with Bootloader version 41.05 and the latest CWM recovery.
Click to expand...
Click to collapse
Having not experienced your issue I can't say for certain, but it may be possible you need to update the bootloader to at least 41.13, which is the 4.4.4 KitKat BL? I'd run it past @Meticulus and see if he might have some direction, there. Also, does the theme you apply have a different bootanimation, by any chance? There is a known issue/potential memory leak related to large boot animations on Lollipop that can cause failures at boot or bootloops.
a_gert said:
Having not experienced your issue I can't say for certain, but it may be possible you need to update the bootloader to at least 41.13, which is the 4.4.4 KitKat BL? I'd run it past @Meticulus and see if he might have some direction, there. Also, does the theme you apply have a different bootanimation, by any chance? There is a known issue/potential memory leak related to large boot animations on Lollipop that can cause failures at boot or bootloops.
Click to expand...
Click to collapse
Thank you for the advice I have downloaded a file with the name of falcon_boost_user_4.4.4_KXB21.14-L1.57_57_release-keys-cid9.xml.zip, unzipped it, then flashed according to the directions posted on how to restore the stock firmware. Everything during installation seemed to go smoothly, but at this point, I am stuck again. When I try to boot up, it just shows the splash screen ("Warning Bootloader Unlocked") and stays there indefinitely :| I have hard reset the phone and got into boootloader, which states that I am now on 41.13, but it just stays at that splash screen Should I boot into TWRP and try flashing an update.zip of the stock 4.4.4 Boost ROM? What else can I try?
EDIT: Flashing the stock update did not work, but I was able to install CM11 (so I'm am on bootloader 41.13 with CM11 currently)
EDIT TWO: Yes! I'm on bootloader 41.19 now and official CM12.1 nightly is booting!!
EDIT THREE: NOOOO It just started bootlooping again! CM animation twice, "Android is starting...", lockscreen, then cycle again. It happened after I changed my DPI from 320 to 280 (never restarted, just looped from then on).
I now have a logcat! I'm having trouble understanding what it is talking about, but I started logging as soon as the "Android is starting..." box changed status from "Optimizing apps x of x" to "Starting apps" and then stopped logging after a couple seconds of the boot animation. It is attached below (split into three parts).
EDIT: Attached what might be a better logcat reading (recording started right before lockscreen showed, I tried unlocking it, then stopped as soon as I saw the blue animation)
tartilc said:
Thank you for the advice I have downloaded a file with the name of falcon_boost_user_4.4.4_KXB21.14-L1.57_57_release-keys-cid9.xml.zip, unzipped it, then flashed according to the directions posted on how to restore the stock firmware. Everything during installation seemed to go smoothly, but at this point, I am stuck again. When I try to boot up, it just shows the splash screen ("Warning Bootloader Unlocked") and stays there indefinitely :| I have hard reset the phone and got into boootloader, which states that I am now on 41.13, but it just stays at that splash screen Should I boot into TWRP and try flashing an update.zip of the stock 4.4.4 Boost ROM? What else can I try?
EDIT: Flashing the stock update did not work, but I was able to install CM11 (so I'm am on bootloader 41.13 with CM11 currently)
EDIT TWO: Yes! I'm on bootloader 41.19 now and official CM12.1 nightly is booting!!
EDIT THREE: NOOOO It just started bootlooping again! CM animation twice, "Android is starting...", lockscreen, then cycle again. It happened after I changed my DPI from 320 to 280 (never restarted, just looped from then on).
Click to expand...
Click to collapse
Whoa, that's a lot of jumps! Be careful with the bootloader, as once you're on the Lollipop BL (and it appears you've already made that jump), you're kind of locked into LP ROMs from this point out. The point you were failing on the 4.4.4 stock would probably have been a good time to go in and manually restore things via fastboot just to make sure all your partitions were straight. What did you use to update your bootloader to 41.19? And have you tried a ROM specifically designated for the CDMA-only XT1031/Boost? I've only used the Meticulus and the unofficial Linaro CM12.1 buld by Cody on my XT1028 specifically because I know they're CDMA compatible, so I'm not sure where the official CM12.1 sits on that right now.
I know there exists an actual legitimate stock 5.0.2 Boost ROM and it's possible that may be able to be restored manually as a last resort, so don't move too hastily.
XPOSED on Meticulous Rom?
Is there any way to get XPOSED working? I really want gravity box for LL.
Awesome. I was going to download this from your site today but it is showing an error with connecting to its database. None of the computers i have access to can get on your site.
no wifi no cellular network
and after i flashed cynogenmod 12.0 in my moto g 2014, there is no wifi nor network :'( what am i suppose to do now?
Ui crash
Is there anything special i need to do to flash this update? i'm running on the 408 build and every time i try ti go the next version there is an issue. Either data stops working or i get a system Ui crash like on the 530 build. I would love to get this issue fixed with the 606 build. Besides that, great job.
a_gert said:
Whoa, that's a lot of jumps! Be careful with the bootloader, as once you're on the Lollipop BL (and it appears you've already made that jump), you're kind of locked into LP ROMs from this point out. The point you were failing on the 4.4.4 stock would probably have been a good time to go in and manually restore things via fastboot just to make sure all your partitions were straight. What did you use to update your bootloader to 41.19? And have you tried a ROM specifically designated for the CDMA-only XT1031/Boost? I've only used the Meticulus and the unofficial Linaro CM12.1 buld by Cody on my XT1028 specifically because I know they're CDMA compatible, so I'm not sure where the official CM12.1 sits on that right now.
I know there exists an actual legitimate stock 5.0.2 Boost ROM and it's possible that may be able to be restored manually as a last resort, so don't move too hastily.
Click to expand...
Click to collapse
Yeah that is a lot of jumps I'd be hella nervous myself lol
K well guys today is your day , as a_gert stated there is a boost 5.02 , and it does work fine on any cdma xt1031 so first flash that
-depending on signal you may wish to update your modem also there is only 4.4 modem for boost public
Buuuutttt nvm all that for now
The problem the ONLY problem I have had when bootlooping was that it was not prepped correctly and my phone came with 41.19 and came unlocked-
1.) Make sure you are on c/O SuperR-Developer -- PhilZ-Touch-6.59.0_LPK .img OR twrp * twrp-2.8.6.0.1-falcon_STOCK.img
**Notice For Even PhilZ I only Named the -IMG- Version which means flash it with adb properly please
***if ever after you flash it via recovery it will show partition mismatch which apparently is no problem just that the custom recovery does not match the factory one is all.. ..
1.) Download PhilZ-Touch-6.59.0-LPK.img to PC
2.) Reboot to bootloader
3.) Plug phone into PC
4.) Open terminal in directory where the img is located
5.) Issue the following command:
Code:
fastboot flash recovery twrp-2.8.6.0.1-falcon_STOCK.img
2.) Do a format of System w/EXT4 AND REBOOT INTO RECOVERY
3.) Format dalvik/art + Cache + Data w/EXT4 & REBOOT INTO RECOVERY
4.) Format Data PLUS data/media with f2fs then Do the 'factory wipe' then manually format data/media with f2fs again please ..
- SIDELOAD THE ATTACHED STOCK LOLLIPOP NO GAPPS GIVE IT TEN MINUTES REBOOT FEW TIMES/ POWER DOWN ONCE & REBOOT AGAIN
5.) Reboot into recovery and flash the first zip I have attached (I_nomodem is just IF you find your 4.4 radio baseband worked better and want to format it for LP again in the future WITHOUT LP radio included)
****EDIT - SEE VERY BOTTOM OF POST CENTERED AREA LOL
6.) Power off & reboot into recovery manually
7.) Flash your Rom (OR STOCK LOLLIPOP DEBLOATED AGAIN) + Kernel(if any custom one) + Gapps -wait 5-15 minutes for initial boot
* I recommend AeroKernel for the included stock lollipop 5.0 debloated if not the stock kernel or after flashing and few reboots to settle ,just follow instructions from that thread if any are needed..
Please anyone with any moto g don't think updating your bootloader is needed or even really safe whatsoever it is THE main reason moto phones get bricked or messed up otherwise it is not necessary or any kind of improvement yes once you are on an LP one leave it be..
Other flashing yeah okay, bootloader no if so proceed with utmost caution.
After this your modem will be updated with the cdma LolliPop one, if you have any signal issues or what not go to the stock modems section for your specific phone and flash the one for your specific carrier and/or find the "update RIL" flash thingie on here in moto G section and follow instructions but the boost modems work on all cdma variants of Moto G..
For whatever reason I could not upload files to xda I tried five times it kept dying so here there are on googldrive :good:
**Do not Click individual Item Use the Download Arrow At the Very Top of Page to DL the zip properly plz
1.) Falcon LolliPop Part Updater + Modem
2.) Falcon LolliPops Part Updater (No Modem)
_____________________________________________________________________________________________________________________________
--EDIT #2-- LolliPop 5.0 Falcon XT1031 debloated
SIDENOTE: IF YOU FORMAT DATA/MEDIA & DO NOT KNOW HOW TO SIDELOAD THE ABOVE STOCK DEBLOATED ZIP I'M PRETTY SURE YOU'RE NOT GONNA LIVE TO TELL BOUT IT
BE PREPARED TO SIDELOAD - REBOOT IMMEDIATELY AFTER SIDELOAD THE ZIP ROM IS COMPLETE NOT INTO RECOVERY NOT ANYWHERE ELSE SYSTEM REBOOT
-And wait 5-10 Minutes For First Boot - You Only Need to Do this for the first LP rom loadin after that normal flashing do NOT format data/media anymore after this initial setup
--You can try to just use the script, but it did not work for me after many tries the above was the real solution and has been perfect since
2,3,4,5,6,7
·Install flashable (Boost Mobile/CDMA XT1031 only):
·Download falcon_PhilZ-Touch-6.59.0_LPK.zip to phone
·Reboot into current custom recovery
·Flash zip
·Enjoy!
Use the script again to prepare you partition properly anytime you are about to flash a new rom clean after factory wipe/ format is done..
As I said before data/media is never necessary again after this and MAY not be this time but it is the only thing that kept me out of bootloops ,and if you do it yeah it will force you to sideload your rom it erases all leftovers and your rom zips off the internal card and formats them for fresh start The script does not format /media guys k no worries
------TWRP 2.8.6..1 does not seem to restore properly- -system write only thing .. PhilZ-Touch is fine as is twrp-2.8.6..0 also
Nice, got 41.19 BL!
I tested this and works fine, now i have my shiny new moto g running AICP. Thanks @shoobiedoobiiwhompwop!
rammsteinaus said:
I tested this and works fine, now i have my shiny new moto g running AICP. Thanks @shoobiedoobiiwhompwop!
Click to expand...
Click to collapse
K welcome
Arrite guys for a little clearer step by step see here please apologies carrying on and on I have been gone quite some time here http://forum.xda-developers.com/mot...-moto-g-xt1031-lollipop-t3132974#post61346260
It actually Runs really nice, really REALLY nice once the system app package I am adding shortly was used and tweaked out ..
Is it safe to flash cyanogenmod onto the verizon moto G - 1028 4.3 plus
Hello community ,
I had serious problems flashing cyanogenmod onto a galaxy S3 that was running stock 4.3 , verizon bricked my S3 , and said that the software was not authorized by Verizon. Does this problem exist across the board for any verizon phone running 4.3 or higher ?? If so ... then anything to do with flashing cyanogenmod onto a verizon phone should have warnings in BIG RED LETTERS ... because you cannot even buy a new phone with 4.2 on it anymore.
Issues flashing cm12.1 on XT1031 Please Help
Tried flashing the second to last release on 2 of my moto g xt1031's and I keep getting diff issues. This is what I did:
I had complete stock 4.4.4
unlocked bootloaders,
flashed latest TWRP,
Did a factory wipe
Flashed CM12.1
Flashed Gapps
Rebooted
Stuck in boot loop--> waited over 30mins and rebooted a few times. No luck.
I heard to try flashing CM11 first, then flashing 12.1 so I did this:
Back to TWRP -->factory wipe
Flash cm11
reboot to cm11
reboot to TWRP -->factory wipe
Flash CM12.1
Now I can get past the boot logo and begin setup, however, it will randomly reboot to the boot logo and then back to setup after a minute or so- erasing anything I've already input. Sometimes I could make it through the setup to the desktop, but then it would do the same thing. Had this same exact issue on both of my xt1031s with the same process used for both.
After this I tried doing a factory wipe and then also wiping /data and /system in the advanced wipe options and then flashing cm12.1 and still had the same issue of the rebooting. At some point I must have done somthing, but I started trying to just flash cm12.1 several times over to see if it would stick and I noticed when I did the factory wipe I was getting a parsing error so I tried doing a full data format, and fix data filesystem. I'm not sure what format it was supposed to be so I did a ex4. THat stopped the parsing error, but still having the same issues.. any help would be appreciated.
Moto G CDMA issues
citizen3rased said:
Tried flashing the second to last release on 2 of my moto g xt1031's and I keep getting diff issues. This is what I did:
I had complete stock 4.4.4
unlocked bootloaders,
flashed latest TWRP,
Did a factory wipe
Flashed CM12.1
Flashed Gapps
Rebooted
Stuck in boot loop--> waited over 30mins and rebooted a few times. No luck.
I heard to try flashing CM11 first, then flashing 12.1 so I did this:
Back to TWRP -->factory wipe
Flash cm11
reboot to cm11
reboot to TWRP -->factory wipe
Flash CM12.1
Now I can get past the boot logo and begin setup, however, it will randomly reboot to the boot logo and then back to setup after a minute or so- erasing anything I've already input. Sometimes I could make it through the setup to the desktop, but then it would do the same thing. Had this same exact issue on both of my xt1031s with the same process used for both.
After this I tried doing a factory wipe and then also wiping /data and /system in the advanced wipe options and then flashing cm12.1 and still had the same issue of the rebooting. At some point I must have done somthing, but I started trying to just flash cm12.1 several times over to see if it would stick and I noticed when I did the factory wipe I was getting a parsing error so I tried doing a full data format, and fix data filesystem. I'm not sure what format it was supposed to be so I did a ex4. THat stopped the parsing error, but still having the same issues.. any help would be appreciated.
Click to expand...
Click to collapse
Hello Citizen 3 , You are farther along than me. I have only successfully flashed cyanogenmod once , and that was on an S3 so it was straightforward. I still have not unlocked my bootloader. I have not been able to copy and paste the long strings of characters from motorola , inside command prompt. It would be so nice if Meticulus or one of the other developers could get this to be an official release. The Moto G , and a few other inexpensive phones ( LG realm , Kyocera Hydro latest version ) would work like greased lightning , if they were running CM12. Any help that you could offer with pasting the strings of unlock code would be so appreciated.
Q&A for [ROM][5.1.1] Candy 5 - Skyrocket
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][5.1.1] Candy 5 - Skyrocket. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
hello
I changed my i727 to 5 candy lollipop , everything works except that appeals nobody hears me and I hear nothing
Here are the notes from phone
baseband i727ucmc1
Version 3.0.101 CyanogenMod - g0c7bddd
uMTS network
state service
current service
Homelessness: Homelessness without
state of the mobile network : offline
thank you for your answer
i have installed rom from sd card after wipe data and partitions
___________________________________________________________
new:
that's it, after two reboot it works; but I'm waiting still the problem will return, I install once "kitkat bluelighting 4.4.4" and "Slim-skyrocket - 4.4.4.build.6 - OFFICIAL-5252" "
everything worked very well
Thank you
Anaya Boom said:
hello
I changed my i727 to 5 candy lollipop , everything works except that appeals nobody hears me and I hear nothing
Here are the notes from phone
baseband i727ucmc1
Version 3.0.101 CyanogenMod - g0c7bddd
uMTS network
state service
current service
Homelessness: Homelessness without
state of the mobile network : offline
thank you for your answer
i have installed rom from sd card after wipe data and partitions
___________________________________________________________
new:
that's it, after two reboot it works; but I'm waiting still the problem will return, I install once "kitkat bluelighting 4.4.4" and "Slim-skyrocket - 4.4.4.build.6 - OFFICIAL-5252" "
everything worked very well
Thank you
Click to expand...
Click to collapse
This is a problem with most 5.1 roms. Mostly after using another audio app like hangouts phone,whatsapp phone,music players and video players. Driver is not released back too phone.Reboot is needed . On a good note, Paranoid Android 5.1.1 has just come out with an update and an audio patch that fixed mine. Hope this helps.
I don't get any signal
My phone after updating it to candy 5(5.1 Lollipop) I can't get any signal?
Please Help!
New to this
This is the best rom I have installed ever since fixing my bricked Skyrocket a couple weeks ago.
Latest Version 5/15:
After installing the latest update the data drops far less frequently... however it is still a good five times every twenty minutes or when I send two or more text messages. I tried rebooting, messing with wifi/airplane mode, removing excess APN's, and using Signal Boosters which are junk. Folders seem to be a bit different and overall rom is a bit more laggy compared to previous version. My recents menu did not work, holding the home button with no response, fixed by turning on OmniSwitch.
Installing SlipLP fixed the data, so I am confident you will figure it out for Candy! If only I digged the look of SlimLP.
Will report back next update, still learning how to Logcat... I will post if I figure it out tonight.
I am not getting any charging or heat issues like the poster above. I did not change to noop prior to writing this.
Found a PERMANENT signal fix!
Apparently this has something to do with the radio being flashed and 5.x.
Here is how you fix it, I have not had one drop in signal since my previous post!
(For AT&T, T-Mobile, possibly others)
1. Download the [UCMC1] I717 AT&T Radio
http://d-h.st/PKI
- official thread: http://forum.xda-developers.com/showthread.php?t=2228292
2. Either Clean flash or Recover from a backup of Candy 5.x
3. Install the AT&T Radio
Signal drop is fixed, select your APN and enjoy!
I suggest this for those who are using AT&T Servers, T-Mobile, or etc. If not visit here and find your carrier radio... http://forum.xda-developers.com/showthread.php?t=1785999
I hope this helps everybody! :good::fingers-crossed:
I am not a professional, I have been flashing custom for a couple years here and there! This is working on my device, I now have ZERO signal drops and perfect signal, please allow OP to further test.
requiredhq said:
Apparently this has something to do with the radio being flashed and 5.x.
Here is how you fix it, I have not had one drop in signal since my previous post!
(For AT&T, T-Mobile, possibly others)
1. Download the [UCMC1] I717 AT&T Radio
http://d-h.st/PKI
- official thread: http://forum.xda-developers.com/showthread.php?t=2228292
2. Either Clean flash or Recover from a backup of Candy 5.x
3. Install the AT&T Radio
Signal drop is fixed, select your APN and enjoy!
I suggest this for those who are using AT&T Servers, T-Mobile, or etc. If not visit here and find your carrier radio... http://forum.xda-developers.com/showthread.php?t=1785999
I hope this helps everybody! :good::fingers-crossed:
I am not a professional, I have been flashing custom for a couple years here and there! This is working on my device, I now have ZERO signal drops and perfect signal, please allow OP to further test.
Click to expand...
Click to collapse
Thanks, yes the UCMC1 radio or newer is needed for this. It is one of the last versions available for the Skyrocket. My Slim threads have this but I didn't see that mentioned here, so I have updated the OP.
Cheers!
Preinstalled App
Does this ROM has Apollo music player installed?
Hunter661 said:
Does this ROM has Apollo music player installed?
Click to expand...
Click to collapse
It has CM's Eleven music player. You can install whatever you want, Google Music, XenoAmp, etc.
GAPPS
Everything is working on my Skyrocket SGH-I727R but when I want to install gapps from my recovery it says it successful but I can't find google play when I installed the zip. Do I need to use a different GAPPS file?
Candy 5 v2.5.3 onto skyrocket I727 as well as I727R)
tried to update from v2.5.1 .Got Google play bug .
Then did a full wipe and installed on both units with slim Gapps .No more chance .same error .When back to prvious version from restore .
Should we be able to update from the previous 5.1.1 buid v2.5.1 ?
Thanks
Twisterboy669 said:
Everything is working on my Skyrocket SGH-I727R but when I want to install gapps from my recovery it says it successful but I can't find google play when I installed the zip. Do I need to use a different GAPPS file?
Click to expand...
Click to collapse
Michel177 said:
tried to update from v2.5.1 .Got Google play bug .
Then did a full wipe and installed on both units with slim Gapps .No more chance .same error .When back to prvious version from restore .
Should we be able to update from the previous 5.1.1 buid v2.5.1 ?
Thanks
Click to expand...
Click to collapse
Make sure you are using an up-to-date version of GApps. Recommended is Slim's Zero GApps (~60MB), a link to which you can find in the OP.
Google Cards
The google now widget I can't find under the widgets tab is their anyway to retrieve it?
Minor Question
How would you update the 2.53 version to this one?
Twisterboy669 said:
The google now widget I can't find under the widgets tab is their anyway to retrieve it?
Click to expand...
Click to collapse
When you flash the ROM, either the GApps package you flash needs Google Now (might be Google Search, not sure), or you need to install it from the Play Store separately. Voice input on the AOSP/Google keyboards may be missing as well until you do.
I partitioned my Skyrocket to have a 6GB Data partition so the tiny GApps is fine and I can install pretty much all I want for apps. It's quite nice.
Twisterboy669 said:
How would you update the 2.53 version to this one?
Click to expand...
Click to collapse
Wipe Dalvik and Cache in recovery
Make a nandroid backup
Flash the ROM
Flash either Slim Zero GApps or a very small base GApps package
Reboot
Have fun!
Flashing Potential Issue
I am currently Flashing the ROM using TWRP and everything seems good it's just that its stock on "Patching system unconditionally" It's been on that step for about ten minutes. I did the Cache and Dalvick Cache wipes. So I Don't know what I did wrong.
Twisterboy669 said:
I am currently Flashing the ROM using TWRP and everything seems good it's just that its stock on "Patching system unconditionally" It's been on that step for about ten minutes. I did the Cache and Dalvick Cache wipes. So I Don't know what I did wrong.
Click to expand...
Click to collapse
Then it sounds like there were core changes which may require a full wipe (/data or a factory reset).
I normally clean flash to test, so unless I've made a change that I know requires a full wipe, or coming from another version (5.0 vs. 5.1, etc.) I would suggest to try dirty first and see. If you get stuck, as you have, then I'd go clean.
Sorry for any inconvenience...
NoSpamDan said:
Then it sounds like there were core changes which may require a full wipe (/data or a factory reset).
I normally clean flash to test, so unless I've made a change that I know requires a full wipe, or coming from another version (5.0 vs. 5.1, etc.) I would suggest to try dirty first and see. If you get stuck, as you have, then I'd go clean.
Sorry for any inconvenience...
Click to expand...
Click to collapse
When I down graded bak to 2.5.3 It flashed perfectly. So do I just wait for the next update or is their a solution because none of the methods you mentioned to me are working. I backed up my data and did a full factory reset.
Twisterboy669 said:
When I down graded bak to 2.5.3 It flashed perfectly. So do I just wait for the next update or is their a solution because none of the methods you mentioned to me are working. I backed up my data and did a full factory reset.
Click to expand...
Click to collapse
Have you wiped /system in the process?
Have you formatted your device with ODIN using a PIT file, or have you used any virtual partitioning?
Post your recovery log. You can export it from TWRP.
NoSpamDan said:
Have you wiped /system in the process?
Have you formatted your device with ODIN using a PIT file, or have you used any virtual partitioning?
Post your recovery log. You can export it from TWRP.
Click to expand...
Click to collapse
Nvm, Sorry I forgot about the dirty flashing and it worked. Thank you
CyanogenMod and D2VZW: Marshmallow Love!
To Make this easy, I am going to copy a bit of the common sense information Master Cylinder put up for the release of Lollipop, same basics apply here!
Huge thanks to Invisiblek for making these builds for us!
Thanks to Master Cylinder for all the super useful information!
De-unified Marshmallow builds for the Galaxy S3 line. This is for the Verizon variant (SCH-I535) only
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0 which is designed to increase performance and reliability over stock Android for your device.
Notes:
Please Use Firmware: VRBMF1
and
Modem/Baseband Version: NE1 (Also, see "Notes - Possible Bugs" section below)
(EDIT: The following statement might not be true. It happened to one user. Unsure about circumstances...)If you have recently downgraded firmware from 4.3 to 4.1.2, DO NOT flash the MF1 firmware. You'll brick your device!
If you know you never took the 4.3 OTA, then you can flash the firmware and modem to your hearts content.
CWM Recovery addicts: Please seriously consider giving up CWM and come on board with what works for sure with 5.1.x and up, TWRP. Problems have been coming up with CWM users so if you have one, that's were to start. Hopefully there's a 12-step program somewhere for y'all
Google apps addon:
Open GApps opengapps.org They have many options for you to choose from based on your needs. Updated daily.
>>>WARNING!!<<< The first time one installs Open GApps, you have to do it with a ROM update (or reinstall current ROM) AND manually wipe the system partition first. Then install the ROM and the GApps normally, then wipe Dalvik and Cache. After that, you can flash them anytime. (More info on Website.) ALSO, for now, don't install Webview as it might not work. There is an "Android System Webview" in the Play Store that will work.
I personally don't use GApps on my Daily Driver, I have a second S3 on Wi-Fi only that I put GApps on, and I use it to basically keep all my apk files up to date. When they get updated, I move the updated apk to my main phone!
I went to opengapps.org, went to Platform: ARM, then to Android: 6.0, and then to Variant: pico. Invisiblek made sure he warned me to do a clean install of the ROM, then Immediately flash the GApps package, then Wipe Dalvik and Cache, then boot. He said NOT to try to install ROM, then add GApps later otherwise bad things can happen! Obviously pick the flavor of GApps that suits your needs!
This page will be a work in progress, so please don't yell if something is missing. I just got the OK to share this with others and wanted to get it out there for you to enjoy. I have been playing with it for the last 24 hours and it is ROCK SOLID in my opinion. I haven't found any issues yet! Daily Driver for me for certain. If you have issues, please post them for discussion below!
Firmware and Modem thanks to Invisiblek
Download - MF1 firmware with NE1 modem Combo: http://www.invisiblek.org/firmware/d2/d2vzw_MF1_firmware_NE1_modem.zip (md5sum: 7a49bb13c1160f4d4a89488127684b5b)
And without further delay, the link you all want! : http://www.invisiblek.org/roms/cm-13.0/d2vzw/
BUGS:
Need to possibly load a different File Explorer to access SD Card (DoctorImpossible)
Access to camera is not functioning correctly (DoctorImpossible) *EDIT 11-23 build camera works, camcorder fix coming next build!
Outgoing text messages show "not sent", but actually send fine. (Stealth111)
Incoming phone calls do not show caller information (Stealth111)
**When you get your ROM installed and up and running, please be kind and put a small post with information about your install so we can get as much info gathered as possible. (ROM build you installed, Recovery type/version, Clean install, or Dirty (and if dirty, over what version did you flash), what GApps package you installed(exact one please) as well as when you installed it (if on same initial install as ROM, or differently). And lastly maybe the firmware/modem combo you are running. Thanks!
***IMPORTANT INFORMATION*** If you are going to flash to cm-13.0-20151121-UNOFFICIAL-d2vzw or later build, there have been some database changes. InvisibleK has provided a flashable zip file to accommodate nuking your old telephony and settings databases. Nandroid or backup files as needed if you want, as I seem to remember doing this with CM before, and clearing the database wiped texts and call logs I believe. This only needs to be done 1 time, the first time you flash any build from 11-21 on. After you have done this once, you are good to go moving forward, you will be upgraded to the new databases. If you do not flash the "Nuke_It" zip file, you will get phone FC's and a "No SIM Card" error message. So whether upgrading, dirty flashing or whatever, reboot into recovery, flash the ROM, and BEFORE you boot, flash the following zip!
Nuke IT Database Wiper
Profit!
Enjoy!
Stealth111
For Future Use
First
For Future Use
Second
Stealth111 said:
Second
Click to expand...
Click to collapse
First!! To download from here ... I see you've got an OpenGApps link, but it says a patch has to be used. I think I saw it mentioned on a thread somewhere (when I was tracking you to see where you got the build, which didn't lead me anywhere, but then I remembered our old friend invisiblek!)
And thanks a million for starting this thread!!!:good::good::good:
Master Cylinder said:
First!! To download from here ... I see you've got an OpenGApps link, but it says a patch has to be used. I think I saw it mentioned on a thread somewhere (when I was tracking you to see where you got the build, which didn't lead me anywhere, but then I remembered our old friend invisiblek!)
And thanks a million for starting this thread!!!:good::good::good:
Click to expand...
Click to collapse
I personally don't use GApps on my Daily driver, I have a second S3 on Wi-Fi only that I put GApps on, and I use it to basically keep all my apk files up to date. When they get updated, I move the updated apk to my main phone!
I went to opengapps.org, went to Platform: ARM, then to Android: 6.0, and then to Variant: pico. Invisiblek made sure he warned me to do a clean install of the ROM, then Immediately flash the GApps package, then Wipe Caches, then boot. He said NOT to try to install ROM, then add GApps later otherwise bad things can happen! Obviously pick the flavor of GApps that suits your needs! I'll add this bit up-top as well! I don't know anything about a patch though..
Stealth111
Stealth111 said:
I personally don't use GApps on my Daily driver, I have a second S3 on Wi-Fi only that I put GApps on, and I use it to basically keep all my apk files up to date. When they get updated, I move the updated apk to my main phone!
I went to opengapps.org, went to Platform: ARM, then to Android: 6.0, and then to Variant: pico. Invisiblek made sure he warned me to do a clean install of the ROM, then Immediately flash the GApps package, then Wipe Caches, then boot. He said NOT to try to install ROM, then add GApps later otherwise bad things can happen! Obviously pick the flavor of GApps that suits your needs! I'll add this bit up-top as well! I don't know anything about a patch though..
Stealth111
Click to expand...
Click to collapse
Thanks. I also misread the notation at OpenGApps, which said that need a "ROM" with the patch to allow Google services permissions. Also, there are some posts I've found about fixing permissions after boot then reinstalling GApps, but I won't post that here in case it misleads. I'll be the guinea pig as I've dloaded and backed up and ready to jump out the window!
Stealth111 said:
CyanogenMod and D2VZW: Marshmallow Love!
Firmware and Modem thanks to Invisiblek
Download - MF1 firmware with NE1 modem Combo: http://www.invisiblek.org/firmware/d..._NE1_modem.zip (md5sum: 7a49bb13c1160f4d4a89488127684b5b)
And without further delay, the link you all want! : http://www.invisiblek.org/roms/cm-13.0/d2vzw/
Enjoy!
Stealth111
Click to expand...
Click to collapse
Hello and thank you for providing us, S3 users, with the chance to try the long awaited Marshmallow ROM.
I downloaded the ROM a minute ago, but unable to download the MF1 firmware and NE1 modem, via link. I keep getting:
Error 404: Server be all like
Am I doing something wrong? If not... What next?
I just finished booting it. It seems pretty nice, and I only noticed a few things. The boot time was around half an hour as usual with lollipop. I did notice that there wasn't any camera app preloaded and I couldn't access my sd card through the file explorer (I chose not to format my sd card as internal and I gave the file explorer root access).
Ghost Protocol said:
Hello and thank you for providing us, S3 users, with the chance to try the long awaited Marshmallow ROM.
I downloaded the ROM a minute ago, but unable to download the MF1 firmware and NE1 modem, via link. I keep getting:
Error 404: Server be all like
Am I doing something wrong? If not... What next?
Click to expand...
Click to collapse
Yes, @Stealth111 you've copied the text from the CM12 OP but that won't work for links EDIT: that are truncated in a post. You have to manually copy the link, ex: right click on the link (if you're using a computer,) copy link location of whatever, and insert it manually.
Here is the working link: http://www.invisiblek.org/firmware/d2/d2vzw_MF1_firmware_NE1_modem.zip
On another note: I couldn't get my install to function past the first couple of screen in setup. com.android.phone fc avalanche stops all progress. Wiped and installed 3 times with no success. Running NE1 modem (after flashing and booting with ML1 the first time.)
Doctorimpossible said:
It seems pretty nice, and I only noticed a few things. . I did notice that there wasn't any camera app preloaded and I couldn't access my sd card through the file explorer (I chose not to format my sd card as internal and I gave the file explorer root access).
Click to expand...
Click to collapse
I also can't access the camera even after installing a new camera app. A new file explorer took care of my sd card issues however.
@ Master Cylinder, thanks for the heads up on the link, I have fixed it in the OP. For ****s and giggles, trying wiping and installing just the ROM, and then wipe Dalvic and Cache and see how it goes. Maybe a GApps issue. Also, goes without saying, make sure the MD5 from the download matches to verify you got a good DL..
@Doctorimpossible, glad you were able to sort out the access issue. I install ES File Explorer right away, so I didn't notice the issue. Good catch. These are the types of thing we need to sort out as quickly as possible to get this thing rolling! I will say that my initial boot only took about 5 minutes, but again, I did not load ANY GApps.
Master Cylinder said:
Yes, @Stealth111 you've copied the text from the CM12 OP but that won't work for links EDIT: that are truncated in a post. You have to manually copy the link, ex: right click on the link (if you're using a computer,) copy link location of whatever, and insert it manually.
Here is the working link: http://www.invisiblek.org/firmware/d2/d2vzw_MF1_firmware_NE1_modem.zip
On another note: I couldn't get my install to function past the first couple of screen in setup. com.android.phone fc avalanche stops all progress. Wiped and installed 3 times with no success. Running NE1 modem (after flashing and booting with ML1 the first time.)
Click to expand...
Click to collapse
So is this a hit or miss when flashing or not?
Ghost Protocol said:
So is this a hit or miss when flashing or not?
Click to expand...
Click to collapse
I have installed it on 4 devices myself with no issues. They were all with TWRP 2.8.7.0, clean installs, data wiped, ROM only install, and wiped caches before first boot. DoctorImpossible also has installed it and is up and running. I don't know what GApps he is running (if any). I will add to the OP asking people to put what they did/used for successful installs.
Stealth111 said:
@ Master Cylinder, thanks for the heads up on the link, I have fixed it in the OP. For ****s and giggles, trying wiping and installing just the ROM, and then wipe Dalvic and Cache and see how it goes. Maybe a GApps issue. Also, goes without saying, make sure the MD5 from the download matches to verify you got a good DL..
@Doctorimpossible, glad you were able to sort out the access issue. I install ES File Explorer right away, so I didn't notice the issue. Good catch. These are the types of thing we need to sort out as quickly as possible to get this thing rolling! I will say that my initial boot only took about 5 minutes, but again, I did not load ANY GApps.
Click to expand...
Click to collapse
I tried that just now for the 4th crapout, and there's no MD5 that I can see, but I'm gonna dload the ROM again to my lap and push it over and try again.
Ghost Protocol said:
So is this a hit or miss when flashing or not?
Click to expand...
Click to collapse
Of course! It's the first unofficial build for us.
Stealth111 said:
I have installed it on 4 devices myself with no issues. They were all with TWRP 2.8.7.0, clean installs, data wiped, ROM only install, and wiped caches before first boot. DoctorImpossible also has installed it and is up and running. I don't know what GApps he is running (if any). I will add to the OP asking people to put what they did/used for successful installs.
Click to expand...
Click to collapse
I used the GApps linked in the description with the stock option and flashed using TWRP 2.8.7.0. I rebooted from 5.1.1, factory reset, manually wiped system, flashed the rom, then flashed GApps, wiped the cache, rebooted, rebooted again and flashed xposed (which works by the way!)
Master Cylinder said:
I tried that just now for the 4th crapout, and there's no MD5 that I can see, but I'm gonna dload the ROM again to my lap and push it over and try again.
Of course! It's the first unofficial build for us.
Click to expand...
Click to collapse
Here is the MD5 from my file if it helps!
192BD2F6A83BCA791E0AFE9570134058
Doctorimpossible said:
I used the GApps linked in the description with the stock option and flashed using TWRP 2.8.7.0. I rebooted from 5.1.1, factory reset, manually wiped system, flashed the rom, then flashed GApps, wiped the cache, rebooted, rebooted again and flashed xposed (which works by the way!)
Click to expand...
Click to collapse
Yuppers! Exposed for Android 6
Thanks for the report!
Fingers crossed for Master Cylinder!!
Stealth111 said:
If you have recently downgraded firmware from 4.3 to 4.1.2, DO NOT flash the MF1 firmware. You'll brick your device!
Click to expand...
Click to collapse
how do i know if i have the right one ? it was a while since i rooted and flashed my phone.
thanks.
Sent from my SCH-I535
Jaws4God said:
how do i know if i have the right one ? it was a while since i rooted and flashed my phone.
thanks.
Sent from my SCH-I535
Click to expand...
Click to collapse
There's no way to tell, but you're probably okay. How did you flash your ROM? This is to warn people that the recent post for a procedure to "Downgrade" from their locked bootloader 4.3 OTA that all of us avoided because we were already rooted, etc. This new method has only been around since this summer, so if you have been rooted in the years category, you're probably okay.
Besides, it may even not be a problem if one had done that new method.
Master Cylinder said:
There's no way to tell, but you're probably okay. How did you flash your ROM? This is to warn people that the recent post for a procedure to "Downgrade" from their locked bootloader 4.3 OTA that all of us avoided because we were already rooted, etc. This new method has only been around since this summer, so if you have been rooted in the years category, you're probably okay.
Besides, it may even not be a problem if one had done that new method.
Click to expand...
Click to collapse
all i rememeber was downgrading from h2 to h1 to get root access.. then flashed CM12.1 on top of that ..
Sent from my SCH-I535
So I decide to upgrade a a couple of weeks after OTA update to CM13 arrived. Turns out it was a massive mistake, especially since no backup, no ADB enabled, no root and nothing custom. This is the best I have so far: https://jira.cyanogenmod.org/browse/BACON-4808 (summary: System UI and com.android.phone both crash on startup). Sad thing is I can see phone working just fine behind the crashed UI (getting mail, notifications etc.) I know my data is in there but cannot get to it.
Anyway, customer support is responsive but I am not sure they will let me keep my data.
I am pretty much starting from scratch regarding flashing, and the first few hours was deciphering abbreviations and other bull. Other than that I am decently proficient with the tech stuff.
Would be grateful if you guys can help point me in the right direction. The info I currently have:
* I want to keep my data
* images here: http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
* I know that my phone is recognized by PC if I put it into ADB sideload mode (didn't yet try whether it works though)
* phone is also recognized when in fastboot
* possibly downgrade might work, but I am trying to find a method that will let me keep the data, if I get glitches I don't care for now
What I am not so sure about:
* flashing for example cm-12.1-YOG7DAS2K1-bacon-signed.zip in full should let me keep the data, true?
* taking fastboot image and just flashing boot&system should also let me keep the data, true? Did I miss anything?
What do you guys suggest I do? I know that in the end I might crash everything anyway, but at least I want to do the best I can (And make that backup soon after). Thanks for all and any help!
edit: Did the sideload flashing, that went fine, is easy. Problem is those images seem not to work for me anyway (bootloop). Probably because I didn't wipe userdata.
maybe try to use the restore tool (http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851) its pretty old (CM11s) but if it workd then refalsh the TWRP and update your phone to cm12.1 (with the required firmware)
A good question after all I did: Did anyone ever successfully downgrade from 13 to 12.1 without full data wipe?
p.s. it is very very easy to downgrade, it just doesn't work since OS upgrade makes changes to local data making it incompatible. This is what I did:
1) down+power on
2) chose upgrade and sideload upgrade from adb
3) while in that menu phone will wait for the update, just connect it to pc and do adb sideload image.zip (image needs to be signed ordinary image not the fastboot one)
4) wait until it completes and reboot phone
Tried all 4 CM12.1 images to no avail.
Dear all,
After flashing cm-13.0-ZNH0EAS2JK-bacon-signed FROM cm-12.1-YOG7DAS2K1 through TWRP on my rooted OPO as usual i do. MY mobile stuck in boot loader "CYANOGEN MOD READY" And not starting even after 45 mins.
So again i installed cm-12.1-YOG7DAS2K1-bacon-signed. Working fine. Tried many tiimes by wiping data,cache,dalvik too. But every time im stucking at boot loader "CYANOGEN MOD READY" . Please suggest me the best way to shift to marshmallow. I dont want to unroot.
skundurthy said:
Dear all,
After flashing cm-13.0-ZNH0EAS2JK-bacon-signed FROM cm-12.1-YOG7DAS2K1 through TWRP on my rooted OPO as usual i do. MY mobile stuck in boot loader "CYANOGEN MOD READY" And not starting even after 45 mins.
So again i installed cm-12.1-YOG7DAS2K1-bacon-signed. Working fine. Tried many tiimes by wiping data,cache,dalvik too. But every time im stucking at boot loader "CYANOGEN MOD READY" . Please suggest me the best way to shift to marshmallow. I dont want to unroot.
Click to expand...
Click to collapse
Take a backup of your internal storage
Flash factory images of CM13 using Index #8 http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
After flashing factory images, flash TWRP (Index #8)
After flashing TWRP, flash SuperSu from TWRP http://download.chainfire.eu/supersu-stable