Database Develop

[HELP] Pi-llama

Hello, my phone is stock (BR 4.1.2) and not root and unlocked bootloader, the problem is that as I begin the process has several flaws and ends when he asks to enter recorvery continuing with the process he gets the logo motorola and no longer goes out, this I thank you.
Code:
"Activa depuracion usb en tu terminal (configuracion, opc. del desarrollador) i
nstala los drivers motorola y conecta el usb."
"Recuerda tener cargada la bateria por lo menos 50 o mas."
Pressione qualquer tecla para continuar. . .
3597 KB/s (1576781 bytes in 0.428s)
< waiting for device >
sending 'system' (102400 KB)...
OKAY [ 9.165s]
writing 'system'...
FAILED (remote: Preflash validation failed)
finished. total time: 9.525s
sending 'boot' (11264 KB)...
OKAY [ 1.375s]
writing 'boot'...
FAILED (remote: Preflash validation failed)
finished. total time: 2.015s
sending 'radio' (8449 KB)...
OKAY [ 1.137s]
writing 'radio'...
OKAY [ 75.934s]
finished. total time: 77.071s
sending 'recovery' (11264 KB)...
OKAY [ 1.397s]
writing 'recovery'...
FAILED (remote: Preflash validation failed)
finished. total time: 1.763s
erasing 'cache'...
Creating EXT4 FileSystem for cache
OKAY [ 3.400s]
finished. total time: 3.400s
"Selecciona Recovery, instala Fix.zip que se encuentra en tu memoria interna."
"CUANDO TE PREGUNTE DISSABLE RECOVERY FLASH SELECCIONA -NO!"
"listo.."
Pressione qualquer tecla para continuar. . .

solution
Synk0 said:
Hello, my phone is stock (BR 4.1.2) and not root and unlocked bootloader, the problem is that as I begin the process has several flaws and ends when he asks to enter recorvery continuing with the process he gets the logo motorola and no longer goes out, this I thank you.
Code:
"Activa depuracion usb en tu terminal (configuracion, opc. del desarrollador) i
nstala los drivers motorola y conecta el usb."
"Recuerda tener cargada la bateria por lo menos 50 o mas."
Pressione qualquer tecla para continuar. . .
3597 KB/s (1576781 bytes in 0.428s)
< waiting for device >
sending 'system' (102400 KB)...
OKAY [ 9.165s]
writing 'system'...
FAILED (remote: Preflash validation failed)
finished. total time: 9.525s
sending 'boot' (11264 KB)...
OKAY [ 1.375s]
writing 'boot'...
FAILED (remote: Preflash validation failed)
finished. total time: 2.015s
sending 'radio' (8449 KB)...
OKAY [ 1.137s]
writing 'radio'...
OKAY [ 75.934s]
finished. total time: 77.071s
sending 'recovery' (11264 KB)...
OKAY [ 1.397s]
writing 'recovery'...
FAILED (remote: Preflash validation failed)
finished. total time: 1.763s
erasing 'cache'...
Creating EXT4 FileSystem for cache
OKAY [ 3.400s]
finished. total time: 3.400s
"Selecciona Recovery, instala Fix.zip que se encuentra en tu memoria interna."
"CUANDO TE PREGUNTE DISSABLE RECOVERY FLASH SELECCIONA -NO!"
"listo.."
Pressione qualquer tecla para continuar. . .
Click to expand...
Click to collapse
hi bro, is a problem too weird, it happened to me once and loading the firmware fix jelly bean, you tried to run back. bat?
sorry for my bad english

max_choco said:
hi bro, is a problem too weird, it happened to me once and loading the firmware fix jelly bean, you tried to run back. bat?
sorry for my bad english
Click to expand...
Click to collapse
the problem continues after this procedure he asks to go into recovery it gets the most out soon and not only do I command the Power + Vol Down

Try to make a full data wype in the Recovery and then try again, opening the .bat file while in the android home screen and don't forget to turn on usb debugging.

The main problem is, that his Razr is not rooted and unlocked bootloader so without CWM. I guess.

I don't understand his Post to 100%, but it looks like he's not unlocked. There're only preflash validation errors, this usually happens when you try to flash an FW that doesn't match with your Phones Region. You have to be unlocked to flash EU Files (System of Pillama) on an BR XT890.
And of course, CWM won't pass, too.
Gesendet von meinem XT890 mit Tapatalk 2

