Database Develop

XT1052 Need Help :(

I'm quite pissed with what's happening to my phone. No matter how I upgrade to lollipop (through fastboot or going back to 4.4.4 and then taking the OTA or by flashing zip through stock recovery) it doesn't recognize my home wifi. It works fine on stock 4.4.4 asia retail image
- I also noticed a strange thing, I don't know why but the Verizon logo shows up just before the boot finishes on 5.1!! I'm in India and why would verizon logo come on my phone?
- My bootloader is unlocked and also upgraded to 30BE so I can't flash gpt and boot files but rest of the files flash just fine through fastboot and I'm able to go back to stock 4.4.4 asia retail. everything works as expected (Wifi too)!!!
Somebody please tell me how can I get stock lollipop 5.1 and have the Wifi work too?
I've tried flashing 4.4.4 modem over 5.1 but it still doesn't recognizde my home wifi.. although it is able to scan all other nearby wifi!!!
Kitkat version - XT1052_RETAIL-ASIA_4.4.4_KXA21.12-L1.26_18_cid7_CFC_1FF.xml
Lollipop version - Blur_Version.212.44.26.ghost_row.AsiaRetail.en.03

sroy001 said:
I'm quite pissed with what's happening to my phone. No matter how I upgrade to lollipop (through fastboot or going back to 4.4.4 and then taking the OTA or by flashing zip through stock recovery) it doesn't recognize my home wifi. It works fine on stock 4.4.4 asia retail image
- I also noticed a strange thing, I don't know why but the Verizon logo shows up just before the boot finishes on 5.1!! I'm in India and why would verizon logo come on my phone?
- My bootloader is unlocked and also upgraded to 30BE so I can't flash gpt and boot files but rest of the files flash just fine through fastboot and I'm able to go back to stock 4.4.4 asia retail. everything works as expected (Wifi too)!!!
Somebody please tell me how can I get stock lollipop 5.1 and have the Wifi work too?
I've tried flashing 4.4.4 modem over 5.1 but it still doesn't recognizde my home wifi.. although it is able to scan all other nearby wifi!!!
Kitkat version - XT1052_RETAIL-ASIA_4.4.4_KXA21.12-L1.26_18_cid7_CFC_1FF.xml
Lollipop version - Blur_Version.212.44.26.ghost_row.AsiaRetail.en.03
Click to expand...
Click to collapse
First of all, wrong section to post.
Second, flash this through fastboot/RSDLite - https://mega.co.nz/#!U9lRFBgD!POchMYI96ZTy16M_PGSZ4aIjo6ktpaHKaJAmp6XBUR4
It's the 5.1 factory image. works on Asia retail without any problem.. try if it works

Made a separate thread in General section now.. Not sure how to delete the thread.. Can't find the option in XDA app
RSD Lite flashing doesn't work for me anymore as 1st two commands about GPT and Motoboot fail due to upgraded boot loader.. So I'll try and flash through fastboot
Sent from my XT1052 using XDA Free mobile app

sroy001 said:
Made a separate thread in General section now.. Not sure how to delete the thread.. Can't find the option in XDA app
RSD Lite flashing doesn't work for me anymore as 1st two commands about GPT and Motoboot fail due to upgraded boot loader.. So I'll try and flash through fastboot
Sent from my XT1052 using XDA Free mobile app
Click to expand...
Click to collapse
RSD will work as this is a 5.1 factory image. make sure to flash gpt and bootloader, it won't fail.
if you dont flash those then you'll have gpt and bootloader from Asia.Retail and other files from Europe.Retail so future OTAs might fail

Okay done.. So if RSD lite doesn't flash GPT and Motoboot, should I manually try and flash through fastboot?
Sent from my XT1052 using XDA Free mobile app

sroy001 said:
Okay done.. So if RSD lite doesn't flash GPT and Motoboot, should I manually try and flash through fastboot?
Sent from my XT1052 using XDA Free mobile app
Click to expand...
Click to collapse
Since you have already updated the bootloader and partition tables to the latest one from Lollipop there is no need to flash those files again. Just flash the modem, recovery, data and system files using cmd line.
Sent from my XT1053 using Tapatalk

bushako said:
Since you have already updated the bootloader and partition tables to the latest one from Lollipop there is no need to flash those files again. Just flash the modem, recovery, data and system files using cmd line.
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
I'm flashing through fastboot and unable to manually flash system.img
C:\adb>mfastboot flash system system.img
(bootloader) Variable not supported!
target max-download-size: 768MB
Multi-Flash is enabled!
load_file: could not allocate 1394503608 bytes
error: cannot load 'system.img': Not enough space

sroy001 said:
I'm flashing through fastboot and unable to manually flash system.img
C:\adb>mfastboot flash system system.img
(bootloader) Variable not supported!
target max-download-size: 768MB
Multi-Flash is enabled!
load_file: could not allocate 1394503608 bytes
error: cannot load 'system.img': Not enough space
Click to expand...
Click to collapse
I think you may need to flash gpt.bin first.. i'll post a log of what happened when i flashed here.. flash it in the same order..
H:\platform-tools>mfastboot devices
TAxxxxxxxx fastboot
H:\platform-tools>mfastboot flash partition gpt.bin
sending 'partition' (32 KB)...
OKAY [ 0.250s]
writing 'partition'...
This may take a few seconds, if a
different partition table is being
flashed since we need to backup
and restore a few partitions
OKAY [ 0.437s]
finished. total time: 0.689s
H:\platform-tools>mfastboot flash motoboot motoboot.img
sending 'motoboot' (1604 KB)...
OKAY [ 0.350s]
writing 'motoboot'...
flashing tz ...
flashing rpm ...
flashing aboot ...
flashing sbl1 ...
flashing sbl2 ...
flashing sbl3 ...
OKAY [ 5.979s]
finished. total time: 6.330s
H:\platform-tools>mfastboot flash logo logo.bin
sending 'logo' (245 KB)...
OKAY [ 0.310s]
writing 'logo'...
OKAY [ 1.385s]
finished. total time: 1.695s
H:\platform-tools>mfastboot flash boot boot.img
sending 'boot' (10240 KB)...
OKAY [ 0.940s]
writing 'boot'...
OKAY [ 2.209s]
finished. total time: 3.150s
H:\platform-tools>mfastboot flash recovery recovery.img
sending 'recovery' (10240 KB)...
OKAY [ 0.950s]
writing 'recovery'...
OKAY [ 1.522s]
finished. total time: 2.472s
H:\platform-tools>mfastboot flash system system.img
sending 'system' (786432 KB)...
OKAY [ 49.478s]
writing 'system'...
OKAY [ 43.636s]
sending 'system' (575387 KB)...
OKAY [ 36.324s]
writing 'system'...
OKAY [ 36.938s]
finished. total time: 166.385s
H:\platform-tools>mfastboot flash modem NON-HLOS.bin
sending 'modem' (54276 KB)...
OKAY [ 3.720s]
writing 'modem'...
OKAY [ 4.811s]
finished. total time: 8.531s
H:\platform-tools>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.789s]
finished. total time: 0.790s
H:\platform-tools>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.816s]
finished. total time: 0.817s
H:\platform-tools>mfastboot flash fsg fsg.mbn
sending 'fsg' (226 KB)...
OKAY [ 0.380s]
writing 'fsg'...
OKAY [ 1.154s]
finished. total time: 1.535s
H:\platform-tools>mfastboot erase cache
erasing 'cache'...
OKAY [ 2.822s]
finished. total time: 2.823s
H:\platform-tools>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 18.879s]
finished. total time: 18.879s
H:\platform-tools>mfastboot erase customize
erasing 'customize'...
OKAY [ 0.182s]
finished. total time: 0.182s
H:\platform-tools>mfastboot erase clogo
erasing 'clogo'...
OKAY [ 0.604s]
finished. total time: 0.604s
H:\platform-tools>mfastboot reboot
rebooting...
finished. total time: 0.001s
H:\platform-tools>

