Database Info

[Q] flashing cm11, after aosp 4.4.2, then cant revert to cm11

hello. so i flashed the cm11 beta 2 on my lg l5 610. wanted to try also the aosp 4.4.2 stock, but was a bit laggy. so i decided to go back to cm11. after flasing it, with cwm, it got into a loop, just the cm boot screen. done that many times( clearing cache, clearing data), reinstalling the cm11. no succes. all was done by recovery .

Unable to install custom ROMS - phone process error

Hi
Just moved onto the Moto G from a couple of Huawei devices, G300 then Y300... (bye bye Modaco!) - So I'm pretty used to flashig, wiping etc using TWRP and CWM...
Anyhow, got the Moto G (XT1033), booloader unlocked, done a full restore to clean 4.2 and let it update to 4.4 fine, no problems.
Installed the latest CWM, got root, all fine... again, no problems...
But EVERY rom I try - slim, CM11, always install OK but on booting come up with phone process failures and I have to abandon.
I tried putting the 422 modem zip from the CM11 thread on, made no difference.
So I've rewiped back to stock and updated to 4.4.2, and flashed CWM, but still can't install a custom rom, getting the phone process error on startup.
Any suggestions?

Resolved myself! Revert to factory, install CWM and flash new roms without doing the ota to kitkat first.

TangerineTractor said:
Resolved myself! Revert to factory, install CWM and flash new roms without doing the ota to kitkat first.
Click to expand...
Click to collapse
So you installed CM11 from stock jelly bean??
Sent from my XT1032 using Tapatalk

xheon said:
So you installed CM11 from stock jelly bean??
Sent from my XT1032 using Tapatalk
Click to expand...
Click to collapse
Yes. Originally I let it run through the ota update, then installed CWM and tried to install various roms. All gave me a FC on outdoor process as soon as I booted.
tried again with TWRP, same thing. third time lucky, I restored to factory, let it boot but didn't do the ota update, installed CWM for 4.3 bootloader, and all has been find since, flashed several roms with no problems.

So you have a dual SIM version and you flashed a custom ROM which means only one SIM works now. Am I right? How is everything else, no issues with performance just because yours is a dual SIM variant?

Cant update Android..

I have a rooted Moto G phone. It is android 4.3 , I cant update it to 4.4.2 Kitkat for some reason.
I saved Kitkat to the SD Card, loaded into Recovery mode on the MOTO, then tried to install Android 4.4.2 from the .zip file
saved on the SD card in my phone.
I cant get this to work and i tried to install CARBON ROM the same way with out any results.. it says ERROR and fails to install.
Any help would be greatly appreciated.
ALSO does android need to be updated to 4.4.2 to install CARBON ROM?
Thanks

I don't know but maybe can help...
I could update successfully to last minor 176.44.1 update only after flashing stock recovery.img from my exact stock ROM.
after rooting process on KitKat motoG my recovery was modified, restoring the stock one worked for me. I just updated ota normally in WiFi without problems.
after that I flashed cwm recovery.

I restored to stock recovery and removed root. After that applied KitKat OTA, then flashed custom recovery and re-rooted.
Sent from my Moto G using Tapatalk

this involve wiping of all data and a factory reset, so first try just restoring the stock recovery.
If not working make a good backup first.

If the phone is rooted, OTA updates do not work afaik...

gymfreak81 said:
ALSO does android need to be updated to 4.4.2 to install CARBON ROM?
Thanks
Click to expand...
Click to collapse
Flashing a ROM overwrites system partition completely. You could have android version 1 running and still just flash another ROM

[Completed] My t999 s3 doesnt want to install cyangenmod

i had cm10 installed but after a few months of problems i decided to upgrade to cm11. After trying to upgrade to twrp 2.8.3 something happened then my cyangen was tripping balls so i went back to stock s3 4.1.3 by flashing with odin. Then i rooted my s3 again using odin. Then i installed rashr and installed twrp 2.8.3. Then i booted into twrp 2.8.3 and before twrp loaded it had the cyanogen logo on it.Then did factory reset and the davik cahce clear thing. Then i proceeded to installed cm11 20141112 snapshotm12 and gapps kk20140606 but when i rebooted my s3 in still goes into the stock andriod what is going on? i tried to install cyanogen mod from a different sd card and i have no luck

eric95204 said:
i had cm10 installed but after a few months of problems i decided to upgrade to cm11. After trying to upgrade to twrp 2.8.3 something happened then my cyangen was tripping balls so i went back to stock s3 4.1.3 by flashing with odin. Then i rooted my s3 again using odin. Then i installed rashr and installed twrp 2.8.3. Then i booted into twrp 2.8.3 and before twrp loaded it had the cyanogen logo on it.Then did factory reset and the davik cahce clear thing. Then i proceeded to installed cm11 20141112 snapshotm12 and gapps kk20140606 but when i rebooted my s3 in still goes into the stock andriod what is going on? i tried to install cyanogen mod from a different sd card and i have no luck
Click to expand...
Click to collapse
Do you mean this unofficial CM11: [ROM][4.4] CM 11 Unofficial - Beta 7 11-22-13 (Discontinued due to new device)?
Or this one: Cyanogenmod CM11?
Please check this thread: T999 UVDMD5 Firmware / Bootloader.
According to this, you might have to update some files (bootloader, modem, etc.) to be able to install newer CM versions.
AFAIK, only CM10 is officially suported for your device: [ROM][OFFICIAL] CyanogenMod 10 Nightly Builds for SGH-T999.
If you have further questions, please ask in the T-Mobile Galaxy S III Q&A, Help & Troubleshooting.

Thread closed and thank you.

TWRP: Pre-ROM flash Wipe, boots back into system instead (Moto G 4G LTE)

Hi guys,
Not sure if anyone else has had this issue, but I've only got a Moto G 4G fairly recently (my Nexus 5 died) and have been attempting ROM flashing (never had an issue with multiple Nexus phones & tablets) I was flashing the rom OK but the sim card wasn't recognised - so went back to rooted stock Kitkat & Xposed.
Today I thought I'd give it another go, got into TWRP, advanced wipe as usual...but it didn't complete and the phone suddenly booted back into the system (with the Android upgrading/optimizing message you usually get when starting a new phone)
System is untouched, still rooted/xposed etc. Does anyone have an idea why this has suddenly happened? Never encountered anything like this before. TWRP is the latest version 3.1.1.0
Any suggestions welcome, cheers.

Just thinking....would flashing with adb be a solution?

Just flash lollipop stock ROM using mfastboot
later you can flash twrp recovery and then proceed with the nougat or oreo based ROM.. Bootloader should be updated so my suggestion is flash lollipop stock ROM