Pixel (sailfish) bootloop (blackscreen after logo) - Google Pixel Questions & Answers

Ok, so I bought a used Pixel and it just blackscreens and bootloops after the Google logo. I can access bootloader/recovery mode and flash firmware, but whatever I do, it won't go past the logo. Seems like a hardware defect to me, anything I can do myself?

Try to install stock boot.img

Song0329 said:
Try to install stock boot.img
Click to expand...
Click to collapse
Like I said, can still get into recovery and bootloader, so I've tried flashing all official firmwares form 7 to 10, Lineage OS and PixelDust to no avail.

Velcorn said:
Like I said, can still get into recovery and bootloader, so I've tried flashing all official firmwares form 7 to 10, Lineage OS and PixelDust to no avail.
Click to expand...
Click to collapse
Try clean flash:
1. Download twrp.img
2. Fastboot boot twrp.img
3. Wipe advance,check all except sdcard and otg
4. Reboot recovery
5. Install stock rom
If still bootloop...smash your android to the ground :laugh:

Song0329 said:
Try clean flash:
1. Download twrp.img
2. Fastboot boot twrp.img
3. Wipe advance,check all except sdcard and otg
4. Reboot recovery
5. Install stock rom
If still bootloop...smash your android to the ground :laugh:
Click to expand...
Click to collapse
Tried all of it multiple times. I'll probably take the last advice
Edit: Not giving up on this device yet. Got it to boot Lineage 18.0 and managed to complete the setup. Still freezes up after 30-60 seconds though. Here are screens of the setting and BL info:

Velcorn said:
Tried all of it multiple times. I'll probably take the last advice
Edit: Not giving up on this device yet. Got it to boot Lineage 18.0 and managed to complete the setup. Still freezes up after 30-60 seconds though. Here are screens of the setting and BL info:
Click to expand...
Click to collapse
mine is doing the exact same thing. did you fix it?

i think thats hardware defect, mine doing aswell. dont know what to do.
cant boot to main screen, cant go to recovery mode, locked status. doom

BakolteLo said:
i think thats hardware defect, mine doing aswell. dont know what to do.
cant boot to main screen, cant go to recovery mode, locked status. doom
Click to expand...
Click to collapse
Mine keeps going into a boot loop. after flashing so many OTAs and factory images I was able to get it to boot on 7.1 nougat. Knowing me I can't leave well enough alone I decided to fast boot boot twrp. Once again boot loop. Now when I boot it it says writing to ext4. Ugh

Does anyone know if a 32 GB motherboard would fit in the 128 GB frame?

I had bought a used Pixel (sailfish) back in October of 2020 and it was perfectly fine until November where it ran into the bootloop problem. I had tried various things but what worked for me was disabling the 3rd and 4th cores of the processor.
I have read that the Nexus 6p and 5x had this problem where the heavy Snapdragon cores of these models (5th and 6th, being hexa-cores) were causing the bootloop and disabling them avoided the problem.
I haven't heard of this problem as far as the 1st gen Pixels are concerned but tried it anyway. Short story is that I had to download the factory images from google, modify the boot.img (using an application in linux, had to install ubuntu in my windows 10 laptop). Setting maxcpus=1 and boot_cpus=0 yielded the best result (in terms of not running into a bootloop), though maxcpus=2 and boot_cpus=0-1 also was a fairly stable setup. Since then I've been using the Pixel, mainly for the camera, but even with the dual-core setup, performance has taken a significant decline (shots would take several seconds, sometimes > 10s in HDR+ on) but for the price, definitely workable. No bootloops nor restarts since.
Perhaps try this if you're out of options. Best of luck.