HSD-Pilot said:
I don't understand his Post to 100%, but it looks like he's not unlocked. There're only preflash validation errors, this usually happens when you try to flash an FW that doesn't match with your Phones Region. You have to be unlocked to flash EU Files (System of Pillama) on an BR XT890.
And of course, CWM won't pass, too.
Gesendet von meinem XT890 mit Tapatalk 2
Click to expand...
Click to collapse
Lucki_X said:
The main problem is, that his Razr is not rooted and unlocked bootloader so without CWM. I guess.
Click to expand...
Click to collapse
If I can not unlock it because the assistants motorola say that my device is not developer site and not of assistance.
if this is the problem then I will have to put up stock rom for a while thanks to everyone who helped me.
Version System: 982.50.20.XT890.Brasil.en.BR
Version of the Baseband: SUNRISE_SMB_REV30_V2_R3_1233.C9_sec
Number of Version: 9.82l-50_SML-20.20
NOTE:if you need anything more just ask
Thx

You have to try it again. Some Users here in Germany got the same Problem. This seems to be Moto-Server related.
After some attempts they where finally able to unlock the Device.
Gesendet von meinem XT890 mit Tapatalk 2

http://batakang.com/ftp/RAZRi/HomemadeFastboots/91.2.26001.Retail.en.EU.zip check working my cell
Sent from my XT890 using xda premium

@zipi23 - My cell phone is with the bootloader locked and can not unlock because it appears this message "your device does not qualify for unlocking bootloader and I could not make this homemade.

Synk0 said:
@zipi23 - My cell phone is with the bootloader locked and can not unlock because it appears this message "your device does not qualify for unlocking bootloader and I could not make this homemade.
Click to expand...
Click to collapse
god ... brother did not read the guide?? clarify very well need the bootloader unlocked
Enviado desde mi XT890 usando Tapatalk 2

max_choco said:
god ... brother did not read the guide?? clarify very well need the bootloader unlocked
Enviado desde mi XT890 usando Tapatalk 2
Click to expand...
Click to collapse
sorry :/ I could not quite understand What did it was written

I managed to unlock the bootloader, updating the SML SML 20 to 28, Many thanks for your help and attention.
Send: Razr I Tapatalk 4

how to unlock bootloader on bricked mobile?

Hello
my mobile is blocked on the HUAWEI logo
when I press VOL- and POWER I go to FASTBOOT & RESCUE MODE (mobile connected to the PC)
PHONE Locked
FRP Lock
my questions:
* if the bootloader is blocked, it is not possible to flash the BOOT, RECOVERY, SYSTEM, etc. with ADB?
* If the mobile is bricked, it is not possible then to unlock the bootloader?
* why, when I introduce an SD card with a LOAD folder, containing UPDATE.APP the mobile does not perform the firmware installation?
I try I do not know how many firmware and I have not yet managed to unblock.
if someone has had the same problem, I want their help.
otherwise, tell me clearly that it is not possible to unlock and the mobile will end up in the trash ...
it will save me from tearing off the rest of hair on my head

iblda said:
Hello
my mobile is blocked on the HUAWEI logo
when I press VOL- and POWER I go to FASTBOOT & RESCUE MODE (mobile connected to the PC)
PHONE Locked
FRP Lock
my questions:
* if the bootloader is blocked, it is not possible to flash the BOOT, RECOVERY, SYSTEM, etc. with ADB?
* If the mobile is bricked, it is not possible then to unlock the bootloader?
* why, when I introduce an SD card with a LOAD folder, containing UPDATE.APP the mobile does not perform the firmware installation?
I try I do not know how many firmware and I have not yet managed to unblock.
if someone has had the same problem, I want their help.
otherwise, tell me clearly that it is not possible to unlock and the mobile will end up in the trash ...
it will save me from tearing off the rest of hair on my head
Click to expand...
Click to collapse
You are totally bricked.. Must have luck to unbrick this but try with DC-Phoenix unlocker, but It"s paid.. I was have same problem and this one help to me

