Database Info

CM 11 cripples Moto G, can't use ADB/fastboot to install CM 10

I installed Cyanogen Mod (cm-11-20140504-SNAPSHOT-M6-falcon.zip) on my 1st generation Moto G using TWRP. When I boot into CM, I keep getting the message that "Unfortunately, the process com.android.systemui has stopped". Every time I banish that popup, I get a split second of usage before it pops up again. After some troubleshooting and web searching, I found that I have to revert to CM 10. The details are documented at androidforums.com/threads/windows-mtb-usb-device-driver-error-when-moto-g-running-twrp.901001 and forum.xda-developers.com/chef-central/android/windows-mtb-usb-device-driver-error-t3022946
I haven't searched for CM 10 yet, but I'm scouting out the process to push it to the device. I can't find a way to get ADB to see the device, even after enable USB debugging (www.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android and android.stackexchange.com/questions/67249/how-to-enter-usb-debugging-mode-in-cyanogenmod). Given that I only have a split second after banishing each error message, that took forever, but I confirmed that USB debugging is enabled after rebooting.
The only alternative I know to ADB is fastboot. According to forum.xda-developers.com/showthread.php?t=702069, it is theoretically possible for fastboot to flash a ROM, but the zip file should contain a data.img and system.img. I checked the CM 11 zip file to see what I can expect from CM 10, and found no such img files.
Given that ADB and fastboot processes don't work for me (at least the the degree that I've explored them), what other options are there for flashing CM 10?
P.S. Does anyone know how to get exit (say) Settings or the browser and get back to the cyanogenmod start page? There is no home button, and web searching refers an icon with 3 bars on the top, which I don't have. I basically have to reboot.

my1stSmartPhone said:
I installed Cyanogen Mod (cm-11-20140504-SNAPSHOT-M6-falcon.zip) on my 1st generation Moto G using TWRP. When I boot into CM, I keep getting the message that "Unfortunately, the process com.android.systemui has stopped". Every time I banish that popup, I get a split second of usage before it pops up again. After some troubleshooting and web searching, I found that I have to revert to CM 10. The details are documented at androidforums.com/threads/windows-mtb-usb-device-driver-error-when-moto-g-running-twrp.901001 and forum.xda-developers.com/chef-central/android/windows-mtb-usb-device-driver-error-t3022946
I haven't searched for CM 10 yet, but I'm scouting out the process to push it to the device. I can't find a way to get ADB to see the device, even after enable USB debugging (www.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android and android.stackexchange.com/questions/67249/how-to-enter-usb-debugging-mode-in-cyanogenmod). Given that I only have a split second after banishing each error message, that took forever, but I confirmed that USB debugging is enabled after rebooting.
The only alternative I know to ADB is fastboot. According to forum.xda-developers.com/showthread.php?t=702069, it is theoretically possible for fastboot to flash a ROM, but the zip file should contain a data.img and system.img. I checked the CM 11 zip file to see what I can expect from CM 10, and found no such img files.
Given that ADB and fastboot processes don't work for me (at least the the degree that I've explored them), what other options are there for flashing CM 10?
P.S. Does anyone know how to get exit (say) Settings or the browser and get back to the cyanogenmod start page? There is no home button, and web searching refers an icon with 3 bars on the top, which I don't have. I basically have to reboot.
Click to expand...
Click to collapse
This is the wrong forum to post this in. Also, Snapshot M6 is almost a year old. Flash the latest nightly. That will work better. There's no CM10 for this device since it shipped with Android 4.3, so you'd be wasting your time looking for it. Even though systemui is crashing, mtp will still work, so you can transfer files to your phone normally. Also, this should teach you, that it is dangerous to experiment with your phone without a legitimate way out of issues or a backup.

As you able to flash a custom rom via custom recovery?

Press and hold power and volume down button together till 10 secs after your phone is turned off. You will go to bootloader menu. Connect it via USB to access fastboot.

@audit13: Re. whether I can flash via custom recovery, the short answer is no. I haven't been able to get CWM working, but with TWRP, I could flash CM 11 if I first push the zip file to /sdcard with the device booted up normally. TWRP has a problem with MTP drivers (seems endemic, from what I've been able to find online), and ADB on my laptop can't see the device when it is running TWRP. I've documented this in the 1st 2 links of paragraph 1 in my original post. Unfortunately, with CM 11 installed, the laptop can't see the device at all, so no push is possible. That is the reason why I was trying to find info on flashing via fastboot in my original post. Please note that I also haven't been able to get TWRP to sideload, probably due to the invisibility of the device to the laptop.
@i_rnb: I can get into bootloader OK, but my concern is how to use fastboot to flash an OS rather than a recover. According to forum.xda-developers.com/showthread.php?t=702069, it is theoretically possible for fastboot to flash a ROM, but the zip file should contain a data.img and system.img. I checked the CM 11 zip file to see what I can expect from CM 10, and found no such img files.

Did you try the latest Philz from here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/falcon/
That's what I used on my xt1032 and it's fine for install ROMs via OTG and internal SD card.
Flashing via fastboot should work as long as you are able to boot into fastboot mode and the proper drivers are installed.
Stock ROMs with have the system.img or data.img files you need where as custom ROMs do not.

