Hello fellas
Finally i catch OREO from Z2 Play and posting for all , it was a hard work of 3 days to scripting and get a valid serial number
I am not responsible for any brick in the device and only do the procedures if you are sure of what you are doing .
This will not avoid your warranty (if you have locked bootloader) and you will still be available to get automatic OTA from your device.
Warning:
* You need to have february patch from Nougat and buildnumber (NPSS26.118-19-1-6) to install OTA.
* If you have a different buildnumber or your device is branded to any carrier, you need to install a fresh nougat compatible with this OTA.
* Dont try ota update with custom rom, root, magisk or whatever. Install fresh nougat first.
* I recommend to make a backup of all yours data (they might be lost in process)
* Make a backup of your EFS partition.
* You cant downgrade to NOUGAT again, your IMEI and SIMCARD will be not available due partition and bootloader compatibility.
* If you brick your device, erase all your userdata, cache, system from device and install a fresh nougat to update OTA again, cause if not you can get stuck in bootloop.
* Be sure adb/fastboot will recognize your device using (fastboot devices or adb devices)
Download:
Stock NOUGAT NPS26.118.19-1-6
Motorola Drivers
Standalone ADB/FASTBOOT (thanks XDA/ GOOGLE)
Download OTA
Steps for installing OTA:
1. Connect your device in USB and install Motorola Drivers (I recommend dont try to install drivers first)
2. Download adb/fastboot and extract it (i suggest c:\adb for beginners)
3. Download OTA (dont extract) and place it in adb folder
4. Make a factory reset (recommended)
5 Be sure you have atleast 50% of your battery
6. Shutdown your phone, enter in recovery mode then hold power and press volume down for 1 second and release both.
7. Choose apply update from adb
8. In command prompt goto adb folder, then execute command: adb sideload Blur_Version.27.21.26.albus.retail.en.US.zip
It may take a while for install, so please be patient.
If i forget anything please tell me to i fix the post.
If you have got an OTA from another country (india, europe and others...) and you dont know how to catch it, please be free to contact me , so we can release it together and help others !
Thanks Junior Passos
Good job @raphamfc. Thanks.
Unable to download "Stock NOUGAT NPS26.118.19-1-6", and I've had a few others try as well; no luck. It gets to about 0.2/1.9GB and fails.
Worked for me
Moto z2 Play
hello it turns out that it tries to degrade nougat and it turns out that now I have been stuck for security downgrade so can I fix this to reinstall oreo?
there is not a method to flash it?
My update but i'm not really sure why. I have the NPSS26.118-19-1-6 build, installed as Junior Passos suggested, everything works fine. But it displays an error when trying to sideload de OTA. Could it be because my bootloader is unlocked?
Thank you guys, you are far way better support than Motorola itself.
Mod edit: OP quote removed
---------- Post added at 01:53 AM ---------- Previous post was at 01:47 AM ----------
The error i'm getting says: E2004: oem partition fails to recover... oem has been remounted R/W and has changed the partition contents... Partition contents should not be changed for successful updates; reflash devide to enable OTA updatesE:Error in /sideload/package.zip (Status 7).
I'm going to try reflashing 7.1.1 and then sideloading the OTA to 8.0
Sanefc said:
My update but i'm not really sure why. I have the NPSS26.118-19-1-6 build, installed as Junior Passos suggested, everything works fine. But it displays an error when trying to sideload de OTA. Could it be because my bootloader is unlocked?
Thank you guys, you are far way better support than Motorola itself.
Click to expand...
Click to collapse
IT WORKED! Thanks!!!!!
Sanefc said:
My update but i'm not really sure why. I have the NPSS26.118-19-1-6 build, installed as Junior Passos suggested, everything works fine. But it displays an error when trying to sideload de OTA. Could it be because my bootloader is unlocked?
Thank you guys, you are far way better support than Motorola itself.
---------- Post added at 01:53 AM ---------- Previous post was at 01:47 AM ----------
The error i'm getting says: E2004: oem partition fails to recover... oem has been remounted R/W and has changed the partition contents... Partition contents should not be changed for successful updates; reflash devide to enable OTA updatesE:Error in /sideload/package.zip (Status 7).
I'm going to try reflashing 7.1.1 and then sideloading the OTA to 8.0
Click to expand...
Click to collapse
Hello, I am currently in version NPSS26.118-19-22. must I downgrade in NPSS26.118-19-1-6 version to flash the OTA?
the OTA file says enUS: does it work in europe?
Sorry for my English, I'm French.
----------
Bonjour, je suis actuellement en version NPSS26.118-19-22. Est ce que je suis obligé de redescendre en version NPSS26.118-19-1-6 pour flasher la OTA?
le fichier OTA indique en.US : est ce qu'il fonctionne en europe?
désolé pour mon anglais je suis Français.
miniyouki said:
Hello, I am currently in version NPSS26.118-19-22. must I downgrade in NPSS26.118-19-1-6 version to flash the OTA?
the OTA file says enUS: does it work in europe?
Sorry for my English, I'm French.
----------
Bonjour, je suis actuellement en version NPSS26.118-19-22. Est ce que je suis obligé de redescendre en version NPSS26.118-19-1-6 pour flasher la OTA?
le fichier OTA indique en.US : est ce qu'il fonctionne en europe?
désolé pour mon anglais je suis Français.
Click to expand...
Click to collapse
If you check your ro.build.version.full (via adb shell, and command: getprop ro.build.version.full) you'll see that your phone is also .en.US. In my case I'm on retapac (pacific software channel) and I have the version Blur_Version.27.21.26.albus.retail.en.US.
Try to check that, and if you see en.US, don't worry aobut the version.
I also downgraded to NPSS26.118-19-1-6 to install Oreo OTA.
thank's a lot for your answer : it's write :
Blur_Version.26.286.28.albus.retail.en.US
So must I downgrade?
It works with the Mexican variant XT1710-06, first you have to install the nougat ROM with the February patch following the steps in the the Junior pasos trheat. Also, I don't know if there's an error in your instructions but in order to do the sideload, in the recovery you have to use the Vol+ button to access the menu. That's what I did in my phone.
Do you have all stock? Locked bootloader?
SinkyChan17 said:
Unable to download "Stock NOUGAT NPS26.118.19-1-6", and I've had a few others try as well; no luck. It gets to about 0.2/1.9GB and fails.
Click to expand...
Click to collapse
I'll try to post a Google drive Link for you
NikioXD said:
hello it turns out that it tries to degrade nougat and it turns out that now I have been stuck for security downgrade so can I fix this to reinstall oreo?
there is not a method to flash it?
Click to expand...
Click to collapse
If you downgrade your new version from nougat , you don't need to mess with bootloader or partition. Just flash the others (logo, modem, system, oem and so on )
you will be available to upgrade to Oreo since your build is correctly
Sanefc said:
My update but i'm not really sure why. I have the NPSS26.118-19-1-6 build, installed as Junior Passos suggested, everything works fine. But it displays an error when trying to sideload de OTA. Could it be because my bootloader is unlocked?
Thank you guys, you are far way better support than Motorola itself.
---------- Post added at 01:53 AM ---------- Previous post was at 01:47 AM ----------
The error i'm getting says: E2004: oem partition fails to recover... oem has been remounted R/W and has changed the partition contents... Partition contents should not be changed for successful updates; reflash devide to enable OTA updatesE:Error in /sideload/package.zip (Status 7).
I'm going to try reflashing 7.1.1 and then sideloading the OTA to 8.0
Click to expand...
Click to collapse
doesn't have any problem you have locked or not. Just use a compatible nougat, enable debugging mode and don't forgot to remove password + fingerprint from cellphone, cuz he will show device is encrypted.
miniyouki said:
thank's a lot for your answer : it's write :
Blur_Version.26.286.28.albus.retail.en.US
So must I downgrade?
Click to expand...
Click to collapse
No, your version is a old one, you will upgrade to 26.291-7
ok where can i find this version ?
raphamfc said:
I'll try to post a Google drive Link for you
Click to expand...
Click to collapse
Sorry I never responded! It worked perfectly after I waited a few days and now I'm not only on Oreo, but my IMEI is back *AND* My NFC works! Perfect! Thanks so much for your hard work
Is Magisk working for anyone? With installed Magisk v16.4 my device isn't booting anymore since Oreo, it just stays on the "Your device has been unlocked and can't be trusted." screen after a short vibrate.
Boots again after I sideloaded the uninstaller.
https://androidfilehost.com/?fid=890278863836283331
Anyone got the OTA in Europe?
Related
I really need help on this issue.
It got into a bootloop and the only thing available is fastboot. No recovery or erecovery. This happened when I was at B170 with unlock bootloader and un-rooted on my L01.
Since this, I´ve flashed
fastboot flash boot BOOT.img
fastboot flash system SYSTEM.img
fastboot flash recovery RECOVERY.img
fastboot flash cache CACHE.img
fastboot flash cust CUST.img
using Update.app from B100, B121 and B130. No erros with any of these.
I´ve read all the threads about similar problems and used other solutions like:
Change the order of fastboot flash;
Use Multitool-unbrick
Flash TWRP and oficial recovery with multitool but none worked
Remove sim tray
Connect fastboot to Hisuite, but the PC detects the phone, as it plays a sound, but the Hisuite says no phone is connected
Right now my phone is on at fastboot, because I cant even turn it off. It just restarts, vibes, shows Honor screen and restarts after a few seconds.
I really appreciate any help on this.
Hi!
I had a similar problem once. This was due to a bad recovery and boot partition flashed. You need to flash recovery.img and boot.img extracted from the update.zip from B170 (or B180?) update file.
In my case I was only able to access fastboot but not forced update with update.app (by holding VOL + and -) because the recovery wasn't good. If it's also your case, my solution above must be it.
Envoyé de mon PLK-L01 en utilisant Tapatalk
Sideness said:
Hi!
I had a similar problem once. This was due to a bad recovery and boot partition flashed. You need to flash recovery.img and boot.img extracted from the update.zip from B170 (or B180?) update file.
In my case I was only able to access fastboot but not forced update with update.app (by holding VOL + and -) because the recovery wasn't good. If it's also your case, my solution above must be it.
Envoyé de mon PLK-L01 en utilisant Tapatalk
Click to expand...
Click to collapse
Thanks a million, it worked oddly since I flash, like you said, recovery and boot from B170, but firmware version is B121.
Now it wont manual update to B313 or B121 or even have any OTA...
Is it because I have a unlocked bootloader ?
Edit: made a restore factory defaults with clean internal memory and reflashed B121 through update (local) menu. It now acknowledges B170 OTA. Urrraayyyy
Next step: re-lock bootloader?
Edit: Bootloader relocked using this post.
zinko_pt said:
Thanks a million, it worked oddly since I flash, like you said, recovery and boot from B170, but firmware version is B121.
Now it wont manual update to B313 or B121 or even have any OTA...
Is it because I have a unlocked bootloader ?
Edit: made a restore factory defaults with clean internal memory and reflashed B121 through update (local) menu. It now acknowledges B170 OTA. Urrraayyyy
Next step: re-lock bootloader?
Edit: Bootloader relocked using this post.
Click to expand...
Click to collapse
Hi !
A few months ago I unlocked my bootloader in order to root the phone. Last month I decided that I no longer needed root, so I flashed stock recovery and stock ROM. I updated yesterday to B180 without problem. You don't need to re-lock bootloader. It can stay unlocked without affecting the phone behaviour.
Sideness said:
Hi!
I had a similar problem once. This was due to a bad recovery and boot partition flashed. You need to flash recovery.img and boot.img extracted from the update.zip from B170 (or B180?) update file.
In my case I was only able to access fastboot but not forced update with update.app (by holding VOL + and -) because the recovery wasn't good. If it's also your case, my solution above must be it.
Envoyé de mon PLK-L01 en utilisant Tapatalk
Click to expand...
Click to collapse
Hi man, can you explain it more clearly pls? Having same problem even masters keeping silent,3 of them couldn't fix it.
---------- Post added at 06:44 AM ---------- Previous post was at 06:28 AM ----------
zinko_pt said:
Thanks a million, it worked oddly since I flash, like you said, recovery and boot from B170, but firmware version is B121.
Now it wont manual update to B313 or B121 or even have any OTA...
Is it because I have a unlocked bootloader ?
Edit: made a restore factory defaults with clean internal memory and reflashed B121 through update (local) menu. It now acknowledges B170 OTA. Urrraayyyy
Next step: re-lock bootloader?
Edit: Bootloader relocked using this post.
Click to expand...
Click to collapse
Hi Zinko
It seems to me you have a great experience fixing that type of problem,please share with me as well,I have Huawei Mate 7 and it's rebooting only after trying to upgrade to Marshmallow.
As Sideness said for sure it's due to a bad recovery and boot partition flashed.In my case it's most probably "boot partition".
Sideness said:
Hi!
I had a similar problem once. This was due to a bad recovery and boot partition flashed. You need to flash recovery.img and boot.img extracted from the update.zip from B170 (or B180?) update file.
In my case I was only able to access fastboot but not forced update with update.app (by holding VOL + and -) because the recovery wasn't good. If it's also your case, my solution above must be it.
Envoyé de mon PLK-L01 en utilisant Tapatalk
Click to expand...
Click to collapse
God thank you so much, 4 days i'm struggling with my Honor and now i flash the boot and recovery from the 170 update and IT BOOTS !
Thank you so much.
Now i just had to update to 170 (i was in 121) via OTA and the updates starts and ends properly (first time in big time).
Main thing to understand is that you don't need a matching system.img, just an proper boot and recovery to flash. (if anyone is bricked to hell just like i was)
Demeth said:
God thank you so much, 4 days i'm struggling with my Honor and now i flash the boot and recovery from the 170 update and IT BOOTS !
Thank you so much.
Now i just had to update to 170 (i was in 121) via OTA and the updates starts and ends properly (first time in big time).
Main thing to understand is that you don't need a matching system.img, just an proper boot and recovery to flash. (if anyone is bricked to hell just like i was)
Click to expand...
Click to collapse
I guess if you try to update from B170 to B313 it will mess the recovery.
To fix this, it is required to re-flash the recovery from B170, AND THEN go back to B121. After that it is up to you to go through B140 and jump to B313 or follow the Lollipop path until B180.
Im stuck with the same issue. I had trwp + root installed, the 180 update came, i derooted the device, installed 313 official recovery- rebooted- and installed the update. After this the phone would not boot again.
I have tried everything, and if i choose the B170 recovery from multi tool, i come to the "Huawei software installing" but it stops at 90%.... What can i do to fix this? are there any way to flash a stock rom with TWRP?
---------- Post added at 07:41 PM ---------- Previous post was at 06:59 PM ----------
flashing recovery.img and boot.img from the update.zip from (B170 to B180) update file worked! the phone starts on version b130! but im struggeling to update the phone any further? what do do?
leholtet said:
Im stuck with the same issue. I had trwp + root installed, the 180 update came, i derooted the device, installed 313 official recovery- rebooted- and installed the update. After this the phone would not boot again.
I have tried everything, and if i choose the B170 recovery from multi tool, i come to the "Huawei software installing" but it stops at 90%.... What can i do to fix this? are there any way to flash a stock rom with TWRP?
---------- Post added at 07:41 PM ---------- Previous post was at 06:59 PM ----------
flashing recovery.img and boot.img from the update.zip from (B170 to B180) update file worked! the phone starts on version b130! but im struggeling to update the phone any further? what do do?
Click to expand...
Click to collapse
Flash a complete B121 and then go all the way untill B180. The updates will show automatically, as you will have only to choose to update.
ZTE Nubia M2 guide:
I just got a Nubia M2, and there is my tutorial to unlocking Boot loader , root and install TWRP:
1: First thing i downgrade my global rom from 1.11 to 1.06 from update software menu
2: I unlock the boot loader by MyPhone Flasher
3: Then i install TWRP
4: and install Magisk from TWRP menu
5: In the final i install my first Custom Rom
6: I enjoy it
Thank's to yasasbandara :https://forum.xda-developers.com/member.php?u=4672130
I would like to quote his very good article from here: https://forum.xda-developers.com/showpost.php?p=76098771&postcount=143
English Guide for TWRP+Root+Custom Rom
Step 1 – Preparation
Step 2 – Installing Chinese Rom (to get an Unlocked Bootloader) via Stock Recovery
Step 3 – Using ADB to replace Stock Recovery with TWRP
Step 4 – Installing Custom/Official Rom/Roms and Rooting
Step 1:-
Prepare a SD card and copy the china rom (NX551-update_1.59.zip), Super SU Zip (SuperSU-v2.82-201705271822.zip) and any Custom Rom you wanna flash.
Get rid of any encryptions, fingerprints, passwords etc. you may have put on the phone.
Copy contacts, sms, call logs etc. (use super backup) and store on SD card.
**You can use a tool called "Nubia Emergency Tool" for backing up the service areas of the phone (optional). This backup will contain IMEI numbers and stuff. It'll help you later if you turn up with a brick after a bad custom rom flash**
Charge fully.
Download a flasher package like GizFlasher M2 v2 etc. prepared by developers in the gizchina forum, Greek Forum or 4PDA (to search for these, just use google and type nubia m2 gizchina/nubia m2 greek forum etc. Use google translation for understanding).
Step 2:-
Turn the phone off. Press Power & Volume up --> Boot to Stock Recovery. Use wipe function to wipe caches and data. Use update function and select the NX551-update_1.59.zip file and flash it. This will give you an unlocked bootloader.
Step 3:-
Boot to system. Select language and stuff. Turn on developer options. Tick OEM unlocking and USB debugging.
Use GizFlasher M2 v2 (or similar packages from other developers) to install ADB. For GizFlasher M2 v2, uncompress into a folder and run ‘Autorun.exe’ with admin rights. Answer ‘Yes’ to all and install ADB drivers systemwide.
You can check drivers by connecting the phone in “charge only” mode. Check device manager to see if ‘Android ADB interface’ is available. Give permission in the phone if required.
(If you find unknown Android devices in device manager, chose driver update (right click) --> Browse drivers on my computer --> Choose from list of drivers on the computer --> Android device --> Next --> Android ADB interface version.)
If the drivers are OK, keep the phone in charging only mode and check adb installation with a command like “adb devices” using the command prompt. This should initiate adb service and drivers (useful in Win10). Your device name will be displayed. Close the command prompt.
In the GizFlasher folder, run the "GizFlasher.bat" with administrator rights. In the window that appear, give "1" and enter for unlocking the bootloader (confirm on the phone if required).
Wait for the phone to restart.
The phone will restart in fastboot mode.
After this, type "2" and enter for flashing TWRP.
TWRP will be flashed and the phone will start in the new Recovery. You can unplug the phone from the PC.
*** Immediately after the TWRP, it’s always a good idea to setup language, time and brightness and remove screen timeout. Do a TWRP backup using the SD card.***
Step 4:-
Please note that using the stock recovery and ADB commands are usually harmless and rarely cause issues. But from this point onwards, it’s always a good idea to get a TWRP backup stored in somewhere safe (in your PC). Furthermore, if you wanna be more careful, take a backup of the service areas of your phone using a program called “Nubia Emergency Tool”. You’ll need the latest Chinese only version and instructions will be available at the 4pda forum.
Once, you’ve chosen a custom rom, please read instructions by the respective developer and follow those instructions.
Boot to TWRP recovery and do the reset. As a general rule, always wipe caches and data (full reset) and flash the rom. You’ll need to flash the SuperSU zip afterwards and wipe caches to obtain root.
If the ROM is working properly, restore your contacts, SMS etc. using super backup.
Note -
** Older phones that did not come with a higher 'Global Rom' version have their bootloaders already unlocked. In such a case, you can skip the Chinese Rom installation.
** For those who are having problems with ADB and Fastboot in newer Windows 10 versions - This is not your fault. The problem is probably with Windows. You can try to force-remove driver signature checking [restart with shift key-->troubleshooting-->Advanced-->restart-->remove sig. checking (option 7)] and do everything over.
However, do not waste a lot of time going through the same dance over and over again. The easiest way to use ADB/Fastboot is via Linux. That's an undisputed truth.
Just search for a project called FWUL (F*** Windows Use Linux) in XDA forum and follow instructions. You'll need a small pen drive (2GB or more) and that's it.
Stock Roms:
Link to last Global version 1.11
http://rom.download.nubia.com/Europe%26Asia/M2/NX551J_Z69_EN_TSXPR17D11L111.zip
Link to 1.06 Global version:
http://rom.download.nubia.com/Europe%26Asia/M2/NX551J_Z69_EN_TSXPR17D00L106.zip
Link to last chinese version 2.04
https://drive.google.com/uc?id=1WGQNasYmBjZ5rtJGAhS9kZLFKTsM1C5m&export=download
Link to chinese version 1.59
https://mega.nz/#!AzhAkJTY!v4RYYkY4xuSE5e6xF0icQXQ4uygh-HZfSXJw_jpt6sk
Custom Roms:
Germakrom: (my first Custom rom)
v2.10:
#Added default Nubia internet browser.
#Fixed notifications that didn't come.
#All apps now work in the background.
#bug fixes
https://mega.nz/#!IvIFSBhZ!wXLwGIzalGGGbkV_-wOvGQPBJbzWLLzHnwubTGH9jjk
GizROM:
v 1.0
#release iniziale;
#basata sul firmware internazionale NubiaUI 1.06 (Marshmallow).
https://rom.gizchina.it/upload/M2/M2_NubiaUI_M_1.10_GizRom.zip
GizROM MIUI 9 edition
v(8.2.1 EU)
Changelog 1.4:
#aggiornamento alla MIUI 9 8.2.1 EU.
http://rom.gizchina.it/upload/M2/M2_MIUI9_8.2.1_EU_francko76.zip
GizROM ColorOS Edition
Changelog 1.0:
#Versione iniziale;
#basata sul firmware 20171221 per OPPO R9s
http://rom.gizchina.it/upload/M2/M2_ColorOS_20171221_GLOBAL_francko76.zip
GizROM Flyme Edition
Changelog 1.0:
#Flyme 6.7.12.22R;
#DT2W funzionante.
http://rom.gizchina.it/upload/M2/flyme_NX551J_6.7.12.22R-francko76.zip
Le_ITA
Le ITA V1 by leitagroup Basata sulla Nubia UI 5 Cinese
Changelog:
Rimosse app cinesi;
Tradotte app di sistema;
Aggiunte Gapps;
Aggiunto Magisk per il root;
Modificato il bootanimation;
Primo avvio gestito dall'app di google;
Italiano selezionabile tra le lingue;
Avvertenze:
Al play services al primo avvio non vengono concesse le autorizzazioni, quindi dovrete skippare la configurazione iniziale che riguarda l'account google, andare nelle impostazioni/applicazioni e dare tutti i permessi al play services. Altra cosa, l'app della camera non è tradotta perchè ci sono stati dei problemi.
Traduzione:
Fatemi sapere se trovate roba non tradotta, se la trovate mandate uno screen di tutto ciò che sta da tradurre e dove trovarlo. Oltre all'app della camera anche il meteo, l'app del backup e dei temi non sono tradotte
Link:
https://androidfilehost.com/?fid=890129502657597464
Developed by @mauronofrio
MIUI Pro ROM
https://miuipro.by/rommgr/device/530
Tools:
1.# Nubian emergency tool:
v:1.0.6:
https://mega.nz/#!75VkSJaA!FxEk5OlcRzlLRe3qfWTf2XAzYy8ghB_KjC5Jav9NhwE
V:1.1.4
https://drive.google.com/file/d/10VYEh8jtFi5Ui-7Dwcl4yohEx88qGRa7/view
https://mega.nz/#!1qBzjCYS!utR9UjlNTOHo636iIczbqjLoycss-VEdn8Ae9CqOIHI
2#GizFlasher:
https://mega.nz/#!JcE0xQCD!8PBIyIvNsMmgPqUIIG_cWldQ0jexVQblDwxF6BJCCVk
3#Nubia M2 Toolkit files: (very very useful)
https://drive.google.com/file/d/0By-NOo-lCyxBbm13Q0liejNURFU/view
4#TOOL ALL IN ONE: Nubia M2 supported
https://www.androidfilehost.com/?a=show&w=files&flid=38683
Visit :https://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711 for more instructions
Kernel source:
https://github.com/ztemt/NX551J_M_kernel
Thanks for You hard work .
Nice wrap up of instructions.well done.
If you want in tools section add this one too
https://forum.xda-developers.com/android/development/nubia-m2-emergency-tool-1-1-4-unbrick-t3772342
Thanks for this Topic!
GERMAD said:
Nice wrap up of instructions.well done.
If you want in tools section add this one too
https://forum.xda-developers.com/android/development/nubia-m2-emergency-tool-1-1-4-unbrick-t3772342
Thanks for this Topic!
Click to expand...
Click to collapse
Yes it's an update of nubiaan emergency tools
I posted an earlier version
I will update it soon
parmaniec said:
Thanks for You hard work .
Click to expand...
Click to collapse
You must use the Thank You button instead of a message to keep the article readable
Why I have a sad face in my rom?do you have an issue that I can help?
Germakrommy first Custom rom)
Ps: Earlier version you put don't work for Nubia m2 that's why I told you to put this one I posted.
GERMAD said:
Why I have a sad face in my rom?do you have an issue that I can help?
Germakrommy first Custom rom)
Ps: Earlier version you put don't work for Nubia M2 that's why I told you to put this one I posted.
Click to expand...
Click to collapse
Sad face was inadvertance by the
For me Nubia Emergency tool 1.0.6 works fine for me, but i update to the last as you suggested .
As for backup it works.but previous versions don't work for unbricking Nubia M2.
Sad news for us
moyses said:
Sad news for us
Click to expand...
Click to collapse
Screenshot
Gesendet von meinem ONE A2001 mit Tapatalk
For 20 days I'm using the Miui Pro 9.5.2.0 chinese stable, to me this is the best custom rom for the Nubia M2.
I only see two problems...
First, this rom don't has the NeoVision camera
Second, usb debug not working, I tried enable, disable, revoke permissions, editing build.prop etc...
I'll wait to the next atualization
Congratulations to Miui Pro team developers! :good:
THANK YOU!
THANKS for the hard work guys , i really appreciate it a lot. CHEERS:good:
when i try to install twrp its show waiting for device in cmd, how to fix that ? help me please
Hi Guys. I successfully unlocked the bootloader and installed LOS 15.1.
Is it possible to flash the internatonal stock rom? Any fastboot or twrp based solution?
Thanks.
AE
Please help me, im using twrp version 3.2.1 that recommend for LOS 15.1 rom. But when i try to install magisk or something that .zip format via twrp (like nubia camera.zip) its always reset my handphone, all my application is gone, please help me fix this mate, please.
Please help, I installed Android Oreo, I made it wipe through an Android Oreo TWRP that was here in the forum. However, I ran out of operating system.
Then through HuaweiExtractor subtraction System.img, kernel.img, recovery ramdisk.img. Flashes by ABD (I had bootload access) however I had no solution.
Then at startup a bootloop was generated where I started in
"Error Mode" Please update system again "Func NO : 11 (recovery image)" and "Error NO : 2 (load failed!)". All wrong.
I searched the internet and they said that when the "Error Mode" message appeared, it was because the bootloader was not fully unlocked.
So I proceeded to block it with the command: fastboot oem relock xxxxxxxxxxxxx. The bootloader is blocked, however, now the cell phone starts and remains pasted on this screen:
https://ibb.co/ftbq1n
It doesn't restart, it just freezes there.
Does anyone know how to solve my problem?I will be eternally grateful if anyone can help me.
_____________________________________________________________________________________________
UPDATE: The cell phone was completely downloaded. I plugged it into the computer and was able to enter Fastboot mode. So again I have TWRP for OREO.
But I still have a boot loop of "Error MODE". Any idea how to fix it?
TWRP 8 Oreo https://ibb.co/nEn5HS
Error MODE https://ibb.co/mrErrn
Aspiranteh said:
Please help, I installed Android Oreo, I made it wipe through an Android Oreo TWRP that was here in the forum. However, I ran out of operating system.
Then through HuaweiExtractor subtraction System.img, kernel.img, recovery ramdisk.img. Flashes by ABD (I had bootload access) however I had no solution.
Then at startup a bootloop was generated where I started in
"Error Mode" Please update system again "Func NO : 11 (recovery image)" and "Error NO : 2 (load failed!)". All wrong.
I searched the internet and they said that when the "Error Mode" message appeared, it was because the bootloader was not fully unlocked.
So I proceeded to block it with the command: fastboot oem relock oem xxxxxxxxxxxxx. The bootloader is blocked, however, now the cell phone starts and remains pasted on this screen:
https://ibb.co/ftbq1n
It doesn't restart, it just freezes there.
Does anyone know how to solve my problem?I will be eternally grateful if anyone can help me.
Sorry bad english.
Click to expand...
Click to collapse
try to flash stock recovery then try force upgrade method.
h30_u10 said:
try to flash stock recovery then try force upgrade method.
Click to expand...
Click to collapse
Edit:
I can flash the recovery stock however, I don't know if in android OREO I can install full firmware through a folder (dload) on the SD card. Is there a similar way as in Nougat and earlier versions of android?
Try to flash your rom with twrp and install magisk before trying to boot into rom. Magisk patch boot.img and remove many security/error check when booting to rom.
rhaavin said:
Try to flash your rom with twrp and install magisk before trying to boot into rom. Magisk patch boot.img and remove many security/error check when booting to rom.
Click to expand...
Click to collapse
I'll give it a try. The problem is that the Rom Oreo I have is not flash for TWRP. I have searched but I still can't find an Oreo ROM that can be flashed by TWRP.
I found this method: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-oreo-update-package-t3699522
that I think can work. However, it is for Mate 9, so I have to replace the files with those of Mate 10 lite and rename them as if they were Mate 9. Although I'm not sure what I should extract from Update.app to rename.
If someone could guide me, I'd be very grateful.
If that doesn't work, I will try this other method I found by browsing the forums. [ Chuckles]
https://forum.xda-developers.com/showpost.php?p=75628230&postcount=71
Any contribution is welcome.
Translated with www.DeepL.com/Translator
I stucked on the same or very similar fastboot screen, phones OS was oreo, here is why it happened:
I tried to use command fastboot flash recovery TWRP3.1.1.img
It will always show Failure message.
Then on this kind XDA forum I came to know that the recovery location is changed in oreo to
recovery_ramdisk I flashed with: fastboot flash recovery_ramdisk TWRP3.1.1.img
And thus reached the same fastboot error screen you have posted.
Workaround was: Get the update.app file from the update zip files (I used HWOTA method
to upgrade to Oero when my device was already soft bricked). So used update extractor
to pull out UPDATE.APP file form the biggesst update zip file from HWOTA folder,
but first u have to go to settings and disable header check sum option otherwise it will show error.
So I pulled out the proper stock recovery file named like: recovery_ramdisk.img
I used command: fastboot flash recovery_ramdisk revcovery_ramdiskimg
Now I got the stock recovery that I can use to wipe data and do factory reset.
So if you can come to this point, may be after factory reset you would be able to get it back.
Good luck.
Fix Error (SOLVE)
I can say from experience that the same thing happened to me, and the only thing you have to do is wait until your phone has a 0% charge, leaving the screen turned on with the error.
When that happens, connect the original cable to the PC and connect it in Fasboot mode, unlock the bootloader if you do not have it, then install the firmware of it ... with the HWOTA tool that you will see in one of the posts in this section ... you will have to have the three corresponding files of the same one ... the UPDATE, DATA, DATAPUBLIC and follow the steps in the post of HWOTA ... and you will relive your team.
Greetings ... I hesitate to answer for the difference of time and my work ... Greetings from Panama
Aspiranteh said:
Please help, I installed Android Oreo, I made it wipe through an Android Oreo TWRP that was here in the forum. However, I ran out of operating system.
Then through HuaweiExtractor subtraction System.img, kernel.img, recovery ramdisk.img. Flashes by ABD (I had bootload access) however I had no solution.
Then at startup a bootloop was generated where I started in
"Error Mode" Please update system again "Func NO : 11 (recovery image)" and "Error NO : 2 (load failed!)". All wrong.
I searched the internet and they said that when the "Error Mode" message appeared, it was because the bootloader was not fully unlocked.
So I proceeded to block it with the command: fastboot oem relock xxxxxxxxxxxxx. The bootloader is blocked, however, now the cell phone starts and remains pasted on this screen:
https://ibb.co/ftbq1n
It doesn't restart, it just freezes there.
Does anyone know how to solve my problem?I will be eternally grateful if anyone can help me.
_____________________________________________________________________________________________
UPDATE: The cell phone was completely downloaded. I plugged it into the computer and was able to enter Fastboot mode. So again I have TWRP for OREO.
But I still have a boot loop of "Error MODE". Any idea how to fix it?
TWRP 8 Oreo https://ibb.co/nEn5HS
Error MODE https://ibb.co/mrErrn
Click to expand...
Click to collapse
usman400 said:
I stucked on the same or very similar fastboot screen, phones OS was oreo, here is why it happened:
I tried to use command fastboot flash recovery TWRP3.1.1.img
It will always show Failure message.
Then on this kind XDA forum I came to know that the recovery location is changed in oreo to
recovery_ramdisk I flashed with: fastboot flash recovery_ramdisk TWRP3.1.1.img
And thus reached the same fastboot error screen you have posted.
Workaround was: Get the update.app file from the update zip files (I used HWOTA method
to upgrade to Oero when my device was already soft bricked). So used update extractor
to pull out UPDATE.APP file form the biggesst update zip file from HWOTA folder,
but first u have to go to settings and disable header check sum option otherwise it will show error.
So I pulled out the proper stock recovery file named like: recovery_ramdisk.img
I used command: fastboot flash recovery_ramdisk revcovery_ramdiskimg
Now I got the stock recovery that I can use to wipe data and do factory reset.
So if you can come to this point, may be after factory reset you would be able to get it back.
Good luck.
Click to expand...
Click to collapse
I also uploaded to OREO by HWOTA like you, I managed to do it without problems, all functional. Then I don't remember why but I decided to give wipes and that's when my problem started.
Yes, recovery_ramdisk was already in consideration.
I even flashed:
fastboot flash recovery_vbmeta recovery_vbmeta.img
fastboot flash recovery_ramdisk recovery_ramdis.img
fastboot flash recovery_vendor recovery_vendor.img
fastboot flash kernel kernel.img
fastboot flash system system.img
fastboot reboot
but I can't get it to start just throw that "MODE ERROR" at me, I don't think system is completely installed :/ /
emorenoebultron said:
I can say from experience that the same thing happened to me, and the only thing you have to do is wait until your phone has a 0% charge, leaving the screen turned on with the error.
When that happens, connect the original cable to the PC and connect it in Fasboot mode, unlock the bootloader if you do not have it, then install the firmware of it ... with the HWOTA tool that you will see in one of the posts in this section ... you will have to have the three corresponding files of the same one ... the UPDATE, DATA, DATAPUBLIC and follow the steps in the post of HWOTA ... and you will relive your team.
Greetings ... I hesitate to answer for the difference of time and my work ... Greetings from Panama
Click to expand...
Click to collapse
Yes, I really think this is the solution but it's only posted HWOTA and not HWOTA8 for Mate 10 lite... If there was only one HWOTA8 for our equipment, I'm sure I could fix it .
Aspiranteh said:
I also uploaded to OREO by HWOTA like you, I managed to do it without problems, all functional. Then I don't remember why but I decided to give wipes and that's when my problem started.
Yes, I really think this is the solution but it's only posted HWOTA and not HWOTA8 for Mate 10 lite... If there was only one HWOTA8 for our equipment, I'm sure I could fix it .
Click to expand...
Click to collapse
hmmm since I am all set with Oreo update and its working and I am not a very advanced user in flashing etc.
So am not going to any further thing until proper oreo update comes
But I was thinking at a point, why not go through existing HWOTA script, change the commands where recovery
is referred, (change recovery to recovey_ramdisk in any fastboot command found inside script), then running it to
try luck.
Also I think TWRP for mate 10 lite for Oreo version was made available a few days ago in this forum, search it
usman400 said:
hmmm since I am all set with Oreo update and its working and I am not a very advanced user in flashing etc.
So am not going to any further thing until proper oreo update comes
But I was thinking at a point, why not go through existing HWOTA script, change the commands where recovery
is referred, (change recovery to recovey_ramdisk in any fastboot command found inside script), then running it to
try luck.
Also I think TWRP for mate 10 lite for Oreo version was made available a few days ago in this forum, search it
Click to expand...
Click to collapse
Forgive my ignorance but what would be the script to edit, I downloaded the HWOTA again to modify it but I don't really know which file to modify. :confuso:
** @vovan1982 Hi, excuse me. I saw you post HwOTA for Mate 10 lite, do you know if there are any options for HwOTA8? Thank you very much in advance!
Aspiranteh said:
Forgive my ignorance but what would be the script to edit, I downloaded the HWOTA again to modify it but I don't really know which file to modify. :confuso:
** @vovan1982 Hi, excuse me. I saw you post HwOTA for Mate 10 lite, do you know if there are any options for HwOTA8? Thank you very much in advance!
Click to expand...
Click to collapse
If you can enter to trwp8, I can try to give you my backup of oreo mate 10. The problem for the script is, I think, the recovery push by vovan1982 is not comptatible with the aero installed, and when you are in twrp8, usb cable don't work!
gmbengue said:
If you can enter to trwp8, I can try to give you my backup of oreo mate 10. The problem for the script is, I think, the recovery push by vovan1982 is not comptatible with the aero installed, and when you are in twrp8, usb cable don't work!
Click to expand...
Click to collapse
If I have access to Twrp8, if you could share your backup with me I would be very grateful! :fingers-crossed:
Aspiranteh said:
If I have access to Twrp8, if you could share your backup with me I would be very grateful! :fingers-crossed:
Click to expand...
Click to collapse
I'm in L21. like I see, your model is L03. If you confirm that it's good I'll try to upload it. If someone can help for what to backup. It's too big (ramdisk, kernel, product, product image, cust, cust image,system, vendor, vendor image, version and version image)
gmbengue said:
I'm in L21. like I see, your model is L03. If you confirm that it's good I'll try to upload it. If someone can help for what to backup. It's too big (ramdisk, kernel, product, product image, cust, cust image,system, vendor, vendor image, version and version image)
Click to expand...
Click to collapse
If you please. If that's what you ask in MediaFire, there are 10 GB free to upload to the cloud. I know your help will help someone else at some point. . Thx.
file name is shell inside the folders find it or edit the .bat file to know where is the shell located
but if this is something new 4u then ask some one with little knowledge of MS DOS commands or shell scripts to edit it for u
Aspiranteh said:
If you please. If that's what you ask in MediaFire, there are 10 GB free to upload to the cloud. I know your help will help someone else at some point. . Thx.
Click to expand...
Click to collapse
Ok, waiting for a response of Kingofmezi, I want to know what to put in the backup
Lords, I have news for you. After many attempts I couldn't fix my "ERROR MODE", so I blocked the Bootloader and went to the shop to make my warranty effective... The technician believed my history that the phone was blocked after an update that appeared to me through OTA and will enforce my warranty because the phone presented "Factory Errors"... XD. Well, that's it, I've got my cell phone working again. Thank you all for your help.
gmbengue said:
Ok, waiting for a response of Kingofmezi, I want to know what to put in the backup
Click to expand...
Click to collapse
Maybe if you upload the backup you can help someone else in the future. Thank you very much for your willingness to help me. :good::fingers-crossed:
Urgent ordi 8.0 failed
gmbengue said:
Ok, waiting for a response of Kingofmezi, I want to know what to put in the backup
Click to expand...
Click to collapse
Bonjour
J'ai exactement le même problème.
Tu pourrais me donné le backup de ton mate 10 ton envie , s'il te plait.
Je serrais usurper heureux si tu pouvais m'aider.
Merci d'avance.
Je m'excuser ne parle pas anglais .
Up
RobotGuerrier said:
Bonjour
J'ai exactement le même problème.
Tu pourrais me donné le backup de ton mate 10 ton envie , s'il te plait.
Je serrais usurper heureux si tu pouvais m'aider.
Merci d'avance.
Je m'excuser ne parle pas anglais .
Click to expand...
Click to collapse
XDA Forum rules
4. Use the English language.
We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator.
FOR MOTO G7 PLUS ONLY!!!
FOR STOCK SYSTEM VERSION: PPW29.98-107 ONLY!!!
Hello, everyone.
I Will leave here a little tutorial for those who do not want to wait the TWRP of the Moto G7 Plus to be able to install Magisk. Use as a basis the file I will leave below:
Step 1: Put the phone into Fastboot mode (Volume Down + Power);
Step 2: With the mobile phone in fastboot mode, run the file "Flash modded boot PPW29.98-107. bat ";
Step 3: Turn on your phone and make sure the Magisk application is already installed, otherwise copy the Magisk apk to the device's internal memory and install.
Installed Magisk and Root permission granted!!!
Link: http://www.mediafire.com/file/fifw46dwo6fgd4p/Root_Moto_G7_Plus_-_PPW29.98-107.zip/file
I was rooted using the Magisk method without TWRP from the Moto G7 forum that involves creating then flashing the patched boot.img from stock firmware. Worked fine for almost 3 weeks then today I had no root, nothing had changed and I was barely using the phone recently.
I have root back now but had to flash the full PPW29.998-66 firmware because the original method didn't work anymore, even after a factory reset, but on full firmware again it worked on the first try. Don't want to mess with it but if I lose root again I'll try your method and thanks for posting it.
Locked or Unlocked Bootloader?
Laercio_lalau said:
Locked or Unlocked Bootloader?
Click to expand...
Click to collapse
Unlocked bootloader.
Luiz, este processo funciona com a versão retbr ?
Luiz, this process work with retbr firmware ?
Thanks
JoãoBC said:
Luiz, este processo funciona com a versão retbr ?
Luiz, this process work with retbr firmware ?
Thanks
Click to expand...
Click to collapse
If needed, you can create a magisk patched boot.img yourself directly on your device using your firmware. Then just fastboot flash the patched_boot.img. Also, if you're using TWRP, you can flash the patched_boot.img in TWRP or even just simply try flashing the Magisk.zip in TWRP.
Quiero tener acceso raíz en mi moto G7 plus, con compilación PPWS29.98-66-2.
Cómo podría hacerlo?
I want to have root access on my G7 plus motorcycle, with PPWS29.98-66-2 compilation.
How could I do it?
---------- Post added at 02:37 PM ---------- Previous post was at 02:25 PM ----------
Dahenjo said:
I was rooted using the Magisk method without TWRP from the Moto G7 forum that involves creating then flashing the patched boot.img from stock firmware. Worked fine for almost 3 weeks then today I had no root, nothing had changed and I was barely using the phone recently.
I have root back now but had to flash the full PPW29.998-66 firmware because the original method didn't work anymore, even after a factory reset, but on full firmware again it worked on the first try. Don't want to mess with it but if I lose root again I'll try your method and thanks for posting it.
Click to expand...
Click to collapse
Cómo obtengo raíz en moto G7 plus PPW29.98-66-2? Ayúdame por favor
Thread closed at OP request
Unfortunately Installed Wrong Codename ROM On My poco f1
after that my device goes in to fastboot mode
and i cannot access recovery mode because fastboot everywhere
if i press volume up + power button = fastboot mode
if i reboot = fastboot mode
if i plug in to charger = fastboot mode
then i flashed mi global stable build from miflash
still device booting in to fastboot mode automatically
after that when i flashed miui 9 device booted up successfully then i updated to miui 10 oreo from system update
but when i try to update miui 10 oreo to pie from ota/twrp/fastboot device automatically booting in to fastboot mode
after that i tried android q dp4 gsi guess what device booted android q gsi successfully
Tested All pie custom roms also same issue
it means i cant install pie
dont know what is happening exactly
DOWNLOAD
"beryllium-9.6.27-9.0-vendor-firmware" AND PUT IT on sdcard/usbotg and FLASH it via TWRP from
https://mirror.akhilnarang.me/MIUI/beryllium/
then flash any pie rome + GAPPS (if needed) +magisk19.3(if you wana root) and reboot
the device will boot
Xiaomi Poco uses Modified Vendor image ! that why it needed to be flashed saperatedly!
check and let me know!
edit1
if you cannot access recovery! BOOT into recovery via fastboot command line (while Poco is connected in Fastboot mode to your PC) and your PC have all driver installed. Open Minimal adb and fastboot
fastboot device // to check connection
fastboot boot ..... and Drag twrp from desktop and DROP it on CMD window ... then ENTER,
your POCO will BOOT, while its on Yellow LOGO, try to put USB OTG drive so that Twrp can READ its contents for you to Flash! , usb otg plugged AFTER twrp boot usually don't get red! ... OR better put flashable zips in sd card using any adaptor
I suffer from the same problem and applied all your steps but go to put fastboot .
please solve this
hekoo1 said:
I suffer from the same problem and applied all your steps but go to put fastboot .
please solve this
Click to expand...
Click to collapse
please xplain more
1. did you flash vendor (latest) ?
2. what rom you are flashing?
3. miui works?
plz explain
yasuhamed said:
please xplain more
1. Did you flash vendor (latest) ?
2. What rom you are flashing?
3. Miui works?
Plz explain
Click to expand...
Click to collapse
1. I flashed vendor 9.6.27-9.0 via recovery
2. I want flash miui 10.3.5 latest
3. Miui android 8.1 working . Android 9 not working
hekoo1 said:
1. I flashed vendor 9.6.27-9.0 via recovery
2. I want flash miui 10.3.5 latest
3. Miui android 8.1 working . Android 9 not working
Click to expand...
Click to collapse
THERE IS NO NEED TO FLASH VENDOR if you going to flash ANY MIUI!
make sure you have correct build/version of MIUI 10.3.5,
some times, if DATA partitions is CORRUPT then click on FORMAT data, type YES and it will wipe the WHOLE device! encryptions will be reset! then place MIUI10.3.5 and check!
remember, to take backups!
if miui 9 has worked then this means the downloaded miui10 is not the correct one!
No I can not.
When installing any system MIUI ANDROID 9 PIE the phone is rebooted to FASTBOOT
---------- Post added at 09:05 AM ---------- Previous post was at 08:55 AM ----------
YasuHamed said:
THERE IS NO NEED TO FLASH VENDOR if you going to flash ANY MIUI!
make sure you have correct build/version of MIUI 10.3.5,
some times, if DATA partitions is CORRUPT then click on FORMAT data, type YES and it will wipe the WHOLE device! encryptions will be reset! then place MIUI10.3.5 and check!
remember, to take backups!
if miui 9 has worked then this means the downloaded miui10 is not the correct one!
Click to expand...
Click to collapse
No I can not.
When installing any system MIUI ANDROID 9 PIE the phone is rebooted to FASTBOOT
PLEASE SOLVE THIS
hekoo1 said:
No I can not.
When installing any system MIUI ANDROID 9 PIE the phone is rebooted to FASTBOOT
---------- Post added at 09:05 AM ---------- Previous post was at 08:55 AM ----------
No I can not.
When installing any system MIUI ANDROID 9 PIE the phone is rebooted to FASTBOOT
PLEASE SOLVE THIS
Click to expand...
Click to collapse
I know this is a longshot but, bro, did you manage to solve the issue? I'm in the same situation and trying to find a solution. Opened a new thread but no help from anywhere... Anyone? Guys?
[QUOTE = "crimsonFay, postagem: 83995307, membro: 10638959"]
Eu sei que é uma hipótese remota, mas, mano, você conseguiu resolver o problema? Estou na mesma situação e tentando encontrar uma solução. Abriu um novo tópico, mas sem ajuda de lugar nenhum ... Alguém? Rapazes?
[/CITAR]
eu tmb estou a meses nessa situação, acho que só flash edl auth l resolver
For People Stuck On Oreo Firmware (Poco F1)
I have seen many people facing this issue where they flashed a OxygenOS rom of different phone ( Due to a idiot youtuber said it can be flashed on all devices ) I recently recieved a POCO F1, with same condition where i cannot update MIUI over...
forum.xda-developers.com