Twrp - efs - imei - Moto X4 Questions & Answers

I installed Lineage and somehow lost my IMEI.
I reverted back to stock and restored the EFS backup in TWRP.
My IMEI still shows as 0 and I cannot make calls.
Any ideas???

I had the same problem what I did was download Android 8.1 and then update to the latest patch with Android 9.0 and it worked.
Android 8.1
Android 9.0

That worked, thank you

Hola bro ami me pasa lo mismo y tambien soy de mexico entonces lo que ago es instalar android 8.1 actualizo asta el urtimo parche y espues instalo android 9 por medio de fastboot o recovery?

If you download it to Android 8.1 and upload it again to Android 9 .0
But not by twrp it is by means of commands

Thank you for this post. I made the same mistake with my mom's G6 and I thought lineage had corrupted the IMEI has it had before to my G5s plus. But then I read this and the comments, (luckily I have an x4 and read the forum from time to time) and was like oh duh, so I flashed the most current stock rom to her phone and it fixed it.

Related

Hardbricked Moto X xt1058 with 5.1 Brazil

ENGLISH: i installed stock 5.1 brazil in my Moto X XT1058, after starting are a new update (not the camera) said it was of stagefright and i clicked install, when it was installing my phone shutdown and no start more .
My PC does not recognize in any way my Moto X, does not sound, and no recharges the list in "device administrator" .
The only thing you notice is that after leaving for a while loading my Moto X was heated slightly
Name of stock rom zip: XT1058_GHOST_RETBR_5.1_LPA23.12-15_cid12_CFC.xml.zip
Spanish: Flashee mi Moto X 1gen a 5.1 brasil, luego de iniciar todo me salto una actualizacion (no es de la camara) decia que era de stagefright y le di aceptar, cuando se estaba instalando llego a la mitad, se apago y ya no enciendo mas.
Mi PC no reconoce de ningun modo mi Moto X, no suena ni se recarga la lista de dispositivos.
Lo unico que note es que luego de dejar cargando por un buen rato mi Moto X se calento un poco.. ayuda plz
Sorry for my bad english..
Hi, you have indicated that your device does not show up whatsoever in device administrator. While I can understand that this is worrying, you probably just need to set up the QHUSB drivers. It does not sound like you messed up as bad as I did. As long as you haven't flashed a bootloader or partition table that is incompatible you should be safe to do perform a blank flash then reflash your device with the stock firmware.
This should at least get you back into your bootloader so that you can flash your stock firmware.
This might be a bit simpler to follow, but it is the less effective method (some people do still report success with it).
This will have your stock firmware. Do try to flash the right version. RSDLite can simplify the matter, but the commands are pretty universally used in fastboot.
Good luck!

Stock Nougat 7.0 Downgrade for Binary 3

