Database Info

Easy Flash to Nougat Tutorial (Unlocked Retail Devices)

Easy Flash to Nougat Tutorial (Unlocked Retail Devices)
Prerequisites:
Download RSD lite XML to Batch Script from https://www.androidfilehost.com/?fid=24651430732235266
Download ROGERS_MPL24.246-45 from https://mega.nz/#!nssGEDiT!hhLkcTM106hmqbH_fiWfAytEV-fgdlYOhUwpcd_sGJY
Download Nougat firmware from https://mega.nz/#!608HGYqB!kKTc1196PhimDtVte6OdCWF6aXSWGSNLToEkvUePymE
Steps:
Unpack RSDLite XML to Batch Script to a folder on your computer
Unpack Rogers 24.246-45 firmware to the SAME folder
Run 2-rsd-flash-flashfile-windows.bat
Batch File #2 will convert the flashfile.xml file (included in Rogers zip) to a Batch file
Run flashfile.bat which will flash the Rogers firmware to your device (WILL WIPE EVERYTHING EXCEPT MICRO SD CARD)
Wait till its done!
Your device should now have Rogers 24.246-45 Firmware.
From the Bootloader, select Recovery Mode.
If you see No Command don't panic! That's normal. Press the power button for a couple seconds and press volume up or down (not sure if you need volume buttons but I always do anyway)
Once it displays on screen, Select ADB Sideload
From an adb capable command prompt, enter ADB Sideload <name and location of Nougat.zip> (minus the <> obviously)
This will take time. Leave it alone!
Once complete, simply reboot from recovery and let the device start like normal.
TROUBLESHOOTING:
If ADB Sideload gives you a Can't Read error, try these steps:
1. Download Large Address Awareness from here https://www.techpowerup.com/forums/threads/large-address-aware.112556/
2. Download ADB from here http://forum.xda-developers.com/showthread.php?t=2588979
3. Start Task Manager and kill adb.exe if its running
4. Load the adb.exe file from Large Address Awareness and check the flag button
5. Continue on with adb sideload
I've tested this process multiple times today and it should work well. Let me know if you have any trouble!
I want to mention I have had NO success backing up with TWRP and restoring after this. Something changed with Nougat and any modification to System causes a soft brick (it did for me anyway). Do not attempt to flash system mode TWRP or flash the TurboZ kernel. They don't work and they will cause a boot loop.
UPDATE:
This method might not be for everyone, and if you're not interested in sticking with stock 7.0 and potentially want to roll around to other ROMs you should follow this guide instead; http://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-versions-t3506342

Great thank you! Question:
Will all the radio bands (T-MOBILE) still work as normal?
Have you try this out with Google Day Dream VR yet?
I had the note 7 and the Galaxy VR., Kinda of miss that.

dallas90733 said:
Great thank you! Question:
Will all the radio bands (T-MOBILE) still work as normal?
Have you try this out with Google Day Dream VR yet?
I had the note 7 and the Galaxy VR., Kinda of miss that.
Click to expand...
Click to collapse
Daydream works from what I can tell. Also I'm on att so I haven't checked T-Mobile bands but im assuming they work fine. I know there's an app to check which bands your device supports. I'll try downloading it and let you know

So I get to the point to sideload the nougat update and it always says "can't read..." I've done factory resets and everything else I could think of, still no go for me.

Prfndhatrdofman said:
...
I want to mention I have had NO success backing up with TWRP and restoring after this. Something changed with Nougat and any modification to System causes a soft brick (it did for me anyway). Do not attempt to flash system mode TWRP or flash the TurboZ kernel. They don't work and they will cause a boot loop.
Click to expand...
Click to collapse
So... are you of the opinion that recovering a Nougat boot+system TWRP backup on a MM phone would cause a soft brick too?
What type of soft brick do you faced exactly?

Prfndhatrdofman said:
Easy Flash to Nougat Tutorial (Unlocked Retail Devices)
Prerequisites:
Download RSD lite XML to Batch Script from https://www.androidfilehost.com/?fid=24651430732235266
Download ROGERS_MPL24.246-45 from https://mega.nz/#!nssGEDiT!hhLkcTM106hmqbH_fiWfAytEV-fgdlYOhUwpcd_sGJY
Download Nougat firmware from https://mega.nz/#!608HGYqB!kKTc1196PhimDtVte6OdCWF6aXSWGSNLToEkvUePymE
Steps:
Unpack RSDLite XML to Batch Script to a folder on your computer
Unpack Rogers 24.246-45 firmware to the SAME folder
Run 2-rsd-flash-flashfile-windows.bat
Batch File #2 will convert the flashfile.xml file (included in Rogers zip) to a Batch file
Run flashfile.bat which will flash the Rogers firmware to your device (WILL WIPE EVERYTHING EXCEPT MICRO SD CARD)
Wait till its done!
Your device should now have Rogers 24.246-45 Firmware.
From the Bootloader, select Recovery Mode.
If you see No Command don't panic! That's normal. Press the power button for a couple seconds and press volume up or down (not sure if you need volume buttons but I always do anyway)
Once it displays on screen, Select ADB Sideload
From an adb capable command prompt, enter ADB Sideload <name and location of Nougat.zip> (minus the <> obviously)
This will take time. Leave it alone!
Once complete, simply reboot from recovery and let the device start like normal.
I've tested this process multiple times today and it should work well. Let me know if you have any trouble!
I want to mention I have had NO success backing up with TWRP and restoring after this. Something changed with Nougat and any modification to System causes a soft brick (it did for me anyway). Do not attempt to flash system mode TWRP or flash the TurboZ kernel. They don't work and they will cause a boot loop.
Click to expand...
Click to collapse
I did up until this
From the Bootloader, select Recovery Mode.
If you see No Command don't panic! That's normal. Press the power button for a couple seconds and press volume up or down (not sure if you need volume buttons but I always do anyway)
Once it displays on screen, Select ADB Sideload
From an adb capable command prompt, enter ADB Sideload <name and location of Nougat.zip> (minus the <> obviously)
But when I boot up i have no wifi and I am unable to get the no command to go away to select sideload any ideas?

pieman13 said:
So I get to the point to sideload the nougat update and it always says "can't read..." I've done factory resets and everything else I could think of, still no go for me.
Click to expand...
Click to collapse
Same here, did you find a fix? Tried re-downloading Blur_Version.24.21.46.griffin.retail.en.US.zip and got the same error...

pixelens said:
Same here, did you find a fix? Tried re-downloading Blur_Version.24.21.46.griffin.retail.en.US.zip and got the same error...
Click to expand...
Click to collapse
This happened to me as well. I think it came down to being an ADB Driver issue for me. I reinstalled a different set of ADB drivers and it had no issue after that.

enetec said:
So... are you of the opinion that recovering a Nougat boot+system TWRP backup on a MM phone would cause a soft brick too?
What type of soft brick do you faced exactly?
Click to expand...
Click to collapse
Didn't work for me. As soon as the system partition was mounted R/W My device would boot loop. Could be a symptom of something else but im not sure.

Prfndhatrdofman said:
This happened to me as well. I think it came down to being an ADB Driver issue for me. I reinstalled a different set of ADB drivers and it had no issue after that.
Click to expand...
Click to collapse
Interesting... I'm using the adb drivers from Android Studio.
---------- Post added at 02:27 PM ---------- Previous post was at 02:16 PM ----------
Tried using the ADB drivers from Minimal ADB and Fastboot, same result. Oh well.