my1stSmartPhone said:
@audit13: Re. whether I can flash via custom recovery, the short answer is no. I haven't been able to get CWM working, but with TWRP, I could flash CM 11 if I first push the zip file to /sdcard with the device booted up normally. TWRP has a problem with MTP drivers (seems endemic, from what I've been able to find online), and ADB on my laptop can't see the device when it is running TWRP. I've documented this in the 1st 2 links of paragraph 1 in my original post. Unfortunately, with CM 11 installed, the laptop can't see the device at all, so no push is possible. That is the reason why I was trying to find info on flashing via fastboot in my original post. Please note that I also haven't been able to get TWRP to sideload, probably due to the invisibility of the device to the laptop.
@i_rnb: I can get into bootloader OK, but my concern is how to use fastboot to flash an OS rather than a recover. According to forum.xda-developers.com/showthread.php?t=702069, it is theoretically possible for fastboot to flash a ROM, but the zip file should contain a data.img and system.img. I checked the CM 11 zip file to see what I can expect from CM 10, and found no such img files.
Click to expand...
Click to collapse
I'm sorry, but you're misunderstanding/reading the wrong things. You WILL NEVER find CM10 for the Moto G because CM 10 simply never existed for this device. You need to look for issues which are device specific and not just general issues all over the internet. Also, you WILL NEVER find a system.img and data.img in a CM11 zip. Those are only found in the stock ROM meant specifically for flashing via fastboot. All that information can be found by looking around the Moto G XDA forums itself. You'll find a lot of helpful stuff in the General section. You can also push a zip to /sdcard. You need to boot into bootloader and then push via ADB. MTP works on the latest TWRP recovery. So you can transfer it to your phone that way too.