cxyqqz said:
You are totally bricked.. Must have luck to unbrick this but try with DC-Phoenix unlocker, but It"s paid.. I was have same problem and this one help to me
Click to expand...
Click to collapse
I paid 15 € !!
I have this message on DC phoenix
Writing rescue_recovery partition with file recovery
rescue_recovery partition UPDATE ...OK
Looking for device in upgrade mode...
and the mobile is on fastboot & rescue mode ..
if i try to pass the mobile with flight + & power, it shows me the same screen as the departure:
Error!
Func NO: 10 (boot image)
Error NO: 1 (security verify failed)

this morning another test with DC phoenix
error 10
error 1

iblda said:
this morning another test with DC phoenix
error 10
error 1
Click to expand...
Click to collapse
try : https://www.youtube.com/watch?v=8E43DkUQGMM

cxyqqz said:
try : https://www.youtube.com/watch?v=8E43DkUQGMM
Click to expand...
Click to collapse
dc unlocker does not detect my mobile
only DC phoenix detects it
using the tab "update oeminfo" on DC Phoenix 0.0.0.63, I manage to put the mobile in "PHONE UNLOCKED"
from there I take the opportunity to try to flash BOOT, RECOVERY, SYSTEM with ADB commands.
everything goes smoothly and without error but by restarting the mobile always the same screen with the error in red.
message ADB:
Microsoft Windows [version 10.0.17134.407]
(c) 2018 Microsoft Corporation. Tous droits réservés.
C:\Users\José>cd c:/adb
c:\adb>fastboot erase cache
erasing 'cache'...
OKAY [ 0.020s]
finished. total time: 0.021s
c:\adb> fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (22688 KB)...
OKAY [ 0.539s]
writing 'boot'...
OKAY [ 0.683s]
finished. total time: 1.227s
c:\adb>astboot flash recovery recovery.img
'astboot' n’est pas reconnu en tant que commande interne
ou externe, un programme exécutable ou un fichier de commandes.
c:\adb> fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (36166 KB)...
OKAY [ 0.894s]
writing 'recovery'...
OKAY [ 1.079s]
finished. total time: 1.981s
c:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460798 KB)...
OKAY [ 18.360s]
writing 'system'...
OKAY [ 8.003s]
sending sparse 'system' (442517 KB)...
OKAY [ 20.055s]
writing 'system'...
OKAY [ 7.675s]
sending sparse 'system' (459746 KB)...
OKAY [ 17.637s]
writing 'system'...
OKAY [ 7.992s]
sending sparse 'system' (444901 KB)...
OKAY [ 18.492s]
writing 'system'...
OKAY [ 7.729s]
sending sparse 'system' (438286 KB)...
OKAY [ 17.082s]
writing 'system'...
OKAY [ 7.612s]
sending sparse 'system' (150611 KB)...
OKAY [ 5.483s]
writing 'system'...
OKAY [ 2.622s]
finished. total time: 138.805s
c:\adb>

I do not know how I managed to unbrick with a rom NOVA LITE PRA-LX3
how to get back to p8lite ROM now and without the brick again?
EDIT:
I do not know how I managed to unbrick with a rom NOVA LITE PRA-LX3
how to get back to p8lite ROM now and without the brick again?
I took the risk and I flashed again with DC Phoenix with the ROM:
* Prague-L31_C432B100_Firmware_Portugal_Switzerland_France_Germany_Spain_Sweden_Austria_Hungary_Greece_Bulgaria_Macedonia_Nonspecific.APP
but the mobile is still NOVA LITE with imei 000000XXXX
the camera does not work, black screen, photo and selfie

iblda said:
I do not know how I managed to unbrick with a rom NOVA LITE PRA-LX3
how to get back to p8lite ROM now and without the brick again?
EDIT:
I do not know how I managed to unbrick with a rom NOVA LITE PRA-LX3
how to get back to p8lite ROM now and without the brick again?
I took the risk and I flashed again with DC Phoenix with the ROM:
* Prague-L31_C432B100_Firmware_Portugal_Switzerland_France_Germany_Spain_Sweden_Austria_Hungary_Greece_Bulgaria_Macedonia_Nonspecific.APP
but the mobile is still NOVA LITE with imei 000000XXXX
the camera does not work, black screen, photo and selfie
Click to expand...
Click to collapse
Boot into eRecovery (Volume up whilw connected to PC, or when it shows "bootloader unlocked" warning, hold volume up.) Update to lates firmware
also if you get opportunity to update via HiSuite or from phone settings update it. Try as many times as you can to succed. It will aventually flash latest and greatest firmware.
Another method is to use update.app for servicing phones. Downlaod it from here, http://androidhost.ru/K5, place the update.app on external_sdcard inside of a "dload" folder. IN the phone app type *#*#2846579#*#* and select sdcard upgrade. It should work
Wish you luck

