Question Some cases in Flash from Android 11 to Android 12 - Sony Xperia 1 III

I has flash 61.1.A.2.211(Cust HK, Android 12) into system ver 61.0.A.23.20(Cust CN, Android 11) when active slot is B
when it end and phone reboot, it got into boot loop (It caused by AVB rollback protect, two system partition isn't the same MAJOR Android version)
after 3 times reboot, I got "device isn't trusted and no boot" alarm
when I force power off and connect it in flash mode, newflasher show baseband version is the old one
so I try use tool(such as bus hound) send "set_active:a" cmd to device bulk EP 1 Out ( this cmd like fastboot but fastboot cannot execute because of Locked Bootloader, I found it in newflasher source code) and reset device
then newflasher show current slot is A, then I flash it again
after this time, it can boot into system normally and show system is Android 12
but when I plug my phone card in, there shows no signal
then I open setting -> phone info, found IMEI become UNKNOWN
As before it cause by modem unmatch, so I try ONLY flash older modem.sin
but it not work after that camera cannot work, Photograpy Pro show Unknow Error
Then I flash 61.1.A.1.149(Cust HK, Android 12) ONLY modem.sin, camera come back, but still no IMEI
Soon I found modemst1 and modemst2 sin file, and try flash it
Then everything is back, I got the Fully functional Android 12
It seems that:
1. In Major version update, the modem would must flash new Android ver and SEA modem cannot use in CN device, but HK can
2. If boot from slot A, it will do AVB check, but if from slot B it won't
3. modem not only effect baseband but also camera
4. modemst1 and modemst2 include IMEI info

Anti-myself said:
I has flash 61.1.A.2.211(Cust HK, Android 12) into system ver 61.0.A.23.20(Cust CN, Android 11) when active slot is B
when it end and phone reboot, it got into boot loop (It caused by AVB rollback protect, two system partition isn't the same MAJOR Android version)
after 3 times reboot, I got "device isn't trusted and no boot" alarm
when I force power off and connect it in flash mode, newflasher show baseband version is the old one
so I try use tool(such as bus hound) send "set_active:a" cmd to device bulk EP 1 Out ( this cmd like fastboot but fastboot cannot execute because of Locked Bootloader, I found it in newflasher source code) and reset device
then newflasher show current slot is A, then I flash it again
after this time, it can boot into system normally and show system is Android 12
but when I plug my phone card in, there shows no signal
then I open setting -> phone info, found IMEI become UNKNOWN
As before it cause by modem unmatch, so I try ONLY flash older modem.sin
but it not work after that camera cannot work, Photograpy Pro show Unknow Error
Then I flash 61.1.A.1.149(Cust HK, Android 12) ONLY modem.sin, camera come back, but still no IMEI
Soon I found modemst1 and modemst2 sin file, and try flash it
Then everything is back, I got the Fully functional Android 12
It seems that:
1. In Major version update, the modem would must flash new Android ver and SEA modem cannot use in CN device, but HK can
2. If boot from slot A, it will do AVB check, but if from slot B it won't
3. modem not only effect baseband but also camera
4. modemst1 and modemst2 include IMEI info
Click to expand...
Click to collapse
Although hard to read, you did hint that flashing an older modemst1 and modemst2 will recover the IMEI. And yes, this has been the case for me as well. After wiping everything and trying a GSI rom (Corvus) I lost the IMEI and got wonky behaviour. After installing an older modemst1 and modemst2 all is good once again. (I used an A11 one).
So, yes, if you lose IMEI try flashing an older modemst1 and 2.

Related

[Help] Kate/Kenzo confusion and brick!

Hi guys! I am very sad with all this. I had bought a xiaomi rerdmi note 3 snapdragon and I wanted to flash Miui 8 thinking that I had kenzo versión. It flash succesfully and the cellphone boots just I lost signal (not imei) and any sensor works. I had finally discovered that I have kate version after a few days. Now cellphone works fine but I couldn't solve mi ril problem. It recognize muy sin card but It says "no service" I really need your help :crying: :crying: :crying:
Restore efs partition of kenzo mobile
yogesh1970 said:
Restore efs partition of kenzo mobile
Click to expand...
Click to collapse
IT WORKS!!! Thank you bro
Unable to flash any twrp or rom in KATE
My redmi note 3 KATE unlock story so far:
- Tried to unlock the official way -> no success
- Tried to unlock the unofficial way (KATE fastboot) -> success
- Figured out that there were new section in oem info which told "critical unlock" was false
- Unlocked the critical unlock to true
- Flashed *alka twrp -> got errors when trying the advanced wipe as pumpino's guide suggested
- Tried to flash many different twrps but no success to boot them -> only fastboot mode worked
- Tried to flash the latest KATE fastboot with mi flash tool -> error: product name mismatch (or something like that)
- Tried to flash the latest KENZO fastboot with mi flash tool -> success but sim card failure (imei lost?)
- Unlocked the unofficial way and flashed coffice twrp -> no success, only fastboot mode working
- Removed the getvar name check from KATE fastboot and flashed it -> error while flashing the system img
- Flashed KENZO fastboot without the name check
Now I can boot to adb mode with vol- & power, and to fastboot mode with vol+ & power. Normal boot starts the phone but ends into chinese screen where is only one button to press and then it boots again to the same chinese screen.
Any suggestions?
pokspaks said:
My redmi note 3 KATE unlock story so far:
- Tried to unlock the official way -> no success
- Tried to unlock the unofficial way (KATE fastboot) -> success
- Figured out that there were new section in oem info which told "critical unlock" was false
- Unlocked the critical unlock to true
- Flashed *alka twrp -> got errors when trying the advanced wipe as pumpino's guide suggested
- Tried to flash many different twrps but no success to boot them -> only fastboot mode worked
- Tried to flash the latest KATE fastboot with mi flash tool -> error: product name mismatch (or something like that)
- Tried to flash the latest KENZO fastboot with mi flash tool -> success but sim card failure (imei lost?)
- Unlocked the unofficial way and flashed coffice twrp -> no success, only fastboot mode working
- Removed the getvar name check from KATE fastboot and flashed it -> error while flashing the system img
- Flashed KENZO fastboot without the name check
Now I can boot to adb mode with vol- & power, and to fastboot mode with vol+ & power. Normal boot starts the phone but ends into chinese screen where is only one button to press and then it boots again to the same chinese screen.
Any suggestions?
Click to expand...
Click to collapse
Answer to myself:
As long as you can boot to fastboot, you are pretty much safe. You can boot to edl-mode and flash the (kate) fastboot rom using the mi flash tool.
nachonv said:
Hi guys! I am very sad with all this. I had bought a xiaomi rerdmi note 3 snapdragon and I wanted to flash Miui 8 thinking that I had kenzo versión. It flash succesfully and the cellphone boots just I lost signal (not imei) and any sensor works. I had finally discovered that I have kate version after a few days. Now cellphone works fine but I couldn't solve mi ril problem. It recognize muy sin card but It says "no service" I really need your help :crying: :crying: :crying:
Click to expand...
Click to collapse
i'm in the same condition, didn't know that i have kate device and i flashed kenzo rom. I didn't understand how to solve. Help me please! i have locked bootloader
solved today, flashed keto global and worked
petrov.eduard90 said:
i'm in the same condition, didn't know that i have kate device and i flashed kenzo rom. I didn't understand how to solve. Help me please! i have locked bootloader
Click to expand...
Click to collapse
i have same problems, do you have been solved your problem ?

[Guide][Root][ADB][Unlocking/Locking Bootloader][Lenovo k6/K6 Power] Karate

Lenovo K6/K6 Power (Karate)​Lenovo K6/K6 Power features a 5” 1080P IPS LCD display, giving a pixel density of ~441 PPI. Under the hood sits a Qualcomm Snapdragon 430 SoC, which utilises a 1.4 GHz octa-core CPU, an Adreno 505 GPU and 2 or 3 GB of RAM. The 16 GB internal storage version packs 2 GB of system RAM, the 32 GB, has 3 GB. The primary camera is capable of capturing images at 13 MP, the secondary at 8 MP. The whole 145g package is powered by a non-removable 4000mAh battery.*
Here is the guide for locking/unlocking your bootloader and flash custom recovery .
*Your Warranty will be void after unlocking bootloader*
What You need
A Laptop/PC
ADB Drivers
TWRP recovery
Some Patience
For Unlocking Your Bootloader :
First of all Install ADB drivers In Your Laptop/PC , Link is Here
https://forum.xda-developers.com/showthread.php?t=2588979
Now Go to Settings of Your Phone , Scroll Down and go to About Phone And Click on Build Number Until Your Developer Options Is enabled .
Now go to the Developer Options and turn on USB debugging and OEM unlocking.
Connect Your Mobile To your Pc through a USB cable.
Open ADB folder on Your Pc ( It will be in Local Disk C on your My files ) .
Right click + Press Shift in Adb folder , a popup will open , choose 'open command window here' .
Write Commands
Code:
adb reboot bootloader
(It should reboot your phone to fastboot , if not you must have done something wrong)
Code:
fastboot -i 0x17ef oem unlock-go
(This will unlock your bootloader and it will wipe your internal storage So better to backup first)
Done. Your phone will be rebooted and Your Bootloader is Unlocked.
For Flashing TWRP :
Download the twrp for Lenovo k6/k6 power (karate) from official twrp site.
Place it in the adb folder and rename it to recovery.img .
Now run these command
Code:
adb reboot bootloader
Code:
fastboot -i 0x17ef flash recovery recovery.img
OR​
Code:
fastboot flash recovery recovery.img
Done Recovery is flashed , Now You can Flash anything with the Help of TWRP recovery.
If You want to lock Your Bootloader again :
Use the same process as above , and use command
Code:
adb reboot bootloader
Code:
fastboot oem lock
It should relock Your Bootloader.
Any query about unlocking bootloader or root , feel free to ask here.
Can you please help me with install and use aircrack-ng and metasploit in my Lenovo k6 power.
@dr.bathman
AkashBahetra said:
@dr.bathman
Click to expand...
Click to collapse
Added your thread.
hii
twrp asking for password??
write password to decrypt.?
any idea??
amit.tiger12 said:
hii
twrp asking for password??
write password to decrypt.?
any idea??
Click to expand...
Click to collapse
go to WIPE > FORMAT DATA > TYPE yes
firemax13 said:
go to WIPE > FORMAT DATA > TYPE yes
Click to expand...
Click to collapse
Yep. Got that.. Lenovo stock ROM encrypts device after clearing data or every factory reset..
It doesn't happens with custom ROMs..
Is it necessary to type 0x17ef, i.e. Block ID??
AFAIK, Mostly I type Fastboot OEM Unlock or in case of Motorola, Enter key and for flashing, just Fastboot flash ......
I have k33a42 2gb ram/16 gb K6 Power and Nougat 7.0 (K33_S229_170908_ROW)
Is this method also valid for my phone?
Is there any way to reset boot loader settings to their original state?
Hello,
I have Lenovo K6 Power (K33a42, 32GB, 3GB RAM)
I had accidentally selected USA band in *#*#4636#*#* . Since then, I was only getting signal in one of the selected 4G SIMs, the 2nd SIM was without network. My phone was updated to latest Nougat 7.0 prior to this problem (build S229, July security patch).
To solve the USA band problem, I flashed original ROM with help of Lenovo Moto Smart Assistant 3.2.0.9 (in hopes of reviving the networks). It downloaded S156 (Marshmallow 6.0.1) by default, which I flashed onto device successfully. Still the network problem was not solved, the 2nd sim still did not show any network.
Later, I found this link :
Code:
cnet dot com / forums/discussions/accidentally-selected-usa-band-in-moto-x-play/
so to try the solution I downloaded Platform Tools from Android Developers website :
Code:
developer dot android dot com /studio/releases/platform-tools.html
(Please adjust the above links correctly, XDA did not allow me to post direct links since this is my first post)
and as per the instructions tried these commands:
Code:
adb reboot bootloader
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
Now, the signals did show up on both sims upon reboot, but I realised I lost VoLTE. None of the 4g sims were able to connect to VoLTE. I tried Network Settings Reset, APN settings reset, Restart, updated again to Nougat latest build S229 from phone's Software Update menu, nothing worked.
I also have a minor problem, upon reboot the 1st sim instantly shows network bars, the 2nd sim shows zero bars. Yet inside 'Phone Status' menu, network is shown as connected and even SMSes are received. Putting on Airplane Mode helps, but this is annoying, as I will have to deal with this bug each time I restart.
Can anyone please help? I want my phone's boot loader to be back to default network settings, and both my networks to work like when the phone is new.
I have a lenovo k6 power. I have done
fastboot erase modemst1
fastboot erase modemst2
fastboot erase cache
But after that my phone isn't detecting sim cards. Someone have a solution for this?
hello guys
seems like when i am unlocking my bootloader is very different.
i did follow this tutorial: https://www.youtube.com/watch?v=icMaiZRiugQ&t=171s
but my results are different, seems i can't unlock my bootloader
been searching, reading and watching any possible way but i cant pull this through
can someone please help?
in the tutorial, all is false, but mine is different, and after that, stucks on fastboot
sevenfolds said:
hello guys
seems like when i am unlocking my bootloader is very different.
i did follow this tutorial: https://www.youtube.com/watch?v=icMaiZRiugQ&t=171s
but my results are different, seems i can't unlock my bootloader
been searching, reading and watching any possible way but i cant pull this through
can someone please help?
in the tutorial, all is false, but mine is different, and after that, stucks on fastboot
Click to expand...
Click to collapse
As what we see you need to follow the instruction here in xda because some nuub's people posting fake slash real slash lol things.
I can't help you now because I'm not using k6 power
firemax13 said:
As what we see you need to follow the instruction here in xda because some nuub's people posting fake slash real slash lol things.
I can't help you now because I'm not using k6 power
Click to expand...
Click to collapse
okay bro lol, thanks i'm done. aex now.
Hi, does this method works if I already updated device to the latest official android N?
flashing twrp is not working
on the adb menu says its finished but the device says its still flashing and when i try to use recovery its still the lenovo recovery
---------- Post added at 03:13 PM ---------- Previous post was at 03:11 PM ----------
[/COLOR]
iamvm007 said:
i have same problem , have you got solution?
Click to expand...
Click to collapse
AravindN said:
I have a lenovo k6 power. I have done
fastboot erase modemst1
fastboot erase modemst2
fastboot erase cache
But after that my phone isn't detecting sim cards. Someone have a solution for this?
Click to expand...
Click to collapse
have you got solution? i have same problem
Gonime said:
flashing twrp is not working
on the adb menu says its finished but the device says its still flashing and when i try to use recovery its still the lenovo recovery
Click to expand...
Click to collapse
I'm also experiencing this. Did I screw up somewhere?
Gonime said:
flashing twrp is not working
on the adb menu says its finished but the device says its still flashing and when i try to use recovery its still the lenovo recovery
Click to expand...
Click to collapse
goblin95 said:
I'm also experiencing this. Did I screw up somewhere?
Click to expand...
Click to collapse
Just after flashing the recovery (the last step), hold the power button, and the volume up button until your device reboots to a screen where you can select recovery option.
The trick is, don't let the device boot to the system, since it flashes the stock recovery and you will have to do it all over again. boot directly to recovery after flashing a custom recovery.
btw, I was on the last update (some S31) stock Nougat 7.0.
Got Unlocked and Twrp Running with this method, including my last step. Hope to see some custom ROM working without issues with it.
little confession here
Well I got this device from a relative and she says it hangs like hell, I was in a habit of getting the back cover out and pulling the battery. forgot about that here and removed the back panel with full force. luckily only some plastic bits came off. That's what happen when I keep jumping in all the forum flashing all kinds of device for my peeps. :laugh::laugh:
Sai SD said:
Hello,
I have Lenovo K6 Power (K33a42, 32GB, 3GB RAM)
I had accidentally selected USA band in *#*#4636#*#* . Since then, I was only getting signal in one of the selected 4G SIMs, the 2nd SIM was without network. My phone was updated to latest Nougat 7.0 prior to this problem (build S229, July security patch).
To solve the USA band problem, I flashed original ROM with help of Lenovo Moto Smart Assistant 3.2.0.9 (in hopes of reviving the networks). It downloaded S156 (Marshmallow 6.0.1) by default, which I flashed onto device successfully. Still the network problem was not solved, the 2nd sim still did not show any network.
Later, I found this link :
Code:
cnet dot com / forums/discussions/accidentally-selected-usa-band-in-moto-x-play/
so to try the solution I downloaded Platform Tools from Android Developers website :
Code:
developer dot android dot com /studio/releases/platform-tools.html
(Please adjust the above links correctly, XDA did not allow me to post direct links since this is my first post)
and as per the instructions tried these commands:
Code:
adb reboot bootloader
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
Now, the signals did show up on both sims upon reboot, but I realised I lost VoLTE. None of the 4g sims were able to connect to VoLTE. I tried Network Settings Reset, APN settings reset, Restart, updated again to Nougat latest build S229 from phone's Software Update menu, nothing worked.
I also have a minor problem, upon reboot the 1st sim instantly shows network bars, the 2nd sim shows zero bars. Yet inside 'Phone Status' menu, network is shown as connected and even SMSes are received. Putting on Airplane Mode helps, but this is annoying, as I will have to deal with this bug each time I restart.
Can anyone please help? I want my phone's boot loader to be back to default network settings, and both my networks to work like when the phone is new.
Click to expand...
Click to collapse
Modemst 1 and Modemst 2 means your Imei of sim 1 and sim 2.
Go to phone and type *#06# and it will show you the imei.
It must be null as you erased it.
Since they both are same,you wont have signal in both sims.

Huawei P20 Lite, Bricked??

I am in a massive pickle here.
I installed root on my phone but stupidly enough I forgot to FRP unlock my phone. with also phone unlocked
Phone unlocked
FRP lock
My phone now only boots into erecovery and twrp doesn't load on my phone anymore and have tried multiple times to load it up again.
I have factory reset my phone and tried multiple stock roms to install but all get stuck at 5% and fail.
My build number is ANE-LX1 8.0.0.103(C782)
I then went to DC unlocker to remove FRP and came up with their own error code 'unknown error 405'
I am now stuck on what to do as fastboot device works but when i try to flash something all i get is command failed.
First : have you download your build "FULL-Update" ?
then you need bootloader=unlockt (Phone unlocked) AND FRP=unlock
if nothing help - dc-unlocker can bootloader unlock (4€) and can FRP unlock (15€)
with HuaweiExtractor extract 3 img - ramdisk.img, recovery_ramdis.img, system.img
the Extractor do automatic 3 *.img.header
this 6 files copy to your ADB-folder, then
- fastboot flash ramdisk ramdisk.img
- fastboot flash recovery_ramdisk recovery_ramdis.img
- fastboot flash system system.img
this work only if "bootloader unlockt" AND "FRP unlock" !!!
if flash work and phone reboot - phone boot to stock-recovery and format low-level "data"
if "... stuck at 5% and fail" : your stock-recovery is bad !
if all work, phone boot: all your data is lost (format low-level "data")
factory reset (with format low-level "data") ONLY work with stock-recovery - NO with TWRP
Example
i have TWRP installed
OTA-Update incommig, this write "undate install now ?", i do "NO - later"
i flash stock-recovery
now install the update
if all work i can new-flash TWRP
and 1 question : what the way you root your phone ?
Same sh-t. But in stupid action i've locked boot also. So i have: locked boot, locked frp, no system files, not working recovery (erecovery did nothing helpful (no online updates, no factory reset)) I have nand backup (but dont have twrp) and i have a wish to drop that all-way-stupid-ideas device from ten floor :c Any ways without pay 15e? Better i will smash it and buy something better for smaller cost
I´m in the same situation, but my frp is not locked. What I do is try to unroot my device flashing magiskuninstaller.zip and unSU.zip and everything seems to be ok but on reboot my phone enter erecovery and do anything, the same thing, dont download latest version and manually update with Update.app and dload stuck at 5%. I tried this:
with HuaweiExtractor extract 3 img - ramdisk.img, recovery_ramdis.img, system.img
the Extractor do automatic 3 *.img.header
this 6 files copy to your ADB-folder, then
- fastboot flash ramdisk ramdisk.img
- fastboot flash recovery_ramdisk recovery_ramdis.img
- fastboot flash system system.img
but on first boot there is a bootloop and the second boot sends to erecovery again
My phone is ANE-LX3 latinoamerica, any help will be appreciated....sorry my bad english
please try this :
- download full update rom for your device, extract the .APP files using HuaweiUpdateExtractor
- boot into fastboot by press and hold Volume Down and plug in usb cable into your pc and your phone, hold it until it boot into fastboot
- do this :
fastboot flash kernel kernel.img
fastboot flash ramdisk ramdisk.img
fastboot flash recovery_ramdisk recovery_ramdis.img
fastboot flash recovery_vbmeta recovery_vbmeta.img
fastboot flash recovery_vendor recovery_vendor.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot flash vendor vendor.img
- reboot your device and hold Volume Up and Volume Down to get it boot into eRecovery and do Wipe Cache Partitions and then do Factory Data Reset, and reboot again
- let it boot normally, and see what happen next, i can't remember for sure because it's been so long i unbricked my Nova 2s with this method. there are 2 possibility, you'll boot into system normally, or it will boot into eRecovery again and there is an option Download Latest Version And Recovery and you can choose that, of course you should have connection to internet via wifi.
please report back if you have difficulties.
This p20 lite frp fix works!
Hi if your needing to bypass the frp lock on your huawei because someone factory reset it and forgot the google id do a Google search on huawei p20 frp bypass, scroll down until you come to mobileheadlines website. They had shortcut maker app download and full instructions on how to bypass it, it worked for me no probs, aslo there is a great video by hard reset ablout frp bypassing on the p20 on you tube. Hope this helps u out dave b...
P20 Pro stuck in bootloop
heindrix said:
please try this :
- download full update rom for your device, extract the .APP files using HuaweiUpdateExtractor
- boot into fastboot by press and hold Volume Down and plug in usb cable into your pc and your phone, hold it until it boot into fastboot
- do this :
fastboot flash kernel kernel.img
fastboot flash ramdisk ramdisk.img
fastboot flash recovery_ramdisk recovery_ramdis.img
fastboot flash recovery_vbmeta recovery_vbmeta.img
fastboot flash recovery_vendor recovery_vendor.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot flash vendor vendor.img
- reboot your device and hold Volume Up and Volume Down to get it boot into eRecovery and do Wipe Cache Partitions and then do Factory Data Reset, and reboot again
- let it boot normally, and see what happen next, i can't remember for sure because it's been so long i unbricked my Nova 2s with this method. there are 2 possibility, you'll boot into system normally, or it will boot into eRecovery again and there is an option Download Latest Version And Recovery and you can choose that, of course you should have connection to internet via wifi.
please report back if you have difficulties.
Click to expand...
Click to collapse
Could this method also work for me? I bought a P20 Pro while in China. Being in Europe I did not receive the OTA to Android Pie and I had still Chinese characters popping up left and right.
So I got an bootloader unlock code.
Then used Funkyhuawei to rebrand the phone. The instructions mentioned I had to do the eRecovery twice. But after the first download it got stuck in a bootloop. I cannot get back into eRecovery.
I did manage to clean the data and do a factory reset, but I did not get back in the the eRecovery mode. Now I am stuck.
Thanks
TJL590 said:
I am in a massive pickle here.
I installed root on my phone but stupidly enough I forgot to FRP unlock my phone. with also phone unlocked
Phone unlocked
FRP lock
My phone now only boots into erecovery and twrp doesn't load on my phone anymore and have tried multiple times to load it up again.
I have factory reset my phone and tried multiple stock roms to install but all get stuck at 5% and fail.
My build number is ANE-LX1 8.0.0.103(C782)
I then went to DC unlocker to remove FRP and came up with their own error code 'unknown error 405'
I am now stuck on what to do as fastboot device works but when i try to flash something all i get is command failed.
Click to expand...
Click to collapse
same i did that lol
extract from update.zip the update.app with HuaweiUpdateExtractor0.9.9.5
and search or try any update file until that works
You have to do it flash fastboot flash system system.img
fastboot flash recovery_ramdisk P20LiteTWRP_3.4.0-0.img
The P20LiteTWRP_3.4.0-0.img is in my Mediafile rar Data
fastboot flash vbmeta vbmeta.img
fastboot flash kernel kernel.img
fastboot flash recovery_ramdisk recovery_ramdis.img
fastboot flash recovery_vbmeta recovery_vbmeta.img
fastboot flash recovery_vendor recovery_vendor.img
You forget unlock syntax?
fastboot oem unlock (get here your Code without bracket)
Allert!! The Website:
Global Unlocking Solutions
global-unlocking-solutions.miiduu.com
Is Cheating, you can pay but get nothing.
Complett Unbrick P20 Lite Single SIM
P20 Lite single SIM Recovery
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
MainSource
[Guide] How to install stock firmware & links for ANE-LX1C432 firmwares
Before start changing the firmware you should check first if Huawei release FullOTA for your device. Without full firmware is highly recommend do not mess up with device. Make a full or partial backup with the TWRP [for partial I recommend...
forum.xda-developers.com
P20 lite Single SIM
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G2496/g1789/v192822/f1/full/ANE-L01_hw_eu/update_full_ANE-L01_hw_eu.zip
And you need
MainSource From:
[Guide] Switching OEMINFO versions
I've seen a number of posts asking how to switch the oeminfo of your phone - so I decided to make a quick guide. Warning: Use this guide at your own risk. I did this on my own p20 Lite without issue but YMMV. Pre-req's Please ensure that you...
forum.xda-developers.com
oeminfo.img
For P20 Lite Single Sim
oeminfo_C432_SS.zip | by Sykomaniac for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
You need unlock your bootloader before, you have your code not?
Unlock modems, routers and phones with DC-unlocker software
DC-unlocker is universal, fast and easy to use unlocking tool. Supports Huawei, ZTE, Sierra Wireless and other modems, routers and phones.
www.dc-unlocker.com
Open a ticked not a forum thread!
Your phonedate a secred and only for you!
Phone Model Name
Product IMEI or MEID
Product Serial Number
Product ID (unique for our phone name)
Phone Model Name and IMEI/MEID you will find in Phone Menu >>> Settings >>> About Phone
Product IMEI or MEID(Primary IMEI if phone is dual sim)
Product ID(unique for our phone name)and Serial Number you can get it from phone service menu.
To do that enter on a phone keyboard *#*#1357946#*#* That will open service menu with all information.
What android version you have on your device?
What is your region (e.g. C432, C185...) in build number? Single/dual SIM?
without information about your region I can't help you.

Motorola Moto Z4 bricked - only bootloader / fastboot access remaining (no recovery)

I have a Moto Z4 XT1980-3 (Unlocked retail version with RETUS channel) with bootloader locked - no modifications from official state so far. When I got the December 2019 security patch upgrade, something network-related got corrupted - I have not been able to connect to any WiFi at all! This was the origin of all the desaster.
I read through the internet and found the information that it could happen that an OTA upgrade may not have been got on the device properly and if there are any hassles afterwards, it is required to do a full flash of the recent firmware. Okay, no problem, I thought. I am really familiar with ADB, fastboot and so on, and so I did. Took the recent firmware from here: https://mirrors.lolinet.com/firmware/moto/foles/official/RETUS/ (the one uploaded on 6th of December 2019).
The result was that I could flash all parts of the firmware, except of boot, vbmeta and dspso - for these parts I got a "(bootloader) Preflash validation failed" error. So now I am with an inconsistent firmware state and can only access fastboot mode (not even recovery). Plus sometimes when booting it, I get errors of unbootable A/B slots in the bootloader log. After having flashed gpt again, these errors disappear and I simply get the message that my device won't boot because of an invalid operating system.
What I have already tried to do:
- flash a full factory image (see above)
- use RSD lite (this tool detects my device as connected, but with no device information at all (only "?") and says it can not be switched to fastboot mode - but I am in fastboot mode already ???)
- use LSMA Smart Repair Assistant (this tool says my device is not compatible)
- Blankflash (I have not found out yet how to get my device in edl mode from fastboot)
As bricked devices are a more general Android issue and Moto Z4 is not very spread (the corresponding device forum is almost dead), I try to ask my question here in the general Android troubleshooting section. I hope, somebody can give me any advice how to reanimate my device. Maybe, anybody with special Motorola experience who can tell me why I can not flash the full factory image or explain how I can get boot, vbmeta and dspso back to the device. Any help appreciated.

Question fastboot getvar all

yeah, can anyone check this command in bootloader and paste the output here ? I would be very thankful because my phone is stuck in EDL mode and can't be flashed using Qfil. I need to check the output of this command to hopefully be able to figure something out.
Ask @kofijordan how he accomplished it, we went throught the same scenario with slot_a & slot_b and EDL. I'm thinking you have the wrong QPST/QFIL. Send him a private message or maybe he'll see the mention and let you know what his setup has installed.
&(*) said:
Ask @kofijordan how he accomplished it, we went throught the same scenario with slot_a & slot_b and EDL. I'm thinking you have the wrong QPST/QFIL. Send him a private message or maybe he'll see the mention and let you know what his setup has installed.
Click to expand...
Click to collapse
The thing is, I need to check if there is anything like unlock_a & unlock_b partitions. When I flashed the sn.img it could be the A slot only, and now it has switched to B which bootloader might be locked and preventing user from using Qfil.
That's not your issue with switching the current slot, you didn't clone all your slots and now it doesn't have everything it needs to mount properly back into the bootloader. My bet is you have the wrong software and need the more recent QPST and maybe the vc++ redistributables (both 2010 & 2012 x86).
I'm using Qfil 2.0.3.5 from QPST 2.7.496 (the latest one i could find) and have the qualcomm drivers and vc installed, and it's still the same
Both vc 2010 & 2012? Are you executing QFIL from the QPST path where all the .dll dependencies are?
&(*) said:
Both vc 2010 & 2012? Are you executing QFIL from the QPST path where all the .dll dependencies are?
Click to expand...
Click to collapse
Yup, everything is as should be
Did you previously use QFIL without the issues you are facing currently, meaning the phone in it's present state is the issue?
&(*) said:
Did you previously use QFIL without the issues you are facing currently, meaning the phone in it's present state is the issue?
Click to expand...
Click to collapse
I wrote it in another post already, from the moment i started tinkering with it (it was fully functional back then), there always was this Sahara error happening
I went through a similar process when I first installed QFIL with errors but fixed them after installing vc 2010 & vc 2012 x86 redistributables. In device manager is there a yellow exclamation anywhere when you plug the device in (missing driver)? I remember reading you installed QFIL v2 from lolinet, correct? QPST (.496) comes with it, so my guess is you don't have the right version of QFIL or have replaced it with the other version and now there is a mismatch when it executes. You could also try deleting temp data stored as a hidden folder under (username)/appdata/local/temp, though I don't think that is what's causing the issue. If all else fails delete every reference of data after uninstalling QPST (ProgramData, ProgramFiles(x86), etc) and reinstall it and do not use the other QFIL version supplied from lolinet.
&(*) said:
I went through a similar process when I first installed QFIL with errors but fixed them after installing vc 2010 & vc 2012 x86 redistributables. In device manager is there a yellow exclamation anywhere when you plug the device in (missing driver)? I remember reading you installed QFIL v2 from lolinet, correct? QPST (.496) comes with it, so my guess is you don't have the right version of QFIL or have replaced it with the other version and now there is a mismatch when it executes. You could also try deleting temp data stored as a hidden folder under (username)/appdata/local/temp, though I don't think that is what's causing the issue. If all else fails delete every reference of data after uninstalling QPST (ProgramData, ProgramFiles(x86), etc) and reinstall it and do not use the other QFIL version supplied from lolinet.
Click to expand...
Click to collapse
Every program's version was the most recent and I had everything installed correctly but I decided to check the drivers details under the HS-USB QDLOADER 9008 device and it turned out, my antivirus had installed a usb driver that was superior to the Qualcomm one and was overriding it. Now Qfil loads some things but still shows the error, which now is ERROR: it took x seconds to open port. Which is longer than 3. This indicates your target is not stable.
A little progress; now try with the device fully powered down, hold both volume buttons and power button, screen should flash for a split second then plug it in and flash the build right away.
Can't do that because this phone is constantly in edl mode and there is no way to turn it off. Holding power off or power off + volume for 15 seconds causes Qfil to blink the port for a split second but there is nothing on the device.
I tried to do it for like 30 mins and every time it reports com port timeout at around 10sec instead of 3
SOOOO
it works !!
Turns out i wasted like 20 hours trying to flash it. The first error was caused by a different driver interfering with the appropriate one. The next one - timeout - solved it by using the _lite elf file instead of _ddr. The _lite one should have flashed the Super.img partition as far as i know. Now it boots .062.
That's good news. Would you be willing to try to install the CN Pro 2 version?
If so, flash the bundle and right after it finishes boot into the bootloader and type:
reboot fastboot
(make sure it registers as a fastboot device), then
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
Both vbmeta and vbmeta_system can be found within the CN 12.5.591 bundle.
Downloading cn roms atm. There are some problems after reflashing the global firmware. The baseband has been wiped along with imei info so no network access for now, there should be no radio.img so something entirely different may be causing it. There is abnormal battery drain, ca. 30-40% during the night with wifi turned off and power saving mode enabled, no LEDs nor fan working. Also the front camera isn't calibrated correctly and the motor tries to move it like double the usual distance. Flashing the persist.img didn't help and i have no QCN backup but it's no big deal as i bough it for gaming and tinkering.
&(*) said:
That's good news. Would you be willing to try to install the CN Pro 2 version?
If so, flash the bundle and right after it finishes boot into the bootloader and type:
reboot fastboot
(make sure it registers as a fastboot device), then
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
Both vbmeta and vbmeta_system can be found within the CN 12.5.591 bundle.
Click to expand...
Click to collapse
with or without flashing vbmeta and vbmeta_system all it does is boot up, shows the boot animation with chinese SD888 banner and displays the incorrect firmware warning.
Flashing the CN 12.5.535 via Qfil with boot.img already swapped to TWRP boot.img in the root folder also does not work, the phone is stuck in bootloader just like with global rom and modified boot.img.
Malberd said:
Downloading cn roms atm. There are some problems after reflashing the global firmware. The baseband has been wiped along with imei info so no network access for now, there should be no radio.img so something entirely different may be causing it. There is abnormal battery drain, ca. 30-40% during the night with wifi turned off and power saving mode enabled, no LEDs nor fan working. Also the front camera isn't calibrated correctly and the motor tries to move it like double the usual distance. Flashing the persist.img didn't help and i have no QCN backup but it's no big deal as i bough it for gaming and tinkering.
Click to expand...
Click to collapse
Everything you mention is why QFIL should be used very cautiously and carefully. It's best used for patching or targeting a specific partition. There is a tutorial that has been reported to work for Legion Duels posted here . You might need to request a blank QCN from another Legion Duel 2/Pro 2 owner, or the blank QCN posted within that thread might be modifiable to restore what's missing. The porting from Pro 2 to Duel 2 is turning out to be an unnecessary nightmare and the Lenovo Hong Kong devs need to address it with a solution. The device feels practically abandoned and it shouldn't be.

Categories

Resources