audit13 said:
Did you try the latest Philz from here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/falcon/
That's what I used on my xt1032 and it's fine for install ROMs via OTG and internal SD card.
Flashing via fastboot should work as long as you are able to boot into fastboot mode and the proper drivers are installed.
Stock ROMs with have the system.img or data.img files you need where as custom ROMs do not.
Click to expand...
Click to collapse
I need to become familiar with Philz. Being a newcomer to smartphones, it's not familiar to me. One of the fundamental requirements that I established at the outset of my search for a smartphone was to have the provider of the OS & phone be trustworthy or, failing that, go to open source so that it has the eyes of the world on it. It is also why I seek to be familiar with the source of ROMs, tools, etc. So far, I tried to download to from main sites for CWM, TWRP, and CM 11.
I know, it sounds odd these days, but I'm spoiled from before the internet days, when you can store any personal info you want on electronic organizers that had no connection, wired or wireless, to computers or the internet (which didn't exist). These days, it seems that you have to be very careful if you wish store any personal info on these personal devices. Either that, or carry a paper organizer around for the personal stuff (and I don't want to do that).
Thanks for confirming flashability via fastboot even without system.img and data.img. As it turns out, however, it isn't as promising a way ahead for me because I found out that the reversion back to CM 10 was a mistake (www.reddit.com/r/cyanogenmod/comments/2gvmqu/cm11moto_g_comandroidsystemui_is_crashing_after). The OP meant M10 snapshot, not CM 10. Which is odd, since the Moto G has no M10 snapshot (download.cyanogenmod.org/?type=snapshot&device=falcon). There's no M10 in the names of the nightly snapshots either (though that's less of a concern for me as I don't want to wander into nightly territory until I get the confidence of having my first attempt working).
I'll mull over Philz after some web search. I also distinctly recall backing up the stock Carrier ROM, so perhaps another way out is to find it and go through the details of restoring it.

my1stSmartPhone said:
@i_rnb: I can get into bootloader OK, but my concern is how to use fastboot to flash an OS rather than a recover. According to forum.xda-developers.com/showthread.php?t=702069, it is theoretically possible for fastboot to flash a ROM, but the zip file should contain a data.img and system.img. I checked the CM 11 zip file to see what I can expect from CM 10, and found no such img files.
Click to expand...
Click to collapse
1. Boot into Fastboot.
2. Flash TWRP recovery via Fastboot.
3.. Select Recovery from the menu and boot to TWRP recovery.
4. Put the ROM zip in a USB OTG drive.
5. Connect it to your device and mount it from recovery menu.
6. Install the zip via TWRP recovery from USB OTG.
DONE !

This is very odd.
I could not restore from my pre-CyanogenMod backups because when I browse to the date+time-stamped folders, it was empty. However, I had previously copied to contents of at least one date+time-stamped folder to my laptop.
I used fastboot to uprade TWRP from 2.8.3 to 2.8.4 in hopes of getting past the MTP driver problem, which would enable me to copy the files back to the device. Halleluya, it did allow the device to be seen in Windows Explorer. But I didn't need to use the copy on the laptop because moving to 2.8.4 also allowed the backups to be seen on the device.
I gleefully restored the backup. It said "failed", but I rebooted anyway. Unfortunately, the failed restoration was real, and I was still with CyanogenMod. I interrupted the boot process to get back to bootloader.
I reverted back to TWRP 2.8.3, hoping that it would still see the backup. I was hoping that 2.8.3 would properly restore the backup because it was created using 2.8.3. It did indeed see the backup, but the restoration still resulted in "failed", and a reboot still led to the CyanogenMod bootup.
Oddly, CyanogenMod booted properly this time without the repeated systemui popups. It's great! Though I wonder if I somehow affected CyanogenMod with the failed attempts at restoring the stock carrier's ROM. Not that I care right now. CyanogenMod awaits exploration.
But there are a couple of things that I hope someone can comment on. What might cause CyanogenMod to boot properly after upgrading TWRP and reverting back, failing to restore the stock carrier ROM with both versions? Could CyanogenMod now be corrupt? And why won't my backups restore? How can I ensure that I create good backups?
P.S. Thanks to i_rnb for the tip about USB OTG. I did not go that route because I only have the cable that came with the device.
P.P.S. I'm a bit (or rather, quite) unsettled by the randomness with which things work...

I downloaded the CyanogenMod nightly for Moto G, cm-12-20150213-NIGHTLY-falcon.zip. I got it working. Pretty robust so far, so I want to enjoy it a bit before clobbering it by attempting to restore the Carrier stock ROM. I admit that I will have to do that at some point because I need to ensure that my backups are good.
I would like to take this opportunity to recount how I got around the problems I faced. I think that others may run into this, and my story may help them get back to a working phone when it looks like it is bricked.
The problem was that CM 11 was crippled by the repeated systemui popup messages. I thought it went away, but it came back. I still don't know what triggers it. And my backups of the carrier OS either failed to restore (twrp 2.8.3) or were not visible (twrp 2.8.4). I had spent so many days trying to think of a way ahead that simply didn't care about bricking the phone anymore. After all, it wasn't doing a whole lot of good as-is. So in one of my attempts of trying something, I erased the OS in the process of re-installing CM 11. And the re-install failed. Not a good situation, since ADB worked only when an OS was running (not when a recovery was running), and the MTP driver errors prevented the device from being accessed from windows when recovery was running. It didn't matter whether I was running twrp 2.8.3, 2.8.4, or CWM. So sideload didn't work in any of those recoveries.
There was basically no way to push *any* new OS to the phone. I forgot the details, but the CM 11 imag file that was on the phone might not have been visible to the one or more of the recoveries I tried. I was so out of options that I even tried fastboot to flash to OS, and that did not succeed.
Here is what I found worked. I don't know what particular detail was responsible for the success, so it requires experimentation.
First, I un-installed re-installed the SDK tool set for installing custom ROMs, making sure that I included Google USB drivers. The subsequent update required many more things to be installed, so that might have been part of the solution. I then looked for Motorola driver apps in Windows's Programs menu, uninstalled both, and re-installed. I don't know what contribution it had to the success, as I never got the Device Manager running. Whenever I launched it, it searched for updates, came back and reported no updates and that my device was uknown, then quit. Maybe because no OS on the device was running.
The one thing that seemed to help was that, even though the device was otherwise incommunicato from the laptop, I was able to fastboot flash recoveries. After the above re-installs, a re-install of twrp 2.8.4 allowed the computer to see the device in Windows Explorer. I believe it had something to do with better-functioning MTP USB drivers in the re-install, but I can't be sure. So I was able to copy the nightly CM 12 to the device, then use one of the recoveries to install it.
But the story didn't end there. Even after the CM install, I was still getting repeated popups. This time, however, it was something other than systemui, but otherwise, the symptoms were the same. At that point, I had pretty well concluded that my experiment with Moto G was at its end, and that I would look at Blackberry (now that they committed to stay in the handset market). But I did half-heartedly experiment a bit more. Good thing, too, because the 2nd attempt at re-installing CM 12 seems to have worked. No repeated popups so far. What I made sure that I did was to wipe out anything for which there was a check box, e.g., any cache, data partition, OS, etc. Since it was a virgin phone, I could do this with impunity, so I'm not sure how well this "solution" would fit someone else's situation. Also, I did try to wipe things in past attempts, just not with so much thoroughness.
So there you have it. I hope this helps someone.

[Q&A] [ROM][5.X][XT1028/XT1031] CyanogenMod 12.1 for Moto G [METICULUS]

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.

Trying to do CM13 to CM12.1 downgrade on soft-bricked

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

How To Guide (P12/TB-Q706F) Flash GSI on Xiaoxin Pad Pro 12.6

C:
#include <std/disclaimer.h>
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear
* war, or the current economic crisis caused by you following these
* directions. YOU are choosing to make these modifications, and
* if you point your finger at me for messing up your device, I will
* laugh at you.
*/
I bought the new tablet and unlocked it as soon as I was able to. After some fiddling I eventually got GSI up and running.
Originally I planned to post this when an actual forum for P12 becomes available, but given some known issues with the stock FW at the time of writing, I think I'll just post it here now.
What you need
1. Unlocked bootloader
Go to ZUI official unlock page to request an unlock (the page is in Chinese). For this tablet, you need to use the 4th option (Lenovo Tablet), which only requires you to enter the device's SN (can be found in the Settings screen, or from bootloader). Once you obtained the file needed to be flashed for unlocking, follow the official instructions to unlock the device.
NOTE: You need to wait for at least 8 hours since the device's initial connection to Internet to get your device's SN recognized by the official unlock service. If it complains about "incorrect SN" but you've verified that your input is correct, simply wait a few more hours and try again.
!!! WARNING: Like any other Android device, unlocking bootloader will wipe your data so BACKUP FIRST !!!
2. fastboot
The process utilizes fastboot exclusively, so make sure you have fastboot installed. No other tools are needed.
3. Magisk-patched boot.img, or a patched vbmeta
As there's currently no available PRC ROM dump for this tablet, the currently only known ROW dump will do.
Although you should be able to use GSI without Magisk, you'll probably need to patch vbmeta so the stock kernel won't refuse to boot the GSI in this case. This guide does not cover non-Magisk scenario for now, as I'm not entirely sure. With Magisk, patching vbmeta is not needed. Optionally you may consider patching and flashing vbmeta_system (it's most likely not needed).
!!! WARNING: Flashing images with fastboot/fastbootd can invalidate existing encryption signature so the device will no longer be able to decrypt userdata, requiring you to format and start over. As a result, BACKUP EVERYTHING FIRST IN CASE OF CLEAN FLASHING OR UPDATING OTHER COMPONENTS. !!!
4. Additional stuffs to flash
WARNING: This tablet happens to be very picky about the kernel and vendor image you use when running GSI. While a mismatched kernel (Magisk patched) worked fine on stock as far as I could remember, on GSI, it'll result in the device's Wi-Fi and Audio not working, unless additional components (vendor, maybe also odm) of the same FW version are also used.
If you're going to use the boot.img from the ROW dump (and patched it with Magisk), note about these images from the dump. I think at least vendor is needed. You may also try flashing odm if you're having issues.
- super_5.img (vendor.img)
- super_6.img (odm.img)
FOR EXPERTS: The boot.img and vendor.img (as well as additional files like dtbo and vbmeta) from Android 12L developer preview might also be usable for running GSIs. I haven't tested this yet and it's possible the binaries may carry known or unknown issues.
Steps to flash GSI
1. Enter fastboot
Use the following adb command to enter fastboot.
Bash:
adb reboot bootloader
2. Enter fastbootd
Enter the following command to enter fastbootd, where you can actually access the system partitions, as this tablet uses Dynamic Paritions.
Bash:
fastboot reboot fastboot
WARNING: The following steps will actually modify your system partitions and may leave your tablet unbootable. Make sure you have backed up everything before proceeding.
3. Flash Magisk patched boot.img
Assume you have the Magisk patched boot.img as boot_magisk.img, enter the following command.
Bash:
fastboot flash boot boot_magisk.img
Note that you can also flash boot.img directly from fastboot, before entering fastbootd.
4. Flash the GSI
Enter the following commands, assuming your GSI is called gsi.img.
Bash:
fastboot erase system
fastboot flash system gsi.img
Note that the erase command is optional. Replace gsi.img with the actual GSI image file of your choice.
5. Flash additional stuffs
You need to flash the vendor.img (or also odm.img) from the same FW dump as your boot.img. Assuming your vendor image is vendor.img, and odm image is odm.img, use the following command.
Bash:
fastboot flash vendor vendor.img
fastboot flash odm odm.img
NOTE: For which image files in the ROW dump correspond to vendor and odm, read above.
FOR EXPERTS: If you could somehow obtain a dump of the running boot.img and patch it with Magisk, you may skip this step, but you can always flash those stuffs in case Wi-Fi and Audio are not working. As there's no known PRC ROM dumps at the time of writing, I'm not entirely sure.
6. Wipe userdata if needed
You don't need to wipe userdata if you are dirty flashing newer build of a same GSI over the existing one.
In case you need to do so (such as flashing a different GSI, or factory reset), enter the following commands.
WARNING: These commands will erase everything in the internal storage, not just app data! Make sure you have everything in the internal storage backed up before doing this.
Bash:
fastboot erase userdata
fastboot erase metadata
7. Reboot
Enter the following command to reboot.
Bash:
fastboot reboot
If nothing goes wrong and the GSI doesn't have any major issue that might prevent it from successfully booting, you should be able to boot the GSI and further configure it yourself.
Current Status for GSIs
So far everything I could test works on Android 11 and 12 GSIs.
- Wi-Fi (needs matching vendor and maybe odm images, read above)
- Camera (both sides)
- Fingerprint Sensor (may occasionally not work)
- 120Hz refresh rate
- Bluetooth (Lenovo Precision Pen works)
- Physical Keyboard Case
I'm currently running DotOS 5.2 GSI on this tablet and am yet to encounter any serious issue. Even some demanding games work just fine. Just that when using the boot.img, vendor.img (as well as odm.img) from the ROW dump, the system would use a smaller font size by default.
The latest phh-AOSP A12 (v400) as well as some other unofficial A12 GSIs can work with this tablet. I'm currently running SuperiorOS-12. Everything works fine after some tweaking, just that I noticed some touch related issues which might have something to do with similar reports on official Android 12L beta.
NOTE: Like any other Qualcomm devices, "Use alternate audio policy" option may be needed to ensure audio works the same as on stock ROM. However, it seems audio can work without enabling this option on Android 12 GSIs.
Still, I'm not sure about how to get features specific to ZUI, like Desktop Mode, to work on GSIs.