aciupapa said:
Another method is to use update.app for servicing phones. Downlaod it from here, http://androidhost.ru/K5, place the update.app on external_sdcard inside of a "dload" folder. IN the phone app type *#*#2846579#*#* and select sdcard upgrade. It should work
Wish you luck
Click to expand...
Click to collapse
this method does not work
the mobile does not exceed 5% and then displays SOFTWARE INSTALL FAILED

Try using HurUpdater. Flash twrp, the download all these files.
1. http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1727/g1647/v146015/f1/full/update.zip dont change name
2.For dualsim
http://update.hicloud.com:8180/TDS/...l/PRA-L31_hw_eu/update_full_PRA-L31_hw_eu.zip (change filename to update_all_hw.zip)
For single sim http://update.hicloud.com:8180/TDS/...l/PRA-L11_hw_eu/update_full_PRA-L11_hw_eu.zip (change filename to update_all_hw.zip)
3. http://update.hicloud.com:8180/TDS/...15/f1/full/public/update_data_full_public.zip (change filename to update_data_public.zip)
4. http://www.mediafire.com/file/ze5z78dq7zu3sxb/HuRUpdater_0.3.zip dont change filename
put all thesw files in one folder on an external sdcard
.
Flash or boot twrp on your phone, and do a "fornat data" commad. wipe all partitions except for the external sd. Flash the HuRupdater_0.3.zip file and confirm flashing by pressing
volume down. After flashing is complete Reboot your phone. ic everything works, it works. If it does not work, do a wipe data and cache in the stock recovery (hurupdater installs stock recovery from the update package automatically)