pixelens said:
Interesting... I'm using the adb drivers from Android Studio.
---------- Post added at 02:27 PM ---------- Previous post was at 02:16 PM ----------
Tried using the ADB drivers from Minimal ADB and Fastboot, same result. Oh well.
Click to expand...
Click to collapse
Yeah i struggled for about 3 hours trying to get sideload to work. I dunno why but after i completely deleted the driver, rebooted, reinstalled from ADB it finally worked. Its definitely not your device or the image its just ADB being a pain in the ass. I even tried multiple versions of ADB. One guy just tried on a different computer and it worked. I dunno why

Prfndhatrdofman said:
Yeah i struggled for about 3 hours trying to get sideload to work. I dunno why but after i completely deleted the driver, rebooted, reinstalled from ADB it finally worked. Its definitely not your device or the image its just ADB being a pain in the ass. I even tried multiple versions of ADB. One guy just tried on a different computer and it worked. I dunno why
Click to expand...
Click to collapse
Yah, I've had similar experiences in the past - been ages since I've done this though (Samsung Galaxy SII Skyrocket days) so just wanted to make sure I wasn't missing something.
Quick question though, title says "unlocked retail devices" - does that mean the bootloader has to be unlocked? Or will this work with a locked bootloader? Cheers.

pixelens said:
Yah, I've had similar experiences in the past - been ages since I've done this though (Samsung Galaxy SII Skyrocket days) so just wanted to make sure I wasn't missing something.
Quick question though, title says "unlocked retail devices" - does that mean the bootloader has to be unlocked? Or will this work with a locked bootloader? Cheers.
Click to expand...
Click to collapse
I specifically meant network unlocked. Really just any device purchased directly from Motorola.
But yeah i think you might need to have an unlocked bootloader as well.

pixelens said:
Same here, did you find a fix? Tried re-downloading Blur_Version.24.21.46.griffin.retail.en.US.zip and got the same error...
Click to expand...
Click to collapse
Fix was I went back to my pixel and sold the Z.

Mine has unlocked bootloader. Unlocked thru Motorola's website since the first hour I got it

Got the Nougat update to sideload (yay!) - tried a different computer that had no adb drivers installed, used the ones from Minimal ADB and Fastboot and they worked no problem.
Is it possible to lock the bootloader after the Nougat update? I tried and received "(bootloader) still require signed boot.img" message.

pixelens said:
Got the Nougat update to sideload (yay!) - tried a different computer that had no adb drivers installed, used the ones from Minimal ADB and Fastboot and they worked no problem.
Is it possible to lock the bootloader after the Nougat update? I tried and received "(bootloader) still require signed boot.img" message.
Click to expand...
Click to collapse
Dunno. I get the same error.

Thank you for this guide!

Prfndhatrdofman said:
Easy Flash to Nougat Tutorial (Unlocked Retail Devices)
Prerequisites:
Download RSD lite XML to Batch Script from https://www.androidfilehost.com/?fid=24651430732235266
Download ROGERS_MPL24.246-45 from https://mega.nz/#!nssGEDiT!hhLkcTM106hmqbH_fiWfAytEV-fgdlYOhUwpcd_sGJY
Download Nougat firmware from https://mega.nz/#!608HGYqB!kKTc1196PhimDtVte6OdCWF6aXSWGSNLToEkvUePymE
Steps:
Unpack RSDLite XML to Batch Script to a folder on your computer
Unpack Rogers 24.246-45 firmware to the SAME folder
Run 2-rsd-flash-flashfile-windows.bat
Batch File #2 will convert the flashfile.xml file (included in Rogers zip) to a Batch file
Run flashfile.bat which will flash the Rogers firmware to your device (WILL WIPE EVERYTHING EXCEPT MICRO SD CARD)
Wait till its done!
Your device should now have Rogers 24.246-45 Firmware.
From the Bootloader, select Recovery Mode.
If you see No Command don't panic! That's normal. Press the power button for a couple seconds and press volume up or down (not sure if you need volume buttons but I always do anyway)
Once it displays on screen, Select ADB Sideload
From an adb capable command prompt, enter ADB Sideload <name and location of Nougat.zip> (minus the <> obviously)
This will take time. Leave it alone!
Once complete, simply reboot from recovery and let the device start like normal.
I've tested this process multiple times today and it should work well. Let me know if you have any trouble!
I want to mention I have had NO success backing up with TWRP and restoring after this. Something changed with Nougat and any modification to System causes a soft brick (it did for me anyway). Do not attempt to flash system mode TWRP or flash the TurboZ kernel. They don't work and they will cause a boot loop.
Click to expand...
Click to collapse
Hello
I flashed the rogers 45 firmware, but when I go to recovery mode I can't get the ADB menu to appear. I've held power and down, power and up, nothing, etc. Am I missing something? I did the rogers install, then went to homescreen, then powered off.
EDIT
after restarting my phone like 10 times in 5 minutes (rest in peace...) I finally figured it out. Now my issue is that I can't seem to get the sideload to work. I am going to try uninstalling android studio and start again. Did you guys figure out why it says * cannot read ' blur.....' * ?

I found how to fix the adb problem about being unable to read from another thread on XDA
1. Download Large Address Awareness from here https://www.techpowerup.com/forums/threads/large-address-aware.112556/
2. Download ADB from here http://forum.xda-developers.com/showthread.php?t=2588979
3. Start Task Manager and kill adb.exe if its running
4. Load the adb.exe file from Large Address Awareess and check the flag button
5. Continue on with adb sideload
---------- Post added at 09:42 AM ---------- Previous post was at 09:40 AM ----------
Porcelainfog said:
Hello
I flashed the rogers 45 firmware, but when I go to recovery mode I can't get the ADB menu to appear. I've held power and down, power and up, nothing, etc. Am I missing something? I did the rogers install, then went to homescreen, then powered off.
Click to expand...
Click to collapse
Do you see the "No command" picture after choosing Recover Mode? Once you get to that, I hold down power and tap volume up and down again and again

[GUIDE] How to flash a custom recovery and root a Nokia 6 Retail Phone

