[HELP] Pi-llama - RAZR i Q&A, Help & Troubleshooting

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

Related

Xperia ZR Bootloader

How to flash bootloader on this phone???
i only has fastboot mode,
when it power on there all many horizontal lines on the screen, i tryed to flash bootloader but no succes
it says ''
sending 'bootloader' (169 KB)...
OKAY [ 0.014s]
writing 'bootloader'...
FAILED (remote: Command not allowed)
finished. total time: 0.045s
''
Help me
Need help ...
malivrag11 said:
How to flash bootloader on this phone???
i only has fastboot mode,
when it power on there all many horizontal lines on the screen, i tryed to flash bootloader but no succes
it says ''
sending 'bootloader' (169 KB)...
OKAY [ 0.014s]
writing 'bootloader'...
FAILED (remote: Command not allowed)
finished. total time: 0.045s
''
Help me
Click to expand...
Click to collapse
Remov 0x in the bootloader unlock code
I had the same prob
it say : ''FAILED (remote: Incorrect format for unlock data. Should be on the form "0x)
finished. total time: 0.043s''
no success at all help me
malivrag11 said:
it say : ''FAILED (remote: Incorrect format for unlock data. Should be on the form "0x)
finished. total time: 0.043s''
Click to expand...
Click to collapse
Me too .help ne
c5503

[Moto X XT1058] Wont Quit the Brick / no sale del brick [English/spanish]

hello. in advance sorry for my bad english did the best i could thanks for all the help this is my first post
I own a xt1058 at&t version, bootloader is unlocked and its also rooted, it used to run XT1058_GHOST_ATT_5.1_LPA23.12-21.7_cid1_CFC.xml note that its LPA23.12 not LPAS23.12 it has an (S).
one day it went off(discharged) and now it just turns on and shows bootlogo, bootanimation (both are custom )then it goes black stays there for hours, if i try to go into twrp its stuck on the teamwin image. // un dia se descargo y ahora solo prende me muestra el bootlogo luego el bootanimation ambos son customizados mios y luego se queda en negro al igual cuadno quiero entrar en twrp se queda en la presentacion teamwin
ive tried almost everything I have good Knowledge about flashing // ya he probado casi todo pero necesito de su ayuda tengo buen conocimiento acerca de flashear celulares
tried to flash via rds lite it flashes well it sends the phone to reboot but nothing changes and it stays black after boot image and boot animation so i downloaded more version for it:
XT1058_GHOST_RETAR_5.1_LPA23.12-21.7_cid12_CFC.xml
XT1058_GHOST_NIIBR_5.1_LPA23.12-21.7_cid3_CFC.xml
XT1058_GHOST_ATT_5.1_LPA23.12-21.7_cid1_CFC.xml
ATT_XT1058_4.4.4-KXA21.12-L1.26_CFC_1FF.xml
XT1058_RETAIL-AR_4.4.4_KXA21.12-L1.26_62_cid12_CFC_1FF.xml
XT1058_GHOST_TIMBR_5.1_LPAS23.12-21.7-1_cid12_CFC.xml
FUNNY thing about all is that i have a custom bootlogo and a custom boot animation so when i flash the stock ones, doesnt change a thing and it flashes with no error I WOULD LIKE THAT PEOPLE SEE THIS FIRST AND THE WISE GUYS TRY HELP ME EXPLAIN THIS FIRST lo mas RARO de todo es que como tengo el bootlogo y animation customizado cuando flasheo todas esas rom stock no cambia nada y deberia hacer incluso proba solo con esos archivos a ver si lo delvolvia al warning del bootloader y a el planeta motorola y nada me gustaria que nos enfocaramos en esto ya que puede ser una buena explicacion del por que no esta hagarrando flash
BOOTLOADER DISPLAY:
AP Fastboot Flash Mode (s)
30.BE (sha-34b7ccb, 2015-04-22 12:57:17)
emmc: 16GB sandisk rv=06 PV=07 TY=17
DRAM: 2048 samung s4 SDRAM DIE=4GB
uptime: 2minutes
device is UNLOCKED. Status code:3 (this is highlighted in yellow)
Baterry ok (charging) (this is highlighted in green)
Transfer Mode: USB Connected (highlighted in green also)
PD 1: I always use MFASTBOOT not FASTBOOT but ive tried wit both // he probado con ambos
PD 2: no matter what rom im flashing i always get the same error if i try downgrading it wont let me because of the security thing gpt and stuff, also have modified the lines when flashing with rds nothing works
Got this info in cmd with the following command: fastboot getvar all // esto lo obtuve en CMD con el comando "
fastboot getvar all "
version-bootloader: 30BE
version: 0.5
cpu: MSM8960 Pro CS
ram: 2048MB Samsung S4 SDRAM DIE=4Gb
emmc: 16GB Sandisk REV=06 PRV=07 TYPE=17
product: ghost
revision-hardware: 0x8300
radio: 0x1
secure: yes
mid: 026b
serialno: TA1760BX0Y
qe: qe 1/1
unlocked: yes
iswarrantyvoid: yes
max-download-size: 805306368
uid: 9F8110040C000100000000000000
imei: 354984054025132
meid:
sku: 000000000000000
cid: 0x0c
iccid:
date: 11-12-2013
cust_md5:
reason: Key pressed
ro.build.date: Mon Aug 17 05:52:36 CDT 2015
ro.build.id: LPA23.12-21.7
ro.build.tags: bldacfg,release-keys
ro.build.type: user
ro.build.user: hudsoncm
ro.build.version.codename: REL
ro.build.version.incremental: 6
ro.build.version.release: 5.1
ro.mot.build.customerid: att
ro.product.name: ghost_att
ro.build.fingerprint[0]: motorola/ghost_att/ghost:5.1/LPA
ro.build.fingerprint[1]: 23.12-21.7/6:user/bldacfg,releas
ro.build.fingerprint[2]: e-keys
ro.build.version.full[0]: Blur_Version.222.26.7.ghost_att.
ro.build.version.full[1]: ATT.en.US
kernel.version[0]: Linux version 3.4.42-gfff16c8 (h
kernel.version[1]: [email protected]) (gcc version
kernel.version[2]: 4.8 (GCC) ) #1 SMP PREEMPT Mon A
kernel.version[3]: ug 17 06:05:02 CDT 2015
all:
finished. total time: 0.245s
just for recon purposes but everthing still the same error, tried to reflash the twrp with FASTBOOT it says:
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\Root Moto X\Root Moto X
>fastboot flash recovery twrp.img
sending 'recovery' (8498 KB)...
OKAY [ 0.769s]
writing 'recovery'...
OKAY [ 0.849s]
finished. total time: 1.619s
NO LUCK STILL GET STUCK also tried a diferent version of twrp same thing.
FLASHING CWM pretty much the same:
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\Root Moto X\Root Moto X
>fastboot flash recovery recovery.img
sending 'recovery' (8488 KB)...
OKAY [ 0.780s]
writing 'recovery'...
OKAY [ 0.869s]
finished. total time: 1.649s
everytime I flash CWM or stock recovery it seens to be overwrited by twrp. Even if I boot right after flashing it. // cada vez que flasheo CWM o Stock recovery pareciera que lo vence el twrp y no se deja cambiar, incluso si hago el flash y de inmediato quiero verificar
MFASTBOOT does give and error with XT1058_GHOST_ATT_5.1_LPA23.12-21.7_cid1_CFC.xml <bootloader> Variable Not supported but not with RSD lite // MFASTBOOT ME DA ERROR <bootloader> Variable Not supported pero rsd lite no da tal error
everyting went just fine but "status" stays on reboot beacause the phone never finish booting so i have to re-enter bootloader so it can say PASS // el rsd todo parece haber ido bien pero el "status" no pasa de reboot debido a que el telefono nunca termina de encender
FLASHING XT1058_GHOST_NIIBR_5.1_LPA23.12-21.7_cid3_CFC.xml with fastboot
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\ROM\XT1058_GHOST_NIIBR_
5.1_LPA23.12-21.7_cid3_CFC.xml>fastboot oem fb_mode_set
...
OKAY [ 0.130s]
finished. total time: 0.130s
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\ROM\XT1058_GHOST_NIIBR_
5.1_LPA23.12-21.7_cid3_CFC.xml>fastboot flash partition gpt.bin
sending 'partition' (32 KB)...
OKAY [ 0.249s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.120s
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\ROM\XT1058_GHOST_NIIBR_
5.1_LPA23.12-21.7_cid3_CFC.xml>fastboot flash motoboot motoboot.img
sending 'motoboot' (1604 KB)...
OKAY [ 0.359s]
writing 'motoboot'...
flashing tz ...
flashing rpm ...
flashing aboot ...
flashing sbl1 ...
flashing sbl2 ...
flashing sbl3 ...
OKAY [ 5.090s]
finished. total time: 5.450s
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\ROM\XT1058_GHOST_NIIBR_
5.1_LPA23.12-21.7_cid3_CFC.xml>fastboot flash logo logo.bin
sending 'logo' (245 KB)...
OKAY [ 0.310s]
writing 'logo'...
OKAY [ 0.879s]
finished. total time: 1.189s
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\ROM\XT1058_GHOST_NIIBR_
5.1_LPA23.12-21.7_cid3_CFC.xml>fastboot flash boot boot.img
sending 'boot' (10240 KB)...
OKAY [ 1.069s]
writing 'boot'...
OKAY [ 1.348s]
finished. total time: 2.418s
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\ROM\XT1058_GHOST_NIIBR_
5.1_LPA23.12-21.7_cid3_CFC.xml>fastboot flash recovery recovery.img
sending 'recovery' (8488 KB)...
OKAY [ 0.940s]
writing 'recovery'...
OKAY [ 0.908s]
finished. total time: 1.849s
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\ROM\XT1058_GHOST_NIIBR_
5.1_LPA23.12-21.7_cid3_CFC.xml>fastboot flash system system.img
sending 'system' (786432 KB)...
OKAY [ 58.986s]
writing 'system'...
OKAY [ 22.717s]
sending 'system' (663972 KB)...
OKAY [ 50.521s]
writing 'system'...
OKAY [ 19.100s]
finished. total time: 151.327s
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\ROM\XT1058_GHOST_NIIBR_
5.1_LPA23.12-21.7_cid3_CFC.xml>fastboot flash modem NON-HLOS.bin
sending 'modem' (54272 KB)...
OKAY [ 4.180s]
writing 'modem'...
OKAY [ 2.378s]
finished. total time: 6.559s
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\ROM\XT1058_GHOST_NIIBR_
5.1_LPA23.12-21.7_cid3_CFC.xml>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.459s]
finished. total time: 0.459s
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\ROM\XT1058_GHOST_NIIBR_
5.1_LPA23.12-21.7_cid3_CFC.xml>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.441s]
finished. total time: 0.441s
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\ROM\XT1058_GHOST_NIIBR_
5.1_LPA23.12-21.7_cid3_CFC.xml>fastboot flash fsg fsg.mbn
sending 'fsg' (226 KB)...
OKAY [ 0.330s]
writing 'fsg'...
OKAY [ 0.799s]
finished. total time: 1.129s
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\ROM\XT1058_GHOST_NIIBR_
5.1_LPA23.12-21.7_cid3_CFC.xml>fastboot erase cache
erasing 'cache'...
OKAY [ 0.679s]
finished. total time: 0.679s
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\ROM\XT1058_GHOST_NIIBR_
5.1_LPA23.12-21.7_cid3_CFC.xml>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.552s]
finished. total time: 0.552s
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\ROM\XT1058_GHOST_NIIBR_
5.1_LPA23.12-21.7_cid3_CFC.xml>fastboot erase customize
erasing 'customize'...
OKAY [ 0.159s]
finished. total time: 0.159s
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\ROM\XT1058_GHOST_NIIBR_
5.1_LPA23.12-21.7_cid3_CFC.xml>fastboot erase clogo
erasing 'clogo'...
OKAY [ 0.538s]
finished. total time: 0.539s
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\ROM\XT1058_GHOST_NIIBR_
5.1_LPA23.12-21.7_cid3_CFC.xml>fastboot oem fb_mode_clear
...
OKAY [ 0.166s]
finished. total time: 0.166s
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\ROM\XT1058_GHOST_NIIBR_
5.1_LPA23.12-21.7_cid3_CFC.xml>fastboot reboot
rebooting...
finished. total time: 0.001s
I tried to cover the most i could so theres no doubt about what im doing please help..!// trate de cubrir el mayor terreno prosible tal vez en cuanto a sus preguntas es mi primer post si falto algo me avisan se los agradezco
sinceros saludos ..almerHDSerViceS:..
Moto X XT1058 (Ghost)
ROM: Lollipop 5.1 Stock (AT&T) | Kernel: Stock | Root: SuperSU | BL: Unlocked | Recovery: TWRP 2.8.6.0