athulele said:
I think you may need to flash gpt.bin first.. i'll post a log of what happened when i flashed here.. flash it in the same order..
H:\platform-tools>mfastboot devices
TAxxxxxxxx fastboot
H:\platform-tools>mfastboot flash partition gpt.bin
sending 'partition' (32 KB)...
OKAY [ 0.250s]
writing 'partition'...
This may take a few seconds, if a
different partition table is being
flashed since we need to backup
and restore a few partitions
OKAY [ 0.437s]
finished. total time: 0.689s
H:\platform-tools>mfastboot flash motoboot motoboot.img
sending 'motoboot' (1604 KB)...
OKAY [ 0.350s]
writing 'motoboot'...
flashing tz ...
flashing rpm ...
flashing aboot ...
flashing sbl1 ...
flashing sbl2 ...
flashing sbl3 ...
OKAY [ 5.979s]
finished. total time: 6.330s
H:\platform-tools>mfastboot flash logo logo.bin
sending 'logo' (245 KB)...
OKAY [ 0.310s]
writing 'logo'...
OKAY [ 1.385s]
finished. total time: 1.695s
H:\platform-tools>mfastboot flash boot boot.img
sending 'boot' (10240 KB)...
OKAY [ 0.940s]
writing 'boot'...
OKAY [ 2.209s]
finished. total time: 3.150s
H:\platform-tools>mfastboot flash recovery recovery.img
sending 'recovery' (10240 KB)...
OKAY [ 0.950s]
writing 'recovery'...
OKAY [ 1.522s]
finished. total time: 2.472s
H:\platform-tools>mfastboot flash system system.img
sending 'system' (786432 KB)...
OKAY [ 49.478s]
writing 'system'...
OKAY [ 43.636s]
sending 'system' (575387 KB)...
OKAY [ 36.324s]
writing 'system'...
OKAY [ 36.938s]
finished. total time: 166.385s
H:\platform-tools>mfastboot flash modem NON-HLOS.bin
sending 'modem' (54276 KB)...
OKAY [ 3.720s]
writing 'modem'...
OKAY [ 4.811s]
finished. total time: 8.531s
H:\platform-tools>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.789s]
finished. total time: 0.790s
H:\platform-tools>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.816s]
finished. total time: 0.817s
H:\platform-tools>mfastboot flash fsg fsg.mbn
sending 'fsg' (226 KB)...
OKAY [ 0.380s]
writing 'fsg'...
OKAY [ 1.154s]
finished. total time: 1.535s
H:\platform-tools>mfastboot erase cache
erasing 'cache'...
OKAY [ 2.822s]
finished. total time: 2.823s
H:\platform-tools>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 18.879s]
finished. total time: 18.879s
H:\platform-tools>mfastboot erase customize
erasing 'customize'...
OKAY [ 0.182s]
finished. total time: 0.182s
H:\platform-tools>mfastboot erase clogo
erasing 'clogo'...
OKAY [ 0.604s]
finished. total time: 0.604s
H:\platform-tools>mfastboot reboot
rebooting...
finished. total time: 0.001s
H:\platform-tools>
Click to expand...
Click to collapse
I was indeed able to flash 5.1 image through latest version of rsd lite.. But it still doesn't detect my home WiFi.. It scans all other neighborhood WiFi though
So went back to stock 4.4.4 through fastboot and WiFi is back.. Quite strange but now I'm pissed of trying.. Have at least flashed my phone 15 times in last two days trying almost all method
Sent from my XT1052 using XDA Free mobile app

sroy001 said:
I was indeed able to flash 5.1 image through latest version of rsd lite.. But it still doesn't detect my home WiFi.. It scans all other neighborhood WiFi though
So went back to stock 4.4.4 through fastboot and WiFi is back.. Quite strange but now I'm pissed of trying.. Have at least flashed my phone 15 times in last two days trying almost all method
Sent from my XT1052 using XDA Free mobile app
Click to expand...
Click to collapse
That's weird.. Have you tried resetting the router?

can you please share the 5.1 firmware for asia retail?

athulele said:
That's weird.. Have you tried resetting the router?
Click to expand...
Click to collapse
OMG!! Here I was flashing factory images going back and forth and simply resetting the router worked! So silly of me.. Thanks bud.. I'm now on stock 5.1 Asia retail and all working great
Sent from my XT1052 using XDA Free mobile app

koolguy366 said:
can you please share the 5.1 firmware for asia retail?
Click to expand...
Click to collapse
Here you go!
https://mega.nz/#!SVZ3XJTT!POchMYI96ZTy16M_PGSZ4aIjo6ktpaHKaJAmp6XBUR4
Sent from my XT1052 using XDA Free mobile app

sroy001 said:
OMG!! Here I was flashing factory images going back and forth and simply resetting the router worked! So silly of me.. Thanks bud.. I'm now on stock 5.1 Asia retail and all working great
Sent from my XT1052 using XDA Free mobile app
Click to expand...
Click to collapse
Heh, that's good.

sroy001 said:
Here you go!
https://mega.nz/#!SVZ3XJTT!POchMYI96ZTy16M_PGSZ4aIjo6ktpaHKaJAmp6XBUR4
Sent from my XT1052 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks dude, BTW how u flashed it? RSD lite?

koolguy366 said:
Thanks dude, BTW how u flashed it? RSD lite?
Click to expand...
Click to collapse
You can use RSD lite.. I flashed through Fastboot.. It's same thing
Sent from my XT1052 using XDA Free mobile app

Need a hand fixing my bootloop

Hello.
I am hoping some kind soul out there could help me solve my boot looping issue. I have been following the instructions from the mega-thread and have successfully managed to unlock the boot loader. However I also managed to get stuck in a boot loop. As such I have been reading up on Chapter 4 of the mega-thread but I have been unable to fix it.
Phone info:
Code:
Dual sim
Model number
- ALE-L21
Build Number
- ALE-L21C432B200
Android version
- 5.0.1
Android Security Patch Level
- 1 March 2016
Baseband Version
- 22.126.21.00.00
- 22.126.21.00.00
Kernel Version
- 3.10.61-gcd3fde7-dirty
- [email protected] #2
- Wed May 18 22:24:39 CST 2016
EMUI Version
- EMUI3.1
Console results:
Code:
C:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (21706 KB)...
OKAY [ 0.554s]
writing 'boot'...
OKAY [ 0.622s]
finished. total time: 1.178s
C:\adb>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (218981 KB)...
OKAY [ 5.529s]
writing 'cust'...
OKAY [ 3.545s]
finished. total time: 9.077s
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (34280 KB)...
OKAY [ 0.872s]
writing 'recovery'...
OKAY [ 0.979s]
finished. total time: 1.853s
C:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460798 KB)...
OKAY [ 12.767s]
writing 'system'...
OKAY [ 7.406s]
sending sparse 'system' (460385 KB)...
OKAY [ 12.957s]
writing 'system'...
OKAY [ 7.476s]
sending sparse 'system' (460747 KB)...
OKAY [ 12.980s]
writing 'system'...
OKAY [ 7.473s]
sending sparse 'system' (457010 KB)...
OKAY [ 12.907s]
writing 'system'...
OKAY [ 7.423s]
sending sparse 'system' (443304 KB)...
OKAY [ 12.394s]
writing 'system'...
OKAY [ 7.186s]
finished. total time: 100.983s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.023s
I have flashed with both the dual and single sim files provided in the mega-thread. Neither solves my boot loop problem. How do I proceed from here?
Thank you.

try with C432B170 file... that may help