Wow you seem to know your stuff.
Currently i'm stuck with a 12.6 tablet which is stuck in the boot loader due to flashing the ROW ROM and tripping the region lock check. The boot loader wont let me activate any other modes (i.e. Recovery). Am I stuck this way until I can get a bootable Chinese ROM?
I don't suppose you made a backup of your original chinese ROM did you? If so if you could share with my I definitely owe you a few drinks!

mardon85 said:
Wow you seem to know your stuff.
Currently i'm stuck with a 12.6 tablet which is stuck in the boot loader due to flashing the ROW ROM and tripping the region lock check. The boot loader wont let me activate any other modes (i.e. Recovery). Am I stuck this way until I can get a bootable Chinese ROM?
I don't suppose you made a backup of your original chinese ROM did you? If so if you could share with my I definitely owe you a few drinks!
Click to expand...
Click to collapse
Sorry, I don't have a full backup of the ROM my device had (I even let the device took an OTA, but all I got is a useless incremental package).
It certainly wasn't possible for me to dump partitions without being rooted first. So far I haven't seen anyone released a dumped a PRC FW for this device at a place that's easy to find.
I didn't flash everything from ROW. I only flashed some of the files (boot, vendor, odm, vbmeta, vbmeta_system) from ROW when I was trying to get GSI working. Some of the stuffs I flashed (namely vbmeta and vbmeta_system) may be optional, though.

@LSS4181 are we able to load the stock global P12 rom onto the Chinese Xiaoxin devices?

pdscoelho said:
@LSS4181 are we able to load the stock global P12 rom onto the Chinese Xiaoxin devices?
Click to expand...
Click to collapse
I didn't try it myself. mardon85 flashed the ROW FW before and the device got stuck at bootloader with virtually no way to recover.
Personally I'm against doing anything reckless when your bootloader is locked, as I don't know what can happen. The device may at worst end up hard-bricked.
It may be safe to flash these things when you're unlocked. When flashing, DON'T flash anything more than necessary. In fastbootd mode, just flash boot, system, vendor and vbmeta should be sufficient.
Assuming you're unlocked, you may consider patching boot with Magisk if you like. If not, you probably need to patch vbmeta to prevent bootloader from freaking out.
EDIT: I've updated the OP a bit to reflect the existence of an official Android 12 developer preview which is for our device, in case you might be interested. The package contained just these stuffs: boot, dtbo, system, vendor and vbmeta. Not sure if dtbo is also needed, though.