gengriffron2 said:
I had bought a used Pixel (sailfish) back in October of 2020 and it was perfectly fine until November where it ran into the bootloop problem. I had tried various things but what worked for me was disabling the 3rd and 4th cores of the processor.
I have read that the Nexus 6p and 5x had this problem where the heavy Snapdragon cores of these models (5th and 6th, being hexa-cores) were causing the bootloop and disabling them avoided the problem.
I haven't heard of this problem as far as the 1st gen Pixels are concerned but tried it anyway. Short story is that I had to download the factory images from google, modify the boot.img (using an application in linux, had to install ubuntu in my windows 10 laptop). Setting maxcpus=1 and boot_cpus=0 yielded the best result (in terms of not running into a bootloop), though maxcpus=2 and boot_cpus=0-1 also was a fairly stable setup. Since then I've been using the Pixel, mainly for the camera, but even with the dual-core setup, performance has taken a significant decline (shots would take several seconds, sometimes > 10s in HDR+ on) but for the price, definitely workable. No bootloops nor restarts since.
Perhaps try this if you're out of options. Best of luck.
Click to expand...
Click to collapse
Hey, I'd love to try this; any chance you have a more in-depth guide on how to modify the boot image? What application to use, etc.?
EDIT: Through some extensive googling came across this guide which explains how to do this for the G4. So I just downloaded the latest marlin factory image, extracted the boot image from that, and followed the steps.
If you're on Win10/11 you can install WSL2 and via the Ubuntu distro get abootimg via
Code:
sudo apt install abootimg
Then copy the boot.img file to your ubuntu distro's home folder and run
Code:
abootimg -i boot.img
Copy the entire cmdline from the output and simply append
Code:
maxcpus=1 boot_cpus=0
to the start of the parameters, then run
Code:
abootimg -u boot.img -c "<cmdline>"
where <cmdline> is your edited cmdline output.
For me (Marlin, latest A10 image) that was
Code:
abootimg -u boot.img -c "cmdline = maxcpus=1 boot_cpus=0 console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=marlin user_debug=31 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 [email protected] loop.max_part=7 buildvariant=user veritykeyid=id:34e81e2c57675086f628c1b2e4b4ade8e0a1941d"
Then it'll write to the same boot.img file with which you can try
Code:
fastboot boot boot.img
with the Pixel XL in fastboot mode to see if it'll work. I haven't tested the boot image yet, will report back here if it works.

Related

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.

guid to flash Treble GSI on Nokia 6 (2018)