amageek said:
try with C432B170 file... that may help
Click to expand...
Click to collapse
Thank you for your suggestion. I grabbed the update.app file for HUAWEI_ALE-L21_C432B170_Firmware_Western Europe_Channel-Others_Android 5.0_EMUI 3.1_05012XFU and extracted the BOOT.img, CUST.img, RECOVERY.img and SYSTEM.img with the HuaweiUpdateExtractor. After which I flashed my device again, console results:
Code:
C:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (22796 KB)...
OKAY [ 0.582s]
writing 'boot'...
OKAY [ 0.650s]
finished. total time: 1.234s
C:\adb>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (244905 KB)...
OKAY [ 6.196s]
writing 'cust'...
OKAY [ 3.977s]
finished. total time: 10.175s
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (31630 KB)...
OKAY [ 0.807s]
writing 'recovery'...
OKAY [ 0.903s]
finished. total time: 1.712s
C:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460798 KB)...
OKAY [ 12.539s]
writing 'system'...
OKAY [ 7.464s]
sending sparse 'system' (459817 KB)...
OKAY [ 12.749s]
writing 'system'...
OKAY [ 7.425s]
sending sparse 'system' (455915 KB)...
OKAY [ 12.435s]
writing 'system'...
OKAY [ 7.380s]
sending sparse 'system' (444418 KB)...
OKAY [ 12.311s]
writing 'system'...
OKAY [ 7.180s]
sending sparse 'system' (460198 KB)...
OKAY [ 12.624s]
writing 'system'...
OKAY [ 7.391s]
sending sparse 'system' (49397 KB)...
OKAY [ 1.378s]
writing 'system'...
OKAY [ 0.809s]
finished. total time: 101.698s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.024s
C:\adb>
However it did not end the boot loop sequence. I am presented with the logo then straight into a black screen. After 2 or 3 minutes the device reboots.
Did I do it incorrectly?

may be you didn't flashed in correct order??
try once this sequence:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cust cust.img
fastboot flash system system.img

amageek said:
may be you didn't flashed in correct order??
try once this sequence:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cust cust.img
fastboot flash system system.img
Click to expand...
Click to collapse
Console results:
Code:
C:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (22796 KB)...
OKAY [ 0.583s]
writing 'boot'...
OKAY [ 0.645s]
finished. total time: 1.231s
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (31630 KB)...
OKAY [ 0.805s]
writing 'recovery'...
OKAY [ 0.896s]
finished. total time: 1.704s
C:\adb>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (244905 KB)...
OKAY [ 6.192s]
writing 'cust'...
OKAY [ 3.968s]
finished. total time: 10.162s
C:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460798 KB)...
OKAY [ 12.667s]
writing 'system'...
OKAY [ 7.465s]
sending sparse 'system' (459817 KB)...
OKAY [ 12.933s]
writing 'system'...
OKAY [ 7.410s]
sending sparse 'system' (455915 KB)...
OKAY [ 12.644s]
writing 'system'...
OKAY [ 7.389s]
sending sparse 'system' (444418 KB)...
OKAY [ 12.462s]
writing 'system'...
OKAY [ 7.152s]
sending sparse 'system' (460198 KB)...
OKAY [ 12.775s]
writing 'system'...
OKAY [ 7.406s]
sending sparse 'system' (49397 KB)...
OKAY [ 1.403s]
writing 'system'...
OKAY [ 0.805s]
finished. total time: 102.527s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.023s
Still no luck through, however the reboot cycle is much faster if that means anything.
I transferred the dload folder onto a SD card in order to restore. Holding down the volume up and down buttons along with power for 12 seconds. While the device does vibrate as if command was accepted it never shows anything beyond the logo.
Do you have any further advice or an idea as to what is my device's problem?

can you go to recovery? if yes, then you can wipe everything again and see if that helps..

3 key methods that try to install with stock recovery. Update.app file copy to dload folder.
Marcolomboss

amageek said:
can you go to recovery? if yes, then you can wipe everything again and see if that helps..
Click to expand...
Click to collapse
I have attempted this however nothing shows when holding down both volume and power buttons. The phone does vibrate as if the phone accepted the recovery mode command yet the screen stays black.
marcolomboss said:
3 key methods that try to install with stock recovery. Update.app file copy to dload folder.
Marcolomboss
Click to expand...
Click to collapse
I have also attempted this. I loaded my 32gb SD card with "HUAWEI_ALE-L21_C432B170_Firmware_Western Europe_Channel-Others_Android 5.0_EMUI 3.1_05012XFU" update.app file. As previously stated trying to enter recovery mode however is not successful despite the phone vibrates as if it was.
Please advise. Thank you.

YetAnotherP8Owner said:
I have attempted this however nothing shows when holding down both volume and power buttons. The phone does vibrate as if the phone accepted the recovery mode command yet the screen stays black.
I have also attempted this. I loaded my 32gb SD card with "HUAWEI_ALE-L21_C432B170_Firmware_Western Europe_Channel-Others_Android 5.0_EMUI 3.1_05012XFU" update.app file. As previously stated trying to enter recovery mode however is not successful despite the phone vibrates as if it was.
Please advise. Thank you.
Click to expand...
Click to collapse
any update.app file "Huawei Update Extractor" Open the program. After flashed in the recovery.img file. Sorry for bad english
Marcolomboss

YetAnotherP8Owner said:
Hello.
I am hoping some kind soul out there could help me solve my boot looping issue. I have been following the instructions from the mega-thread and have successfully managed to unlock the boot loader. However I also managed to get stuck in a boot loop. As such I have been reading up on Chapter 4 of the mega-thread but I have been unable to fix it.
Phone info:
Code:
Dual sim
Model number
- ALE-L21
Build Number
- ALE-L21C432B200
Android version
- 5.0.1
Android Security Patch Level
- 1 March 2016
Baseband Version
- 22.126.21.00.00
- 22.126.21.00.00
Kernel Version
- 3.10.61-gcd3fde7-dirty
- [email protected] #2
- Wed May 18 22:24:39 CST 2016
EMUI Version
- EMUI3.1
Console results:
Code:
C:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (21706 KB)...
OKAY [ 0.554s]
writing 'boot'...
OKAY [ 0.622s]
finished. total time: 1.178s
C:\adb>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (218981 KB)...
OKAY [ 5.529s]
writing 'cust'...
OKAY [ 3.545s]
finished. total time: 9.077s
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (34280 KB)...
OKAY [ 0.872s]
writing 'recovery'...
OKAY [ 0.979s]
finished. total time: 1.853s
C:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460798 KB)...
OKAY [ 12.767s]
writing 'system'...
OKAY [ 7.406s]
sending sparse 'system' (460385 KB)...
OKAY [ 12.957s]
writing 'system'...
OKAY [ 7.476s]
sending sparse 'system' (460747 KB)...
OKAY [ 12.980s]
writing 'system'...
OKAY [ 7.473s]
sending sparse 'system' (457010 KB)...
OKAY [ 12.907s]
writing 'system'...
OKAY [ 7.423s]
sending sparse 'system' (443304 KB)...
OKAY [ 12.394s]
writing 'system'...
OKAY [ 7.186s]
finished. total time: 100.983s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.023s
I have flashed with both the dual and single sim files provided in the mega-thread. Neither solves my boot loop problem. How do I proceed from here?
Thank you.
Click to expand...
Click to collapse
try with vers.c432b132,flash in this order:
boot
recovery
cust
system
if is work,your imei will be null,in that case just update to a higher version(ex.c432b170)

