Related
Official A16 ozip was released yesterday:
realme.com/support/software-update
My working flow is as follows:
1. Extract boot.img and vbmeta.img from the converted zip
2. Use Magisk to patch the boot.img , we got magisk_patched.img
3. fastboot flash boot magisk_patched.img and reboot. However, in this method it says
the current image (boot/recovery) have benn destroyed and can not boot
4. I asked others, they said I have to flash vbmeta.img too. So I used ./fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img. This time, when booting, it just turns black (Under normal circantance, it will show a yellow REALME logo, however not appearing in this method)
_____________________________________
What should I do? Does this vbmeta.img in the official zip work? Thanks for your help!
cocoon_zz said:
Official A16 ozip was released yesterday:
realme.com/support/software-update
My working flow is as follows:
1. Extract boot.img and vbmeta.img from the converted zip
2. Use Magisk to patch the boot.img , we got magisk_patched.img
3. fastboot flash boot magisk_patched.img and reboot. However, in this method it says
the current image (boot/recovery) have benn destroyed and can not boot
4. I asked others, they said I have to flash vbmeta.img too. So I used ./fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img. This time, when booting, it just turns black (Under normal circantance, it will show a yellow REALME logo, however not appearing in this method)
_____________________________________
What should I do? Does this vbmeta.img in the official zip work? Thanks for your help!
Click to expand...
Click to collapse
Upload a video
Hi, I have twrp on the rmx1901cn (Chinese version), can I use the converted zip to image my phone back to its original state using twrp? I don't mind getting back to Chinese stock ROM anymore.
Also, I only have access to TWRP and boot loader now.
Please provide some more hints. I'm stuck at the same spot.
LovemyRealme said:
Hi, I have twrp on the rmx1901cn (Chinese version), can I use the converted zip to image my phone back to its original state using twrp? I don't mind getting back to Chinese stock ROM anymore.
Also, I only have access to TWRP and boot loader now.
Click to expand...
Click to collapse
I've got a little further. I converted the ozip to zip. Extracted the boot.img from the converted file. Flashed boot.img to the phone. and flashed vbmeta.img using the same commands as cocoon_zz.
I'm getting the same black screen as cocoon_zz. I haven't use Magisk but the stock rom is okay by me. Can you guys please give some hints on how to get pass the black screen after the realme logo?
Hi!
I've had trouble installing a GSI on my HTC U12+, but AOSP GSI maintainer phhusson helped me, so I'm sharing a quick tutorial.
1. Download and extract Android SDK Platform Tools
2. Download the GSI of your choice (ARM64, AB variant), and move it inside platform tools folder (I've only tested AOSP 10.0)
3. Download and extract the HTC RUU Decryption and Extraction Tool
4. Download the RUU for your device and move it inside HTC-RUU_Decrypt_Tool_XXX folder
5. Follow instructions from the RUU Decryption Tool thread to decrypt and extract the RUU, with all default settings
6. Move the vbmeta.img file you've just extracted (it's inside HTC-RUU_Decrypt_Tool_XXX/OUT_XXX/firmware) to the platform tools folder
6. Unlock bootloader
7. Restore stock firmware with microSD method or factory reset if you already have stock firmware
8. Reboot in bootloader
9. From a computer, launch a terminal, change directory to the platform tools folder, then execute "fastboot erase system"
10. Then execute "fastboot flash system <your_gsi.img>"
11. Execute "fastboot reboot bootloader"
12. Execute "fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification" (WARNING : According to 5m4r7ph0n36uru, you can't flash vbmeta via fastboot if your device isn't S-OFF, you have to use TWRP, but I don't know how, so ask someone who knows! I will update my tutorial once I see instructions.)
13. Execute "fastboot reboot"
It should boot the GSI!
On first boot it may ask for a previous decryption password and complain about a corrupt data partition. You can erase it (you will lose what was inside).
If you have bugs or issues with the GSI, there may be workarounds here: https://github.com/phhusson/treble_experimentations/wiki/HTC-U12-Plus
Enjoy your GSI on your HTC U12+!
Romano2K said:
Hi!
I've had trouble installing a GSI on my HTC U12+, but AOSP GSI maintainer phhusson helped me, so I'm sharing a quick tutorial.
1. Download and extract Android SDK Platform Tools
2. Download the GSI of your choice (ARM64, AB variant), and move it inside platform tools folder (I've only tested AOSP 10.0)
3. Download and extract the HTC RUU Decryption and Extraction Tool
4. Download the RUU for your device and move it inside HTC-RUU_Decrypt_Tool_XXX folder
5. Follow instructions from the RUU Decryption Tool thread to decrypt and extract the RUU, with all default settings
6. Move the vbmeta.img file you've just extracted (it's inside HTC-RUU_Decrypt_Tool_XXX/OUT_XXX/firmware) to the platform tools folder
6. Unlock bootloader
7. Restore stock firmware with microSD method or factory reset if you already have stock firmware
8. Reboot in bootloader
9. From a computer, launch a terminal, change directory to the platform tools folder, then execute "fastboot erase system"
10. Then execute "fastboot flash system <your_gsi.img>"
11. Execute "fastboot reboot bootloader"
12. Execute "fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification"
13. Execute "fastboot reboot"
It should boot the GSI!
On first boot it may ask for a previous decryption password and complain about a corrupt data partition. You can erase it (you will lose what was inside).
If you have bugs or issues with the GSI, there may be workarounds here: https://github.com/phhusson/treble_experimentations/wiki/HTC-U12-Plus
Enjoy your GSI on your HTC U12+!
Click to expand...
Click to collapse
Hello, which GSI did you tried from the list? If you tried more then one, which is the one that runs better?
Thank you
Hi!
I have tried AOSP 10.0 v206 system-quack-arm64-ab-gapps.img. v208 is out now.
I still have to try others.
Let us know if you find one working better than others!
i have problem with this line fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification
My fastboot say C:\adb\fastboot.exe: unknown option -- disable-verity How to fix this?
Edit: My htc is dead, power button dont work, does not respond to the charger and PC.
mientus25 said:
i have problem with this line fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification
My fastboot say C:\adb\fastboot.exe: unknown option -- disable-verity How to fix this?
Edit: My htc is dead, power button dont work, does not respond to the charger and PC.
Click to expand...
Click to collapse
Hi mientus25! I'm sorry if you bricked your smartphone trying to flash it. I think the --disable-verity option not working was a matter of platform tools (adb) version.
My htc have actually hard brick. I will try to send it to the service(warranty). Will tell you what comes of it.
fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification doesn't working
it says: not allowed in production device
bootloader:unlocked
xreeman said:
fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification doesn't working
it says: not allowed in production device
bootloader:unlocked
Click to expand...
Click to collapse
If on 2.55.401.1 try flashing this vbmeta. It already has verity and verification disabled, pulled from an S-OFF device allowing the above flashing commands. It flashed fine on my U12+ and I've been able to boot PE 10 GSI afterwards without any problems.
@Romano2K feel free to add it to the OP.
5m4r7ph0n36uru said:
If on 2.55.401.1 try flashing this vbmeta. It already has verity and verification disabled, pulled from an S-OFF device allowing the above flashing commands. It flashed fine on my U12+ and I've been able to boot PE 10 GSI afterwards without any problems.
@Romano2K feel free to add it to the OP.
Click to expand...
Click to collapse
Hello, can I may ask you if I can send you a PM? I have an HTC u12+ and I would like to install and Android 10 GSI and I would like a step by step help to do it. Can you please also tell me which bugs are you facing with it? Thank you very much
GaetanoS.89 said:
Hello, can I may ask you if I can send you a PM? I have an HTC u12+ and I would like to install and Android 10 GSI and I would like a step by step help to do it. Can you please also tell me which bugs are you facing with it? Thank you very much
Click to expand...
Click to collapse
No help by PM. I cannot do this for professional reasons. And also for personal reasons not to give individual support.
5m4r7ph0n36uru said:
No help by PM. I cannot do this for professional reasons. And also for personal reasons not to give individual support.
Click to expand...
Click to collapse
All right, would you please write a message over with all the steps here? Thank you
GaetanoS.89 said:
All right, would you please write a message over with all the steps here? Thank you
Click to expand...
Click to collapse
Starting from a Stock ROM, Bootloader Unlocked, I took the following steps to flash and boot an Android 10 GSI to my HTC U12+:
Go to Settings > System and perform a factory reset
Reboot in the Bootloader by
Code:
adb reboot bootloader
Delete the system and data partition by
Code:
fastboot erase data
and
Code:
fastboot erase system
Flash the nonverity vbmeta image via
Code:
fastboot flash vbmeta nameofvbmeta.img
(the vbmeta image must be in the fastboot folder on your computer)
Flash the GSI via
Code:
fastboot flasch system nameofgsi.img
(the GSI must be in the fastboot folder on your computer)
Reboots the HTC U12+ into Download Mode and perform another Factory Reset
Reboot and enjoy
If /data still can't be read, do another Factory Reset from settings menu
https://www.xda-developers.com/goog...al&utm_source=twitter.com&utm_campaign=buffer
Wiil this work with the U12+???
It may work for GSIs with a fixed verity status. Thus it doesn't work for some Android 10 GSIs without flashing a noverity vbmeta as. Thus I decided long ago, to never recommend such tools, and not to help people who used one, as those using such tools most of the time didn't even care learn the basics of adb and fastboot. I can't remember anyone, who used a tool, who's ever been fully capable to identify potential problems and errors, let alone how to solve them. And the latter is the baseline to start modding a device.
Sent from my Pixel 4 XL using XDA Labs
5m4r7ph0n36uru said:
Starting from a Stock ROM, Bootloader Unlocked, I took the following steps to flash and boot an Android 10 GSI to my HTC U12+:
Go to Settings > System and perform a factory reset
Reboot in the Bootloader by
Delete the system and data partition by and
Flash the nonverity vbmeta image via (the vbmeta image must be in the fastboot folder on your computer)
Flash the GSI via (the GSI must be in the fastboot folder on your computer)
Reboots the HTC U12+ into Download Mode and perform another Factory Reset
Reboot and enjoy
If /data still can't be read, do another Factory Reset from settings menu
Click to expand...
Click to collapse
Hello,
I have unlocked the bootloader yesterday, and I was having a look to your steps, and I noticed you are not using TWRP. Are you doing everything by CMD right?
Romano2K said:
Hi!
I've had trouble installing a GSI on my HTC U12+, but AOSP GSI maintainer phhusson helped me, so I'm sharing a quick tutorial.
1. Download and extract Android SDK Platform Tools
2. Download the GSI of your choice (ARM64, AB variant), and move it inside platform tools folder (I've only tested AOSP 10.0)
3. Download and extract the HTC RUU Decryption and Extraction Tool
4. Download the RUU for your device and move it inside HTC-RUU_Decrypt_Tool_XXX folder
5. Follow instructions from the RUU Decryption Tool thread to decrypt and extract the RUU, with all default settings
6. Move the vbmeta.img file you've just extracted (it's inside HTC-RUU_Decrypt_Tool_XXX/OUT_XXX/firmware) to the platform tools folder
6. Unlock bootloader
7. Restore stock firmware with microSD method or factory reset if you already have stock firmware
8. Reboot in bootloader
9. From a computer, launch a terminal, change directory to the platform tools folder, then execute "fastboot erase system"
10. Then execute "fastboot flash system <your_gsi.img>"
11. Execute "fastboot reboot bootloader"
12. Execute "fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification"
13. Execute "fastboot reboot"
It should boot the GSI!
On first boot it may ask for a previous decryption password and complain about a corrupt data partition. You can erase it (you will lose what was inside).
If you have bugs or issues with the GSI, there may be workarounds here: https://github.com/phhusson/treble_experimentations/wiki/HTC-U12-Plus
Enjoy your GSI on your HTC U12+!
Click to expand...
Click to collapse
Hello I am trying to follow all the steps on the guode, but when I have to flash the vbmeta file from Bootloader Mode I am getting this:
C:\Users\User\Desktop\ADB2>fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (4 KB) OKAY [ 0.004s]
Writing 'vbmeta' FAILED (remote: 'Not allowed on PRODUCTION device')
fastboot: error: Command failed
If I try to install the vbmeta from Download Mode I am getting this error
GaetanoS.89 said:
Hello,
I have unlocked the bootloader yesterday, and I was having a look to your steps, and I noticed you are not using TWRP. Are you doing everything by CMD right?
Click to expand...
Click to collapse
Yes I'm doing everything from CMD indeed. Always do so, as long as it is possible.
@Romano2K vbmeta can't be flashed via fastboot on S-On/production devices. It has to be flashed as update.zip from TWRP. It should be mentioned anywhere.
5m4r7ph0n36uru said:
Yes I'm doing everything from CMD indeed. Always do so, as long as it is possible.
@Romano2K vbmeta can't be flashed via fastboot on S-On/production devices. It has to be flashed as update.zip from TWRP. It should be mentioned anywhere.
Click to expand...
Click to collapse
So how do I have to proceed??
9. From a computer, launch a terminal, change directory to the platform tools folder, then execute "fastboot erase system"
10. Then execute "fastboot flash system <your_gsi.img>"
11. Execute "fastboot reboot bootloader"
And after?
GaetanoS.89 said:
So how do I have to proceed??
9. From a computer, launch a terminal, change directory to the platform tools folder, then execute "fastboot erase system"
10. Then execute "fastboot flash system <your_gsi.img>"
11. Execute "fastboot reboot bootloader"
And after?
Click to expand...
Click to collapse
Which software version are you running!?
Sent from my Pixel 4 XL using XDA Labs
5m4r7ph0n36uru said:
Which software version are you running!?
Click to expand...
Click to collapse
I was running Android 9 stock. After a few trials I have been able to install and boot the Pixel Experience and the permessiver and everything seems to work without flashing the vbmeta file
Hello lads,
I have been having issues with my OnePlus Nord N100.
On my fault, I wanted to root with magisk using fastboot. Unfortunately, I had flashed boot a magisk.img which was not compatible with OnePlus Nord N100.
The phone is currently stuck in Fastboot Mode. I have tried several times to flash boot it back to its original boot.img, unfortunately it does not work.
Every time I try to go to Recovery Mode, it leads me right back to the Fastboot main menu. I can turn off the phone and reboot it with no issues.
I believe I have soft bricked it, and I need help recovering it back to it's original state, or better yet root it in a riskless way.
Here is a list of commands and techniques I have tried so far:
- Fastboot -w
- Fastboot erase cache
- Fastboot erase boot
- Fastboot erase boot_a
- Fastboot erase boot_b
- Fastboot boot boot.img (Ends up with a failure)
- Fastboot flash boot boot.img (Command is successful, but no changes for boot)
- Tried all combinations keys to go to Recovery Mode (Power button + Volume Down Button + Volume Up Button)
Thank you for helping me out if you can.
Windwell said:
Hello lads,
I have been having issues with my OnePlus Nord N100.
On my fault, I wanted to root with magisk using fastboot. Unfortunately, I had flashed boot a magisk.img which was not compatible with OnePlus Nord N100.
The phone is currently stuck in Fastboot Mode. I have tried several times to flash boot it back to its original boot.img, unfortunately it does not work.
Every time I try to go to Recovery Mode, it leads me right back to the Fastboot main menu. I can turn off the phone and reboot it with no issues.
I believe I have soft bricked it, and I need help recovering it back to it's original state, or better yet root it in a riskless way.
Here is a list of commands and techniques I have tried so far:
- Fastboot -w
- Fastboot erase cache
- Fastboot erase boot
- Fastboot erase boot_a
- Fastboot erase boot_b
- Fastboot boot boot.img (Ends up with a failure)
- Fastboot flash boot boot.img (Command is successful, but no changes for boot)
- Tried all combinations keys to go to Recovery Mode (Power button + Volume Down Button + Volume Up Button)
Thank you for helping me out if you can.
Click to expand...
Click to collapse
Tried changing between active slot ?
Also flashed the unpatched boot.img to both slots a/b?
fastboot --set-active=a
or:
fastboot --set-active=b
AJHutchinson said:
Tried changing between active slot ?
Also flashed the unpatched boot.img to both slots a/b?
fastboot --set-active=a
or:
fastboot --set-active=b
Click to expand...
Click to collapse
Hey mate,
Thanks for responding. Sorry for the late reply.
From what you had suggested, I did "fastboot --set-active=a" , "fastboot flash boot boot.img", and "fastboot reboot" (with the stock unpatched boot.img) the commands were successful once again, but there were no effective changes.
Afterwards, I did "fastboot --setactive-b", "fastboot flash boot boot.img", and "fastboot reboot" the commands were successful once more, and this time, I was finally able to go into recovery mode. On the other hand, in recovery mode I wiped the cache and erased everything, but unfortuantely I still could not boot into Android, even though I tried to flash boot the image once more.
Thank you for these commands, as I was at least able to recover recovery mode.
Any other suggestions maybe?
Hello,
Use this tool and it will fix it, I had the same problem. Just download the software and flash it in Qualcomm EDL mode.
MSMDownload image needed
Hello guys, I managed to flash the wrong image to OnePlus NORD N100 BE2013, I overlooked for the first time what I'm doing and messed it up Now it's in Qualcomm EDL mode and I need and image to flash it to bring it back do life, anyone I can...
forum.xda-developers.com
I alsp posted boot.img which is compatible you can flash it. Link is in the comments.
Thanks
Boot.img from nord n100 in this thread, I exctracted and rooted it myself.
I WHANT RECOVERY Boot.img FOR ROOT MY ONEPLUS NORD N100
I unlock bootloader and i whant to root with magisk my phone, i need boot.img for rocovery..I try anather boot.img from One plus nord, etc, i sucessfull flash this recovery's with command in windows but is no go in recovery, stay in bootloop..Can...
forum.xda-developers.com
Hello,
I used the tool MSMDownload but unfortunately I was unable at all to boot into Qualcomm Edl mode, even though I have installed correctly all the drivers for Windows Qualcomm, and OnePlus USB drivers, and used the correct method (Volume Button UP and Down at the same time whilst connecting the phone via USB). I tried flash booting with the boot.img you gave me, but still no changes. I am still stuck in Fastboot.
If you had encountered the same issue back then, can you tell me the excat procedure you did please?
Thank you so much.
I was in the exact same situation after flashing boot.img from one plus nord by mistake.
It got so bad it was totally bricked and just got into EDL mode by holding down the up and down volume buttons and holding power on. Even the screen didn't work.
Once that started, MSMDownload tool from the N100 thread worked fine, you downloaded the proper package right?
Which model does it say on the back? This was BE2013.
I think solution for you is a fastboot image, I extracted the payload.bin to .img files and brought it back to life with it and rooted it with magisk.
The boot.img I uploaded here was from Oxygen OS 10.5.5.
If you have fastboot you should 100% be able to boot into EDL mode, just hold down the up and down volume buttons for long time and then the power button
Thanks
AJHutchinson said:
Tried changing between active slot ?
Also flashed the unpatched boot.img to both slots a/b?
fastboot --set-active=a
or:
fastboot --set-active=b
Click to expand...
Click to collapse
oh
thts ok man
بلوک سبک
I will try to make a fastboot image for OnePlus NORD N100 BE2013 with 10.5.5 and upload it to mega, I'll send you the link. If you are in fastboot mode you will be able to flash it I believe, let me have a look.
Fast boot image is ready for Oxygen 10.5.5 Nord N100 EUROPE, I am uploading it to MEGA.
motovnet said:
I was in the exact same situation after flashing boot.img from one plus nord by mistake.
It got so bad it was totally bricked and just got into EDL mode by holding down the up and down volume buttons and holding power on. Even the screen didn't work.
Once that started, MSMDownload tool from the N100 thread worked fine, you downloaded the proper package right?
Which model does it say on the back? This was BE2013.
I think solution for you is a fastboot image, I extracted the payload.bin to .img files and brought it back to life with it and rooted it with magisk.
The boot.img I uploaded here was from Oxygen OS 10.5.5.
If you have fastboot you should 100% be able to boot into EDL mode, just hold down the up and down volume buttons for long time and then the power button
Thanks
Click to expand...
Click to collapse
For some reason Qualcomm Mode Edl does not launch whatsoever.
motovnet said:
Fast boot image is ready for Oxygen 10.5.5 Nord N100 EUROPE, I am uploading it to MEGA.
Click to expand...
Click to collapse
Thank you that's very kind of you. I think the only way to fix it by flash boot.img, but I have doubts because it does not work.
The only commands I am doing are "fastboot devices", "fastboot flash boot boot.img"
With the fastboot image you will be able to flash everything, it contains not only boot.img but system and etc. I managed to boot mine and bring it back to life by reflashing everyhing.
So the only thing I need to do is "fastboot flash boot ''.img" right?
Where can I get all the nesscary files?
And how did you manage to root it?
The fastboot image flashes all partitions, not just boot with stock Oxygen OS 10.5.5
What you need to do is run flash-all.bat from the archive and it will flash the entire os not just boot.img.
If you can't get to EDL mode, fastboot flash is the only solution. What model does it say in the back? This one was EUROPE BE2013.
Is your EU or Global device?
Archive is uploading still.
Thanks
The model is the correct one. BE2013, although it does not say EU or anything.
In the archive, I would just need to run flash-all.bat which flash boots all the nesscary images correct?
Thank you once agian.
2.55 GB file on MEGA
mega.nz
This is a fastboot image for OnePlus NORD N100 EU BE2013 device.
Extract it to a new folder, it contains fastboot in it.
Right click flash-all.bat and run as admin.
You can open the flash-all.bat file with notepad to check yourself there is nothing strange in it. I used a bat file from the forum that was fastboot image for OnePlus NORD and changed it to use the .img files for OnePlus NORD N100.
Contains Oxygen 10.5.5, once you bring it back to life (IF YOU HAVE THIS MODEL), you can use magisk to patch the boot.img and flash it via fastboot.
This is how I rooted it and it worked properly.
Please use it with caution and ensure your model matches! I can not guarantee it will work on other devices.
If you can't go to EDL mode, this is your way to go, but I don't know if flashing GLOBAL version will work.
Thanks
Windwell said:
The model is the correct one. BE2013, although it does not say EU or anything.
In the archive, I would just need to run flash-all.bat which flash boots all the nesscary images correct?
Thank you once agian.
Click to expand...
Click to collapse
I would guess BE2013 is the EU one, as this worked on mine.
motovnet said:
I would guess BE2013 is the EU one, as this worked on mine.
Click to expand...
Click to collapse
Okay thank you for helping me. I will try this later and keep you in touch.
Windwell said:
Okay thank you for helping me. I will try this later and keep you in touch.
Click to expand...
Click to collapse
Thanks, let me know if it works for you. If you're unable to flash it via fastboot, only EDL will help.
I've been trying to root my Note 9T. The bootloader has been unlocked, and I've followed a guide from here: https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/
I'm now stuck in a bootloop.
Anyone been successful?
I additionally tried using a different version of TWRP, which wiped the "misc" partition. Can anyone provide an image dump of the misc partition so I can flash it back on? I can't find a copy of misc in the stock firmware file.
UPDATE 1:
I put the full stock image back on and am back to having a working unrooted phone, so I don't need the misc image. Would really like to get this thing rooted though.
I've installed the Magisk APK, patched the boot image, and flashed it. But this also results in a boot loop. If I flash the stock image back it works again. Any ideas what's going on here?
UPDATE 2:
I got it working! The key was to flash the stock vbmeta.img with fastboot functions to disable it.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Hiya. I've tried that and managed to get to the twrp page. However, when I go to install magisk via twrp, it just reboots into a bootloop. Any ideas?
Update: This seems to have worked.
[SOLVED] Phone gets stuck in bootloop if I try to install Magisk ZIP!
From the forum I followed these step to install magisk: - Patched my boot.img of my current rom using Magisk Manager and flashed via fastboot - After rebooting from fastboot it got stuck in recovery so had to wipe all data and it booted finally...
forum.xda-developers.com
Did you manage to get Magisk working after the reinstall of stock firmware, or you've just resolved the bootloop?
dsclee1 said:
I've been trying to root my Note 9T. The bootloader has been unlocked, and I've followed a guide from here: https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/
I'm now stuck in a bootloop.
Anyone been successful?
I additionally tried using a different version of TWRP, which wiped the "misc" partition. Can anyone provide an image dump of the misc partition so I can flash it back on? I can't find a copy of misc in the stock firmware file.
UPDATE 1:
I put the full stock image back on and am back to having a working unrooted phone, so I don't need the misc image. Would really like to get this thing rooted though.
I've installed the Magisk APK, patched the boot image, and flashed it. But this also results in a boot loop. If I flash the stock image back it works again. Any ideas what's going on here?
UPDATE 2:
I got it working! The key was to flash the stock vbmeta.img with fastboot functions to disable it.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
I'm interesting in at least rooting and if possible install TWRP .
Can you post i complete procedure to root the note 9 T ?
Thanks
I can have a go. But I'm not 100% sure what exact steps I took that got it working, as I flashed and re-flashed several times. Give this a try and let me know if it works or not?
WARNING: EXPECT TO LOSE ALL THE DATA ON YOUR PHONE!
Step 1
Obviously you need to unlock the bootloader first: https://en.miui.com/unlock/
If you haven't done this already, after your application it's likely you might have to wait 7 days before Xiaomi actually let you unlock.
Unlocking wipes your data.
Step 2
Start the phone normally. Copy the latest magisk apk (https://github.com/topjohnwu/Magisk/releases) over to the phone and install it.
Step 3
Find the correct original ROM for your device (https://xiaomifirmwareupdater.com/miui/cannong/). You'll need the full image. From the ROM extract the boot.img and vbmeta.img. Copy the boot.img over to your phone.
Step 4
In magisk choose the option to install and select "Select and Patch a File" (should be the only option anyway). Select the boot.img you copied over. This will produce a new file called something like "magisk_patched-22100_XXXXX.img". Copy this file off your phone and onto your computer.
Step 5
Boot your phone to fastboot mode (you should already know how to do this, as you would have had to have done it to unlock your phone in the first place - Hold down Volume Down and the Power button at the same time).
Step 6
Run the following commands (obviously replace the boot image with the correct magisk image, and use the vbmeta.img you took from the ROM):
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot magisk_patched-22100_XXXXX.img
Hopefully this will work. But I can't be 100% sure, as the disabling of "verity" could mean that your encrypted user data now can't be read (if you've only just unlocked the bootloader then you're not going to have any data anyway, so not too much of an issue). If this is the case it's likely you'll now need to factory reset the phone. Hold down Volume Up and Power on start to reach the stock recovery menu, and there's a selection for factory reset. You can also install TWRP at this point, and could then use it's factory reset function instead. I downloaded this version of TWRP: https://www.mediafire.com/file/ou8553psro9yyt2/3.4.2_redmi_note_9_5G.rar/file, which came from the other rooting guide (https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/ - which didn't work). Just flash that version of TWRP to the recovery partition (fastboot flash recovery recovery.img), and ignore all the steps given in the guide it came from.
Let me know how you get on.
sorry for the answer delay.
Adding my 2 cents about unlocking the bootlader .
In order to do it .
FIRST - do not try it from a virtual PC . It does not work (at least it did not work for me)
SECOND , before to run the xiaomi batch_unlock bootlader , don't forget to update google usb drivers
I hard some hard time to just connect the unlocker to my phone . Now i have to wait 167 hours to complete the process .
dsclee1 said:
I've been trying to root my Note 9T. The bootloader has been unlocked, and I've followed a guide from here: https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/
I'm now stuck in a bootloop.
Anyone been successful?
I additionally tried using a different version of TWRP, which wiped the "misc" partition. Can anyone provide an image dump of the misc partition so I can flash it back on? I can't find a copy of misc in the stock firmware file.
UPDATE 1:
I put the full stock image back on and am back to having a working unrooted phone, so I don't need the misc image. Would really like to get this thing rooted though.
I've installed the Magisk APK, patched the boot image, and flashed it. But this also results in a boot loop. If I flash the stock image back it works again. Any ideas what's going on here?
UPDATE 2:
I got it working! The key was to flash the stock vbmeta.img with fastboot functions to disable it.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
ive been trying for the last 4 hours to flash twrp on my redmi note 9T 5g global..can you please explain to me how you got it to work. i flashed the recovery.img and vbmeta.img file that i got from the unofficialtwrp.com download, when i flash boot recovery.img, it just reboots my phone into normal...and i missing something? My device is on Miui 12.0.8.0 andriod 10. should i be on the new update 12.5 andriod 11 for it to work. Please help.
dsclee1 said:
I can have a go. But I'm not 100% sure what exact steps I took that got it working, as I flashed and re-flashed several times. Give this a try and let me know if it works or not?
WARNING: EXPECT TO LOSE ALL THE DATA ON YOUR PHONE!
Step 1
Obviously you need to unlock the bootloader first: https://en.miui.com/unlock/
If you haven't done this already, after your application it's likely you might have to wait 7 days before Xiaomi actually let you unlock.
Unlocking wipes your data.
Step 2
Start the phone normally. Copy the latest magisk apk (https://github.com/topjohnwu/Magisk/releases) over to the phone and install it.
Step 3
Find the correct original ROM for your device (https://xiaomifirmwareupdater.com/miui/cannong/). You'll need the full image. From the ROM extract the boot.img and vbmeta.img. Copy the boot.img over to your phone.
Step 4
In magisk choose the option to install and select "Select and Patch a File" (should be the only option anyway). Select the boot.img you copied over. This will produce a new file called something like "magisk_patched-22100_XXXXX.img". Copy this file off your phone and onto your computer.
Step 5
Boot your phone to fastboot mode (you should already know how to do this, as you would have had to have done it to unlock your phone in the first place - Hold down Volume Down and the Power button at the same time).
Step 6
Run the following commands (obviously replace the boot image with the correct magisk image, and use the vbmeta.img you took from the ROM):
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot magisk_patched-22100_XXXXX.img
Hopefully this will work. But I can't be 100% sure, as the disabling of "verity" could mean that your encrypted user data now can't be read (if you've only just unlocked the bootloader then you're not going to have any data anyway, so not too much of an issue). If this is the case it's likely you'll now need to factory reset the phone. Hold down Volume Up and Power on start to reach the stock recovery menu, and there's a selection for factory reset. You can also install TWRP at this point, and could then use it's factory reset function instead. I downloaded this version of TWRP: https://www.mediafire.com/file/ou8553psro9yyt2/3.4.2_redmi_note_9_5G.rar/file, which came from the other rooting guide (https://unofficialtwrp.com/twrp-3-4-2-root-redmi-note-9-5g-cannon/ - which didn't work). Just flash that version of TWRP to the recovery partition (fastboot flash recovery recovery.img), and ignore all the steps given in the guide it came from.
Let me know how you get on.
Click to expand...
Click to collapse
should I be on the latest version of Miui...12.5 android 11? for me to be able to install twrp. i downgraded back to Miui 12.0.8.0 android 10 as i didnt like my data folder been blocked in android folder. My device is global cannong redmi 9T 5g with diminsity 800u soc, can you please help if you can. thanks in advance
Android 10 is fine. You need to fastboot flash recovery recovery.img
To boot into it you need to turn the phone off, then hold vol up and power until you feel a buzz, then let go.
I have the same Problem as HighEndGamer:
if I enter 'fastboot flash recovery recovery.img', it sayes that everything worked OK in just a few seconds. But nothing realy happend!
If I enter 'fastboot boot recovery.img', phone boot just as normal.
If I enter 'fastboot oem device-info', it sayes "FAILED (remote: unknown command)'.
If I enter 'fastboot oem lock', it works and I have to start from the beginning..
I have MIUI Global 12.0.2.0{QJEEUMX)
chmick said:
sorry for the answer delay.
Adding my 2 cents about unlocking the bootlader .
In order to do it .
FIRST - do not try it from a virtual PC . It does not work (at least it did not work for me)
SECOND , before to run the xiaomi batch_unlock bootlader , don't forget to update google usb drivers
I hard some hard time to just connect the unlocker to my phone . Now i have to wait 167 hours to complete the process .
Click to expand...
Click to collapse
I confirm it does not work from a VM (and the need for latest drivers). There is something funky going on with the USB communication when running from a VM: the first call of the fastboot executable from the windows VM generally works fine, but any other call hang. So the batch_unlock tool cannot work (since it does call fastboot several times).
Hello
I've just ordered my Pixel 6 Pro, coming from the OnePlus 8 Pro.
I love tinkering with Root/Kernels/Roms.
So my question is, if there is always a way to get back to stock in case of emergency?
The OnePlus phones are considered as "unbreakable", because You can ALWAYS unbrick it via MSM unbrick tool.
Would be nice to know when I start unlocking the bootloader of my Pixel
Thanks!
Sorry that Pixel doesn't have that unbrick tool ...
The only one is a batch commend file - Flash-All extracted from factory full ROM ...
It is possible to hardbrick a Pixel device without hopes of getting it running again, for example if you nuke your recovery.
Most softbricks can be solved by either doing what Kris Chen suggested, or by using
Android Flash Tool
flash.android.com
or
Google Pixel - Update and Software Repair
After flashing a module that bootloops you can try this:
If it almost boots up but flashes, in a cmd window type:
adb wait-for-device shell magisk --remove-modules
It may grab that and remove all modules. If it doesn't, you can try this:
1. fastboot flash boot boot.img, reboot.
2. long press power button, then long press "power off", click ok to enter safemode.
3. Before your phone boots all the way up, boot to fastboot.
4. fastboot flash boot magisk_patched.img, reboot.
5. In cmd window type: adb wait-for-device shell magisk --remove-modules
6. Your phone will boot up with root and all modules removed.
There's a shortcut to safemode that removes everything but I'm not sure what it is.
Edit: boot.img is taken from the applicable firmware you are on downloaded from Google. Unzip the main zip, go into the folder and unzip the image zip that is inside.
Thank you all for your detailed information, very appreciated
Could someone check if the following is the right procedure to revert to stock kernel?
fastboot flash boot <magisk-patched-image>.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash dtbo dtbo.img
fastboot reboot fastboot (wait a bit, this takes a bit of time until you see the fastbootd screen)
fastboot flash vendor_dlkm vendor_dlkm.img
fastboot reboot
And do I have to do this procedure everytime before switching from a custom kernel to another kernel?
Thanks!
Lycidias said:
Thank you all for your detailed information, very appreciated
Could someone check if the following is the right procedure to revert to stock kernel?
fastboot flash boot <magisk-patched-image>.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash dtbo dtbo.img
fastboot reboot fastboot (wait a bit, this takes a bit of time until you see the fastbootd screen)
fastboot flash vendor_dlkm vendor_dlkm.img
fastboot reboot
And do I have to do this procedure everytime before switching from a custom kernel to another kernel?
Thanks!
Click to expand...
Click to collapse
Yes, correct, and yes, safest to do so each time switching kernels.