Sharing this guide seems quite late but since xda red magic threads taught me a lot about the rooting and corrupted stuffs, I think it would not hurt to return something back to this community.
This is my attempt to compile people's responses that helped other people here which are scattered around forums.
Myself included also tinkered a lot on this device and literally go back here on this guide to lessen headaches.
EDIT: Tested a lot of times with V5.08 and V5.09 Android R versions
REMINDER: Tested on Android 9, no clues yet on Android 10 and 11
WHEN TO USE?
Use this guide to restore your phone to boot in Android OS again normally without wiping data, retaining your apps, games intact
Requirements:
- Windows computer. NOTE: Done this using Windows 10, so I'm not exactly sure if latest ADB works the same on Windows 7.
- Nubia Red Magic 3 or 3S battery charge should be at 50% above at least.
- You need a USB cable to connect your phone to PC. XDA Users reported better with USB 2.0 port
NOTE: Can be used also on 3S. I just don't have 3S so I haven't tested it on actual 3S.
Download latest the ADB (Android Debug Bridge) from Android Developers site.
1.) Go to https://developer.android.com/studio/releases/platform-tools
2.) Click Download SDK Platform-Tools for Windows.
3.) Click the checkbox beside 'I have read and agree with the above terms and conditions'
and click DOWNLOAD ANDROID SDK PLATFORM-TOOLS FOR WINDOWS
*Current version as of December 12, 2020
platform-tools_r30.0.5-windows.zip
4.) Create a folder in C:\ Drive and name it ADB. Extract platform-tools_rxx.x.x-windows.zip inside ADB folder.
*NOTE: rxx.x.x on platform-tools_rxx.x.x-windows depends on the current version available on Android Developers site.
5.) On your Windows desktop, press the Window logo button on your keyboard, type 'cmd'. Right-click on Command Prompt and click Run as administrator.
7.) On command prompt, type 'cd c:\ADB' and press Enter. *type without quotes *DO NOT CLOSE Command prompt!
8.) Connect your Nubia Red Magic 3 or 3S to a USB 2.0 port.
9.) Wait for Windows to install drivers of your phone. If a CD Drive showed up on "This PC / My Computer", double-click on it and install the driver.
10.) Type 'adb reboot bootloader' and press Enter. *type without quotes
11.) Go back to your command prompt. Type 'fastboot devices'. It should show your phone's serial number and a 'fastboot' word. This means your PC can properly communicate with your Nubia Red Magic 3. *DO NOT CLOSE Command prompt!
12.) Get your ROM ready. Download from these official links if you haven't already.
IMPORTANT: Try to remember the specific version of ROM your Red Magic has.
Because for example if the currently installed is Android 11 (R) but you used the lower version say Android 10 or 9, flashing will proceed but it will not boot to Android OS
For Global, Europe and North America versions:
REDMAGIC 3 Global ROM flash instructions - REDMAGIC (Global)
Want to flash your REDMAGIC device? Here's how. NOTE: Please proceed with caution.
global.redmagic.gg
Chinese version:
Nubia Red Magic 3
http://ui.nubia.cn/rom/detail/62
Nubia Red Magic 3S
http://ui.nubia.cn/rom/detail/64
13.) Extract the zip file to any folder you want. Get inside it and copy the following:
* parameter.img
* boot.img
* recovery.img
* splash.img
* dtbo.img
* vbmeta.img
* NON-HLOS.bin
* dspso.bin
14.) Continuing from the step above, paste the files you copied to ADB folder you created from step 4.
15.) Go back to your command prompt. And type and press Enter the below commands one by one:
fastboot oem nubia_unlock NUBIA_NX629J
fastboot erase parameter
fastboot flash parameter parameter.img
fastboot erase boot
fastboot flash boot boot.img
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot erase splash
fastboot flash splash splash.img
fastboot erase dtbo
fastboot flash dtbo dtbo.img
fastboot erase vbmeta
fastboot flash vbmeta vbmeta.img
fastboot erase modem
fastboot flash modem NON-HLOS.bin
fastboot erase dsp
fastboot flash dsp dspso.bin
Recommended read:
Why erase is important: https://android.stackexchange.com/questions/161103/what-fastboot-erase-actually-does#161115
*Disconnect the USB-C cable from your NRM3/3S
16.) Your phone still on fastboot, press volume down to choose "Reboot to recovery mode" and press power button to confirm.
17.) Your phone should boot to recovery. On the recovery Main Menu, press volume down to choose 'Wipe Data', choose Wipe cache and also User partition.
18.) After the wipe is successful, copy the ROM zip file to your USB flash drive. Insert your USB Flash drive to your OTG USB-C adapter. Then finally insert it to your Nubia Red Magic 3/3S USB-C port.
19.) Your phone still on recovery, select "Choose Update Package" and specify the ROM zip file in your USB OTG device.
20.) Wait for the system installation to finish.
Alternatively, you can view the guide's pastebin. Plain and simple layout especially when you are just using data on your phone
Solution for Nubia Red Magic 3 / 3S "device is corrupt"
leipnacht said:
Sharing this guide seems quite late but since xda red magic threads taught me a lot about the rooting and corrupted stuffs, I think it would not hurt to return something back to this community.
This is my attempt to compile people's responses that helped other people here which are scattered around forums.
Myself included also tinkered a lot on this device and literally go back here on this guide to lessen headaches.
REMINDER: Tested on Android 9, no clues yet on Android 10 and 11
WHEN TO USE?
Use this guide to restore your phone to boot in Android 9 again normally without wiping data, retaining your apps, games intact
Requirements:
- Windows computer. NOTE: Done this using Windows 10, so I'm not exactly sure if latest ADB works the same on Windows 7.
- Nubia Red Magic 3 or 3S battery charge should be at 50% above at least.
- You need a USB cable to connect your phone to PC. XDA Users reported better with USB 2.0 port
NOTE: Can be used also on 3S. I just don't have 3S so I haven't tested it on actual 3S.
Download latest the ADB (Android Debug Bridge) from Android Developers site.
1.) Go to https://developer.android.com/studio/releases/platform-tools
2.) Click Download SDK Platform-Tools for Windows.
3.) Click the checkbox beside 'I have read and agree with the above terms and conditions'
and click DOWNLOAD ANDROID SDK PLATFORM-TOOLS FOR WINDOWS
*Current version as of December 12, 2020
platform-tools_r30.0.5-windows.zip
4.) Create a folder in C:\ Drive and name it ADB. Extract platform-tools_rxx.x.x-windows.zip inside ADB folder.
*NOTE: rxx.x.x on platform-tools_rxx.x.x-windows depends on the current version available on Android Developers site.
5.) On your Windows desktop, press the Window logo button on your keyboard, type 'cmd'. Right-click on Command Prompt and click Run as administrator.
7.) On command prompt, type 'cd c:\ADB' and press Enter. *type without quotes *DO NOT CLOSE Command prompt!
8.) Connect your Nubia Red Magic 3 or 3S to a USB 2.0 port.
9.) Wait for Windows to install drivers of your phone. If a CD Drive showed up on "This PC / My Computer", double-click on it and install the driver.
10.) Type 'adb reboot bootloader' and press Enter. *type without quotes
11.) Go back to your command prompt. Type 'fastboot devices'. It should show your phone's serial number and a 'fastboot' word. This means your PC can properly communicate with your Nubia Red Magic 3. *DO NOT CLOSE Command prompt!
12.) Get your ROM ready. Download from these official links if you haven't already.
For Global, Europe and North America versions:
REDMAGIC 3 Global ROM flash instructions - REDMAGIC (Global)
Want to flash your REDMAGIC device? Here's how. NOTE: Please proceed with caution.
global.redmagic.gg
Chinese version:
Nubia Red Magic 3
http://ui.nubia.cn/rom/detail/62
Nubia Red Magic 3S
http://ui.nubia.cn/rom/detail/64
13.) Extract the zip file to any folder you want. Get inside it and copy the following:
* parameter.img
* boot.img
* recovery.img
* splash.img
* dtbo.img
* vbmeta.img
* NON-HLOS.bin
* dspso.bin
14.) Continuing from the step above, paste the files you copied to ADB folder you created from step 4.
15.) Go back to your command prompt. And type and press Enter the below commands one by one:
fastboot oem nubia_unlock NUBIA_NX629J
fastboot erase parameter
fastboot flash parameter parameter.img
fastboot erase boot
fastboot flash boot boot.img
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot erase splash
fastboot flash splash splash.img
fastboot erase dtbo
fastboot flash dtbo dtbo.img
fastboot erase vbmeta
fastboot flash vbmeta vbmeta.img
fastboot erase modem
fastboot flash modem NON-HLOS.bin
fastboot erase dsp
fastboot flash dsp dspso.bin
Recommended read:
Why erase is important: https://android.stackexchange.com/questions/161103/what-fastboot-erase-actually-does#161115
*Disconnect the USB-C cable from your NRM3/3S
16.) Your phone still on fastboot, press volume down to choose "Reboot to recovery mode" and press power button to confirm.
17.) Your phone should boot to recovery. On the recovery Main Menu, press volume down to choose 'Wipe Data', choose Wipe cache and also User partition.
18.) After the wipe is successful, copy the ROM zip file to your USB flash drive. Insert your USB Flash drive to your OTG USB-C adapter. Then finally insert it to your Nubia Red Magic 3/3S USB-C port.
19.) Your phone still on recovery, select "Choose Update Package" and specify the ROM zip file in your USB OTG device.
20.) Wait for the system installation to finish.
Alternatively, you can view the guide's pastebin. Plain and simple layout especially when you are just using data on your phone
Solution for Nubia Red Magic 3 / 3S "device is corrupt"
Click to expand...
Click to collapse
Looks like you've been using another cell
leipnacht said:
Sharing this guide seems quite late but since xda red magic threads taught me a lot about the rooting and corrupted stuffs, I think it would not hurt to return something back to this community.
This is my attempt to compile people's responses that helped other people here which are scattered around forums.
Myself included also tinkered a lot on this device and literally go back here on this guide to lessen headaches.
EDIT: Tested a lot of times with V5.08 and V5.09 Android R versions
REMINDER: Tested on Android 9, no clues yet on Android 10 and 11
WHEN TO USE?
Use this guide to restore your phone to boot in Android OS again normally without wiping data, retaining your apps, games intact
Requirements:
- Windows computer. NOTE: Done this using Windows 10, so I'm not exactly sure if latest ADB works the same on Windows 7.
- Nubia Red Magic 3 or 3S battery charge should be at 50% above at least.
- You need a USB cable to connect your phone to PC. XDA Users reported better with USB 2.0 port
NOTE: Can be used also on 3S. I just don't have 3S so I haven't tested it on actual 3S.
Download latest the ADB (Android Debug Bridge) from Android Developers site.
1.) Go to https://developer.android.com/studio/releases/platform-tools
2.) Click Download SDK Platform-Tools for Windows.
3.) Click the checkbox beside 'I have read and agree with the above terms and conditions'
and click DOWNLOAD ANDROID SDK PLATFORM-TOOLS FOR WINDOWS
*Current version as of December 12, 2020
platform-tools_r30.0.5-windows.zip
4.) Create a folder in C:\ Drive and name it ADB. Extract platform-tools_rxx.x.x-windows.zip inside ADB folder.
*NOTE: rxx.x.x on platform-tools_rxx.x.x-windows depends on the current version available on Android Developers site.
5.) On your Windows desktop, press the Window logo button on your keyboard, type 'cmd'. Right-click on Command Prompt and click Run as administrator.
7.) On command prompt, type 'cd c:\ADB' and press Enter. *type without quotes *DO NOT CLOSE Command prompt!
8.) Connect your Nubia Red Magic 3 or 3S to a USB 2.0 port.
9.) Wait for Windows to install drivers of your phone. If a CD Drive showed up on "This PC / My Computer", double-click on it and install the driver.
10.) Type 'adb reboot bootloader' and press Enter. *type without quotes
11.) Go back to your command prompt. Type 'fastboot devices'. It should show your phone's serial number and a 'fastboot' word. This means your PC can properly communicate with your Nubia Red Magic 3. *DO NOT CLOSE Command prompt!
12.) Get your ROM ready. Download from these official links if you haven't already.
IMPORTANT: Try to remember the specific version of ROM your Red Magic has.
Because for example if the currently installed is Android 11 (R) but you used the lower version say Android 10 or 9, flashing will proceed but it will not boot to Android OS
For Global, Europe and North America versions:
REDMAGIC 3 Global ROM flash instructions - REDMAGIC (Global)
Want to flash your REDMAGIC device? Here's how. NOTE: Please proceed with caution.
global.redmagic.gg
Chinese version:
Nubia Red Magic 3
http://ui.nubia.cn/rom/detail/62
Nubia Red Magic 3S
http://ui.nubia.cn/rom/detail/64
13.) Extract the zip file to any folder you want. Get inside it and copy the following:
* parameter.img
* boot.img
* recovery.img
* splash.img
* dtbo.img
* vbmeta.img
* NON-HLOS.bin
* dspso.bin
14.) Continuing from the step above, paste the files you copied to ADB folder you created from step 4.
15.) Go back to your command prompt. And type and press Enter the below commands one by one:
fastboot oem nubia_unlock NUBIA_NX629J
fastboot erase parameter
fastboot flash parameter parameter.img
fastboot erase boot
fastboot flash boot boot.img
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot erase splash
fastboot flash splash splash.img
fastboot erase dtbo
fastboot flash dtbo dtbo.img
fastboot erase vbmeta
fastboot flash vbmeta vbmeta.img
fastboot erase modem
fastboot flash modem NON-HLOS.bin
fastboot erase dsp
fastboot flash dsp dspso.bin
Recommended read:
Why erase is important: https://android.stackexchange.com/questions/161103/what-fastboot-erase-actually-does#161115
*Disconnect the USB-C cable from your NRM3/3S
16.) Your phone still on fastboot, press volume down to choose "Reboot to recovery mode" and press power button to confirm.
17.) Your phone should boot to recovery. On the recovery Main Menu, press volume down to choose 'Wipe Data', choose Wipe cache and also User partition.
18.) After the wipe is successful, copy the ROM zip file to your USB flash drive. Insert your USB Flash drive to your OTG USB-C adapter. Then finally insert it to your Nubia Red Magic 3/3S USB-C port.
19.) Your phone still on recovery, select "Choose Update Package" and specify the ROM zip file in your USB OTG device.
20.) Wait for the system installation to finish.
Alternatively, you can view the guide's pastebin. Plain and simple layout especially when you are just using data on your phone
Solution for Nubia Red Magic 3 / 3S "device is corrupt"
Click to expand...
Click to collapse
hi and thank you for your hard work
last time I installed Red Magic 3 V5.11 (official version) chinese rom, then I thought I need google play store so i wanted to downgrade my rom with the help of nubia red magic 3 unbrick tool which was working fine before Red Magic 3 V5.11 (official version) but at this time when i try to downgrade then it shows your devices is corrupted and will not boot ..... since then i tried each and every possible way to recover it but I don't have any technical knowledge so i'm unable to solve the problem so its my humble request to you please help me sir ....... i don't know how to flash rom through pc please guide me and help me.
kalaan10 said:
hi and thank you for your hard work
last time I installed Red Magic 3 V5.11 (official version) chinese rom, then I thought I need google play store so i wanted to downgrade my rom with the help of nubia red magic 3 unbrick tool which was working fine before Red Magic 3 V5.11 (official version) but at this time when i try to downgrade then it shows your devices is corrupted and will not boot ..... since then i tried each and every possible way to recover it but I don't have any technical knowledge so i'm unable to solve the problem so its my humble request to you please help me sir ....... i don't know how to flash rom through pc please guide me and help me.
Click to expand...
Click to collapse
give me something i can contact with u in to help u
RZaR2001 said:
give me something i can contact with u in to help u
Click to expand...
Click to collapse
[email protected] u can contact me here sir
I need some help,
Last time i updated my phone to 5.09 cn rom after that when i got bugs i tried to downgrade to 3.34 and i bricked my phone , then i use unbrick tool and get back to asia version but now my phone doesnot have the charging animation in power off mode and also fastboot device is can't get the device in win7/win 10. I also tried 2-3 times by reflash the cn rom and again back to asian version.
Need help any guide please.
Thanx in advance..
I forgot to mention that adb is working, bootloader is unlocked, i can access bootloader by using keys and adb reboot-bootloader command, but can't get device in device manager in fastboot mode , i can also access 9008 mode and recovery mode. Everything working fine but i have that two issue now, also i have my device in 5.11cn rom now.
kalaan10 said:
hi and thank you for your hard work
last time I installed Red Magic 3 V5.11 (official version) chinese rom, then I thought I need google play store so i wanted to downgrade my rom with the help of nubia red magic 3 unbrick tool which was working fine before Red Magic 3 V5.11 (official version) but at this time when i try to downgrade then it shows your devices is corrupted and will not boot ..... since then i tried each and every possible way to recover it but I don't have any technical knowledge so i'm unable to solve the problem so its my humble request to you please help me sir ....... i don't know how to flash rom through pc please guide me and help me.
Click to expand...
Click to collapse
I think I encountered this problem also when going from Android 11 (V5.11) to Android 10 (V3.34). What worked for me is the tool posted on nubia bbs.
It's on chinese but I put some screenshots on this link to be able to use it.
Red Magic 3 - Mediafire
To use the tool, put your Red Magic 3 on fastboot mode.
How to boot on Fastboot
1.) Turn off your NRM3.
2.) HOLD Volume down and power
3.) Your NRM3 should boot on fastboot
And for google play store, I'm currently using 5.09 and successfully root it with g-apps. Flashing magisk and g-apps is working ong V3.34 and V5.09.
I had problem about less charger mA on 3 charger and cables so strange , so today i did buy another cable and same thing less mA like 100 should be 3000 , so i did use one charger adapter rampow for try , when i did put charger less again but the screen get blocked and reboot , when it restarted i did see that if i put to charger again also with orginal charger and cable will block screen and reboot so i did try to reset and install Europe & Asia: V212 , when did get 100% will show that " Device is corrupt. It can't be trusted and will not boot " ,this happen if you put one not original cable or charger i did discovery ,now the problem is if i put the cable on laptop for flash install roms windows will not detected the new hardware of red magic so how can i fix that now
cacaocaca said:
I had problem about less charger mA on 3 charger and cables so strange , so today i did buy another cable and same thing less mA like 100 should be 3000 , so i did use one charger adapter rampow for try , when i did put charger less again but the screen get blocked and reboot , when it restarted i did see that if i put to charger again also with orginal charger and cable will block screen and reboot so i did try to reset and install Europe & Asia: V212 , when did get 100% will show that " Device is corrupt. It can't be trusted and will not boot " ,this happen if you put one not original cable or charger i did discovery ,now the problem is if i put the cable on laptop for flash install roms windows will not detected the new hardware of red magic so how can i fix that now
Click to expand...
Click to collapse
Have you tried to on the developer options and turn on USB debugging on your Red Magic 3?
How can I activate the debug if just show me that
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can just enter in recovery mode , emerg recovery mode and edload but I can t do nothing if windows will not detect the device, this it happen when I did use the charger not official, it just ridiculous, I did use the charger rampow for iPhone android without problem while in this phone did happen that just because Nubia want steal money for the assistance
Maybe it hardbrick
RZaR2001 said:
give me something i can contact with u in to help u
Click to expand...
Click to collapse
can u help me too pls
cacaocaca said:
How can I activate the debug if just show me that View attachment 5173669
I can just enter in recovery mode , emerg recovery mode and edload but I can t do nothing if windows will not detect the device, this it happen when I did use the charger not official, it just ridiculous, I did use the charger rampow for iPhone android without problem while in this phone did happen that just because Nubia want steal money for the assistance
Click to expand...
Click to collapse
I think you should try service centre once.
jhonangelo30 said:
can u help me too pls
Click to expand...
Click to collapse
Okay pm me
3
Sir i have the same thing. Im using rm3 when i bought this its already flash on global rom. So im curious because its box is Chinese text but it's global rom so i flash to china rom and its success but suddenly i figure it out that chinarom doesn't have google so i flash again to global rom then suddenly it corrupt after the flash. I tried those method like that unbrick tool non.eu i follow the steps very well but when it comes to the part that cmd will pop 'downloading port 4'
It says that faile and un identified and it says that please check your status or what. I'm humble asking for your help because this is my only phone and i need this for my online school
johnbrinan1 said:
3
Sir i have the same thing. Im using rm3 when i bought this its already flash on global rom. So im curious because its box is Chinese text but it's global rom so i flash to china rom and its success but suddenly i figure it out that chinarom doesn't have google so i flash again to global rom then suddenly it corrupt after the flash. I tried those method like that unbrick tool non.eu i follow the steps very well but when it comes to the part that cmd will pop 'downloading port 4'
It says that faile and un identified and it says that please check your status or what. I'm humble asking for your help because this is my only phone and i need this for my online school
Click to expand...
Click to collapse
don't worry it can be fixed
RoseRahman said:
I think you should try service centre once.
Click to expand...
Click to collapse
My phone was in assistance and now it come back and work fine , no more device corrupt and no more slow charger , they did exachange the motherboard on my phone , if you will not ear the sound while plug the device to windows this mean problem motherboard maybe like me
leipnacht said:
Sharing this guide seems quite late but since xda red magic threads taught me a lot about the rooting and corrupted stuffs, I think it would not hurt to return something back to this community.
This is my attempt to compile people's responses that helped other people here which are scattered around forums.
Myself included also tinkered a lot on this device and literally go back here on this guide to lessen headaches.
EDIT: Tested a lot of times with V5.08 and V5.09 Android R versions
REMINDER: Tested on Android 9, no clues yet on Android 10 and 11
WHEN TO USE?
Use this guide to restore your phone to boot in Android OS again normally without wiping data, retaining your apps, games intact
Requirements:
- Windows computer. NOTE: Done this using Windows 10, so I'm not exactly sure if latest ADB works the same on Windows 7.
- Nubia Red Magic 3 or 3S battery charge should be at 50% above at least.
- You need a USB cable to connect your phone to PC. XDA Users reported better with USB 2.0 port
NOTE: Can be used also on 3S. I just don't have 3S so I haven't tested it on actual 3S.
Download latest the ADB (Android Debug Bridge) from Android Developers site.
1.) Go to https://developer.android.com/studio/releases/platform-tools
2.) Click Download SDK Platform-Tools for Windows.
3.) Click the checkbox beside 'I have read and agree with the above terms and conditions'
and click DOWNLOAD ANDROID SDK PLATFORM-TOOLS FOR WINDOWS
*Current version as of December 12, 2020
platform-tools_r30.0.5-windows.zip
4.) Create a folder in C:\ Drive and name it ADB. Extract platform-tools_rxx.x.x-windows.zip inside ADB folder.
*NOTE: rxx.x.x on platform-tools_rxx.x.x-windows depends on the current version available on Android Developers site.
5.) On your Windows desktop, press the Window logo button on your keyboard, type 'cmd'. Right-click on Command Prompt and click Run as administrator.
7.) On command prompt, type 'cd c:\ADB' and press Enter. *type without quotes *DO NOT CLOSE Command prompt!
8.) Connect your Nubia Red Magic 3 or 3S to a USB 2.0 port.
9.) Wait for Windows to install drivers of your phone. If a CD Drive showed up on "This PC / My Computer", double-click on it and install the driver.
10.) Type 'adb reboot bootloader' and press Enter. *type without quotes
11.) Go back to your command prompt. Type 'fastboot devices'. It should show your phone's serial number and a 'fastboot' word. This means your PC can properly communicate with your Nubia Red Magic 3. *DO NOT CLOSE Command prompt!
12.) Get your ROM ready. Download from these official links if you haven't already.
IMPORTANT: Try to remember the specific version of ROM your Red Magic has.
Because for example if the currently installed is Android 11 (R) but you used the lower version say Android 10 or 9, flashing will proceed but it will not boot to Android OS
For Global, Europe and North America versions:
REDMAGIC 3 Global ROM flash instructions - REDMAGIC (Global)
Want to flash your REDMAGIC device? Here's how. NOTE: Please proceed with caution.
global.redmagic.gg
Chinese version:
Nubia Red Magic 3
http://ui.nubia.cn/rom/detail/62
Nubia Red Magic 3S
http://ui.nubia.cn/rom/detail/64
13.) Extract the zip file to any folder you want. Get inside it and copy the following:
* parameter.img
* boot.img
* recovery.img
* splash.img
* dtbo.img
* vbmeta.img
* NON-HLOS.bin
* dspso.bin
14.) Continuing from the step above, paste the files you copied to ADB folder you created from step 4.
15.) Go back to your command prompt. And type and press Enter the below commands one by one:
fastboot oem nubia_unlock NUBIA_NX629J
fastboot erase parameter
fastboot flash parameter parameter.img
fastboot erase boot
fastboot flash boot boot.img
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot erase splash
fastboot flash splash splash.img
fastboot erase dtbo
fastboot flash dtbo dtbo.img
fastboot erase vbmeta
fastboot flash vbmeta vbmeta.img
fastboot erase modem
fastboot flash modem NON-HLOS.bin
fastboot erase dsp
fastboot flash dsp dspso.bin
Recommended read:
Why erase is important: https://android.stackexchange.com/questions/161103/what-fastboot-erase-actually-does#161115
*Disconnect the USB-C cable from your NRM3/3S
16.) Your phone still on fastboot, press volume down to choose "Reboot to recovery mode" and press power button to confirm.
17.) Your phone should boot to recovery. On the recovery Main Menu, press volume down to choose 'Wipe Data', choose Wipe cache and also User partition.
18.) After the wipe is successful, copy the ROM zip file to your USB flash drive. Insert your USB Flash drive to your OTG USB-C adapter. Then finally insert it to your Nubia Red Magic 3/3S USB-C port.
19.) Your phone still on recovery, select "Choose Update Package" and specify the ROM zip file in your USB OTG device.
20.) Wait for the system installation to finish.
Alternatively, you can view the guide's pastebin. Plain and simple layout especially when you are just using data on your phone
Solution for Nubia Red Magic 3 / 3S "device is corrupt"
Click to expand...
Click to collapse
Hello, thanks for your contribution I practiced it 100 but it did not work, I hope you can help me, I have a global nubia rm3S, I had android 9 but I wanted to change to android 11 ch, when updating by OTG it worked without problems, but I did not open an application of my work so I had to try to return to android 9 global, but after the update reached% 100 it restarted and I stayed in DEVICE CORRUPT, now I don't know what to do, I already tried with your method and everything Apparently it is perfect, it does not make an error in anything and I have communication from the adb it gives me my serial number and the drivers are perfect, what can I do?
ZephyrOne said:
Hello, thanks for your contribution I practiced it 100 but it did not work, I hope you can help me, I have a global nubia rm3S, I had android 9 but I wanted to change to android 11 ch, when updating by OTG it worked without problems, but I did not open an application of my work so I had to try to return to android 9 global, but after the update reached% 100 it restarted and I stayed in DEVICE CORRUPT, now I don't know what to do, I already tried with your method and everything Apparently it is perfect, it does not make an error in anything and I have communication from the adb it gives me my serial number and the drivers are perfect, what can I do?
Click to expand...
Click to collapse
I see you upgraded to Android 11 CN then downgraded to Android 9 again. You need the TWRP from baidu guide regarding downgrading from A11.
Here's the link. Google Drive - TWRP from Baidu
DM me if you're having problems with TWRP.
leipnacht said:
I see you upgraded to Android 11 CN then downgraded to Android 9 again. You need the TWRP from baidu guide regarding downgrading from A11.
Here's the link. Google Drive - TWRP from Baidu
DM me if you're having problems with TWRP.
Click to expand...
Click to collapse
Hello thanks for your help, the problem is that I do not enable oem unlocking in the system. Do you know if twrp can be installed without that option?
Related
Acer Liquid Z330 [Acer T01]
A- Unbrick
B- Unlock Bootloader
C- TWRP
D- Root
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi,
First i want to tell you my english is too bad .. but i will do my best..
This is the first Thread for this Phone..
_____________________________________________________________________________
A- Unbrick Acer Liquid Z330 (On Windows Only)
Step 1: Required Files ->
1- Converter (To make a System.img file) : Download
2- Stock Firmware :
For "WW_GEN1" : WW_GEN1
For "EMEA_BGCS" : EMEA_BGCS
(If links not working download from this link Acer Official)
3- Download & install Adb and Fastboot from this thread : ADB and Fastboot
4- Download & install Python 3.x (Required for Converter) : Python For Windows
Step 2: Prepare Files ->
1- Extract Converter folder.
2- Extract Stock firmware and copy "file_contexts" , "system.new.dat", "system.patch.dat", "system.transfer.list" from it to Converter Folder.
3- Launch "Converter.exe" and tap any key and wait...
4- If all done you got 2 file called : system_new.img and system.raw.img - we need just one file called system_new.img
5- Move "system_new.img" from Converter folder to your adb folder (for me is C:\\adb) and rename it to "system.img"
6- Back to Stock Firmware Folder and copy from it this files "boot.img", "misc.bin", "NON-HLOS.bin", "rpm.mbn", "sbl1.mbn" to your adb folder.
7- Check if you have on your adb folder all this files: "system.img", "boot.img", "misc.bin", "NON-HLOS.bin", "rpm.mbn", "sbl1.mbn"
Step 3: Enter to fastboot ->
1- Shutdown your device
2- Press Volume Up (Volume +) don't release it and press power key untill Acer logo appear and release power key only (keep your finger on volume up) until you enter to recovery mode
3.a- if you have stock recovery, just choose Fastboot mode
3.b- if you have TWRP choose Reboot and Bootloader
4- Connect the device to the computer through USB.
5- Now launch CMD on adb folder (press shift on keyboard and right click on your adb folder and choose "Open Command Window Here".
6- Verify your PC sees the device by typing :
Code:
fastboot devices
***** If you don't see your device serial number, and instead see "<waiting for device>", fastboot is not configured properly on your machine. *****
Step 4: Flash files ->
1- Execute this commands :
Code:
fastboot -w
Code:
fastboot erase cache
Code:
fastboot erase sbl1
Code:
fastboot flash sbl1 sbl1.mbn
Code:
fastboot erase rpm
Code:
fastboot flash rpm rpm.mbn
Code:
fastboot erase misc
Code:
fastboot flash misc misc.bin
Code:
fastboot erase modem
Code:
fastboot flash modem NON-HLOS.bin
Code:
fastboot erase system
Code:
fastboot flash system system.img
******** NOTE : flash system take about 5/10 mins.. Don't worry about "Max length message" just wait until you show you "Finished" *************
Code:
fastboot erase boot
Code:
fastboot flash boot boot.img
Code:
fastboot reboot
2- Normally after finished the phone take about 10mins on boot to system.. just wait
3-[JUST IN CASE] If your phone stuck on demo mode (show demo mode on bottom) please don't worry.. connect it to wifi and reboot.. Phone check the updates.. download and install all update and do a factory reset.
DONE !! Your phone back to life
Credits : The Converter Developed By "XN creation"
_____________________________________________________________________________
B- Unlock Bootloader
Step 1: Required Files ->
1- Download & install Adb and Fastboot from this thread : ADB and Fastboot
Step 2: Prepare Your device ->
1- Enable USB debugging on the device (How To)
2- Enable "OEM unlock" in the Developer options settings on the device.
3- Shutdown your device
4- Press Volume Up (Volume +) don't release it and press power key untill Acer logo appear and release power key only (keep your finger on volume up) until you enter to recovery mode
5- On stock recovery, just choose Fastboot mode
6- Connect the device to the computer through USB.
7- Now launch CMD on adb folder (press shift on keyboard and right click on your adb folder and choose "Open Command Window Here".
8- Verify your PC sees the device by typing :
Code:
fastboot devices
***** If you don't see your device serial number, and instead see "<waiting for device>", fastboot is not configured properly on your machine. *****
Step 3: Execute this commands
1-
Code:
fastboot oem unlock
2- Verify if your bootloader unlocked
Code:
fastboot oem device-info
***** If all ok show you "Device unlocked: true" ************
3- Reboot to system
Code:
fastboot reboot
_____________________________________________________________________________
C- Install TWRP Recovery
Step 1: Bootloader Unlocked Required !! If not follow my instructions on top
Step 2: Download TWRP.zip from this link (Download) and extract recovery.img and copy it to your adb folder.
Step 3: Enter your device to Fastboot Mode, Connect it to the computer through USB and launch CMD prompt from your adb folder.
Step 4: Type this command
Code:
fastboot flash recovery recovery.img
Code:
fastboot reboot
And DONE ! You have now TWRP !!
Credits : TWRP compiled from the original source by "Jemmini"
_____________________________________________________________________________
D- Root
Step 1: Bootloader Unlocked & TWRP Recovery Required !! Please Follow My Instructions on top (B & C instructions)
Step 2: Download latest Supersu from this thread (SuperSU v2.79) Choose "TWRP / FlashFire installable ZIP" one.
Step 3: Copy SuperSU zip file to your internal or external storage on your device.
Step 4: Reboot to TWRP recovery :
Press Volume Up (Volume +) don't release it and press power key untill Acer logo appear and release power key only (keep your finger on volume up) until you enter to recovery mode.
Step 5: On TWRP enter to INSTALL and Choose the superSU zip file and install it.
Step 6: Reboot.
Done... Your Device Rooted !!
_____________________________________________________________________________
Thats All !!
Sorry for my bad English...
I'm here if you have any questions..
the converting the system.new.dat files to system.img part failed (the program gave some error). Could you maybe provide the system.img you used?
Also, did your phone keep going off and on again during those 10 mins of first startup?
Mounir9912 said:
the converting the system.new.dat files to system.img part failed (the program gave some error). Could you maybe provide the system.img you used?
Also, did your phone keep going off and on again during those 10 mins of first startup?
Click to expand...
Click to collapse
System.img is a big file to upload about 2.6gb ... your are install Python or not ?
My phone stuck on startup around 15 mins .. but it's working..
Please try both official rom.. for me my phone working only with the second one..
Ysfzone said:
System.img is a big file to upload about 2.6gb ... your are install Python or not ?
My phone stuck on startup around 15 mins .. but it's working..
Please try both official rom.. for me my phone working only with the second one..
Click to expand...
Click to collapse
I've tried it with the other rom and it worked. Well, actually the converter didn't work. I actually had to use this:
https://github.com/xpirt/sdat2img
to create the system.img in ext4 format, then I had to use this:
http://forum.xda-developers.com/showthread.php?t=2749797
to create a flashable sparse chunk from the system.img.
the rest of the stuff like the boot, modem, cache etc flashed just fine. After flashing everything it booted perfectly.
Only problem is it's in demo mode and it requires the google account of the previous owner to log in before it unlocks. Since I'm only repairing it for someone I don't have that and can't get it out of demo mode for now.
failed remote:failed to erase partition
I get failed remote:failed to erase partition error...how can I fix this? please help (
sYntrax121 said:
I get failed remote:failed to erase partition error...how can I fix this? please help (
Click to expand...
Click to collapse
Where give you this problem ?
When I try to update the phone, it automatically boots into twrp recovery and after rebooting it says update failed. I think it's trying to update via the recovery but it can't because it isn't the original recovery. Do you have the stock (original) recovery?
Btw, where did you get the EMEA_BGCS firmware from?
Mounir9912 said:
When I try to update the phone, it automatically boots into twrp recovery and after rebooting it says update failed. I think it's trying to update via the recovery but it can't because it isn't the original recovery. Do you have the stock (original) recovery?
After flashing all files the phone back to stock recovery itself.. please use erase commands..
Btw, where did you get the EMEA_BGCS firmware from?
Click to expand...
Click to collapse
from here : https://www.acer.com/ac/fr/BE/content/support-product/6358?b=1
I did do all the erase commands, did you also erase the recovery though?
When you have the time, could you explain step by step what you did to convert the .dat files into the .img files? That's the only thing I did differently because it didn't work for me (yes python was installed)
Ysfzone said:
Where give you this problem ?
Click to expand...
Click to collapse
everytime I run "fastboot erase cache" command
sYntrax121 said:
everytime I run "fastboot erase cache" command
Click to expand...
Click to collapse
Just ignore it and jump to next command
Hello the 4th step does 'nt work for me, my old vista 32 say that there are some error. Is it possible to use an ither program to create the image file?
"4- If all done you got 2 file called : system_new.img and system.raw.img - we need just one file called system_new.img"
anicee said:
Hello the 4th step does 'nt work for me, my old vista 32 say that there are some error. Is it possible to use an ither program to create the image file?
"4- If all done you got 2 file called : system_new.img and system.raw.img - we need just one file called system_new.img"
Click to expand...
Click to collapse
if you have any other program use it.. why not
Ysfzone said:
if you have any other program use it.. why not
Click to expand...
Click to collapse
No unfornately I have' nt an other program to do that, but I have tried to install the original rom of acer and I have this message :
E: footer is wrong
E:signature verification failed
Installation aborted
I tchat with a technician of acer. He ask me to give the build number.... Yes but I can't give it that. My mobile is bricked! He advises to send my phone on SAV, but the phone is rooted!
Is there someone would be kind enough to give me the build number, please? :crying:
Or is it possible to get this number with adb?
Thank you for your answer and sorry for my English
На 4pda .ru есть тема "Обсуждение Acer Liquid Z330 Duo" страница 47, пост #930 в ней описан способ прошивки и сама прошивка 027 версии для разных языков. Телефон прошивается без проблем, проверено. Ссылку сайт не дает вставить. По этому ищите вручную.
Amazing work!
Windows 10 mobile --> android = Problems
Hello. I installed on the Z330 Windows 10 mobile. Help please go back to Android. Presumably change Disk Partitions. How is it to create one?
TWRP won't Install, it's always goes to stock Recovery instead TWRP. Help please thanks ~
I got the same result with #19, and my image version is Acer_AV0L0_T01_RV01RB10_TWN_GEN1.
The fastboot flash command seemed to pass, but I can not boot into TWRP. It still stayed in the old recovery mode.
BR.
TAT TecKnight's Aristo 2 Tutorials series
Click the description below to pull up the detailed post
Restore your Aristo 2 / 2 + Images/Animations & Carrier Software to stock
Access the Operator HiddenMenu on your Aristo 2 / 2 +
Install a pre-rooted ROM to your LG Aristo 2 / 2 + / Best root method
Install LGUP Dual Mode(Dev/User) on your Windows PC
List of LG cv1 devices with Model number and common name
What you need to know about LG's Oreo firmware for the Aristo 2 and variants
Root your LG Aristo 2/2+/K8+, remove encryption/verity & install TWRP and Magisk
Fix your LG Aristo 2 / 2 plus / K8 + that is stuck in TWRP
Restore some or all of your rooted LG Aristo 2 plus partitions to stock 10j firmware w/o LGUP
Restore your LG phone to the latest factory firmware using LG Bridge
Install a specific .KDZ image to your LG phone using LGUP
Install Xposed Framework on your Magisk rooted Aristo 2/2 +
Useful links for LG Aristo 2/2 +/K8 +
More tutorials coming soon !!
XDA:DevDB Information
Tec's Lightning ROM for Aristo 2 / 2 plus, ROM for the Android General
Contributors
tecknight
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: An LG Aristo 2 (MPCS) or Aristo 2 plus (T-Mobile)
Based On: LG Stock firmware
Version Information
Status: Stable
Current Stable Version: v20g-rel
Stable Release Date: 2019-06-06
Current Beta Version: v20k-beta1
Beta Release Date: 2019-12-03
Created 2019-10-21
Last Updated 2019-12-04
Root your LG Aristo 2/2+/K8+, remove encryption/verity & install TWRP and Magisk
TAT TecKnight's Aristo 2 Tutorials series
Root your LG Aristo 2/2+/K8+, remove encryption/verity & install TWRP and Magisk
Requirements:
An LG Aristo 2 / 2 + / K8 +
A PC running Windows with an internet connection.
A USB cable.
Note: This procedure is deprecated for several reasons, the most important one being that fastboot will not flash a partition on a cv1 device running the latest (Oreo) firmware.
I recommend this procedure instead:
Install a pre-rooted ROM to your LG Aristo 2 / 2 + / Best root methodHowever, if your phone is currently running Android 7 (Nougat) based firmware, this procedure will still work.
1. On your phone, go to Settings->General->About Phone->Software Info. Click on Build Number 7 times. You have now enabled Developer Options
2. On your phone, go to Settings->Developer Options and Turn ON both OEM Unlock and USB debugging. Turn OFF Automatic System Updates. Click on Select USB Configuration and select MTP (Media Transfer Protocol)
3. Connect your phone to your PC using the USB cable.
4. On your PC, open a command prompt or power shell session in the folder where your adb and fastboot executables reside.
5. In your command prompt or power shell session, type"
adb devicesYou should see:
List of devices attached
<SerialNumofPhone> device6. Now type:
adb reboot bootloader7. You should see some text in very small letters on your phone. You are now in bootloader or fastboot mode.
8. Currently, Magisk stable and beta versions are the same (17.1).
If you have a MetroPCS Aristo 2, firmware 10K or earlier, download this file:
10K_M171_EVD.img --> Aristo 2 Magisk 17.1 rooted boot image encrypt/verity/rct disabledor if you have a MetroPCS Aristo 2, firmware 10L or later, download this file:
10L_M173_EVD.img --> Aristo 2 Magisk 17.3 rooted boot image encrypt/verity/rct disabledSpecial note for Aristo 2 owners running 10L or later: I have personally and I have had reports from others who have experienced boot loops after flashing the 10L or later patched boot image. Others have reported success using this image. If you do experience boot loops after flashing the 10L or later boot image, I recommend the following:
Install a custom pre-rooted ROM to your LG Aristo 2 or Aristo 2 plus using TWRP
or if you have a T-Mobile Aristo 2 plus, download this:
RB_M171_EVD_A2P.img --> Aristo 2 + Magisk 17.1 rooted boot image encrypt/verity/rct disabled
or if you have a US Cellular K8 plus, download this:
RB_M171_EVD_K8P.img --> K8 + Magisk 17.1 rooted boot image encrypt/verity/rct disabledDownload this file as well:
recovery.img --> Latest TWRP 3.2.1.0 for Aristo 2 by armandop_ (works on 2+ and K8+ as well)9. Place both files into the folder where your adb and fastboot executables reside. Make sure they are named exactly as listed above.
10. Type the following in the command prompt or power shell session:
fastboot devicesYou should see:
<SerialNumofPhone> fastboot11. Type this:
fastboot flashing unlockfastboot will say this will wipe your data. Tell it to continue.
Now we need to erase the userdata and cache partitions to prevent fastboot from encrypting them. Type:
fastboot erase userdataYou should see:
******** Did you mean to fastboot format this ext4 partition?
erasing 'userdata'...
OKAY [ 0.031s]
finished. total time: 0.031sNow type:
fastboot erase cacheYou should see:
******** Did you mean to fastboot format this ext4 partition?
erasing 'cache'...
OKAY [ 0.031s]
finished. total time: 0.031s12. Now that you are unlocked, flash the rooted boot image. Depending on the file you downloaded above, type:
fastboot flash boot 10K_M171_EVD.img
or
fastboot flash boot 10L_M173_EVD.img
or
fastboot flash boot RB_M171_EVD_A2P.img
or
fastboot flash boot RB_M171_EVD_K8P.img
You should see:
target reported max download size of 262144000 bytes
sending 'boot' (15210 KB)...
OKAY [ 0.585s]
writing 'boot'...
OKAY [ 0.200s]
finished. total time: 0.790s13. Now flash TWRP. Type:
fastboot flash recovery recovery.imgYou should see:
target reported max download size of 262144000 bytes
sending 'recovery' (17010 KB)...
OKAY [ 0.585s]
writing 'recovery'...
OKAY [ 0.200s]
finished. total time: 0.790s14. Now reboot back to Android. Type:
fastboot rebootNote: Your bootup screen will now look like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This message does not indicate a problem. This is the normal bootup screen of the Aristo 2, once the bootloader is unlocked. DO NOT lock the bootloader or your phone will then refuse to boot.
Note: Since we had to wipe userdata, Android will boot up with the setup wizard, just like the first time the phone was booted.
15. Once you get past the setup wizard, repeat steps 1 and 2, as most of our settings have been reset back to defaults. After completing steps 1 and 2, return to step 16.
16. Download the following file and copy it to your phone's Download folder:
Magisk-v17.1.zip --> Magisk 17.1 installation .zip
17. On your PC, go to your command prompt or power shell and type:
adb reboot recoveryYour phone will now boot into TWRP for the first time.
18. On your phone, Swipe to allow modifications.
19. Now select INSTALL, then browse into the Download folder and select your Magisk install .zip.
Swipe to confirm flash. TWRP will install Magisk on your system.
20. Now, select Reboot System.
Your phone will boot back into Android. Your phone should now be rooted, unencrypted and have Magisk and TWRP installed.
21. Confirm that Magisk is installed and working. Look for the Magisk Manager icon on your android desktop. The icon looks like this:
If you can't find the icon, download and install the app from here:
Magisk Manager 5.9.1 download
22. Click on the Magisk Manager icon to launch it. You should see a screen resembling the following:
You should have the 2 green check marks at the top, with the version showing as 17.1.
Under Advanced Settings, both Preserve options should be unchecked.
If you don't have the green check marks, click Install, then install again, then Direct Install (Recommended).
If you want to keep the latest Magisk beta on your phone, click on the 3 horizontal lines and select Settings, click on Update Channel and select Beta.
23. Once Magisk is installed, I recommend you check out the multitude of cool, mostly rooted apps available from the Magisk repo. Click on the 3 horizontal lines and select Downloads, then browse thru the large list of apps that are available.
Please hit the Thanks button at the bottom of this post if you appreciate my work.
_________
Change Log:
02/03/2019 Added note that this procedure is deprecated.
11/22/2018 Added link to flashing rooted image with TWRP as alternative.
11/19/2018 Added specific note and instructions when running Aristo 2 version 10L or later. Thanks to @Dillmiester for showing me that I was not the only one having issues with 10L.
10/20/2018 Changed all of the custom file downloads from Google Drive to androidfilehost.com.
9/18/2018 Added K8 plus patched boot image. Thanks to @RandoSwift for providing the stock K8 plus boot image.
9/3/2018 Updated Magisk installer and Magisk manager links to reflect current versions (17.1 and 5.9.1). I also updated the patched boot images to 17.1 and linked to those images.
8/4/2018 Added a picture of the bootloader unlocked warning that displays when the phone is booted.
8/2/2018 Added newest version of TWRP for Aristo 2 by @Armandop_. It now pulls the correct date/time.
8/2/2018 Added Aristo 2 plus patched boot image. Thanks to @SteelH for providing the stock Aristo 2 plus boot image.
7/23/2018 Changed Magisk beta boot image and installation .zip to ver 16.7.
7/15/2018 Removed LG root checking tool from both boot images and changed Magisk beta boot image to ver 16.6.
7/3/2018 Made changes to allow user to choose to install either Magisk 16 released or Magisk 16.4 beta. Thanks to @GotHeart for information regarding Magisk 16.4 beta.
6/27/2018 Made several changes when I determined that fastboot was creating encrypted userdata and cache partitions whenever flashing lock state was changed. Ultimately, I was able to simplify this procedure, as I can now guarantee that step 14 will create a non-encrypted userdata and cache filesystem. This allowed me to eliminate several subsequent steps. Thanks to @tge101 for identifying this issue.
5/21/2018 Created initial procedure.
Useful links for LG Aristo 2/2+
TAT TecKnight's Aristo 2 Tutorials series
Useful links for LG Aristo 2/2+
Windows Software
LG USB drivers. The latest official USB drivers for LG phones.
http://tool.cdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
LGUP - LGUP was LG's internal utility used to flash images to phones. But it was leaked to the public and is now the most used user utility for flashing phones. I have made some mods to enable developer options and increase it's compatibility.
Download it here:
https://www.androidfilehost.com/?fid=11410932744536985527
Full installation instructions are here:
Install LGUP Dual Mode(Dev/User) on your Windows PC
Uppercut-An XDA devs enhancement tool for LGUP. Use if LGUP does not recognise your phone.
http://downloads.codefi.re/autoprime/LG/Flash_Tools/LGUP/UPPERCUT_1.0.0.0.zip
LG Bridge for Windows. A useful tool capable of identifying your phone, downloading the latest firmware for it and then flashing the firmware image to your phone.
http://tool.cdn.gdms.lge.com/dn/downloader.dev?fileKey=PWZO7A26B9UW
Other Links
Official firmware images in the form of .KDZ files.
Aristo 2 firmware:
https://lg-firmwares.com/lg-lmx210ma-firmwares/firmwares/
Aristo 2 plus firmware:
https://lg-firmwares.com/lg-lmx212ta-firmwares/#tab=firmwares
K8 plus firmware:
https://lg-firmwares.com/lg-lmx210ulm-firmwares/firmwares/
Please hit the Thanks button at the bottom of this post if you appreciate my work.
Restore your LG phone to the latest factory firmware using LG Bridge
TAT TecKnight's Aristo 2 Tutorials series
Restore your LG phone to the latest factory firmware using LG Bridge
This Tutorial describes how you can restore your LG phone to the latest official firmware using LG Bridge windows software.
Note that LG Bridge will always restore the latest factory firmware to your phone. If you need to restore a specific KDZ image to your phone, you should use:
Install a specific .KDZ image to your LG phone using LGUP
instead.
This procedure will work even if your phone is not able to boot properly.
As long as the bootloader is loading (ie: something is displaying on the screen when you power it up), LG Bridge should be able to restore your phone.
Requirements:
An LG phone
A PC running Windows with an internet connection.
A USB cable.
Note: I have had reports that as of 8/5/2018, this procedure is not working on the LG Aristo 2 plus, as Update error recovery gets the error:
Your phone information cannot be checked.
Please contact LG customer service
Still, if you have an Aristo 2 plus and have a need to restore your phone to stock, I would give this procedure a try, as I expect it will start working at some point.
1. Download LG Bridge to your Windows PC from here:
http://tool.cdn.gdms.lge.com/dn/downloader.dev?fileKey=PWZO7A26B9UW2. Install LG Bridge on your PC.
3. Launch LG Bridge on your PC.
4. Power OFF your Phone.
5. Connect one end of the USB cable to your PC.
6. Press and hold Volume + on the phone. Connect the other end of USB cable to your phone while still pressing Volume +.
5. Download Mode should appear on the phone, and then change to Firmware Update
6. LG Bridge should now detect your phone. Click on the Software Update tab. then select Update error recovery.
7. LG Bridge will download the latest available firmware for your model and then restore your phone using LGUP utility integrated into the LG Bridge software.
Please hit the Thanks button at the bottom of this post if you appreciate my work.
_________
Change Log:
8/4/2018 Changed the wording to make this procedure apply to all LG phones.
8/2/2018 Added detail as to the tab and option to select in LG Bridge.
5/28/2018 Created initial procedure.
which partition do i flash it wants me to be specific n an not just say flash
tecknight said:
Root your LG Aristo 2 from stock, remove forced encryption, and install TWRP and Magisk
1. Go to Settings->General->About Phone->Software Info. Click on Build Number 10 times. You have now enabled Developer Options
2. Go to Settings->Developer Options and Turn ON OEM Unlock
3. Shut down your phone.
4. Plug one end of a USB cable into your PC, but do not plug the other end into your phone yet.
5. Press and hold Vol - on the phone.
6. Connect the unconnected end of the USB cable to your phone while still holding Vol -.
7. Once you see some text in very small letters on your phone, release Vol -. You are now in fastboot mode.
8. On your PC, open a command prompt or power shell in the folder where your adb and fastboot executables reside. You should place the newtwrp.img and root_boot.img into this folder. If you need to download the files:
root_boot.img --> https://androidfilehost.com/?fid=673956719939818308
newtwrp.img --> https://drive.google.com/file/d/1Gz5C9AZVilARyLIKm4bHy2BRWaFqkiMa/view?usp=drivesdk
9. Type the following in command prompt or power shell:
fastboot devices
You should see:
xxxxxxxxxx fastboot
10. Type this:
fastboot oem unlock
fastboot will say this will wipe your data. Tell it to continue.
11. now that you are unlocked, flash the modified boot image:
fastboot flash boot root_boot.img
12. Now flash TWRP:
fastboot flash recovery newtwrp.img
13. Now reboot back to Android:
fastboot reboot
14. Once Android boots up, go to Settings->Developer options and make sure adb is enabled.
15. Now go back to the power shell session and type:
adb devices
You should see:
List of devices attached
xxxxxxxxxxxxx device
16. Before booting into TWRP, make sure to download these two files and copy them to your phone's Download folder:
Magisk-v16.0.zip --> https://github.com/topjohnwu/Magisk/releases/download/v16.0/Magisk-v16.0.zip
no-verity-opt-encrypt-6.0.zip --> https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-6.0.zip
17. Once those files are in place, go to your command prompt or power shell and type:
adb reboot recovery
Your phone will boot into TWRP for the first time.
18. Swipe to allow modifications.
19. If TWRP asks for a password, press the back key to get to the main TWRP screen.
20. Select WIPE then Format Data. Swipe to confirm.
21. Go back to main TWRP screen and select Reboot then Recovery
This should force an unencrypted data partition. TWRP will boot back up again.
22. Now select INSTALL, then browse into the Download folder and select the
no-verity-opt-encrypt-6.0.zip, then select Add more zips and select the Magisk-v16.0.zip.
23. Swipe to confirm flash. TWRP will change the boot image to allow data to be unencrypted and also will install Magisk on your system.
24. From the main TWRP screen, select Reboot then System.
Your phone will boot back into Android. Your phone is now rooted and has TWRP and Magisk installed.
Click to expand...
Click to collapse
alls i need to kno now(i hope) is which partition do i tell it to flash an where can i find the stock metro pcs .kdz
[email protected] said:
alls i need to kno now(i hope) is which partition do i tell it to flash an where can i find the stock metro pcs .kdz
Click to expand...
Click to collapse
If you follow the procedure listed, you will see that you are flashing 2 partitions:
the boot partition and the recovery partition
from the procedure:
...
11. now that you are unlocked, flash the modified boot image:
fastboot flash boot root_boot.img
12. Now flash TWRP:
fastboot flash recovery newtwrp.img
...
Click to expand...
Click to collapse
You don't need a kdz to restore back to stock. Just follow the procedure here:
Restore your Aristo 2 to the latest factory firmware using LG Bridge
If you want a kdz, however, they are all here:
https://lg-firmwares.com/lg-lmx210ma-firmwares/
what now
tecknight said:
If you follow the procedure listed, you will see that you are flashing 2 partitions:
the boot partition and the recovery partition
from the procedure:
You don't need a kdz to restore back to stock. Just follow the procedure here:
Restore your Aristo 2 to the latest factory firmware using LG Bridge
If you want a kdz, however, they are all here:
https://lg-firmwares.com/lg-lmx210ma-firmwares/
Click to expand...
Click to collapse
i folowed all this here's the screenshots idk man i'm either caveman status or coding Ain't for me
sorry for repost
tecknight said:
If you follow the procedure listed, you will see that you are flashing 2 partitions:
the boot partition and the recovery partition
from the procedure:
You don't need a kdz to restore back to stock. Just follow the procedure here:
Restore your Aristo 2 to the latest factory firmware using LG Bridge
If you want a kdz, however, they are all here:
https://lg-firmwares.com/lg-lmx210ma-firmwares/
Click to expand...
Click to collapse
followed to a t bro either im dumb an coding aint for me or im misinterpreting the lingo but here's screenshots oof my sd card where the files are an my adb im at a loss for words sorry didn't know my first post went through
[email protected] said:
i folowed all this here's the screenshots idk man i'm either caveman status or coding Ain't for me
Click to expand...
Click to collapse
check the next message
[email protected] said:
i folowed all this here's the screenshots idk man i'm either caveman status or coding Ain't for me
Click to expand...
Click to collapse
Your problem is clear.
you typed the command
fastboot flash recovery recovery.img
for that command to work, you would have to have a file named recovery.img in your:
C:\Program Files\WindowsPowerShell\Minimal ADB and Fastboot\ folder.
You do not have an image file named recovery.img, and your image files are not saved in the correct folder.
See this step in the instructions ?
Read it carefully, especially the sentence I have highlighted in red:
8. On your PC, open a command prompt or power shell in the folder where your adb and fastboot executables reside. You should place the newtwrp.img and root_boot.img into this folder.
If you need to download the files:
root_boot.img --> https://androidfilehost.com/?fid=673956719939818308
newtwrp.img --> https://drive.google.com/file/d/1Gz5...w?usp=drivesdk
Click to expand...
Click to collapse
Did you place the newtwrp.img and root_boot.img into that folder ?
done now what battery pull or factory data reset(aka boot to twrp?)
Click to expand...
Click to collapse
tecknight said:
Root your LG Aristo 2 from stock, remove forced encryption, and install TWRP and Magisk
1. Go to Settings->General->About Phone->Software Info. Click on Build Number 7 times. You have now enabled Developer Options
2. Go to Settings->Developer Options and Turn ON both OEM Unlock and USB debugging
3. Shut down your phone.
4. Plug one end of a USB cable into your PC, but do not plug the other end into your phone yet.
5. Press and hold Vol - on the phone.
6. Connect the unconnected end of the USB cable to your phone while still holding Vol -.
7. Once you see some text in very small letters on your phone, release Vol -. You are now in fastboot mode.
8. On your PC, download the following files:
root_boot.img --> https://androidfilehost.com/?fid=673956719939818308
newtwrp.img --> https://drive.google.com/file/d/1Gz5C9AZVilARyLIKm4bHy2BRWaFqkiMa/view?usp=drivesdk
9. Place both files into the folder where your adb and fastboot executables reside. Make sure they are named exactly as listed above.
10. Open a command prompt or power shell in the same folder we just placed the image files into.
Type the following in the command prompt or power shell session:
fastboot devices
You should see:
<SerialNumofPhone> fastboot
11. Type this:
fastboot flashing unlock
fastboot will say this will wipe your data. Tell it to continue.
12. Now that you are unlocked, flash the rooted boot image:
fastboot flash boot root_boot.img
13. Now flash TWRP:
fastboot flash recovery newtwrp.img
14. Now reboot back to Android:
fastboot reboot
15. Once Android boots up, go to the command prompt or power shell session on your PC and type:
adb devices
You should see:
List of devices attached
<SerialNumofPhone> device
16. Before booting into TWRP, make sure to download these two files and copy them to your phone's Download folder:
Magisk-v16.0.zip --> https://github.com/topjohnwu/Magisk/releases/download/v16.0/Magisk-v16.0.zip
no-verity-opt-encrypt-6.0.zip --> https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-6.0.zip
17. Once those files are in place, go to your command prompt or power shell and type:
adb reboot recovery
Your phone will now boot into TWRP for the first time.
18. Swipe to allow modifications.
19. If TWRP asks for a password, press the back key to get to the main TWRP screen.
20. Select WIPE then Format Data. Swipe to confirm.
21. Go back to main TWRP screen and select Reboot then Recovery
This should force an unencrypted data partition. TWRP will boot back up again.
22. Now select INSTALL, then browse into the Download folder and select the
no-verity-opt-encrypt-6.0.zip, then select Add more zips and select the Magisk-v16.0.zip.
23. Swipe to confirm flash. TWRP will change the boot image to allow data to be unencrypted and also will install Magisk on your system.
24. From the main TWRP screen, select Reboot then System.
Your phone will boot back into Android. Your phone is now rooted and has TWRP and Magisk installed.
Click to expand...
Click to collapse
i had them in right place forgot they had number in () after it i changed it im good now what pull battery or hard reset
nevermind i figured it out all thanks bro
[email protected] said:
i had them in right place forgot they had number in () after it i changed it im good now what pull battery or hard reset
Click to expand...
Click to collapse
nevermind i figured it out your a life savr yo
---------- Post added at 05:30 PM ---------- Previous post was at 04:57 PM ----------
[email protected] said:
i had them in right place forgot they had number in () after it i changed it im good now what pull battery or hard reset
Click to expand...
Click to collapse
nevermind i figured it out your a life savr yo ill send screenshts when i finally get ungitty i bbeen workin on this for awhile
many many thanks to you @tecknight's
[email protected] said:
nevermind i figured it out your a life savr yo
---------- Post added at 05:30 PM ---------- Previous post was at 04:57 PM ----------
nevermind i figured it out your a life savr yo ill send screenshts when i finally get ungitty i bbeen workin on this for awhile
many many thanks to you @tecknight's
Click to expand...
Click to collapse
Glad it finally worked out. I was wondering there for a second
tecknight said:
Glad it finally worked out. I was wondering there for a second
Click to expand...
Click to collapse
Now if I can just figure out why root only works for certain apps like I downloaded a reboot to recovery app and it says I need and then some Root Checker App Store saying I haven't I don't is that have to do with the DM Verity option cuz I would rather be able to have Superuser throughout I don't really care about the whole verity thing
---------- Post added at 04:03 AM ---------- Previous post was at 03:46 AM ----------
Hey man I just want to thank you again for taking the time to help a greenhorn like me I was also wondering why root only works for certain apps is that because of the DM Verity option and if it is you know how I can just have root throughout I don't really care about getting the over-the-air updates and what not I just want awesome root access throughout and if you know anywhere where a greenhorn like me could start and you know in the learning process that would be awesome and I appreciate everything I probably should have stuck with coding in high school I probably be a whiz by now
[email protected] said:
Now if I can just figure out why root only works for certain apps like I downloaded a reboot to recovery app and it says I need and then some Root Checker App Store saying I haven't I don't is that have to do with the DM Verity option cuz I would rather be able to have Superuser throughout I don't really care about the whole verity thing
---------- Post added at 04:03 AM ---------- Previous post was at 03:46 AM ----------
Hey man I just want to thank you again for taking the time to help a greenhorn like me I was also wondering why root only works for certain apps is that because of the DM Verity option and if it is you know how I can just have root throughout I don't really care about getting the over-the-air updates and what not I just want awesome root access throughout and if you know anywhere where a greenhorn like me could start and you know in the learning process that would be awesome and I appreciate everything I probably should have stuck with coding in high school I probably be a whiz by now
Click to expand...
Click to collapse
You need to run Magisk Manager. The icon should be on your Android desktop. Once you run it, Magisk should secure root. After that when an application requests root, Magisk will pop up asking if you want to grant root access to the app. icon looks like this:
If you can't find the icon, download and install the app from here:
https://github.com/topjohnwu/MagiskManager/releases/download/v5.7.0/MagiskManager-v5.7.0.apk
tecknight said:
You need to run Magisk Manager. The icon should be on your Android desktop. Once you run it, Magisk should secure root. After that when an application requests root, Magisk will pop up asking if you want to grant root access to the app. icon looks like this:
If you can't find the icon, download and install the app from here:
https://github.com/topjohnwu/MagiskManager/releases/download/v5.7.0/MagiskManager-v5.7.0.apk
Click to expand...
Click to collapse
Downloadzip patch boot image or direct download
[email protected] said:
Downloadzip patch boot image or direct download
Click to expand...
Click to collapse
When you launch Magisk Manager, you should see a dialog like this:
If you followed the Root your Aristo 2 from stock instructions correctly, you will have green check boxes at the top, Magisk is already installed.
If you don't have the green check marks, click install, then install again, then Direct Install (Recommended). Once the install is complete, any apps you have that request root access, will cause this dialog to pop up:
When it pops up, select GRANT, and your app will have root access.
If you already had the green check marks and did not have to install Magisk directly, touch the 3 horizontal lines in the upper left corner. You will see this:
Now select Superuser. You will see something like this:
Any apps that have requested root access should be listed. You can turn on root access for any of these apps by dragging the switch to the right
tecknight said:
TAT TecKnight's Aristo 2 Tutorials series
Restore your Aristo 2 to the latest factory firmware using LG Bridge
Click to expand...
Click to collapse
Thanks for the tutorial, honestly it did allow me to reinstall the same update/software on the phone successfully. Unfortunately my issue appears to be phone specific (even after a successful reset and attempting again it simply won't accept the connection to the tmobile network after an unlock was made) and there appears to be nothing else I can do. I've exhausted all resources.
TheDerekHarper said:
Thanks for the tutorial, honestly it did allow me to reinstall the same update/software on the phone successfully. Unfortunately my issue appears to be phone specific (even after a successful reset and attempting again it simply won't accept the connection to the tmobile network after an unlock was made) and there appears to be nothing else I can do. I've exhausted all resources.
Click to expand...
Click to collapse
There is a T-Mobile specific Aristo 2 that just got released.
I think T-Mobile is calling it the Aristo 2 Plus, but the hardware is identical.
Model number is X212TAL
You might try flashing that image to your phone
Install a specific .KDZ image to your LG phone using LGUP
TAT TecKnight's Aristo 2 Tutorials series
Install a specific .KDZ image to your LG phone using LGUP
Requirements:
An LG phone
A PC running Windows with an internet connection
A USB cable.
Note: This procedure will restore all of your partitions to stock for the firmware image you select. This means you will lose your rooted boot image (and root), TWRP and Magisk. This procedure will even work when your phone is not able to boot properly. As long as the bootloader is loading (ie: something is displaying on the screen when you power it up), LGUP should be able to image your phone. However, LGUP does not restore the flashing or oem lock state. If your phone was unlocked, it will stay that way.
1. If you don't already have LGUP installed on your PC, complete this procedure:
Install LGUP Dual Mode(Dev/User) on your Windows PC2. If you don't already have a .KDZ file that you want to image your phone with, go here:
https://lg-firmwares.com/lg-lmx210ma-firmwares/firmwares/and download one.
3. Power OFF your Phone.
4. Connect one end of the USB cable to your PC.
5. Press and hold Volume + on the phone. Connect the other end of USB cable to your phone while still pressing Volume +.
6. Download Mode should appear on the phone, and then change to Firmware Update.
7. Launch LGUP. It should detect your phone. You should see a screen resembling this:
8. In the lower section, to the right of File Path, click on the ..., then browse to and select your .kdz file. Your screen should now resemble this:
9. Make sure REFURBISH is selected, then click Start to flash your phone.
Please hit the Thanks button at the bottom of this post if you appreciate my work.
_________
Change Log:
7/5/2018 Moved actual LGUP installation to a separate tutorial. This tutorial now refers to that tutorial if LGUP is not already installed on PC.
6/30/2018 Created initial procedure.
Code:
[B]DISCLAIMER[/B]
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
**All credits for this guide go to Denver Alfito Anggada and Realme 3 pro Indonesia Group. I am just sharing it here for the benefit of those people who are not on Telegram**
UNLOCK BOOTLOADER
1.Download the In depth test APK (see attachment)
2.Open the In Depth Test application
APK then tap In Query Application Status
Request Submission then
wait about 5 minutes
4. Tap the back button in the left corner
top then reopen
In Query Application status
5. When "Review Sucessful " appeared, tap
start in depth test.
6. The device will then
enter fastboot, then plug the
device to PC. Download and install
fastboot (https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads/)
then move the folder named
"platform-tools" to the desktop
(recommended).
7. Open the platform-tools folder
then right-click +shift, then select
open command window here (Win
7) or Open Windows
Powershell (Windows 10)
8.a. For Windows 7, you must have
installed NET Framework
4.5. Type "fastboot flashing unlock "
b. For Windows 10, type
"./fastboot flashing unlock "
9. Then, press the volume button
to UNLOCK BOOTLOADER
10. CONGRATULATIONS! YOU HAVE
SUCCESSFULLY UNLOCKED YOUR
BOOTLOADER
HTML:
<iframe width="560" height="315" src="https://www.youtube.com/embed/mZMVohIuOYU" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
TWRP
**INTERNAL MEMORY WILL BE WIPED! BACKUP BEFORE PROCEEDING**
11. Turn off your device
12. Hold the volume key
-down + power to device
-go to fastboot
13. Plug the device into a PC / Laptop
14. Download recovery.img (https://drive.google.com/file/d/1z8Mv2IBstJchXlbsHpL-Xxup2Xr_O7gR/view)
Move the recovery file that you have downloaded into the folder platform-tools
15. Inside the folder, Shift + Right-click then select open command window here (Windows 7) or open Windows Powershell (10)
16.
a. type fastboot flash recovery.img (Windows 7)
b.
type ./fastboot flash recovery.img (Windows 10)
17. After getting OKAY written, Continue to install VBMETA (see attachment)
18. Move the vbmeta.img file into the platform-tools folder
19. Return to Windows Powershell /Command prompt then type fastboot - disabled-verity - vbmeta flash-verification-enabled vbmeta.img (Windows 7)
./fastboot - disabled-verity - vbmeta flash-verification-enabled vbmeta.img (Windows 10)
20. Press the volume button to Recovery then press power to confirm
21. After entering Recovery, make sure the device is still plugged in,the select wipe then FORMAT DATA, type yes, then tap back and reboot to recovery.
22. After returning to recovery, copy Charlie Decryption by Nitish (see attachment) to your device through computer
23. Flash fix and VOILA! you successfully installed TWRP on your device
INSTALL GSI
**ONLY FLASH A/B GSI**
24. To flash GSI, enter the GSI file on your device (make sure already in the img format, if not yet, try extracting first.
25. Then, in TWRP, press install, then open the file location you, if it doesn't appear, press install the image below right,then tap the file
26. Tap System Image and slide to flash
27. VOILA YOU HAVE SUCCESSFULLY FLASHED GSI ON YOUR DEVICE
Some GSI's you can try:
AOSIP: https://sourceforge.net/projects/il.../AOSiP-9.0-GSI-arm64_ab-20190604.img/download (or whichever is latest)
Bootleggers:https://androidfilehost.com/?fid=1395089523397961183 (or whichever is latest)
Havoc OS:https://androidfilehost.com/?fid=6006931924117888100
MAGISK
Download and extract patched image.tar (https://drive.google.com/file/d/1W1DYJJH6g7AgtT3SCCDdtag1u_F9TMX-/view?usp=drive_open)
Unlock bootloader (if you haven't)
Place all extracted images in ADB tool’s folder.
Then open a CMD window inside that folder. To do that, Shift + Right click on any empty white space inside the folder and then select Open command window here.
Connect your Android device to the PC. Type the following into the command window to boot your device into bootloader/fastboot mode:
adb reboot bootloader
If your device asks for permission to “Allow USB debugging”, tap OK.
Once your device boots into bootloader mode, type these into the command line.
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Reboot device into system
Done
if you boot on gsi you will get full mode magisk (able to use module )
if you boot on colorOS you will get core mode magisk (not able to use module )
if you boot GSI with magisk , install magisk module named SafetyPatch , this will give you safety net passed
*THE END*
Wow. Thanks a lot bro. Anyway have you tried the gsi rom? What knid ofbugs on realme 3 pro? Some says fingerprint not work, etc.
matrix0807 said:
Wow. Thanks a lot bro. Anyway have you tried the gsi rom? What knid ofbugs on realme 3 pro? Some says fingerprint not work, etc.
Click to expand...
Click to collapse
Fingerprint/pin/pattern not working
Problems with making calls (you can make call but cannot end it) I think it is related to VoLTE
Bluetooth music (Potential fix: Go to Vendor/Overlay/BluetoothResCommon.apk delete this apk, then reboot...BT music works...) need confirmation
Bluetooth incall audio
Confirmation
Is this process working successfully?
Yes many people have followed this method
Hb20032003 said:
Fingerprint/pin/pattern not working
Problems with making calls (you can make call but cannot end it) I think it is related to VoLTE
Bluetooth music (Potential fix: Go to Vendor/Overlay/BluetoothResCommon.apk delete this apk, then reboot...BT music works...) need confirmation
Bluetooth incall audio
Click to expand...
Click to collapse
I hope I can add busybox or Xposed modules without bricking/bootlooping my phone ?
Failed fastboot commamd
I am getting failed (write to device failed (too many links)) when using fastboot command please help
How to relock bootloader
TWRP corrupted my device when I flashed now don't wanna take more risks. How to relock the bootloader please
failed (write to device failed (too many links))
Muktesharyan said:
I am getting failed (write to device failed (too many links)) when using fastboot command please help
Click to expand...
Click to collapse
I was facing the same issue on my Windows 10. To solve the issue run the same command in a windows 7 PC. It worked for me 100%. i wasted the entire day searching for the solution. but switching to good'ol windows 7 pc fixed it.
Can someone help me..I'm stuck after the following command..
./fastboot - disabled-verity - vbmeta flash-verification-enabled vbmeta.img
Command prompt says unknown command -
PS: I modified like this.. ./fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img everything went smooth, but rootchecker says no root access. What might be the problem?
PS: I run magisk app, now it's been rooted.
Edit: Magisk installation is lost after sometime. No root access anymore. Guide need update. Had to follow other method. Thanks to @4j17h for helping me.
Is it possibleto unlock the bootloader without the depth test apk part?
Okay I can enter TWRP after following the first part of the guide....
until I followed the Magisk guide, then I cant enter TWRP anymore...
Also, does anyone knows how to remove that irritating red flashing saying that you rooted your device?
Hb20032003 said:
Fingerprint/pin/pattern not working
Problems with making calls (you can make call but cannot end it) I think it is related to VoLTE
Bluetooth music (Potential fix: Go to Vendor/Overlay/BluetoothResCommon.apk delete this apk, then reboot...BT music works...) need confirmation
Bluetooth incall audio
Click to expand...
Click to collapse
Hi,
I am trying to delete BluetoothResCommon.apk , but it says file system is read only , Can someone help me out here.
Regards
Need help
Hi, everybody. Really need help.
There is a phone Realme X Lite. Write that it is Realme 3 Pro for the Chinese market, as well as firmware.
My version was: RMX1851_11_A.05
Tried to flash RMX1851EX_11_OTA_0150_all_2Zfcensdoezk.ozip, recovery gave an error, *_0140_* wrote that the current version is newer.
In depth test APK on the version out of the box wrote that this version of the phone is not supported, so the bootloader could not unlock.
But in the official website came across an offer to join the testing of Android Q
r1.realme.net/general/20190522/1558492614147.pdf
There are two files, the second for rollback.
I installed P2Q, everything went well, but the SnapDragon camera is used and it is terrible if there is not enough light. In depth test is not even installed, apparently not supported in the new version.
I decided to roll back, chose in Recovery Q2P archive, there were no errors, but after rebooting the phone hangs on the initial screen saver and after 10 minutes throws in the recovery with the error "Data error, select wipe data to recovery system". Wipe doesn't help. The same with other archives for Realme 3 Pro.
Also found RMX1851_11_A.12_190423_abecd1fa.ofp for firmware via MsmDownloadTool, but it requires authorization and support refuses to call login details.
Can who faced a similar problem on this or other phone.
Please help, pay for the time spent =)
do you have tutorial to remove bloatware/pre-installed in RM 3 Pro ?
No bootloader
Hi, I tried to unlock the bootloader of my Realme 3 Pro on latest version A15, but something went wrong after the Depth Test app.
When I try to boot the bootloader, it only shows me a monkey icon, with letters in chinese (I guess), with something like 6 10 written, then it reboot.
Tried to install stock A14, but nothing changed.
Would be glad if someone know a solution.
jayroulm953 said:
do you have tutorial to remove bloatware/pre-installed in RM 3 Pro ?
Click to expand...
Click to collapse
If you're rooted then no worries, just use TiBu to uninstall all those bloatwares.
Samdroid18 said:
If you're rooted then no worries, just use TiBu to uninstall all those bloatwares.
Click to expand...
Click to collapse
without root ? no chance ?
Hello...!!!! Do you know why the phone does not go into fastboot mode when you start the depth test? It restarts in system mode. Thank you.
Pasku21 said:
Hello...!!!! Do you know why the phone does not go into fastboot mode when you start the depth test? It restarts in system mode. Thank you.
Click to expand...
Click to collapse
I have exactly the same problem, I don't know what to do...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
This is a customised version of TWRP specifically for the Blackview BV9100!
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now voided.
*
* I am not responsible for bricked devices, a meteorite crashing into your house,
* dead SD cards or thermonuclear war, YOU are choosing to make these modifications,
* and if you point the finger at me for messing up your device, I'll just ignore you.
*
*/
What works?
* Basic functions (Boot, Touch, ADB, Mount (internal/external), etc)
* Data decryption
What's broken?
* You tell me.
IMPORTANT - Disable dm-verity with the following fastboot command, or the recovery won't boot!
Make sure you use the vbmeta.img from stock rom!
Code:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
Downloads
Click here!
Device sources
Need help?
BV9100 Telegram Community
TWRP 3.5 - 28/02/2021
Download
Changelog:
Spoiler: Changelog
- Sync with latest TWRP changes
- Update encryption blobs
- Fix MicroSD/OTG mounting issue
Reserved #3
@bengris32
works but im unable to mount micro sd nor a usb stick in exfat nor making 2 partitions on one use (over 32gb) in 16k partitions less than 32 gigs.
may i ask how or where did you obtain the file?
mexamilian said:
@bengris32
works but im unable to mount micro sd nor a usb stick in exfat nor making 2 partitions on one use (over 32gb) in 16k partitions less than 32 gigs.
may i ask how or where did you obtain the file?
Click to expand...
Click to collapse
I didn't "obtain" the recovery, I made my own device trees for it, and built it from source.
As for the sdcard/usb mounting issue, I'll look into it.
@bengris32
Thanks for share
I noticed you are using BV9100_EEA_M860A_V1.0_20200430V19 in source files Where can i get BV9100 latest FW for non-EEA(non EU vs). Im on NON-EU version *NON-EEA* - notEU_BV9100_M860A_V1.0_20190910V2. Cant get my hands on their latest OTA updated FW. Maybe that's my problem? Does it even matter if its EEA on non EEA i mean they both run on same mk6765 platform.
There are 2 files i could find from official source, EU and non-EU versions, can be found here https://bbs.blackview.hk/viewtopic.php?t=532355 (version 20190910V2) kinda old but there is also the latest FW that goes OTA after u check for FW updates on bv9100. Blackview did not provide more recent updated one. Been working at it since Wednesday spending pretty much whole days figuring this out and back at it again atm
Not seeming to get this to work, but I'm not sure I know what I'm doing.
I took careful notes about what I did, anything look wrong wih the process?
First boot
► minimal set up then enable developer mode
(Settings 🞂 System 🞂 Advanced 🞂 About phone
▻ tap on "Build number" until unlocked, maybe 8 times
unlocks "Settings 🞂 System 🞂 Advanced 🞂 Developer options" menu
)
► In Developer options menu
▻ Select OEM unlocking (enter system password / pin)
▻ Turn on USB debugging (without cable attached)
► Connect USB cable
► On computer: "adb devices"
► On phone "Allow debugging" prompt comes up, allow it
► On computer: "adb devices"
▻ shows device "BV9100NEEA000..."
► Disconnect USB cable
► Power off phone
► Power on phone with volume down button pushed
► Connect USB cable
► On computer: "adb reboot bootloader"
► On computer: "fastboot devices"
▻ shows device "BV9100NEEA000..."
► On computer: "fastboot flashing unlock"
▻ computer shows "(bootloader) Start unlock flow"
▻ phone shows tiny text prompting for push volume up to allow
▻ push volume up
▻ computer shows "OKAY [ 23.545s]" (and some other stuff)
► On computer: "fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img"
▻ using vbmeta.img from blackview forum link in post 6
▻ computer shows (about) OKAY ... sending ... OKAY ... writing ... OKAY
► On computer: "fastboot flash recovery recovery.img"
using recovery.img 3.4.0 linked from first post
▻ computer shows (about) OKAY ... writing ... OKAY
► On computer: "fastboot reboot"
▻ computer shows "rebooting..."
▻ phone shows tiny message about unlocked bootloader and delays boot 5 seconds
► Phone boots back into new system wizard
► Re-enable dev mode and reallow USB debugging
► On computer: "adb reboot recovery"
▻ seems to boot into an Android standard recovery, not TWRP
► Phone regular boot shows nothing different
neccowafer said:
Not seeming to get this to work, but I'm not sure I know what I'm doing.
Click to expand...
Click to collapse
What model of phone and FW are u running. I know u posted " BV9100NEEA000" but do u have the right FW on it that came witht he phone? There are 2 versions of this phone also FW files on official site are not updated to latest OTA update. Official FW for eu and non eu can be found here, but its old.
https://bbs.blackview.hk/viewtopic.php?t=532355 You can flash the older FW back and try again. If u have the original hardware FW on ur EU model phone then it could be possible for you
Ive made a post asking for the files, my message needs to be approved as a new registered user. You can bookmark the link below and wait for my post to appear and the files when and if they provide em.
official firmware - Page 2 - bbs.blackview.com
bbs.blackview.hk
Currently i reverted back to latest OTA stock FW till i get those new files.
I am at a standstill on the proper order to root and get twrp on this non eu model phone.
Magist guide says i need to flash to recovery partition (u need original to patch which i cant have without TWRP on the phone in the 1st place) Then there is another issue of getting TWRP onto the device before rooting which again u need the original vbmeta.img, i can do with a blank one but the problem comes to TWRP then setting an encrypted password provided by bengris32 which his twrp is for EU model of the phone. Headache
I'm on non EU FW, BV9100_M860A_v1.0_20200722V3
You can get SP Flash Tool thats needed to flash this phones FW, here https://spflashtool.com/ which has the latest version shown as V5.1924. There is also v5.2044 which i dont know how and where it came out, can be found here https://forum.hovatek.com/thread-13970.html @Hovatek seems reputable after me digging around for the past 3-4 days https://forum.xda-developers.com/m/hovatek.5636663/
Assuming you have MTK Drivers installed. if not https://forum.hovatek.com/thread-16640.html or find official site.
Open up SP Flash Tool,
Go to tab Download
Point Download Agent to where SP Flash Tool is installed to the file "MTK_AllInOne_DA.bin"
Load up you FWs scatter file in the 2nd box/line "Scatter-loading File.
***IMPORTANT! In the graph table below MAKE SURE U UNCHECK the preloader box. This will help getting TWRP as recovery later on.****
Klik box up top with green arrow that says "Download"
Phone is in off state.
Attach your USB cable to the phone, but NOT to the computer yet.
Hold VOLUME UP & DOWN at the same time then connect it to the PC.
On the SP Flash Tools you will see a long white bar on the bottom of the softwares window
It will turn RED then Yellow and will start flashing your phone.
You can RELEASE KEYS after you see the RED COLOR.
Once SP Flash Tools is done flashing a box will come up and say Done.
Close box, close SP Flash Tools.
Disconnect Phone from PC and Phone and u are on stock FW.
If u didnt uncheck the "preloader" box TWRP will not work on your phone
mexamilian said:
I'm on non EU FW, BV9100_M860A_v1.0_20200722V3
Click to expand...
Click to collapse
That's the same as mine: BV9100_M860A_V1.0_2020722V3, so I guess I'm waiting on BV to respond to your firmware update request.
neccowafer said:
Not seeming to get this to work, but I'm not sure I know what I'm doing.
I took careful notes about what I did, anything look wrong wih the process?
First boot
► minimal set up then enable developer mode
(Settings 🞂 System 🞂 Advanced 🞂 About phone
▻ tap on "Build number" until unlocked, maybe 8 times
unlocks "Settings 🞂 System 🞂 Advanced 🞂 Developer options" menu
)
► In Developer options menu
▻ Select OEM unlocking (enter system password / pin)
▻ Turn on USB debugging (without cable attached)
► Connect USB cable
► On computer: "adb devices"
► On phone "Allow debugging" prompt comes up, allow it
► On computer: "adb devices"
▻ shows device "BV9100NEEA000..."
► Disconnect USB cable
► Power off phone
► Power on phone with volume down button pushed
► Connect USB cable
► On computer: "adb reboot bootloader"
► On computer: "fastboot devices"
▻ shows device "BV9100NEEA000..."
► On computer: "fastboot flashing unlock"
▻ computer shows "(bootloader) Start unlock flow"
▻ phone shows tiny text prompting for push volume up to allow
▻ push volume up
▻ computer shows "OKAY [ 23.545s]" (and some other stuff)
► On computer: "fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img"
▻ using vbmeta.img from blackview forum link in post 6
▻ computer shows (about) OKAY ... sending ... OKAY ... writing ... OKAY
► On computer: "fastboot flash recovery recovery.img"
using recovery.img 3.4.0 linked from first post
▻ computer shows (about) OKAY ... writing ... OKAY
► On computer: "fastboot reboot"
▻ computer shows "rebooting..."
▻ phone shows tiny message about unlocked bootloader and delays boot 5 seconds
► Phone boots back into new system wizard
► Re-enable dev mode and reallow USB debugging
► On computer: "adb reboot recovery"
▻ seems to boot into an Android standard recovery, not TWRP
► Phone regular boot shows nothing different
Click to expand...
Click to collapse
Hi, this is because android restores the original recovery when the device boots, you must not let your device boot into android until you boot TWRP for the first time, repeat all of your steps, but when you "fastboot reboot", hold the volume up button to access the boot menu, then select recovery mode. Once your device boots into TWRP, it will automatically patch the rom to prevent the original recovery from being restored on boot up.
bengris32 said:
Hi, this is because android restores the original recovery when the device boots, you must not let your device boot into android until you boot TWRP for the first time, repeat all of your steps, but when you "fastboot reboot", hold the volume up button to access the boot menu, then select recovery mode. Once your device boots into TWRP, it will automatically patch the rom to prevent the original recovery from being restored on boot up.
Click to expand...
Click to collapse
I confirm on my non EU bv9100 M860A
kept holding like you said then typed fastboot reboot and still held a selection menu popped up with 3 option on black background, i released the key then selected recovery, pressed the vol down to accept then quickly release it and went back to holding volume up and son of the devil it worked thanks, now i go back to messing with magisk installation.
Question though,
once booted into recovery following what u just said above, should vipe data factory be done like other (lineageOS) require or not? if it work it works just maybe thats where i had my issue with no mount for microsd and external
@neccowafer i can link you the official FW so u can flash what i have?
Latest stock rom link of BV9100 - bbs.blackview.com
bbs.blackview.hk
get the non-EEA version and flash it follow your own steps you mentioned
EDIT: Just did wipe data button bottom right on button [WIPE] then did factory wipe.
How access to internal and MTP on reboot into recovery with buttons, still can get micro sd mount
Got a reply from official blackview admin
official firmware - Page 2 - bbs.blackview.com
bbs.blackview.hk
looks like there wont be any updates to A10 and over. Gonna be trying out different CFW and see how it does, i managed to get unofficial lineage-17.1-20201215 unofficial with test keys flashed
I just got one of these phones today and I'm having a bear of a time getting into it with adb to install TWRP and hopefully flash a new ROM. I tried to follow the detailed instructions from neccowafer (thank you for those!) earlier in this thread, but adb returns the device as unauthorized when in recovery mode.
This phone seems to have two recovery modes. One is accessed by booting while holding vol-down and the other is loaded when you boot holding vol-up and choose recovery from the menu.
In either recovery mode, I run adb devices and get
List of devices attached
BV9100EEA00016800 unauthorized
While booted to Android, I run adb devices and get
List of devices attached
BV9100EEA00016800 device
I'm becoming a bit frustrated trying to figure it out on my own, and it's been a few years since I did any custom bootloader or custom ROM stuff with Android, so any help would be very much appreciated.
@JeffJK I have factory mode on my down key and recovery mode on up, you wanna do up. my model is NEEA
mexamilian said:
@JeffJK I have factory mode on my down key and recovery mode on up, you wanna do up. my model is NEEA
Click to expand...
Click to collapse
Oh good to know! I got the same error noted above in the up key mode, the unauthorized thing from adb. Any idea why?
did u enable dev mode then enabled usb debugging, boot loader unlocked?
when u got ur phone out of the box, skip everything and dont sim in, just skip things, make sure u dont set any pass and dont encrypt device, enable dev mode then enable debugging by tapping on ur build in settings all the way on bottom in about. make sure oem unlock is also enabled and greyed out if u done already so.
mexamilian said:
did u enable dev mode then enabled usb debugging, boot loader unlocked?
when u got ur phone out of the box, skip everything and dont sim in, just skip things, make sure u dont set any pass and dont encrypt device, enable dev mode then enable debugging by tapping on ur build in settings all the way on bottom in about. make sure oem unlock is also enabled and greyed out if u done already so.
Click to expand...
Click to collapse
Ah, I did set the phone up. Should I wipe and start over?
EDIT: I did a factory reset and booted into Android to turn on debugging, and even without setting up anything on the phone, encryption was enabled in the security settings and adb still lists the device as unauthorized while in recovery mode.
EDIT 2: Also tried wiping /data from the recovery mode menu, which put out the below lines but still did not allow adb access even after a kill-server
Code:
Formatting /data. . .
Formatting /cache. . .
Formatting /mnt/vendor/nvdata. . .
Data wipe complete.
@JeffJK To remove encryption meaning you had twrp installed and made it work or stock os?
Boot into recovery Format data / factory reset This will remove encryption and delete all files stored in the internal storage, as well as format your cache partition (if you have one).
*DONT set any passwords for lockscreen, dont login to google, pay attention to not encrypt device when setting up. just basic skip u dont even need wifi or sim in phone
Dont forget to unlock ur bootloader before flashing or doing anything. Follow post #7 thats exactly how you would do it then read up on post #10 and #11 and it will work.
Also did you install USB drivers?
Get android usb drivers https://developer.android.com/studio/run/win-usb
if that didnt work try the one below,
https://forum.hovatek.com/thread-16640.html (need to register) you want the " Auto Mediatek USB VCOM Drivers Signed"
If you messed up you just flash your legit FW back to stock and follow post #7 10 and 11
mexamilian said:
@JeffJK To remove encryption meaning you had twrp installed and made it work or stock os?
Boot into recovery Format data / factory reset This will remove encryption and delete all files stored in the internal storage, as well as format your cache partition (if you have one).
*DONT set any passwords for lockscreen, dont login to google, pay attention to not encrypt device when setting up. just basic skip u dont even need wifi or sim in phone
Dont forget to unlock ur bootloader before flashing or doing anything. Follow post #7 thats exactly how you would do it then read up on post #10 and #11 and it will work.
Also did you install USB drivers?
Get android usb drivers https://developer.android.com/studio/run/win-usb
if that didnt work try the one below,
https://forum.hovatek.com/thread-16640.html (need to register) you want the " Auto Mediatek USB VCOM Drivers Signed"
If you messed up you just flash your legit FW back to stock and follow post #7 10 and 11
Click to expand...
Click to collapse
I couldn't get TWRP because adb still reads the device as unauthorized. I wiped the data while in recovery mode, booted to the"Welcome" screen, and when I skipped everything in the setup wizard, the settings still show encryption as enabled, and I had no option to enable or disable it at any point. Bootloader also still showed as unlocked. This seems like a very unusual problem! I have drivers but will try the vcom ones.
if u are able to get into adb and fastboot then u dont need the VCOM drivers.
On device use "Revoke USB debugging authorizations" in "Developer Options"
then reconnect to phone to cable then pc
@JeffJK
Would you do me a favor, my current connected device sn is 123456789ABCDEF.
I messed up with flashing some roms and wiped the nvnand partition without making a backup of official stock one( didnt know about nvnand till issues started happening), been working on fixing S/N and device connected via adb to stock, currently have tee key and google key in red as overlay, i know ways of getting rid of it but id rather have the original back.
need some structural info, you can replace last 5 number from your serial with XXXXX if u want. i have some files i managed to scrape up digging around on how tos, just clueless on how to get tee key/google key and serial back onto device with proper format.
go into your phones setting>system>advanced>About phone. Post what what you see in the following:
*SIM Status (sim slot 1) klik on in and scroll down to EID (mine says unknown) and post (hide last 4 or so numbers but include full length) i will need to know what to look for when flashing mine back to my phones original status
*Model & Hardware klik on it my says for Model: BV9100 Serial number says 0123456789ABCDEF (again hide last 4 or 5 so i have an idea of what i need to look for in my files)
*WI-Fi MAC address and Bluetooth address all i need from this is do they match or are different, also post last 2 digits/bits in wifi and bt addresses ( i need this for to figure if multicast)
I REALLY RECOMMEND you write this info down before messing with roms and flashing or ull end up like me with blank IMEI (managed to flash fix it), serial of 123456789ABCEDF(still cant fix), and a permanent tee key google key in red(still cant perma fix, have to always remove factorymode). you can watch tutorials on how to use "Mtk Droid Tool to backup your nvnand IMEI serial, make a scatter file on updated OTA latest update of stock BV9100 rom (its really well optimized after trying Lineage unofficial 17.1, HavokOS 3.12 (I have files and sources)
I do not know where the official source for MTK DROID TOOLS is (the latest version i have found is Mtk_Droid_Tool_v2.5.3B some say 2.5.3 I have both if needed source to https://forum.hovatek.com/thread-15665.html) (bitdefender total security says clean on my pc before i installed, it does run sluggish on 10850k with 128gigs ram on nvme) I do recommend u scan with your AV and upload it also to https://www.virustotal.com/gui/ and any other files you get just do be safe
Heres a little write up on how to do so as i cannot cause my phone doesnt have proper setup on stock after a mess up
"
Requirement : Your Google android device should be rooted.(Officially provided with source if u need, DONT root it via the mtk droid tools, there is an option. Go with magisk official https://github.com/topjohnwu/Magisk/releases/tag/v21.2 After you have TWRP installed from this thread, download the 21.2 magisk zip file and install inside twrp reboot and configure it)
Download and open MTK droid tools application.
Enable USB debugging mode on your device. Settings > Developer Option > Click USB debugging mode.
SKIP THIS UNLESS YOU HAVE ISSUES(let me know)Then connect your android smartphone to the computer. Your device will detect by MTK droid tools within few minutes. If your mobile phone is not detected, then you have to install USB drivers on your device first. Right click on the “InstallDriver.exe” and select “Run As Administrator” and then restart your computer to install USB driver.
Click IMEI/NVRAM to backup android IMEI and then click backup. Your android backup will be stored in BackupNVRAM folder.
Continue to the backup system, firmware, data and etc (Android ROM) select on Root, backup, recovery tab and backup tab. The process will finish within few minutes.
"
Greetings,
I've appreciated @Slikkster2k's terrific thread that explains and walks you through fastboot recovery of a OnePlus 9. To make it more convenient, I've taken his process and adapted @mauronofrio's OnePlus 8 fastboot ROM to post a fastboot ROM zip for the OnePlus 9.
PLEAE NOTE THAT FASTBOOT ROMS CAN ONLY BE USED IN DEVICES WITH AN UNLOCKED BOOTLOADER!!!
AND BE WARNED THAT YOU WILL WIPE INTERNAL STORAGE COMPLETELY.
THIS IS NOT MEANT FOR BRANDED DEVICES, OR TO SWITCH REGIONAL TYPES, OR AS AN UPGRADE PATH.
THIS IS THE LAST DITCH ATTEMPT BEFORE USING AN MSM TOOL TO GET YOU A BOOTING DEVICE...
Instructions:
- On your PC, install bootloader drivers for OP9 (I used the Universal ADB driver found here: https://adb.clockworkmod.com/) and afterwards, you may need to use Device Manager in Windows' control panel to "update driver" for an unrecognized OP9 in Bootloader and Fastbootd modes.
- Ensure you're using the LATEST version of SDK platform tools (from Android Studio) on your PC or you might be stuck at a later step (specifically, when rebooting to Fastbootd)
- On your PC, download the Fastboot ROM zip from the download link below.
- On your PC, unzip downloaded file
- On your PC, navigate to its now-uncompressed folder
- Reboot your OnePlus 9 to bootloader mode. From a crashed state, you might need to hold down the power button for an ungodly amount of time (think 30 seconds) to fully shut down. Then hold down power and both volume buttons until you see the Bootloader screen
- Connect the OP9 to your PC
- On your PC in the uncompressed folder, double-click cmd.bat
- In the PowerShell window that opens, type fastboot devices
=if you see a small string of characters, you're good
=if you only get another prompt, you need to install adb drivers (see 1st step) before going any further
- type flash-all_slotb.bat
- type y
= because there's almost NO CIRCUMSTANCE that a fastboot ROM successfully flashes without wiping your data. As in deleting, formatting, absolutely annihilating everything on your device. Now if you have a perfectly functional device, then maybe you can avoid wiping. But that's not why you're here, are you? You've buggered your phone and are desperately looking for someway to get it to boot normally, before calling OnePlus and begging for an MSM tool. So if you're here, take a deep breath and kiss your data goodbye.
= flashing the ROM to slot B and then booting slot B gives you a better shot at one-step flashing success. It's been my experience that f you flash to slot A, some files simply don't flash and then you're left having to flash to slot B anyways.
= at some point, your OP9 will reboot to Fastboot mode for more flashing...but if you happen to see <awaiting any device> for several minutes, it means that the OP9 in Fastboot mode is not being recognized by Windows due to a driver issue, and for those unlucky folks, go to Post #2
= if your OP9 continues to blissfully flash in Fastboot mode, just let it go...
- Success is when you see a final reboot, and the twirling dots of a normal OOS boot, at which point you can finally unplug your OP9 from your PC.
Optional steps, at end:
Once you've successfully booted to 11.2.2.2, I would recommend that you download the latest full OTA from OnePlus' support page (11.2.9.9 is in the DOWNLOAD LINKS, below) and place it on your internal SD card's "root" directory (note that this is not the true root directory of internal storage accessible only if you are rooted with Magisk)
Then Settings>system>system updates and tap the gear icon (top right of screen) to do a local upgrade.
After Fastboot ROM flashing on slot B, this local upgrade ensures that slot A will be overwritten by the full stock ROM, ending whatever badness was on slot A that led you to need a Fastboot ROM flash. So now, both slots A and B should have solid functioning ROMs.
Good luck!
DOWNLOAD LINKS:
Fastboot ROM 11222AA zip:
Fastboot OOS_11222AA_stock.zip | by reaper000 for OnePlus 9
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Stock Full OTA 11299AA zip
https://www.androidfilehost.com/?fid=7161016148664810093
Credits:
- @Slikkster2k
- @mauronofrio (please un-retire!)
++This post is ONLY for those unfortunate souls who see <awaiting any device> in Fastboot mode for minutes while following the Instructions in Post #1++
- Once your OP9 screen shows Fastboot mode and you see <awaiting any device> for several minutes
- hit CTRL C to stop the flashing process
- go to Device Manager in Windows and look for the yellow-triangled ! device. LE2115 -- that's your unrecognized Fastboot device
- right click it and select update driver
- select "Browse my computer for drivers" and then "Let me pick from a list..."
- select ADB interface (and you might further need to pick the Universal or Samsung Android device) and install it
- once that driver window closes, go back to the PowerShell window
- type fastboot devices
=if you see a small string of characters, you're good. Go to the last step!
=if you only get another prompt, you need to unplug the OP9 and then reconnect it. Since you just updated the driver, Windows should now recognize and engage the driver for the Fastboot mode OP9. Confirm this by looking for a small string once you again type fastboot devices
=if you still don't get a small string confirming device recognition, try updating the driver again. And again. Because, you know, Windows. If you never succeed in getting Windows to recognize the OP9 in Fastboot mode, you might need to try downloading another ADB driver. But you really can't go further in this flashing process till the OP9 is recognized in Fastboot mode. Only then can you go on...
- the last step! Type rescuefastbootd.bat to complete the flashing process in Fastboot mode. With any luck, your OP9 will now flash the 2nd set of images and then reboot normally, on OOS 11.2.2 in slot B, and you will see the orbiting dots of a normal OOS boot. When you do, you can unplug your phone from the PC. Success!!
OPTIONAL: if you're reading this before catastrophe, I would suggest that you ensure you have working drivers for both Bootloader and Fastboot modes. (I used the Universal ADB driver found here: https://adb.clockworkmod.com/) After driver installation on your PC, steps to do this look like:
- Settings>About Phone> tap Build number 7 times, then
- Settings>System>Developer Options>toggle Advanced Reboot.
- Hold the power button, select the 3-dot menu icon, tap Bootloader
- connect OP9 to your PC, and Windows 10 should install the right driver.
- On your PC, navigate to the Fastboot ROM downloaded unzipped folder.
- double-click cmd.bat and a PowerShell window opens.
- in the PowerShell window, type: fastboot devices
=if you get a small string of identifying characters, you're good.
=if you get nothing but a command prompt, you need to install adb drivers in Windows' Device Manager
- type: fastboot reboot fastboot
and your OP9 will reboot into Fastbootd mode; when you see a splash screen with a choice of languages...
- type: fastboot devices
=if you get a small string of identifying characters, you're good.
=if you get nothing but a command prompt, you need to install adb drivers in Windows' Device Manager (read over Post #2). Once that's done successfully (typing: fastboot devices and getting an identifying string), you want to reboot normally. Success!!
Yeah. Just in case.
Thank you
Nice write up, friend! Thank you for taking the time to do so.
reaper000 said:
Greetings,
I've appreciated @Slikkster2k's terrific thread that explains and walks you through fastboot recovery of a OnePlus 9. To make it more convenient, I've taken his process and adapted @mauronofrio's OnePlus 8 fastboot ROM to post a fastboot ROM zip for the OnePlus 9.
PLEAE NOTE THAT FASTBOOT ROMS CAN ONLY BE USED IN DEVICES WITH AN UNLOCKED BOOTLOADER!!!
AND BE WARNED THAT YOU WILL WIPE INTERNAL STORAGE COMPLETELY.
THIS IS NOT MEANT FOR BRANDED DEVICES, OR TO SWITCH REGIONAL TYPES, OR AS AN UPGRADE PATH.
THIS IS THE LAST DITCH ATTEMPT BEFORE USING AN MSM TOOL TO GET YOU A BOOTING DEVICE...
Instructions:
- On your PC, install bootloader drivers for OP9 (I used the Universal ADB driver found here: https://adb.clockworkmod.com/) and afterwards, you may need to use Device Manager in Windows' control panel to "update driver" for an unrecognized OP9 in Bootloader and Fastbootd modes.
- On your PC, download the Fastboot ROM zip from the download link below.
- On your PC, unzip downloaded file
- On your PC, navigate to its now-uncompressed folder
- Reboot your OnePlus 9 to bootloader mode. From a crashed state, you might need to hold down the power button for an ungodly amount of time (think 30 seconds) to fully shut down. Then hold down power and both volume buttons until you see the Bootloader screen
- Connect the OP9 to your PC
- On your PC in the uncompressed folder, double-click cmd.bat
- In the PowerShell window that opens, type fastboot devices
=if you see a small string of characters, you're good
=if you only get another prompt, you need to install adb drivers (see 1st step) before going any further
- type flash-all_slotb.bat
- type y
= because there's almost NO CIRCUMSTANCE that a fastboot ROM successfully flashes without wiping your data. As in deleting, formatting, absolutely annihilating everything on your device. Now if you have a perfectly functional device, then maybe you can avoid wiping. But that's not why you're here, are you? You've buggered your phone and are desperately looking for someway to get it to boot normally, before calling OnePlus and begging for an MSM tool. So if you're here, take a deep breath and kiss your data goodbye.
= flashing the ROM to slot B and then booting slot B gives you a better shot at one-step flashing success. It's been my experience that f you flash to slot A, some files simply don't flash and then you're left having to flash to slot B anyways.
= at some point, your OP9 will reboot to Fastboot mode for more flashing...but if you happen to see <awaiting any device> for several minutes, it means that the OP9 in Fastboot mode is not being recognized by Windows due to a driver issue, and for those unlucky folks, go to Post #2
= if your OP9 continues to blissfully flash in Fastboot mode, just let it go...
- Success is when you see a final reboot, and the twirling dots of a normal OOS boot, at which point you can finally unplug your OP9 from your PC.
Good luck!
DOWNLOAD LINK:
Fastboot OOS_11222AA_stock.zip | by reaper000 for OnePlus 9
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Credits:
- @Slikkster2k
- @mauronofrio (please un-retire!)
Click to expand...
Click to collapse
Thank you very much, if not for this I would have to wait for my device to arrive from oneplus(cancel my request).
Fireblast3 said:
Thank you very much, if not for this I would have to wait for my device to arrive from oneplus(cancel my request).
Click to expand...
Click to collapse
Glad to help.
Here's your next steps:
I would recommend that you download the full OTA of 11.2.4.4 from OnePlus' support page and place it on your internal SD card's "root" directory (note that this is not the true root directory of internal storage accessible only if you are rooted with Magisk)
Then Settings>system>system updates and tap the gear icon (top right of screen) to do a local upgrade.
After Fastboot ROM flashing on slot B, this ensures that slot A will be overwritten by the full stock ROM, ending whatever badness was on slot A that led you to need a Fastboot ROM flash.
Good luck!
reaper000 said:
Glad to help.
Here's your next steps:
I would recommend that you download the full OTA of 11.2.4.4 from OnePlus' support page and place it on your internal SD card's "root" directory (note that this is not the true root directory of internal storage accessible only if you are rooted with Magisk)
Then Settings>system>system updates and tap the gear icon (top right of screen) to do a local upgrade.
After Fastboot ROM flashing on slot B, this ensures that slot A will be overwritten by the full stock ROM, ending whatever badness was on slot A that led you to need a Fastboot ROM flash.
Good luck!
Click to expand...
Click to collapse
Thanks for the tip but the dam oneplus page is giving me this error "Parameter error"
Fireblast3 said:
Thanks for the tip but the dam oneplus page is giving me this error "Parameter error"
Click to expand...
Click to collapse
Try the direct link...?
https://oxygenos.oneplus.net/OnePlus9Oxygen_22.O.07_OTA_0070_all_2104122241_e0f2a4d74c3844b4.zip
reaper000 said:
Try the direct link...?
https://oxygenos.oneplus.net/OnePlus9Oxygen_22.O.07_OTA_0070_all_2104122241_e0f2a4d74c3844b4.zip
Click to expand...
Click to collapse
Thanks, I contact oneplus support and it seem like they are updating their Software Upgrade section.
Will this convert tmobile variant to global?
infamousvincci said:
Will this convert tmobile variant to global?
Click to expand...
Click to collapse
Let me quote the OP:
THIS IS NOT MEANT FOR BRANDED DEVICES, OR TO SWITCH REGIONAL TYPES, OR AS AN UPGRADE PATH.
It wasn't intended to convert Tmo to Global.
If I recall correctly, there were reports of softbricks in previous OnePlus devices when Fastboot ROMs were tried as conversion tools, necessitating either MSM tool deployment or return to manufacturer.
reaper000 said:
Let me quote the OP:
THIS IS NOT MEANT FOR BRANDED DEVICES, OR TO SWITCH REGIONAL TYPES, OR AS AN UPGRADE PATH.
It wasn't intended to convert Tmo to Global.
If I recall correctly, there were reports of softbricks in previous OnePlus devices when Fastboot ROMs were tried as conversion tools, necessitating either MSM tool deployment or return to manufacturer.
Click to expand...
Click to collapse
ooofff. gotcha. Thank you so much!
Fireblast3 said:
Thanks, I contact oneplus support and it seem like they are updating their Software Upgrade section.
Click to expand...
Click to collapse
I've provided an AFH mirror for OOS' full OTA 11.2.4.4AA for convenient download.
Also, the recommendation I gave you is also now added to the OP.
I appreciate this. It would have definitely helped me back when I had these issues. Now it's here. I'm honestly scared to flash anything on this device.
I've redone the original post to reflect OnePlus' publication of 11.2.7.7AA as a downloadable full OTA and provided a mirror on AFH
My device bricked
I'm sorry to hear that. I'm not sure how much I can help, but perhaps you can please provide details? (device model, what circumstances led you here, what version of oos, what you've already tried, etc)
Please upload to MEGA or Google Drive or actually anywhere else as AFH is so slow it gives me 3 days for estimated download time. Thank you. Somebody sending a mirror would be much appreciated.