marcolomboss said:
any update.app file "Huawei Update Extractor" Open the program. After flashed in the recovery.img file. Sorry for bad english
Marcolomboss
Click to expand...
Click to collapse
I am not sure I'm following what you are trying to convey. I have already flashed the recovery.img file with various firmware versions with no luck. Do you have a specific firmware version in mind?
cristi.blidariu said:
try with vers.c432b132,flash in this order:
boot
recovery
cust
system
if is work,your imei will be null,in that case just update to a higher version(ex.c432b170)
Click to expand...
Click to collapse
Fetched 'ALE-L21 C432B132 Europe channel Dual' and flashed as ordered. Black screen still occur. Recovery mode is still not responding.
Console results:
Code:
C:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (21708 KB)...
OKAY [ 0.553s]
writing 'boot'...
OKAY [ 0.619s]
finished. total time: 1.174s
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (34282 KB)...
OKAY [ 0.873s]
writing 'recovery'...
OKAY [ 0.969s]
finished. total time: 1.844s
C:\adb>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (257901 KB)...
OKAY [ 6.520s]
writing 'cust'...
OKAY [ 4.174s]
finished. total time: 10.697s
C:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460798 KB)...
OKAY [ 12.720s]
writing 'system'...
OKAY [ 7.479s]
sending sparse 'system' (446518 KB)...
OKAY [ 12.505s]
writing 'system'...
OKAY [ 7.221s]
sending sparse 'system' (457326 KB)...
OKAY [ 12.749s]
writing 'system'...
OKAY [ 7.369s]
sending sparse 'system' (459322 KB)...
OKAY [ 12.890s]
writing 'system'...
OKAY [ 7.427s]
sending sparse 'system' (460740 KB)...
OKAY [ 12.818s]
writing 'system'...
OKAY [ 7.433s]
sending sparse 'system' (1124 KB)...
OKAY [ 0.037s]
writing 'system'...
OKAY [ 0.027s]
finished. total time: 100.690s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.024s
Is there a reason why I can not enter recovery mode? What causes this issue that is preventing me from doing a recovery?
Thank you for your answers so far.

very interesting. You're in the wrong place, but where
Marcolomboss

YetAnotherP8Owner said:
I am not sure I'm following what you are trying to convey. I have already flashed the recovery.img file with various firmware versions with no luck. Do you have a specific firmware version in mind?
Fetched 'ALE-L21 C432B132 Europe channel Dual' and flashed as ordered. Black screen still occur. Recovery mode is still not responding.
Console results:
Code:
C:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (21708 KB)...
OKAY [ 0.553s]
writing 'boot'...
OKAY [ 0.619s]
finished. total time: 1.174s
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (34282 KB)...
OKAY [ 0.873s]
writing 'recovery'...
OKAY [ 0.969s]
finished. total time: 1.844s
C:\adb>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (257901 KB)...
OKAY [ 6.520s]
writing 'cust'...
OKAY [ 4.174s]
finished. total time: 10.697s
C:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460798 KB)...
OKAY [ 12.720s]
writing 'system'...
OKAY [ 7.479s]
sending sparse 'system' (446518 KB)...
OKAY [ 12.505s]
writing 'system'...
OKAY [ 7.221s]
sending sparse 'system' (457326 KB)...
OKAY [ 12.749s]
writing 'system'...
OKAY [ 7.369s]
sending sparse 'system' (459322 KB)...
OKAY [ 12.890s]
writing 'system'...
OKAY [ 7.427s]
sending sparse 'system' (460740 KB)...
OKAY [ 12.818s]
writing 'system'...
OKAY [ 7.433s]
sending sparse 'system' (1124 KB)...
OKAY [ 0.037s]
writing 'system'...
OKAY [ 0.027s]
finished. total time: 100.690s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.024s
Is there a reason why I can not enter recovery mode? What causes this issue that is preventing me from doing a recovery?
Thank you for your answers so far.
Click to expand...
Click to collapse
i have upload boot.img from aosap and twrp recovery here
https://mega.nz/#!3U1WwKRA!N2rNjghUugSSHtKDnbAzP1Xy4OlkI9CtyXz0jDxRBog
download,extract and flash boot and recovery,once you done,don't use command fastboot reboot,press and hold volume up for about 10 sec.,it will restart in erecovery,from there choose shutdown option,when your phone is complete shutdown press and hold volume up and power key,when you see the huawei logo,release the power key but keep press volume up until you enter in recovery,once there(if is work) wipe all

cristi.blidariu said:
i have upload boot.img from aosap and twrp recovery here
https://mega.nz/#!3U1WwKRA!N2rNjghUugSSHtKDnbAzP1Xy4OlkI9CtyXz0jDxRBog
download,extract and flash boot and recovery,once you done,don't use command fastboot reboot,press and hold volume up for about 10 sec.,it will restart in erecovery,from there choose shutdown option,when your phone is complete shutdown press and hold volume up and power key,when you see the huawei logo,release the power key but keep press volume up until you enter in recovery,once there(if is work) wipe all
Click to expand...
Click to collapse
Flashed with the provided images; console results:
Code:
C:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (24064 KB)...
OKAY [ 0.613s]
writing 'boot'...
OKAY [ 0.381s]
finished. total time: 0.996s
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (27062 KB)...
OKAY [ 0.689s]
writing 'recovery'...
OKAY [ 0.440s]
finished. total time: 1.131s
C:\adb>
After holding down volume up button for 10 seconds I am presented with the 'Huawei eRecovery' mode. It gives me three options of "Reboot", "Download new version and recovery" and "Shutdown". I choose shutdown and wait for the phone to appear completely off after 5 seconds or so. Which after I hold down volume down, volume up and power buttons to enter the recovery mode. The phone vibrates as expected however no recovery mode is shown. Black screen still appears.
Please advise and thank you.

YetAnotherP8Owner said:
Flashed with the provided images; console results:
After holding down volume up button for 10 seconds I am presented with the 'Huawei eRecovery' mode. It gives me three options of "Reboot", "Download new version and recovery" and "Shutdown". I choose shutdown and wait for the phone to appear completely off after 5 seconds or so. Which after I hold down volume down, volume up and power buttons to enter the recovery mode. The phone vibrates as expected however no recovery mode is shown. Black screen still appears.
Please advise and thank you.
Click to expand...
Click to collapse
To enter the recovery mode you need to press and hold volume up and power buttons only

YetAnotherP8Owner said:
Flashed with the provided images; console results:
Code:
C:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (24064 KB)...
OKAY [ 0.613s]
writing 'boot'...
OKAY [ 0.381s]
finished. total time: 0.996s
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (27062 KB)...
OKAY [ 0.689s]
writing 'recovery'...
OKAY [ 0.440s]
finished. total time: 1.131s
C:\adb>
After holding down volume up button for 10 seconds I am presented with the 'Huawei eRecovery' mode. It gives me three options of "Reboot", "Download new version and recovery" and "Shutdown". I choose shutdown and wait for the phone to appear completely off after 5 seconds or so. Which after I hold down volume down, volume up and power buttons to enter the recovery mode. The phone vibrates as expected however no recovery mode is shown. Black screen still appears.
Please advise and thank you.
Click to expand...
Click to collapse
read all my friend and do as i say:
download,extract and flash boot and recovery,once you done,don't use command fastboot reboot,press and hold volume up for about 10 sec.,it will restart in erecovery,from there choose shutdown option,when your phone is complete shutdown press and hold volume up and power key,when you see the huawei logo,release the power key but keep press volume up until you enter in recovery,once there(if is work) wipe all

cristi.blidariu said:
read all my friend and do as i say:
download,extract and flash boot and recovery,once you done,don't use command fastboot reboot,press and hold volume up for about 10 sec.,it will restart in erecovery,from there choose shutdown option,when your phone is complete shutdown press and hold volume up and power key,when you see the huawei logo,release the power key but keep press volume up until you enter in recovery,once there(if is work) wipe all
Click to expand...
Click to collapse
I apologize, I misread the instructions.
After the complete shutdown, I held down volume up and power button. Upon seeing the Huawei logo, I let go of the power button. After a few seconds, the screen goes blank, then booted into 'Huawei eRecovery' mode and presented with the same options as before. "Reboot", "Download new version and recovery" and "Shutdown".
Am I to choose "Download new version and recovery" option from this screen?

YetAnotherP8Owner said:
I apologize, I misread the instructions.
After the complete shutdown, I held down volume up and power button. Upon seeing the Huawei logo, I let go of the power button. After a few seconds, the screen goes blank, then booted into 'Huawei eRecovery' mode and presented with the same options as before. "Reboot", "Download new version and recovery" and "Shutdown".
Am I to choose "Download new version and recovery" option from this screen?
Click to expand...
Click to collapse
No,that not gone help at all,please try again to shutdown your phone and do the same think with volume up and power key,if is not gone boot in to recovery try again to flash but this time flash stock recovery
Sent from my ALE-L21 using XDA-Developers mobile app