LSS4181 said:
I didn't try it myself. mardon85 flashed the ROW FW before and the device got stuck at bootloader with virtually no way to recover.
Personally I'm against doing anything reckless when your bootloader is locked, as I don't know what can happen. The device may at worst end up hard-bricked.
It may be safe to flash these things when you're unlocked. When flashing, DON'T flash anything more than necessary. In fastbootd mode, just flash boot, system, vendor and vbmeta should be sufficient.
Assuming you're unlocked, you may consider patching boot with Magisk if you like. If not, you probably need to patch vbmeta to prevent bootloader from freaking out.
EDIT: I've updated the OP a bit to reflect the existence of an official Android 12 developer preview which is for our device, in case you might be interested. The package contained just these stuffs: boot, dtbo, system, vendor and vbmeta. Not sure if dtbo is also needed, though.
Click to expand...
Click to collapse
Yeah I'm interested in trying out the Android 12L beta lenovo have released for the P12 but not sure if I can try it on the Chinese Xiaoxin?
Hence I want to load the global rom. I'm not in a hurry though. Will wait for more support. Don't want to brick my device.

pdscoelho said:
Yeah I'm interested in trying out the Android 12L beta lenovo have released for the P12 but not sure if I can try it on the Chinese Xiaoxin?
Hence I want to load the global rom. I'm not in a hurry though. Will wait for more support. Don't want to brick my device.
Click to expand...
Click to collapse
Lenovo have been pretty ****ty with this tbh. There's no recovery image for the Chinese ROM but if you flash anything including the New Android Preview which Lenovo actively promote you are at real risk of bricking your device.
I would leave well alone until one becomes available.

I've got 12L running on my Xiaoxin Pad Pro 12.6. I couldn't stand the original stuff that was on there. Its pretty janky and has a lot of features disabled. I didn't make a backup of my original ROM b/c there was no way I was going back, but I should have. Today, I tried to go back to an official ROM via the Lenovo Rescue and Smart Assistant app which wasn't successful. Well, it was successful as far as tool was concerned, but the tablet said the software wasn't compatible once it booted and then just powered off. It downloaded TB_Q706F_USR_S211043_2111300010_Q00243_ROW. Probably didn't like the 8 GB or the 256 GB flash. No idea. I was able to get it into fastboot mode and re-flash it w/ 12L so no worse off than before.
As far as 12L on this, it works, but as mentioned, lots of features not present. It is buggy in detecting finger presses and scrolling. Once I'm in an app, it works pretty well other than I have trouble getting touches to register properly. I hope this unit becomes supported once 12L goes legit. The Chinese ROM was horrible, all kind of garbage on it, weird modes, setting not even close to normal, and lots of Chinese language regardless of the language settings. I had to use Google Translate on my phone to read some of the pop-ups. Very annoying, but, hey, I bought a Chinese unit. Me wanting that 8GB and 256 GB flash may end up biting me in the butt.

Slimerang said:
I've got 12L running on my Xiaoxin Pad Pro 12.6. I couldn't stand the original stuff that was on there. Its pretty janky and has a lot of features disabled. I didn't make a backup of my original ROM b/c there was no way I was going back, but I should have. Today, I tried to go back to an official ROM via the Lenovo Rescue and Smart Assistant app which wasn't successful. Well, it was successful as far as tool was concerned, but the tablet said the software wasn't compatible once it booted and then just powered off. It downloaded TB_Q706F_USR_S211043_2111300010_Q00243_ROW. Probably didn't like the 8 GB or the 256 GB flash. No idea. I was able to get it into fastboot mode and re-flash it w/ 12L so no worse off than before.
As far as 12L on this, it works, but as mentioned, lots of features not present. It is buggy in detecting finger presses and scrolling. Once I'm in an app, it works pretty well other than I have trouble getting touches to register properly. I hope this unit becomes supported once 12L goes legit. The Chinese ROM was horrible, all kind of garbage on it, weird modes, setting not even close to normal, and lots of Chinese language regardless of the language settings. I had to use Google Translate on my phone to read some of the pop-ups. Very annoying, but, hey, I bought a Chinese unit. Me wanting that 8GB and 256 GB flash may end up biting me in the butt.
Click to expand...
Click to collapse
I agree the Chinese rom is absolutely terrible and very buggy.
For a number of reasons this will be my last Lenovo product. Unless they release some significant fixes this will be getting traded out for a Samsung Tablet ASAP.

