Database Info

Cannot install custom recovery despite unlocked and rooted device

A warm hello to my dear fellow Xiaomians!
I've been campaigning for Xiaomi phones for quite a while now, successfully convincing several friends of their unbeatable price-perfomance ratio. So far I've received very positive feedback. Unfortunately now that I'm trying to move past MIUI for the first time, it's giving me headaches. I was lucky enough to get a used Mi 4C with an unencrypted bootloader (fastboot oem unlock), but I can't for the life of me figure out how to flash TWRP. fastboot flash recovery always fails due to "size too large", even though the target reported max download size is around 760MB (given in bytes). I tried several versions of TWRP to no avail.
After abandoning the fastboot method I finally managed to flash the recovery image with the Flashify app (after successfully applying Kingo Root). Now the recovery appears to be gone completely since I'm unable to boot into recovery, and are instead presented with fastboot mode. This was the result after more than 5 hours of research and trial-and-error so you can imagine how frustrated I am. This device is listed as officially supported by LineageOS so of course I didn't expect it would be such a nuisance to flash.
My educated guess is that the device has been modified in a way that renders flashing impractical. Perhaps the partitions were resized improperly, but that would seem odd to me since the stock recovery was still present. There are a few more anomalies whose meaning I couldn't figure out on my own. The stock recovery presented me two systems to boot from. I have no idea how that feature is supposed to work, and couldn't find any information on it. The device has obviously been tampered with (as confirmed by fastboot oem device-info), as the MIUI version in about phone included the term decuro which I hadn't heard before. I quickly found out that decuro is an abandoned German MIUI project. Booting the second system would present me with what I believe to be the original MIUI 6 startup wizard. However it was completely unusable due to constant error messages of system processes. After my initial failures to flash TWRP I performed a full wipe. Everything appears to be the same (sans a bunch of bloatware), however the decuro reference in the about phone screen is now replaced with "BETA" (see screenshot below).
What also struck me is the differences in hardware to the official specifications you can found for this device online. XDA says about the Mi 4C:
"It comes in two variants, one with 16GB internal storage and 2GB of RAM, the other with 32GB internal storage and 3GB of RAM. Both are powered by a 1.82GHz hexa-core Qualcomm Snapdragon 808 processor"
Does that mean I have some kind of special variant? Does anyone have information on the specific model that I own? Please note also that when I tap System updates, an obviously modified Updater app is launched, again featuring the decuro label:
Before trying to flash anything I tried updating to the latest official MIUI ROM, assuming the bootloader was locked. I had to download the ROM manually since the Updater app says there are no updates. Trying to install the update package from within the app fails instantly, not specifiying what went wrong. So I renamed it to "update.zip" and moved it to the root directory of the internal storage, went into stock recovery and tried to flash from there. At 98% it would give me update failed due to signature verification. I'm now glad it didn't succeed because it would have locked the bootloader, and I prefer LineageOS anyway.
I hope someone here can shed some light on the whole thing. As of now I'm stuck with KitKat and no recovery, so any advice is highly appreciated.
UPDATE: Thread solved. I can't believe it, but this isn't a Mi 4C (libra). I checked the IMEI with Xiaomi's Product Authentication site because I was starting to consider that it might be a fake. Turns out it's genuine, and a Mi 4 (cancro)! The seller on eBay listed it as a 4C, the about phone menu said it was a 4C, and even Windows showed the device name as "Mi 4C". I don't get what this deception was supposed to achieve, but anyway. All working now.

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.

Android One XT1900-1 WiFi/SIM Not Working After Stock Flash

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

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?

Question Lenovo P11 Tab TB-J606F Wifi issues after GSI

Hi all
I have a bit of a problem after flashing the Google GSI (android 13) on my Lenovo Tab P11. Everything seemed to work well. Rebooted into the OS without any issues, everything seemed to work (Wifi included). I then swapped and deployed LineageOS 20 GSI which again, seemed to go okay but I had a google play protect issue.
During a quick check, I was planning on just rolling back to the Google GSI one, but accidently locked my device with
./fastboot.exe flashing lock
instead of unlock. And, taking no notice of the on screen prompts proceeded to relock the device which effectively bricked it. Nothing would load, not even recovery or fastboot.
A fair while later I managed to get recovery/fastboot working again by redoploying the boot.img, recovery.img and vbmeta.img from the stock ROM. I then discovered my current-slot had changed from b to a, so swapped that back too. This allowed the device to at least go into fastbootd so I ccould reflash it. I put the LineageOS back on, but now Wifi isn't working. Rolled back to Google GSI and the same.
I've tried following guides to re-install stock, but that's failing as well. I have read a couple of posts detailing issues with Wifi on GSI but the fixes didn't do anything or weren't necessarily inline with what I had. I suspect I have missed something I need to push back out to the device, but at this point I'm a bit stuck.
Anyone came across this before, or can point me where I can get some more information on it?
ta

whether some partitions are deleted or corrupted. You have the original backup qcn . try restoring it or trying to fix the partitions