Related
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.
OK,
I have posted this within another thread but have decided to start anew as other threads seem to be resolved after Rom has flashed because of changes made in the update script dealing with bootloader version. My issue is after the Rom has flashed and apologize if I missed it but have not at least seen another thread with the same issue or complaint so will once again apologize if I am not correct but my issue is or do not beleive is related to the update.
e script bootloader insertion.
Also a bit lazy in that although I will do research have come to trust advice from xda members who may reply so all and all like knowing that whatever I may find may be backed up here as opposed to spending and wasting limited time searching down the wrong rabbit hole looking for resolutions so with that said below is what I wrote on another thread whose creators issue seemed resolved after moving past the errors received in the process of flashing.
I have had a few issues with latest versions of CM.
First was errors received during the flash process. Was able to get past this a number of ways.
Change bootloader version in update script.
removed bootloader version check line altogether from the script .
Edit line in source for my current bootloader and compiling myself.
This was all find and dandy but with every one of the above mentioned changes to either flash an official nightly or one compiled myself after flashing has gone through without error I am stuck on the "Google" logo after rebooting into system. Have done a quick search and have seen a number of posts like the one mentioned above that after getting past flash errors by modifying update script or in the above case had probably worked because older script was from an update.zip created before the bootloader check had been added by CM after the flash was successful no additional issues had been experienced.
So far I have tried a number of different update.zip's from flashing a number of official nightly zips to compiling my own nightly and even going back and flashing older CM-12 versions either still on SD card or PC that I have flashed in the past without issue and depending on age flash currently without any bootloader version edits as had been created or downloaded before the check had been added and still nothing will go past the "Google" logo.
"
Have also changed versions of TWRP and at one point had seen two versions with one for caf that I do not see as I no longer see any versions on the TWRP website just link to install the TWRP Manager app but in my quick reads had seen that it had only addressed the bootloader issue but now not sure as it had disappeared once I returned for more info and to download.
I do not have any problems installing AOSP Roms as compiled, flashed and running 5.1.0 "LMY47I" for a few days now and have no issue in restoring cm12 created nandroids even though flashing the zip from which the nandroid was created results in a permanent stop on the "Google" logo the nandroid restores and boots up just fine. Also had yesterday gave cm another try as had seen a commit in hammerhead device listing my current bootloader and "LMY41I" Build Number but still "Google" logo.
Should also probably mention I fastboot flashed the image for first "LMY47D" image and then later the "LMY47I" images. After each image flash would first thing fastboot flash twrp and create a nandroid backup before doing anything but would then flash supersu reboot system and set up everything before creating a second nandroid of each. Not sure how this would effect my current cm issue but thought worth noting because am obviously confused so what I think may be related in any way can be thrown out the window . Otherwise have not seen anything helpful in researching and have even considered flashing the bootloader taken from the 5.0.1 factory image as problems began after flashing 5.1.0 "LMY47D" factory image.
One last tidbit is I have tried booting into cm after flashing both with gapps and without in the case maybe something in the gapps packages I have is screwing with things preventing from booting past the "Google" Logo
tl;dr - TWRP touch screen won't work after installing custom ROM, much hassle to unbrick, looking for a "bumped" (still not actually sure what that term means) or otherwise modified version of TWRP that won't go haywire when installing a custom ROM.
tl;dr 2 - Also interested in the LATEST "stock-based" ROM recommendations anyone may have... G3 backports or whatever. She needs her Camera to work well but older 4.4.x and 5.0.x OS is missing a lot of new functionality and compatibility with new apps.
I'll just start out by saying that I've figured out just about every way to brick and subsequently un-brick this device that is feasibly possible, and am considering starting a thread specific to those various methods... but that's not what this is for.
This is an issue I've encountered a few times now, definitely on my girlfriend's T-Mobile LG G2 D801 with Lollipop (30B and now again on D801 30C), and iirc, also on KitKat.
I'll explain what I can remember, most of this has been done in the middle of the night after many frustrating hours of attempting various methods... I have to say, this phone has been much more difficult to mod compared to my previous experiences with Samsung and Nexus devices.
I had gotten this device all the way through to CM12 or 13 a year or so ago but recent issues made us decide to attempt to revert back to a Stock-based ROM.
Steps:
1. Root (ioroot / Autorec, can't remember which or for what reason, I have multiple versions of each)
2. Install TWRP Custom Recovery (most recently and successfully using a modified version of the "30B Freedom Tool", although I haven't tried that on 30C - yet.
3. Transfer custom ROM & Kernel to SDCard.
4. Boot into TWRP and install custom ROM & Kernel - most recently GoogleEdition 1.5 and then DorimanX 12.0 Kernel
5. Clear Cache / DALVIK Cache.
6. Reboot device. This is where the trouble begins...
Results: Won't boot into OS at all, instead I end up at the text-based "fastboot" screen, which after multiple tries I can eventually get back into TWRP or into Download Mode.
Once in TWRP after installing custom ROM, the bottom ~1" of the screen won't respond and all other touches aren't accurate... playing with it, I can usually eventually get into some of the TWRP screens, but for most purposes it's about useless.
I managed to restore a backup of the original 30B system image via command line over MTP using ADP TWRP commands, but that bricked the phone in an entirely separate manner where I couldn't access Recovery anymore and the system wouldn't boot at all... I ended up using the LG Update tool to get it up to 30C, and was surprised to find that it still had the restored backup data (apps, pictures, settings, etc), and the phone is now working again, albeit back to stock recovery.
Now, as I mentioned, this isn't the first time I've run into this "phantom touch" issue in TWRP on this device, although the circumstances seem to be a little backwards this time vs when I was taking the device over to CM12/13. I think I remember something about a "bumped" or otherwise modified version of TWRP being out there, but I can't find it now or put my finger on what the changes were.
Has anyone else run into this? I am hoping I've just overlooked something, but days of digging through threads hasn't turned up much.
/edit/ To give you an idea, attached is the folder I've got files stored in... with tons more in Archive and Stock-Based... I've used them ALL at some point. I'd like to get enough info in here to write a Step by Step guide for new owners who are picking these devices up on the cheap, and would appreciate if anyone wants to help out with this!
I have the Google Fi Android One X4 XT1900-1, and I made the mistake of trying out Lineage OS, which was great on my last couple phones but a bit underwhelming here. So I wanted to go back to stock. I tried following the threads here and here (just the return-to-stock part, not the Pie update), using the Linux shell script. And everything worked great! EXCEPT! Neither the WiFi nor the SIM card are working. I tried using the firmware from Motorola-Firmware-Team on Android File Host that were marked as Fi, both the most recent and a few versions back. And everything works except the modems.
Any suggestions? I don't really want to be stuck with this meh version of Lineage.
https://mirrors.lolinet.com/firmware/moto/payton/official/FI/
Flash the latest release (XT1900-1_PAYTON_FI_9.0_PPW29.69-39-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip) with your shell script, I guess you flashed stock oreo instead of pie and going back to oreo with pie modem is not a good idea
First, I didn't realize there was a Q&A-specific subforum, admin please feel free to move this thread there!
I gave it a try with the version of the firmware you suggested (I thought since it'd shipped with Oreo and gotten Pie OTA the Oreo one might be better, that's why I was trying that first), but still no luck even with the latest Pie. Maybe there's a problem with the version of the flash-all.sh I'm using? Here's the contents of it, leaving out the AOSP license text:
Code:
#!/bin/sh
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
sleep 9
fastboot --set-active=a
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth_a BTFM.bin
fastboot flash dsp_a dspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_b system_other.img
fastboot flash oem_a oem.img
fastboot erase carrier
fastboot erase userdata
fastboot erase ddr
fastboot reboot
Maybe there's something missing, or something I should take out?
It wouldn't help. I have the same issue. I did try reflash with different Roms, Android,firmware.. Everything looks the same. no cellular service, WiFi at all. Imei/WiFi mac address broken.
Next what I want to do to write correct Imei separately..
trixter42 said:
First, I didn't realize there was a Q&A-specific subforum, admin please feel free to move this thread there!
I gave it a try with the version of the firmware you suggested (I thought since it'd shipped with Oreo and gotten Pie OTA the Oreo one might be better, that's why I was trying that first), but still no luck even with the latest Pie. Maybe there's a problem with the version of the flash-all.sh I'm using? Here's the contents of it, leaving out the AOSP license text:
Maybe there's something missing, or something I should take out?
Click to expand...
Click to collapse
ElijahUSA said:
It wouldn't help. I have the same issue. I did try reflash with different Roms, Android,firmware.. Everything looks the same. no cellular service, WiFi at all. Imei/WiFi mac address broken.
Next what I want to do to write correct Imei separately..
Click to expand...
Click to collapse
I imagine you guys did NOT backup your EFS partition in twrp?
I've personally been lucky and never have killed this partition but it's been my understanding that immediately after you install twrp on any device you should backup this partition before installing roms/firmware..
I go the extra yard and save the backup to my PC...
I'd try googling around terms like efs corruption / restore
SyberHexen said:
I imagine you guys did NOT backup your EFS partition in twrp?
I've personally been lucky and never have killed this partition but it's been my understanding that immediately after you install twrp on any device you should backup this partition before installing roms/firmware..
I go the extra yard and save the backup to my PC...
I'd try googling around terms like efs corruption / restore
Click to expand...
Click to collapse
I can look into that, but would Lineage OS still work just fine if that was the case? Because Lineage OS works just fine except for a couple missing features. The modem works on that, no problem. I'd just prefer to use the stock firmware, and that's where I run into problems.
Sorry, my last three phones were a Nexus 4, a Nexus 5, and a Nextbit Robin, so I'm not used to a phone being this difficult to work with.
trixter42 said:
I can look into that, but would Lineage OS still work just fine if that was the case? Because Lineage OS works just fine except for a couple missing features. The modem works on that, no problem. I'd just prefer to use the stock firmware, and that's where I run into problems.
Sorry, my last three phones were a Nexus 4, a Nexus 5, and a Nextbit Robin, so I'm not used to a phone being this difficult to work with.
Click to expand...
Click to collapse
That is strange that it's working in roms.
Did you format userdata before going back to stock?
This was recommended when going to custom ROMs.
Might be relavent in reverse.
Another idea is try one of my firmware only zips.
You can find it in the havoc os thread,
first post near the install instructions
SyberHexen said:
That is strange that it's working in roms.
Did you format userdata before going back to stock?
This was recommended when going to custom ROMs.
Might be relavent in reverse.
Another idea is try one of my firmware only zips.
You can find it in the havoc os thread,
first post near the install instructions
Click to expand...
Click to collapse
Still having trouble...
I did format everything in TWRP before flashing it. I've tried this a bunch of times, in a bunch of different variations, but I've made sure not to carry Lineage data over into the stock ROM.
I tried flashing the Pie Fi stock from lolinet and then flashing your Pie Fi firmware, but then it just bootlooped. I tried it with the retail firmware too, just in case it was some weird rebranded old stock thing, but the same thing happened. It was a good thing to try, though!
Ultimately, the stock ROM just isn't reading my IMEI for some reason, even though Lineage sees it just fine. I do have my IMEI, is there a way to enter it into the stock ROM manually? I've also been playing around with the official Moto tools over in Windows, but no luck there either.
I really appreciate all the suggestions though!
I'm hitting the exact same problem. I have a Google Fi variant, went to Lineage to try it out, tried to revert to stock, and wireless and radio are not working. I followed the guide at https://forum.xda-developers.com/moto-x4/development/rom-lineage-os-15-1-t3802265, but accidentally skipped the step to install "Copy Partitions Zip". I've been trying to figure out what that file does, but haven't made much progress. I don't know if it's related or not to stock not working.
I lost all data/wifi/cell service after doing a clean flash of the April update. During the setup phase of the initial flash, I had no 4G, device was failing to acknowledge that I even had a SIM card inserted. Wifi was so intermittent that I couldn't enter my password to restore my Google account to the device. After this I tried out numerous stock flashes of the earlier Pie factory firmwares, LineageOS, HavocOS, none of them having any success..
After getting in a bootloop trying to restore the full backup I made right after unlocking my bootloader, I decided to again do a factory firmware flash of the April update and only restore the backups I made of the EFS and Persist partitions, at the initial boot, that didn't seem to work. I decided to go ahead and proceeded with my normal routine of flashing TWRP and the latest Magisk. Thought maybe a Magisk module could kickstart service. Booting after that, I finally had both Wifi and 4G LTE w/ voLTE on Total Wireless again.
Definitely a pain, especially the full backup I had made turning out to be a waste of time.
Just backup your EFS/Persist partitions. Lenovorola's gross mishandling of the EFS partition on nearly every recent device makes this step nearly vital before doing anything to the phone.
Is there any progress towards a solution on this? I experienced this for the first time while trying to re-flash stock April ROM.
Can the same EFS and Persist partitions interchangeable, as in can I use yours? I've been using the re-flash stock, accept OTAs, re-root/twrp method for months now and this is the first time this has happened. Its only bluetooth capable right now. lol
Ok, after more hours... I re-flashed the base 9.0 stock rom (PAYTON_FI_9.0_PPW29.69-26), then re-flash up to current (PAYTON_FI_PPWS29.69-39-2-1_May2019). SIM/WiFi services have returned. I might need to update the FAQs thread with this knowledge but honestly not sure what was the main solution to the troubles.
hxxps://mirrors.lolinet.com/firmware/moto/payton/official/FI/XT1900-1_PAYTON_FI_9.0_PPWS29.69-39-2-3_subsidy-DEFAULT_regulatory-DEFAULT_NO_ERASE_MODEM_CFC.xml.zip
The latest July 1 2019 Security patch is available for download. I wonder if the "NO_ERASE_MODEM" in the name is to signify that this update is able to be installed by everyone without the possibility of the update screwing up the phone if installed? Pretty pathetic that we have to deal with an issue like this, even when taking careful measures to not destroy our phones, Google/Lenovorola allow an official update release with that exact capability regardless of whether the user has modified their handset.
Neffy27 said:
Ok, after more hours... I re-flashed the base 9.0 stock rom (PAYTON_FI_9.0_PPW29.69-26), then re-flash up to current (PAYTON_FI_PPWS29.69-39-2-1_May2019). SIM/WiFi services have returned. I might need to update the FAQs thread with this knowledge but honestly not sure what was the main solution to the troubles.
Click to expand...
Click to collapse
That's what perplexes me. It seemed completely random both the loss of and reintroduction of network services to those that it affected. In my case rooting with Magisk restored services, which for all intents and purposes is a terrible answer to give the common user. With that said, in some cases simply installing an official update on an unmodified bootloader locked phone could destroy network services for a select few very unlucky people.
But some good news, I have been running with the latest update applied. I flashed the May 1 update, and let it update to the July 1 update then factory reset the device, installed Magisk/TWRP and have been getting excellent performance, still no ZRAM crashing issues as with the April 1 (I think) update, and close to 5 hours of SOT with ~70% brightness, Bluetooth, Mobile Radio and nothing disabled sync-wise (Gmail/Hangouts/Facebook/Google News/Weather etc.).
Even with spotty support, this is easily the best handset I have ever used. It may be the best after my weekend lake excursion where it was submerged in my pocket for about 45 total minutes over the span of 4 hours with a couple of quick rinses in the sink to scare my family, none of which have IP certified phones.
NeoandGeo said:
hxxps://mirrors.lolinet.com/firmware/moto/payton/official/FI/XT1900-1_PAYTON_FI_9.0_PPWS29.69-39-2-3_subsidy-DEFAULT_regulatory-DEFAULT_NO_ERASE_MODEM_CFC.xml.zip
The latest July 1 2019 Security patch is available for download. I wonder if the "NO_ERASE_MODEM" in the name is to signify that this update is able to be installed by everyone without the possibility of the update screwing up the phone if installed? Pretty pathetic that we have to deal with an issue like this, even when taking careful measures to not destroy our phones, Google/Lenovorola allow an official update release with that exact capability regardless of whether the user has modified their handset.
That's what perplexes me. It seemed completely random both the loss of and reintroduction of network services to those that it affected. In my case rooting with Magisk restored services, which for all intents and purposes is a terrible answer to give the common user. With that said, in some cases simply installing an official update on an unmodified bootloader locked phone could destroy network services for a select few very unlucky people.
But some good news, I have been running with the latest update applied. I flashed the May 1 update, and let it update to the July 1 update then factory reset the device, installed Magisk/TWRP and have been getting excellent performance, still no ZRAM crashing issues as with the April 1 (I think) update, and close to 5 hours of SOT with ~70% brightness, Bluetooth, Mobile Radio and nothing disabled sync-wise (Gmail/Hangouts/Facebook/Google News/Weather etc.).
Even with spotty support, this is easily the best handset I have ever used. It may be the best after my weekend lake excursion where it was submerged in my pocket for about 45 total minutes over the span of 4 hours with a couple of quick rinses in the sink to scare my family, none of which have IP certified phones.
Click to expand...
Click to collapse
Any chance you can run me through the order in which I can get my service/Wi-Fi back? Or how to correctly root via TRWP/Majisk? Lol. I tried rooting last week... And managed to miss something.. not sure. But after doing it, the phone wouldn't boot. Kept restarting. So I said he'll with it and found the stock rom and flashed it back. Works fine except it doesn't recognize sim or Wi-Fi. So temporarily, I'm using, what I believe to be the most ridiculously slow "newer phone" ever made... At&t Axia. I'm dead without my x4. Could really use some insight
JustDJ_From_Da_Swamp said:
Any chance you can run me through the order in which I can get my service/Wi-Fi back? Or how to correctly root via TRWP/Majisk? Lol. I tried rooting last week... And managed to miss something.. not sure. But after doing it, the phone wouldn't boot. Kept restarting. So I said he'll with it and found the stock rom and flashed it back. Works fine except it doesn't recognize sim or Wi-Fi. So temporarily, I'm using, what I believe to be the most ridiculously slow "newer phone" ever made... At&t Axia. I'm dead without my x4. Could really use some insight
Click to expand...
Click to collapse
Do you have bootloader unlocked? If yes, just flash latest fastboot ROM (29.69-39-2-3 for XT1900-1), boot to TWRP "fastboot boot twrp.img" and flash latest Magisk. SIM/WiFi will be back.
Comby_sk said:
Do you have bootloader unlocked? If yes, just flash latest fastboot ROM (29.69-39-2-3 for XT1900-1), boot to TWRP "fastboot boot twrp.img" and flash latest Magisk. SIM/WiFi will be back.
Click to expand...
Click to collapse
Awesome, I'll try it now. I greatly appreciate that
---------- Post added at 02:16 PM ---------- Previous post was at 01:39 PM ----------
Hey.. umm.. where can I find that new ROM?.. lol I know, it's a shame
I managed to pull it off. Reflashed the stock ROM you suggested, then TWRP/Magisk. She's rooted and running..WITH CELL SERVICE! ?...now I'm seeing how I can mess it up again. I'm pretty green at all this, but I've always been intrigued. I was thinking about Lineage OS 16...but seems to have some issues that are above my intelligence. So I guess I need to take my old @$$ to bed before I mess up a good phone..again. Can't thank ya enough for the help
JustDJ_From_Da_Swamp said:
I managed to pull it off. Reflashed the stock ROM you suggested, then TWRP/Magisk. She's rooted and running..WITH CELL SERVICE! ...now I'm seeing how I can mess it up again. I'm pretty green at all this, but I've always been intrigued. I was thinking about Lineage OS 16...but seems to have some issues that are above my intelligence. So I guess I need to take my old @$$ to bed before I mess up a good phone..again. Can't thank ya enough for the help
Click to expand...
Click to collapse
Glad you got your problem sorted out. Honestly the best ROM for this device has always been Plain Stock w/ Magisk for root. Everything just seems to work without issues, all of the custom ROMs have the odd issue here and there that really prevents the device from being able to be run trouble free.
same problem on 1900-7 version
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.