Slimerang said:
I've got 12L running on my Xiaoxin Pad Pro 12.6. I couldn't stand the original stuff that was on there. Its pretty janky and has a lot of features disabled. I didn't make a backup of my original ROM b/c there was no way I was going back, but I should have. Today, I tried to go back to an official ROM via the Lenovo Rescue and Smart Assistant app which wasn't successful. Well, it was successful as far as tool was concerned, but the tablet said the software wasn't compatible once it booted and then just powered off. It downloaded TB_Q706F_USR_S211043_2111300010_Q00243_ROW. Probably didn't like the 8 GB or the 256 GB flash. No idea. I was able to get it into fastboot mode and re-flash it w/ 12L so no worse off than before.
As far as 12L on this, it works, but as mentioned, lots of features not present. It is buggy in detecting finger presses and scrolling. Once I'm in an app, it works pretty well other than I have trouble getting touches to register properly. I hope this unit becomes supported once 12L goes legit. The Chinese ROM was horrible, all kind of garbage on it, weird modes, setting not even close to normal, and lots of Chinese language regardless of the language settings. I had to use Google Translate on my phone to read some of the pop-ups. Very annoying, but, hey, I bought a Chinese unit. Me wanting that 8GB and 256 GB flash may end up biting me in the butt.
Click to expand...
Click to collapse
Good to hear that 12L preview can work on PRC models without a hard brick. As for the incompatible software issue, it was some kind of region lock implemented since around ZUI version 12.6. Xiaoxin Pad Pro 2021 users are probably more familiar about this phenomenon than us.
According to official information regarding the 12L preview, they already knew some features are not in a usable state yet, and probably disabled them artificially.
By the way, I'm not sure about your touchscreen issues. Did it happen on stock A11? On my device with GSI the touchscreen works almost flawless. Every single tap is being correctly registered, just that it's a bit oversensitive with swipes (not a major issue, though).
PS: I'm new to Lenovo Rescue and Smart Assistant app, but from your experience, it seems to be able to download a more recent ROW ROM image, although it won't be useful for PRC devices other than getting GSIs running.
mardon85 said:
I agree the Chinese rom is absolutely terrible and very buggy.
For a number of reasons this will be my last Lenovo product. Unless they release some significant fixes this will be getting traded out for a Samsung Tablet ASAP.
Click to expand...
Click to collapse
Personally I would recommend against any Samsung devices from now on. My previous Samsung Galaxy Tab S7+ is plagued by all kinds of touchscreen issues that I don't think it was mere hardware issue. Not to mention some new Samsung devices (like Z Fold 3) disables camera upon unlock to completely deter people from rooting (oh, and there's the so-called DefEx).
While the stock FW sucks, of all devices I've owned, unlocked and customized, Lenovo/Motorola ones are among the easiest to bring up.

Nice to see some progress on this part. I really enjoy the tablet in terms of hardware and looks but the SW is just ugh. Seems like it's just a waiting game now then for 12L. Is there no ROW variant with 8/256?

LSS4181 said:
Good to hear that 12L preview can work on PRC models without a hard brick. As for the incompatible software issue, it was some kind of region lock implemented since around ZUI version 12.6. Xiaoxin Pad Pro 2021 users are probably more familiar about this phenomenon than us.
According to official information regarding the 12L preview, they already knew some features are not in a usable state yet, and probably disabled them artificially.
By the way, I'm not sure about your touchscreen issues. Did it happen on stock A11? On my device with GSI the touchscreen works almost flawless. Every single tap is being correctly registered, just that it's a bit oversensitive with swipes (not a major issue, though).
PS: I'm new to Lenovo Rescue and Smart Assistant app, but from your experience, it seems to be able to download a more recent ROW ROM image, although it won't be useful for PRC devices other than getting GSIs running.
Personally I would recommend against any Samsung devices from now on. My previous Samsung Galaxy Tab S7+ is plagued by all kinds of touchscreen issues that I don't think it was mere hardware issue. Not to mention some new Samsung devices (like Z Fold 3) disables camera upon unlock to completely deter people from rooting (oh, and there's the so-called DefEx).
While the stock FW sucks, of all devices I've owned, unlocked and customized, Lenovo/Motorola ones are among the easiest to bring up.
Click to expand...
Click to collapse
As far as the touchscreen, I was so frustrated by the Chinese ROM that I didn't mess w/ it very much until I got 12L up. I think it is the S/W and not H/W b/c the RSA (Lenovo App) asks to install an app called Mobile Assistant on the tablet that becomes active when RSA is running. It probably runs by itself also. When it is active it has some tests and all the tests pass, like dragging a circle across the screen in ~15 different areas and also a touch test that tracks all 10 fingers very well. I wish I had my old ROM to try that out just for knowing that screen is good.
Maybe I'll give the GSI a try.

