-SOLVED-Hi everyone, I bricked my phone trying to downgrade from Oreo to Nougat.
I extracted the img. files from UPDATE app with Huawei extractor. and flashed via fastboot
But the same error still there.
fastboot flash kernel
fastboot flash ramdisk
fastboot flash recovery_ramdisk
The same ERROR MODE still there. plus I bought some credits on DC Phoenix and did not help at all
I download all the files but I got this error:: -FAIL Command not allowed-
I attached some pictures of the errors.
My phone is totally dead, I will really appreciate your help guys
thanks
osk4rin said:
Hi everyone, I bricked my phone trying to downgrade from Oreo to Nougat.
I extracted the img. files from UPDATE app with Huawei extractor. and flashed via fastboot
But the same error still there.
fastboot flash kernel
fastboot flash ramdisk
fastboot flash recovery_ramdisk
The same ERROR MODE still there. plus I bought some credits on DC Phoenix and did not help at all
I download all the files but I got this error:: -FAIL Command not allowed-
I attached some pictures of the errors.
My phone is totally dead, I will really appreciate your help guys
thanks
Click to expand...
Click to collapse
Fastboot flash the files from the system that you were on before you bricked it or flash twrp then use hwota8 or hurupdater to flash back to stock 8.0.
ajsmsg78 said:
Fastboot flash the files from the system that you were on before you bricked it or flash twrp then use hwota8 or hurupdater to flash back to stock 8.0.
Click to expand...
Click to collapse
I tried all the files that I mentioned and nothing happened, the error still there, TWRP is flashable but won't boot in recovery.
ajsmsg78 said:
Fastboot flash the files from the system that you were on before you bricked it or flash twrp then use hwota8 or hurupdater to flash back to stock 8.0.
Click to expand...
Click to collapse
I flashed the stock recovery_ ramdisk ramdis img. From the stock system 8.0 Oreo where the phone was.
And is stuck on - Your device is booting-
And I see no progress. After that the same Upgrade your system ERROR is back again.
osk4rin said:
I flashed the stock recovery_ ramdisk ramdis img. From the stock system 8.0 Oreo where the phone was.
And is stuck on - Your device is booting-
And I see no progress. After that the same Upgrade your system ERROR is back again.
Click to expand...
Click to collapse
Did you try the recovery from Nougat since that's what you were trying to downgrade to before you bricked it?
ajsmsg78 said:
Did you try the recovery from Nougat since that's what you were trying to downgrade to before you bricked it?
Click to expand...
Click to collapse
I did too, but won't let me flash the Recovery img. from Nougat, just the Oreo recovery
look:
osk4rin said:
Hi everyone, I bricked my phone trying to downgrade from Oreo to Nougat.
I extracted the img. files from UPDATE app with Huawei extractor. and flashed via fastboot
But the same error still there.
fastboot flash kernel
fastboot flash ramdisk
fastboot flash recovery_ramdisk
The same ERROR MODE still there. plus I bought some credits on DC Phoenix and did not help at all
I download all the files but I got this error:: -FAIL Command not allowed-
I attached some pictures of the errors.
My phone is totally dead, I will really appreciate your help guys
thanks
Click to expand...
Click to collapse
Te recomiendo que mejor flashear un rom de Openkirin para que puedas recuperar el celular, y si vas bajar a 7. 0 tendrías que haber bajada las 3 cremalleras que utiliza para hacerlo por medio de hwt8 para que lo flashes por bat. Espero te funcione
franciscojavi31 said:
Te recomiendo que mejor flashear un rom de Openkirin para que puedas recuperar el celular, y si vas bajar a 7. 0 tendrías que haber bajada las 3 cremalleras que utiliza para hacerlo por medio de hwt8 para que lo flashes por bat. Espero te funcione
Click to expand...
Click to collapse
Hola ,gracias por tu respuesta.
Que ROM the Open Kirin?Treble Project?de Oreo?
Gracias!
edited:Ya trate y no ahi algun Progreso.
use erecovery back to that firmware
---------- Post added at 09:42 AM ---------- Previous post was at 09:37 AM ----------
Vol up plus power.approve firmware for imei but using dns as suggested hicloud.doing from another phone or pc. older version firmware before pie supported.
luck2ang said:
use erecovery back to that firmware
---------- Post added at 09:42 AM ---------- Previous post was at 09:37 AM ----------
Vol up plus power.approve firmware for imei but using dns as suggested hicloud.doing from another phone or pc. older version firmware before pie supported.
Click to expand...
Click to collapse
I tried to flashed the recovery from that firmware, but.. Won't flash any Nougat img. Just Oreo
fastboot flash recovery_ramdisk recovery ramdis img.
Won't flash - fastboot flash recovery img.
By the time whe recovery_ramdisk is flashed I did power & volume up to boot into recovery, and it just goes to the message - Your device is booting -
It stays on a bootloop.
osk4rin said:
I tried to flashed the recovery from that firmware, but.. Won't flash any Nougat img. Just Oreo
fastboot flash recovery_ramdisk recovery ramdis img.
Won't flash - fastboot flash recovery img.
By the time whe recovery_ramdisk is flashed I did power & volume up to boot into recovery, and it just goes to the message - Your device is booting -
It stays on a bootloop.
Click to expand...
Click to collapse
Try doing it in command prompt instead of PowerShell.
ajsmsg78 said:
Try doing it in command prompt instead of PowerShell.
Click to expand...
Click to collapse
I tried but can't flash the Nougat recovery img.
osk4rin said:
I tried but can't flash the Nougat recovery img.
Click to expand...
Click to collapse
You have an Oreo partition table at the moment.
You aren't going to be able to flash the Nougat recovery - the N recovery image is a traditional Android boot image (kernel + ramdisk), the O recovery image is just the ramdisk; the O recovery_ramdisk partition is half the size of the N recovery partition.
irony_delerium said:
You have an Oreo partition table at the moment.
You aren't going to be able to flash the Nougat recovery - the N recovery image is a traditional Android boot image (kernel + ramdisk), the O recovery image is just the ramdisk; the O recovery_ramdisk partition is half the size of the N recovery partition.
Click to expand...
Click to collapse
I know, Oreo partition is on it.but the Build system is MHA-L29C432B126 that is why I could not flash any Recovery img from Nougat. and my Original Model is MHA-L29C567 (Oreo)
That means that my phone is dead.
osk4rin said:
I know, Oreo partition is on it.but the Build system is MHA-L29C432B126 that is why I could not flash any Recovery img from Nougat. and my Original Model is MHA-L29C567 (Oreo)
That means that my phone is dead.
Click to expand...
Click to collapse
I haven't yet gone looking too closely into this, but check the P10 guides board - there's a set of instructions there along with some scripts which you can probably use or tweak to revive your device back with Oreo at least. If you were on a recent O security patch you won't be able to roll back to Nougat anyway. (Xloader & fastboot updates in newer security patches cause downgrades to brick.)
Also, the underlying tools (hikey_idt) does work provided you've got suitable sec_usb_xoader/lpm3/fastboot images, which look to be included there.
irony_delerium said:
I haven't yet gone looking too closely into this, but check the P10 guides board - there's a set of instructions there along with some scripts which you can probably use or tweak to revive your device back with Oreo at least. If you were on a recent O security patch you won't be able to roll back to Nougat anyway. (Xloader & fastboot updates in newer security patches cause downgrades to brick.)
Also, the underlying tools (hikey_idt) does work provided you've got suitable sec_usb_xoader/lpm3/fastboot images, which look to be included there.
Click to expand...
Click to collapse
The bootloader is Unlocked as you see on the pic, but Well, I'll keep searching for a solution or just give up with this.
Thanks.
osk4rin said:
The bootloader is Unlocked as you see on the pic, but Well, I'll keep searching for a solution or just give up with this.
Thanks.
Click to expand...
Click to collapse
Bootloader unlock is different than full fastboot unlock. A full fastboot unlock allows for the flashing of any partition (including the partition table itself) via fastboot, a normal bootloader unlock only allows you to flash a selected handful of partitions.
Unfortunately, I only know of 3 ways to get that unlock:
* The backdoor used by DC Unlocker and the like
* NVME patching
* USB xloader from a board firmware package, loaded via testpoints.
If you were ever on a newer security patch, the backdoor doesn't work any longer as the key used for generating the backdoor token was changed; and since you don't have a working system or recovery, you can't do the NVME patch.
irony_delerium said:
Bootloader unlock is different than full fastboot unlock. A full fastboot unlock allows for the flashing of any partition (including the partition table itself) via fastboot, a normal bootloader unlock only allows you to flash a selected handful of partitions.
Unfortunately, I only know of 3 ways to get that unlock:
* The backdoor used by DC Unlocker and the like
* NVME patching
* USB xloader from a board firmware package, loaded via testpoints.
If you were ever on a newer security patch, the backdoor doesn't work any longer as the key used for generating the backdoor token was changed; and since you don't have a working system or recovery, you can't do the NVME patch.
Click to expand...
Click to collapse
Yes, I cant able to flash the recovery from the Nougat system. Just Oreo.
Pretty much can't do anything.
osk4rin said:
Yes, I cant able to flash the recovery from the Nougat system. Just Oreo.
Pretty much can't do anything.
Click to expand...
Click to collapse
No, you can't flash a Nougat recovery on an Oreo partition table. Absolutely won't work.
You HAVE to flash an Oreo recovery, and you probably need to make sure you've got a suitable kernel image as well in the 'kernel' partition. (As has been said before - recent security patch CANNOT roll back to Nougat. You will brick. There is no workaround, it will fail, as you have discovered. Usually the brick is worse - you don't even get fastboot. You just get the serial port in download mode waiting for a sec signed xloader & such to come down.)
This was coming to mind when you posted that:
From an Oreo package, you might try flashing the following:
kernel
recovery_ramdisk
recovery_vendor
recovery_vbmeta
Then try booting recovery. I don't remember whether fastboot will allow you to flash the other two, but at the very least I know you need a working kernel and recovery image - if flashing those will get you booting to recovery, you can probably load up an Oreo TWRP from there and possibly use hurupdater or hwota8 to flash the full system back.
irony_delerium said:
No, you can't flash a Nougat recovery on an Oreo partition table. Absolutely won't work.
You HAVE to flash an Oreo recovery, and you probably need to make sure you've got a suitable kernel image as well in the 'kernel' partition. (As has been said before - recent security patch CANNOT roll back to Nougat. You will brick. There is no workaround, it will fail, as you have discovered. Usually the brick is worse - you don't even get fastboot. You just get the serial port in download mode waiting for a sec signed xloader & such to come down.)
This was coming to mind when you posted that:
From an Oreo package, you might try flashing the following:
kernel
recovery_ramdisk
recovery_vendor
recovery_vbmeta
Then try booting recovery. I don't remember whether fastboot will allow you to flash the other two, but at the very least I know you need a working kernel and recovery image - if flashing those will get you booting to recovery, you can probably load up an Oreo TWRP from there and possibly use hurupdater or hwota8 to flash the full system back.
Click to expand...
Click to collapse
I flashed those commands and nothing happened.
Power +Volume Up trying to boot into Recovery.
My device is Just:
Your Device is booting now....
-Bootloop-
Also Same error, Please update your system
Error!
Func NO: 11 (recovery image)
Func NO: 2 (load failed!)
Related
Hi !
I had follow this thread https://forum.xda-developers.com/nokia-3/how-to/guide-how-to-flash-twrp-magisk-t3785768
and I had install TWRP but now when i try to start my phone,I can access to TWRP and fastboot but I can't access to the system.
My Nokia 3 freeze on "Powered by Android - Orange state -Your device has been unlocked and can't be trusted - Your device will boot in 5 seconds"
------
Nokia 3 - 1032 / Dowgraded to 7.0
Somebody help me plz ! :fingers-crossed:
>Taps< said:
Hi !
I had follow this thread https://forum.xda-developers.com/nokia-3/how-to/guide-how-to-flash-twrp-magisk-t3785768
and I had install TWRP but now when i try to start my phone,I can access to TWRP and fastboot but I can't access to the system.
My Nokia 3 freeze on "Powered by Android - Orange state -Your device has been unlocked and can't be trusted - Your device will boot in 5 seconds"
------
Nokia 3 - 1032 / Dowgraded to 7.0
Somebody help me plz ! :fingers-crossed:
Click to expand...
Click to collapse
Did you unlocked your bootloader and after that did you flash TWRP without reboot?
Maybe I'm wrong but when you unlock your bootloader, the phone automatically reboots into stock recovery and and immediately wipe everything (included your internal storage) and then reboots normally. If you flashed TWRP after unlocking your bootloader, your phone will boot into TWRP but it won't wipe anything.
I think that happened.
Isrks said:
Did you unlocked your bootloader and after that did you flash TWRP without reboot?
Maybe I'm wrong but when you unlock your bootloader, the phone automatically reboots into stock recovery and and immediately wipe everything (included your internal storage) and then reboots normally. If you flashed TWRP after unlocking your bootloader, your phone will boot into TWRP but it won't wipe anything.
I think that happened.
Click to expand...
Click to collapse
Mmh after I unlocked the bootloader, my phone was freeze on this
Select Boot Mode :
[VOLUME_UP to select. VOLUME DOWN is OK]
[Recovery Mode]
[Fastboot Mode] <<==
[Normal Mode]
=> FASTBOOT mode.....
So, I forced it to reboot, after everything seems ok.
What part must I reflash ?
>Taps< said:
Mmh after I unlocked the bootloader, my phone was freeze on this
Select Boot Mode :
[VOLUME_UP to select. VOLUME DOWN is OK]
[Recovery Mode]
[Fastboot Mode] <<==
[Normal Mode]
=> FASTBOOT mode.....
So, I forced it to reboot, after everything seems ok.
What part must I reflash ?
Click to expand...
Click to collapse
When I unlocked the bootloader my phone freezed too, so I typed in Windows cmd "fastboot reboot". After that, my phone was formatted by stock recovery.
You should reflash stock recovery if you have TWRP, so the stock recovery can format your internal storage, if not, your phone won't boot.
:fingers-crossed:
Isrks said:
When I unlocked the bootloader my phone freezed too, so I typed in Windows cmd "fastboot reboot". After that, my phone was formatted by stock recovery.
You should reflash stock recovery if you have TWRP, so the stock recovery can format your internal storage, if not, your phone won't boot.
:fingers-crossed:
Click to expand...
Click to collapse
Ok, so fastboot didn't work at all (just waiting devices)
I tried to reflash TWRP nothing happens, I tried to do a factory wipe with twrp but nothing happens too.
I searched a stock recovery for nokia 3 1032- Android 7.0 but found nothing - must i use stock recovery for Android 7.1.1 or do you have a link to a stock recovery for 7.0 ?
------------
I found this on XDA : Is it a good way if nothing work ?
Hi, I was able to unbricked my phone using this:
"https://mega.nz/#F!0lMBiIIYgB!c9TeOWFrKpf0XfOwXzunrg"
Here is the SP Flash tool, the download agent for Nokia's phones and the ROM unpacked
As SkaboXD said (i don't know if it were in this post or in other one) you must:
1- Download the files I provided you
2- Install SP Flash Tool
3- Choose the download agent
4- Choose the scatter
5- Press download and plug your phone (it must be OFF)
6- Wait and enjoy.
I must thank to everyone who give us this files. I couldn't unbricked my phone without your help
Click to expand...
Click to collapse
>Taps< said:
Ok, so fastboot didn't work at all (just waiting devices)
I tried to reflash TWRP nothing happens, I tried to do a factory wipe with twrp but nothing happens too.
I searched a stock recovery for nokia 3 1032- Android 7.0 but found nothing - must i use stock recovery for Android 7.1.1 or do you have a link to a stock recovery for 7.0 ?
------------
I found this on XDA : Is it a good way if nothing work ?
Click to expand...
Click to collapse
I think that this is the link:
https://forum.xda-developers.com/nokia-3/help/nokia-3-preloader-bricked-t3719357/post76069467#post76069467
I used SP flash tools to downgrade and install TWRP in my phone.
Which tool did you use to downgrade your phone?
Isrks said:
I think that this is the link:
https://forum.xda-developers.com/nokia-3/help/nokia-3-preloader-bricked-t3719357/post76069467#post76069467
I used SP flash tools to downgrade and install TWRP in my phone.
Which tool did you use to downgrade your phone?
Click to expand...
Click to collapse
Ok thanks :fingers-crossed:, I will try it
To downgrade I used OST LA and to flash TWRP I used SP flash tools
>Taps< said:
Ok thanks :fingers-crossed:, I will try it
To downgrade I used OST LA and to flash TWRP I used SP flash tools
Click to expand...
Click to collapse
Good luck. :fingers-crossed:
You can flash again with OST LA. Or try to flash with SP flash tool the whole rom or just the recovery. To flash with SP flash tools you need a nb0 unpacker tool (my previous post have a link to another post with the tool link).
BTW feel free to ask something that you don't understand. :highfive:
Isrks said:
Good luck. :fingers-crossed:
You can flash again with OST LA. Or try to flash with SP flash tool the whole rom or just the recovery. To flash with SP flash tools you need a nb0 unpacker tool (my previous post have a link to another post with the tool link).
BTW feel free to ask something that you don't understand. :highfive:
Click to expand...
Click to collapse
Heyyyyy !!! Thank you !!!
It works again :victory: !!!
I used OST LA to reflash it !!! Thanks again <3
I think I will use the second alternative step to not get a brick bootloader ^^' https://forum.xda-developers.com/nokia-3/how-to/guide-how-to-flash-twrp-magisk-t3785768
----------
Do you know the safest way to relock the bootloader ?
>Taps< said:
I think I will use the second alternative step to not get a brick bootloader ^^' https://forum.xda-developers.com/nokia-3/how-to/guide-how-to-flash-twrp-magisk-t3785768
----------
Do you know the safest way to relock the bootloader ?
Click to expand...
Click to collapse
Is like unlock bootloader, just change "fastboot oem unlock" to "fastboot oem lock".
But your internal storage will be formatted again by stock recovery, so you must have stock recovery installed.
After relock, your device will get ota updates, so you need stock recovery to install them.
I recommend root your device after all the updates, even you can install TWRP without problems.
I installed TWRP, root and installed stock recovery to get updates. Choose the method that you like.
Good luck. :highfive:
Hi, i really need help, I don't know what to do ...
I tried to flash ma phone with lineageos 16.
But i had some problems with play store, so i tried re-flash lineageos with TWRP.
I must have done something wrong with full wipe but now, my phone can't launch anymore...
It don't launch system or recovery ...
I can turn into fastboot mode but that's all. I tried flash recovery ramdisk with erecovery stock (emui9) but it doesn't launch...
The first picture shows what's one screen when i boot into normal mode and the second one shows what's on screen when i boot into recovery mod.
But after these pictures, nothing happen.... really nothing.... The screen stay like this for long time. The phone comes very hot .... I had to let the battery down to reboot into fastboot mode.
Please anyone can help me ????
Can you boot into eRecovery with Volume up?First Pic Number 2
letschky said:
Can you boot into eRecovery with Volume up?First Pic Number 2
Click to expand...
Click to collapse
No...
When I do, it's just the same... Screen block like first picture...
Envoyé de mon F5121 en utilisant Tapatalk
Rob1hn said:
No...
When I do, it's just the same... Screen block like first picture...
Envoyé de mon F5121 en utilisant Tapatalk
Click to expand...
Click to collapse
Test a another way,
Power off the Phone.
Press and Hold Volume up and put the USB Cable from your Pc in the Phone and keep volume up until it's booted into the eRecovery
---------- Post added at 06:04 PM ---------- Previous post was at 05:53 PM ----------
that does not work,boot into Fastboot Mode and Flash System,Cust,Boot and Recovery img from Stockrom via Fastboot.
You should know what version you had before, before you flashed Lineage OS.
Download Emui Stockrom and extract the UPDATE.APP with Huawei Extractor and copy System,Cust,Boot and Recovery img in your ADB/Fastboot Folder
You can the Firmware found in Huawei Firmware Finder from Playstore.
Flash all the img files via Fastboot
Huawei Extractor
Did not make Twrp Backup before you flashed Lineageos that could help too.
From pictures attached
which img files i have to flash and which command line i have to use?
Thanks a lot
Rob1hn said:
From pictures attached
which img files i have to flash and which command line i have to use?
Thanks a lot
Click to expand...
Click to collapse
Did you try booting to erecovery? Thats the best way to restore, i messed up my v10 the same way and restored via erecovery.
If not, you may try dload method to restore stock.
Or you may try flashing the system, cust and other img as mentioned in above comment.
Erecovery and dload is still your best bet.
I can't turn into erecovery....
The screen stay on the pictures I uploaded
Which img files exactly I have to flash and which command line I have to use?
Thanks
Envoyé de mon F5121 en utilisant Tapatalk
Rob1hn said:
I can't turn into erecovery....
The screen stay on the pictures I uploaded
Which img files exactly I have to flash and which command line I have to use?
Thanks
Envoyé de mon F5121 en utilisant Tapatalk
Click to expand...
Click to collapse
Check one of the guide in my signature to return to stock with such issues.
Here
https://forum.xda-developers.com/ho...return-to-stock-flashing-custom-roms-t3809905
shashank1320 said:
Check one of the guide in my signature to return to stock with such issues.
Here
https://forum.xda-developers.com/ho...return-to-stock-flashing-custom-roms-t3809905
Click to expand...
Click to collapse
I have the same issue and already tried that. Your guide seems to be for EMUI 8.x and with 9.x some files and partition names have changed so i get errors. Tried adapting it and even managed to flash the system but it does not boot or enter erecovery.
I can even flash twrp on the phone but it gets then stuck on the splashscreen of twrp and doesn*t load further. fastboot boot is not working either and i can't relock the bootloader. I am pretty much out of options.
180190 said:
I have the same issue and already tried that. Your guide seems to be for EMUI 8.x and with 9.x some files and partition names have changed so i get errors. Tried adapting it and even managed to flash the system but it does not boot or enter erecovery.
I can even flash twrp on the phone but it gets then stuck on the splashscreen of twrp and doesn*t load further. fastboot boot is not working either and i can't relock the bootloader. I am pretty much out of options.
Click to expand...
Click to collapse
I think the partition names have changed because I am in the same situation.
This is my story:
https://forum.xda-developers.com/honor-view-10/help/9-0-0-official-pie-update-failed-boot-t3889378
elfabio said:
I think the partition names have changed because I am in the same situation.
This is my story:
https://forum.xda-developers.com/honor-view-10/help/9-0-0-official-pie-update-failed-boot-t3889378
Click to expand...
Click to collapse
I have figured it out. You have to flash ramdisk_recovery and kernel. Then you should get into erecovery with pluged usb in and holding power up and power off/on button. Worked for me.
Tripar said:
I have figured it out. You have to flash ramdisk_recovery and kernel. Then you should get into erecovery with pluged usb in and holding power up and power off/on button. Worked for me.
Click to expand...
Click to collapse
Let's just assume i am a total idiot. Which file exactly did you flash to what partition?
180190 said:
Let's just assume i am a total idiot. Which file exactly did you flash to what partition?
Click to expand...
Click to collapse
I have downloaded BKL-L09C432E4R1P9B159 (9.0.0.159) file from this site. Then I downloaded HuaweiExtractor and extracted the update.app file that is located in rom zip. After that i extracted the kernel and recovery_ramdisk files and in fastboot mode write:
fastboot flash kernel KERLEL.IMG
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.IMG (or something like that).
I am not sure if flashing system is needed here, but I did it too.
Hope this helps.
EDIT: Those files are for C435.
Sadly this didn't help me. Still stuck at "Your device is booting now..."
And did you tried to plug in usb and hold volume up and power off? It should boot into erecovery now.
Tried that, no erecovery. I have no idea what i could have done to damage it this badly.
Tripar said:
I have figured it out. You have to flash ramdisk_recovery and kernel. Then you should get into erecovery with pluged usb in and holding power up and power off/on button. Worked for me.
Click to expand...
Click to collapse
I think i have already tried this.
1/ Can you say me which fastboot command did you use for flashing kernel and the recovery_ramdisk ?
2/ Can you say me which files (source link or whatever) did you use ?
elfabio said:
I think i have already tried this.
1/ Can you say me which fastboot command did you use for flashing kernel and the recovery_ramdisk ?
2/ Can you say me which files (source link or whatever) did you use ?
Click to expand...
Click to collapse
I wrote it in the previous post.
180190 said:
Sadly this didn't help me. Still stuck at "Your device is booting now..."
Click to expand...
Click to collapse
Bro, check my QnA. I explained how it got resolved for me. Or I just got lucky. Unsure! This is quite recoverable.
ankan1993 said:
Bro, check my QnA. I explained how it got resolved for me. Or I just got lucky. Unsure! This is quite recoverable.
Click to expand...
Click to collapse
Where can I find that? Nothing i have tried has worked so far.
Links to Firmware & OTA & TWRP & Magisk & Bootloader - Z3 PLAY BECKHAM (All Variants)
Firmwares
the latest firmware as of time of writing is February's 2020 OTA (BECKHAM_RETAIL_9.0_PPWS29.131-27-1-18_subsidy-DEFAULT_regulatory-DEFAULT_CFC) = https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
previous OTAs RETAIL variant can be found here = https://mirrors.lolinet.com/firmware/moto/beckham/official/RETAIL/
future OTAs possibly here = https://androidfilehost.com/?w=search&s=beckham
other variants = https://mirrors.lolinet.com/firmware/moto/beckham/official/
Unlock Bootloader
first you need to install Motorola Drivers = https://support.motorola.com/us/en/solution/MS88481
- ATTENTION - use the most up-to-date ADB Drivers otherwise will brick if older version is used; instead of downloading ADB elsewhere which is often old version, get it directly from GOOGLE, here = https://dl.google.com/android/repository/platform-tools-latest-windows.zip
now you can proceed to unlock bootloader = https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
TWRP
get the official TWRP here = https://dl.twrp.me/beckham/
- ATTENTION - if you just want root access, then there's no need to install TWRP, just boot from the .img once using the latest version
use TWRP to make a backup of EFS partition before installing anything, store the backup files outside of the device
if you want custom ROMs or GSI, then you will need to install TWRP installer .zip into the recovery partition. To install the .zip, boot using a .img for example the 3.3.1-0, then use it to install the latest .zip version in the recovery partition. Unfortunately the only official installable version of TWRP that exists is bugged, and the TWRP developers haven't fixed it yet, go talk to them ask for some love, be respectful = https://github.com/TeamWin/android_device_motorola_beckham/issues
Magisk
install Magisk using the new&correct method AKA "Boot Image Patching Method" to be able to install OTA later = https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
when OTA arrives, you may manually install it whilst retaining Magisk by carefully following these instructions = https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
- ATTENTION - you won't be able to install stock OTAs if you use older method or if system partition is modified, be really careful to not alter the hash of the partitions
Another mirror for the latest ROM with May 1st patches, uploaded by me you can find here:
https://forum.xda-developers.com/showpost.php?p=79122632&postcount=45
@heynando, what is the difference between "retail" and "retus"? Also, does anyone know the numbering system? All the uploads on lolinet.com for Pie have 131 as the first three numbers, but the few posted about here have 183. Maybe 183 is an ota number?
ritchea said:
@heynando, what is the difference between "retail" and "retus"?
Click to expand...
Click to collapse
RETUS is short for Retail + US.
The difference between RETUS and RETAIL is, I imagine, cannot confirm, the same RETAIL firmware with some US regional modifications such as bloatware or CSC thing
you can check which model is yours in SETTINGS > SYSTEM > ABOUT PHONE > SOFTWARE CHANNEL. Or in the bootloader by running the command
Code:
fastboot getvar product
you can find the entire list of product codes here = https://mirrors.lolinet.com/firmware/moto/readme-en.html#listone
XT1929-4(Canada, SS, 4+32GB) XT1929-3(NA/Sprint, SS, 4+32GB)
XT1929-4(NA/AMZ/BWACA/RETCA/RETUS/USC, SS, 4+64GB)
XT1929-5(BRAZIL/RETBR/TIMBR/TEFBR, DS, 4+64GB / 6+128GB)
XT1929-6(LATAM/AMXLA/NIIPE/ATTMX//TEFCL/TEFPE/RETLA/RETAR/RETMX/RETCL/AMXMX, DS, 4+64GB)
XT1929-6(LATAM/RETLA/TEFCO/TIGCO, DS, 6+128GB)
XT1929-8(EMEA_APAC/RETEU/DTEU, DS, 4+32GB / 4+64GB)
ritchea said:
Also, does anyone know the numbering system? All the uploads on lolinet.com for Pie have 131 as the first three numbers, but the few posted about here have 183. Maybe 183 is an ota number?
Click to expand...
Click to collapse
I believe that's the internal version of the software. If the number changes that emphasizes there has been software changes and/or tweaks in the system and/or firmware. If the number doesn't change, then it's just a regular security patch with no further modifications in system and/or firmware.
Thanks for that info. Yeah, I know mine has the retus software channel. I just couldn't find or figure out if Retail was actually one word or if it was a combo of ret+ail. That version has a LOT of software posted.
I flashed retail on an EU model. And after it the software channel say Reteu just like the original. Also the model number is as it should be. In my opinion you can flash retail firmware on us and EU models.
confirmed that this firmware is working on XT1929-4
these are the steps I took:
downloads and setup
install moto drivers (in windows, not needed for linux)
install android tools (adb and fastboot)
downloaded official TWRP
downlaoded and extracted the firmware
backup of partitions (including efs)
Code:
adb reboot bootloader
fastboot boot twrp_recovery.img
backed up lots of partitions
rebooted system
copied the TWRP backup files to my pc for safe keeping
set the fastboot slot (i did this because many of teh fastboot commands below were failing)
Code:
adb reboot bootloader
fastboot --set-active=a
rebooted back into bootloader
installed the firmware
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system_b system_other.img
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase ddr
fastboot reboot
installed magisk the new good way
did the initial device setup
installed magisk manager
copied the boot.img from the extracted firmware above to the phone.
followed these steps for boot img patching and install of magisk https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
sirkuttin,
Thanks for the detail how to. That worked perfectly for me, and my moto z3 play, same model as yours. I could not get the ota or even lenovo smart assistant to work on my phone. It basically had it locked up, stuck on the boot logo. I'm assuming its the old way of install magisk that caused that. This got me on the latest firmware release, and then installed magisk the new way. Lenovo smart assistant was useful in downloading the firmware.
Thanks.
Hi I tried the new magisk install way. I'm on XT1929-4_BECKHAM_RETUS_9.0_PPW29.183-29-1, copy boot.img and patched it to magisk_patched.img. Then after fastboot flash boot /path/to/magisk_patched.img and a reboot, i'm not stuck on the motorola powered by android screen. Verity mode is set to disabled.
I tried holding down the power button to simulate a battery pull but no luck, the screen just stays on. Can anybody give me any advise? I think now I have to just wait till the device is out of juice. Never experience this before.
---------- Post added at 02:16 PM ---------- Previous post was at 01:31 PM ----------
So the battery pull is "Power + Vol Down". I was able to flash the PPW29.183-29-1 firmware and get it going again. I noticed it tried to upgrade me to PPW29.183-29-1-2 so I must have been on newer firmware. I flashed the magisk_patched and am rooted now.
It seems there is TWRP 3.3.1-1 with an Installer. Does it mean it can be flashed to recovery partition? Tried booting it, but got stuck on TWRP logo (3.3.1-0 boots fine).
ch3mn3y said:
It seems there is TWRP 3.3.1-1 with an Installer. Does it mean it can be flashed to recovery partition? Tried booting it, but got stuck on TWRP logo (3.3.1-0 boots fine).
Click to expand...
Click to collapse
I haven't tested it myself, though you're correct, the installer .zip can be installed on recovery partition. To install the .zip, boot using a .img for example the 3.3.1-0, then use it to install the .zip in the recovery partition.
PS only do it if you have a reason to, I'm not sure if the firmware OTA checks the hashing of the recovery partition so altering it could potentially prevent you from installing OTAs of the official ROM.
heynando said:
I haven't tested it myself, though you're correct, the installer .zip can be installed on recovery partition. To install the .zip, boot using a .img for example the 3.3.1-0, then use it to install the .zip in the recovery partition.
PS only do it if you have a reason to, I'm not sure if the firmware OTA checks the hashing of the recovery partition so altering it could potentially prevent you from installing OTAs of the official ROM.
Click to expand...
Click to collapse
It, unfortunately, does... However I csnnot update (continous update unsuccesful) :f Have to check if Xposed module is not a reason.
And You probably could use Installer to flash stock recovery? If not TWTP itself however I've never checked if one for Play has access to recovery partiotion to flash images. It should gave if it can be done using the installer...
Sent from my Moto Z3 Play using Tapatalk
ch3mn3y said:
However I csnnot update (continous update unsuccesful)
Click to expand...
Click to collapse
Me too and it drove me nuts, I did patch the /boot partition with the original file, but the OTA app still failed to install, even after reboot. And there's no useful data in the logcat to debug the app. So I gave up and had to use Titanium to freeze the OTA app otherwise it would keep trying to download and install infinitely.
ch3mn3y said:
:f Have to check if Xposed module is not a reason.
Click to expand...
Click to collapse
It's probably not because I don't use it and the OTA method didn't work me either
ch3mn3y said:
And You probably could use Installer to flash stock recovery?
Click to expand...
Click to collapse
Yes you're right, I agree there..
heynando said:
Yes you're right, I agree there..
Click to expand...
Click to collapse
Just checked the inside of the installer zip file and it won't work. Still once every 3 months it wouldn't be a problem to connect device to PC and flash recovery.img with fastboot.
Is there a list with a commands and order how to flash Z3 Play images of official firmware? I want July patches and have some problems, so clean reflash is what I need.
Additional question is if I have to use "-u" when flashing second and other system images? Remember I had to do it with my X Play coz of unlocked bootloader and here I have one in the same state as well. If yes than could someone tell me where to put it, coz I'm not sure...
tb110188 said:
Another mirror for the latest ROM with May 1st patches, uploaded by me you can find here:
https://forum.xda-developers.com/showpost.php?p=79122632&postcount=45
Click to expand...
Click to collapse
Hi. How are you doing. My software channel says: US Retail. and my build number is 183-19-1-2. What would be the firmware?
tb110188 said:
Another mirror for the latest ROM with May 1st patches, uploaded by me you can find here:
https://forum.xda-developers.com/showpost.php?p=79122632&postcount=45
Click to expand...
Click to collapse
Hi. How are you doing. My software channel says: US Retail. and my build number is 183-19-1-2. What would be the firmware?
Ramble2k said:
Hi. How are you doing. My software channel says: US Retail. and my build number is 183-19-1-2. What would be the firmware?
Click to expand...
Click to collapse
This one, make sure to get the latest. https://mirrors.lolinet.com/firmware/moto/beckham/official/RETUS/
Hi, I'm trying to unlock my Moto Z3 Play bootloader, but I don't get the code on CMD, but only a few numbers ... The version of my device is PPW29.131-27-1-11, channel RETBR software.
Someone went through this, can you tell how to reverse this situation?
I couldn't get the bootloader unlocked for xt1929-4. I tried different computers, Linux and win. Have latest adb and fastboot. When fastboot OEM get_unlock_data is given, I says counttas slot not found etc., can someone help?
It may seem obvious, but you
checked OEM unlocking and USB Debugging?
Hi guys:
Once again it's me... I have tried with no success to "covert" my Axon 10 Pro from Mexico (Guess US model, 855A03 no NA 855A03_NA) to EU, I have downloaded several zip files from XDA and other sites. I have tried with QFIL, MiFlash and the EDL tool as well.
But none of them work, do you know if this is possible or a guide to do it?
MiFlash: Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
QFIL: Error (can't remember right now)
EDL: Error (can't remember right now)
Or maybe a way to recover fastboot to try the Lineage ROM, since I don't have it... I tried with adb reboot bootloader (no go, the phone restarts and goes directly to the carrier logo, no fastboot) I have tried with the vol - and power keys (no go, the same).
Ooooooorrr.... Maybe a way to install TWRP from EDL since I haven't fastboot, I've tried with emmcdl:
emmcdl -p COM4 -f prog_ufs_firehose_sdm855.elf -b recovery twrp.img
It appears to flash it, but after that it reboots and the old recovery is there.
Kind regards!
So... I've finally installed TWRP using a ROM from other forum, but in the end it didn't end as expected, I could install recovery, then I tried to install lineage but... Bootloop.
I´ll try again later.
JUst to let you know, is possible to install TWRP. I'll post my tutorial later. Regards
zparallax said:
Hi guys:
Once again it's me... I have tried with no success to "covert" my Axon 10 Pro from Mexico (Guess US model, 855A03 no NA 855A03_NA) to EU, I have downloaded several zip files from XDA and other sites. I have tried with QFIL, MiFlash and the EDL tool as well.
But none of them work, do you know if this is possible or a guide to do it?
MiFlash: Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
QFIL: Error (can't remember right now)
EDL: Error (can't remember right now)
Or maybe a way to recover fastboot to try the Lineage ROM, since I don't have it... I tried with adb reboot bootloader (no go, the phone restarts and goes directly to the carrier logo, no fastboot) I have tried with the vol - and power keys (no go, the same).
Ooooooorrr.... Maybe a way to install TWRP from EDL since I haven't fastboot, I've tried with emmcdl:
emmcdl -p COM4 -f prog_ufs_firehose_sdm855.elf -b recovery twrp.img
It appears to flash it, but after that it reboots and the old recovery is there.
Kind regards!
Click to expand...
Click to collapse
I have the same version (telcel) es una lástima que Telcel ni ZTE le den seguimiento para actualizar, si pudiste cambiarlo a la versión de EU o internacional, agradecer
Hi, I am looking for the boot.img for LineageOS 18 20211002-nio-156
I had damaged boot on my device, and it goes to fastboot mode every time. I have tried looking for the boot.img on LineageOS website, but there is only LineageOS 20 images.
If anyone have the image, version of LineageOS 18 20211002-nio-156, would you kindly share with me? Thanks a lot!
Just look for a tool to unzip the ROM and get the boot.img
Deivid Soltoski said:
Just look for a tool to unzip the ROM and get the boot.img
Click to expand...
Click to collapse
Thanks for your reply, unfortunately I do not have the ROM.
Oh :l
Deivid Soltoski said:
Oh :l
Click to expand...
Click to collapse
I got the img of 20211002-nio. But after I used
fastboot flash boot_a boot.img
to falsh boot_a and boot_b, the Edge S still goes to fastboot mode with the litte green robot on screen. Did I did it wrong, or is the version of my Edge S is different? Is there anyway to tell which version of my device is using from the fastboot screen?
I found this on screen
BL: MBM-3.0-NIO_RETCN-840E9BB764-211103
Should I use image of MBM-3.0-NIO_RETCN-840E9BB764-211103?
There are couple of game save files I have not backup. Is that possible to use fasboot mode or recovery mode to get those files out? Then I can flash the device.
fuluel said:
I got the img of 20211002-nio. But after I used
fastboot flash boot_a boot.img
to falsh boot_a and boot_b, the Edge S still goes to fastboot mode with the litte green robot on screen. Did I did it wrong, or is the version of my Edge S is different? Is there anyway to tell which version of my device is using from the fastboot screen?
I found this on screen
BL: MBM-3.0-NIO_RETCN-840E9BB764-211103
Should I use image of MBM-3.0-NIO_RETCN-840E9BB764-211103?
Click to expand...
Click to collapse
RETCN it's chinese ROM, you will have to reinstall the ROM or install stock Android 11 because it conflicts with Android 12 bases
Deivid Soltoski said:
RETCN it's chinese ROM, you will have to reinstall the ROM or install stock Android 11 because it conflicts with Android 12 bases
Click to expand...
Click to collapse
I saw TWRP (Team Win Recovery Project) has a button called Mount. Is that possible to get some files out the phone? But I have not Edgs S or G100 in there list. The closest one is Edge (racer). Is that OK to use this image?
fuluel said:
I saw TWRP (Team Win Recovery Project) has a button called Mount. Is that possible to get some files out the phone? But I have not Edgs S or G100 in there list. The closest one is Edge (racer). Is that OK to use this image?
Click to expand...
Click to collapse
Mount just mounts the cell phone partitions to access and modify them, and the G100 only works with TWRP on Android 11 only, and don't even try to install another type of ROM/recovery from another device because you can have your device blocked and then just throw it in the trash XD
When I am tring to flash Lineage-images-18-20211002-nio-156, I always got signature verification failed message. When I click YES, the process just stopped.
I had followed this guide https://wiki.lineageos.org/devices/nio/install/variant1 Is there anything I did wrong? Or is that possible to disable signature vericication in LOS revocery?