Fastboot stuck - Nokia 3.2 Questions & Answers

Anyone here can help me, because I'm stuck in fastboot mode after I tried to root my device using magisk.
Qfil not recognise my device (also Adb, using "Adb devices" devices)
Bootloader Unlocked
Unrooted

Hi you need to activate Test Mode in Windows and install qdloader drivers in device manager (listed as Qh_USB_BULK or something like that) Google it. In my Google drive folder is a Firmware for qfil otherwise download it from Hikary calyx Website. Just Google 'Nokia 3.2 edl firmware'. You need to remove those lines in rawprogram0.xml which are not as image there. So compare the filenames in this file and delete those lines where a image is not in that folder (like dp_AP_signed.mbn is not in that folder so remove the line)
Good luck

i am also stuck on fastboot mode. i want to get back to stock rom. whats the procedure

s3tupw1zard said:
Hi you need to activate Test Mode in Windows and install qdloader drivers in device manager (listed as Qh_USB_BULK or something like that) Google it. In my Google drive folder is a Firmware for qfil otherwise download it from Hikary calyx Website. Just Google 'Nokia 3.2 edl firmware'. You need to remove those lines in rawprogram0.xml which are not as image there. So compare the filenames in this file and delete those lines where a image is not in that folder (like dp_AP_signed.mbn is not in that folder so remove the line)
Good luck
Click to expand...
Click to collapse
Would the "Nokia 3.2 edl firmware" work as well for the Nokia 2.2? I haven't found any firmware specific for the 2.2. Also, would the firmware contain the boot.img file? (I just want to root the 2.2 and this is the file I'm missing).

I had the same issue after trying to install an incompatible custom ROM the way I fixed it is by:
1- downloading the stock ROM
2- extract it
3- while the phone is in fastboot flash all .img files like this:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
etc...
after flashing all .img files type
Code:
fastboot reboot
and that's it, it might tell you your phone isn't trusted this will go after a system update.

MRza3ter said:
I had the same issue after trying to install an incompatible custom ROM the way I fixed it is by:
1- downloading the stock ROM
2- extract it
3- while the phone is in fastboot flash all .img files like this:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
etc...
after flashing all .img files type
Code:
fastboot reboot
and that's it, it might tell you your phone isn't trusted this will go after a system update.
Click to expand...
Click to collapse
please teach me how to do this pleaseeee i dont get it

fjeeg said:
please teach me how to do this pleaseeee i dont get it
Click to expand...
Click to collapse
Okay so what you want to do is download the stock ROM, just go in Google then search nokia 3.2 stock ROM, after download right click then extract, then hold shift then right click on nothing in the extracted file then click on open with powershell, after that just type the code

MRza3ter said:
Okay so what you want to do is download the stock ROM, just go in Google then search nokia 3.2 stock ROM, after download right click then extract, then hold shift then right click on nothing in the extracted file then click on open with powershell, after that just type the code
Click to expand...
Click to collapse
mine says that the partition table doesnt exist

Related

my zen faild google verification to boot up