WARNING: This method currently doesn't work on Nokia 6 TA-1000 with latest Android O Update! Finding workaround.
Workaround found on leaked Android 8.1 Update, with Magisk Systemless Root Method.
ROOT YOUR PHONE MAY VOID YOUR WARRANTY, DO IT AT YOUR OWN RISK
You can download new recovery from this post: https://forum.xda-developers.com/nokia-6/how-to/nokia-6-ta-1000-homebrew-stock-android-t3752006
Changes in new TWRP Recovery 3.2.1-0:
1. Add English Interface.
2. Use Magisk ROOT instead of SuperSU ROOT.
3. You can backup EFS. However you can't backup modem or the procedure will break.
Thanks to @xinkid 's effort, we can finally root Nokia 6 on Android Oreo again.
Procedure for non TA-1000 users:
0. Backup your phone and remove your lock screen password before proceed! If your phone get stuck at "Powered by Android" splash after the procedure, you may need to format userdata.
1. Sideload the PLE-372B ota package in recovery, which you can download from here:
https://forum.xda-developers.com/nokia-6/help/nokia-6-ota-update-ddls-t3721424
Refer this guide's part 2 to downgrade.
https://forum.xda-developers.com/nokia-6/how-to/guide-upgrade-downgrade-nougat-oreo-t3752393
2. Flash the service bootloader and grant service permission
Reboot to bootloader, then flash the service bootloader with following commands. Service bootloader file (D1C-emmc_appsboot.mbn attached in this topic)
Code:
fastboot oem dm-verity [md5_of_your_device_serial_number]
fastboot flash aboot D1C-emmc_appsboot.mbn
fastboot reboot-bootloader
fastboot oem dm-verity [md5_of_your_device_serial_number]
For example, if your serial number is PLEABCD123456789, and the md5 checksum of your serial number is 5f47b9a8dc1da1873c12945cf806691e, then type this command:
Code:
fastboot oem dm-verity 5f47b9a8dc1da1873c12945cf806691e
fastboot flash aboot D1C-emmc_appsboot.mbn
fastboot reboot-bootloader
fastboot oem dm-verity 5f47b9a8dc1da1873c12945cf806691e
You can google a website to calculate md5 checksum of a string.
3. Reflash newer firmware basis to your phone except aboot
After you grant service permission, Extract the newer one OTA package on your PC, in this case, PLE-558B.
Everything you need are placed at firmware-update folder that you extracted.
Take PLE-558B for example, type these commands (commands need to be changed if newer firmware released):
Code:
fastboot flash sbl1 D1C-0-558B-sbl1.mbn
fastboot flash keymaster D1C-0-558B-keymaster.mbn
fastboot flash devcfg D1C-0-558B-devcfg.mbn
fastboot flash cmnlib64 D1C-0-558B-cmnlib64.mbn
fastboot flash rpm D1C-0-558B-rpm.mbn
fastboot flash tz D1C-0-558B-tz.mbn
fastboot flash cmnlib D1C-0-558B-cmnlib.mbn
fastboot flash modem D1C-0-558B-NON-HLOS.bin
fastboot flash dsp D1C-0-558B-adspso.bin
fastboot flash default_nv D1C-0-558B-NV-default.mbn
fastboot flash persist D1C-0-558B-00WW-persist.img
fastboot flash hwcfg D1C-0-558B-hwcfg.img
fastboot flash mdtp D1C-0-558B-00WW-mdtp.img
fastboot flash systeminfo fver
fastboot flash sec D1C-0-558B-sec.dat
fastboot flash cda PLE-00WW-013-cda.img
You'll also need the boot img in the extracted ota package:
fastboot flash boot boot.img
Then flash the custom recovery:
fastboot flash recovery nokia-6-ta-1000-8_0-twrp3.2.1-7to-recovery-magisk-root-2018.3.15.img
Power off your phone (case sensitive). Disconnect your phone after execute this command:
fastboot oem HALT
4. Connect your phone to a charger. When charging animation appears, press and hold Volume Up and Power until you see "7to.com" logo. Tap the white cog to choose English language, tap Advanced - Magisk Root, and wait for the procedure complete.
========================SEPARATOR====================
This new guide is only based and tested on Nokia 6 TA-1000. Non TA-1000 (e.g. TA-1021) users need to find their own old OTA package to downgrade.
1. Downgrade the bootloader according to this guide: https://forum.xda-developers.com/nokia-6/how-to/guide-upgrade-downgrade-nougat-oreo-t3752393
If you've flashed my homebrew Android O firmware, skip this step.
2. Use old method below to flash the new recovery again. You must use this recovery, otherwise you can't mount and root.
If you've flashed my homebrew Android O firmware, type this command will allow you to flash recovery:
Code:
fastboot-android oem dm-verity (your_serial_number's_md5_checksum)
3. Use old method below to enter recovery. To load English interface, tap the white cog on the top-right corner, then tap "English" and OK button, just wait few seconds.
4. Tap "Advanced" - "Magisk ROOT" and swipe.
5. If you meet recovery loop after rooted, flash the package misc_initial.zip attached below to escape from recovery loop.
That's it. It's not recommended to receive any newer OTA update since it will overwrite bootloader to patched state.
If you're using TA-1000, you can also try to flash Android 8.1 Homebrew Firmware before rooting.
I'm sorry if you found the guide looks confusing.
Following method for Nougat is archived, only for reference.
Yesterday, I got my own Nokia 6 Retail Phone. Since I’ve already rooted Nokia 5, 6 and 8 Prototype, now it’s time to find out how to root retail Nokia 6 without involving risky Qualcomm EDL Mode.
It works on any variant of Nokia 6 in theory, but I only tested it on D1C/TA-1000.
If there’s a custom recovery for Nokia 2/3/5 released, the guide also works on them. But I’ve tested it on a Nokia 8 retail phone, it doesn’t work on it.
To Nokia 7 and 8 Users, You may want to read this topic: https://forum.xda-developers.com/showthread.php?t=3729396
Click to expand...
Click to collapse
First, you need to download OFW of Nokia 6, install OST LA and patch it.
You can download them from here: https://forum.xda-developers.com/no...ia-8-official-firmware-links-updated-t3678487
(Although the link is for Nokia 8, firmware for Nokia 6 is still available)
如果你是中国用户，诺6固件的下载和使用方法请看本文：
https://www.ithome.com/html/android/328333.htm
Click to expand...
Click to collapse
If you own an unlocked prototype device, just skip to step 6.
Click to expand...
Click to collapse
1. Open OST LA from INSTALLATION DIRECTORY DIRECTLY instead of Start Menu.
2. Load your OFW you downloaded with extension name nb0.
3. Power off your phone, then connect it to your PC. This will boot your phone to “Download mode” directly, in fact it’s fastboot mode.
4. Click “Edit Phone Info” on OST LA. This will load a service purposed bootloader. When your phone reboots and re-enters the Download mode, the service purposed bootloader is now loaded.
5. You can close OST LA when it prompts “Boot FTM mode fail”, or just kill it in task manager if it’s not responding.
6. Open a command prompt or PowerShell in OST LA Installation Directory, then execute this command to flash a custom recovery:
Code:
.\fastboot-android flash recovery E:\recovery.img
I assume that you put the custom recovery in drive E and named as recovery.img.
You can also use your own fastboot if you want, but I’ll prefer the one provided along with OST LA.
I used the recovery from here: https://forum.xda-developers.com/no...veryteamwim-recovery-project-nokia-6-t3650499
7. Type this command but do not execute right now:
Code:
.\fastboot-android reboot
8. Now this step is a little tricky. Press and hold [Volume Up] and [Power] on your phone, then execute the command above at the same time. DO NOT RELEASE both keys on your phone until your phone entered the custom recovery.
9. Now your phone has entered a custom recovery. In this example, we’re using TWRP from Chinese 7to forum, only Chinese is available. I believe most of members on XDA can’t read Chinese, so I’ll attach screenshots. Simply tap “Advanced” – “SuperSU ROOT” will root your phone. If you prefer your own root zip update package, tap “Install Zip” then flash your own zip package in your storage, or tap “Advanced” – “ADB Sideload” then use ADB to sideload a zip package.
You can install the Materialized Theme for TWRP to get English interface from https://forum.xda-developers.com/android/themes/theme-twrp-materialised-dark-light-play-t2915584 by @z31s1g
Click to expand...
Click to collapse
Currently, DO NOT FLASH Magisk, or your phone will brick as Qualcomm 900E.
You can only use Magisk Root method in latest Android O Update, which I'll cover later.
Click to expand...
Click to collapse
10. After your phone rooted, you can reboot your phone. DO NOT INSTALL ANY OTA UPDATES OR YOUR PHONE WILL GET STUCK AT STOCK RECOVERY, but I’ll recommend you to disable automatic update in settings.
That’s wraps up the whole guide. Please do feedback if there’s something wrong.
Here' the video of how to root a Nokia 6: https://youtu.be/24b-49qTheg
Special thanks:
@blackpanther0582 for Nokia 3/5/6/8 Official Firmware.
@xinkid from Chinese 7to forum for his TWRP.
@hawwin88 for providing info about adding English Interface to recovery.
UPDATE: Uploaded the SuperSU ZIP (verify-xinkid.zip) used in this recovery.

Thank you it worked on nokia6 ta-1000 chinese. I rooted the phone successfully

Finally!
Boy O Boy!
Finally, after a long, long wait, Got my Nokia 6 Rooted! (TA-1000)
Thanks a LOT, Man! :good:

Anyone tried it on any other variant yet?

Hi .i am 1st root my ta1021 with Android 7.1.2 .f**k me
but your method have some problems ...
1. I can't find powershell or anything else in ost la folder.
2.fastboot-android not working....
Now I want complete your method from 6.
6. Before you must install adb and fastboot tools and drivers and use command prompt ,
copy recovery.img to drive c
After ost la changeing phone to edit mod wait 10 second and type this command
Fastboot flash recovery c:\recovery.img
And after flashing completed hold both volume+ and power button and type this command
Fastboot reboot
Don't release buttons and after few seconds you enter Chinese recovery swipe it to right and use screen shots to root your device, after that reboot to system you can find it from screenshot, it go to download mod and then type
Fastboot continue
And enter congratulations, your phone go to normal boot.
Bla bla super su installed....
Thanks, hikari_calyx. For this thread..
Some errors happend when I use rill but after reboot again it is not happening....

same6630 said:
Hi .i am 1st root my ta1021 with Android 7.1.2 .f**k me
but your method have some problems ...
1. I can't find powershell or anything else in ost la folder.
2.fastboot-android not working....
Now I want complete your method from 6.
6. Before you must install adb and fastboot tools and drivers and use command prompt ,
copy recovery.img to drive c
After ost la changeing phone to edit mod wait 10 second and type this command
Fastboot flash recovery c:\recovery.img
And after flashing completed hold both volume+ and power button and type this command
Fastboot reboot
Don't release buttons and after few seconds you enter Chinese recovery swipe it to right and use screen shots to root your device, after that reboot to system you can find it from screenshot, it go to download mod and then type
Fastboot continue
And enter congratulations, your phone go to normal boot.
Bla bla super su installed....
Thanks, hikari_calyx. For this thread..
Some errors happend when I use rill but after reboot again it is not happening....
Click to expand...
Click to collapse
If you're running Windows Vista or Windows 7, you can open a command prompt from installation directory by click right button on the mouse while holding Shift key on the keyboard.
If you're running Windows 8/8.1 or Windows 10, you can open a command prompt or PowerShell from the left corner "File" button. Administrators privilege is optional.
Also, as I mentioned:
You can also use your own fastboot if you want.
Click to expand...
Click to collapse

IDK but you should have change/put the title of this topic as Nokia 6 - TA 1000 (Chinese variant) rather than Retail Phone.
Well, getting root is definitely a temptation but since I'm just a noob and the HMD hasn't release any official firmware/tool yet to recover the phone if thing goes wrong, I guess I'll wait a little bit longer then.

lips_1234 said:
IDK but you should have change/put the title of this topic as Nokia 6 - TA 1000 (Chinese variant) rather than Retail Phone.
Click to expand...
Click to collapse
As I mentioned on the topic, it works on any variant, not only China Variant TA-1000 and Hong Kong Variant TA-1003.
 @same6630 tested on a TA-1021 which is a global variant.
lips_1234 said:
Well, getting root is definitely a temptation but since I'm just a noob and the HMD hasn't release any official firmware/tool yet to recover the phone if thing goes wrong, I guess I'll wait a little bit longer then.
Click to expand...
Click to collapse
HMD released official firmware of Nokia 6 of course, and it's needed to flash a recovery.

Mine
I got some screenshots....

Did someone successfully rooted his Nokia 6 TA-1033?

So just to be clear before I do this to my TA-1000; how do I go about to update it later if I want to update it? For example, my TA-1000 still don't have the 7.1.2 update, and the 8.0 update coming later would be something I want as well.
Do I just update through zip files, or will I simply not be able to update?

Make.Sense said:
So just to be clear before I do this to my TA-1000; how do I go about to update it later if I want to update it? For example, my TA-1000 still don't have the 7.1.2 update, and the 8.0 update coming later would be something I want as well.
Do I just update through zip files, or will I simply not be able to update?
Click to expand...
Click to collapse
After you rooted your phone, you're not able to install any update until you reinstall stock rom.

[THEME][TWRP] TWRP Materialised
U can also install theme for your chinese twrp and you will show english language ...
download theme from this thread
https://forum.xda-developers.com/android/themes/theme-twrp-materialised-dark-light-play-t2915584

hawwin88 said:
U can also install theme for your chinese twrp and you will show english language ...
download theme from this thread
https://forum.xda-developers.com/android/themes/theme-twrp-materialised-dark-light-play-t2915584
Click to expand...
Click to collapse
Thanks for providing info!

When I try to flash the recovery.img through command I have this:
...etc
FAILED (remote. Partition flashing is not allowed)~
finished. ´
etc...
Im using a TA-1033, unlocked UK version.
Can anyone help me, please.

wolfpower95 said:
When I try to flash the recovery.img through command I have this:
...etc
FAILED (remote. Partition flashing is not allowed)~
finished. ´
etc...
Im using a TA-1033, unlocked UK version.
Can anyone help me, please.
Click to expand...
Click to collapse
maybe u are not in bootloader mode .. try to reconnect ur phone again and tap "edit phone" on OST LA software
or try to type this in command :
"fastboot reboot-bootloader"

hawwin88 said:
maybe u are not in bootloader mode .. try to reconnect ur phone again and tap "edit phone" on OST LA software
or try to type this in command :
"fastboot reboot-bootloader"
Click to expand...
Click to collapse
When I connect my TA-0033 it enters in Download mode, when I press "Edit phone", the device continues in download mode and the OST LA software goes unresponsive.
Im using a TA-0033 with 7.1.2 N

done!!!! thank you my good friend!!!! i've just installed the recovery AND ROOT MY TA-1021 with english theme. only a question. without pc what is the best way to reboot in recovery mode nokia 6? when i'ts time to update to oreo, i've only just click to restore in: setting=>backup and restore?? thanksssssss

canapo92 said:
done!!!! thank you my good friend!!!! i've just installed the recovery AND ROOT MY TA-1021 with english theme. only a question. without pc what is the best way to reboot in recovery mode nokia 6? when i'ts time to update to oreo, i've only just click to restore in: setting=>backup and restore?? thanksssssss
Click to expand...
Click to collapse
I recommend you to install Xposed and GravityBox for Nougat to enable Reboot to Recovery option.

hikari_calyx said:
I recommend you to install Xposed and GravityBox for Nougat to enable Reboot to Recovery option.
Click to expand...
Click to collapse
I just got Nokia 6 TA 1021 android 7.1.1, Build is 00WW_3_320. Can your method also work for it?

[DOWNGRADE] Oreo to Nougat

Our devices have been updated to Oreo by HTC, that was a good new since there are many reports and claims from the End Users that was an unstable update, so how to downgrade to a stable Nougat version, here is the way:
[IMPORTANT]
TESTED ON HTC U Ultra DUAL SIM (INDIA - SEA VERSION) and S-ON DEVICE ONLY with UNLOCKED BOOTLOADER, BUT THIS MIGHT WORK ON OTHER VARIANTS
I. PREPARATION
1. HTC Sync Manager for drivers: http://www.htc.com/us/software/htc-sync-manager/
2. ADB and Fastboot, u can use the latest version of Minimal ADB and Fastboot:
https://forum.xda-developers.com/showthread.php?t=2317790 (thanks to @shimp208 for this great tool)
3. Stock Nougat RUU:
https://androidfilehost.com/?a=show&w=files&flid=164315 (thanks to @sardroid for RUUs uploading)
or for the tested device, this RUU has been used:
https://androidfilehost.com/?fid=962187416754465286 (thanks to @minhnewpro for uploading this)
or the latest 1.64.400.10 for Dual SEA - India I have just found
https://vnrom.net/2018/03/rom-stock-ruu-zip-cho-htc-u-ultra-ocean-note/ (original link to support to the RUU publisher)
4. Latest version of TWRP recovery:
https://twrp.me/htc/htcuultra.html (thanks Team Win for this popular and useful TWRP)
5. The most important, HTC Version Tool:
https://drive.google.com/file/d/1ubjDGNqCfIply-aRN8C7IQNb-YVkD4M7/view (thanks to @sabpprook for this super super great tool ^^ )
II. DOWNGRADING TO NOUGAT
1. Install HTC Sync Manager, ADB and Fastboot tool, extract HTC_Version_Tool.exe and copy it and twrp to your adb and fastboot folder
2. If your device's bootloader is unlocked, ignore this, if not
- go to https://www.htcdev.com/
- register for an account and then follow the site's instruction to unlock bootloader
3. Reboot your device into download mode and flash TWRP by opening cmd at your adb and fastboot folder and type:
Code:
fastboot devices
fastboot flash recovery twrp-3.2.1-1-oce.img
4. Boot device into Bootloader mode then boot to TWRP recovery
5. While your phone entered TWRP, open cmd, type:
Code:
adb devices
to check if your device is recognized
6. Once your device is recognized, open HTC_Version_Tool.exe
7. Type the version of the RUU that you are going to flash at new version line, for example, mine is 1.64.400.3 and press enter
8. Rename the RUU file to 2PZCIMG and REMEMBER TO KEEP .zip EXTENSION, then copy it to the root folder of SD Card (External SD Card is recommended)
9. Reboot your device into download mode, press Vol+, then press Power to start flashing 7.0 RUU
10. After flashing, your device can boot into Android but no signal or IMEI received, dont worry, continue these steps
11. Reboot into download mode, reflash TWRP, then boot to TWRP
12. At cmd windows, type
Code:
adb devices
adb shell
mke2fs -t ext4 /dev/block/bootdevice/by-name/persist
13. Reboot device to check if IMEI received
14. If IMEI received, you should reflash stock recovery from RUU.zip, but reflash the RUU is recommended.
If not, try to format the persist partition manually again (step 12)
15. Done
And at last, I want to say big thanks to @sabpprook for helping me a lot to downgrade the device and @paulpier007 for HTC U11 downgrade method which gave me the idea for downgrading our U Ultra (https://forum.xda-developers.com/u11/how-to/guide-downgrade-htc-u11-oreo-to-nougat-t3754481)

#reserved1

#reserved2

Shouldnt be posted in this one mate this custom roms should be q&a
But thanks

panda968 said:
Shouldnt be posted in this one mate this custom roms should be q&a
But thanks
Click to expand...
Click to collapse
Oops sorry for that :| how can i move this topic to Q&A

Its ok mate im not mod
I wish haha
But its ik your helping people dont stress

panda968 said:
Its ok mate im not mod
I wish haha
But its ik your helping people dont stress
Click to expand...
Click to collapse
Yeah I will not make this mistake next time tks for saying me that bro

Dont stress mate
As i said your helping as htc is very confusing with there firmware

panda968 said:
Dont stress mate
As i said your helping as htc is very confusing with there firmware
Click to expand...
Click to collapse
Yeah I got no stress, hope someone who has troubles with Oreo and wants to go back to Nougat will downgrade successfully
Sent from my HTC U Ultra using XDA Labs

lapaho said:
Our devices have been updated to Oreo by HTC, that was a good new since there are many reports and claims from the End Users that was an unstable update, so how to downgrade to a stable Nougat version, here is the way:
[IMPORTANT]
TESTED ON HTC U Ultra DUAL SIM (INDIA - SEA VERSION) and S-ON DEVICE ONLY with UNLOCKED BOOTLOADER, BUT THIS MIGHT WORK ON OTHER VARIANTS
I. PREPARATION
1. HTC Sync Manager for drivers: http://www.htc.com/us/software/htc-sync-manager/
2. ADB and Fastboot, u can use the latest version of Minimal ADB and Fastboot:
https://forum.xda-developers.com/showthread.php?t=2317790 (thanks to @shimp208 for this great tool)
3. Stock Nougat RUU:
https://androidfilehost.com/?a=show&w=files&flid=164315 (thanks to @sardroid for RUUs uploading)
or for the tested device, this RUU has been used:
https://androidfilehost.com/?fid=962187416754465286 (thanks to @minhnewpro for uploading this)
or the latest 1.64.400.10 for Dual SEA - India I have just found
https://vnrom.net/2018/03/rom-stock-ruu-zip-cho-htc-u-ultra-ocean-note/ (original link to support to the RUU publisher)
4. Latest version of TWRP recovery:
https://twrp.me/htc/htcuultra.html (thanks Team Win for this popular and useful TWRP)
5. The most important, HTC Version Tool:
https://drive.google.com/file/d/1ubjDGNqCfIply-aRN8C7IQNb-YVkD4M7/view (thanks to @sabpprook for this super super great tool ^^ )
II. DOWNGRADING TO NOUGAT
1. Install HTC Sync Manager, ADB and Fastboot tool, extract HTC_Version_Tool.exe and copy it and twrp to your adb and fastboot folder
2. If your device's bootloader is unlocked, ignore this, if not
- go to https://www.htcdev.com/
- register for an account and then follow the site's instruction to unlock bootloader
3. Reboot your device into download mode and flash TWRP by opening cmd at your adb and fastboot folder and type:
Code:
fastboot devices
fastboot flash recovery twrp-3.2.1-1-oce.img
4. Boot device into Bootloader mode then boot to TWRP recovery
5. While your phone entered TWRP, open cmd, type:
Code:
adb devices
to check if your device is recognized
6. Once your device is recognized, open HTC_Version_Tool.exe
7. Type the version of the RUU that you are going to flash at new version line, for example, mine is 1.64.400.3 and press enter
8. Rename the RUU file to 2PZCIMG and REMEMBER TO KEEP .zip EXTENSION, then copy it to the root folder of SD Card (External SD Card is recommended)
9. Reboot your device into download mode, press Vol+, then press Power to start flashing 7.0 RUU
10. After flashing, your device can boot into Android but no signal or IMEI received, dont worry, continue these steps
11. Reboot into download mode, reflash TWRP, then boot to TWRP
12. At cmd windows, type
Code:
adb devices
adb shell
mke2fs -t ext4 /dev/block/bootdevice/by-name/persist
13. Reboot device to check if IMEI received
14. If IMEI received, you should reflash stock recovery from RUU.zip, but reflash the RUU is recommended.
If not, try to format the persist partition manually again
15. Done
And at last, I want to say big thanks to @sabpprook for helping me a lot to downgrade the device and @paulpier007 for HTC U11 downgrade method which gave me the idea for downgrading our U Ultra (https://forum.xda-developers.com/u11/how-to/guide-downgrade-htc-u11-oreo-to-nougat-t3754481)
Click to expand...
Click to collapse
Excellent guide .... this method is sure to go back without problems and does not need to be in S-OFF.

paulpier007 said:
Our devices have been updated to Oreo by HTC, that was a good new since there are many reports and claims from the End Users that was an unstable update, so how to downgrade to a stable Nougat version, here is the way:
[IMPORTANT]
TESTED ON HTC U Ultra DUAL SIM (INDIA - SEA VERSION) and S-ON DEVICE ONLY with UNLOCKED BOOTLOADER, BUT THIS MIGHT WORK ON OTHER VARIANTS
I. PREPARATION
1. HTC Sync Manager for drivers: http://www.htc.com/us/software/htc-sync-manager/
2. ADB and Fastboot, u can use the latest version of Minimal ADB and Fastboot:
https://forum.xda-developers.com/showthread.php?t=2317790 (thanks to @shimp208 for this great tool)
3. Stock Nougat RUU:
https://androidfilehost.com/?a=show&w=files&flid=164315 (thanks to @sardroid for RUUs uploading)
or for the tested device, this RUU has been used:
https://androidfilehost.com/?fid=962187416754465286 (thanks to @minhnewpro for uploading this)
or the latest 1.64.400.10 for Dual SEA - India I have just found
https://vnrom.net/2018/03/rom-stock-ruu-zip-cho-htc-u-ultra-ocean-note/ (original link to support to the RUU publisher)
4. Latest version of TWRP recovery:
https://twrp.me/htc/htcuultra.html (thanks Team Win for this popular and useful TWRP)
5. The most important, HTC Version Tool:
https://drive.google.com/file/d/1ubjDGNqCfIply-aRN8C7IQNb-YVkD4M7/view (thanks to @sabpprook for this super super great tool ^^ )
II. DOWNGRADING TO NOUGAT
1. Install HTC Sync Manager, ADB and Fastboot tool, extract HTC_Version_Tool.exe and copy it and twrp to your adb and fastboot folder
2. If your device's bootloader is unlocked, ignore this, if not
- go to https://www.htcdev.com/
- register for an account and then follow the site's instruction to unlock bootloader
3. Reboot your device into download mode and flash TWRP by opening cmd at your adb and fastboot folder and type:
4. Boot device into Bootloader mode then boot to TWRP recovery
5. While your phone entered TWRP, open cmd, type:
to check if your device is recognized
6. Once your device is recognized, open HTC_Version_Tool.exe
7. Type the version of the RUU that you are going to flash at new version line, for example, mine is 1.64.400.3 and press enter
8. Rename the RUU file to 2PZCIMG and REMEMBER TO KEEP .zip EXTENSION, then copy it to the root folder of SD Card (External SD Card is recommended)
9. Reboot your device into download mode, press Vol+, then press Power to start flashing 7.0 RUU
10. After flashing, your device can boot into Android but no signal or IMEI received, dont worry, continue these steps
11. Reboot into download mode, reflash TWRP, then boot to TWRP
12. At cmd windows, type
Excellent guide .... this method is sure to go back without problems and does not need to be in S-OFF.
Click to expand...
Click to collapse
That got something as same as the method with U11 that u have posted
Sent from my HTC U Ultra using XDA Labs

where can i get ruu for oreo

waseem.gani said:
where can i get ruu for oreo
Click to expand...
Click to collapse
We are searching for it but still no results

lapaho said:
That got something as same as the method with U11 that u have posted
Sent from my HTC U Ultra using XDA Labs
Click to expand...
Click to collapse
The procedure is almost identical to that of HTC U11 with the exception of the recovery of the IMEI code that forces you to make an extra step ...

paulpier007 said:
The procedure is almost identical to that of HTC U11 with the exception of the recovery of the IMEI code that forces you to make an extra step ...
Click to expand...
Click to collapse
Yes, because U Ultra won't re-build persist partition while rebooting after wipe it, therefore we need format it manually

lapaho said:
Yeah I got no stress, hope someone who has troubles with Oreo and wants to go back to Nougat will downgrade successfully
Sent from my HTC U Ultra using XDA Labs
Click to expand...
Click to collapse
You helped me.
Been a lurker for years. You made me sign back into my account just so I can personally say thank you for posting this. I've been trying to many different things to no avail. I'm finally back on 7.0.
Thank you for sharing your knowledge. Best wishes to you pal.

LogisticsXLS said:
You helped me.
Been a lurker for years. You made me sign back into my account just so I can personally say thank you for posting this. I've been trying to many different things to no avail. I'm finally back on 7.0.
Thank you for sharing your knowledge. Best wishes to you pal.
Click to expand...
Click to collapse
I'm happy to hear that from u and don't forget to thanks @sabpprook, he has helped us a lot to downgrade our U Ultra

Hello,
I cannot downgrade. I always get the following errors when it says press VolUp to start flash and Start ui_updating:
22 RU_HEADER_ERROR
22 RU_HEADER_ERROR
FAIL22 RU_HEADER_ERROR
I already tried to flash with two different RUUs.

LogisticsXLS said:
You helped me.
Been a lurker for years. You made me sign back into my account just so I can personally say thank you for posting this. I've been trying to many different things to no avail. I'm finally back on 7.0.
Thank you for sharing your knowledge. Best wishes to you pal.
Click to expand...
Click to collapse
vinczetibor said:
Hello,
I cannot downgrade. I always get the following errors when it says press VolUp to start flash and Start ui_updating:
22 RU_HEADER_ERROR
22 RU_HEADER_ERROR
FAIL22 RU_HEADER_ERROR
I already tried to flash with two different RUUs.
Click to expand...
Click to collapse
What is your variant ?

India (CID 60) dualsim and 2.19.400.1 firmware on my phone. Unlocked bootloader, S-On.

(guide) root nokia 3 android 9.0

Download all the files and unzip the platform-tools folder and move apk and boot to the phone memory
first we have to download magisk apk .. install and open
then we will install magisk, a window will open and we will install it and it will ask us to patch a boot image
we look for the boot image that we download ... then we click on it and the boot image will be patched ...
the patched image of awaits in in download in internal storage ..
we go to the computer and move the patched image to the desktop ..
we go to the platform-tools folder and open it and give alt and right click in an empty space and open the powershell or cmd window .. once it starts in the command window we will give it a series of commands
first: we have to activate the cell phone's usb debug and connect to the computer
in the command window we put:
cmd
adb devices (we have to detect the device)
adb reboot bootloader (or start bootloader manually)
fasboot devices (we have to detect the cell phone)
fastboot flash boot (and we move the patched image in the command window next to the last command or this one)
we give space and we give enter and the image will be installed and we give ..
fastboot reboot
and ready you have root just open magisk and it is already installed https://drive.google.com/drive/folders/1UjyAzSZeMUBIwSTvlNo1CFL7BO3dMLPW?usp=sharing

https://drive.google.com/open?id=1HtjdNjdJ3XiSaOAUNVwZ8E-tGv3xr2Ly
https://drive.google.com/open?id=1eFpvFeUe_xLRUFnBbT2ZzKdTgX8-nyYQ

I will try it and see that it breaks this time

Marakas89 said:
Download all the files and unzip the platform-tools folder and move apk and boot to the phone memory
first we have to download magisk apk .. install and open
then we will install magisk, a window will open and we will install it and it will ask us to patch a boot image
we look for the boot image that we download ... then we click on it and the boot image will be patched ...
the patched image of awaits in in download in internal storage ..
we go to the computer and move the patched image to the desktop ..
we go to the platform-tools folder and open it and give alt and right click in an empty space and open the powershell or cmd window .. once it starts in the command window we will give it a series of commands
first: we have to activate the cell phone's usb debug and connect to the computer
in the command window we put:
cmd
adb devices (we have to detect the device)
adb reboot bootloader (or start bootloader manually)
fasboot devices (we have to detect the cell phone)
fastboot flash boot (and we move the patched image in the command window next to the last command or this one)
we give space and we give enter and the image will be installed and we give ..
fastboot reboot
and ready you have root just open magisk and it is already installed https://drive.google.com/drive/folders/1UjyAzSZeMUBIwSTvlNo1CFL7BO3dMLPW?usp=sharing
Click to expand...
Click to collapse
Thanks for share
work fine in me

wirdan.hungkul said:
Thanks for share
work fine in me
Click to expand...
Click to collapse
by chance you don't have the ota? (zip), the last update available that I have is a security patch for 8.1
:c

djxpro said:
by chance you don't have the ota? (zip), the last update available that I have is a security patch for 8.1
:c
Click to expand...
Click to collapse
I don't have Ota update ..., you should re-flash your device

wirdan.hungkul said:
I don't have Ota update ..., you should re-flash your device
Click to expand...
Click to collapse
Well, remember something: I guess for it to work, the bootloader must be disabled, right?
:c

djxpro said:
Well, remember something: I guess for it to work, the bootloader must be disabled, right?
:c
Click to expand...
Click to collapse
bootloader must be activated ..

wirdan.hungkul said:
bootloader must be activated ..
Click to expand...
Click to collapse
I tried it with 8.1 files
and cmd show me a device locked error
It may be by the method in the wrong version.

djxpro said:
I tried it with 8.1 files
and cmd show me a device locked error
It may be by the method in the wrong version.
Click to expand...
Click to collapse
try this https://forum.xda-developers.com/nokia-3/how-to/guide-how-to-unlock-bootloader-nokia-3-t3699344
if an error still occurs
try flash it https://forum.xda-developers.com/nokia-3/how-to/nokia-3-ta-1032-official-firmware-sp-t3744634
and if after Flash Dead And Vibrate only
https://www.youtube.com/watch?v=zW6srLB5fBM

wirdan.hungkul said:
try this https://forum.xda-developers.com/nokia-3/how-to/guide-how-to-unlock-bootloader-nokia-3-t3699344
if an error still occurs
try flash it https://forum.xda-developers.com/nokia-3/how-to/nokia-3-ta-1032-official-firmware-sp-t3744634
and if after Flash Dead And Vibrate only
https://www.youtube.com/watch?v=zW6srLB5fBM
Click to expand...
Click to collapse
I tried the first thing and it throws me another different mistake.
something like unknown command.
or something concerning the communication with the device
and the other link is a 7.1 rom, right?
my device is the ta 1028...
technically it is the same

djxpro said:
I tried the first thing and it throws me another different mistake.
something like unknown command.
or something concerning the communication with the device
and the other link is a 7.1 rom, right?
my device is the ta 1028...
technically it is the same
Click to expand...
Click to collapse
is it already installed mtk driver?
https://androidmtk.com/download-mtk-driver-auto-installer
or
https://androidmtk.com/download-mtk-usb-all-drivers
yes, anothet link 7.0 and 7.1 rom...
or you can try https://forum.xda-developers.com/nokia-3/how-to/nokia-3-official-firmware-india-uae-t3674320
Firmware supported for below Nokia 3 Supported Models
- NOKIA 3 TA-1032 DS
- NOKIA 3 TA-1020 SS
- NOKIA 3 TA-1028 SS
- NOKIA 3 TA-1038 DS

Apparently it is an issue of the operator that I do not have the update yet.
I went back to 8.0 while I find out what happened to the ota.
And if it comes out I'll capture it.

wirdan.hungkul said:
is it already installed mtk driver?
https://androidmtk.com/download-mtk-driver-auto-installer
or
https://androidmtk.com/download-mtk-usb-all-drivers
yes, anothet link 7.0 and 7.1 rom...
or you can try https://forum.xda-developers.com/nokia-3/how-to/nokia-3-official-firmware-india-uae-t3674320
Firmware supported for below Nokia 3 Supported Models
- NOKIA 3 TA-1032 DS
- NOKIA 3 TA-1020 SS
- NOKIA 3 TA-1028 SS
- NOKIA 3 TA-1038 DS
Click to expand...
Click to collapse
well, finally, i have android 9.
but, i cant flash the patched boot
:c failed: unknown command

Well, I managed to root.
I got the OTA in a Russian forum.
After a couple of failed attempts, I managed to figure out how to mount the OTA.
Then, not working or rooting, and realize that the bootloader was not unlocked, I repeated all the steps.
I noticed that I am subnormal, and that the code I was using to unlock was not correct (several months to realize this).
Anyway, go down to 7.1, unlock the bootloader, flash to 8.1 (4.42) (orange state up)
I mounted OTA 5.20 through recovery
I did the steps in the post, and finally I have Pie with root
Orange State continues, but I will not block the bootloader again

djxpro said:
Well, I managed to root.
I got the OTA in a Russian forum.
After a couple of failed attempts, I managed to figure out how to mount the OTA.
Then, not working or rooting, and realize that the bootloader was not unlocked, I repeated all the steps.
I noticed that I am subnormal, and that the code I was using to unlock was not correct (several months to realize this).
Anyway, go down to 7.1, unlock the bootloader, flash to 8.1 (4.42) (orange state up)
I mounted OTA 5.20 thrgough recovery
I did the steps in the post, and finally I have Pie with root
Orange State continues, but I will not block the bootloader again
Click to expand...
Click to collapse
:good:

Well.....i thought let me give it a try.....but.....problem started then...
--- adb works fine.....both the commands (adb devices and adb reboot bootloader) gets executed
--- but my device doesn't get detected in fastboot mode
--- thinking that its problem with drivers...i tried every driver (adb and fastboot) out in the internet and nokia drivers...but got no luck
--- hoping that someone could help me i posted here.... thanks in advance

djxpro said:
well, finally, i have android 9.
but, i cant flash the patched boot
:c failed: unknown command
Click to expand...
Click to collapse
i found a way to flash the patched boot and unlock the bootloader on pie
Here

NulledRoot said:
i found a way to flash the patched boot and unlock the bootloader on pie
Here
Click to expand...
Click to collapse
actually, i have a rooted phone.
but, i lock the bootloader again, and now, i need connect to usb to start up
without usb, i give a red state
.-.)

my phone stuck at reboot loop can someone help me?

Cannot flash RN7Pro

Hi
I can't flash my redmi note 7 pro.
Bootloader is unlocked: I did the procedure, there is the unlocked logo at boot, and Dev options says "OEM unlock: device already unlocked".
I tried the Pixel Experience way, I ran the command "fastboot flash recovery" under Windows (opens a shell window that immediately closes) and under Linux (nothing happens), and I also tried the Xiaomi flash tool which ends up with a "cannot find the file flash all bat".
Would someone have any idea?
Thanks!!

pata2000 said:
Hi
I can't flash my redmi note 7 pro.
Bootloader is unlocked: I did the procedure, there is the unlocked logo at boot, and Dev options says "OEM unlock: device already unlocked".
I tried the Pixel Experience way, I ran the command "fastboot flash recovery" under Windows (opens a shell window that immediately closes) and under Linux (nothing happens), and I also tried the Xiaomi flash tool which ends up with a "cannot find the file flash all bat".
Would someone have any idea?
Thanks!!
Click to expand...
Click to collapse
Hello,
download platform-tools (ADB) zip and extract it.
download fastboot rom and extract it.
1) copy all the files from "violet_in_global_images_V11.0.5.0.PFHINXM_20191022.0000.00_9.0_in" (Total 12 items) folder into extracted platform tools folder.
2) boot device in Fastboot mode and connect it to pc.
3) now open cmd and check if device is detected by pc.
(use following command -> fastboot devices)
4) now close cmd.
5) now go to platform tools folder and double click on "flash_all.bat" file.
6) it will flash ur device with MIUI. DONE.

