TUTORIAL REALIZADO POR F.J.V
Si copia este tutorial mencione al creador y fuente.
Hi, I can not post an external link, so I translate with google translator from Spanish:
Hi, I leave a modified experimental version of cwm 6.0.3.6 my Marcinbar published.
I realize that I am not responsible of functioning, I have done for me and I thought it appropriate to share, but I can say that I have been using it for several days, and I miss many tests without problems.
Also I have to warn you that I am not a programmer or anything, everything I miss so I searched google and I found out testing and risking my own phone, but I have not invented anything, what I miss is what I have seen in other versions of cwm that worked perfectly.
Well, I put tutorial, but I will explain step by step what I miss, because it would be long, those who understand a bit because I can easily do my cost me hehe. If ever I have time I explain to people without knowledge, but some linux should know, not much, I know nothing and through Gloogle I've been looking into what I need.
First the point, why the cwm 6.0.3.6 and other versions of cwm our mobile and others do loop?
Well, it may be for several reasons, but in our case, (gt-gt-s6310 s6310n compatible) is a very simple issue, but find out after many hours of watching ... missing a configuration file.
The file is postrecoveryboot.sh and going in the sbin folder of recovery.img ramdisk.
This file've seen in the latest versions of cwm, although varies with the make and model of the terminal, I took one with an architecture similar to ours as much, and I just changed the partition line specifies your terminal to point to the partition 14, which is our terminal. I notice that if you want to try on a different terminal, you have to find out what the "PARAM" or "PARAMETER", in our case the partition 14. In the same file is explained, I have not changed.
Well that's all, for those who want to know what I miss in the attached recovery.img explain it:
1 Unpack. Who does not know how it's done google search, you can even do in windows, but I did it in linux, ubuntu, there are easy to find tutorials.
2 Change the kernel. This is optional. I changed the kernel by the most modern S6310N, bringing with worked fine, but could not mount partition "sd-ext" in case you want to format, but rather the sd partitioned, and formatted with partitioning.
3 In the ramdisk, add to the root file_contexts an empty file called. This is optional. Not useless, just not to leave the warning that the file is missing, the ideal would be to have it, but do not know where or how to generate it out, so better vacuum with another terminal.
4th Back in the ramdisk, add the file already commented postrecoveryboot.sh in sbin folder. This is very important to add, but the loops that keep us out of cwm appear.
5th Amend recovery.fstab file is in the etc folder of the ramdisk. This is also optional, in that brings functions, I added a modified, derived from the version stock-added, but is the same as bringing the cwm with an added line to mount sd-ext and we can format it without partition sd card again. This file gives a lot of play in the end I opted to leave practically already had, but can be modified to recognize both "internal" and external sd, but after several tests have ruled this release that prevents us format the sd card.
6th Repackage for our new recovery.img. Then it's a matter of flashing this recovery on your terminal, for which we can choose the option that suits us. I have used a zip that usually go well, flash the cwm recovery.img through. If you need the recovery.img stick out of the zip.
CREDITS:
Thank you for letting me post Marcinbar a modified recovery.img yours.
Thanks to google, without the side I would ever do this.
Well, I think that I will not forget anything. Those who dare to try to be commenting to see how it goes. Greetings.
En español:
Hola, les dejo una versión experimental modificada por mi del cwm 6.0.3.6 publicado por Marcinbar.
Advierto que no me hago responsable del funcionamiento del mismo, lo he hecho para mi y he creído conveniente compartirlo, pero puedo decir que llevo utilizándolo varios días, y he echo muchas pruebas sin problemas.
También tengo que advertir que no soy programador ni nada parecido, todo lo que he echo lo he buscado por google y lo he averiguado probando y arriesgando mi propio teléfono, pero no me he inventado nada, lo que he echo es lo que he visto en otras versiones de cwm que funcionaban perfectamente.
Bueno, he puesto tutorial, pero no voy a explicar paso por paso lo que he echo, porque seria largo, los que entiendan un poco pues lo podrán hacer fácilmente, a mi me ha costado jeje. Si algún día tengo tiempo lo explico para gente sin conocimientos, pero algo de linux debe de saber, no mucho, yo no se nada y a través de gloogle me he ido buscando lo que me hacia falta.
Primero al grano, ¿porqué el cwm 6.0.3.6 y otras versiones de cwm de nuestro móvil y otros hacen loop?
Bueno, puede ser por varios motivos, pero en nuestro caso, (gt-s6310 gt-s6310n y compatibles) es por un tema muy sencillo, pero que averigüe después de muchas horas de observar... falta un fichero de configuración.
El fichero es postrecoveryboot.sh y va en la carpeta sbin del ramdisk del recovery.img.
Este fichero lo he visto en las ultimas versiones de cwm, y aunque varia según la marca y modelo del terminal, he cogido uno con una arquitectura lo mas parecida al nuestro, y solo he modificado la linea de la partición especifica de nuestro terminal, para que apunte a la partición 14, que es la de nuestro terminal. Advierto que si lo quieren probar en un terminal distinto, tienen que averiguar cual es la partición "PARAM" o "PARAMETER", en nuestro caso la 14. En el mismo archivo viene explicado, no lo he modificado.
Pues eso es todo, para el que quiera saber que es lo que he echo en el recovery.img que adjunto lo explico:
1º Desempaquetar. Quien no sepa como se hace buscar en google, incluso se puede hacer en windows, pero yo lo hice en linux, con ubuntu, hay tutoriales fáciles de encontrar.
2º Cambiar el kernel. Esto es opcional. Yo he cambiado el kernel por el mas moderno de S6310N, con el que traía funcionaba bien, pero no podia montar la particion "ext-sd" por si la quiero formatear, pero si particiona bien la sd, y la formatea con el particionado.
3º En el ramdisk, añadir a la raiz un fichero vacío que se llame file_contexts. Esto es opcional. No sirve para nada, solo para que no salga la advertencia de que falta el fichero, lo ideal seria tenerlo, pero no se de donde sacarlo o como generarlo, así que mejor vacío que con el de otro terminal.
4º De nuevo en el ramdisk, añadir el fichero ya comentado postrecoveryboot.sh en la carpeta sbin. Esto es muy importante de añadirlo, sino aparecerán los bucles que no nos dejan salir de cwm.
5º Modificar el fichero recovery.fstab que está en la carpeta etc del ramdisk. Esto también es opcional, con el que trae funciona, yo he añadido uno modificado, sacado de la versión stock con añadido, pero es igual que el que trae el cwm con una linea añadida para montar sd-ext y que podamos formatearla sin tener que particionar de nuevo la tarjeta sd. Este fichero da mucho juego, al final he optado por dejar prácticamente el que ya traía, pero se puede modificar para que reconozca tanto la sd "interna" como la externa, pero después de muchas pruebas he descartado publicar esta versión porque nos impide formatear la tarjeta sd.
6º Volver a empaquetar para obtener nuestro nuevo recovery.img. Luego ya es cuestión de flashear este recovery en nuestro terminal, para lo que podemos elegir la opción que más nos convenga. Yo he aprovechado un zip que me suele ir bien, flashea el recovery.img a traves de cwm. Si necesitáis el recovery.img lo sacáis del zip.
CREDITOS:
Gracias a Marcinbar por dejarme publicar un recovery.img modificado del suyo.
Gracias a google, sin el me hubiera costado siglos hacer esto.
Bueno, creo que no se me olvida nada. Los que se atrevan a probarlo que vayan comentando a ver como les va. Saludos.
published in htcmania.com
How do I install this into the phone? Can I use Odin?
razvangrig said:
How do I install this into the phone? Can I use Odin?
Click to expand...
Click to collapse
No. It's a zip to install from cwm. To install from odin you must extract recovery.img from the zip format and compress it to odin.
hi when i got the cwm reboot loop i found very simple solution by my self all i had to do is to install cwm img "recovery.tar.md5" with odin and it worked
stifbaker7 said:
hi when i got the cwm reboot loop i found very simple solution by my self all i had to do is to install cwm img "recovery.tar.md5" with odin and it worked
Click to expand...
Click to collapse
English language generated by google translator:
Well you've been very lucky. It's like you buy a lottery ticket for the first time and touch him. Not to say that if you buy one ticket you play again.
If you go into a loop with this cwm is a very small chance that is fixed by simply flashing odin recovery.tar.md5, for one simple reason, the problem is not in the recovery partition.
Do not talk the talk, I tried that method you mention, not served me. And when I made the modification I post I tried several ways to exit the loop.
Sign loop is very easy, just make a recovery from cwm reboot when entering advanced startup and make a power off, and see how you are no longer able to start the terminal, take you time and again to cwm.
The unique methods that worked for me before making this modification was to install the original recovery by odin and then reinstall cwm, with all the waste of time that entails, or another method much easier, use a temporary cwm from another terminal published by ocoot, which is very comfortable, you take on the phone and if you get this temporary loop install cwm, reboot and go.
Even so, the method to flash by odin has the disadvantage that if you enter the loop away from a PC with odin you have to wait to use your phone.
All this is fine, but what I propose is to forget the loops. Just a little cwm person using it may not want to risk, but for the sufferer often loops certainly prefer to forget it.
Having said all this, I'll upload the flashable by odin version is the same zip, but ready for odin.
md5sum:
a47cc51b2b7fed7d137b01e52c908b94 recovery.tar.md5
here you can not upload a file with the extension .md5, so I upload a zip called decompress.zip, obviously unzip. Decompress.zip not install, unzip for recovery.tar.md5
regards
versión original en español:
Pues has tenido mucha suerte. Es como quien compra un boleto de loteria por primera vez y le toca. No quiere decir que si compras otro boleto te vuelva a tocar.
Si entras en un bucle con este cwm hay una posibilidad muy pequeña de que se arregle simplemente flasheando por odin recovery.tar.md5, por una simple razón, el problema no está en la particion de recovery.
No hablo por hablar, yo probé ese metodo que comentas, y no me sirvio. Y cuando hice la modificacion que publico probé varias formas de salir del bucle.
Entrar en bucle es muy facil, simplemente desde cwm haz un reboot recovery, cuando arranque entra en avanzado y haz un power off, y veras como ya no eres capaz de iniciar el terminal, te lleva una y otra vez a cwm.
Los unicos metodos que me funcionaron antes de hacer esta modificacion fue instalar por odin el recovery original, para luego volver a instalar cwm, con toda la perdida de tiempo que eso conlleva, u otro metodo mucho mas facil, utilizar un cwm temporal de otro terminal, publicado por ocoot, que es muy comodo, lo llevas en el movil y si te entra en bucle instalas este cwm temporal, reinicias y listo.
Aun así, el metodo de flasear por odin tiene el inconveniente de que si entras en bucle fuera del alcance de un PC con odin, tienes que esperar para poder utilizar tu telefono.
Todo esto está muy bien, pero lo que yo propongo es olvidarse de los bucles. Igual a una persona que utilice poco cwm puede que no quiera arriesgar, pero para el que sufre bucles muy a menudo seguro que prefiere olvidarse del tema.
Y dicho todo esto, voy a subir la version flasheable por odin, es la misma del zip, pero lista para odin.
suma md5:
a47cc51b2b7fed7d137b01e52c908b94 recovery.tar.md5
aqui no se puede subir un archivo con extensión .md5, asi que subo un zip que se llama decompress.zip, que evidentemente hay que descomprimir. No instalar decompress.zip, descomprimir para obtener recovery.tar.md5
Saludos
Did anyone says?
I guess those who have downloaded without errors.
It is easier to complain than to comment
¿Will be interested to read also the internal memory?
Greetings.
tested on xxana1, its working.... Thanks bro....
odin flash-able
if you need this cwm file install with odin,go here http://forum.xda-developers.com/showthread.php?t=2281287
or download http://d-h.st/xsac , flash odin,put to PDA
Generated by translator bing English
Comment if they detect any failure.
I have detected a slight error formatting second partition of the sd.
Partition the SD card work properly, creates the first partition "fat", and the second can choose "ext3" or "ext4" and if we want another 3rd "swap".
The error occurs if you have partitions and want to format only the 2nd partition. With "ext4" format, there is no error, but if you have "ext3" formatting is transformed into "ext4" format.
To correct the error, change recovery.fstab. The entry "sd-ext" change "ext4" by "auto". Now the format is according to the type of partition.
Best regards.
En español:
Comenten si detectan algun fallo.
He detectado un pequeño error al formatear la 2º particion de la sd.
Particionar la sd funciona correctamente, crea la 1ª particion "fat", y la 2ª podemos elegir "ext3" o "ext4" y si queremos otra 3ª "swap".
El error ocurre si ya tenemos las particiones y queremos formatear solo la 2ª particion. Con el formato "ext4" no hay error, pero si tenemos "ext3" al formatear se transforma en formato "ext4".
Para corregir el error, modificar recovery.fstab. En la entrada "sd-ext" cambiar "ext4" por "auto". Ahora el formato será según el tipo de partición.
Saludos.
Si copian y publican el tutorial mencionen al creador y la fuente
If they copy and publish the tutorial mention to the creator and the source
Today many downloads and no comments
cwm working well?
do you find them well the tutorial?
Best regards
Im confused what does it actually do.
Does it get you out of CWM boot or it fix the problem that causes CWM boot loop
Waiting for replay
Thanks
Sent from my GT-S6312
Fix problem
F.J.V said:
Fix problem
Click to expand...
Click to collapse
[emoji1] wow man i tried it yesterday working perfectly thankyou you are awesome
Sent from my GT-S6312
Thanks alot...you saved me from reflashing stock rom again..
[Help][Galaxy S6312]
Can you tell me from where did you get this file ?
Is it 100% working ?
I am also in the same problem.
http://forum.xda-developers.com/galaxy-young/help/help-able-to-exit-cwm-v6-0-3-2-recovery-t3290547
amitkumar005 said:
Can you tell me from where did you get this file ?
Is it 100% working ?
I am also in the same problem.
http://forum.xda-developers.com/galaxy-young/help/help-able-to-exit-cwm-v6-0-3-2-recovery-t3290547
Click to expand...
Click to collapse
Thanks, it works
amitkumar005 said:
Can you tell me from where did you get this file ?
Is it 100% working ?
I am also in the same problem.
http://forum.xda-developers.com/galaxy-young/help/help-able-to-exit-cwm-v6-0-3-2-recovery-t3290547
Click to expand...
Click to collapse
In google translator from Spanish.
Hello amitkumar005 what I did was unpack several CWM version of it but other terminals and working without error. Checking these in 6310, I had the problem of loop, I realized postrecoveryboot.sh missing.
All postrecoveryboot.sh do basically the same thing, calling a particular partition and passes parameters. The only differences between the various I saw was the way to get to the partition, depending on the type of terminal, and that the partition is specific to each terminal.
What I did was take a postrecoveryboot.sh not remember which specific terminal was, but it was a version 6.0.3.6 and made sure that the call to the correct partition was for 6310, which is the same as 6312. I could choose from several ways to call the partition, and between putting the same name or number, as proved in several different ways and all worked, but as I had to publish a then chose to publish in its day. With version 6.0.3.2 spent exactly the same, so the solution is the same.
I published the files are the original version of CWM 6.0.3.6 with postrecoveryboot.sh modified by me.
The postrecoveryboot.sh file is not my invention nor is any patch or anything, just missing and I added and adapted to the parameters of our terminal.
Regards.
Hola a todos,
He decidido crear este hilo con informacion de este dispositivo, porque es bastante dificil encontrar algo de soporte.
De momento solo se que se puede rootear (yo utilice kingroot), hacer un backup del sistema con flashfire de chainfire y utilizar una herramienta de QPST
que viene con el programa que se llama QFil.
El motivo!!!?, pues que si a mi me ha costado:crying::crying: mucho, no quiero imaginar a la persona que se ponga la primera vez.
Asi que voy a empezar...
1- al rootear el dispositivo copia de seguridad de EFS, con las herramientas efs backup y/o partitions backup y guardarlo en lugar seguro.
2-opcional cambiar supersu por su chino de kingroot, si quereis hacer backup con flashfire os hara falta cambiarlo.
3-drivers qualcomm, yo instale qualcomm hs-usb device 9091 y me reconocia el movil. antes ya tenia instalado los adb fastboot drivers en mi pc.
4-QPST programa para hacer tambien copia de seguridad de modem pero con archivos.qcn, flash de roms, etc.
5-QFil programa de QPST, que se encuentra en la carpeta bin.
6-De todas formas tendreis que buscar por internet, pero mejor esto que volverse loco/a.
Yo de momento, repíto, aparte de tener el movil con root, hice una prueba de flasheo con QFile.
La carpeta la encontre buceando por internet después de horas y aunque no tenia el movil con brick de ningun tipo funcionó.
Puse android 5.1.1 y no falló nada,ni red,ni wifi ni nada,solo tuve que volver a rootear.
7- Entrar en recovery: power+volumen(-)+volumen(+), entrar en modo descarga: power+volumen(+), aqui aparece un menú chino, no tocar nada. Conectar al pc y listo.
8-Os dejo un enlace de mega con la carpeta para este dispositivo. Espero que esto ayude a alguien sino bien ahora, en el futuro.
https://mega.nz/#F!XAkUDajB!EaYNGGsABPapaVFkeGNqTw
Hello everyone,
I have decided to create this thread with information of this device,because it is quite difficult to find some support.
At the moment I only know that it can be rooted (I use kingroot), make a backup of the system with flashfire of the chainfire and use a tool of QPST
which comes with the program called QFil.
The reason !!',Because if it cost me:crying::crying: much, I do not want to imagine the person who puts the first time.
So I´m going to start...
1-When rooting, efs backup device, with efs backup tools and/or partitions backup and save it in a safe place.
2-Optional switch supersu for your chinese su, if you want to backup with flashfire you will need to change it.
3-Drivers Qualcomm, I install qualcomm hs-usb device 9091. Before I had installed the adb fastboot drivers on my pc.
4-QPST program to do also modem backup but with .qcn files, roms flash,etc.
5-QFil QPST program, which is located in the bin folder.
6-Anyway you will have to search the internet, but better this than going crazy.
For now, I repeat, apart from having the cell with root, I did a flash test with QFile.
The folder I found diving on the internet after hours and although I had the mobile with no brick of any kind worked.
I put android 5.1.1 and nothing failed, network,wyfy,or anything, I just had to re-root.
7-Enter to recovey: power+volume(-)+volume(+), enter to download modeower+volume(+),here a chinese menu appears, do not touch anything. Connect to pc.
8-I leave you mega link the folder for this device. I hope this helps somebody but well now, in the future.
https://mega.nz/#F!XAkUDajB!EaYNGGsABPapaVFkeGNqTw
Hola tengo un problema, he buscado en todos lados y no he encontrado la solución, espero me puedan ayudar:
Tengo dos Alcatel 4060a (los nombraré como Alcatel 1 y Alcatel 2 para evitar confusión), le hice un back up a Alcatel 1 y se lo instale a Alcatel 2. Me he quedado sin poder usar la SIM en Alcatel 2. El IMEI está bien y el wifi también funciona simplemente no reconoce la SIM. Ah sí, también noté que la dirección Mac de Alcatel 2 es la misma que de Alcatel 1, razón por la cual no pueden estar conectados a la misma red wi-fi (siempre uno de los dos se queda sin internet). A la hora de hacer el Back up con twrp venían todas las casillas demarcadas, así que seleccioné todas:
aboot
abootbak
devinfo
efsdata
fsg
hdcp
Módem
modemst1
modemst2
simlock
splash
tctpersist
traceability
tunning
Boot
Recovery
Cache
System
Data
Sí al principio parecía buena idea :'(
English:
Hello, I have a problem, I have searched everywhere and I can not find the solution, I hope you can help me:
I have two Alcatel 4060a (I will name them Alcatel 1 and Alcatel 2 to avoid confusion), I made a backup of Alcatel 1 and installed it on Alcatel 2. I could not use the SIM on Alcatel 2. The IMEI is fine and the wifi also it works, it simply does not recognize the SIM card.I also noticed that the Mac address of Alcatel 2 is the same as that of Alcatel 1. When I made the backup with twrp, I selected all the boxes:
aboot
abootbak
devinfo
efsdata
fsg
hdcp
Módem
modemst1
modemst2
simlock
splash
tctpersist
traceability
tunning
Boot
Recovery
Cache
System
Data
alcatel 4060a
hi, alice05 the truth is that I dont know that model,but if you have a pc there is tool called mauimeta that directly installs imeis on phones with mediatek processors.
https://www.youtube.com/watch?v=VEYVoDM2uHw
find out if the processor is mediatek, if it is, this tool is perfect and easy to install and use.
find out first what processor you have and if I can help you I would be happy to do so.
I forgot to tell you that you needed the originals imeis.
I pass this link if you want to try it, I think the processor of your mobile is qualcomm.
https://firmwarefile.com/alcatel-ideal-4060a
help need the bankflash for the version MOTO G7 POWER XT1955-2(OCEAN) please
I sorry for the translation
I;m actually on the same boat for using a common firmware XD
It seems to happen almost specifically for xt1955-2s tho, tried using blankflash from the loli website and I noticed I do get something among the lines 'unknown msm8953' or something, wonder what's going on
I've been trying to get a partitions.xml but the py script I use throws me this:
File "GPTAnalyzer.py", line 684, in <module>
main()
File "GPTAnalyzer.py", line 662, in main
fbuf = get_part_table_area(f, gpt_header)
File "GPTAnalyzer.py", line 182, in get_part_table_area
fbuf = get_lba(f, part_entry_start_lba, first_use_lba_for_partitions - part_entry_start_lba)
File "GPTAnalyzer.py", line 80, in get_lba
fhandle.seek(LBA_SIZE*entry_number)
OverflowError: long too big to convert
Don't know enuff py to fix it, I tried running it on a 32bit system/vm, to see if it'd help but no cigar as well
Anyone else in the same boat?
I have successfully used the lolinet blankflash file on my XT1955-2
https://mirrors.lolinet.com/firmware/moto/ocean/blankflash/
Note that, since the phone is USB2 and NOT USB3, the connector must sometimes be flipped (change position) and connected to a USB2 port on your motherboard instead of a USB3 if possible.
Run the script and then connect the phone ASAP.
Needed it a couple times and always worked
does it work for Moto G7 Power XT1955-7?
DanAlucard said:
I have successfully used the lolinet blankflash file on my XT1955-2
https://mirrors.lolinet.com/firmware/moto/ocean/blankflash/
Note that, since the phone is USB2 and NOT USB3, the connector must sometimes be flipped (change position) and connected to a USB2 port on your motherboard instead of a USB3 if possible.
Run the script and then connect the phone ASAP.
Needed it a couple times and always worked
Click to expand...
Click to collapse
i have same model xt1955-2 but i cant get success still says waiting for firehose even tho i changed usb port 3 and 2 as you mentioned im on windows 10
DiegoR0922 said:
help need the bankflash for the version MOTO G7 POWER XT1955-2(OCEAN) please
I sorry for the translation
Click to expand...
Click to collapse
did you manage to repair it? / Lograste Repararlo?
Nico95f said:
i have same model xt1955-2 but i cant get success still says waiting for firehose even tho i changed usb port 3 and 2 as you mentioned im on windows 10
Click to expand...
Click to collapse
I have the same problem, it seems that it does not support the February patch / Tengo el mismo problema, parece que no es compatible con el parche de febrero. si encuentras alguna solucion nos avisas. estamos en las mismas
Miinoru said:
did you manage to repair it? / Lograste Repararlo?
I have the same problem, it seems that it does not support the February patch / Tengo el mismo problema, parece que no es compatible con el parche de febrero. si encuentras alguna solucion nos avisas. estamos en las mismas
Click to expand...
Click to collapse
estoy en la misma esperando que alguien cree un blankflash actualizado el mio es el xt1955-2 o tambien creo que hay otro metodo pero hay que tener otro telefono igual al que tienes para crear un archivo loader.img y asi ponerlo en una tarjeta sd y la colocas en tu celular y asi puede entrar al modo fastboot y mi madre justo tiene el mismo modelo que yo pero de ahi a que me lo preste no se para instalarle una rom y rootearlo no creo que me lo preste pero igual podrias investigar mas sobre ese archivo
Nico95f said:
estoy en la misma esperando que alguien cree un blankflash actualizado el mio es el xt1955-2 o tambien creo que hay otro metodo pero hay que tener otro telefono igual al que tienes para crear un archivo loader.img y asi ponerlo en una tarjeta sd y la colocas en tu celular y asi puede entrar al modo fastboot y mi madre justo tiene el mismo modelo que yo pero de ahi a que me lo preste no se para instalarle una rom y rootearlo no creo que me lo preste pero igual podrias investigar mas sobre ese archivo
Click to expand...
Click to collapse
tengo el unbrick img del xt1955-5 pero no tengo microusb. mañana comprare una y probare haber si funciona. aunque no sea la misma versión. cualquier avance lo publicare aqui igual si logras repararlo me avisas
Miinoru said:
tengo el unbrick img del xt1955-5 pero no tengo microusb. mañana comprare una y probare haber si funciona. aunque no sea la misma versión. cualquier avance lo publicare aqui igual si logras repararlo me avisas
Click to expand...
Click to collapse
ojala que funcione :fingers-crossed: yo solo probe un loader.img pero de un g7 normal y no funciono a proposito de donde conseguiste ese unbrick.img del xt1955-5 ? recuerda seguir bien los pasos para que no haya error plis :fingers-crossed:
can someone create a blank flash for the xt1955-1 in the February 2020 patch?
https://build.lolinet.com/file/blankflash_sdm632_PDOS29.114-134-9.zip
mirrors.lolinet.com offers firmware for the Moto G8 Plus.
I have a XT2019-1 on reteu. Did anyone try this with XT2019-1_DOHA_RETEU_9.0_PPI29.65-51_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip ?
My phone says it is on PPIS29.65-24-2. What does the missing S in PPI29.65-51 mean?
Me
Mounib BOULAABI said:
Me
Click to expand...
Click to collapse
Me ... and?
bornheim2 said:
Me ... and?
Click to expand...
Click to collapse
It's just a security update. Nothing new ... I am very disappointed with the lack of follow-up from Motorola. Still no Android 10 while Google phones already benefit from the first developer version of Android 11
I Tried it. No problems..
Hi.
I have tried the 29.65.51 from lolinet. It works fine.. Phone Moto G8. XT2019-1.
Flashed with fastboot.
I also have bricked my phone 3-4 times, and found how to recover by using blankflash found on lolinet.
There was a little fiddling to get it work..
Check HTML Code
What Name said:
Hi.
I have tried the 29.65.51 from lolinet. It works fine.. Phone Moto G8. XT2019-1.
Flashed with fastboot.
I also have bricked my phone 3-4 times, and found how to recover by using blankflash found on lolinet.
There was a little fiddling to get it work..
Click to expand...
Click to collapse
Shure works fine and you brick your phone because not write the correct code in fastboot terminal.
You need read the code in the firmware packet and translate the correct code in the terminal.
I use blocnote in windows to write the correct code an copy/paste in fastboot terminal and no brick for the moment.
hola tengo el moto g8 plus xt2019-2 y luego de la ultima actualizacion de seguridad automatico, el teléfono comenzó a funcionar mal, la linterna funcionaba intermitente, no se activaba turbo power con el cargador, cuando lo reinicio deja de funcionar el touch y ahora se quedo en "fastboot flash mode" y no arranca el sistema y tampoco funcionan las opciones de este menu, solo se reinicia en "fastboot flash mode". El PC no lo detecta y adb tampoco. Ya instale todos los drivers adb y motorola. Que mas puedo hacer?
Trata esto.
Axelruben said:
hola tengo el moto g8 plus xt2019-2 y luego de la ultima actualizacion de seguridad automatico, el teléfono comenzó a funcionar mal, la linterna funcionaba intermitente, no se activaba turbo power con el cargador, cuando lo reinicio deja de funcionar el touch y ahora se quedo en "fastboot flash mode" y no arranca el sistema y tampoco funcionan las opciones de este menu, solo se reinicia en "fastboot flash mode". El PC no lo detecta y adb tampoco. Ya instale todos los drivers adb y motorola. Que mas puedo hacer?
Click to expand...
Click to collapse
Si no lo detecta adb o fastboot es porque en el celular no está activada la depuración USB y para eso necesitas que inicie, ya intentaste hacer hardreset eso debería funcionar si no vas a tener que llevarlo a garantía porque por el momento no hay box para ese teléfono.