hey
when my phone boots shows that my device is not verified by google , what to do?
Jwtiyar said:
hey
when my phone boots shows that my device is not verified by google , what to do?
Click to expand...
Click to collapse
you might have unlocked bootloader with unofficial method. nothing to worry about its just a warning devices are far more insecure. if you are worried about privacy things. believe there is nothing like secure when using digital devices. and there is not even single service provider which do not collect data. hence enjoy your unlocked device and play around
sukhwant717 said:
you might have unlocked bootloader with unofficial method. nothing to worry about its just a warning devices are far more insecure. if you are worried about privacy things. believe there is nothing like secure when using digital devices. and there is not even single service provider which do not collect data. hence enjoy your unlocked device and play around
Click to expand...
Click to collapse
Thank you bro, the problem is now its not booting (bootlooping)after upgrading bootloader, flashing twrp then flashing RBR ROM, IDK if this is ROM related or bootloader related
Jwtiyar said:
Thank you bro, the problem is now its not booting (bootlooping)after upgrading bootloader, flashing twrp then flashing RBR ROM, IDK if this is ROM related or bootloader related
Click to expand...
Click to collapse
flash boot, fastboot, recovery image for the same firmware u had working last time. if still do not boots. flash bom token, dnx, ifwi for the same firmware. flash boot, recovery and fastboot again while u flash dnx and ifwi.
sukhwant717 said:
flash boot, fastboot, recovery image for the same firmware u had working last time. if still do not boots. flash bom token, dnx, ifwi for the same firmware. flash boot, recovery and fastboot again while u flash dnx and ifwi.
Click to expand...
Click to collapse
You made it really complex bro i dont understand what to do.
Jwtiyar said:
You made it really complex bro i dont understand what to do.
Click to expand...
Click to collapse
the last working firmware. whichever was installed last time. (assume you were on latest MM ww4.21.40.233... extract it and get the files (boot.img, recovery.img, droidboot.img, splashscreen.img) in the same firmware there will be ifwi.zip extract that too and get the files (bom token, dnx , ifwi)... now copy the extracted files to adb fastboot tool folder. and then in same folder move cursor to and empty place and hold shift and right click on mouse. you will get option open command windows here.
now reboot your phone in fastboot mode and connect to PC.. now run the following commands
fastboot devices ( to see if device is recognized by pc and fastboot tool)
fastboot flash splashscreen splashscreen.img
fastboot flash token " bom token file name" (without commas )
fastboot flash dnx "dnx file name"
fastboot flash ifwi "ifwi file name"
fastboot erase boot
fastboot flash boot boot.img
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot erase fastboot
fastboot flash fastboot droidboot.img
fastboot reboot
keep in mind extract files from the same firmware you were on the last time when your device was working.
sukhwant717 said:
the last working firmware. whichever was installed last time. (assume you were on latest MM ww4.21.40.233... extract it and get the files (boot.img, recovery.img, droidboot.img, splashscreen.img) in the same firmware there will be ifwi.zip extract that too and get the files (bom token, dnx , ifwi)... now copy the extracted files to adb fastboot tool folder. and then in same folder move cursor to and empty place and hold shift and right click on mouse. you will get option open command windows here.
now reboot your phone in fastboot mode and connect to PC.. now run the following commands
fastboot devices ( to see if device is recognized by pc and fastboot tool)
fastboot flash splashscreen splashscreen.img
fastboot flash token " bom token file name" (without commas )
fastboot flash dnx "dnx file name"
fastboot flash ifwi "ifwi file name"
fastboot erase boot
fastboot flash boot boot.img
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot erase fastboot
fastboot flash fastboot droidboot.img
fastboot reboot
keep in mind extract files from the same firmware you were on the last time when your device was working.
Click to expand...
Click to collapse
Thank you very much bro,but the last working firmware i dont know which one was but it was 5.1.1, which firmware is that android version?
Jwtiyar said:
Thank you very much bro,but the last working firmware i dont know which one was but it was 5.1.1, which firmware is that android version?
Click to expand...
Click to collapse
device model ze551ml oe ze550ml?
sukhwant717 said:
device model ze551ml oe ze550ml?
Click to expand...
Click to collapse
ze551
Jwtiyar said:
ze551
Click to expand...
Click to collapse
download the following file extract it. now reboot your phone in fastboot mode and connect to pc. wait till pc recognize it and make detection sound.
now it extracted folder double click to run the file update bootloader.bat
all done
report back if device boots or gives any error in cmd
wait it has an error
sukhwant717 said:
download the following file extract it. now reboot your phone in fastboot mode and connect to pc. wait till pc recognize it and make detection sound.
now it extracted folder double click to run the file update bootloader.bat
all done
report back if device boots or gives any error in cmd
wait it has an error
Click to expand...
Click to collapse
before this problem happen i upgraded boorloader to MM then flash TWRP and installed MM ROM so now it has MM Custom ROM.
i did your solution and installed successfully but in adb commands as i saw give that boot.img not found then rebooted and now directly will go to installing system update and give the error (android robot with red warning icon ) .
Jwtiyar said:
before this problem happen i upgraded boorloader to MM then flash TWRP and installed MM ROM so now it has MM Custom ROM.
i did your solution and installed successfully but in adb commands as i saw give that boot.img not found then rebooted and now directly will go to installing system update and give the error (android robot with red warning icon ) .
Click to expand...
Click to collapse
when there at that error screen press and hold volume button you will enter into recovery mode. there go to option reboot bootloader phone will boot in fastboot mode
now in the extracted folder at empty place shift and right click.. then open cmd here and run command
fastboot flash boot boot.img
fastboot reboot
which mm rom you installed?
btw i have corrected the boot.img not found error. you can download and rung the bat file
https://drive.google.com/open?id=0B72QQTXqZSRwSVpwSG9iWS0tbUk
sukhwant717 said:
when there at that error screen press and hold volume button you will enter into recovery mode. there go to option reboot bootloader phone will boot in fastboot mode
now in the extracted folder at empty place shift and right click.. then open cmd here and run command
fastboot flash boot boot.img
fastboot reboot
which mm rom you installed?
btw i have corrected the boot.img not found error. you can download and rung the bat file
https://drive.google.com/open?id=0B72QQTXqZSRwSVpwSG9iWS0tbUk
Click to expand...
Click to collapse
I installed RBR ROM which based on MM , now the error gone after flashing boot.img but the will boot to asus logo and will reboot again it seems its bootloop .
sukhwant717 said:
when there at that error screen press and hold volume button you will enter into recovery mode. there go to option reboot bootloader phone will boot in fastboot mode
now in the extracted folder at empty place shift and right click.. then open cmd here and run command
fastboot flash boot boot.img
fastboot reboot
which mm rom you installed?
btw i have corrected the boot.img not found error. you can download and rung the bat file
https://drive.google.com/open?id=0B72QQTXqZSRwSVpwSG9iWS0tbUk
Click to expand...
Click to collapse
this is the output now after flashing coorected .zip file you provided:
http://paste.ubuntu.com/24395746/
Jwtiyar said:
this is the output now after flashing coorected .zip file you provided:
http://paste.ubuntu.com/24395746/
Click to expand...
Click to collapse
it is bootlooping because of incorrect system
now tell me do u want to flash custom rom or official marshmallow?
sukhwant717 said:
it is bootlooping because of incorrect system
now tell me do u want to flash custom rom or official marshmallow?
Click to expand...
Click to collapse
custom MM
Jwtiyar said:
custom MM
Click to expand...
Click to collapse
as you already downloaded that rom.. and also the recovery needed for that rom..
first of all same as earlier flash MM bootloader. ther reboot bootloader once then flash twrp. the exactly mentioned in the RBR rom thread. then go to advanced in twrp and click adb sidelaod. tick wipe dalvik cache and cache. swipe to sideload ... now run command adb sideload "rom file name"
if bootloops after flashing firmware. do a factory reset and reboot. going to sleep now 1.15 AM here. will answer tomorrow if any other question
sukhwant717 said:
as you already downloaded that rom.. and also the recovery needed for that rom..
first of all same as earlier flash MM bootloader. ther reboot bootloader once then flash twrp. the exactly mentioned in the RBR rom thread. then go to advanced in twrp and click adb sidelaod. tick wipe dalvik cache and cache. swipe to sideload ... now run command adb sideload "rom file name"
if bootloops after flashing firmware. do a factory reset and reboot. going to sleep now 1.15 AM here. will answer tomorrow if any other question
Click to expand...
Click to collapse
thank you very much now its booted successfully
Jwtiyar said:
thank you very much now its booted successfully
Click to expand...
Click to collapse
great good to know your device is alive again
sukhwant717 said:
great good to know your device is alive again
Click to expand...
Click to collapse
Thank you bro

Question Need help rooting the Poco F3

Hello fellow XDA'ers
I have waited and unlocked the phone, running the MIUI 12.5.1.0 (RKHEUXM) the EU Official Rom that came with the phone, and was following the guide on how to root from NaldoTech, but i'm stuck, magisk can't patch any Firmware file i throw at it...
Don't know what i am doing wrong, i opened the zip files manually looking for the boot.img file but i cant seem to find it in any of the Firmwares i download from XiaomiFirmwareUpdater.
Also tried downloading the rom file and extracting the contents using the xiaomi-flashable-firmware-creator, but no luck with that either, throws some permission error at extracting the payload.bin
what can i do from here??
thanks in advance
Easy peasy
Steps
Download Adb and fastboot tool.
Or just download TWRP image and start CMD from there "the folder containing the twrp img" (in destination bar type cmd and press Enter) /the drivers should be installed and working properly ofc.
1- set phone in fastboot mode then plug it in to PC
2- Type: fastboot boot twrp.img (twrp here is the img file)
Then the phone will boot into twrp.
The phone will be shown in PC. Paste Magisk in the phone. Then go back and flash it using TWRP. Then reboot to system. And you're all done.
laid1995 said:
.
Click to expand...
Click to collapse
doesnt boot to twrp just turns off :S
Fyat said:
doesnt boot to twrp just turns off :S
Click to expand...
Click to collapse
You're doing something wrong then.
Check all drivers are set up properly. Try flashing twrp then boot to it using Volume UP + Power button.
Make sure you download Nebrassy's twrp 3.5.10
Managed to do it, not with twrp tho, the way i intended originally, i found this payload extractor, went on miui and download latest package (on the phone), after that sent the file to pc and extracted the contents to the payload extractor tool, follow the tool's guide and Tadaaaa! got yoursef a boot.img.
after that was simple and follow the rest of the NaldoTech guide, which is sending the boot.img to phone, open magisk manager, click install, select the boot image to pach, wait couple seconds and done. After that just copy the magisk patched boot image to pc and turn off your phone, enter fastboot, and flash the boot.img in boot_a and boot_b.
and you are done boot the phone and open magisk app to see the installed confirmation
Fyat said:
Managed to do it, not with twrp tho, the way i intended originally, i found this payload extractor, went on miui and download latest package (on the phone), after that sent the file to pc and extracted the contents to the payload extractor tool, follow the tool's guide and Tadaaaa! got yoursef a boot.img.
after that was simple and follow the rest of the NaldoTech guide, which is sending the boot.img to phone, open magisk manager, click install, select the boot image to pach, wait couple seconds and done. After that just copy the magisk patched boot image to pc and turn off your phone, enter fastboot, and flash the boot.img in boot_a and boot_b.
and you are done boot the phone and open magisk app to see the installed confirmation
Click to expand...
Click to collapse
Whatever was your way, I'm glad you managed to do it
sir i need boot.img file for poco f3
ZAki6464 said:
sir i need boot.img file for poco f3
Click to expand...
Click to collapse
Good
Which version do you need?
Is this international version I should get to use in USA on T-Mobile to root the same way as you?
Amazon F3
I'm using Europe version currently on Global 12.5.6.0 (RKHEUXM)
Fyat said:
I'm using Europe version currently on Global 12.5.6.0 (RKHEUXM)
Click to expand...
Click to collapse
Do you have access to gpu rendering tweaks in turbo game mode ? I can't make it work, I'm on same version than you
Greenspoof said:
Do you have access to gpu rendering tweaks in turbo game mode ? I can't make it work, I'm on same version than you
Click to expand...
Click to collapse
I'm not sure where to find these options as i do not use the turbo mode, can you point to it?

I installed linux by a mistake into my nokia 3.2 and now i am stuck in fastboot

I installed Linux by a mistake into my Nokia 3.2 which led me here, I am stuck in fast boot mode I tried multiple solutions like scratching the edl trigger, going to recovery mode, and restarting the bootloader. it only vibrates and reopens the fastboot menu, I cannot install, or perhaps I don't know how to install the default OS, IMG, or whatever you call it I am really new to this kinda stuff, sorry, and I appreciate your help.
I had the same issue after trying to install an incompatible custom ROM the way I fixed it is by:
1- downloading the stock ROM
2- extract it
3- while the phone is in fastboot flash all .img files like this:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
etc...
after flashing all .img files type
Code:
fastboot reboot
and that's it, it might tell you your phone isn't trusted this will go after a system update.
MRza3ter said:
I had the same issue after trying to install an incompatible custom ROM the way I fixed it is by:
1- downloading the stock ROM
2- extract it
3- while the phone is in fastboot flash all .img files like this:
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
etc...
after flashing all .img files type
Code:
fastboot reboot
and that's it, it might tell you your phone isn't trusted this will go after a system update.
Click to expand...
Click to collapse
to download the stock ROM just search Nokia 3.2 stock rom

Oppo A83 [CPH1729] TWRP RECOVERY

⚠Warning: This is not official TWRP, use it at your own risk!!!
Data will be erased. Back up if neccessary
This device is kind of weird so to flash twrp you need these things:
1. Prepare materials​
Install driver so as to have access to preloader (Just install automatically and no need to do anything in device manager)
This software to access to preloader -> fastboot (fastboot is somehow not available via adb methods) Enter fastboot
This tool for flashing
2. Unlock bootloader (need testpoint, python, git (optional) - you can search on google)​
Use this tool - go to this section. Follow guides to unlock bootloader (remember to use testpoint not hardware buttons)
3. Enter fastboot mode​
Use latest MTK META Ultility tool
Select Reboot Fastboot Mode in BRom section
Hold volume down button. While holding connect it to your computer
*Now your phone is in fastboot mode​4. Flash​
Open platform-tools folder in Downloads folder
Shift + Right click then "open command window here"
Input these commands into cmd
fastboot flash boot drag twrp file to cmd
fastboot flash recovery drag twrp file to cmd.
fastboot reboot. Swipe to allow modification in twrp (to make sure that stockboot wont replace twrp). After that reboot to recovery to make it installed on your device permanently.
Now your recovery is ready to flash file you can push stock image file to your root folder using adb command: "adb push. Drag the stock image file. /" (Because Decryption right now doesnt work on my device yet)
Enjoy
*Sounds crazy but it is required to make sure twrp is installed correctly​*If successful, when you power on, you will get a red section on top of your device. If you want to recover to stock recovery, flash the recovery.img below.​*Also, if you want to make your own twrp, you can try recovery.img below.​
Also thanks SebaUbuntu and Mofadal El-Tayeb (مُفَضَّل) for awesome apps
​
​​
​
Here is the PBRB version for this device
Hey I'm stuck in the third step.can you please help me?
Sorry for late reply. What problems do you have?
Is this the stock boot image you provided?
SAMIUL ISLAM 0 said:
Is this the stock boot image you provided?
Click to expand...
Click to collapse
Yes it is. I took it from OTA update
Hey friends
I want to upgrade my oppo a 83 fone to a costum rom to upgrade my androide to android 8 or higher
mahmoud2503 said:
Hey friends
I want to upgrade my oppo a 83 fone to a costum rom to upgrade my androide to android 8 or higher
Click to expand...
Click to collapse
Unfortunately, I have no custom roms available for this phone (

Question Devices not detected after install Fastboot ROM

I try to install fastboot rom with MiFlashTool, this is my FastbootROM nabu_global_images_V14.0.3.0.TKXMIXM_20230306.0000.00_13.0_global_80c69df295.tgz
After i flash with MiFlashTool, the process is never end, but my Mi Pad 5 restarting without any reason in middle of flashing, but the process keep going, then i close the MiFlashTool, after that i try to fastboot devices in my platform tools directory, now my Mi Pad completely undetected in my PC, also in MiFlashTool now not detected
I can still open Recovery and Fastboot mode, but in Fastboot mode i cant do anything because my PC cant detect my devices, also i try with my other PC but still not detected, maybe the main reason this happend is because i terminate the MiFlashTool during process because i saw my Mi Pad restarting, any help for this issue ?
kzquandary said:
I can still open Recovery and Fastboot mode
Click to expand...
Click to collapse
It indicates that your bootloader is still full functional. Otherwise recovery wouldn't boot anymore.
- Windows device manager shows what?
- output of 'fastboot devices'?
WoKoschekk said:
It indicates that your bootloader is still full functional. Otherwise recovery wouldn't boot anymore.
- Windows device manager shows what?
- output of 'fastboot devices'?
Click to expand...
Click to collapse
the problem for devices not detected is solved sir, but now i stuck in fastboot mode every time i use fastboot reboot, because last time ago i want to try disable-verity using empty vbmeta.img, then after i try command fastboot flash --disable-verity vbmeta.img, i ended up in Fastboot Mode, now i want to try install new rom sir and i have download it miui_NABUGlobal_V14.0.3.0.TKXMIXM_45f6ebc192_13.0.zip , any tips for install this rom to Mi Pad ? because i cant use mi flash tool for install new rom
kzquandary said:
because i cant use mi flash tool for install new rom
Click to expand...
Click to collapse
Did u try this one?
XiaoMiTool V2 - Modding of Xiaomi devices made easy for everyone
XiaoMiTool V2 is a easy to use tool to install rom on your Xiaomi device. Modding made easy for everyone! Download it for free now!
www.xiaomitool.com
WoKoschekk said:
Did u try this one?
XiaoMiTool V2 - Modding of Xiaomi devices made easy for everyone
XiaoMiTool V2 is a easy to use tool to install rom on your Xiaomi device. Modding made easy for everyone! Download it for free now!
www.xiaomitool.com
Click to expand...
Click to collapse
i downloaded your suggested app, but there is no Xiaomi Pad 5 in device list, and my downloaded recovery rom is zip, i just cant find tool for flash zip in fastboot sir
Your download is only a recovery ROM and not the full fastboot ROM. Full fastboot ROM:
MiPad 5 – MIUI Download Xiaomi Official ROM
Ok, a recovery zip is only flashable in a recovery. It's like any other flashable zip for TWRP, i.e. a Magisk installer zip or sth else. These zips need a shell to execute their commands. Fastboot is only for flashing single images via cmd line on your PC.
Download the full fastboot ROM. It's a *.tgz-archive that needs to be unpacked for the Mi Flash Tool (v2).
WoKoschekk said:
Ok, a recovery zip is only flashable in a recovery. It's like any other flashable zip for TWRP, i.e. a Magisk installer zip or sth else. These zips need a shell to execute their commands. Fastboot is only for flashing single images via cmd line on your PC.
Download the full fastboot ROM. It's a *.tgz-archive that needs to be unpacked for the Mi Flash Tool (v2).
Click to expand...
Click to collapse
Thanks sir, its worked, i use fastboot room with .tgz and all solved
WoKoschekk said:
Ok, a recovery zip is only flashable in a recovery. It's like any other flashable zip for TWRP, i.e. a Magisk installer zip or sth else. These zips need a shell to execute their commands. Fastboot is only for flashing single images via cmd line on your PC.
Download the full fastboot ROM. It's a *.tgz-archive that needs to be unpacked for the Mi Flash Tool (v2).
Click to expand...
Click to collapse
But any tips for permanent root in Mi Pad 5 sir ? because every time i restart, its always unrooted
kzquandary said:
But any tips for permanent root in Mi Pad 5 sir ? because every time i restart, its always unrooted
Click to expand...
Click to collapse
Install the Magisk app, extract the boot.img from inside your firmware and patch it with Magisk. Then flash the patched boot.img with fastboot flash boot "your patched image" and start your device.
WoKoschekk said:
Install the Magisk app, extract the boot.img from inside your firmware and patch it with Magisk. Then flash the patched boot.img with fastboot flash boot "your patched image" and start your device.
Click to expand...
Click to collapse
Wow thanks sir, its worked like magic

Categories

Resources