YOU ARE NOT ALLOWED TO USE ANY PART OF THIS ROM WITHOUT MY PERMISSION
Attention
The rom and the bootloader provided in this topic and to be used in a device where the Bootloader Binary has been changed to 3, devices where the binary has not been altered that is in Binary 1 or 2, it is not necessary to use these files to Downgrade. If you use and come, there is an error such as: Loss of IMEI, Battery Bug, Super Heating, Boot Random. I am not responsible for any errors caused by user error or misuse.
Instruction:
1º Download the most recent version of Odin or it can be the version also v3.10.
2nd Download the files needed to downgrade.
3º Open Odin, and in the AP put the file with the name (bootloaderDowngrade.tar) of the start to start the procedure. The unit will restart by itself. Go back in download mode again and in AP put the file (Downgrade Nougat 7.0.0 Binary 3.tar) of the start again leaves until the device restarts normally.
Note: The first start of it may take 5 to 10 minutes.
4º After the procedure is finished, the phone will restart with ROM STOCK Nougat 7.0, NO ROOT and NO MODIFICATION (ROM IS FACTORY). However this procedure did not allow updating by OTA, because in this procedure the Binary will still continue with B3 and file is with binary combination. But when installing any other ROM STOCK when passing them on ODIN, just do not put the Bootloader of 6.0 or 8.1.0 in the BL option. Only use the stock files as standard AP, CP and CSC.
Download:
bootloaderdowngrade
Downgrade Nougat 7.0.0 Binary 3
Donation:
Click Here
XDA:DevDB Information
Nougat 7.0 Downgrade By Pass Binary 3, ROM for the Samsung Galaxy J7
Contributors
darkfalling
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Version Information
Status: Stable
Stable Release Date: 2018-11-07
Created 2018-11-07
Last Updated 2018-11-07
reserved
Reserved
Hi there!
There is a way to get root?
Thanks for your job.
¡Hola!
Espero obtener el link por favor ya que actualize y quisiera bajar, muy buen aporte.
darkfalling said:
YOU ARE NOT ALLOWED TO USE ANY PART OF THIS ROM WITHOUT MY PERMISSION
Attention
The rom and the bootloader provided in this topic and to be used in a device where the Bootloader Binary has been changed to 3, devices where the binary has not been altered that is in Binary 1 or 2, it is not necessary to use these files to Downgrade. If you use and come, there is an error such as: Loss of IMEI, Battery Bug, Super Heating, Boot Random. I am not responsible for any errors caused by user error or misuse.
Instruction:
1º Download the most recent version of Odin or it can be the version also v3.10.
2nd Download the files needed to downgrade.
3º Open Odin, and in the AP put the file with the name (bootloaderDowngrade.tar) of the start to start the procedure. The unit will restart by itself. Go back in download mode again and in AP put the file (Downgrade Nougat 7.0.0 Binary 3.tar) of the start again leaves until the device restarts normally.
Note: The first start of it may take 5 to 10 minutes.
4º After the procedure is finished, the phone will restart with ROM STOCK Nougat 7.0, NO ROOT and NO MODIFICATION (ROM IS FACTORY). However this procedure did not allow updating by OTA, because in this procedure the Binary will still continue with B3 and file is with binary combination. But when installing any other ROM STOCK when passing them on ODIN, just do not put the Bootloader of 6.0 or 8.1.0 in the BL option. Only use the stock files as standard AP, CP and CSC.
Download:
bootloaderdowngrade
Downgrade Nougat 7.0.0 Binary 3
Donation:
Click Here
XDA:DevDB Information
Nougat 7.0 Downgrade By Pass Binary 3, ROM for the Samsung Galaxy J7
Contributors
darkfalling
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Version Information
Status: Stable
Stable Release Date: 2018-11-07
Created 2018-11-07
Last Updated 2018-11-07
Click to expand...
Click to collapse
Muchas Gracias! funciono perfecto. hay alguna manera de obtener root?? no acepta el recovery de twrp
Great!
Why did not you use a more current version of the nougat system?
jbryanr022 said:
Muchas Gracias! funciono perfecto. hay alguna manera de obtener root?? no acepta el recovery de twrp
Click to expand...
Click to collapse
Without TWRP and ROOT forecast, I'm working to resolve this. I get for ROOT and TWRP but because of the Binario continue in 3, TWRP gets the Bug that can not access internal space and even with this bug. But you can turn it on but it stays on a black screen saying it's a problem.
Rod_1980 said:
Great!
Why did not you use a more current version of the nougat system?
Click to expand...
Click to collapse
Even putting a current version of Android would not change at all. I am using my J7 G610M to do this procedure and the other recent firmware the Binary of it are all of end 1 ... and change 6 by half dozen.
Ops, I commented on the wrong post. Sorry
Como vuelvo a instalar una version 8.1 oficial en mi telefono , ya que no me deja
Cyanogem said:
Como vuelvo a instalar una version 8.1 oficial en mi telefono , ya que no me deja
Click to expand...
Click to collapse
Puede instalar el 8.1.0 en su teléfono por el odin sin ningún problema, vea si esta usando la ROM correcta pues no hay nada que te impida instalar el OREO, el único error es del downgrade a 6.0.1 y 7.0 binario 3 no se permite.
amigo, esto puede servir para un s7 que esta en binario 3? gracias
draconash said:
amigo, esto puede servir para un s7 que esta en binario 3? gracias
Click to expand...
Click to collapse
No puede, en el sitio de Sammobile tiene el firmware con revisión para Binario 3
Hola amigo si Sabes Montar eso de roms Y Modificarlas, Tengo una gran idea Para este mismo Cell. Como pude encontrar el J7-j700t Cuenta con Nougat 7.1.1 en Bootloader 3. Los dispositivos Tiene Casi todas Las mismas funciones. Creo que Serviría Mucho si Lograses Adaptar esa Rom Para este dispositivo, Que Opinas? La rom esta en Sammobile/firmwares/galaxy-j7/SM-J700T/TMB/download/J700TUVU3BQK3/196920/
can i use this firmware to g610y model? hoping that it could fix unknown baseband issue.already tried latest binary 2 firmware but still unknown baseband
can i install it and flash supersu by otg without issues? Thanks!
another thing... there is a rom for j7 j700t wich is in binary 3 with nougat 7.1.1. you can convert it for j7 prime. the both ones have the same characteristics!
Downgrading I remove the LTE option in the second line of mobile only worked in E... Line 1 was left in H and H+, disabling one of the lines could only access LTE :laugh:
No me deja insalar Downgrade Nougat 7.0.0 Binary 3.tar Se queda en setupconecction, ayuda pls (((!!
I can not install Oreo 8.0 firmware
Cyanogem said:
Como vuelvo a instalar una version 8.1 oficial en mi telefono , ya que no me deja
Click to expand...
Click to collapse
the same happens to me
After doing this, can I install an android 8.0 firmware? Because when I start Odin, it does not let me install what can I do to install the bt and its most current firmware?

Amazon X4 will not OTA, can I sideload to Pie?

I bought an ebay special really cheap x4 and it turns out it is the Amazon version. To make matters even worse; the phone is hungup on a security update it keeps trying but it will not complete. Besides that, the phone is fine.
I would like to update it to the newest version of the Amazon firmware manually, flashing it, if that is possible somehow? I downloaded the firmware from the Motorola Android Team site, now I just need to know how to do it, is it possible to sideload to Pie? The current version it has is Oreo 8.1
Build number OPW28.3
Motorola Version
OPW28.46-21
My phone will download a security update via OTA, but is never able to finish updating it, and so never gets to OTA Pie.
saludos usa este programa Lenovo Moto Smart Assistant es oficial y te lo actualiza a la ultima version de firmware existente para el modelo motorola que tengas
jesusno said:
saludos usa este programa Lenovo Moto Smart Assistant es oficial y te lo actualiza a la ultima version de firmware existente para el modelo motorola que tengas
Click to expand...
Click to collapse
Thank you that is very helpful! I have installed it to my PC and I am downloading the update, which is PPWS29.69-39-6-1
Is it possible to backup the entire phone including the ROM with this application before updating, in case of any problems? I hope it works alright after the update!
I do see this app has "rescue mode", maybe that is all I would need if it goes bad?
Thanks again! Really nice app to upgrade the phone "lenovo smart assistant " to flash the latest update to my Motorola X4!
jesusno said:
saludos usa este programa Lenovo Moto Smart Assistant es oficial y te lo actualiza a la ultima version de firmware existente para el modelo motorola que tengas
Click to expand...
Click to collapse
Darn it failed! Something wrong with this phone but it works just unable to update
motorola smart assitant "failed to clean up factory mode"
I wonder about this "factory mode" on the phone, and could that be useful?
Thank you, this worked! It was saying it failed but putting it in factory mode it finished the install after i unplugged it Wild

Sensors don't work and can't calibrate camera after flashing fastboot ROM

I was in Syberia Android 11 and wanted to go back to Android 10 so I flashed RR but after it booted the sensors and front camera didn't work so I flashed fastboot ROM 12.20 but the camera and sensors don't work either, when I try to calibrate it says it couldn't calibrate.
How can I fix this? Thanks in advance
Isley_ said:
I was in Syberia Android 11 and wanted to go back to Android 10 so I flashed RR but after it booted the sensors and front camera didn't work so I flashed fastboot ROM 12.20 but the camera and sensors don't work either, when I try to calibrate it says it couldn't calibrate.
How can I fix this? Thanks in advance
Click to expand...
Click to collapse
try flashing persist image from your fastboot rom folder.
I had same calibration issue when coming from oss vendor rom to miui vendor and litrerally today.
So i booted oxfox and flashed persist image which is present in my fastboot rom folder and after that camera calibrated fine. It asked to caliberate and this time no errors after that i changed rom to evox a11 no issues.
Ezio553 said:
try flashing persist image from your fastboot rom folder.
I had same calibration issue when coming from oss vendor rom to miui vendor and litrerally today.
So i booted oxfox and flashed persist image which is present in my fastboot rom folder and after that camera calibrated fine. It asked to caliberate and this time no errors after that i changed rom to evox a11 no issues.
Click to expand...
Click to collapse
I flashed persist from TWRP and it worked, thanks a lot
[QUOTE = "Ezio553, publicación: 84025973, miembro: 9272113"]
intente flashear la imagen persistente desde su carpeta rom fastboot.
Tuve el mismo problema de calibración cuando venía de la rom del proveedor de oss al proveedor de miui y literalmente hoy.
Así que arranqué oxfox y mostré la imagen persistente que está presente en mi carpeta de fastboot rom y luego la cámara se calibró bien. Pidió calibrar y esta vez no hubo errores después de eso cambié la rom a evox a11 sin problemas.
[/CITAR]
ME puedes decir los pasos que debo seguir para hacer eso porfavor te lo agradecería mucho
Gabriel 059 said:
[QUOTE = "Ezio553, publicación: 84025973, miembro: 9272113"]
intente flashear la imagen persistente desde su carpeta rom fastboot.
Tuve el mismo problema de calibración cuando venía de la rom del proveedor de oss al proveedor de miui y literalmente hoy.
Así que arranqué oxfox y mostré la imagen persistente que está presente en mi carpeta de fastboot rom y luego la cámara se calibró bien. Pidió calibrar y esta vez no hubo errores después de eso cambié la rom a evox a11 sin problemas.
[/CITAR]
ME puedes decir los pasos que debo seguir para hacer eso porfavor te lo agradecería mucho
Click to expand...
Click to collapse
can u write this in english as i don't understand this..
I have the same problem. I flashed fastboot recovery via twrp. Sensors started working but camera still won't pop up. Is it another issue? Please help.
Kailas142 said:
I have the same problem. I flashed fastboot recovery via twrp. Sensors started working but camera still won't pop up. Is it another issue? Please help.
Click to expand...
Click to collapse
Try flashing the persist.img from the fastboot ROM in recovery. Just make sure it's the persist.img from a fastboot fastboot ROM (a fastboot ROM that is flashed via recovery)
Will it work of if I do a backup via Orfox Recovery of my working persist.img ( with both camera and sensor working) on Android 10 and restore (if necessary) when switching between A10 to A11 or A11-10 or OSS Vendor-MIUI Vendor ?
I've done something like that before, you can try
Does than mean I have to flash fastboot rom then backup persist there? Can .tgz file be flashed in recovery? Or do I download .zip of fastboot rom?
Kailas142 said:
Does than mean I have to flash fastboot rom then backup persist there? Can .tgz file be flashed in recovery? Or do I download .zip of fastboot rom?
Click to expand...
Click to collapse
Learn here about differences between fastboot/tgz vs recovery/zip firmware, how to flash, etc
How to Install MIUI Fastboot ROM - android file box
For some reasons you may want to completely re-install Android OS running on your Xiaomi phone either Mi series or Redmi series. While updating the ROM is simply a one-tap action through...
androidfilebox.com
Btw, you can also extract persist.img from tgz (tar, gzip archive) and flash from Fastboot.
However, if you lost DRM L1 license (due to playing with custom ROMs) and if you didn't back-up your original persist.img, you cannot repair by flashing tgz or its exteacted persist.img
It worked, twrp flashable fastboot zip solved it. Thx archieve persist file didn't work. Thanks man

Question Mi 11 bricked

Hello,
I unfortunately bricked my Mi11. I flashed Android 12, worked. Then miui eu 12.6, worked. As I wanted back to the western Europe miui 12.5.1, the phone stopped installing and nothing worked anymore. Every time I reboot it, it boots into fastboot mode. I tried miflash, didn´t work. MiToolsV2 didn´t work either, also fastboot. I don´t know what to do anymore. Could somebody please help me?
Edit:
Seems I solved it with an quite old eu version.
Blubber120 said:
Hola
Desafortunadamente bloqueé mi Mi11. Parpadeé Android 12, funcionó. Entonces miui eu 12.6, funcionó. Como quería volver a Europa occidental miui 12.5.1, el teléfono dejó de instalarse y ya nada funcionó. Cada vez que lo reinicio, arranca en modo fastboot. Probé miflash, no funcionó. MiToolsV2 tampoco funcionó, también fastboot. Ya no sé qué hacer. ¿Podría alguien por favor ayudarme?
Editar:
Parece que lo resolví con una versión bastante antigua de la UE.
Click to expand...
Click to collapse
As it did? Pass me the link?
I also got bricked few times. Just download stable miui and flash it with official miui flash tool. Clean data when flashing.

Categories

Resources