rasik107 said:
Hello,
download platform-tools (ADB) zip and extract it.
download fastboot rom and extract it.
1) copy all the files from "violet_in_global_images_V11.0.5.0.PFHINXM_20191022.0000.00_9.0_in" (Total 12 items) folder into extracted platform tools folder.
2) boot device in Fastboot mode and connect it to pc.
3) now open cmd and check if device is detected by pc.
(use following command -> fastboot devices)
4) now close cmd.
5) now go to platform tools folder and double click on "flash_all.bat" file.
6) it will flash ur device with MIUI. DONE.
Click to expand...
Click to collapse
Thanks a lot for your reply. I'll try that as soon as I have some time.
Just another question:
I am running MIUI Global 11.0.4.0 | Stable (PFGMIXM) at the moment. Which is not the same as you indicated (I believe yours is Indian version dated 22 Oct 2019).
This page does not include any Global rom: https://xiaomifirmwareupdater.com/archive/firmware/violet/
And the Global ROM available on MIUI website under the RN7Pro page (https://c.mi.com//miuidownload/detail?device=1700360) is noted "lavender" and not "violet" - and I do not want to risk installing the wrong firmware, I've read a few topics and it does not ends well.
So bottom line: which one should I work with?
thanks again!

pata2000 said:
Thanks a lot for your reply. I'll try that as soon as I have some time.
Just another question:
I am running MIUI Global 11.0.4.0 | Stable (PFGMIXM) at the moment. Which is not the same as you indicated (I believe yours is Indian version dated 22 Oct 2019).
This page does not include any Global rom: https://xiaomifirmwareupdater.com/archive/firmware/violet/
And the Global ROM available on MIUI website under the RN7Pro page (https://c.mi.com//miuidownload/detail?device=1700360) is noted "lavender" and not "violet" - and I do not want to risk installing the wrong firmware, I've read a few topics and it does not ends well.
So bottom line: which one should I work with?
thanks again!
Click to expand...
Click to collapse
No need to flash Firmware.
just download fastboot rom of your region and u r good to go.

rasik107 said:
No need to flash Firmware.
just download fastboot rom of your region and u r good to go.
Click to expand...
Click to collapse
OK, I've found 2 options:
This one here on XDA:
https://forum.xda-developers.com/redmi-note-7-pro/how-to/miui-11-public-beta-violet-t3973921
(dowloading the "Fastboot ROM V11.0.6.0")
But it is 11.0.6.0 while my phone is under 11.0.4.0: is this a problem?
This other one:
Note 7 Europe V11.0.4.0.PFGEUXM at: https://www.leakite.com/xiaomi-redmi-note-7-pro-firmware-fastboot-recovery-rom/
It's not exactly the same code (PFGEUXM instead of PFGMIXM), I don't know if it makes any difference?
Sorry for keeping asking question, but I'd better be safe since I am very new to this kind of things...
and thanks a lot for your help and patience.

pata2000 said:
OK, I've found 2 options:
This one here on XDA:
https://forum.xda-developers.com/redmi-note-7-pro/how-to/miui-11-public-beta-violet-t3973921
(dowloading the "Fastboot ROM V11.0.6.0")
But it is 11.0.6.0 while my phone is under 11.0.4.0: is this a problem?
This other one:
Note 7 Europe V11.0.4.0.PFGEUXM at: https://www.leakite.com/xiaomi-redmi-note-7-pro-firmware-fastboot-recovery-rom/
It's not exactly the same code (PFGEUXM instead of PFGMIXM), I don't know if it makes any difference?
Sorry for keeping asking question, but I'd better be safe since I am very new to this kind of things...
and thanks a lot for your help and patience.
Click to expand...
Click to collapse
https://forum.xda-developers.com/redmi-note-7-pro/how-to/miui-11-public-beta-violet-t3973921
this one looks fine.
but make sure it is a fastboot file (.tgz) :good:

rasik107 said:
https://forum.xda-developers.com/redmi-note-7-pro/how-to/miui-11-public-beta-violet-t3973921
this one looks fine.
but make sure it is a fastboot file (.tgz) :good:
Click to expand...
Click to collapse
HI again
it still won't flash no matter what.
I'll deal with it
the reason I wanted to flash was essentially to remove all non necessarry stuff, which I did by following the "remove bloatware" thread.
thanks anyway

pata2000 said:
HI again
it still won't flash no matter what.
I'll deal with it
the reason I wanted to flash was essentially to remove all non necessarry stuff, which I did by following the "remove bloatware" thread.
thanks anyway
Click to expand...
Click to collapse
flash aosp recovery, then adb sideload PE rom

Srikanth0721 said:
flash aosp recovery, then adb sideload PE rom
Click to expand...
Click to collapse
Thanks!
Based on PE instructions (https://telegra.ph/Flashing-PE-for-the-first-time-using-the-AOSP-Recovery--Or-updating-12-06) and if I understand properly:
- I download the firmware and Aosp recovery
- I enter in fastboot and connect the phone to PC, then I type fastboot flash recovery.img (in folder Download+Recovery)
- Then reboot into the new recovery
- Then Tap the power + vol up(2 times vol up) together once or twice and the AOSP recovery menu will pop up
- I then type adb sideload NameofthePErom.zip
- Then: Use the volume keys to select Factory Reset and confirm. ( If you want to format data if not just ignore this part )
- Reboot!
Am I correct?
I'll give it a try even though I don't understand why flashing aosp would work when flashing other stuff didn't... But who knows!
Will let you guys know anyway.

pata2000 said:
Thanks!
Based on PE instructions (https://telegra.ph/Flashing-PE-for-the-first-time-using-the-AOSP-Recovery--Or-updating-12-06) and if I understand properly:
- I download the firmware and Aosp recovery
- I enter in fastboot and connect the phone to PC, then I type fastboot flash recovery.img (in folder Download+Recovery)
- Then reboot into the new recovery
- Then Tap the power + vol up(2 times vol up) together once or twice and the AOSP recovery menu will pop up
- I then type adb sideload NameofthePErom.zip
- Then: Use the volume keys to select Factory Reset and confirm. ( If you want to format data if not just ignore this part )
- Reboot!
Am I correct?
I'll give it a try even though I don't understand why flashing aosp would work when flashing other stuff didn't... But who knows!
Will let you guys know anyway.
Click to expand...
Click to collapse
Also check the recovery in the extracted folder, I got a twrp recovery so I guess I have facee issues with flashme.bat (immediate close).
If u face that issue, download aosp recovery separately or from their telegram channel and flash using fastboot cmd and do the rest..

Srikanth0721 said:
Also check the recovery in the extracted folder, I got a twrp recovery so I guess I have facee issues with flashme.bat (immediate close).
If u face that issue, download aosp recovery separately or from their telegram channel and flash using fastboot cmd and do the rest..
Click to expand...
Click to collapse
well it would not work either. that is not a problem though, I'll survive with the MIUI rom!
thanks