tested on ta-1054.
WHY flash ?
nokia system use 2GB memory after boot. there's lots of things auto start. if you try to disable it ,some app else will crash sometime.
in chinese version, there's some spy action in the system apps. for example:
you'll find a folder called "baidu" in /storage/emulated/0/. in the folder,there's some files used to trace your action. but you never installed any app. this is done by a build-in app called weather service.
again, a folder called ".com.nb.filemanager" created by the build-in file manager.
lots of service backend , for example: tencentlocationservice.
in /system/priv-app/cust, there're lots of service only for chinese version. you know what does it mean. and can't be deleted.
treble rom from phh works on my ta-1054. both AOSP and lineageOS works.
it takes only 1.2GB memory when start up. when you install apks, it act fast ,unlike the OEM one ,pause 4seconds more when goes to 90%.
but there's one problem : wifi couldn't be switched on. ------This has been fixed now.
but another problem found. about the calling. when flash the system to slot a, it recognize two sim. both could receive calling.but calling panel will auto quite when calling out. (the other side will ring, but hear nothing when pick up).
when flash the system to slot b, it recognize one sim card only. call and receive ok.
so take your choice, try to go away from rubbish app or not. flash system may brick your phone,take your risk.
HOW TO :
1. unlock your bootloader.
2.backup your things on the phone.
3. fastboot tools. optional: adb tools.
4.download a boot image from https://dospy.wang/forum.php?mod=viewthread&tid=69.
now treble is build on android 8.1, so download B2N-222A-0-00WW-B06-patched-boot.img .
now , i've extracted the stock boot kernal from my nokia 6.1, version android 8.1. use this instead of the former one , the wifi will works.
https://pan.baidu.com/s/1R0ZconptEvAuth5nJt_ekQ
5.download gsi system image :
lineageOS
AOSP [recommend]
important: choose ab one , instead of a only system. choose arm64 instead of arm.
6.turn your phone to download mode.
you may use adb command:
Code:
adb reboot bootloader
or shutdown and hold on volume+ and power key to boot, when a doid picture appear, press these two keys again. then choose reboot to bootloader.
optional: see which slot you are in, a or b:
Code:
fastboot getvar all
check "current sloct:" and remember it. if you faild to start system later, you may go back to fastboot. if you failed to boot ,sometimes the bootloader will load another slot. so, check it. and you could be aware where you are. we flash one slot is enough, two works too.
7. wipe user data,type:
Code:
fastboot -w
8.flash the system image:
Code:
fastboot flash system your-image.img
9.flash the boot image:
Code:
fastboot flash boot B2N-222A-0-00WW-B06-patched-boot.img
tips: if your former system is android 8.1, and you didn't rooted it, then you may skip this step.
10.wipe data again:
Code:
fastboot -w
11.reboot your phone:
Code:
fastboot reboot
ok, you may see lineage os starts up now.
if you want to root your phone, just install magisk.apk, and then add the magisk.zip module. reboot, that's ok.
maybe problem:
fastboot waiting devices.
two reason. 1. your fastboot version . please use the one extracted from android SDK, the one installed by apt install doesn't work. 2. udev rules .add your device ID to /etc/udev/rules.d/51-android.rules.
find your device id by lsusb.
bootloop
if you could enter recovery ,this means boot img ok. try to flash system again. remember to check wich slot you are in. if not the former one, just switch it by "fastboot set_active a/b" a or b choose the currect one.
if you couldn't enter recoery, just flash boot.img again.
This is great an all, but the fundamental issue with all of this is the bootloader unlock. When you say to unlock the bootloader, do you refer to using the paid service to do so?
JBlaze05 said:
This is great an all, but the fundamental issue with all of this is the bootloader unlock. When you say to unlock the bootloader, do you refer to using the paid service to do so?
Click to expand...
Click to collapse
yes, i've paid about 5$ to unlock. I don't know any free way to do it util now. and it's important to do it for me,so i paid.
superium said:
yes, i've paid about 5$ to unlock. I don't know any free way to do it util now. and it's important to do it for me,so i paid.
Click to expand...
Click to collapse
so BL unlocking aside, how smoothly do the GSI's run on this phone compared to the stock rom? Scrolling, fluidity, speed, and whatnot.
JBlaze05 said:
so BL unlocking aside, how smoothly do the GSI's run on this phone compared to the stock rom? Scrolling, fluidity, speed, and whatnot.
Click to expand...
Click to collapse
Good questions!
Good experience :
* it tesk much less time than the stock one when boot.
* It's fast more than the stock one.when start up, it takes about 1.2GB memery, the stock one takes 2GB.
* it's smooth and very pure to use. when installing apps, it's more fast than the stock one. you may notice the stock one will pause several seconds when installing process goes to about 90%.
* there's no so much backround services, like tencentlocationservices, overlay apps for CN ....etc.
* the OTA could recognize all partions when your usb devices have several partitions. the stock one only recognize the first partition.
* the fling navigation is so cool in RRemix and AICP.
Not So Good experience :
* when flash the system to slot a, it recognize two sim. both could receive calling.but calling panel will auto quite when calling out. (the other side will ring, but hear nothing when pick up).
when flash the system to slot b, it recognize one sime only. call and receive ok.
* sms receive will crash the system if you use lineage , RRemix, AICP. Fortunately, the AOSP works good.
* if you use lineageos , scan other blue-tooth devices will crash the system . but transfer files ok.
* if you use lineageos ,AOSP,AICP , you will experience no-response several times. because the Privacy Guard pop toast to ask you allow or deny something, but it freeze the system if it's not the most top app. Fortunately, this will not happen in AOSP because there's no such app.
* when charging in power-off status, can't detect the power percent. (only tested in AOSP)
* compass degree err, all GSI including AOSP.
Additonal
* fly model in the night, about 8 hours. seems lineage and RRemix takes much less power,some version only takes 1%. the AOSP takes about 8%.
* the wifi problem is due to the boot kernal.
now , i've extracted the stock boot kernal from my nokia 6.1, version android 8.1. use this instead of the former one , the wifi will works.
https://pan.baidu.com/s/1R0ZconptEvAuth5nJt_ekQ
superium said:
Good questions!
Good experience :
* it tesk much less time than the stock one when boot.
* It's fast more than the stock one.when start up, it takes about 1.2GB memery, the stock one takes 2GB.
* it's smooth and very pure to use. when installing apps, it's more fast than the stock one. you may notice the stock one will pause several seconds when installing process goes to about 90%.
* there's no so much backround services, like tencentlocationservices, overlay apps for CN ....etc.
* the OTA could recognize all partions when your usb devices have several partitions. the stock one only recognize the first partition.
* the fling navigation is so cool in RRemix and AICP.
Not So Good experience :
* when flash the system to slot a, it recognize two sim. both could receive calling.but calling panel will auto quite when calling out. (the other side will ring, but hear nothing when pick up).
when flash the system to slot b, it recognize one sime only. call and receive ok.
* sms receive will crash the system if you use lineage , RRemix, AICP. Fortunately, the AOSP works good.
* if you use lineageos , scan other blue-tooth devices will crash the system . but transfer files ok.
* if you use lineageos ,AOSP,AICP , you will experience no-response several times. because the Privacy Guard pop toast to ask you allow or deny something, but it freeze the system if it's not the most top app. Fortunately, this will not happen in AOSP because there's no such app.
* when charging in power-off status, can't detect the power percent. (only tested in AOSP)
* compass degree err, all GSI including AOSP.
Additonal
* fly model in the night, about 8 hours. seems lineage and RRemix takes much less power,some version only takes 1%. the AOSP takes about 8%.
* the wifi problem is due to the boot kernal.
now , i've extracted the stock boot kernal from my nokia 6.1, version android 8.1. use this instead of the former one , the wifi will works.
https://pan.baidu.com/s/1R0ZconptEvAuth5nJt_ekQ
Click to expand...
Click to collapse
ok good to hear, i can deal with those cons. ive been wanted to get this phone but i want prices to come down just a bit and i was hoping that the guy who does BL unlocking would publicize his work but oh well. Thanks for the info
I've installed this on the TA-1054 but it says no sim card on both my sim slots. any ideas?
---------- Post added at 03:14 AM ---------- Previous post was at 02:49 AM ----------
I'm getting "No SIM" any ideas?
I have a Nokia ta-1054 with forked firmware so I tried your method. However, I am stuck in powered by Android and I can only enter download mode. I've tried again and again the steps above but I cannot boot normally into android. I've tried different AOSP firmwares, as well as different boot.img, and I cannot enter recovery mode. What can I do?
Metzas said:
I have a Nokia ta-1054 with forked firmware so I tried your method. However, I am stuck in powered by Android and I can only enter download mode. I've tried again and again the steps above but I cannot boot normally into android. I've tried different AOSP firmwares, as well as different boot.img, and I cannot enter recovery mode. What can I do?
Click to expand...
Click to collapse
flash boot file and then fastboot reboot. don't fastboot -w after you flash boot file. this worked for me.
Although the 1054 still cannot recognize my ATT Sim card.
I want to restore my 1054 back to the stock chinese firmware so I can make sure the SIM read error is not a hardware issue but i cannot find the chinese firmware
I also have a TA-1045 USA edition. Is there anyway I can pull the stock image and flash it to my 1054?
Its a paytool for Nokia. Its called ntools they provide and the stock ROMs but is only for these tool
stealthj said:
flash boot file and then fastboot reboot. don't fastboot -w after you flash boot file. this worked for me.
Although the 1054 still cannot recognize my ATT Sim card.
Click to expand...
Click to collapse
Unfortunately that didn't work for me. Is there any other solution or am I stuck with a bricked phone?
Again make sure you are using the correct slots. Then flash, erase userdata, flash boot, fastboot reboot and disconnect USB cable right after pressing enter on fastboot reboot, should reboot into the OS
Anyone try this on TA-1045 yet ?
I have a TA-1050, Does anyone know of the hardware differences between the models and If that would effect the patched boot.img needed? Would it brick if I tried?
TA 1050 supported ?!
this phone is treble enabled by default. not sure why you need to flash a modded boot.img? id flash a rom but there is no way to go back to stock as of now soo ill hold off.
Hi,
Thanks for the guide, however I'm stuck in bootloops no matter which Oreo GSI I'm trying to flash... (Nokia TA-1043, went straight from stock > unlocked bootloader > 8.1 AOSP > stuck on bootanimation)
Solannae said:
Hi,
Thanks for the guide, however I'm stuck in bootloops no matter which Oreo GSI I'm trying to flash... (Nokia TA-1043, went straight from stock > unlocked bootloader > 8.1 AOSP > stuck on bootanimation)
Click to expand...
Click to collapse
Same on TA-1043
Managed to flash back stock firmware using Ntool. My phone's working fine now
After installing TWRP (all version for 1043) phone will stuck either at bootlogo or opens TRWP, but never runs OS.
I don't know how often I reflashed System and Boot, at the moment I flash TWRP, it stops workung. Any ideas?
After some flashing of TWRP it showed a "decrypted message" and internal SD was full of unrecognizable trash-files.

