Database Info

Stuck Rooting @ tf300t

hi guys,
i was following this thread guide http://forum.xda-developers.com/showthread.php?t=1668173
and while i'm on step 5, i accidentally pick the wipe data (available options are RCK, Android and Wipe Data)
now, i am stuck in this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and totally unable to mount sdcard, emmc. Hopefully my tablet hasn't bricked yet.

johnson234 said:
hi guys,
i was following this thread guide http://forum.xda-developers.com/showthread.php?t=1668173
and while i'm on step 5, i accidentally pick the wipe data (available options are RCK, Android and Wipe Data)
now, i am stuck in this View attachment 2454401 and totally unable to mount sdcard, emmc. Hopefully my tablet hasn't bricked yet.
Click to expand...
Click to collapse
I remember on the old bootloader that ended in and insta-brick, but idk which BL you are on.

cmendonc2 said:
I remember on the old bootloader that ended in and insta-brick, but idk which BL you are on.
Click to expand...
Click to collapse
By BL u mean bootloader? My stock bootloader is 4.2.1 Jelly Bean. I tried to dl the twrp.blob from the twrp website with -4.2 and try to use the terminal emulator thingy but it still boot into CWM based Recovery.
However, I just bought the ROM Toolbox Pro in Google Play and use the 'Flash Recovery' but it search my whole tablet and returns nothing while i have already copy and paste the twrp.blob into the/sdcard/

johnson234 said:
By BL u mean bootloader? My stock bootloader is 4.2.1 Jelly Bean. I tried to dl the twrp.blob from the twrp website with -4.2 and try to use the terminal emulator thingy but it still boot into CWM based Recovery.
However, I just bought the ROM Toolbox Pro in Google Play and use the 'Flash Recovery' but it search my whole tablet and returns nothing while i have already copy and paste the twrp.blob into the/sdcard/
Click to expand...
Click to collapse
Edit: I am a first timer a.k.a. newbie. Sorry for that if i don't understand the short form/ slang u used.

johnson234 said:
By BL u mean bootloader? My stock bootloader is 4.2.1 Jelly Bean. I tried to dl the twrp.blob from the twrp website with -4.2 and try to use the terminal emulator thingy but it still boot into CWM based Recovery.
However, I just bought the ROM Toolbox Pro in Google Play and use the 'Flash Recovery' but it search my whole tablet and returns nothing while i have already copy and paste the twrp.blob into the/sdcard/
Click to expand...
Click to collapse
Wait it boots into android? What exactly are you trying to do? Just install the Superuser binaries for root or get a custom ROM?

cmendonc2 said:
Wait it boots into android? What exactly are you trying to do? Just install the Superuser binaries for root or get a custom ROM?
Click to expand...
Click to collapse
I plan to root it into a custom rom but ended up installing cwm which I later found out to be incompatible with my device. This is because I thought that everyone need to undergo these three process (root>install recovery>install rom) now I'm trying to remove or replace this cwm with a twrp then I can start installing my custom rom. I have already root my tablet with supersu (kingo). Did I do anything wrong on my steps above? If yes, please enlighten me. Thanks
anyway, what's a super user binary?