aciupapa said:
.
Flash or boot twrp on your phone, and do a "fornat data" commad. wipe all partitions except for the external sd.
Flash the HuRupdater_0.3.zip file and confirm flashing by pressing volume down.
After flashing is complete Reboot your phone. ic everything works, it works.
If it does not work, do a wipe data and cache in the stock recovery (hurupdater installs stock recovery from the update package automatically)
Click to expand...
Click to collapse
I flash how?
with what?
where is trwp?
How do I install it?
sorry, I'm starting to be lost ..
this is what I get with the twrp that I downloaded with ADB:
PS C:\Users\José\Documents\MOBILES\huawei\P8\zzzzzz> fastboot flash recovery TWRP-3.2.1-0.img
target reported max download size of 471859200 bytes
sending 'recovery' (8486 KB)...
OKAY [ 0.226s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 0.256s
WITH MULTI-TOOL FOR HUAWEI:
target reported max download size of 471859200 bytes
sending 'recovery' (23942 KB)...
OKAY [ 0.637s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 0.653s

my big problem is the installation of a recovery custom.
I can not install it.
the mobile is good in fastboot with bootloader unlocked
but there is no way to flash the recovery:
c: \ adb> fastboot flash recovery twrp-2.8.7.1-p8.img
target reported download size of 471859200 bytes
sending 'recovery' (25880 KB) ...
OKAY [0.676s]
writing 'recovery' ...
FAILED (remote: image verification error)
finished. total time: 0.707s
this is the message I have for all recovery.
EDIT:
and now I have no access unlocking the bootloader with DC phoenix.
Looking for a device in fastboot mode
Device found: 9DCDU17124012020
05/12/2018 23:00:16 Starting to write device in FASTBOOT mode...
Device found: 9DCDU17124012020
IMEI: 862551034926948
Build number: RA-LX1C432B211
Product model: PRA-LX1
Batery state: 4279mv
Not enough credits
he was talking about 72 hours, the time is over.
it's really stealing this dunking thing. the mobile never finally landed, when it was back again it was blocked again.
really **** these huawei as soon as it's bricked.

RIP​
[emoji34][emoji35][emoji34][emoji35][emoji34][emoji35]
​
thanks anyway for your help, even if it did not work ..
Envoyé de mon MHA-L29 en utilisant Tapatalk

iblda said:
I flash how?
with what?
where is trwp?
How do I install it?
sorry, I'm starting to be lost ..
this is what I get with the twrp that I downloaded with ADB:
PS C:\Users\José\Documents\MOBILES\huawei\P8\zzzzzz> fastboot flash recovery TWRP-3.2.1-0.img
target reported max download size of 471859200 bytes
sending 'recovery' (8486 KB)...
OKAY [ 0.226s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 0.256s
WITH MULTI-TOOL FOR HUAWEI:
target reported max download size of 471859200 bytes
sending 'recovery' (23942 KB)...
OKAY [ 0.637s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 0.653s
Click to expand...
Click to collapse
------------------------
In your command line you write: fastboot flash recovery TWRP-3.2.1-0.img
just write: fastboot boot TWRP-3.2.1.0.img.. Then TWRP will open.
Now in TWRP you can install TWRP recovery, after reboot you will be able yo use it.
I hope this help you.

Android 12.1 Custom Rom [Pixel Experience] or any Treble-Enabled Device Development A/AB ROMS on Nord n100

Hello all nord n100 owners. thanks to @bentalebnordine I've found how to Install Pixel experience android 12 on you're device.
Here are the steps below :
1-first backup your phone
2-unlock your bootloader by : fastboot oem unlock
Click to expand...
Click to collapse
3- download and extract the Nord n100 SDK rar file here :
https://drive.google.com/file/d/11zzlWYwxoDcNr8HrjeL4NTZNyxfrugd7/view?usp=drivesdk
Click to expand...
Click to collapse
4-then download the [GSI][UNOFFICIAL][12] Pixel Experience arm64-ab-slim :
PixelExperience_Plus_arm64-ab-slim-12.1-20220613-UNOFFICIAL.img.xz
Click to expand...
Click to collapse
5- extract the PixelExperience_Plus_arm64-ab-slim-12.1-20220613-UNOFFICIAL.img and put the file in Nord n100 SDK folder
{note that you can put any GSI treble-enabled rom on the SDK folder of your choice, but the extracted image file shouldn't be bigger than 2.7 GB}
** there are plenty other GSI Treble-Enabled ROMS over here : forum.xda-developers.com/f/treble-enabled-device-development-a-ab-roms.7260/
Click to expand...
Click to collapse
6- open Command Prompt in Nord n100 SDK folder by holding shift button and right clicking mouse.
7- then type :
adb reboot bootloader
fastboot --set-active=a
Setting current slot to 'a' OKAY [ 0.049s]
Finished. Total time: 0.053s
fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.003s]
< waiting for any device >
Finished. Total time: 17.266s
fastboot flash product_a product_gsi.img
Resizing 'product_a' OKAY [ 0.013s]
Sending 'product_a' (328 KB) OKAY [ 0.015s]
Writing 'product_a' OKAY [ 0.312s]
Finished. Total time: 0.396s
fastboot erase system_a
Erasing 'system_a' OKAY [ 0.665s]
Finished. Total time: 0.679s
fastboot resize-logical-partition system_a 421000000
Resizing 'system_a' OKAY [ 0.012s]
Finished. Total time: 0.015s
fastboot -w
Erasing 'userdata' OKAY [ 2.078s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.015s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 2.136s
fastboot reboot bootloader
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.005s
fastboot -w
Erasing 'userdata' OKAY [ 0.188s]
F2FS-tools: mkfs.f2fs Ver: 1.14.0 (2020-08-24)
Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 93872792 (45836 MB)
Info: zone aligned segment0 blkaddr: 512
Info: add quota type = 0 => 4
Info: add quota type = 1 => 5
[f2fs_init_sit_area: 587] Filling sit area at offset 0x00600000
[f2fs_init_nat_area: 621] Filling nat area at offset 0x00a00000
[f2fs_write_root_inode:1210] Writing root inode (hot node), 13000 0 200 at of
fset 0x00077824
[f2fs_write_default_quota:1286] Writing quota data, at offset 00013601,
00013602
[f2fs_write_qf_inode:1377] Writing quota inode (hot node), 13000 0 200 at o
ffset 0x00077825
[f2fs_write_default_quota:1286] Writing quota data, at offset 00013603,
00013604
[f2fs_write_qf_inode:1377] Writing quota inode (hot node), 13000 0 200 at o
ffset 0x00077826
[f2fs_update_nat_root:1431] Writing nat root, at offset 0x00000a00
[f2fs_add_default_dentry_root:1628] Writing default dentry root, at offset 0
x00013600
Info: Overprovision ratio = 0.940%
Info: Overprovision segments = 431 (GC reserved = 220)
[f2fs_write_check_point_pack: 774] Writing main segments, cp at offset 0x00
000200
[f2fs_write_check_point_pack: 911] Writing Segment summary for HOT/WARM/COL
D_DATA, at offset 0x00000201
[f2fs_write_check_point_pack: 938] Writing Segment summary for HOT_NODE, at
offset 0x00000202
[f2fs_write_check_point_pack: 950] Writing Segment summary for WARM_NODE, a
t offset 0x00000203
[f2fs_write_check_point_pack: 961] Writing Segment summary for COLD_NODE, a
t offset 0x00000204
[f2fs_write_check_point_pack: 969] Writing cp page2, at offset 0x00000205
[f2fs_write_check_point_pack: 989] Writing NAT bits pages, at offset 0x0000
03fe
[f2fs_write_check_point_pack:1010] Writing cp page 1 of checkpoint pack 2,
at offset 0x00000400
[f2fs_write_check_point_pack:1029] Writing cp page 2 of checkpoint pack 2,
at offset 0x00000405
[f2fs_write_super_block:1062] Writing super block, at offset 0x00000000
Info: format successful
Sending 'userdata' (85 KB) OKAY [ 0.010s]
Writing 'userdata' OKAY [ 0.002s]
Erasing 'metadata' OKAY [ 0.023s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 9.997s
fastboot --disable-verity flash vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (8 KB) OKAY [ 0.016s]
Writing 'vbmeta' OKAY [ 0.002s]
Finished. Total time: 0.141s
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
Sending 'vbmeta_system' (4 KB) OKAY [ 0.003s]
Writing 'vbmeta_system' OKAY [ 0.002s]
Finished. Total time: 0.040s
fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.003s]
< waiting for any device >
Finished. Total time: 10.023s
fastboot flash system PixelExperience_Plus_arm64-ab-slim-12.1-20220613-UNOFFICIAL.img [or any other GSI Treble-enabled ROMS]
Invalid sparse file format at header magic
Resizing 'system_a' OKAY [ 0.012s]
Sending sparse 'system_a' 1/7 (524228 KB) OKAY [ 20.447s]
Writing 'system_a' OKAY [ 2.675s]
Sending sparse 'system_a' 2/7 (524228 KB) OKAY [ 20.208s]
Writing 'system_a' OKAY [ 2.684s]
Sending sparse 'system_a' 3/7 (524252 KB) OKAY [ 20.297s]
Writing 'system_a' OKAY [ 2.693s]
Sending sparse 'system_a' 4/7 (524248 KB) OKAY [ 20.846s]
Writing 'system_a' OKAY [ 2.745s]
Sending sparse 'system_a' 5/7 (524248 KB) OKAY [ 20.274s]
Writing 'system_a' OKAY [ 2.717s]
Sending sparse 'system_a' 6/7 (524204 KB) OKAY [ 21.480s]
Writing 'system_a' OKAY [ 2.771s]
Sending sparse 'system_a' 7/7 (461172 KB) OKAY [ 17.803s]
Writing 'system_a' OKAY [ 2.638s]
Finished. Total time: 199.508s
Click to expand...
Click to collapse
8- enjoy
[note that there might be bugs but Android 12 worth it]

Does this work for the Metro variant?? be2015/ BE82CF ?

I've tested on my BE2013, so make a backup and test.

AesopRock127 said:
Does this work for the Metro variant?? be2015/ BE82CF ?
Click to expand...
Click to collapse
It applies to all treble enabled devices, more specifically OnePlus devices, note that OnePlus n100 is arm64 a/b device

The full rom is the best.
https://github.com/ponces/treble_build_pe/releases/download/v414-plus/PixelExperience_Plus_arm64-ab-12.1-20220613-UNOFFICIAL.img.xz

AesopRock127 said:
Does this work for the Metro variant?? be2015/ BE82CF ?
Click to expand...
Click to collapse
No, it doesn't. I don't what the difference is but in order to flash a GSI on this variant you'll need to use this ( MSM link ) and flash the global firmware to the Metro version. It's super simple, the tool has already been modified. I didn't mod it but I've used it and it works flawlessly.
AesopRock127 said:
Does this work for the Metro variant?? be2015/ BE82CF ?
Click to expand...
Click to collapse

sdflowers32 said:
No, it doesn't. I don't what the difference is but in order to flash a GSI on this variant you'll need to use this ( MSM link ) and flash the global firmware to the Metro version. It's super simple, the tool has already been modified. I didn't mod it but I've used it and it works flawlessly.
Click to expand...
Click to collapse
Thanks that's kind of what I was thinking even though the other poster said it did.

AesopRock127 said:
Thanks that's kind of what I was thinking even though the other poster said it did.
Click to expand...
Click to collapse
You'll find the most useful information on this device in the 4pda forum Here. It's a bit choppy but you'll find info that's pretty much the same across the board. Most useful is the info regarding removing encryption. I've flashed more than 10 different GSI's both A11 and A12 to this device. I've heard one person say they were able to do so on the Metro variant but I never seen any proof and I know I was never able to so best option is to flash the global version to the Metro variant. Also you can unlock the bootloader without a token once you're on global 10.5.5.

.

Děkuji Dlouho jsem hledal ROM pro svůj Oneplus Nord N100 (BE2013). O instalaci vlastní ROM do telefonu jsem neuvažoval, ale po výměně neoriginálního displeje se mi telefon neustále restartoval, nic nepomohlo, tak jsem nainstaloval vlastní ROM Pixel Experience a vše funguje jako předtím.
Moc děkujeme

ringtone for incoming calls are not playing even when im in settings trying to change the ringtone nothings playing but the phone vibrates on incoming calls.
And in the music players songs are playing fine!
Is there any solution for this?

Releases · ponces/treble_build_pe
Script and patches for building PHH-Treble Pixel Experience - ponces/treble_build_pe
github.com
Can I use latest pixel experience 13 plus in this link instead?

Mahdi0047 said:
Releases · ponces/treble_build_pe
Script and patches for building PHH-Treble Pixel Experience - ponces/treble_build_pe
github.com
Can I use latest pixel experience 13 plus in this link instead?
Click to expand...
Click to collapse
I tried it with `PixelExperience_Plus_arm64-ab-slim-13.0-20230104-UNOFFICIAL.img.xz` and it didn't work. It booted, but the screen got black as soon as I ended the initial configuration.

I tried Pixel Experience this weekend. Screen flickers and dims. Could be refresh problem. But phone finally got so dark it was unusable. Display would not show anything at all. But the reboot menu was fine.

I tried to flash following the instructions and after rebooting, the phone goes into 'Qualcomm CrashDump Mode' with 'Attempted to kill init! exit code=0x00007f00 do_exit'. Does anyone know how can I fix this? The phone still works if i switch to the b slot.

Halphix said:
I tried to flash following the instructions and after rebooting, the phone goes into 'Qualcomm CrashDump Mode' with 'Attempted to kill init! exit code=0x00007f00 do_exit'. Does anyone know how can I fix this? The phone still works if i switch to the b slot.
Click to expand...
Click to collapse
I fixed the issue. For anyone that has this issue download the msm tool and use that to unbrick which will also install android 10. Then update to android 11 which will install it into slot b. This will also wipe any data you have in slot b before this. Then just follow instructions for flashing gsi

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.

mi a2 and fastboot flash - Error

Hi All,
The issue i am encountering (with my mi a2 ) is the following:
Start: All was working, and i did a restart of the phone;
Effect: The phone did not start up any more and kept hanging on -android one- splash
Analysis: I can still start the phone in fastboot mode, and can still connect with ADB and fastboot
(this is correctly installed and working with my other M2 phones.. also cables are correct and using usb 2 etc..)
Problem: When flashing, every second flash command seems to fail:
example log:
E:\platform-tools>fastboot flash storsec storsec.mbn
Sending 'storsec' (48 KB) OKAY [ 0.011s]
Writing 'storsec' OKAY [ 0.001s]
Finished. Total time: 0.020s
E:\platform-tools>fastboot flash mdtpsecapp_b mdtpsecapp.img
Sending 'mdtpsecapp_b' (1057 KB) FAILED (remote: 'Error flashing partition.')
fastboot: error: Command failed
E:\platform-tools>fastboot flash mdtpsecapp_b mdtpsecapp.img
Sending 'mdtpsecapp_b' (1057 KB) OKAY [ 0.026s]
Writing 'mdtpsecapp_b' OKAY [ 0.001s]
Finished. Total time: 0.031s
E:\platform-tools>fastboot flash mdtpsecapp_a mdtpsecapp.img
Sending 'mdtpsecapp_a' (1057 KB) FAILED (remote: 'Error flashing partition.')
fastboot: error: Command failed
E:\platform-tools>fastboot flash mdtpsecapp_a mdtpsecapp.img
Sending 'mdtpsecapp_a' (1057 KB) OKAY [ 0.035s]
Writing 'mdtpsecapp_a' OKAY [ 0.000s]
Finished. Total time: 0.040s
In theory just repeating the flash commands will get it done; HOWEVER some flashes have bigger images like system
E:\platform-tools>fastboot flash system_a system.img
Sending sparse 'system_a' 1/6 (516064 KB) FAILED (remote: 'Error flashing partition.')
fastboot: error: Command failed
E:\platform-tools>fastboot flash system_a system.img
Sending sparse 'system_a' 1/6 (516064 KB) OKAY [ 11.452s]
Writing 'system_a' OKAY [ 0.000s]
Sending sparse 'system_a' 2/6 (514680 KB) FAILED (remote: 'Error flashing partition.')
fastboot: error: Command failed
After the first flashed chunk the second part fails and the link between phone and pc hangs; I need to reboot the phone in fastboot again to get control again;
(sadly i cannot directly flash part 2of 6 since its one command)
------------------------------------------
Additional findings:
When i try to boot the twrp image for my phone (below latest version)
E:\platform-tools>fastboot boot twrp-3.7.0_9-0-jasmine_sprout.img
Sending 'boot.img' (32164 KB) OKAY [ 0.738s]
Booting OKAY [ 10.315s]
Finished. Total time: 11.079s
The flash goes well (because its the first flash command) and the phone restarts to boot;
Sometimes it actually boots in the twrp menu but 98% of the times it hangs on the twrp splash screen
Additional findings:
I read something about encryption etc so i tried to wipe stuff (with wipe command)
This always seem to result in a hang on erasing cache
(COULD BE that cache is not used or available in Mi a2??)
E:\platform-tools>fastboot -w
Erasing 'userdata' OKAY [ 0.053s]
mke2fs 1.46.2 (28-Feb-2021)
Creating filesystem with 12285943 4k blocks and 3072000 inodes
Filesystem UUID: 50443726-8896-11ed-ab67-67ab2caed3b8
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424
Allocating group tables: done
Writing inode tables: done
Creating journal (65536 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'userdata' (260 KB) OKAY [ 0.008s]
Writing 'userdata' OKAY [ 0.001s]
Erasing 'cache' ^C
------------------------------------
ALL in all i cannot get my phone to work anymore since flashing seems to hang every second flash command
This also means i cannot get a working stable STOCK rom put back on my phone;
Does anybody have some ideas or tips on how to fix this?
Personally i think there is something wrong with the memory disk inside the phone? Corrupted? Bad sectors?
Maybe i should look in the direction of formatting something?
All input / help will be appreciated;
Regards
Tom

I assume phone is fully unlocked. Otherwise search for Test-Point / EDL guide.
> When flashing, every second flash command seems to fail
- Try to use another USB 2.x slot, for example in an external USB hub (most modern monitors have one built-in). Note that USB3.x slots are not fully supported with MiA2 drivers.
- Maybe update fastboot.exe with latest platform tools (https://developer.android.com/studio/releases/platform-tools)
- Recheck installed Win64 USB drivers with USBDeview (http://www.nirsoft.net/utils/usb_devices_view.html)
> Sometimes it actually boots in the twrp menu but 98% of the times it hangs on the twrp splash screen
- "Official" TWRP is buggy,
- use the working one by @Nebrassy
[RECOVERY] [UNOFFICIAL] TeamWin Recovery Project
#include /* * Your warranty is now void. * * We are not responsible for bricked devices, dead SD cards, * thermonuclear war or you getting fired because the alarm app failed. Please * do some research if you have any concerns...
forum.xda-developers.com
Downloads for : Xiaomi Mi A2 | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
> cache is not used or available in Mi a2
I believe so, yet "fastboot -w" used to work for everybody ... or RAM went south
Have you tried to switch A/B slots to previously installed ROM in TWRP or fastboot?