cristi.blidariu said:
No,that not gone help at all,please try again to shutdown your phone and do the same think with volume up and power key,if is not gone boot in to recovery try again to flash but this time flash stock recovery
Sent from my ALE-L21 using XDA-Developers mobile app
Click to expand...
Click to collapse
I attempted flashing with the provided files again, boot then recovery. I did not use 'fastboot reboot' command but instead held in the volume up button for 10 seconds until 'Huawei eRecovery' mode appeared. I chose shutdown, waited for the phone to completely shut off upon which I then held in volume up and power buttons. Soon as the Huawei logo appears, I let go of the power button and continued to hold in volume up. Once more I was presented with 'Huawei eRecovery' and three options of "Reboot", "Download new version and recovery" and shutdown.
I did notice if I disconnect the phone before attempting to enter recovery mode by holding in volume up and power buttons, instead of shown 'Huawei eRecovery' the screen stays blank as recovery mode is still not responding.
What is the command to flash the stock recovery image? 'fastboot flash stockrecovery'? And with what image should I flash it with?

YetAnotherP8Owner said:
I attempted flashing with the provided files again, boot then recovery. I did not use 'fastboot reboot' command but instead held in the volume up button for 10 seconds until 'Huawei eRecovery' mode appeared. I chose shutdown, waited for the phone to completely shut off upon which I then held in volume up and power buttons. Soon as the Huawei logo appears, I let go of the power button and continued to hold in volume up. Once more I was presented with 'Huawei eRecovery' and three options of "Reboot", "Download new version and recovery" and shutdown.
I did notice if I disconnect the phone before attempting to enter recovery mode by holding in volume up and power buttons, instead of shown 'Huawei eRecovery' the screen stays blank as recovery mode is still not responding.
What is the command to flash the stock recovery image? 'fastboot flash stockrecovery'? And with what image should I flash it with?
Click to expand...
Click to collapse
You can extract from any firmware stock recovery using huawei update extractor,what i gave you is a custom recovery,the command is fastboot flash recovery recovery.img
Sent from my ALE-L21 using XDA-Developers mobile app

Question Help restoring Stock ROM [SOLVED]