How can I find my Recovery?

My phone is NUM-UL10. I did factory reset without exiting google account, and then I lost my Recovery.
I can`t flash it with fastboot command, it said :
E:\adb>fastboot flash recovery E:\adb\EliteTWRP-3.2.1-0_2018-01-19.img
target reported max download size of 471859200 bytes
sending 'recovery' (31572 KB)...
OKAY [ 0.963s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.975s
Also when tried command: adb devices in Bootloader mode, the pc can`t find my phone, it said:
E:\adb>adb devices
List of devices attached
but when I open my phone, it can find my phone.
I have tryed to install drivers correctlly, change another pc, close Find My Phone and use other tools, but none of these methods solve my problem.
What else can I do?
Did you unlock the bootloader?
Envoyé de mon NEM-L22 en utilisant Tapatalk

[ROM] [Q] MIUI 11 [Lenovo Z6 Pro] [Unofficial]

Warning: I am not responsible for any damage cause. Read instructions carefully before. I am not the creator of this rom, neither the maintainer. I am just sharing for our passion.
This is port of MIUI 11 from Redmi k20 by Art Chen.
Works all things, fingerprint and camera also works. May be something not work, you say me.
How to install (your bootloader must be unlocked):
1. Download and unpack
2.Connect your phone in fastboot mode
2.Run flash.bat
Screenshots:
Download:
Link
Sdcard patch: View attachment sdcard_patch.zip
Ayuda
Quiero instalar esta ROM , mi duda es el parche es para cambiar el idioma o para que es? Y como se instala?.
works on z6 lite?
ÃÙ╩õ╚Ù╩²ÎÍÐíȱ─·Á─╔Þ▒©Î┤╠¼:
**-1.┐¬╗· -**
**-2.fastboot -**
Ðíȱ:2
╦ó╚ÙBootÀÍð....
Sending 'boot' (40692 KB) OKAY [ 0.998s]
Writing 'boot' OKAY [ 0.213s]
Finished. Total time: 1.226s
fastboot: error: cannot load '.\images\dtbo.img': No such file or directory
╦ó╚ÙVendorÀÍð....
Invalid sparse file format at header magic
Sending sparse 'vendor' 1/1 (755787 KB) OKAY [ 19.036s]
Writing sparse 'vendor' 1/1 OKAY [ 0.004s]
Finished. Total time: 20.733s
╦ó╚ÙSystemÀÍð....
Invalid sparse file format at header magic
Sending sparse 'system' 1/5 (786026 KB) FAILED (data write failure (Unknown error))
Finished. Total time: 65.884s
Sending 'vbmeta' (64 KB) FAILED (command write failed (Unknown error))
Finished. Total time: 5.021s
░┤╚╬ÊÔ╝³¢°ððÎÈ»©±╩¢╗»data▓┘θú¿╦¨Ëð╩²¥¦¢½Â¬╩ºú®(╚þ╣¹Í«Ã░╩é├¤Á═│Á─ÃÚ┐÷¤┬┐╔ÊÈÍ▒¢Ë╣Ï▒ı┤░┐┌▓óÈ┌╩Í╗·ÐíȱStartã¶Â»╩Í╗·)...
I always get those errors when I want to install this rom...
Installation successful
Installed mine successfully, make sure your boot loader is unlocked first.
alexeei said:
Warning: I am not responsible for any damage cause. Read instructions carefully before. I am not the creator of this rom, neither the maintainer. I am just sharing for our passion.
This is port of MIUI 11 from Redmi k20 by Art Chen.
Works all things, fingerprint and camera also works. May be something not work, you say me.
How to install (your bootloader must be unlocked):
1. Download and unpack
2.Connect your phone in fastboot mode
2.Run flash.bat
Screenshots:
Download:
Link
Sdcard patch:
Click to expand...
Click to collapse
Link does not work
Mahz4130 said:
Link does not work
Click to expand...
Click to collapse
Here you go
https://mega.nz/file/3tBVjISI#_v_mbuO769VKJtq0GI1ncq05NU5YfwOpgbIP7NAqqKo
Can someone make rom miui 12, based on the global firmware miui 12, I really liked the rom from ArtChen, but it's purely Chinese.