Hello friends,
I ran into the very same problem you had with region lock. The Rescue and Smart Assistant tool ruined the device and I can't boot it anymore. Having this error message "The current system is not compatible …"
I tried going back to at least the 12L Preview but every time I run the script, it doesn't work. The device is not authorized
List of devices attached
HA**** unauthorized
How can I get it authorized from the recovery screen? There is no message in the device to ask me to grant the adb connection. By the weay, the device is already unlocked.
When I tried the manual instructions to flash 12L, during the below command, I get this error message
fastboot flash vendor vendor.img
target reported max download size of 805306368 bytes
sending 'vendor' (650920 KB)...
OKAY [ 16.256s]
writing 'vendor'...
FAILED (remote: Partition not found)
finished. total time: 16.261s"
Also:
fastboot flash system TB-Q706F-DPP_USR_S100039_2111232000_V4.5_DEV_system.img
Invalid sparse file format at header magic
Sending sparse 'system' 1/3 (786344 KB) OKAY [ 19.666s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
I even tried another image from GSI but all have this error message.
Many thanks in advance

famaTV said:
Hello friends,
I ran into the very same problem you had with region lock. The Rescue and Smart Assistant tool ruined the device and I can't boot it anymore. Having this error message "The current system is not compatible …"
I tried going back to at least the 12L Preview but every time I run the script, it doesn't work. The device is not authorized
List of devices attached
HA**** unauthorized
How can I get it authorized from the recovery screen? There is no message in the device to ask me to grant the adb connection. By the weay, the device is already unlocked.
When I tried the manual instructions to flash 12L, during the below command, I get this error message
fastboot flash vendor vendor.img
target reported max download size of 805306368 bytes
sending 'vendor' (650920 KB)...
OKAY [ 16.256s]
writing 'vendor'...
FAILED (remote: Partition not found)
finished. total time: 16.261s"
Also:
fastboot flash system TB-Q706F-DPP_USR_S100039_2111232000_V4.5_DEV_system.img
Invalid sparse file format at header magic
Sending sparse 'system' 1/3 (786344 KB) OKAY [ 19.666s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
I even tried another image from GSI but all have this error message.
Many thanks in advance
Click to expand...
Click to collapse
I hate to break this to you but I couldn't find any way out of this mess. I couldn't find a Chinese ROM to flash back to. I had to send it back to China for repair. Got it back and it was someone else's broken Tablet and had to ship it off again. Its turned into a right old saga. Where did you purchase yours?

mardon85 said:
I hate to break this to you but I couldn't find any way out of this mess. I couldn't find a Chinese ROM to flash back to. I had to send it back to China for repair. Got it back and it was someone else's broken Tablet and had to ship it off again. Its turned into a right old saga. Where did you purchase yours?
Click to expand...
Click to collapse
I bought it from Lenovo Global Store in Aliexpress. I already contacted the seller and they mentioned that they will check best solution and get back to me. I will update everyone accordingly.
Still wondering how come I can't flash the 12L or any GSI roms because of the vendor.img strange partition error. Anyone else with more guidance is truly appreciated.
Here is the store I bought it from:
https://www.aliexpress.com/item/1005003607767936.html?spm=a2g0s.12269583.0.0.e0e96cdfCpFMz5
UPDATE: Two new things I learned. When things seems not working, open a new CMD window and start working. Sometimes fastbootd won't activate. Make sure you have "fastbootd" text showing on the top of the screen to be able to proceed with vendor.img and system.img without the partition issues. Also, 12L system.img didn't work. I tried a couple of them and was so successful to flash lineage-19.0-20211216-UNOFFICIAL-treble_arm64_bgS.img image. Finally I got the tab running with LoS image. At least it's not bricked hopefully. Will update everyone once the tab retailer answers me (I hope he will manage to get a CN backup rom to use). Thanks
UPDATE2: There is an annoying continuous notification stating "The device isn't Play Protect certified" Not sure how to get this solved, but I slienced it anyway. However, can't get it to work. Playstore won't open.
UPDATE3: I managed to install PixelExperience_arm64-ab-12.0-20211226-UNOFFICIAL.img without any problems with Magisk. I am exploring it now and shall share my feedback later on. So far, no major issues.

famaTV said:
I bought it from Lenovo Global Store in Aliexpress. I already contacted the seller and they mentioned that they will check best solution and get back to me. I will update everyone accordingly.
Still wondering how come I can't flash the 12L or any GSI roms because of the vendor.img strange partition error. Anyone else with more guidance is truly appreciated.
Here is the store I bought it from:
https://www.aliexpress.com/item/1005003607767936.html?spm=a2g0s.12269583.0.0.e0e96cdfCpFMz5
UPDATE: Two new things I learned. When things seems not working, open a new CMD window and start working. Sometimes fastbootd won't activate. Make sure you have "fastbootd" text showing on the top of the screen to be able to proceed with vendor.img and system.img without the partition issues. Also, 12L system.img didn't work. I tried a couple of them and was so successful to flash lineage-19.0-20211216-UNOFFICIAL-treble_arm64_bgS.img image. Finally I got the tab running with LoS image. At least it's not bricked hopefully. Will update everyone once the tab retailer answers me (I hope he will manage to get a CN backup rom to use). Thanks
UPDATE2: There is an annoying continuous notification stating "The device isn't Play Protect certified" Not sure how to get this solved, but I slienced it anyway.
Click to expand...
Click to collapse
Good luck getting a Chinese ROM. If you manage it there will be many happy people.
I'm going to ask reseller to flash Global rom on mine. I wish someone would make a guide or share the exact process on how to do it correctly.

famaTV said:
I bought it from Lenovo Global Store in Aliexpress. I already contacted the seller and they mentioned that they will check best solution and get back to me. I will update everyone accordingly.
Still wondering how come I can't flash the 12L or any GSI roms because of the vendor.img strange partition error. Anyone else with more guidance is truly appreciated.
Here is the store I bought it from:
https://www.aliexpress.com/item/1005003607767936.html?spm=a2g0s.12269583.0.0.e0e96cdfCpFMz5
UPDATE: Two new things I learned. When things seems not working, open a new CMD window and start working. Sometimes fastbootd won't activate. Make sure you have "fastbootd" text showing on the top of the screen to be able to proceed with vendor.img and system.img without the partition issues. Also, 12L system.img didn't work. I tried a couple of them and was so successful to flash lineage-19.0-20211216-UNOFFICIAL-treble_arm64_bgS.img image. Finally I got the tab running with LoS image. At least it's not bricked hopefully. Will update everyone once the tab retailer answers me (I hope he will manage to get a CN backup rom to use). Thanks
UPDATE2: There is an annoying continuous notification stating "The device isn't Play Protect certified" Not sure how to get this solved, but I slienced it anyway. However, can't get it to work. Playstore won't open.
UPDATE3: I managed to install PixelExperience_arm64-ab-12.0-20211226-UNOFFICIAL.img without any problems with Magisk. I am exploring it now and shall share my feedback later on. So far, no major issues.
Click to expand...
Click to collapse
As for "The device isn't Play Protect certified" aka uncertified device, you need to manually register the device with Google otherwise you won't be able to log in your Google account.
However, that didn't work for me so I used NanoDroid (for microG and modded IAP-capable Play Store) instead. Maybe you need to wait much longer for device registration to take effect so you could log in.

LSS4181 said:
As for "The device isn't Play Protect certified" aka uncertified device, you need to manually register the device with Google otherwise you won't be able to log in your Google account.
However, that didn't work for me so I used NanoDroid (for microG and modded IAP-capable Play Store) instead. Maybe you need to wait much longer for device registration to take effect so you could log in.
Click to expand...
Click to collapse
Hello!
Thanks … Good to know.
The PixelExperience Android 12 works without any issues so far and I am happy with the experience of the rom.

famaTV said:
Hello!
Thanks … Good to know.
The PixelExperience Android 12 works without any issues so far and I am happy with the experience of the rom.
Click to expand...
Click to collapse
Nice to know. Does anything not work?

mardon85 said:
Nice to know. Does anything not work?
Click to expand...
Click to collapse
I haven't noticed anything not working (yet). Overall the performance is so smooth, camera, gps, fingerprint, gestures, gaming, videos are all working fine. Pen is working however, buttons are not functioning (registered) due to missing app. I wish desktop mode is included. Split screen / flexible screen experience could be improved compared to the stock version.
I have two devices, one with PixelExperience installed and another with stock Chinese ROM. The GSI seems to be smoother as Chinese ROM tends to lag sometimes (not sure why). The them of the stock rom is so refreshing and polished compared the GSI version. But I won't mind it. I am giving it a couple more weeks before changing the 2nd device to PixelExperience (and hopefully by then, the Aliexpress seller comes back with a backup solution to revert back to Global Rom / Chinese Rom).
Thanks again for your valuable help.

I super messed up, need suggestions. [I fixed it like the chad I am :) ]

Cant flash twrp nor the patched magisk boot img to both slot a and b.
Bootloader is unlocked.
Flashing scripts via .bat files for stock zips of both android 10 and 12 results in "FAILED (remote: Partition product not found)" or "FAILED (remote: variable not found)" respectively.
I have no recovery.
When I had twrp, I've made the mistake of wiping my whole android 12 data, storage, and system and flashing an android 10 rom without reading up of the separate a and b boot slots nor the effects of my actions leading to bootlooping. (I've done with this other devices before with no problems). This in turn wiped the twrp recovery I had flashed and left me only fastboot commands and a twrp version up to 3.3 and 3.2 with no hope of getting usb otg to work as it was only available with the later versions of twrp and since I and now technically on an android 10 bootloader, any attempt at that time to flash twrp 3.6 was met with a (remote: Error calling AvbLoadAndVerifyBootImages Load Error) or some kind of other error I have no logs for. Now I cant even tetherboot to twrp 3.2 nor 3.3 and I get that error regardless.
[Boots to bootloader no matter what. Shows as UFS:Micron, Error reason - reboot bootloader - bootloader version is b1c1-0-4-7617406]
I believe I can get access to internal storage to flash these updates once I get a recovery tethered from the bootloader. I do not know if its possible to boot to fastbootd or whatever its called (used for write permissions/sideload update zips) even if I hadn't gotten into this predicament. I will be buying another Pixel 3 in the meantime as I have money to burn and like to hurt myself financially, and emotionally to get to my goal with this device. ( Didn't buy another one, I was committed to the cause!)
I am not a noob nor a pro, but somewhere in between. My biggest point of failure is not reading up on how the partitions are set up and the various issues others had when flashing android 10 and 11 roms. Any suggestions other than "uPdAtE tHe fAsTbOoT aNd AdB dRiVeRs" are not welcomed. Thank you. I will update once I find a soluton to my problem Which I Will.
Again, my main concern right now is getting tethered twrp to work again and need suggestions. I have older versions of platform tools and the latest so please non of those comments I see on literally every other thread.
Edit: I didn't mention this before, but I did have the ability yo sideload when I had twrp at the time before crapping everything out the window, but nothing would work and gave up. Just wanted to add if anyone was wondering.

