• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [CDMA] Get ready for OTA's!

amarc78 said:
That's weird, tyr this: https://docs.google.com/file/d/0B4-30E6G5pbIWEx4aC1FMVpqYUk/edit?usp=docslist_api
Click to expand...
I did a little reading on this, and it seems Motorola needs to release the firmware and all the needed files are in an img called motoboot.img. This img exists in the firmware we have for 4.4.2 and 4.4.4 so it will probably exist in 5.0.2 firmware as well. I don't know if you want to take a chance again, lol, but i am downloading the firmware for Brazil XT1032 5.0.2 to see if motoboot.img is in there. If it is we may be able to get what you need but it may make things worse too :o
 
SuperR said:
I did a little reading on this, and it seems Motorola needs to release the firmware and all the needed files are in an img called motoboot.img. This img exists in the firmware we have for 4.4.2 and 4.4.4 so it will probably exist in 5.0.2 firmware as well. I don't know if you want to take a chance again, lol, but i am downloading the firmware for Brazil XT1032 5.0.2 to see if motoboot.img is in there. If it is we may be able to get what you need but it may make things worse too :eek:
Click to expand...
LOL. I'm downloading it to. It does have the motoboot.IMG. I had the firmware and just deleted it right before I bricked my phone. I just have no idea how to make it the right format for the tool.
 
amarc78 said:
LOL. I'm downloading it to. It does have the motoboot.IMG. I had the firmware and just deleted it right before I bricked my phone. I just have no idea how to make it the right format for the tool.
Click to expand...
I will try to mount it and see if I can extract the files. It will be next week at the rate this thing is downloading
 
Has anyone else noticed this rom has 250mb worth of swap space? That's why there's less storage space space. I was wondering how there was 500+mb of free RAM.
 
Last edited by a moderator:
Slayer72 said:
lost101 has posted the flashable zip for the 5.0.2 Soak Test OTA on XDA, head over there to pick it up :3
Click to expand...
I don't see where he posted it. Didn't he post it like 2 days ago then took it down because it had some issues? SuperR's is working pretty good for me.
 
Slayer72 said:
lost101 has posted the flashable zip for the 5.0.2 Soak Test OTA on XDA, head over there to pick it up :3
Click to expand...
Havent seen his for the XT1031, SuperR posted 2 versions here regular and debloated along with partition updater...they seem to be working perfectly so far.
 
SuperR both zip working perfectly, tried both and reverted to 4.4.4
Got flickering issue on both , might be due to 4.4.4 radio and bootloader, I didnt used partition updater.
again going to test full zip today night
 
I just found lost101's ROM in the general section on XDA. He made a debloat script for it.
Edit: I was wrong, it's in that Android Development section.
 
Last edited by a moderator:
flashed SuperR's full stock zip, working well with xposed.
this time did dalvik wipe after installing Xposed zip. no low space bug this time.
still on 4.4.4 BL and Radio so flickering is still visible.
 
How to recover from stuck at flash screen or bootloop.

I upgraded to 5.0.2 using the Blur OTA file as soon as it became available. It worked great. Then I rooted it with Chainfires Auto Root. Although it didn't go to the Red Android screen, once it rebooted I checked for root and I had root access. So again everything good to go.

Next I installed TWRP 2.8.5 Multirom Recovery, rebooted, still good. Next I flashed Multirom installer in recovery and thats where things went very wrong. It installed, took me to the ROM selection screen once, but after selecting "boot now" the phone stuck at "boot loader unlocked screen" and went no further. I tried a few more times but it was futile. So I thought I'd try and flash a "modded for multirom" kernel to remedy. Bad Idea... really bad. Now I lost recovery (not sure why, but I did) and only had access to adb/fastboot. Tried to fastboot flash back to KitKat and start over to reinstall the OTA and try again... minus Multirom of course. So I tried to return to full on out of the box stock with a stock image but it would not boot either. So I tried to ADB side load SuperR's stock 4.4.4 no luck there either. It failed at 84% everytime. So I tried his debloated and deodexed 4.4.4. And it booted but every two seconds it was force closing and was unusable.

After all this I began to think it was a done deal. No returning from this one. Then I saw SuperR made a fasbable zip of Lollipop. His "first attempt ROM". But it woud not sideload either failing at various points over and over again. Maybe if I could get that first attempt ROM to the internal storage I'd be good. There was only one ROM that booted since this disaster and that was SuperR's debloated 4.4.4.

Here is the fix...

1)Format everything System, cache, data, the works.

2)Fastboot firmware flash to attempt to get it back to a KIT KAT format.

3)ADB sideload SuperR's debloated, deodexed 4.4.4 Boot phone. (The phone fully booted but had major performance issues and FC's at this point but it allowed me to transfer the zip file of the "first attempt ROM" created by SuperR to the internal storage of the phone.

4)Boot to boot loader flash a custom recovery. Because your back to stock recovery after flashing the system image via fastboot.

5)Reboot to new recovery and do a full wipe. Now flash SuperR's "first attempt ROM" within recovery. Reboot the phone, and be patient. The first boot took 8 to 10 minutes but I finally got back to a working phone with 5.0.2!

I have had no problems since. I have the screen flicker problem only in recovery, nowhere else and the phone is saved from paper weight status.

Sorry about the long post just wanted people to know the conditions and circumstances of what shut me down.

