Can you guide me on a downgrade for my motorola g6 play xt1922-5 Movistar Mexico from Andorid 9 to Oreo? I installed the variant of Brazil and when I try to return to Oreo the IMEI and the base band number are deleted and I have to flash the Andorid 9 ROM to fix that problem. Excuse English is through Google translator
Quijas02 said:
Can you guide me on a downgrade for my motorola g6 play xt1922-5 Movistar Mexico from Andorid 9 to Oreo? I installed the variant of Brazil and when I try to return to Oreo the IMEI and the base band number are deleted and I have to flash the Andorid 9 ROM to fix that problem. Excuse English is through Google translator
Click to expand...
Click to collapse
Try to reflash stock firmware and DO NOT USE THESE FOLLOWING COMMANDS
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash dsp adspso.bin
REMEMBER DO NOT USE THOSE and try reflashing like normal minus those commands
Traductor de google: Intente volver a actualizar el firmware de stock y NO USE ESTOS COMANDOS SIGUIENTES
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash dsp adspso.bin
RECUERDE NO UTILICE AQUELLOS e intente volver a grabar de manera normal, menos esos comandos,
no puedo decir que no estoy intentando lol ojalá cn entiendas esto
Also what software channel version is your model for example does it say retbr. If not don't use retbr. Find the name that matches with your software channel version
ninjakira said:
Try to reflash stock firmware and DO NOT USE THESE FOLLOWING COMMANDS
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash dsp adspso.bin
REMEMBER DO NOT USE THOSE and try reflashing like normal minus those commands
Traductor de google: Intente volver a actualizar el firmware de stock y NO USE ESTOS COMANDOS SIGUIENTES
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash dsp adspso.bin
RECUERDE NO UTILICE AQUELLOS e intente volver a grabar de manera normal, menos esos comandos,
no puedo decir que no estoy intentando lol ojalá cn entiendas esto
Click to expand...
Click to collapse
That method did not work for me, I'm still losing the IMEI and the baseband number
Do not you know any other way?
My software channel is tefmx and with that intent but I can not))):
Quijas02 said:
That method did not work for me, I'm still losing the IMEI and the baseband number
Do not you know any other way?
My software channel is tefmx and with that intent but I can not))):
Click to expand...
Click to collapse
This is your firmware https://mirrors.lolinet.com/firmware/moto/aljeter/official/TEFMX/ reflash the latest Oreo firmware. If you want Android 9 flash the one for 9 but no matter what do not flash the commands I told you not to flash
ninjakira said:
This is your firmware https://mirrors.lolinet.com/firmware/moto/aljeter/official/TEFMX/ reflash the latest Oreo firmware. If you want Android 9 flash the one for 9 but no matter what do not flash the commands I told you not to flash
Click to expand...
Click to collapse
And finally, review the commands and I realized that the command to flash the recovery is missing. Should I add it?
Quijas02 said:
And finally, review the commands and I realized that the command to flash the recovery is missing. Should I add it?
Click to expand...
Click to collapse
Wow I didn't notice I didn't put that lol thanks for seeing that ive added that command lol. Yes you need to use it. Once you successfully reflash stock firmware if you are wanting to root follow my guide from the top
Quijas02 said:
And finally, review the commands and I realized that the command to flash the recovery is missing. Should I add it?
Click to expand...
Click to collapse
Did it work?
FylipeJ said:
Did it work?
Click to expand...
Click to collapse
It works but they have the wrong things listed. You skip flashing NON-HLOS.bin, the bootloader, and gpt.bin. You should flash everything else. If you downgrade from Pie to Oreo and don't have LTE, flash NON-HLOS.bin from Pie and erase modemst1 & modemst2. If you don't have sound, flash adspso.bin to dsp from Pie.
Taking advantage of the created topic, I would like help from you friends, I have the moto g6 play xt1922-5 had unlocked the bootloader and made the lock again to install the rom stock android pie, so far so good only that I installed via rsd lite da version of my device at retail-br with 2 February patch, only when the April stock retail patch update came out, I installed it with rsd lite and everything worked out, only with the retail version I'm having difficulties with the signal from operator for having installed the retail version, as the zip of the retail-br version of the April patch did not come out, I can’t install the February patch version the last one available on the official website via rsd lite which should give an error, in this case I’m trying to downgrade of the rom version and automatically the security patch too, today I unlocked it again and I'm using LOS 17, what remains for me and wait for the retail-br version zip to come out and thus be able to install via rsd lite again from rom my region
Related
Hi, first of all sorry about mi little english... I have the following issue:
I bought my Find 7 from Telcel (Mexico), the model of my find 7 is shown as Model Number: X9076 and Version Number: X9076MX_12.
I've tried to update (using both project spectrum zip and ColorOS V2.1.5i) using the methods that oppo described in their community posts (flash with stock recovery) with no success. It fails to update and reboot and the only message I get is "Actualizacion Fallida".
Would you please help me with a solution for this problem? Any workaround? It is because of telcel firmware?
My current ColorOS Version, it is V1.2.1i, Android 4.3
Thank you in advance.
Flash the recovery update from this thread first, then try to flash the COS update again.
Please help on updating OPPO Find 7 Telcel-Mexico
AngryHapposai said:
Flash the recovery update from ... first, then try to flash the COS update again.
Click to expand...
Click to collapse
Thank you very much for your answer my friend.. sadly it didn't work.. it keeps telling me "Update Failed" message.. should i try flashing the recovery img using fastboot or unlock the bootloader first (if possible on find 7)? It is safe to install any other recovery like twrp and try to update from it? The phone isn't rooted, it has stock telcel firmware.
leonardoBlancoM said:
Thank you very much for your answer my friend.. sadly it didn't work.. it keeps telling me "Update Failed" message.. should i try flashing the recovery img using fastboot or unlock the bootloader first (if possible on find 7)? It is safe to install any other recovery like twrp and try to update from it? The phone isn't rooted, it has stock telcel firmware.
Click to expand...
Click to collapse
It's possible that the update .zip you downloaded just didn't download correctly; it got corrupted or something. Maybe try downloading it again, and then try installing it again. The first tutorial has worked fine for myself and many others.
However, it is safe for you to install TWRP. I'd recommend downloading it direct from their website here . Grab the latest version available and flash it using fastboot.
BG64 said:
It's possible that the update .zip you downloaded just didn't download correctly; it got corrupted or something. Maybe try downloading it again, and then try installing it again. The first tutorial has worked fine for myself and many others.
However, it is safe for you to install TWRP. I'd recommend downloading it direct from their website here. Grab the latest version available and flash it using fastboot.
Click to expand...
Click to collapse
Thank you again for your answer.. i managed to install the recovery and the COS update using fastboot flash and the recovery img (version 4.3) from the zip file... Now I'm setting up mi Google account on the device... so it's done...thank you so much for your assistance.
leonardoBlancoM said:
Thank you again for your answer.. i managed to install the recovery and the COS update using fastboot flash and the recovery img (version 4.3) from the zip file... Now I'm setting up mi Google account on the device... so it's done...thank you so much for your assistance.
Click to expand...
Click to collapse
No problem!
leonardoBlancoM said:
Hi, first of all sorry about mi little english... I have the following issue:
I bought my Find 7 from Telcel (Mexico), the model of my find 7 is shown as Model Number: X9076 and Version Number: X9076MX_12.
I've tried to update (using both project spectrum zip and ColorOS V2.1.5i) using the methods that oppo described in their community posts (flash with stock recovery) with no success. It fails to update and reboot and the only message I get is "Actualizacion Fallida".
Would you please help me with a solution for this problem? Any workaround? It is because of telcel firmware?
My current ColorOS Version, it is V1.2.1i, Android 4.3
Thank you in advance.
Click to expand...
Click to collapse
Hola hermano! hace mucho vengo intentando actualizar mi telefono, es exactamente las mismas especificaciones que el tuyo, pero no entiendo eso del flashboot, podrias explicarme por favor!! gracias!!
As the title states... I am in a bootloop with this message...I am on a Google purchased XL.... what are my options at this point... the device isn't showing up in ADB either....
cirenj said:
As the title states... I am in a bootloop with this message...I am on a Google purchased XL.... what are my options at this point... the device isn't showing up in ADB either....
Click to expand...
Click to collapse
I am assuming your boot loader is unlocked.
Power it down. Then hold power and volume down to boot into recovery mode. Download the latest factory image. Then use the flashall bat file to flash it back.
Edit the flashall bat file to remove the -w so you save your data and apps and flash it.
Yes...bootloader is unlocked...I was trying to root/install TWRP....and ended up here...as long as I don't relock my bootloader...I didn't screw anything up....correct?
cirenj said:
Yes...bootloader is unlocked...I was trying to root/install TWRP....and ended up here...as long as I don't relock my bootloader...I didn't screw anything up....correct?
Click to expand...
Click to collapse
With the bootloader unlocked you can always get out of these bootloops but it a lot of times requires flashing a new factory image. I have gotten out of bootloops by going back into twrp and doing the factory reset but of course you lose all your data with that. It just depends on what sent you into the bootloop but they can all be fixed by flashing a new factory image. So far, I've never hard bricked a device but I've been in many bootloops!
PS: if you're on the May edition of the OS, then you need the verified boot signer to install twrp or root.
It went into the bootloop trying to flash TWRP...lol
cirenj said:
It went into the bootloop trying to flash TWRP...lol
Click to expand...
Click to collapse
If you're on May, download the verified boot signer, go into bootloader mode, flash the twrp.img so you get to twrp again and reflash the twrp.zip along with the verified boot signer. If you're on June, then that's not the problem but if you have mismatched slots (a/b not the same) you can get into these problems as well.
Im flashing/fixing it with the latest one (June 2017)... guess I need to figure out how to root/custom recovery better.....its no like any of my other Nexus phones...lol
cirenj said:
Im flashing/fixing it with the latest one (June 2017)... guess I need to figure out how to root/custom recovery better.....its no like any of my other Nexus phones...lol
Click to expand...
Click to collapse
This one is definitely different than my nexus 6 was, the 2 slots, etc. But after you flash it with June, you don't need the boot signer. You've seen some guides about the temp twrp.img first from adb/fastboot, then the permanent twrp.zip next flashed from within the temporary twrp, SU 2.82 is what I install next from twrp. You can find the guides. Having the June factory image on both slots can avoid a lot of problems (at least it did for me).
I can boot the phone up now... But still get the message at startup....
I assumed flashing the stock image would have given me the stock recovery, so I wouldn't get that message anymore..
cirenj said:
I assumed flashing the stock image would have given me the stock recovery, so I wouldn't get that message anymore..
Click to expand...
Click to collapse
No, that "can't be checked for corruption" stuff is because you have an unlocked bootloader. It'll always say that when the bootloader is unlocked, just ignore that!
Oh.....what happened to the days of just having a little unlock icon and that's it....lol...
I'll try flashing twrp when I get home... Hope the guide works lol
cirenj said:
I assumed flashing the stock image would have given me the stock recovery, so I wouldn't get that message anymore..
Click to expand...
Click to collapse
You're always going to get that message as long as the bootloader is unlocked. I wouldn't worry about that message. My Nexus 6P always booted up with that exact message when the bootloader was unlocked even if I was otherwise running full stock. Google thinks unlocking your bootloader is by itself a serious enough security concern that you can no longer pass safety net on full stock with the bootloader unlocked.
jhs39 said:
You're always going to get that message as long as the bootloader is unlocked. I wouldn't worry about that message. My Nexus 6P always booted up with that exact message when the bootloader was unlocked even if I was otherwise running full stock. Google thinks unlocking your bootloader is by itself a serious enough security concern that you can no longer pass safety net on full stock with the bootloader unlocked.
Click to expand...
Click to collapse
Does anyone know a trick to disable that notification?
When every boot will appear, does anyone know a trick to disable that notification? +1
blackjackEX said:
When every boot will appear, does anyone know a trick to disable that notification? +1
Click to expand...
Click to collapse
Only one way.... Lock the bootloader :laugh::silly:
chaco81 said:
Only one way.... Lock the bootloader :laugh::silly:
Click to expand...
Click to collapse
Yes, i am forget lock the bootloader, then lock the bootloader my phone cache will be clear, anywhere thank you
cirenj said:
It went into the bootloop trying to flash TWRP...lol
Click to expand...
Click to collapse
I've found that if you fastboot reboot bootloader, then fastboot boot twrp.img.
Then flash twrp installer zip in twrp and then boot into system, I should work. Then you can download Magisk zip into phone and flash it in twrp. You will have root as super su doesn't work anymore. I'm on a Pixel XL with January 8.1 update. Good luck
Hola: a mi me paso lo mismo pero quiero rootearlo , alguien tiene un tutorial para seguir con el procedimiento , porque el cartel dice que solamente esta desbloquedo y no rootedo no ?
Mod edit Google Translate :
Hi, I happen to the same thing but I want to root it, someone has a tutorial to continue with the procedure, because the sign says that it is only unlocked and not rooted, no?
toti23 said:
Hola: a mi me paso lo mismo pero quiero rootearlo , alguien tiene un tutorial para seguir con el procedimiento , porque el cartel dice que solamente esta desbloquedo y no rootedo no ?
Click to expand...
Click to collapse
inglés solo en el foro
English only on the forum.
The message is because the bootloader is unlocked, not because it is rooted. Fastboot boot or flash twrp and flash magisk if you want it rooted
Hi,
I need to flash my phone with that exact firmware version in RETEU region, but I can't find proper firmware anywhere. Can anyone help me with that?
Or maybe can I do this:
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Using RETAIL firmware region safely?
gbdlin said:
Hi,
I need to flash my phone with that exact firmware version in RETEU region, but I can't find proper firmware anywhere. Can anyone help me with that?
Or maybe can I do this:
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Using RETAIL firmware region safely?
Click to expand...
Click to collapse
my zplay is Reteu some time ago I used this version and it worked well for me https://mirrors.lolinet.com/firmware/moto/addison/official/RETAIL/ y working perfect for me
Regards
Enviado desde mi XT1635-02 mediante Tapatalk
iron maiden said:
my zplay is Reteu some time ago I used this version and it worked well for me https://mirrors.lolinet.com/firmware/moto/addison/official/RETAIL/ y working perfect for me
Regards
Enviado desde mi XT1635-02 mediante Tapatalk
Click to expand...
Click to collapse
But are you able to get OTA updates?
gbdlin said:
But are you able to get OTA updates?
Click to expand...
Click to collapse
hi yes perfectly
Enviado desde mi Redmi Note 4 mediante Tapatalk
If you have unlocked BL - just flash this
https://androidfilehost.com/?a=show&w=files&flid=215703
St.Noigel said:
If you have unlocked BL - just flash this
https://androidfilehost.com/?a=show&w=files&flid=215703
Click to expand...
Click to collapse
hello, i have a custom rom and would like to go back to stock (being able to receive OTA and all that). i have the row version (02). would your linked image bring me back to reteu?
i understand its not signed, dont worry i wont try to lock or anything
Giorgos Chatziioannou said:
hello, i have a custom rom and would like to go back to stock (being able to receive OTA and all that). i have the row version (02). would your linked image bring me back to reteu?
i understand its not signed, dont worry i wont try to lock or anything
Click to expand...
Click to collapse
It`ll flash retail (I think retUS, but I`m not sure) version. It works well )
iron maiden said:
my zplay is Reteu some time ago I used this version and it worked well for me https://mirrors.lolinet.com/firmware/moto/addison/official/RETAIL/ y working perfect for me
Regards
Enviado desde mi XT1635-02 mediante Tapatalk
Click to expand...
Click to collapse
Thank you man your suggestion helped me successfully update to the latest OTA :good:
I need help because my MI A2 lite went to bootloop.
I successfully unlocked bootloader and flash TWRP.
After that phone booted correctly but asked me for a Pin to unlock home. As I formerly set a pin to unlock I tried to enter my usual pin but phone said me it was uncorrect.
After a few trials with different pin I thought to do a factory reset doing a Wipe in recovery mode but after that phone entered in bootloop.
Now I still manage to enter in TWRP and I would like to reinstall stock rom but I'm afraid to not follow correct procedure.
Please, could someone tell me:
- if I still could recover bootloop using twrp or if it's safer to use Miflash?
- which steps I have to follow to flash stock rom in both mode (TWRP and/or Miflash) and where I can download correct image?
Thank you in advance for your answers
Zilath said:
I need help because my MI A2 lite went to bootloop.
I successfully unlocked bootloader and flash TWRP.
After that phone booted correctly but asked me for a Pin to unlock home. As I formerly set a pin to unlock I tried to enter my usual pin but phone said me it was uncorrect.
After a few trials with different pin I thought to do a factory reset doing a Wipe in recovery mode but after that phone entered in bootloop.
Now I still manage to enter in TWRP and I would like to reinstall stock rom but I'm afraid to not follow correct procedure.
Please, could someone tell me:
- if I still could recover bootloop using twrp or if it's safer to use Miflash?
- which steps I have to follow to flash stock rom in both mode (TWRP and/or Miflash) and where I can download correct image?
Thank you in advance for your answers
Click to expand...
Click to collapse
Hello,
You Can Flash Your Device With MIFlash Tool.
Stock Image Can Be Downloaded From Given Below Link
https://en.miui.com/download-354.html
Thanks,
MUHAMMAD Asif Qasim
aasiaasi said:
Hello,
You Can Flash Your Device With MIFlash Tool.
Stock Image Can Be Downloaded From Given Below Link
Thanks,
MUHAMMAD Asif Qasim
Click to expand...
Click to collapse
Hi, mine is still stuck in bootloop after MIFlash tool. Any ideas how to fix this?
Se cambio el PIN de mi xiaomi por intentar salir del bootloop
Hola bro, tambien me pasó que al cambiar la partición de arranque para intentar solucionar el problema (fastboot –set-active=a), se me cambió el PIN y ya no ingresa el que tenía antes. Intenté con 1234, 1111, 0000 pero no funciona. Alguna solución? Tengo el Xiaomi MI A2 lite y ya no tengo ganas de volver a comprar a los chinos. Me dañaron el teléfono de la nada. Gracias
I was wanting to install an android 10 gsi but I wasn't getting it so I found that I needed to be in stock rom, so I downgrade to 8.0 and then installed android 10, but I had some bugs so I decided to go back to stock pie, but In this I lost my imei and I realized that in bootloader mode it says "Baseband: Not Found" does anyone have a solution?
HenryBrian14 said:
I was wanting to install an android 10 gsi but I wasn't getting it so I found that I needed to be in stock rom, so I downgrade to 8.0 and then installed android 10, but I had some bugs so I decided to go back to stock pie, but In this I lost my imei and I realized that in bootloader mode it says "Baseband: Not Found" does anyone have a solution?
Click to expand...
Click to collapse
Try flashing NON-HLOS over the ROM "Fastboot flash modem NON-HLOS.bin".
Sometimes the NON-HLOS of certain firmwares may not work. When I switched back to 8.0 I had to flash a different modem from a Pie firmware to have the IMEI working
dotKin said:
Try flashing NON-HLOS over the ROM "Fastboot flash modem NON-HLOS.bin".
Sometimes the NON-HLOS of certain firmwares may not work. When I switched back to 8.0 I had to flash a different modem from a Pie firmware to have the IMEI working
Click to expand...
Click to collapse
muchas gracias por tu ayuda,a mi me sirvio
thank you very much for your help, it served me