First update, I used the propriatary "Tool All In One Tool" and I was able to boot to fastbootd, and wipe my data and storage, while updating my stock zip to android 12. Now I can tetherboot twrp 3.6.1_11-0 with the option for usb otg, wish me luck boys. I'm in.

Second update. Still stuck on first update, but weighing my options in the meantime. I flashed twrp via the flash current twrp option, but when I boot to it, touch is disabled so thats great... I can fast boot to only the twrp versions after 3.6+, so not so bad. I have no os installed, but I will try my hand again at that tool all in one tool again. I'll update tomorrow if anything comes of it.

3rd update. FROM THE BRINK OF DEATH!!! WHOOOOOOOOOO!!!!! I got the pixeldust rom flashed and working like a BOSS!!!!! You won't believe the 2 days I've had trying to get this thing to work. All in all 1 out of my 3 flashdrives finally worked with otg. I had a windows recovery drive premade on it so I just copied and pasted the files there without a hitch! Thank you Google for having to make me miss work and actually do research to get this thing working again! Thank you for the guys at Tool All In One Tool for making this recovery possible, I will shout out your thread. If anyone who's in a similar situation needs any help from me or any info, I'll be glad to help. This will be the second to last update. I can also make phone calls and use data so Pixel Dust rom is good to go if that was one of your concerns. See ya!

Final update, I got crdroid flashed with root and safetynet passed, I just found out that google Pay was imbedded in gapps so now I don't need the pay app anymore to do transactions! My banking app also works, got vanced finally installed (couldn't do it on regular stock ROM) some glitches with the ROM here and there but no worries. For who ever reads this. There's hope. I fd up as bad as you can get shy of a hard brick. I still don't know too much but learned near twice as much as I knew just a few days ago. If you need help just DM me and I'll work my hardest to bring the light. This phone is absolutely amazing and on god wished google was a better company to praise. I have more plans for these phones and hope more Roms come out to support it.
I have one question however, how do I make a backup of my system/system_ext partitions? I can make a back up of everything else but that with these two Roms... I have a backup of it with my stock ROM, but it resumed to mount when I used otg... Didn't try internal yet but I'll assume the same, is it a glitch with current twrp?