johnson234 said:
I plan to root it into a custom rom but ended up installing cwm which I later found out to be incompatible with my device. This is because I thought that everyone need to undergo these three process (root>install recovery>install rom) now I'm trying to remove or replace this cwm with a twrp then I can start installing my custom rom. I have already root my tablet with supersu (kingo). Did I do anything wrong on my steps above? If yes, please enlighten me. Thanks
anyway, what's a super user binary?
Click to expand...
Click to collapse
OK download the -42 TWRP recovery for jellybean onto your computer. Use fastboot (http://forum.xda-developers.com/showthread.php?p=42407269) to flash the bootloader to your tablet with:
Code:
fastboot flash recovery TWRP.img -i 0x0b05
Then reboot into Android and reboot again into TWRP to flash a custom ROM.

cmendonc2 said:
OK download the -42 TWRP recovery for jellybean onto your computer. Use fastboot (http://forum.xda-developers.com/showthread.php?p=42407269) to flash the bootloader to your tablet with:
Code:
fastboot flash recovery TWRP.img -i 0x0b05
Then reboot into Android and reboot again into TWRP to flash a custom ROM.
Click to expand...
Click to collapse
Sorry to tell you but everytime i try to fastboot, (tried this even before posting the problem here) i get this error. Waiting for like 10mins, the 'waiting for device' message is still there.
Command I used,
fastboot flash recovery TWRP.img -i 0x0b05
Click to expand...
Click to collapse
After pressing enter, i get this
< waiting for device >
Click to expand...
Click to collapse
Edit; sorry for the screenshot, typed the command wrong but tried it with the correct 1 but the outcome still the same.

I'm thinking that is it usb drivers problem? currently running on Win8 Professional 64bit.

johnson234 said:
I'm thinking that is it usb drivers problem? currently running on Win8 Professional 64bit.
Click to expand...
Click to collapse
Fastboot utility is very sensitive to connection type. It can refuse to work on some laptops and usb ports on front pannel of desktop PC. Also do not use usb hub or tablet dock with fastboot. And if Windows device manager shows tablet as something like "asus bootloader interface" or "asus fastboot interface" (don't remember exact name) is probably shouldn't be a driver issue.

Graiden05 said:
Fastboot utility is very sensitive to connection type. It can refuse to work on some laptops and usb ports on front pannel of desktop PC. Also do not use usb hub or tablet dock with fastboot. And if Windows device manager shows tablet as something like "asus bootloader interface" or "asus fastboot interface" (don't remember exact name) is probably shouldn't be a driver issue.
Click to expand...
Click to collapse
It has these 2 (see attachment) and I even can use ASUS SYNC perfectly. So i guess the usb driver wont be a problem?

johnson234 said:
It has these 2 (see attachment) and I even can use ASUS SYNC perfectly. So i guess the usb driver wont be a problem?
View attachment 2457522
Click to expand...
Click to collapse
Did You know that to use fastboot tablet should be loaded in fastboot mode? If You connect it in fastboot mode and Windows shows no recognised fastboot or bootloader interface You need a proper driver.

So, you suggest that i need to use a different pc to do the fastboot thing? What are the drivers do i need to install? Where can i download it? Maybe my wind8 64bit professional got some flaw/bug. Thanks for helping. Will try it out when i get back home.

cmendonc2 said:
OK download the -42 TWRP recovery for jellybean onto your computer. Use fastboot (http://forum.xda-developers.com/showthread.php?p=42407269) to flash the bootloader to your tablet with:
Code:
fastboot flash recovery TWRP.img -i 0x0b05
Then reboot into Android and reboot again into TWRP to flash a custom ROM.
Click to expand...
Click to collapse
I get something like this. But when i reboot into android and reboot it, i still get boot into CWM recovery. Nothing changed

Update : I try flashing the TWRP recovery again, but now its freezing on the fastboot mode. Probably still installing. Hopefully everything went well and i can successfully install it.

Graiden05 said:
Did You know that to use fastboot tablet should be loaded in fastboot mode? If You connect it in fastboot mode and Windows shows no recognised fastboot or bootloader interface You need a proper driver.
Click to expand...
Click to collapse
After i run this command
fastboot -i 0x0b05 flash recovery TWRP.img
Click to expand...
Click to collapse
it freeze.(I have waiting for 30mins but still nothing significant comes up.)
There is three option to choose from (RCK, Android and WipeData)
Now under the "Device and Printer", there is a fastboot devices (unspecified). But when i see it in properties of this fastboot device, it's manufacturer is still under ClockworkMod. See attachment

Try this guide.

[Recovery] TWRP 3.2.1-0 for GPD XD Plus / XD+ Handheld MT8176

Update: Thread outdated. A new and working version of TWRP was posted in another Forum. Thanks.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I get this
PS: On instructions for second method you may want to mention you have to rename twrp image to recovery.img

My device is now stuck in the fastboot menu. It says I can navigate the menu using volume up and down but pressing either of those doesn't do anything and I can't seem to power off the device by holding the power button. Any suggestions on how to fix this?

laod said:
My device is now stuck in the fastboot menu. It says I can navigate the menu using volume up and down but pressing either of those doesn't do anything and I can't seem to power off the device by holding the power button. Any suggestions on how to fix this?
Click to expand...
Click to collapse
Some people have reported that touch isn't working and partitions aren't mounting properly. I tried to fix most issues and uploaded a new version. I do not own this device personally - so i can not test the fixes. Please give me feedback for the updated version.

I just got my GPD XD+ today, thanks for the TWRP build but on mine, even with the current build (2018/04/01), I can't perform any actions. Touch still seems not to work for me. I can't get past TWRP asking me "Keep System Read-only?" Let alone see if partitions are loading correctly.
Everything is in portrait mode which is awkward for this device. What about landscape? Shouldn't it be 1280x720 rather than 720x1280?
**Update**
It would appear that my touch controls are inverted... so the fix for others, seems to have inverted my own.
**Update 2***
Well... after realizing the touchscreen was reversed for me, I was able to slide the "Swipe to allow modifications" slider but after that, I chose to reboot out of recovery since the likelyhood of me hitting something by mistake with the controls reversed was high. Being very careful, I was able to tell it to reboot to system and now the system hangs at the GPD logo.. which no longer animates... I can no longer boot into anything but recovery and fastboot.
Any theories as to what has happened? Does anyone have a Clean Stock ROM of the plus model so I can start over using adb?
**Update 3**
PsyOps pointed me towards some stock images at "forum.gpd.hk/t3-the-latest-firmware-of-gpd-game-console" and I'm back in business. Had to flash more than just recovery and boot.. had to flash system as well for some reason.

Goayandi said:
Some people have reported that touch isn't working and partitions aren't mounting properly. I tried to fix most issues and uploaded a new version. I do not own this device personally - so i can not test the fixes. Please give me feedback for the updated version.
Click to expand...
Click to collapse
I have the same situation here.
It happened after unlocked the bootloader, so it's nothing to do with the recovery.
The adb commend return the error: device '(null)' not found.

I can't check the "recovery" box. It doesn't do anything. And the first methode doesn"t work
EDIT : nevermind, I did it but same problem as Busted77

laod said:
My device is now stuck in the fastboot menu. It says I can navigate the menu using volume up and down but pressing either of those doesn't do anything and I can't seem to power off the device by holding the power button. Any suggestions on how to fix this?
Click to expand...
Click to collapse
Same thing here. Now waiting for the battery to empty. What happens after that? Will it work fine and the bootloader be unlocked?

vanzan said:
Same thing here. Now waiting for the battery to empty. What happens after that? Will it work fine and the bootloader be unlocked?
Click to expand...
Click to collapse
I was being dinner and used adb commands instead of fast boot. If you have your device plugged into a computer with fastboot setup you can run "fastboot reboot" and everything should work.

vanzan said:
Same thing here. Now waiting for the battery to empty. What happens after that? Will it work fine and the bootloader be unlocked?
Click to expand...
Click to collapse
Wait for the battery runs out, then recharge, it works fine and the bootloader is unlocked, the first boot will take longer and a few reboot.
And I find that any time you issue fastboot command from you pc, the xd plus will stuck and you have to wait the battery runs out.
I installed the Magisk use fastboot method, stuck again, and need to wait for the battery runs out, recharged, and evertyhing ok then.
There's another root method on Chinese forum (flash supersu pack by recovery), since I rooted by installin Magisk, I didn't try that.
---------- Post added at 11:46 ---------- Previous post was at 11:45 ----------
laod said:
I was being dinner and used adb commands instead of fast boot. If you have your device plugged into a computer with fastboot setup you can run "fastboot reboot" and everything should work.
Click to expand...
Click to collapse
No, when I stuck in the fastboot menu, the adb command return error that no device can find, I have to unplug battery or wait for the battery runs out.

"fastboot reboot" worked perfectly for me!

Fastboot stuck
Same problem here.
I installed the drivers but got the error.
Now my device is in fastboot mode but fastboot reboot etc. don't work.. And I just can't turn it off..
Im really sad.
Windows 10 x64

So.. At least I could fix the problem, I installed the Drivers (had do disable driver signature) and installed your TWRP Mod successfully but the Screen is mirrored! U can use it but its very tricky.. I could open "Install" But if I open it, twrp could not load any data it called "0MB Space" and yeah after reboot, my GPD XD Plus DON'T start..

LeraxGER said:
So.. At least I could fix the problem, I installed the Drivers (had do disable driver signature) and installed your TWRP Mod successfully but the Screen is mirrored! U can use it but its very tricky.. I could open "Install" But if I open it, twrp could not load any data it called "0MB Space" and yeah after reboot, my GPD XD Plus DON'T start..
Click to expand...
Click to collapse
I had the same issue, could use it inverted and mirrored but after running it and not doing anything with it, I could no longer boot into system... Only into recovery. If I tried to boot into system, the boot animation would never animate and the system would hang.
See PsyOps' reply to my question of where to find a stock rom. You can either use the provided tool or you can use adb commands to reflash your system partition... At least for me I had to flash system... Flashing boot and recovery (removing TWRP) didn't work alone...
reddit.com/r/gpdxd/comments/8a50vq/gpd_xd_plus_stock_rom_available/

Busted77 said:
I had the same issue, could use it inverted and mirrored but after running it and not doing anything with it, I could no longer boot into system... Only into recovery. If I tried to boot into system, the boot animation would never animate and the system would hang.
See PsyOps' reply to my question of where to find a stock rom. You can either use the provided tool or you can use adb commands to reflash your system partition... At least for me I had to flash system... Flashing boot and recovery (removing TWRP) didn't work alone...
reddit.com/r/gpdxd/comments/8a50vq/gpd_xd_plus_stock_rom_available/
Click to expand...
Click to collapse
Thanks for the advice, I spoke with him too and he already gave me the guide how to boot into Recovery Mode and then fastboot (Hold VOL+ & On Off Untill Menu apperas, then boot into recovery, then if the android guy appears press On/Off and THEN VOL+, so you're in the normal recovery mode for all the other poor user's )
And I flashed system.img, boot and stock recovery and then it booted up..
The only thing is, that I think that the SD card won't mount correctly anytime and if I plug it to the PC, I dont see the SD card and big files (like the StockROM Update 1.10 abort before its finished).
Greetings

Contact me in discord.

Could you please close the thread and delte the download link? Not even once your TWRP worked, please don't share the file anymore. Other user's will brick their device too.

Hello how to fix a black screen caused by overheating device?i dont know how to use the stock recovery i have thr gpd boot logo but after a black screen and blue led thanks

[GUIDE]Bootloader Unlock Realme C12

After 6 months from launch date, we finally got bootloader unlock permission on March 2nd 2020 for Realme C12 initially based on Realme UI 1.0. Later Realme gave permission for UI 2.0 too.
Before doing anything to device, keep a copy of Stock ROM from here in your PC or SD Card.
Unlocking bootloader will trip safetynet. If you want to use bank apps or some apps that use SafetyNet, then you have to pass SafetyNet. To pass it we have to use a Magisk module called 'Universal SafetyNet fix' Or use a custom rom or GSI that uses it if you dont want Magisk.
Also locking bootloader seems to lead 'Red State' in many devices. This can only be solved by going to Service Center. So be prepared for it. To get rid of it flash stock rom once even if you didn't done any modifications.
Prerequisites:-​- A PC
- USB Cable(We can use charger cable)
- Platform-tools
- Patience
Step 0 - Great! You're ready to go. Make sure to backup your phone's data before continuing on with this tutorial, as unlocking will make it factory reset (wipe)!
Step 1 - Download and Open In Depth Tool from below
For UI 1.0 https://download.c.realme.com/flash/Unlock_tool/DeepTest_realmeC12.apk
For UI 2.0 https://c.realme.com/in/post-details/1526491339024314368
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step 2 - Click “Start applying”.
Step 3 - Please read the disclaimer in detail, select the checkbox, and submit your application
Step 4 - The Application Will be checked by realme Servers..(Wait 10 mins)
Step 5 - Go back. Remove app from Recent apps. Open the app and click on Query verification status which is at top right
Step 6 - You can now click “Start the in-depth test” and the device will reboot to fastboot mode automatically. The following string will display on the screen: fast boot_unlock_verify ok
Step 7 - Now Download and install the fastboot tool on your PC and Connect the device to PC using USB cable and ready to unlock it.
Step 8 - Now you are in Fastboot Mode. Type this command
Code:
fastboot flashing unlock
in command prompt of PC and Press enter.
Step 9 - On your phone press the Volume Down key to select "UNLOCK THE BOOTLOADER” (or press the Volume Up key if you have changed your mind to select "DO NOT UNLOCK THE BOOTLOADER”).
Step 10 - Now type
Code:
fastboot reboot
. Your phone will reboot and all user data on the phone will be erased - I recommend you perform a data backup prior to applying.
And there you go! Your phone will reboot and you can set it all up again. with the ability to root and you can also install GSIs/custom ROMs/recovery!
After unlocking, flash stock rom once from stock recovery to fix some 'Red state' issue and fastboot errors that may lead to GSI booting issues. See this for flashing stock rom. With this you will also get a idea of flashing stock rom.​
Q: Will unlocking my bootloader void my warranty?
A: No, it will not. Unless you brick your device.
Q: I tried unlocking my bootloader but, PC doesn't detect my phone, even though it's in fastboot mode and connected. Help?
A: Here are some things you can try:
- Try another USB port.​- Try another USB cable.​- Download and install exe for 64-bit and 32-bit​- Restart PC​- Connect device to PC​- Go to Device Manager​- Double Click on Unidentified Realme C12(Device with exclamation mark)​- Click on Update Driver​- Select Browser my computer​- Select Let me pick​- Select Android Device​- Click on Next​Enjoy!​
Q: I am getting carrier-customized phone?
A: See this

Relock your bootloader
Locking bootloader without flashing stock rom again may lead to 'Red State'(can only be fixed by flashing stock rom with PC). So before locking bootloader, flash stock rom in stock recovery and boot to stock rom once.
Tutorial:
Step 0 - Flash stock ROM in stock recovery.(Don't skip this step even if you haven't done any modification)
Step 1 - Download the unlock tool again to apply to exit the in-depth test.
Step 2 - Click “Apply to exit in-depth test”. You should manual operation enter the Fastboot mode(Press both the Volume down button and the Power button when power is off).
Step 3 - In the Fastboot mode, use the engineering command below on your PC to re-lock the bootloader.
- Enter the command: fastboot flashing lock​Step 4 - Press the Volume Down button to select the “Lock bootloader” option (or press the Volume Up button to select “Do not lock bootloader" and keep it unlocked).
Step 5 - Then enter command fastboot reboot. The phone will reboot. All user data on the phone will be erased - we recommend you perform a data backup prior to applying.
Thanks
To this

You are showing relame 6pro device

adityalonkar said:
You are showing relame 6pro device
Click to expand...
Click to collapse
All realme devices share same set of procedure. So it is not a problem.
I am using Realme C12 and successfully done all these things.
Thanks

HemanthJabalpuri said:
All realme devices share same set of procedure. So it is not a problem.
I am using Realme C12 and successfully done all these things.
Thanks
Click to expand...
Click to collapse
Ok Thanks

adityalonkar said:
Ok Thanks
Click to expand...
Click to collapse
Is there chances for getting twrp image for c12 ?

adityalonkar said:
Is there chances for getting twrp image for c12 ?
Click to expand...
Click to collapse
We have both TWRP and custom ROMs too. But they are in C11 forums. All C11 things can be used in C12 and C15(MTK) too. So have a look at https://forum.xda-developers.com/f/realme-c11-roms-kernels-recoveries-other-deve.10991/
Also join us at Telegram by searching 'Realme C12'.
Thanks

HemanthJabalpuri said:
We have both TWRP and custom ROMs too. But they are in C11 forums. All C11 things can be used in C12 and C15(MTK) too. So have a look at https://forum.xda-developers.com/f/realme-c11-roms-kernels-recoveries-other-deve.10991/
Also join us at Telegram by searching 'Realme C12'.
Thanks
Click to expand...
Click to collapse
Thanks a lot

Can you make a full tutorial on flashing twrp image on realme c12 device ?

adityalonkar said:
Can you make a full tutorial on flashing twrp image on realme c12 device ?
Click to expand...
Click to collapse
Will try later.
Thanks

adityalonkar said:
Can you make a full tutorial on flashing twrp image on realme c12 device ?
Click to expand...
Click to collapse
Just made a guide at https://forum.xda-developers.com/t/custom-roms-and-recovery-for-realme-c12.4250073/

I'm stuck in "fast_boot_unlock verify ok"
HemanthJabalpuri said:
fast_boot_unlock_verify ok
Click to expand...
Click to collapse
Nothing happens when I enter the command fastboot devices.
Any help will be appreciated.

ramcadag said:
I'm stuck in "fast_boot_unlock verify ok"
Nothing happens when I enter the command fastboot devices.
Any help will be appreciated.
Click to expand...
Click to collapse
See the drivers question in the guide. You need to install drivers for working.
Thanks

I have updated to realme UI 2.0 android version 11 how to unlock bootloader. plzz help .I have to root this phone. Plzz

Raqeshpati said:
I have updated to realme UI 2.0 android version 11 how to unlock bootloader. plzz help .I have to root this phone. Plzz
Click to expand...
Click to collapse
I guess, there is no support for UI2 yet.
So wait for it or downgrade
Thanks

I have two questions
1. I have a Realme c12 device (Realme UI 1.0), it's device model is RMX2189 but the link you provided has only RMX2185 version. Can I flash that stock rom in my phone?
2. I am from Bangladesh, which region version should I flash? (Egypt, Combodia, Indonesia, India, Pakistan, Vietnam)

Shawmik said:
I have two questions
1. I have a Realme c12 device (Realme UI 1.0), it's device model is RMX2189 but the link you provided has only RMX2185 version. Can I flash that stock rom in my phone?
2. I am from Bangladesh, which region version should I flash? (Egypt, Combodia, Indonesia, India, Pakistan, Vietnam)
Click to expand...
Click to collapse
For first question, you can install RMX2185 version. Since C11, C12 and C15 use RMX2185 for stock rom ozips.
For second question, I am not sure what to do with your region.
Thanks

HemanthJabalpuri said:
For first question, you can install RMX2185 version. Since C11, C12 and C15 use RMX2185 for stock rom ozips.
For second question, I am not sure what to do with your region.
Thanks
Click to expand...
Click to collapse
Thanks a lot. I am facing some problems while trying to unlock bootloader. (Forgive me, I am a noob )
I have successfully installed platform-tools, granted usb debugging permission and rebooted my phone to fastboot mode from depth tool. It's showing "fast boot_unlock_verify ok".
Now if I enter the command "fastboot flashing unlock" in command prompt window, it's showing this message: "waiting for device" and nothing is happening afterwards... Am I missing any drivers? (My cable is ok)

@Shawmik
Yeah you are doing right.
But seems like drivers are not installed.
See the questions in bottom of my guide to get solution.
Thanks

HemanthJabalpuri said:
@Shawmik
Yeah you are doing right.
But seems like drivers are not installed.
See the questions in bottom of my guide to get solution.
Thanks
Click to expand...
Click to collapse
I don't know why I am facing these weird issues, sorry for bothering you...
I have installed the driver you mentioned in the questions section, now if I connect my phone while in fastboot mode, my PC detects it but if I give the command "fastboot flashing unlock", the command prompt still shows "Waiting for device"...
And I tried going to device manager and manually update my device drivers (as you guided), still the same

[CLOSED] [FREE] [9.0,10.0 &11.0] Bootloader unlock for Nokia 7.2 [2021-06-22]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Free Bootloader unlock for Nokia 7.2​
Well , after 2 years finally the dream come true. yes , we achieved what we seen in the title of my thread. atlast free bootloader unlock for Nokia 7.2 running on any android version especially android 10 & upcoming android 11 as well.
So what is the magic behind free bootloader unlock? Yes ! Iam not gonna reveal that but yes as a Nokia community Developer this is what I can provide for your all.
A big massive thank you for my back-end team @hikari_calyx , @singhnsk & especially My Nokia 7.2 & 6.2 community for strong support behind the journey.
So what is the exact steps to make it successfull on your Phone.
1. Make sure you own Nokia 7.2 device & computer running on linux or windows
2. Connect phone to computer & enable developer options
3. Enable usb debugging
4. Download adb platform tools latest from Google & Open command prompt , type adb devices
5. Type adb reboot recovery
6. Make sure your device should boot in to stock recovery & Select apply update from adb
7. in cmd type adb sideload DDV_XYZ.zip ( Select package accordingly to your variant. Example for indians DDVA_sprout , for Russian DDV & for global DDV_sprout )
8. Wait for 5 minutes to complete the flashing process on locked bootloader.
9. After flashing completed Select reboot to bootloader
10. Type fastboot devices
11. Type fastboot flashing unlock_critical ( see the phone and select unlock the Bootloader using volume buttons and press power button )
12. Reboot to fastboot again make sure to use volume down and power button at a time for fastboot mode.
13. type fastboot flashing unlock ( see the phone and select unlock the Bootloader using volume buttons and press power button )
Finally Congratulations we successfully completed bootloader unlock.
Now what next? Just reflash stock rom from fastboot accordingly to my stock rom flash tool thread.
Thank you !!
• Download Sideload Packages
• Download adb platform tools
• Stock rom flash tool thread

Very cool. Is this also going to work for Nokia 6.2?

you_ser said:
Very cool. Is this also going to work for Nokia 6.2?
Click to expand...
Click to collapse
yup on the way in few hours

I successfully unlocked and my 7.2 today and faced no problems. The whole process ran flawlessly, thanks for making this possible and keep doing good work.

Amazing ! was waiting for this since forever as couldnt spend money, succesfuly unlocked the bootloader on my nokia 7.2 without any issues thnx a ton to the whole development team. Just follow the instructions

WORKS FINE
ON ANDROID 10
(NOKIA 7.2)
YES, IT DOES WORKS THANK YOU SO MUCH AND KUD
DOS TO THE DEVELOPERS.
I MANAGED TO UNLOCK IT FOR FREE
UNLOCKED MY BOOTLOADER
USING NOKIA 7.2 ON ANDROID 10 WITH INDIAN VARIENT DDVA_sprout.zip update package.
Just follow the steps and it will be just fine
Also I would like to mention that in my case I didn't needed to flash stock rom, it booted normally after few "corrupted file" warnings so skipped the "Stock Rom flash tool threads"... I just let it boot few times 4-7 times max and it booted after that with nokia logo.

Great work! Hope the development grow well for Nokia 7.2 & 6.2!

I only get the message "No Command" after I type `adb reboot recovery`. Is there any other method to get into stock recovery?

zwinca said:
I only get the message "No Command" after I type `adb reboot recovery`. Is there any other method to get into stock recovery?
Click to expand...
Click to collapse
When you see no command. Then press & hold power button and press volume up button then it automatically goes to recovery mode.

Raghu varma said:
When you see no command. Then press & hold power button and press volume up button then it automatically goes to recovery mode.
Click to expand...
Click to collapse
worked like a charm...thank you. nice work

Doesn't work . I am at step 8 and 9, typing
fastboot devices
fastboot flashing unlock_critical, but there is no option called "unlock", only start - restart bootloader - recovery mode - power off - boot to ffbm - qmmi.
whats going on?
edit: stuck at this point:
edit 2" ok, i understand now that the phone should ask for confirmation, but it doesnt.

Wi-Fi is not working with Magisk installed

Ujwal2000 said:
Wi-Fi is not working with Magisk installed
Click to expand...
Click to collapse
So, what was the solution to your problem? Maybe it will help me?
Thanks.

P.G.R. said:
Doesn't work . I am at step 8 and 9, typing
fastboot devices
fastboot flashing unlock_critical, but there is no option called "unlock", only start - restart bootloader - recovery mode - power off - boot to ffbm - qmmi.
whats going on?
edit: stuck at this point:
edit 2" ok, i understand now that the phone should ask for confirmation, but it doesnt.
Click to expand...
Click to collapse
I have the same problem.

I found a solution. It was a driver problem. I installed Google, Inc. - Other hardware - Android Bootloader Interface from Windows Update and now ist works.

N7.2 said:
I found a solution. It was a driver problem. I installed Google, Inc. - Other hardware - Android Bootloader Interface from Windows Update and now ist works.
Click to expand...
Click to collapse
Thanks. Did similar thing on Linux and it worked (fighting with lineage rights now, its a mess).

Hi everyone,
I unlocked my nokia back then when a bug was still in one of the first android versions and there were an official option in my the dev options. (7.2)
Since then my device has been showing an warning alert when android is booting up. Is this still the case with this unlock procedure mentioned here? If yes, would it work for my to lock my device again and reunlock using this tool in this thread?
Regards,

no, the warning message is still there.

abdulrahmanna said:
Great work! Hope the development grow well for Nokia 7.2 & 6.2!
Click to expand...
Click to collapse
@Raghu varma please do it for nokia 6.1 plus

Ujwal2000 said:
Wi-Fi is not working with Magisk installed
Click to expand...
Click to collapse
It's not because of Magisk. On stock ROM, TWRP causes this issue. Instead of flashing Magisk using TWRP, you can flash Magisk patched (stock) boot img for rooting your device.
{Mod edit: Link removed}

Please Help Me. Xiaomi 12x. Bricked Phone after trying to root. Stuck in fastboot bootloop.

Hello.
I've followed instructions as in this thread https://forum.xda-developers.com/t/root-psyche-root-xiaomi-12x-with-magisk.4455293/
only 1 thing I did wrong is downloading 13.02 boot.img file instead of 13.04 boot.img which wasn't available at that time.
After I flashed phone was stuck in Recovery mode bootloop, then for some reason it just got stuck in normal bootloop.
after that I downloaded 13.04 boot.img which was for my version, patched it on another phone in magisk, repeated instructions and now it's stuck in fastboot bootloop.
I also want to mention that I don't have external SD card so I was using boot.img directly from my pc.
Please help me.
There was solution to use Mi Phone Assistant but program doesn't detect my phone.
Edit: I'm green in these kind of termins so want to mention that it doesn't constant rebooting, just everytime I try to boot it goes into fastboot.

If phone is ADB enabled try this
1. Connect Windows desktop computer with phone via USB cable what came with phone
2. In Windows Command prompt run command sequence
Code:
adb devices
adb reboot
to exit phone into NORMAL boot ( i.e. system mode -> ANDROID OS)

xXx yYy said:
If phone is ADB enabled try this
1. Connect Windows desktop computer with phone via USB cable what came with phone
2. In Windows Command prompt run command sequence
Code:
adb devices
adb reboot
to exit phone into NORMAL boot ( i.e. system mode -> ANDROID OS)
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When in fastboot adb devices didn't find any devices
this screenshot is after I entered in recovery mode but you see it yourself...

Looks like USB Debugging isn't got successfully enabled on phone.

xXx yYy said:
Looks like USB Debugging isn't got successfully enabled on phone.
Click to expand...
Click to collapse
Does it mean that phone is forever bricked? Can you throw me some words of hope please.

it is not forever bricked. you just messed up with the boot image. try the troubleshooting steps from the link you ve posted with a different cable. or a different usb. or a different pc. the app should detect the phone at some point.

Fytdyh said:
it is not forever bricked. you just messed up with the boot image. try the troubleshooting steps from the link you ve posted with a different cable. or a different usb. or a different pc. the app should detect the phone at some point.
Click to expand...
Click to collapse
Thank you for advice, I will try.

Fytdyh said:
it is not forever bricked. you just messed up with the boot image. try the troubleshooting steps from the link you ve posted with a different cable. or a different usb. or a different pc. the app should detect the phone at some point.
Click to expand...
Click to collapse
Tried on different PC, didn't work. I doubt it's USB cable because it's original and I unlocked bootloader with it before. I'm desperate...
Edit: I think it's because of software that my phone doesn't get detected, https://prnt.sc/G232WPcRRqC1 mi unlock tool does detect it although only in fastboot mode, not recovery.
edit2: mi pc suite detects my phone in Fastboot mode but writes this... https://prnt.sc/4dB06CtvIfhz

can you enter in recovery mode ? when you enter in recovery mode, what options do you have ?

kiknalex said:
Tried on different PC, didn't work. I doubt it's USB cable because it's original and I unlocked bootloader with it before. I'm desperate...
Edit: I think it's because of software that my phone doesn't get detected, https://prnt.sc/uwS8qnna60rX mi unlock tool does detect it...
Click to expand...
Click to collapse
Hey, just download the Fastboot ROM for your device, extract the boot.img from there and place it in the platform-tools folder.
Then open CMD inside the platform-tools folder and execute the below command to flash the stock boot.img file [assuming you are in the Fastboot Mode]:
Code:
fastboot flash boot boot.img
You may then boot to the OS via the below command
Code:
fastboot reboot

Sidenote: To avoid such scenarios in the near future, please refrain from directly flashing the boot.img. Rather first temporary boot via
Code:
fastboot boot magisk_patched_boot.img
And then use the Direct Install feature of Magisk for permanent root

Fytdyh said:
can you enter in recovery mode ? when you enter in recovery mode, what options do you have ?
Click to expand...
Click to collapse
https://prnt.sc/Oyjs9lxGVFX8 It's same as in this picture, not my phone tho. I didn't try erase data because I think it will disable USB debugging and I chose to wait for answers on forums.

binary**# said:
Sidenote: To avoid such scenarios in the near future, please refrain from directly flashing the boot.img. Rather first temporary boot via
Code:
fastboot boot magisk_patched_boot.img
And then use the Direct Install feature of Magisk for permanent root
Click to expand...
Click to collapse
Hey, thanks for help, I want to clarify 2 things:
1.
Hey, just download the Fastboot ROM for your device, extract the boot.img from there and place it in the platform-tools folder.
Then open CMD inside the platform-tools folder and execute the below command to flash the stock boot.img file [assuming you are in the Fastboot Mode]:
Do I do it with stock boot.img or I should patch it?
2. Isn't that the same as instructions I linked in thread post?

kiknalex said:
Hey, thanks for help, I want to clarify 2 things:
1.
Hey, just download the Fastboot ROM for your device, extract the boot.img from there and place it in the platform-tools folder.
Then open CMD inside the platform-tools folder and execute the below command to flash the stock boot.img file [assuming you are in the Fastboot Mode]:
Do I do it with stock boot.img or I should patch it?
2. Isn't that the same as instructions I linked in thread post?
Click to expand...
Click to collapse
flash the stock image first. after you get a fully fuctional phone attempt the rooting guide. as in, booting the phone as normal, be relieved that you did not hard brick it. then try again, and follow every step of the way.

Fytdyh said:
flash the stock image first. after you get a fully fuctional phone attempt the rooting guide. as in, booting the phone as normal, be relieved that you did not hard brick it. then try again, and follow every step of the way.
Click to expand...
Click to collapse
I just did it and situation is same, it enters bootloops in fastboot... I just remembered one thing and don't know how important it is but maybe makes a difference.
If I recall correctly, when I first flashed patched.img, the installation process wrote sending boot_b but after that it always said sending boot_a
like in this screenshot https://prnt.sc/t931it_cCodT .
Maybe it is root of problems?
I also want to mention a little detail that I rememeber.
When I was checking MIUI updates on site, the release was Stable BETA but only recovery was available, although now fastboot is available too, it's just Stable - without Beta, Perhaps my ROM was Stable Beta and not stable? It's 13.04 GLOBAL.

well, it does have importance. newer devices have 2 partition for booting. while older have only 1.
try this
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot

kiknalex said:
Hey, thanks for help, I want to clarify 2 things:
1.
Hey, just download the Fastboot ROM for your device, extract the boot.img from there and place it in the platform-tools folder.
Then open CMD inside the platform-tools folder and execute the below command to flash the stock boot.img file [assuming you are in the Fastboot Mode]:
Do I do it with stock boot.img or I should patch it?
2. Isn't that the same as instructions I linked in thread post?
Click to expand...
Click to collapse
Oh, I forgot to mention that you should only download the same version of Fastboot ROM that was installed on your device. And then flash the stock boot.img from that ROM to both slots using the commands given by @Fytdyh

Fytdyh said:
well, it does have importance. newer devices have 2 partition for booting. while older have only 1.
try this
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
Click to expand...
Click to collapse
Tried still same... maybe it's something with vbmeta.img?

or if your inactive partition is still non-corrupted [fingers crossed] then you could try booting it via that slot. For that, change the active partition via
Code:
fastboot set_active other
and then
Code:
fastboot reboot

binary**# said:
Oh, I forgot to mention that you should only download the same version of Fastboot ROM that was installed on your device. And then flash the stock boot.img from that ROM to both slots using the commands given by @Fytdyh
Click to expand...
Click to collapse
I downloaded same. :|.
I don't mind using another ROM if it will fix my issues, is it even possible to install from situation like this?