Flashing procedures for Pixel using clean 8.1.0_r38 build

Hi,
I'm looking for clarification on the proper flashing procedure of an unmodified home built version of the 8.1.0_r38 branch for the Pixel. I want to be sure I'm actually doing the flashing correctly.
This image was built on Ubuntu 18 after grabbing the 8.1.0_r38 branch directly from Google along with the correct corresponding Vendor image and driver files. As I said earlier no modifications or customizations were made to the source. It was a straight clean 8.1.0_r38 build.
The flashing procedure I had been using was as follows
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash vendor vendor.img
These are the same steps I've been using since going back years. Here's the reason why I'm seeking verification on the flashing procedures.
Once flashed to the Pixel the device suffers a catastrophic failure running CTS. One module, the CtsAppSecurityHostTestCases module, has a test that causes communication with the device to stop and the device is left in an unusable state because the test put a number lock screen on the device and obviously I don't know the pass code.
I have tried numerous branches of Android 8.0 and 8.1 and they all run into this issue with this module on the Pixel when running CTS.
But the Factory images from Google do not exhibit this issue nor did an OEM Verizon Pixel. They all complete CTS without a problem.
So this is why I'm looking at the builds I'm making as the problem. But I'm not doing anything out of the ordinary with the builds...just a straight source build/ensetup.sh, lunch, and make once I copy the (unzipped files in the) Vendor folder over to the repo.
So that leaves two possibilities as far as I can tell.
Possibility 1: The images that are being built, even though I have got everything I can get from Google for them, are missing something in the driver/vendor area that's tripping up CTS.
Possibility 2: I'm not flashing my images correctly for this device. I started wondering about that when I pulled apart the Factory image for the Pixel to see what it was flashing and how it was flashing it. I'm specifically thinking about system-other.img, which I don't flash. But my understanding of system-other.img is that it's not strictly needed since it's for recovery purposes. So maybe that doesn't matter.
Since trying to eliminate Possibility 1 is all but impossible from where I'm at, I'm attacking Possibility 2. So this is why I'm seeking clarification on what the proper flash procedures are for a clean build of 8.1.0_r38 is on the Pixel.
Thank you for your time.
dswalen said:
Hi,
I'm looking for clarification on the proper flashing procedure of an unmodified home built version of the 8.1.0_r38 branch for the Pixel. I want to be sure I'm actually doing the flashing correctly.
This image was built on Ubuntu 18 after grabbing the 8.1.0_r38 branch directly from Google along with the correct corresponding Vendor image and driver files. As I said earlier no modifications or customizations were made to the source. It was a straight clean 8.1.0_r38 build.
The flashing procedure I had been using was as follows
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash vendor vendor.img
These are the same steps I've been using since going back years. Here's the reason why I'm seeking verification on the flashing procedures.
Once flashed to the Pixel the device suffers a catastrophic failure running CTS. One module, the CtsAppSecurityHostTestCases module, has a test that causes communication with the device to stop and the device is left in an unusable state because the test put a number lock screen on the device and obviously I don't know the pass code.
I have tried numerous branches of Android 8.0 and 8.1 and they all run into this issue with this module on the Pixel when running CTS.
But the Factory images from Google do not exhibit this issue nor did an OEM Verizon Pixel. They all complete CTS without a problem.
So this is why I'm looking at the builds I'm making as the problem. But I'm not doing anything out of the ordinary with the builds...just a straight source build/ensetup.sh, lunch, and make once I copy the (unzipped files in the) Vendor folder over to the repo.
So that leaves two possibilities as far as I can tell.
Possibility 1: The images that are being built, even though I have got everything I can get from Google for them, are missing something in the driver/vendor area that's tripping up CTS.
Possibility 2: I'm not flashing my images correctly for this device. I started wondering about that when I pulled apart the Factory image for the Pixel to see what it was flashing and how it was flashing it. I'm specifically thinking about system-other.img, which I don't flash. But my understanding of system-other.img is that it's not strictly needed since it's for recovery purposes. So maybe that doesn't matter.
Since trying to eliminate Possibility 1 is all but impossible from where I'm at, I'm attacking Possibility 2. So this is why I'm seeking clarification on what the proper flash procedures are for a clean build of 8.1.0_r38 is on the Pixel.
Thank you for your time.
Click to expand...
Click to collapse
You can eliminate possibility 2 by doing this: after you run your lunch command, instead of just running 'make', run 'make otapackage'. This will create a flashable zip, then you can just flash it like so:
Flash the latest factory image
fastboot TWRP
Wipe system, both caches, and data
Flash the zip that was made from 'make otapackage'
Flash twrp
reboot recovery
Flash the vendor image. <- flash the one from this link, just to eliminate problems
flash gapps
reboot
Also, AOSP is very different than Google's factory images (It doesn't include all of googles closed source stuff).
shagbag913 said:
You can eliminate possibility 2 by doing this: after you run your lunch command, instead of just running 'make', run 'make otapackage'. This will create a flashable zip, then you can just flash it like so:
(snip)
Also, AOSP is very different than Google's factory images (It doesn't include all of googles closed source stuff).
Click to expand...
Click to collapse
Thanks. I'll try this but I have a very hard time believing Google would deliberately release source (AOSP) that when compiled blows up its own CTS test. I suppose it's possible but speaking as QA, it would bug the heck out of me if I let my company release something that breaks one of our own tools.
dswalen said:
Thanks. I'll try this but I have a very hard time believing Google would deliberately release source (AOSP) that when compiled blows up its own CTS test. I suppose it's possible but speaking as QA, it would bug the heck out of me if I let my company release something that breaks one of our own tools.
Click to expand...
Click to collapse
It turns out I don't need to do this after all. Android 9's CTS does not display this issue so that means the problem, whatever it is, is either the result of Android 8/8.1s AOSP being deficient in some manner or the Android 8/8.1 CTS test suite being wonky somehow. Either way the problem is not the result of something I was doing wrong since I used the same steps with Android 9 and it didn't display the issue.

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?

Categories

Resources