Related
Hey guys,
just got my Xiaomi Mi A3 today, so i wanted to install TWRP and root the phone with Magisk.
Well my problem is that the device is now stuck in "fastboot" mode. I mean there are tons of tutorials outside, but they are different. So it is really hard to known, which one will work. There are a lot of tutorials which are describing the way with an unofficial .img and and TWRP Installer with it.
So what have i done so far:
1. Installed the needed ADB and Xiaomi drivers and downloaded "Android Platform Tools"
2. Unlocked the bootloader on the device --> so far everything was OK
3. Then i found an tutorial and it is saying that i should use the following command "fastboot boot twrp-3.3.1-0-laurel_sprout.img"
Unfortunately, if i am trying to enter that i am getting the following error: fastboot error: command failed (remote - unknown command)
So after that i was searching for an Tutorial on YouTube and found an different way.
The guy in the tutorial is using the command: "fastboot flash boot twrp.img"
Well, the end of the story is at the moment, it doesn´t matter how i want to reboot my device it always lands in "fastboot" mode.
Is there an kind soul outside, which can help me out to install twrp on my phone? Hopefully with an "CORRECT" Tutorial?
Thank you.
Edit# 1: If i enter the command "fastboot set_active b" my phone loads up and says "Can´t load Android System. Your data may be corrupt. And i can choose between Try again and factory data reset.
Edit# 2: Okay, i made some research and tried the following commands:
fastboot erase userdata
fastboot getvar all
fastboot erase boot
fastboot set_active b
fastboot erase boot
fastboot flash boot twrp.img
fastboot reboot
The phone booted now directly to TWRP.
Edit# 3: Okay, so as far as i understand, i wiped my stock rom with the command: fastboot flash boot twrp.img , because i didn´t switched the slot to "b" before, correct?
After my commands in "Edit# 2" i wiped everything and installed TWRP permanently to slot "b". Just went through TWRP a little bit and if i click on "Install" all Storage devices are at 0MB. So how do i get my stock ROM back?
My Problem is that this device already had this faulty Android 10 version when i bought that. When i firsted turned that on, the phone was showing me that an Android Update is available. But when i wanted to install that, it was saying this update is for Android 9. I think you know what i am talking about.
So what are my options now? Where do i get that stock rom back and how should i proceed? I also saw some posts here that an downgrade is not that good, because a lot of sensors will not work after that.
I was on the latest Android 10 March Security Patch and had the same problem. However, I was able to figure it out and made it work. Here's what I did:
1. Flash the latest Android 10 fastboot rom (search in XDA)
2. Download this modified boot image: https://drive.google.com/file/d/1-dCUenlLq4C-l-LJWQUsOFhlIRRAb5xI/view?usp=drivesdk
3. On fastboot, execute: fastboot getvar current-slot (make sure you are on slot A)
3. If not on A, execute: fastboot set_active a
4. Execute: fastboot flash boot (image name).img
5. Fastboot reboot (make sure to press volume + before hitting enter)
6. You are now booted to TWRP
7. Flash the TWRP Installer zip (can be found in XDA)
8. Wipe dalvik cache
9. Reboot to fastboot
10. Execute: fastboot set_active b
11. Execute: fastboot reboot
Let me know if this works for you! Hope this is a great help.
kevinxjen said:
I was on the latest Android 10 March Security Patch and had the same problem. However, I was able to figure it out and made it work. Here's what I did:
1. Flash the latest Android 10 fastboot rom (search in XDA)
2. Download this modified boot image: https://drive.google.com/file/d/1-dCUenlLq4C-l-LJWQUsOFhlIRRAb5xI/view?usp=drivesdk
3. On fastboot, execute: fastboot getvar current-slot (make sure you are on slot A)
3. If not on A, execute: fastboot set_active a
4. Execute: fastboot flash boot (image name).img
5. Fastboot reboot (make sure to press volume + before hitting enter)
6. You are now booted to TWRP
7. Flash the TWRP Installer zip (can be found in XDA)
8. Wipe dalvik cache
9. Reboot to fastboot
10. Execute: fastboot set_active b
11. Execute: fastboot reboot
Let me know if this works for you! Hope this is a great help.
Click to expand...
Click to collapse
Hey there,
first of all thank you for your reply
Unfortunately those steps were not working for me or i am misunderstanding something.
So i followed your steps:
1. Flash the latest Android 10 fastboot rom (search in XDA) - found that here https://forum.xda-developers.com/mi-a3/how-to/fastboot-rom-android-10-v11-0-8-0-march-t4069077
Unzipped the files to my platform-tools folder and started the "flash_all.bat" file. No errors so far -> after the last command "fastboot reboot" device automatically booted up and it stucked on the "mi" logo. In the thread which i have mentioned above a few people had the same problem and they were told to execute an factory reset.
So i went back to fastbood mode and typed in "fastboot erase userdata" - but nothing happended. So i was stuck at the "mi" logo.
Then i thought i will go on and follow the next steps:
2. Download this modified boot image: - downloaded that
3. On fastboot, execute: fastboot getvar current-slot (make sure you are on slot A)
3. If not on A, execute: fastboot set_active a
4. Execute: fastboot flash boot (image name).img
5. Fastboot reboot (make sure to press volume + before hitting enter)
6. You are now booted to TWRP Endresult: NO TWRP was booting straight away back to fastboot mode
What am i doing wrong? I just want to go back to my Androis OS with latest March Security Patch and Install TWRP permanently,so after that i can root it with Magisk.
Edit# 1: I was not using your modified boot image, i took that one: https://forum.xda-developers.com/showpost.php?p=82087765&postcount=3 and could boot into TWRP after that.
But anyways it seems that there is nothing on my phone, i still stuck at the "mi" logo and when i go to TWRP, everything is empty on the storage device. I mean if i go to the Button "Wipe" --> "then Swipe for factory reset" i get the following errors.
"Could not mount /data and unable to find crypto footer."
"unable to mount storage"
Current state of the device:
Booting normally: Stucks on "Mi" Logo
Holding Volume Down + Power: boots to "FastBoot Mode"
Holding Volume Up + Power: boots to "TWRP"
Edit# 2: Phone is alive again
Followed these steps below and managed to install TWRP permanently and get back my Android OS.
If you have fastboot, simply flash TWRP, boot to TWRP recovery, do a full wipe, including formatting using data. Reboot to TWRP ( check boxes to install TWRP manager - if you see that screen)
Once rebooted to TWRP Recovery, Flash Rom of Choice, Gapps if needed, Flash Magisk again. Boot to system and setup.
The only issue i am having at the moment, everytime i Install the Magisk.zip over TWRP my A3 stucks at "mi" logo. So just need to figure that out.
But hey i´m almost done!
Edit# 3: Tried to install Disable_Dm-Verity_ForceEncrypt package, before Magiskv20.4 installation, but still getting bootloop after flashing the .zip file.
-----------------------------------------------------------------------------------------------------------------------------------------------------------
Final Update: Everything is working Oh god, that was my first day with an Android Phone and i really learned a lot about it. Even if i figured out everything by myself, i hope that this thread helps someone out, who is facing similiar issues.
Final Steps:
1. downloaded MiFlash and flashed my Mi A3 with the latest ROM - laurel_sprout_global_images_V11.0.8.0.QFQMIXM_79d650b0da_10.0 -
2. Device booted up with an error that the Android OS is corrupted and i had to reset it to factory settings
3. Device booted up to the Android OS.
4. Downloaded my stock boot.img and copied that to my Downloads folder
5. Installed Magisk Manager on my device and patched my stock boot image. If everything is done an new magisk_patched.img will be created under the same path.
6.Used following command to copy the .img file from my device to my PC "adb pull /sdcard/Download/magisk_patched.img"
7. Opened CMD --> navigated to my adb tools and typed in following code: adb reboot bootloader --> Enter --> fastboot flash boot magisk_patched.img --> Enter --> fastboot continue
8. Done, device booted up and Magisk was successfully installed.
Thank you.
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via recovery (either stock) because is no more needed. The updates will be done on the slot not used for example if you are using slot a the update will be installed on slot b and the slot b will be set as default. If you brick and you are in bootloop how you can restore the rom? You can't with Stock ROM you have, because the zip can be only installed via Update Engine, so what can you do? Flash a stock rom via fastboot. I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlocked. This will erase all your data and will wipe your internal storage.
HOW TO FLASH
This version is only for not branded devices
Download the zip;
Unpack the zip in a folder;
Reboot the OnePlus Nord in fastboot-bootloader mode (Power and volume + and volume-);
Connect the OnePlus Nord to PC;
Run flash-all.bat flasher you need;
Wait until the process end;
The phone will automatically reboot.
DOWNLOAD
All roms on Sourceforge: https://sourceforge.net/projects/fastbootroms/files/OnePlus Nord/
BRANDED PHONE
For now branded device are not supported
MANUAL FLASH: Windows - OSX - Linux
If you want to manual flash these roms these are the commands (You need the latest sdk platform tools, you can find it here
Is reccomended to format data or the rom cannot boot:
Code:
fastboot -w
Others Commands to flash a fastboot rom
Code:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash recovery recovery.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot reboot fastboot
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash logo logo.img
fastboot flash oem_stanvbk oem_stanvbk.img
fastboot flash odm odm.img
fastboot flash qupfw qupfw.img
fastboot flash storsec storsec.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot reboot
REMEMBER
"Invalid sparce file format at header magic" is not an error, you need to wait a bit when you see that string, just wait.
If the device automatically reboot in Stock Recovery mode don't reboot it and wait the flash end.
These ROMs can't be used to update or downgrade your phone but just to restore your phone.
If the rom seems doesn't start go in recovery stock and follow this guideline: English -> Wipe data and cache -> Erase everything.
If you want to rebrand your phone from HydrogenOS to OxygenOS you can follow this guide: Rebrand Guide
If you want you can use also my tool to flash Factory Images, unlock bootloader, flash twrp or to understand if the device is recognized: https://toolaio.tk/
If you got some problems like write error or no partition, check this: https://forum.xda-developers.com/showpost.php?p=76658555&postcount=34
DONATE LINK
If you want to support this and others my projects please consider making a donation, thanks.
I was already waiting for it.:laugh:
mauronofrio said:
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via recovery (either stock) because is no more needed. The updates will be done on the slot not used for example if you are using slot a the update will be installed on slot b and the slot b will be set as default. If you brick and you are in bootloop how you can restore the rom? You can't with Stock ROM you have, because the zip can be only installed via Update Engine, so what can you do? Flash a stock rom via fastboot. I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlocked. This will erase all your data and will wipe your internal storage.
HOW TO FLASH
This version is only for not branded devices
Download the zip;
Unpack the zip in a folder;
Reboot the OnePlus Nord in fastboot-bootloader mode (Power and volume + and volume-);
Connect the OnePlus Nord to PC;
Run flash-all.bat flasher you need;
Wait until the process end;
The phone will automatically reboot.
DOWNLOAD
All roms on Sourceforge: https://sourceforge.net/projects/fastbootroms/files/OnePlus Nord/
BRANDED PHONE
For now branded device are not supported
MANUAL FLASH: Windows - OSX - Linux
If you want to manual flash these roms these are the commands (You need the latest sdk platform tools, you can find it here
Is reccomended to format data or the rom cannot boot:
Others Commands to flash a fastboot rom
REMEMBER
"Invalid sparce file format at header magic" is not an error, you need to wait a bit when you see that string, just wait.
If the device automatically reboot in Stock Recovery mode don't reboot it and wait the flash end.
These ROMs can't be used to update or downgrade your phone but just to restore your phone.
If the rom seems doesn't start go in recovery stock and follow this guideline: English -> Wipe data and cache -> Erase everything.
If you want to rebrand your phone from HydrogenOS to OxygenOS you can follow this guide: Rebrand Guide
If you want you can use also my tool to flash Factory Images, unlock bootloader, flash twrp or to understand if the device is recognized: https://toolaio.tk/
If you got some problems like write error or no partition, check this: https://forum.xda-developers.com/showpost.php?p=76658555&postcount=34
DONATE LINK
If you want to support this and others my projects please consider making a donation, thanks.
Click to expand...
Click to collapse
I an waiting for TWRP...
cieffe54 said:
I an waiting for TWRP...
Click to expand...
Click to collapse
Check development thread
cieffe54 said:
I an waiting for TWRP...
Click to expand...
Click to collapse
And i am waiting for end of corona pandemic.
Kollachi said:
And i am waiting for end of corona pandemic.
Click to expand...
Click to collapse
But i shared it too...
Hello and thank you for the fastboot roms !
How To Use This!
mauronofrio said:
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via recovery (either stock) because is no more needed. The updates will be done on the slot not used for example if you are using slot a the update will be installed on slot b and the slot b will be set as default. If you brick and you are in bootloop how you can restore the rom? You can't with Stock ROM you have, because the zip can be only installed via Update Engine, so what can you do? Flash a stock rom via fastboot. I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlocked. This will erase all your data and will wipe your internal storage.
HOW TO FLASH
This version is only for not branded devices
Download the zip;
Unpack the zip in a folder;
Reboot the OnePlus Nord in fastboot-bootloader mode (Power and volume + and volume-);
Connect the OnePlus Nord to PC;
Run flash-all.bat flasher you need;
Wait until the process end;
The phone will automatically reboot.
DOWNLOAD
All roms on Sourceforge: https://sourceforge.net/projects/fastbootroms/files/OnePlus Nord/
BRANDED PHONE
For now branded device are not supported
MANUAL FLASH: Windows - OSX - Linux
If you want to manual flash these roms these are the commands (You need the latest sdk platform tools, you can find it here
Is reccomended to format data or the rom cannot boot:
Code:
fastboot -w
Others Commands to flash a fastboot rom
Code:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash recovery recovery.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot reboot fastboot
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash logo logo.img
fastboot flash oem_stanvbk oem_stanvbk.img
fastboot flash odm odm.img
fastboot flash qupfw qupfw.img
fastboot flash storsec storsec.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot reboot
REMEMBER
"Invalid sparce file format at header magic" is not an error, you need to wait a bit when you see that string, just wait.
If the device automatically reboot in Stock Recovery mode don't reboot it and wait the flash end.
These ROMs can't be used to update or downgrade your phone but just to restore your phone.
If the rom seems doesn't start go in recovery stock and follow this guideline: English -> Wipe data and cache -> Erase everything.
If you want to rebrand your phone from HydrogenOS to OxygenOS you can follow this guide: Rebrand Guide
If you want you can use also my tool to flash Factory Images, unlock bootloader, flash twrp or to understand if the device is recognized: https://toolaio.tk/
If you got some problems like write error or no partition, check this: https://forum.xda-developers.com/showpost.php?p=76658555&postcount=34
DONATE LINK
If you want to support this and others my projects please consider making a donation, thanks.
Click to expand...
Click to collapse
Oneplus Nord oxygen os install guide
Get OEM Drivers from https://oneplususbdrivers.com/download-oneplus-usb-driver/
Download Oxygen OS 10.5.4 for your compatible devices from https://sourceforge.net/projects/fastbootroms/files/OnePlus Nord/
(Boot loader Must be Unlocked)
If still able to boot into any version of Android:
1. Install Oneplus OEM Drivers
2. Open Settings
3. Click About
4. Find the build number and click the Build number Severn times until you get a message saying developer Options have been enabled.
5. Enable ADB USB Debugger
6. Unzip the Oxygen OS File
7. Open CMD and run it as Administrator
8. Plug Your Oneplus Nord into your PC
9. Type into CMD cd and drag the Oxygen OS Folder over CMD, then Click Enter
10. This will make the link before the next line quite long.
11. Then Type into CMD “adb reboot bootloader” (This will make your Phone Reboot into Fastboot)
If You are Unable to boot into any Operating System:
1. Install Oneplus OEM Drivers
2. Unzip the Oxygen OS File
3. Open CMD and run it as Administrator
4. Type into CMD cd and drag the Oxygen OS Folder over CMD, then Click Enter
5. This will make the link before the next line quite long.
6. Plug Your Oneplus Nord into your Computer
7. When your phone is powered off, Hold Volume Up, Volume Down and the Power Button until you get the Oneplus Logo with fastboot Beneath.
Once in the Bootloader:
1. Type fastboot devices to confirm that your device has been recognised by your PC.
2. After this Open the Oxygen OS Folder and double click Flash-All.adb and It will open in command Prompt.
3. This will take a long time but wait until the phone has booted up into your phones setup (Do Not touch the Phone or Computer).
4. Setup Your Phone but don’t setup anything as we need to wipe it again, so skip through everything.
5. Once in the primary OS connect to WIFI
6. Go to Settings and Update your phone to the latest version, you will get a message prompting you that the Boot loader is unlocked etc, Ignore this and continue.
7. Click the reboot button when prompted, your Software will update to the latest version of Oxygen OS.
Once Updated:
1. Open Settings
2. Click About
3. Find the build number and click the Build number Severn times until you get a message saying developer Options have been enabled.
4. Enable ADB USB Debugger
5. Unzip the Oxygen OS File
6. Open CMD and run it as Administrator
7. Plug Your Oneplus Nord into your PC
8. Type into CMD cd and drag the Oxygen OS Folder over CMD, then Click Enter
9. This will make the link before the next line quite long.
10. Then Type into CMD “adb reboot bootloader” (This will make your Phone Reboot into Fastboot).
11. Once in Fastboot type “fastboot OEM lock” then your phone will prompt you if you want to Lock the bootloader.
12. Use the volume button to scroll down and press enter to confirm that you want to lock your bootloader.
13. When locked your phone will reboot and it will wipe your operating system and reboot your device into setup.
14. You can now setup your phone as you wish.
there's not oneplus widget? i can't find it
Jackmitchell62 said:
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via recovery (either stock) because is no more needed. The updates will be done on the slot not used for example if you are using slot a the update will be installed on slot b and the slot b will be set as default. If you brick and you are in bootloop how you can restore the rom? You can't with Stock ROM you have, because the zip can be only installed via Update Engine, so what can you do? Flash a stock rom via fastboot. I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlocked. This will erase all your data and will wipe your internal storage.
HOW TO FLASH
This version is only for not branded devices
Download the zip;
Unpack the zip in a folder;
Reboot the OnePlus Nord in fastboot-bootloader mode (Power and volume + and volume-);
Connect the OnePlus Nord to PC;
Run flash-all.bat flasher you need;
Wait until the process end;
The phone will automatically reboot.
DOWNLOAD
All roms on Sourceforge: https://sourceforge.net/projects/fastbootroms/files/OnePlus Nord/
BRANDED PHONE
For now branded device are not supported
MANUAL FLASH: Windows - OSX - Linux
If you want to manual flash these roms these are the commands (You need the latest sdk platform tools, you can find it here
Is reccomended to format data or the rom cannot boot:
Others Commands to flash a fastboot rom
Oneplus Nord oxygen os install guide
Get OEM Drivers from https://oneplususbdrivers.com/download-oneplus-usb-driver/
Download Oxygen OS 10.5.4 for your compatible devices from https://sourceforge.net/projects/fastbootroms/files/OnePlus Nord/
(Boot loader Must be Unlocked)
If still able to boot into any version of Android:
1. Install Oneplus OEM Drivers
2. Open Settings
3. Click About
4. Find the build number and click the Build number Severn times until you get a message saying developer Options have been enabled.
5. Enable ADB USB Debugger
6. Unzip the Oxygen OS File
7. Open CMD and run it as Administrator
8. Plug Your Oneplus Nord into your PC
9. Type into CMD cd and drag the Oxygen OS Folder over CMD, then Click Enter
10. This will make the link before the next line quite long.
11. Then Type into CMD “adb reboot bootloader” (This will make your Phone Reboot into Fastboot)
If You are Unable to boot into any Operating System:
1. Install Oneplus OEM Drivers
2. Unzip the Oxygen OS File
3. Open CMD and run it as Administrator
4. Type into CMD cd and drag the Oxygen OS Folder over CMD, then Click Enter
5. This will make the link before the next line quite long.
6. Plug Your Oneplus Nord into your Computer
7. When your phone is powered off, Hold Volume Up, Volume Down and the Power Button until you get the Oneplus Logo with fastboot Beneath.
Once in the Bootloader:
1. Type fastboot devices to confirm that your device has been recognised by your PC.
2. After this Open the Oxygen OS Folder and double click Flash-All.adb and It will open in command Prompt.
3. This will take a long time but wait until the phone has booted up into your phones setup (Do Not touch the Phone or Computer).
4. Setup Your Phone but don’t setup anything as we need to wipe it again, so skip through everything.
5. Once in the primary OS connect to WIFI
6. Go to Settings and Update your phone to the latest version, you will get a message prompting you that the Boot loader is unlocked etc, Ignore this and continue.
7. Click the reboot button when prompted, your Software will update to the latest version of Oxygen OS.
Once Updated:
1. Open Settings
2. Click About
3. Find the build number and click the Build number Severn times until you get a message saying developer Options have been enabled.
4. Enable ADB USB Debugger
5. Unzip the Oxygen OS File
6. Open CMD and run it as Administrator
7. Plug Your Oneplus Nord into your PC
8. Type into CMD cd and drag the Oxygen OS Folder over CMD, then Click Enter
9. This will make the link before the next line quite long.
10. Then Type into CMD “adb reboot bootloader” (This will make your Phone Reboot into Fastboot).
11. Once in Fastboot type “fastboot OEM lock” then your phone will prompt you if you want to Lock the bootloader.
12. Use the volume button to scroll down and press enter to confirm that you want to lock your bootloader.
13. When locked your phone will reboot and it will wipe your operating system and reboot your device into setup.
14. You can now setup your phone as you wish.
Click to expand...
Click to collapse
Or simply use MSM tool ?
https://forum.xda-developers.com/oneplus-nord/how-to/opnord-unbrick-tool-to-restore-device-t4148415
Reboot in recovery
Hello everyone, I need help.
I got the message "File system raw not supported." after executing the flash_all.bat and
Code:
boot_b, dtbo, modem_b, recovery, vbmeta, vbmeta_system,
was sent with status
Code:
OKAY
(the first part of the script, as far as I can see), then is supposed to reboot on fastboot and stays at
Code:
<waiting for any device>
, here is when my phone restarts in recovery instead (it says "fastbootd" in the upper part and a menu to select chinesse or english, but it's recovery mode, right?), then the first time I wited for 15 minutes but nothing happened, so I selected reboot into fastboot in recovery mode, then in CMD I got the message "fastboot: error Failed to boot into userspace fastboot; one or more components might be unbootable", and the seccond part of the script was executed, but with
Code:
FAILED (remote: 'Flashing is not allowed for Critical Partitions')
status in the writing process, and after,
Code:
"Invalid sparse file format at header magic"
with
Code:
FAILED (remote: 'Partition not found')
when trying to write system, vendor and product. My phone restarted and looked normar but wifi didn't work, and the UI started to fail after the configuration.
So I tried again, but without rebooting from recovery; how much time do I have to wait there?, maybe this will not work.
Please if someone knows how to solve my problem I'll be glad for the help.
MSM TOOL
https://forum.xda-developers.com/oneplus-nord/how-to/opnord-unbrick-tool-to-restore-device-t4148415
I succeeded from linux, everything seems to work fine now.
I just have one question, there's one file missing
fastboot flash storsec storsec.img
Is supposed to be like that or is that an important file missed?
That file doesn't exists in the 10.5.5-INDIA-NordOxygen_14_OTA_007_all_2008180229 zip file
I bricked my device and nothing (what i try) worked.
Hello Guys,
Thanks for the Roms and also for twrp @ mauronofrio!
If i try to flash in fastboot the roms, i get different fails:
the first part of commands are okay until "fastboot reboot fastboot"
than, until "fastboot flash xbl_config xbl_config.img" i get:
"writing 'xbl_config'...
FAILED (remote: Flashing is not allowed for Critical Partitions)"
and for the lasts, i get:
FAILED (remote: Partition not found)
I read that some windows-user have the same Problem and therrefore the Problem is not the bricked phone, is it right?
Someone knows the same Problem in linux? I prefer a solution without windows (msm-tool).
I tried to root and flash with twrp, now i know, it's impossible to flash zips until now. I try some other things with twrp, it's possible that i delete some partitions?
Someone have a good solution?
thanks for reading and support
Hi,
Few questions:
Has Global rom OP dialer? Can be enabled auto call recording with root or adb? I know abut Skvalex.
Can I flash 10.5.5 Global at 10.5.9 EEA (flash_all.bat)?
Getting stuck on odm and vendor flashing. It will not flash odm and vendor no file exists message (using flash all bat). Any help will be greatly appreciated.
Update: got it back to stock using edl mode.
You can flash this way. When you enter from the fastboot to the fastbootD mode Windows thinks it's a new device and doesn't recognize it. If you open device manager from control panel it will showns as unknow device. So all you have to do is install the driver again. Then you can flash anything you want in fastbootD.
-
What does "unbranded" mean here? Will I get OTA updates? Will this relock the bootloader?
delete
Hi all
i want to install TWRP on my Doogee N20PRO . i cannot find a TWRP File on the internet to install. I could find some for the N20 but not for the N20PRO. it´s an Helios P60 Processor with an MTK6771. I tried to install the HAVOC 3.7 but i get the Message "writing 1/15 failed (remote: this partition doesn´t exist)
beinfo said:
Hi all
i want to install TWRP on my Doogee N20PRO . i cannot find a TWRP File on the internet to install. I could find some for the N20 but not for the N20PRO. it´s an Helios P60 Processor with an MTK6771. I tried to install the HAVOC 3.7 but i get the Message "writing 1/15 failed (remote: this partition doesn´t exist)
Click to expand...
Click to collapse
This is simple about TWRP: Your phone have МТК Helio Р60 MT6771V/CA WITH Android 10.0 and it's a NEW phone now. So no developments yet.
For install GSI ROMs your need unlock bootloader and after follow the correct instructions to new phones shipped with A10!
If you only want install GSI so I suggest:
1- Have stock ROM first, always!!;
2- With security 1- you should unlock bootloader;
3- You can install GSI with stock recovery without problems.
The only part is: you cannot backup userdata.....
DragonPitbull said:
This is simple about TWRP: Your phone have МТК Helio Р60 MT6771V/CA WITH Android 10.0 and it's a NEW phone now. So no developments yet.
For install GSI ROMs your need unlock bootloader and after follow the correct instructions to new phones shipped with A10!
If you only want install GSI so I suggest:
1- Have stock ROM first, always!!;
2- With security 1- you should unlock bootloader;
3- You can install GSI with stock recovery without problems.
The only part is: you cannot backup userdata.....
Click to expand...
Click to collapse
Cool This helps already a lot.
i unlocked the Bootloader properly, but then i got a partition error. I assume i´ve an error in the command line. The phone was anyway only an interim solution till my POco F2 was back from repair. now i use it as a playground.
fastboot erase system - there i get a partition error.
erasing the User data was sucessful
but then
fastboot flash system system.img it stops at step 1/15 again for the partition error (partition doesn´t exist) Stock rom is available.
somebody knows the options i´ve to add to the command line?
beinfo said:
The phone was anyway only an interim solution till my POco F2 was back from repair. now i use it as a playground.
fastboot erase system - there i get a partition error.
erasing the User data was sucessful
but then
fastboot flash system system.img it stops at step 1/15 again for the partition error (partition doesn´t exist) Stock rom is available.
somebody knows the options i´ve to add to the command line?
Click to expand...
Click to collapse
Try but REMENBER I am not responsible for any errors. Bootloader should unlocked by adb-fastboot!!
Spoiler: Instructions
1. You need know the difference about fastboot and FASTBOOTD in your device!!
Your device has bootloader mode: recovery - fastboot - reboot (system)
Stock recovery has very options: reboot system - reboot to bootloader - wipe - Enter fastboot - ...
reboot to bootloader => normal fastboot
Enter fastboot => FASTBOOTD
FASTBOOTD => some options
2. Device in fastboot
Code:
fastboot --disable-verification flash vbmeta vbmeta.img
vbmeta file from stock ROM or pulled from device
3.
Code:
fastboot -w
4.
Code:
fastboot reboot fastboot
(you MUST be at the FASTBOOTD menu now. If not, you will not be able to flash the GSI successfully)
5.
Code:
fastboot erase system
or
Code:
fastboot delete-logical-partition system
6.
Code:
fastboot delete-logical-partition product
- deletes the product partition, allowing a larger system partition
I not need resize-logical-partition product. But if you want:
You will need a larger system partition to flash a GSI. There are 2 ways to achieve this
6A. fastboot resize-logical-partition product 509344768
6B. fastboot resize-logical-partition system 3089272064 or 3889272064
resizes product and system partitions. This gives you about 3GB of system partitions. You can adjust or arrive at your own numbers if you want different sizes.
7.
Code:
fastboot --disable-verity --disable-verification flash system GSI.img
8.
Code:
fastboot -w
for confirm great & fast start GSI
9.
Code:
fastboot reboot bootloader
9A.
Code:
fastboot erase userdata
for confirm and boot clean
10. Reboot to system
Code:
fastboot reboot
Enjoy
I also have an N20 Pro which I received Dec 2020. Had some trouble setting it up. I got the OEM ROM from Doogee customer support and was able to extract the boot image and patch it with Magisk. I then burned it with the SP Flash tool. It wouldn't boot until I burned a special vbmeta.img to turn off encryption. Now it's working fine.
Sorry this doesn't help you with TWRP but I think most people looking for TWRP are really looking to root their phone.
beinfo said:
Hi all
i want to install TWRP on my Doogee N20PRO . i cannot find a TWRP File on the internet to install. I could find some for the N20 but not for the N20PRO. it´s an Helios P60 Processor with an MTK6771. I tried to install the HAVOC 3.7 but i get the Message "writing 1/15 failed (remote: this partition doesn´t exist)
Click to expand...
Click to collapse
Okay so what ive seen is that you should avoid flashing custom roms via adb fastboot especially with our doogee phones, and also there are many incompatiable roms so what you will need is to unlock bootloader and do the whole twrp install thing adn also install magisk
before hand install treble info from google playstore and take down the information "arm64 a/b" and search for roms with that information to install custom os/rom/gsi properly. GSI versions are more preferred if your phone supports treblle
if your twrp keeps getting wiped after reboot open file :mount your system and connect to pc via usbcable (mtp if not showing disable mtp and re- enable it )
now got to where build.prop is saved there will be a file called recovery from boot.p , copy the file to pc , open with notepad, remove everything , save and copy back to phone (overwrite)
then go ahead and install magisk
make sure your magisk is working install edxposed, riru core , and busybox ndk get the apps you need for them (edxposed manager...) and then instal and activate a module which you can test if its working(if framework is active in edxposed manager and the module working correctly then you can go ahead and
Install custom os through twrp
follow these instructions ( https://forum.xda-developers.com/t/...lexperience-10-gsi-android-10-stable.4081685/ ) with your custom rom (corvus, havoc, lineage...
(the g-apps didnt flash for me (error code 64) but i just rebooted and everything was working fine (including gapps but camera sucked (doogee's rear camera setup was just terrible))
https://forum.xda-developers.com/t/...lexperience-10-gsi-android-10-stable.4081685/
** i can confirm follow instructions properly and it should work (i used this pixel experience on my doogee n20 make sure you unzip the .xz file and youre flashing a .img file
**also make sure its the gsi file (
I can't install any rom, ADB sideload fails with this error:
Unable to mount storage.
Devices on super may not mount until rebooting recovery.
To flash additional zips, please reboot recovery to switch to the updated slot.
I already tried to switch the slots many times.
I also tried to format data, but it tells me:
E: unable to check merge status
Updating partition details...
...done
Unable to mount storage
I can access the recovery and the factory-reset android, but i can't do anything more.
I think the problem is relative to encryption but I can't even format data, so I don't know how to escape this...
Now I can't even access the rom, I can only access TWRP and fastboot. The problem is that format data does not work, with the same error:
E: unable to check merge status
I tried repairing and changing filesystem, now I don't really know what to do...
just install rom using fast boot tool and
format data after that
muneeb rizwan said:
just install rom using fast boot tool and
format data after that
Click to expand...
Click to collapse
I have never used fastboot tool. I'm on linux. Is this the program i must install?
And also, do I need a fastboot rom?
[Tool] Flash Custom ROMs through Fastboot [mojito / sunny]
Are you struggling to install custom roms on this device? Lots of recovery errors? Can't boot to any rom? Don't worry. Fastboot is a good way to avoid such nonsense... Install any custom rom & miui recovery rom through fastboot Steps: 1...
forum.xda-developers.com
USE THIS TOOL AND YOU DONT NEED FASTBOOT ROM
Ok, i installed CrDroid with fastboot tool, then format data and then re-flashed the rom with adb, but the phone starts just on the CrDroid recovery (slot b) or on fastboot (slot a)...
What is the correct process to install a ROM? This A/B thing gets me mad
Now I managed to install an old MIUI fastboot rom from this link with XiaomiADBFastbootTools (a kind of mi flash tool for linux) and this rom now it is working, so I think I had some problems with the fastboot tool you suggested. But I don't really know what was the problem, the installation process seemed to work, It restarted to recovery, I rebooted to system but then it kept returning to recovery or to fastboot without entering in the system...
Switching slots directly in recovery is not functional. Just look after switching what the active slot is and you will see that it has not changed. Do the slot switching with the fastboot command from the PC.
fastboot --set-active=a
fastboot --set-active=b
StaryMuz said:
Switching slots directly in recovery is not functional. Just look after switching what the active slot is and you will see that it has not changed. Do the slot switching with the fastboot command from the PC.
fastboot --set-active=a
fastboot --set-active=b
Click to expand...
Click to collapse
yes, I was using these commands to switch slots. but when it is necessary to switch slots in the flashing process? I mean, what is the correct order? format - flash rom with adb - reboot to fastboot - switch slot - reboot to system...is this correct?
Slot swapping may not be required. Do it only when it is requested or when the boot crashes into recovery.
StaryMuz said:
Slot swapping may not be required. Do it only when it is requested or when the boot crashes into recovery.
Click to expand...
Click to collapse
OK, so is this the correct order?
Format - flash rom with adb - reboot to system
Now I have a problem with fastboot...I don't know why but it can't boot any recovery...
"fastboot boot recovery.img" remains stuck at:
Sending 'boot.img' (131072 KB)
Click to expand...
Click to collapse
and nothing happens! I tried with TWRP and OrangeFox.
I also tried to change slot but it fails:
fastboot --set-active=a
Setting current slot to 'a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Click to expand...
Click to collapse
The command 'Fastboot reboot' gives me a black screen with a white message: 'any key to shutdown', then the phone reboots to system...
What is the full designation of your phone?
StaryMuz said:
What is the full designation of your phone?
Click to expand...
Click to collapse
what is the designation?
Xiaomi Redmi Note .....
All of it, exactly.
StaryMuz said:
Xiaomi Redmi Note .....
All of it, exactly.
Click to expand...
Click to collapse
Redmi Note 10 64GB/4GB, I think the codename is sunny because I have the global/european version. Do you need more?
I think the best step is to upload the original Miui using MiFlash with the "clear all" setting.
Use this version of MiFlash.
You can get the right Miui here.
Before using MiFlash, I recommend loading the boot.img included in the downloaded Miui into your phone in fastboot mode.
Use the command:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Then use MiFlash and don't play Miui. Wait until the phone starts itself, then you can disconnect it.
If anything is not clear, ask questions.
StaryMuz said:
I think the best step is to upload the original Miui using MiFlash with the "clear all" setting.
Use this version of MiFlash.
You can get the right Miui here.
Before using MiFlash, I recommend loading the boot.img included in the downloaded Miui into your phone in fastboot mode.
Use the command:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Then use MiFlash and don't play Miui. Wait until the phone starts itself, then you can disconnect it.
If anything is not clear, ask questions.
Click to expand...
Click to collapse
Actually I'm already in a original MIUI and it is working. My pc is on linux so I can't use MiFlash but I used XiaomiADBFastbootTools (a kind of MiFlash tool for linux). Can I start from here or I have to install the MIUI version you linked?
The only thing is that I didn't specifically load the boot.img
Unfortunately I don't know the Linux version of MiFlash. They may not work equivalently. It needs to properly clean all the partitions of the phone and load all the files supplied in the ROM.
I recommend to use the Miui listed by me.
As I mentioned before, unlocking the bootloader will fix this issue.
But if you don't want to unlock the bootloader, then this guide is for you.
DO NOT USE THIS METHOD IF JUNE 2023 OR NEWER UPDATE RELEASES IN FUTURE!
YOU SHOULD NOT IGNORE, REVERSE, SKIP ANY OF THE STEPS!
We assume you know how to use ADB/Fastboot commands.
Before you proceed, make sure you have your phone's battery charged as much as possible, or the bootloader will not allow you write any partitions.
1. Download this package and extract:
Non-Chinese users: https://www.androidfilehost.com/?fid=10620683726822058340
Chinese users can download from here: https://api.hikaricalyx.com/FileDownload/CTWorks?id=beb66c13d70644
Code:
SHA256: 72425ebdf249f523c81646786eb92d57229e9164ad25be2ef2d920eb7176fcd3
You should keep at least 10,030MB (10GB approx) empty space.
2. Open FastbootDriver folder and open DPInst64.exe (or DPInst32.exe if you're using 32-bit Windows) to install correct Fastboot driver. Once Fastboot driver installed, open RegistryFix.reg to prevent fastboot mode become unstable.
3. Sideload Android 10 Full OTA Package Under Recovery mode. Enter Recovery Mode by using either of these 2 methods.
- Execute these 2 commands:
Code:
fastboot reboot-fastboot
fastboot reboot-recovery
Then this phone will boot right into Recovery menu.
- At Fastboot screen, use Volume key to select Recovery mode, then power key to confirm.
When you see Android robot lying, press Volume Up key while holding power key to get Recovery menu.
We recommend users to use method 1 as many people don't know how to press such combination key.
4. Download this Android 10 Full OTA package:
https://android.googleapis.com/packages/ota-api/package/627142c637bf373410e6b8911aeb9b2e65bd5969.zip
or from here: https://www.androidfilehost.com/?fid=10620683726822057898Chinese users who don't have access to Google server can download from here: https://api.hikaricalyx.com/FileDownload/CTWorks?id=f427f5862b7749
Code:
SHA256: ba940f216f8d69de988005a6c61ba03073a5b0aacb0789005db5f2f2befe1a02
Please re-download this package if SHA256 is incorrect.
5. Use volume key to select "Apply update from ADB", then power key to confirm.
6. Execute this command to sideload Android 10 Full OTA to your phone:
Code:
adb sideload /path/to/627142c637bf373410e6b8911aeb9b2e65bd5969.zip
You may see downgrade not allowed message on screen, but it will be installed anyway. Wait for the procedure completes.
If the procedure halted at 94% and it says "adb: failed to read command: No error", it's expected.
7. Use volume key to select "Reboot to bootloader", power key to confirm.
8A. To Windows users, double click "0_OpenMeToInstall.cmd", and wait for the procedure completes. We only guarantee it will work on Windows 10 and 11.
DO NOT RUN IT WITH ADMINISTRATOR PRIVILEGES!
-
8B. To non-Windows users or you prefer to flash the package manually, execute these commands. It's absolutely discouraged to use outdated Fastboot binary (e.g. Minimal ADB and Fastboot).
Code:
cd /path/to/where/you/extracted/package/
fastboot flash abl_a abl_proto.elf
fastboot flash abl_b abl_proto.elf
fastboot reboot-bootloader
fastboot flash aop_a aop.img
fastboot flash aop_b aop.img
fastboot flash bluetooth_a bluetooth.img
fastboot flash bluetooth_b bluetooth.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash core_nhlos_a core_nhlos.img
fastboot flash core_nhlos_b core_nhlos.img
fastboot flash devcfg_a devcfg.img
fastboot flash devcfg_b devcfg.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash featenabler_a featenabler.img
fastboot flash featenabler_b featenabler.img
fastboot flash hyp_a hyp.img
fastboot flash hyp_b hyp.img
fastboot flash imagefv_a imagefv.img
fastboot flash imagefv_b imagefv.img
fastboot flash keymaster_a keymaster.img
fastboot flash keymaster_b keymaster.img
fastboot flash mdtp_a mdtp.img
fastboot flash mdtp_b mdtp.img
fastboot flash mdtpsecapp_a mdtpsecapp.img
fastboot flash mdtpsecapp_b mdtpsecapp.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash qupfw_a qupfw.img
fastboot flash qupfw_b qupfw.img
fastboot flash recovery_a recovery.img
fastboot flash recovery_b recovery.img
fastboot flash tz_a tz.img
fastboot flash tz_b tz.img
fastboot flash uefisecapp_a uefisecapp.img
fastboot flash uefisecapp_b uefisecapp.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash vbmeta_system_a vbmeta_system.img
fastboot flash vbmeta_system_b vbmeta_system.img
fastboot flash xbl_a xbl.img
fastboot flash xbl_b xbl.img
fastboot flash xbl_config_a xbl_config.img
fastboot flash xbl_config_b xbl_config.img
fastboot flash super super.img
fastboot flash abl_a abl.img
fastboot flash abl_b abl.img
fastboot reboot
8. Enjoy your fully revived Nokia 8.3 - and all your data should be safe.
Older April 2023 package can be downloaded for archiving purposes. Do not download if you don't know what you're doing.
HCTSW2_BGT-349D-0-00WW-B01_600WW_12_20230401_huaqin_ZQN1876_UnbrickFix.full.lzma2.63640a31.7z | by Hikari Calyx for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
FAQ and Troubleshooting
Q1. ADB prompts cannot read '/path/to/zipfile.zip' when sideloading!
A1. You're probably using outdated ADB binary (e.g. Minimal ADB and Fastboot). Always use latest Platform Tools from here: https://developer.android.com/studio/releases/platform-tools
Your outdated ADB binary might be installed at following directories. We strongly recommend you delete it before you proceed.
Code:
C:\adb
C:\Windows
C:\Windows\system32
Delete these files:
adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll, fastboot.exe
Q2. Can I safely update to newer security updates?
A2. Yes you can. In case it bricked the phone again, rollback with this method.
Q3. The phone gets into bootloop while reinstalling firmware!
A3. To re-enter Fastboot mode, hold volume down key and power key while connected to PC. When the phone displays android one again, release power key immediately but don't release volume down key. Your phone should boot right into fastboot mode without vibration. You may need to try it multiples of times.
Then, re-open 0_OpenMeToInstall.cmd .
Q4: Why we don't recommend you to use "fastboot continue" method to "fix" the phone?
A4: 00WW_3_49E build has following known issues:
* You cannot install APK directly on device. PackageInstaller will crash immediately when you attempt to install APK.
* You cannot install newer OS update.
Those who're staying at 00WW_3_49E can reboot the phone into bootloader mode and follow this method to reinstall 00WW_3_49F update.
Q5: Can I do this under Windows 7?
A5: We can only guarantee it will run under Windows 10 or 11. Take your own risk if you're using Windows 7.
Q6: How to acknowledge if SHA256 is correct?
A6: For Windows users, you can install 7-Zip or it's fork (e.g. NanaZip), and you can find SHA256 checksum feature by right click on the file.
For macOS or Linux users, execute this command:
Code:
sha256sum /path/to/package/you/d/like/to/checksum.zip
Q7: What if the PC is infected by Synaptics virus - where executables become into "._cache.fastboot.exe"?
A7: Please look for an antivirus app you trust, do a full scan then restart. It's most likely caused by using USB Redirector Customer Module before from unknown sources.
Q8: I got "This is not Nokia 8.3" error, but I'm pretty sure it's Nokia 8.3!
A8: I'm afraid that you have ignored some procedure. You must install have driver installed properly before you proceed.
Q9: The PC does not detect the device. I got "The USB device returned an invalid serial number string descriptor." in Device Manager.
A9: Open Administrator privilege command prompt, powershell of terminal, execute these commands:
Code:
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags" /v "IgnoreHWSerNum18d1d00d" /t REG_DWORD /d 1 /f
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags" /v "IgnoreHWSerNum18d14ee0" /t REG_DWORD /d 1 /f
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags" /v "IgnoreHWSerNum18d1d001" /t REG_DWORD /d 1 /f
After that, use volume key to select "reboot to bootloader" on your phone and try again.
Q10: The phone is listed under Universal Serial Bus Controller as "Unknown Device (Device Descriptor Request Failed)" in Device Manager.
A10: This is caused by following reasons and none of them are related to USB driver:
* USB port on your PC or phone is too loose.
* You're using USB cable with low quality.
* If full-size desktop PC, you're not using the USB port on the rear side. Using rear side USB port is always preferred.
Q11: Something wrong happened when using early version of UnbrickFix package, now I cannot enter Recovery mode and cannot flash anything under Fastboot mode. How can I revive my phone?
A11: You'll have to utilize EDL method at this point. Install prototype ABL by following the topic below. Once prototype ABL images are installed, reboot the phone back to fastboot mode and reopen latest version of UnbrickFix package. Note you don't need to unlock the bootloader, just install prototype ABL.
[GUIDE] How to unlock the bootloader for Nokia 8.3 5G
TO CONTENT FARMS ESPECIALLY GETDROIDTIPS: DO NOT REPOST THIS TOPIC ON YOUR WEBSITE! 点击这里查看中文版(Click here for Chinese Version Guide) If you're looking for how to unbrick the phone that received May 2023 Security Update, you've come to the right...
forum.xda-developers.com
Alternately, you can request someone who has access of using HDK to reinstall given firmware for you. We don't have or promote such access, please search online.
Hey, thank you for the guide.
I come across problem when trying to "adb sideload /path/to/627142c637bf373410e6b8911aeb9b2e65bd5969.zip"
My path is "C:\Korjaus\sideloader.zip" and i get "* cannot read 'C:\Korjaus\sideloder.zip' *"
I would be thankfull if somebody proviced help for my case.
E: My phone is found on adb, but i cant figure out why it wont let it read the path, i tried different path to make it smaller.
Kurnauttaja said:
Hey, thank you for the guide.
I come across problem when trying to "adb sideload /path/to/627142c637bf373410e6b8911aeb9b2e65bd5969.zip"
My path is "C:\Korjaus\sideloader.zip" and i get "* cannot read 'C:\Korjaus\sideloder.zip' *"
I would be thankfull if somebody proviced help for my case.
E: My phone is found on adb, but i cant figure out why it wont let it read the path, i tried different path to make it smaller.
Click to expand...
Click to collapse
In this case, try to do this instead:
1. Input adb[space]sideload[space] then do not press enter.
2. Drag OTA package to command prompt then the full path will appear.
3. Press enter.
hikari_calyx said:
In this case, try to do this instead:
1. Input adb[space]sideload[space] then do not press enter.
2. Drag OTA package to command prompt then the full path will appear.
3. Press enter.
Click to expand...
Click to collapse
I tried that, but still:
loading: 'C:\Korjaus\sideloader.zip'
* cannot read 'C:\Korjaus\sideloader.zip' *
Any other possible tricks?
Kurnauttaja said:
I tried that, but still:
loading: 'C:\Korjaus\sideloader.zip'
* cannot read 'C:\Korjaus\sideloader.zip' *
Any other possible tricks?
Click to expand...
Click to collapse
Alternately, if you have external SD card, try to put the package into SD card, then use "apply update from SD card" to install it.
BTW, are you using adb.exe inside of unbrick fix package, or you downloaded it separately (e.g. Minimal ADB and Fastboot)?
If you're using Minimal ADB and Fastboot, please don't use it. Use this instead:
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Hey, i found out other method to fix your bricked 8.3.
I typed just "fastboot continue"
My phone booted itself staying while on Android whitesceen, after like minute or so it continued to "Nokia" logo and started itself perfectly fine!
Dont ask me how i did it or did i do something else by mistake, i dont know anything about these things.
But my phone works finally!
Kurnauttaja said:
Hey, i found out other method to fix your bricked 8.3.
I typed just "fastboot continue"
My phone booted itself staying while on Android whitesceen, after like minute or so it continued to "Nokia" logo and started itself perfectly fine!
Dont ask me how i did it or did i do something else by mistake, i dont know anything about these things.
But my phone works finally!
Click to expand...
Click to collapse
Please check if system version is 00WW_3_490_SP05. This version has faulty PackageInstaller (you cannot install APK directly on device).
To readers here:
I'll reupload a newer package based on recently pushed 00WW_3_49F update (00WW_3_490_SP06).
Once uploaded please let me know if it works well.
hikari_calyx said:
Please check if system version is 00WW_3_490_SP05. This version has faulty PackageInstaller (you cannot install APK directly on device).
Click to expand...
Click to collapse
00WW_3_49E_B01 so 00WW_3_490_SP05.
I see it has problem but im glad my phone works.
Kurnauttaja said:
00WW_3_49E_B01 so 00WW_3_490_SP05.
I see it has problem but im glad my phone works.
Click to expand...
Click to collapse
Now check if you can search 00WW_3_490_SP06 update. If not please wait for upload.
hikari_calyx said:
As I mentioned before, unlocking the bootloader will fix this issue.
But if you don't want to unlock the bootloader, then this guide is for you.
DO NOT USE THIS METHOD IF JUNE 2023 OR NEWER UPDATE RELEASES IN FUTURE!
We assume you know how to use ADB/Fastboot commands.
Before you proceed, make sure you have your phone's battery charged as much as possible, or the bootloader will not allow you write any partitions.
1. Sideload Android 10 Full OTA Package Under Recovery mode. Enter Recovery Mode by using either of these 2 methods.
- Execute these 2 commands:
Code:
fastboot reboot-fastboot
fastboot reboot-recovery
Then this phone will boot right into Recovery menu.
- At Fastboot screen, use Volume key to select Recovery mode, then power key to confirm.
When you see Android robot lying, press Volume Up key while holding power key to get Recovery menu.
We recommend users to use method 1 as many people don't know how to press such combination key.
2. Download this Android 10 Full OTA package:
https://android.googleapis.com/packages/ota-api/package/627142c637bf373410e6b8911aeb9b2e65bd5969.zip
3. Use volume key to select "Apply update from ADB", then power key to confirm.
4. Execute this command to sideload Android 10 Full OTA to your phone:
Code:
adb sideload /path/to/627142c637bf373410e6b8911aeb9b2e65bd5969.zip
You may see downgrade not allowed message on screen, but it will be installed anyway. Wait for the procedure completes.
If the procedure halted at 94% and it says "adb: failed to read command: No error", it's expected.
5. Use volume key to select "Reboot to bootloader", power key to confirm.
6. Download this package and extract:
Non-Chinese users: https://www.androidfilehost.com/?fid=10620683726822057521
Chinese users can download from here: https://api.hikaricalyx.com/FileDownload/CTWorks?id=fc2e8e97ec9243
Code:
SHA256: 63640a314db853c803e1158ec3e86dbd38200e963b99ffc4335691928e5e5921
You should keep at least 10,014MB (10GB approx) empty space.
7A. To Windows users, double click "0_OpenMeToInstall.cmd", and wait for the procedure completes. We only guarantee it will work on Windows 10 and 11.
7B. To non-Windows users or you prefer to flash the package manually, execute these commands. It's absolutely discouraged to use outdated Fastboot binary (e.g. Minimal ADB and Fastboot).
Code:
cd /path/to/where/you/extracted/HCTSW2_BGT-349D-0-00WW-B01_600WW_12_20230401_huaqin_ZQN1876_UnbrickFix.full.lzma2.xxxxxxxx/
fastboot --slot all flash abl abl_proto.elf
fastboot reboot-bootloader
fastboot --slot all flash aop aop.img
fastboot --slot all flash bluetooth bluetooth.img
fastboot --slot all flash boot boot.img
fastboot --slot all flash core_nhlos core_nhlos.img
fastboot --slot all flash devcfg devcfg.img
fastboot --slot all flash dsp dsp.img
fastboot --slot all flash dtbo dtbo.img
fastboot --slot all flash featenabler featenabler.img
fastboot --slot all flash hyp hyp.img
fastboot --slot all flash imagefv imagefv.img
fastboot --slot all flash keymaster keymaster.img
fastboot --slot all flash mdtp mdtp.img
fastboot --slot all flash mdtpsecapp mdtpsecapp.img
fastboot --slot all flash modem modem.img
fastboot --slot all flash qupfw qupfw.img
fastboot --slot all flash recovery recovery.img
fastboot --slot all flash tz tz.img
fastboot --slot all flash uefisecapp uefisecapp.img
fastboot --slot all flash vbmeta vbmeta.img
fastboot --slot all flash vbmeta_system vbmeta_system.img
fastboot --slot all flash xbl xbl.img
fastboot --slot all flash xbl_config xbl_config.img
fastboot flash super super.img
fastboot --slot all flash abl abl.img
fastboot reboot
8. Enjoy your fully revived Nokia 8.3 - and all your data should be safe.
Click to expand...
Click to collapse
Hello,
I have followed instructions got 94%, run 0_OpenMeToInstall.cmd got message from script : rebooting into bootloader - finished.
But now phone wont start it just stuck on android one screen and keep on trying to start ...
Do you have any advice ? Tnx
jelo7777 said:
Hello,
I have followed instructions got 94%, run 0_OpenMeToInstall.cmd got message from script : rebooting into bootloader - finished.
But now phone wont start it just stuck on android one screen and keep on trying to start ...
Do you have any advice ? Tnx
Click to expand...
Click to collapse
Looks like you skipped some procedure.
To re-enter Fastboot mode, hold volume down key and power key while connected to PC. When the phone displays android one again, release power key immediately but don't release volume down key. Your phone should boot right into fastboot mode without vibration. You may need to try it multiples of times.
Then, re-open 0_OpenMeToInstall.cmd .
If the phone still reboots itself, save following content into "RegistryFix.reg" (with quotes) and import it.
Code:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\0489C0090100]
"osvc"=hex:00,00
"SkipContainerIdQuery"=hex:01,00,00,00
"SkipBOSDescriptorQuery"=hex:01,00,00,00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\18D1D00D0100]
"osvc"=hex:00,00
"SkipContainerIdQuery"=hex:01,00,00,00
"SkipBOSDescriptorQuery"=hex:01,00,00,00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\2E04C0090100]
"osvc"=hex:00,00
"SkipContainerIdQuery"=hex:01,00,00,00
"SkipBOSDescriptorQuery"=hex:01,00,00,00
Then try again.
hikari_calyx said:
Now check if you can search 00WW_3_490_SP06 update. If not please wait for upload.
Click to expand...
Click to collapse
No updates available.
Looks like last update what there was is 1st of May.
Did i do somehow a rollback or am i running now on the security update which broke my phone in first case?
Kurnauttaja said:
No updates available.
Looks like last update what there was is 1st of May.
Did i do somehow a rollback or am i running now on the security update which broke my phone in first case?
Click to expand...
Click to collapse
You're running the build that broke your phone.
This is the recently pushed 349F update.
HCTSW2_BGT-349F-0-00WW-B01_600WW_12_20230501_huaqin_ZQN1876_UnbrickFix.full.lzma2.f7f1b642.7z | by Hikari Calyx for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
hikari_calyx said:
You're running the build that broke your phone.
This is the recently pushed 349F update.
HCTSW2_BGT-349F-0-00WW-B01_600WW_12_20230501_huaqin_ZQN1876_UnbrickFix.full.lzma2.f7f1b642.7z | by Hikari Calyx for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Click to expand...
Click to collapse
Sorry im completly noob what comes to phone software and tech.
How do i apply that file/update to my now "perfectly" running phone?
Kurnauttaja said:
Sorry im completly noob what comes to phone software and tech.
How do i apply that file/update to my now "perfectly" running phone?
Click to expand...
Click to collapse
Reboot to recovery manually with "adb reboot fastboot" then "fastboot reboot-recovery". Remember to turn on USB debugging.
Then follow the entire procedure. Do not use outdated ADB binary.
hikari_calyx said:
Looks like you skipped some procedure.
To re-enter Fastboot mode, hold volume down key and power key while connected to PC. When the phone displays android one again, release power key immediately but don't release volume down key. Your phone should boot right into fastboot mode without vibration. You may need to try it multiples of times.
Then, re-open 0_OpenMeToInstall.cmd .
If the phone still reboots itself, save following content into "RegistryFix.reg" (with quotes) and import it.
Code:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\0489C0090100]
"osvc"=hex:00,00
"SkipContainerIdQuery"=hex:01,00,00,00
"SkipBOSDescriptorQuery"=hex:01,00,00,00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\18D1D00D0100]
"osvc"=hex:00,00
"SkipContainerIdQuery"=hex:01,00,00,00
"SkipBOSDescriptorQuery"=hex:01,00,00,00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\2E04C0090100]
"osvc"=hex:00,00
"SkipContainerIdQuery"=hex:01,00,00,00
"SkipBOSDescriptorQuery"=hex:01,00,00,00
Then try again.
Click to expand...
Click to collapse
When I enter fastboot mode, re-open 0_OpenMeToInstall.cmd It says : please connect the phone under fastboot mode to PC and nothing happens ... (cursor is blinking...) What am I doing wrong ?
jelo7777 said:
When I enter fastboot mode, re-open 0_OpenMeToInstall.cmd It says : please connect the phone under fastboot mode to PC and nothing happens ... (cursor is blinking...) What am I doing wrong ?
Click to expand...
Click to collapse
Please check your Device Manager and see if there's "Android" listed in "Other devices".
If so please install driver manually - such driver can be searched via Windows Update, Optional updates if you're using Windows 10 or 11.
hikari_calyx said:
Please check your Device Manager and see if there's "Android" listed in "Other devices".
If so please install driver manually - such driver can be searched via Windows Update, Optional updates if you're using Windows 10 or 11.
Click to expand...
Click to collapse
Install update via win update... run script again...
at the end I get message : finished total time 449129s
fastboot: error: could not check if partition abl has slot all
waiting for any device