I want to thank @SuperR for all his work and the ROMs he created for both KK and 5.0 they are the only game in town ATM that I know of to provide this "means to an end" fix. Without those ROMs my phone would be useless.
 
Last edited:
@joe5150, well that sounds like quite that hassle, LOL! Sorry for the laughing, but I couldn't help bit giggle while reading your post. I may have thrown the phone out the window. I'm glad you got it up and running again. Just don't try to flash a 4.4.4 kernel on a 5.0.2 ROM again, and DO NOT try to downgrade your bootloader! You will brick your phone and more than likely not be able to fix it. I'm beginning to think the flickering issue is from the kernel. It's not the bootloader because it's happening with Lollipop roms running the 4.4.4 bootloader. Hopefully the official OTA will not have this issue. I'm hoping it will be 5.1. I just tried lost101's ROM and it has some issues. Xposed won't stick, the gallery has issues, and there were a few other things I got fed up with. SuperR's is much better. I had one phone updated with the OTA zip and the other with SuperR's ROM and they both seemed exactly the same. Again, thanks and nice work @SuperR!
 
I see lost101 got in some trouble. No more ROM over there. Someone from Motorola had it taken down. I hope someone doesn't get so mad they don't give us an official update.
 
Updated one more moto g with superR zip, this time with partitions update , everything working fine. No flicker.
Also from 4.4.2 to 5.0.2 works no issues.
But partition updater won't work directly, need to flash 444 partition updater then 5.01 partition updater.
 
Looks like there's some major commits and changes in 5.1 that "may" fix the CDMA handling for lollipop on the XT1031...which makes sense because it'd be a pain to de-unify the falcon branch for a couple variants. That being said hope to see some updated AOSP and CM branches in the near future. [emoji16]
 
I did some partition experimenting. I flashed all the 5.0.2 partitions except the bootloader and it will not boot. I restored them back to 4.4.4 and it boots. I flashed just the 5.0.2 modem with no problems. I am not sure which one of the partitions will not allow boot with the 4.4.2 bootloader but I may do some further experimenting going one by one to see if I can remove the screen glitch and keep the 4.4.2 bootloader.
 
Slayer72 said:
MR1 is for 5.1, I just installed 5.1 on my Nexus 7 2012 Wifi tablet, it along with Nexus 5 and Nexus 10 were the first devices that Google released 5.1 factory images for
Click to expand...
Yeah I know MR1 ( Maintenance Release 1) is 5.1, I posted the change log because it looks like it addresses the CDMA hand off in telephony and other services. There's been talk of a de-unified branch for the 3G CDMA falcon devices, which would be silly(since it would effect CDMA only E series etc). I do find 5.1 much smoother on my Nexus 5 and "hopefully" it sorts out the remaining issues a lot of folks have been experiencing. The only issues I have with 5.0.2 on the Motorola G is dialer lag and WiFi/network handoff otherwise its been smooth.
 
SuperR said:
I did some partition experimenting. I flashed all the 5.0.2 partitions except the bootloader and it will not boot. I restored them back to 4.4.4 and it boots. I flashed just the 5.0.2 modem with no problems. I am not sure which one of the partitions will not allow boot with the 4.4.2 bootloader but I may do some further experimenting going one by one to see if I can remove the screen glitch and keep the 4.4.2 bootloader.
Click to expand...
So you don't think its a GPU glitch as some folks have been thinking?
 
starkraving said:
So you don't think its a GPU glitch as some folks have been thinking?
Click to expand...
Well, I think no. If you update all the partitions, you get no glitch while booting or running android but you get a glitch in recovery. If you don't update the partitions, there is no glitch in recovery and you get a glitch while booting and running android. I realize the glitch while running android is not a big deal because it goes away as soon as you turn off your screen once. However, it is a minor annoyance that would be better sorted out if possible. If it were a GPU issue, the problem would not switch from android to recovery with a partition update.
 
SuperR said:
Well, I think no. If you update all the partitions, you get no glitch while booting or running android but you get a glitch in recovery. If you don't update the partitions, there is no glitch in recovery and you get a glitch while booting and running android. I realize the glitch while running android is not a big deal because it goes away as soon as you turn off your screen once. However, it is a minor annoyance that would be better sorted out if possible. If it were a GPU issue, the problem would not switch from android to recovery with a partition update.
Click to expand...
Hmm well when I flashed the first time without the partition updater the flicker was present during initial boot and in recovery, disabling adaptive brightness worked for me in all other parts of the UI except recovery. I then did a clean install with the partition updater and the flicker was only present in recovery ... Not it the UI anywhere else. (Adaptive brightness was on initially.) So you're probably on to something.
 
I flashed the 5.0.2 partitions one by one with the exception of the bootloader. Here are the results:

Safe/No change
fsg
modem
sbl1
gpt
sdi

Breaks Boot
rpm
tz

In conclusion, the rpm and tz partitions rely on the 5.0.2 bootloader. The combination of the 3 or just one of them causes the change in glitches from android to recovery. It may be a kernel problem once on the 5.0.2 bootloader since all of our recoveries use 4.4.2 or 4.4.4 kernel. If I get some time I may build a new recovery with our 5.0.2 kernel source. Not even sure if it is released yet however.
 
You must log in or register to reply here.
Back
Top Bottom