So... I tried to unlock/root my Redmi Note 11 (SPES), and something went wrong. So now I am trying to fix it, restore to the stock ROM to try again.
How I broke it:
1. Unlocked the bootloader.
2. Installed probably the wrong TWRP (I installed twrp-3.6.2-12.1-21.06.22.img from https://razaoinfo.dl.sourceforge.ne...ld/Recovery-Spes/twrp-3.6.2-12.1-21.06.22.img )
3. I tried flashing said img using fastboot (fastboot flash recovery_a <img>, followed by fastboot flash recovery_b <img>, then fastboot boot <img>
4. Got into TWRP, flashed Magisk.
5. Got into ROM. Everything seems to work, I have root. Next day, I realize my bluetooth is not working.
Next day, I tried flashing another TWRP that I found linked in this forum (twrp-3.6.2_12-0-spes-Jabiyeff.img, downloaded from https://forum.xda-developers.com/t/...-redmi-note-11-and-how-do-i-flash-it.4466177/ post #4).
6. After flashing, ROM no longer boots, and just sends me to fastboot.
7. I checked again with fastboot, and.. it seems the recovery partition isn't there?
Code:
C:\adb2>fastboot.exe devices
ff23ad4 fastboot
C:\adb2>fastboot.exe flash recovery twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 796917760 bytes
sending 'recovery' (131072 KB)...
OKAY [ 2.902s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 2.909s
C:\adb2>fastboot.exe flash recovery_a twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 796917760 bytes
sending 'recovery_a' (131072 KB)...
OKAY [ 2.828s]
writing 'recovery_a'...
FAILED (remote: (recovery_a_b) No such partition)
finished. total time: 2.835s
C:\adb2>fastboot.exe flash recovery_b twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 796917760 bytes
sending 'recovery_b' (131072 KB)...
OKAY [ 2.805s]
writing 'recovery_b'...
FAILED (remote: (recovery_b_b) No such partition)
finished. total time: 2.812s
C:\adb2>fastboot.exe flash recovery twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 796917760 bytes
sending 'recovery' (131072 KB)...
OKAY [ 2.849s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 2.857s
C:\adb2>fastboot.exe boot twrp-3.6.2_12-0-spes-Jabiyeff.img #NOTE: Here I changed the active partition in this TWRP from B to A.
downloading 'boot.img'...
OKAY [ 2.790s]
booting...
OKAY [ 0.367s]
finished. total time: 3.159s
C:\adb2>fastboot.exe devices
ff23ad4 fastboot
C:\adb2>fastboot.exe flash recovery twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 268435456 bytes
sending 'recovery' (131072 KB)...
OKAY [ 2.933s]
writing 'recovery'...
FAILED (remote: No such file or directory)
finished. total time: 2.946s
C:\adb2>fastboot.exe flash recovery_a twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 268435456 bytes
sending 'recovery_a' (131072 KB)...
OKAY [ 2.899s]
writing 'recovery_a'...
FAILED (remote: No such file or directory)
finished. total time: 2.918s
C:\adb2>fastboot.exe flash recovery_b twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 268435456 bytes
sending 'recovery_b' (131072 KB)...
OKAY [ 2.931s]
writing 'recovery_b'...
FAILED (remote: No such file or directory)
finished. total time: 2.943s
C:\adb2>fastboot.exe flash recovery twrp-3.6.2_12-0-spes-Jabiyeff.img
target reported max download size of 268435456 bytes
sending 'recovery' (131072 KB)...
OKAY [ 2.874s]
writing 'recovery'...
FAILED (remote: No such file or directory)
finished. total time: 2.887s
So, I wonder if I should be concerned about not finding a recovery/recovery_a/recovery_b partition (I am pretty sure recovery_a/b where there when I flashed TWRP the first time).
So, I am following now this guide to install the stock ROM: https://xiaomistockrom.com/xiaomi-redmi-note-11
Am I on the right path? I want to check before proceeding, because... right now I have fast boot and can boot into TWRP using it, but if I do things incorrectly from now on, I could brick the device. So I wanted to ask for advice on what I am doing first here.
TIA.

It's fairly difficult to hard brick a device. Most of the time you'll just end up soft bricking your device which is easy to fix as long as you can access bootloader mode. If you want to fully restore your device to default, you can download your stock rom (fastboot version) and flash using miflash.
Also yes, the guide you linked is correct.

Thanks, I managed to solve it.
The fastboot issue went away some time afterwards, and I could boot normally into the ROM, but... my bluetooth stopped working (which is really strange considering I only flashed the recovery partition). I tried flashing the bluetooth partition from the stock ROM's, but that didn't fix it.
So I tried flashing the stock ROM, following the previously linked guide (and that guide, not the guides that came bundled in the downloaded ROM, that one was for a different device, not a Xiaomi phone at all, weird!).
And now, I have bluetooth again. Thanks goodness for Migrate, I should be able to restore the rest of the device swiftly now.

How To Guide [STABLE/STOCK/GSI - Android 13] Redmi Note 10 5G (camellian) + Magisk (NO TWRP)

How to flash Google/Pixel Stock Stable Android 13 on Xiaomi Redmi Note 10 5G (in my case camellian) from any MIUI or any GSI rom without custom recoveries:
Download stock (original/unmodified) boot.img from your current MIUI Version
Download LATEST platform-tools (ADB + FASTBOOT) from Google
Download Magisk (in my case Alpha version works best on newer Androids)
Download Android 13 (stable) GSI (ARM64+GMS - Gapps version) from Google:
-- ARM64 without GMS (Gapps) also works, but upon installing Gapps manually I've gotten Bootloops (I tried serveral versions & Magisk Flashable too)
-- After downloading the GSI, extract system.img (you will be flashing this image) and vbmeta.img (and this image)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Place stock boot.img with downloaded system.img and vbmeta.img in the platform-tools folder
Run CMD in platform-tools folder (by typing CMD in address bar and hitting ENTER) and connect your phone (OFC enable USB debugging)
Run following adb / fastboot commands:
Boot phone in fastbootD (important)
Code:
C:\adb\platform-tools>adb reboot bootloader
C:\adb\platform-tools>fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.001s]
< waiting for any device >
Finished. Total time: 12.820s
When booted in fastbootD run:
Code:
C:\adb\platform-tools>fastboot set_active a
Setting current slot to 'a' OKAY [ 0.022s]
Finished. Total time: 0.028s
C:\adb\platform-tools>fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta_a' (4 KB) OKAY [ 0.002s]
Writing 'vbmeta_a' OKAY [ 0.006s]
Finished. Total time: 0.050s
C:\adb\platform-tools>fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta_a' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_a' OKAY [ 0.003s]
Finished. Total time: 0.044s
C:\adb\platform-tools>fastboot --disable-verity --disable-verification flash vbmeta_b vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta_b' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_b' OKAY [ 0.003s]
Finished. Total time: 0.043s
C:\adb\platform-tools>fastboot flash system system.img
Resizing 'system_a' OKAY [ 0.014s]
Sending sparse 'system_a' 1/12 (262108 KB) OKAY [ 10.316s]
Writing 'system_a' OKAY [ 1.183s]
Sending sparse 'system_a' 2/12 (262120 KB) OKAY [ 10.677s]
Writing 'system_a' OKAY [ 1.087s]
Sending sparse 'system_a' 3/12 (262104 KB) OKAY [ 10.270s]
Writing 'system_a' OKAY [ 0.953s]
Sending sparse 'system_a' 4/12 (262124 KB) OKAY [ 10.131s]
Writing 'system_a' OKAY [ 1.040s]
Sending sparse 'system_a' 5/12 (262124 KB) OKAY [ 10.749s]
Writing 'system_a' OKAY [ 1.083s]
Sending sparse 'system_a' 6/12 (262124 KB) OKAY [ 11.126s]
Writing 'system_a' OKAY [ 1.082s]
Sending sparse 'system_a' 7/12 (262124 KB) OKAY [ 10.528s]
Writing 'system_a' OKAY [ 1.045s]
Sending sparse 'system_a' 8/12 (262128 KB) OKAY [ 10.397s]
Writing 'system_a' OKAY [ 0.947s]
Sending sparse 'system_a' 9/12 (262088 KB) OKAY [ 10.333s]
Writing 'system_a' OKAY [ 1.207s]
Sending sparse 'system_a' 10/12 (262120 KB) OKAY [ 10.717s]
Writing 'system_a' OKAY [ 1.027s]
Sending sparse 'system_a' 11/12 (243488 KB) OKAY [ 9.380s]
Writing 'system_a' OKAY [ 1.433s]
Sending sparse 'system_a' 12/12 (46444 KB) OKAY [ 1.797s]
Writing 'system_a' OKAY [ 0.336s]
Finished. Total time: 139.687s
C:\adb\platform-tools>fastboot flash boot boot.img
Sending 'boot_a' (65536 KB) OKAY [ 2.486s]
Writing 'boot_a' OKAY [ 0.337s]
Finished. Total time: 2.858s
C:\adb\platform-tools>fastboot flash boot_a boot.img
Sending 'boot_a' (65536 KB) OKAY [ 2.340s]
Writing 'boot_a' OKAY [ 0.314s]
Finished. Total time: 2.690s
C:\adb\platform-tools>fastboot flash boot_b boot.img
Sending 'boot_b' (65536 KB) OKAY [ 2.321s]
Writing 'boot_b' OKAY [ 0.317s]
Finished. Total time: 2.671s
Now Reboot to Recovery and WIPE DATA
Code:
C:\adb\platform-tools>fastboot reboot recovery
Rebooting into recovery OKAY [ 0.001s]
Finished. Total time: 0.007s
Reboot and done!
My opinion after one day:
If u like alot of customization it's not for you, you have to install even most basic apps let it's completly stock. But battery life is improved by 35-50% !! I'm using it for over 15 hours and still 30% battery left. Google Cam works great. Performance amazing. Few bugs here and there in the UI but overall pretty stable.
Anyway not a daily driver for everyone yet, needs a bit more polish. Enjoy !!

This looks good. Will it work for camellia?
If u like alot of customization it's not for you, you have to install even most basic apps let it's completly stock.
Click to expand...
Click to collapse
That's the reason I'm still on MIUI. Small things like network speed in status bar is very important to me.

sajalkmr said:
This looks good. Will it work for camellia?
That's the reason I'm still on MIUI. Small things like network speed in status bar is very important to me.
Click to expand...
Click to collapse
I am not sure as I don't have one to test it on, but I don't see why it wouldn't; all other GSI's work so. .
Have in mind that it looks good because of the Lawnchair Launcher (god bless the developer of it, i'm using it over 5 years), otherwise you will get the most basic stock functional android quickstep launcher.

Nice wallpaper. Can you share where I can find it?

iijul said:
Nice wallpaper. Can you share where I can find it?
Click to expand...
Click to collapse
Reddit - Dive into anything
www.reddit.com

iijul said:
Nice wallpaper. Can you share where I can find it?
Click to expand...
Click to collapse
Credit to Mia

What about NFC and Bluetooth working or not?

Kubusi3kk said:
What about NFC and Bluetooth working or not?
Click to expand...
Click to collapse
Yep

Hi,
I just tried this procedure with the latest beta build (Android 13 QPR1 BETA) and it does not boot (it restarts by itself every 30s), I switched back to Lineage OS 19.1
Am I the only one having this problem?
Thanks

doesnt work cannot make calls

NewXiaomiUser said:
Hi,
I just tried this procedure with the latest beta build (Android 13 QPR1 BETA) and it does not boot (it restarts by itself every 30s), I switched back to Lineage OS 19.1
Am I the only one having this problem?
Thanks
Click to expand...
Click to collapse
im having the same problem, can you link me a guide to installing los 19.1?

log:
H:\platform-tools_r33.0.3-windows\platform-tools>fastboot devices
dafi8dfurkmz9dau fastboot
H:\platform-tools_r33.0.3-windows\platform-tools>fastboot set_active a
Setting current slot to 'a' OKAY [ 0.008s]
Finished. Total time: 0.009s
H:\platform-tools_r33.0.3-windows\platform-tools>fastboot --disable-verity --disable-verification flash vbmeta "H:\platform-tools_r33.0.3-windows\platform-tools\vbmeta.img"
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta_a' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta_a' OKAY [ 0.003s]
Finished. Total time: 0.130s
H:\platform-tools_r33.0.3-windows\platform-tools>fastboot --disable-verity --disable-verification flash vbmeta_ "H:\platform-tools_r33.0.3-windows\platform-tools\vbmeta.img"
Sending 'vbmeta_' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
H:\platform-tools_r33.0.3-windows\platform-tools>fastboot --disable-verity --disable-verification flash vbmeta_ "H:\platform-tools_r33.0.3-windows\platform-tools\vbmeta.img"
Sending 'vbmeta_' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
H:\platform-tools_r33.0.3-windows\platform-tools>fastboot --disable-verity --disable-verification flash vbmeta_a "H:\platform-tools_r33.0.3-windows\platform-tools\vbmeta.img"
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta_a' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_a' OKAY [ 0.003s]
Finished. Total time: 0.013s
H:\platform-tools_r33.0.3-windows\platform-tools>fastboot --disable-verity --disable-verification flash vbmeta_b "H:\platform-tools_r33.0.3-windows\platform-tools\vbmeta.img"
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta_b' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_b' OKAY [ 0.003s]
Finished. Total time: 0.013s
H:\platform-tools_r33.0.3-windows\platform-tools>fastboot flash system "H:\platform-tools_r33.0.3-windows\platform-tools\system.img"
Resizing 'system_a' OKAY [ 0.010s]
Sending sparse 'system_a' 1/12 (262112 KB) OKAY [ 10.126s]
Writing 'system_a' OKAY [ 1.159s]
Sending sparse 'system_a' 2/12 (262120 KB) OKAY [ 9.476s]
Writing 'system_a' OKAY [ 1.118s]
Sending sparse 'system_a' 3/12 (262112 KB) OKAY [ 9.404s]
Writing 'system_a' OKAY [ 1.213s]
Sending sparse 'system_a' 4/12 (262124 KB) OKAY [ 10.100s]
Writing 'system_a' OKAY [ 1.080s]
Sending sparse 'system_a' 5/12 (262128 KB) OKAY [ 9.308s]
Writing 'system_a' OKAY [ 1.295s]
Sending sparse 'system_a' 6/12 (262124 KB) OKAY [ 9.395s]
Writing 'system_a' OKAY [ 1.147s]
Sending sparse 'system_a' 7/12 (262128 KB) OKAY [ 9.416s]
Writing 'system_a' OKAY [ 1.049s]
Sending sparse 'system_a' 8/12 (262120 KB) OKAY [ 9.430s]
Writing 'system_a' OKAY [ 1.260s]
Sending sparse 'system_a' 9/12 (262088 KB) OKAY [ 10.616s]
Writing 'system_a' OKAY [ 1.113s]
Sending sparse 'system_a' 10/12 (262120 KB) OKAY [ 9.648s]
Writing 'system_a' OKAY [ 1.034s]
Sending sparse 'system_a' 11/12 (260716 KB) OKAY [ 9.342s]
Writing 'system_a' OKAY [ 1.360s]
Sending sparse 'system_a' 12/12 (46712 KB) OKAY [ 1.690s]
Writing 'system_a' OKAY [ 0.308s]
Finished. Total time: 196.646s
H:\platform-tools_r33.0.3-windows\platform-tools>
H:\platform-tools_r33.0.3-windows\platform-tools>fastboot flash boot "H:\platform-tools_r33.0.3-windows\platform-tools\boot.img"
Sending 'boot_a' (65536 KB) OKAY [ 2.401s]
Writing 'boot_a' OKAY [ 0.316s]
Finished. Total time: 2.746s
H:\platform-tools_r33.0.3-windows\platform-tools>fastboot flash boot_a "H:\platform-tools_r33.0.3-windows\platform-tools\boot.img"
Sending 'boot_a' (65536 KB) OKAY [ 2.414s]
Writing 'boot_a' OKAY [ 0.308s]
Finished. Total time: 2.747s
H:\platform-tools_r33.0.3-windows\platform-tools>fastboot flash boot_b "H:\platform-tools_r33.0.3-windows\platform-tools\boot.img"
Sending 'boot_b' (65536 KB) OKAY [ 2.429s]
Writing 'boot_b' OKAY [ 0.309s]
Finished. Total time: 2.764s
H:\platform-tools_r33.0.3-windows\platform-tools>fastboot reboot recovery
Rebooting into recovery OKAY [ 0.000s]
Finished. Total time: 0.002s
H:\platform-tools_r33.0.3-windows\platform-tools>

Hi TedFin,
sure, here is how I flash back LineageOS 19.1:
First of all, I assume you have the ADB and fastboot drivers installed, you can find guides here and there.
Download LineageOS here:
https://sourceforge.net/projects/andyyan-gsi/files/lineage-19.x/lineage-19.1-20221011-UNOFFICIAL-arm64_bvS.img.xz/download
Download stock firmware here:
https://xiaomifirmwareupdater.com/miui/camellian/stable/V13.0.3.0.SKSEUXM/ (choose Fastboot rom)
Extract the Xiaomi stock firware using 7zip or any other compatible software
Reboot your phone in fastboot mode (long press on volume down while booting)
Open a command prompt on the extracted folder and run
Bash:
flash_all.bat
Once completed, your phone should be back on stock rom
Reboot once again in fastboot mode
Then in cmd:
Go to the LineageOS folder
Bash:
cd /d [the folder where you decompressed lineageos]
Reboot in fastbootd
Bash:
fastboot reboot fastboot
Flash LineageOS
Bash:
fastboot flash system lineage-19.1-20220912-UNOFFICIAL-arm64_bgS.img
fastboot flash system_b lineage-19.1-20220912-UNOFFICIAL-arm64_bgS.img
Clean up
Bash:
fastboot reboot recovery
Wipe all then reboot
If you have a boot loop, reboot in Fastboot
Bash:
fastboot flash boot [the stock rom folder]\images\boot.img
fastboot flash boot_b [the stock rom folder]\images\boot.img
Voila!

NewXiaomiUser said:
Hi,
I just tried this procedure with the latest beta build (Android 13 QPR1 BETA) and it does not boot (it restarts by itself every 30s), I switched back to Lineage OS 19.1
Am I the only one having this problem?
Thanks
Click to expand...
Click to collapse
Do you wipe data at the end before reboot?

Hi, thanks for your response,
yes I did it, I also restore the stock firmware before but it does not change anything

NewXiaomiUser said:
Hi, thanks for your response,
yes I did it, I also restore the stock firmware before but it does not change anything
Click to expand...
Click to collapse
try nother gsi. a question: what stock firmware u have installed? i must start from miui13 because have a12 vendor
second. check the active slot. gsi must be installed into primary
third: flash system without erase system partition
forth: reflash boot stock img before reboot
if your phone dont boot and stuck on logo the problem is boot.img or active slot
if your phone boot into recovery wipe data
the bootloops after flashing gsi are caused by boot.img or data that must be wiped
another thing: FLASH VBMETA DISABLING SECURE VERITY CHECK before reboot
the steps for flash gsi are simply. slect the correct gsi and start from the correct stock is important. mut most important is use your brain. i have flashed at lest 5-6 gsi without problems

Hi,
1. Here is the stock ROM I'm using: camellian_eea_global V13.0.2.0 (SKSEUXM)
2. Active slot is A (anyway, I always flash A and B)
3. System partition is erased when flash stock rom. I do not flash after stock
4. I always flash boot (both A and B) after flashing a GSI, tried with stock boot.img and Magisk's
5. After installing a GSI, I always wipe all data in recovery mode
6. flashing vbmeta is part of your process and, of course, I followed it step by step
The phone is not stuck on logo, it just keep restarting again and again without reaching the OS itself (no boot animation)
By the way, I'm able to flash LineageOS or Pixel Experience using the same procedure works without any quirks, this is the only GSI I'm having problem with.
Thanks

NewXiaomiUser said:
Hi,
1. Here is the stock ROM I'm using: camellian_eea_global V13.0.2.0 (SKSEUXM)
2. Active slot is A (anyway, I always flash A and B)
3. System partition is erased when flash stock rom. I do not flash after stock
4. I always flash boot (both A and B) after flashing a GSI, tried with stock boot.img and Magisk's
5. After installing a GSI, I always wipe all data in recovery mode
6. flashing vbmeta is part of your process and, of course, I followed it step by step
The phone is not stuck on logo, it just keep restarting again and again without reaching the OS itself (no boot animation)
By the way, I'm able to flash LineageOS or Pixel Experience using the same procedure works without any quirks, this is the only GSI I'm having problem with.
Thanks
Click to expand...
Click to collapse
I'll try to give you files and help you when I get on my PC today

Sure, no rush, anyway, LOS is pretty stable except I cannot bypass SafetyNet.
Thanks

NewXiaomiUser said:
Sure, no rush, anyway, LOS is pretty stable except I cannot bypass SafetyNet.
Thanks
Click to expand...
Click to collapse
Sorry I forgot about my post, I'll do it now... As for the Safety Net I highly recommend using Alpha (not official) build of Magisk (pay attention to other builds such as Delta and similar "Alpha" builds everywhere; this Telegram Group link is the one and only trusted place where you can find download link-I'll attach latest version down bellow). Every single problem I had with either stock or modified roms; I solved them when I started using it (except when I overdo it with modules which would be my mistake ofc.). The biggest difference is that it is closed-sourced so there is a risk when using it, but it's being maintained by one of the respected people that worked/works on official Magisk.
Next step is of course installing Universal SafetyNet Fix by kdrag0n.
And finally MagiskHide Props Config By Didgeridoohan. After flashing this one you will have to set it up with any terminal (Termux for example) to spoof your device config so the store thinks you're using - in my case Google Pixel 6 Pro. Also in my case the feature "device emulator - 3rd from above" gave me soft brick so be careful. It's easy to set it up as it guides you via terminal (I use first two options and spoofing as Pixel 6 Pro as I said).
Those things are first things I do on a new rom, and yeah I use LSPosed Framework + Zygisk.
No problems and I'm certified in Google Play/Google Games stores even tho I use modified apks to hack multiplayer games.
I'll go and give you all the files so u can try latest generic GSI by Google if you still want, using this guide.

Question Bricked: Failed to boot into userspace fastboot

Hey there,
a couple of weeks ago I purchased a new smartphone with headphone jack in a reasonable size and it should run LineageOS.
So after a long search, the Zenfone 8 met all requirements.
I wanted to flash LineageOS, but went over several problems. Right now I'm stuck in a fastboot-loop. I cannot describe what I've tried to get things working again, sadly.
Recently I stumbled upon this thread and get stuck in the fastboot loop.
Flashing of boot, dtbo, vendor-boot, vbmeta and vbmeta_system seems to work, but after trying to access fastbootd, I get stuck.
Here's the output:
/run/me/g/s/a/e/payload fastboot flash boot boot.img ✔
Sending 'boot_a' (98304 KB) OKAY [ 2.520s]
Writing 'boot_a' OKAY [ 0.257s]
Finished. Total time: 2.822s
/run/me/g/s/a/e/payload fastboot flash dtbo dtbo.img ✔ 3s
Sending 'dtbo' (8192 KB) OKAY [ 0.212s]
Writing 'dtbo' OKAY [ 0.023s]
Finished. Total time: 0.272s
/run/me/g/s/a/e/payload fastboot flash vendor_boot vendor_boot.img
Sending 'vendor_boot' (98304 KB) OKAY [ 2.514s]
Writing 'vendor_boot' OKAY [ 0.278s]
Finished. Total time: 2.832s
/run/me/g/s/a/e/payload fastboot flash vbmeta vbmeta.img ✔ 3s
Sending 'vbmeta' (8 KB) OKAY [ 0.011s]
Writing 'vbmeta' OKAY [ 0.001s]
Finished. Total time: 0.049s
/run/me/g/s/a/e/payload fastboot flash vbmeta_system vbmeta_system.img
Sending 'vbmeta_system' (4 KB) OKAY [ 0.008s]
Writing 'vbmeta_system' OKAY [ 0.001s]
Finished. Total time: 0.044s
/run/me/g/s/a/e/payload fastboot reboot fastboot ✔
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components
might be unbootable.
I'd be so happy to get this working again.
Thanks in advance!

sonix900 said:
Hey there,
a couple of weeks ago I purchased a new smartphone with headphone jack in a reasonable size and it should run LineageOS.
So after a long search, the Zenfone 8 met all requirements.
I wanted to flash LineageOS, but went over several problems. Right now I'm stuck in a fastboot-loop. I cannot describe what I've tried to get things working again, sadly.
Recently I stumbled upon this thread and get stuck in the fastboot loop.
Flashing of boot, dtbo, vendor-boot, vbmeta and vbmeta_system seems to work, but after trying to access fastbootd, I get stuck.
Here's the output:
/run/me/g/s/a/e/payload fastboot flash boot boot.img ✔
Sending 'boot_a' (98304 KB) OKAY [ 2.520s]
Writing 'boot_a' OKAY [ 0.257s]
Finished. Total time: 2.822s
/run/me/g/s/a/e/payload fastboot flash dtbo dtbo.img ✔ 3s
Sending 'dtbo' (8192 KB) OKAY [ 0.212s]
Writing 'dtbo' OKAY [ 0.023s]
Finished. Total time: 0.272s
/run/me/g/s/a/e/payload fastboot flash vendor_boot vendor_boot.img
Sending 'vendor_boot' (98304 KB) OKAY [ 2.514s]
Writing 'vendor_boot' OKAY [ 0.278s]
Finished. Total time: 2.832s
/run/me/g/s/a/e/payload fastboot flash vbmeta vbmeta.img ✔ 3s
Sending 'vbmeta' (8 KB) OKAY [ 0.011s]
Writing 'vbmeta' OKAY [ 0.001s]
Finished. Total time: 0.049s
/run/me/g/s/a/e/payload fastboot flash vbmeta_system vbmeta_system.img
Sending 'vbmeta_system' (4 KB) OKAY [ 0.008s]
Writing 'vbmeta_system' OKAY [ 0.001s]
Finished. Total time: 0.044s
/run/me/g/s/a/e/payload fastboot reboot fastboot ✔
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components
might be unbootable.
I'd be so happy to get this working again.
Thanks in advance!
Click to expand...
Click to collapse
I used the raw image for the ASUS Zenfone 8 mentioned in your post a lot of times to get my Zenfone up and running again without problems after I broke everything
How did you try to get the raw image installed?
And which version of the raw image do you use?
There are batch files in the raw image zip file to do that:
update_image.sh (for Unix)
or
update_image.bat (for Windows)
In neither of them is a command "fastboot reboot fastboot".
I never used the batch file for Windows (I do not have WIndows) but the batch file for Linux reinstallls the original ASUS Android without problems. Afterwards you can install a custom ROM like OmniROM or LineageOS using the install instructions from these ROMs.
regards
Bernd

Hm, I tried on both Windows and Linux (Manjaro).
I downloaded the raw image from the "How To Guide", but I also downloaded the latest image from Asus today and tried that one.
Then I used payload dumper to extract the images from the payload file.
After that I used the command from the "flash-all"-file from the "How To Guide".
Until the "fastboot reboot fastboot" command I get overall OK-messages, but after the reboot the Zenfone restarts into normal fastboot, and not into fastbootd. Also trying to flash the other images brings me the error message.
Could you please tell me what image zip file you have? Within the ones I have, there are noch update_image files.

sonix900 said:
Hm, I tried on both Windows and Linux (Manjaro).
I downloaded the raw image from the "How To Guide", but I also downloaded the latest image from Asus today and tried that one.
Then I used payload dumper to extract the images from the payload file.
After that I used the command from the "flash-all"-file from the "How To Guide".
Until the "fastboot reboot fastboot" command I get overall OK-messages, but after the reboot the Zenfone restarts into normal fastboot, and not into fastbootd. Also trying to flash the other images brings me the error message.
Could you please tell me what image zip file you have? Within the ones I have, there are noch update_image files.
Click to expand...
Click to collapse
Then it's not a raw image for the phone...
Download the raw image file from here:
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS590KS/WW-ZS590KS-31.1010.0410.61-MR0-2204-user-20220422.zip
Unzip the zip file, connect your phone in Bootloader mode, and execute the update_image.sh file from the zip file
(and do NOT mix files from different ZIP files )
The official images from ASUS can not be used for this purpose -- you can later use the official images for updating the installed Android OS but not for the first installation.
regards
Bernd

Wow, with your file it worked flawlessly, million thanks!!!
Apparently I really had the wrong files.
BTW, is there an official website at Asus for the raw files?

sonix900 said:
Wow, with your file it worked flawlessly, million thanks!!!
Apparently I really had the wrong files.
BTW, is there an official website at Asus for the raw files?
Click to expand...
Click to collapse
I don't know .. the raw images are the fallback solution if the installation of a new beta fails.
e.g. the link to the raw image for Android 11 is on this website
Android-12-Beta | ASUS Global
www.asus.com
and the link to the raw image for Android 12 is on this website
Android-13-Beta | ASUS Global
www.asus.com
(at the end of the page in the Section "How to opt out ..."
regards
Bernd