Low level diagnostics

Hi guys and possibly girls...(?)
Well as the title says i'm looking for some kind of tool that lets me discard hardware problems on my xt1925-1 moto G6.
The problem I'm having is that one day stopped booting to android. It was my brother's phone and asked me to fix it since i'm a programmer and a geek I had some experience flashing roms. Well the phone behaves really weird it boots to fastboot and I can't use any option. Almost every time tooks like 20 seconds to boot and the info in the phone is corrupted it shows "product variant: ali 000000000000" instead of the model xt1925 etc etc... and the imei its 00's too as well of the baseband and SKU. when I try to flash the very first command I try fails:
fastboot oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.032s
Click to expand...
Click to collapse
And every flash command and erase command gives me the "(bootloader) Invalid partition name".
The partition gpt.bin gives "Preflash validation failed"
I'll copy the text at the end of the post.
Well the funny thing is that some "sadly few" times boots in less than 5 seconds and the info isn't corrupted. The commands works OK, for a short time, didn't let me finish flashing system, it hangs for a while and fails then boots bad again. Someone told me that the imei and other information shows 0's when de partition table isn't present or is corrupted. This behavior lend me to think that is some kind of Hardware problem in the ROM that sometimes is accessible and sometimes not?.
And i'm looking for a low level diagnose tool that can be run on the pc via USB to tell me if there is some kind of hardware malfunction. I searched on google but didn't found anything please HELP!.
This is the results when I try to flash the stock firmware when the phone is "corrupted":
fastboot getvar max-sparse-size
max-sparse-size: 268435456
finished. total time: 0.003s
fastboot oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.001s
fastboot flash partition gpt.bin
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ 0.007s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.075s
fastboot flash bootloader bootloader.img
target reported max download size of 534773760 bytes
sending 'bootloader' (7419 KB)...
OKAY [ 0.244s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Invalid partition name aboot
(bootloader) Invalid partition name rpm
(bootloader) Invalid partition name tz
(bootloader) Invalid partition name devcfg
(bootloader) Invalid partition name cmnlib
(bootloader) Invalid partition name cmnlib64
(bootloader) Invalid partition name keymaster
(bootloader) Invalid partition name prov
(bootloader) Invalid partition name sbl1
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.353s
fastboot flash modem NON-HLOS.bin
target reported max download size of 534773760 bytes
sending 'modem' (62672 KB)...
OKAY [ 1.527s]
writing 'modem'...
(bootloader) Invalid partition name modem
FAILED (remote failure)
finished. total time: 1.536s
fastboot flash fsg fsg.mbn
target reported max download size of 534773760 bytes
sending 'fsg' (7972 KB)...
OKAY [ 0.223s]
writing 'fsg'...
(bootloader) Invalid partition name fsg
FAILED (remote failure)
finished. total time: 0.230s
fastboot erase modemst1
erasing 'modemst1'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.033s
fastboot erase modemst2
erasing 'modemst2'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.037s
fastboot flash dsp adspso.bin
target reported max download size of 534773760 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.422s]
writing 'dsp'...
(bootloader) Invalid partition name dsp
FAILED (remote failure)
finished. total time: 0.447s
fastboot flash logo logo.bin
target reported max download size of 534773760 bytes
sending 'logo' (2182 KB)...
OKAY [ 0.069s]
writing 'logo'...
(bootloader) Invalid partition name logo
FAILED (remote failure)
finished. total time: 0.092s
fastboot flash boot boot.img
target reported max download size of 534773760 bytes
sending 'boot' (22528 KB)...
OKAY [ 0.612s]
writing 'boot'...
(bootloader) Invalid partition name boot
FAILED (remote failure)
finished. total time: 0.635s
fastboot flash recovery recovery.img
target reported max download size of 534773760 bytes
sending 'recovery' (22628 KB)...
OKAY [ 0.603s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.631s
fastboot flash system system.img_sparsechunk.0
target reported max download size of 534773760 bytes
sending 'system' (259637 KB)...
OKAY [ 6.313s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 6.335s
fastboot flash system system.img_sparsechunk.1
target reported max download size of 534773760 bytes
sending 'system' (262142 KB)...
OKAY [ 6.464s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 6.486s
fastboot flash system system.img_sparsechunk.2
target reported max download size of 534773760 bytes
sending 'system' (262141 KB)...
OKAY [ 6.027s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 6.048s
fastboot flash system system.img_sparsechunk.3
target reported max download size of 534773760 bytes
sending 'system' (262142 KB)...
OKAY [ 6.444s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 6.463s
fastboot flash system system.img_sparsechunk.4
target reported max download size of 534773760 bytes
sending 'system' (262140 KB)...
OKAY [ 6.419s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 6.442s
fastboot flash system system.img_sparsechunk.5
target reported max download size of 534773760 bytes
sending 'system' (262140 KB)...
OKAY [ 6.468s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 6.477s
fastboot flash system system.img_sparsechunk.6
target reported max download size of 534773760 bytes
sending 'system' (261193 KB)...
OKAY [ 6.411s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 6.433s
fastboot flash system system.img_sparsechunk.7
target reported max download size of 534773760 bytes
sending 'system' (262141 KB)...
OKAY [ 6.454s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 6.461s
fastboot flash system system.img_sparsechunk.8
target reported max download size of 534773760 bytes
sending 'system' (262141 KB)...
OKAY [ 6.446s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 6.478s
fastboot flash system system.img_sparsechunk.9
target reported max download size of 534773760 bytes
sending 'system' (187636 KB)...
OKAY [ 4.657s]
writing 'system'...
(bootloader) Invalid partition name system
FAILED (remote failure)
finished. total time: 4.679s
fastboot flash vendor vendor.img_sparsechunk.0
target reported max download size of 534773760 bytes
sending 'vendor' (253727 KB)...
OKAY [ 6.229s]
writing 'vendor'...
(bootloader) Invalid partition name vendor
FAILED (remote failure)
finished. total time: 6.269s
fastboot flash vendor vendor.img_sparsechunk.1
target reported max download size of 534773760 bytes
sending 'vendor' (196061 KB)...
OKAY [ 4.847s]
writing 'vendor'...
(bootloader) Invalid partition name vendor
FAILED (remote failure)
finished. total time: 4.868s
fastboot flash oem oem.img
target reported max download size of 534773760 bytes
sending 'oem' (153177 KB)...
OKAY [ 3.787s]
writing 'oem'...
(bootloader) Invalid partition name oem
FAILED (remote failure)
finished. total time: 3.797s
fastboot erase cache
erasing 'cache'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.033s
fastboot erase userdata
erasing 'userdata'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.036s
fastboot oem fb_mode_clear
...
FAILED (remote failure)
finished. total time: 0.018s
fastboot reboot
rebooting...
finished. total time: 0.017s
Click to expand...
Click to collapse
bye
Some follow up...
I did manage to flash the stock ROM but when it rebooted went to fastboot again because it didn't find the boot partition. The process of flashing went .OKAY. on all the steps. This was when It booted to the "GOOD" fastboot the one that lets me use commands. I can tell the difference because it has a little android with the chest opened and more information:
Well I'm trying to post an image but failed with 2 different file host... -.-
I'll just type the text here:
AP Fasboot Flash Mode (Secure)
BL: MBM-2.1-ali_retail-c999d61-190930
Baseband: M450_21.29.10.88R ALI_LATAM_CUST
Product/Variant: ali XT1925-1 32GB PVT2
Serial Number: ZY322SLP2N
CPU: SDM450
.
.
.
Click to expand...
Click to collapse
And the "BAD" fastboot looks like this, and doesn't have the android and the text of the options are just plain red/green/whit colored text(the other shows the text in a globe). And this is what it shows:
AP Fasboot Flash Mode (Secure)
BL: MBM-2.1-ali_retail-c999d61-190930
Baseband:
Product/Variant: ali 000000000000000 32GB PVT2
Serial Number: 3a9ff2d0
CPU: SDM450
.
.
.
Click to expand...
Click to collapse
bye
facurdoy said:
Algunos siguen ...
Me las arreglé para actualizar la ROM estándar, pero cuando se reinició, volví a arrancar rápido porque no encontró la partición de arranque. El proceso de flasheo fue .OKAY. en todos los escalones. Fue entonces cuando arrancó con el fastboot "BUENO" el que me permite usar comandos. Puedo notar la diferencia porque tiene un pequeño androide con el cofre abierto y más información:
Bueno, estoy tratando de publicar una imagen pero fallé con 2 hosts de archivos diferentes ... -.-
Escribiré el texto aquí:
Y el fastboot "MALO" se ve así, y no tiene Android y el texto de las opciones es simplemente rojo / verde / con texto de color (el otro muestra el texto en un globo). Y esto es lo que muestra:
adiós
Click to expand...
Click to collapse
Hola, a mí me está pasando lo mismo que a ti al principio. ¿Puedes decirme cómo lo resolviste al menos para que aparezca el fastboot "BUENO", que me permite usar comandos. Entonces, para poder notar la diferencia del androide con el cofre abierto

Categories

Resources