If you try to flash the file misc.bin your device can be in bootloop forever, please follow this guide to fix it.
It works with:
- Xiaomi Redmi Note 9
- Xiaomi Redmi 10X 4G
Method 1:
Once your device is on the black screen, plug it on USB (try USB3.0 first).
And then check if it is detected in adb recovery mode:
Code:
adb devices
If you can see your device in adb recovery mode, you have to erase misc partition:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p2
After it is done, you can reboot your device to system or fastboot again.
Keep atention, if you execute this command wrong, you will ERASE any other partition and it can brick your device forever and cause more damages.
Method 2:
Once your device is on the black screen, plug it on USB (try USB3.0 first).
And then check if it is detected in adb recovery mode:
Code:
adb devices
And then reboot to bootloader:
Code:
adb reboot bootloader
And then check if it is detected in fastboot mode:
Code:
fastboot devices
If you can see your device in fastboot mode, you have to erase misc partition:
Code:
fastboot erase misc
Keep attention, if you try to format misc partition, you will get this error: Formatting is not supported for file system with type 'raw data'.
After it is done, you can reboot your device to system or fastboot again.
Keep atention, if you execute this command wrong, you will ERASE any other partition and it can brick your device forever and cause more damages.
Good luck !
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4225163/
VD171 said:
If you boot your device and it keeps in a black screen because outdated TWRP, please follow this guide.
It works with:
- Xiaomi Redmi 10X 4G
- Xiaomi Redmi Note 9
Once your device is on the black screen, plug it on USB (try USB3.0 first).
And then check if it is detected:
Code:
adb devices
If you can see your device in adb recovery mode, you have to format misc partition:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p2
After it is done, you can reboot your device to system or fastboot again.
Keep atention, if you execute this command wrong, you will FORMAT any other partition and it can brick your device forever and cause more damages.
Good luck !
Click to expand...
Click to collapse
OR they can just use
adb reboot bootloader
boot to fastboot and flash the stock image of the partition which is corrupted.
Communos said:
OR they can just use
adb reboot bootloader
boot to fastboot and flash the stock image of the partition which is corrupted.
Click to expand...
Click to collapse
Please, read the guide. This guide is for people who flashed misc.bin partition from the outdated TWRP.
This misc.bin partition from the outdated TWRP, will bootloop the device forever in recovery mode.
There is NO misc partition on stock image. So, you have to erase misc partition for stops with bootloop in recovery.
Thanks! If I knew this a few weeks ago it would have been helpful, But I fixed it with MiTool V2
VD171 said:
Please, read the guide. This guide is for people who flashed misc.bin partition from the outdated TWRP.
This misc.bin partition from the outdated TWRP, will bootloop the device forever in recovery mode.
There is NO misc partition on stock image. So, you have to erase or format misc partition for stops with bootloop in recovery.
Click to expand...
Click to collapse
Well, I've been in this situation twice or thrice, first I fixed by flashing full stock rom, rest of the times flashing stock recovery and stock boot fixed it for me.
Communos said:
Well, I've been in this situation twice or thrice, first I fixed by flashing full stock rom, rest of the times flashing stock recovery and stock boot fixed it for me.
Click to expand...
Click to collapse
As I've said, if you've flashed misc.bin from the outdated TWRP, just flashing stock recovery or stock boot will not fix the problem.
For fixing it, you have to erase misc partition. If it doesn't help you, please, go away and let it help who wants help.
Nice job and see you later.
VD171 said:
If you try to boot your device and it keeps in a black screen because outdated TWRP, please follow this guide.
It works with:
- Xiaomi Redmi Note 9
- Xiaomi Redmi 10X 4G
Method 1:
Once your device is on the black screen, plug it on USB (try USB3.0 first).
And then check if it is detected in adb recovery mode:
Code:
adb devices
If you can see your device in adb recovery mode, you have to format misc partition:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p2
After it is done, you can reboot your device to system or fastboot again.
Keep atention, if you execute this command wrong, you will FORMAT any other partition and it can brick your device forever and cause more damages.
Method 2:
Once your device is on the black screen, plug it on USB (try USB3.0 first).
And then check if it is detected in adb recovery mode:
Code:
adb devices
And then reboot to bootloader:
Code:
adb reboot bootloader
And then check if it is detected in fastboot mode:
Code:
fastboot devices
If you can see your device in fastboot mode, you have to format misc partition:
Code:
fastboot format misc
After it is done, you can reboot your device to system or fastboot again.
Keep atention, if you execute this command wrong, you will FORMAT any other partition and it can brick your device forever and cause more damages.
Good luck !
Click to expand...
Click to collapse
thanks sooo much
imranbinlatif said:
thanks sooo much
Click to expand...
Click to collapse
Good job, my friend.
You are welcome
VD171 said:
If you try to boot your device and it keeps in a black screen because outdated TWRP, please follow this guide.
It works with:
- Xiaomi Redmi Note 9
- Xiaomi Redmi 10X 4G
Method 1:
Once your device is on the black screen, plug it on USB (try USB3.0 first).
And then check if it is detected in adb recovery mode:
Code:
adb devices
If you can see your device in adb recovery mode, you have to erase misc partition:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p2
After it is done, you can reboot your device to system or fastboot again.
Keep atention, if you execute this command wrong, you will ERASE any other partition and it can brick your device forever and cause more damages.
Method 2:
Once your device is on the black screen, plug it on USB (try USB3.0 first).
And then check if it is detected in adb recovery mode:
Code:
adb devices
And then reboot to bootloader:
Code:
adb reboot bootloader
And then check if it is detected in fastboot mode:
Code:
fastboot devices
If you can see your device in fastboot mode, you have to erase misc partition:
Code:
fastboot erase misc
Keep attention, if you try to format misc partition, you will get this error: Formatting is not supported for file system with type 'raw data'.
After it is done, you can reboot your device to system or fastboot again.
Keep atention, if you execute this command wrong, you will ERASE any other partition and it can brick your device forever and cause more damages.
Good luck !
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4225163/
Click to expand...
Click to collapse
Hey there, i erased the Misc partition, it's still bootlooping,
I tried to un-brick my device from the Xiaomi Mod Tool,
Yes i did try flashing a outdated TWRP image,
It got hard bricked, and i tried to fix it,
through some good luck, i managed to get into "fastboot"
And, nothing, it just got soft bricked,
I guess that's proggress?
My device: merlinnfc (Redmi Note 9/10X 4G)
TheMagnificent_Y said:
Hey there, i erased the Misc partition, it's still bootlooping,
I tried to un-brick my device from the Xiaomi Mod Tool,
Yes i did try flashing a outdated TWRP image,
It got hard bricked, and i tried to fix it,
through some good luck, i managed to get into "fastboot"
And, nothing, it just got soft bricked,
I guess that's proggress?
My device: merlinnfc (Redmi Note 9/10X 4G)
Click to expand...
Click to collapse
If you have access to fastboot and erasing misc did not work, simply flash the entire stock rom you were on through MiFlash.
TheMagnificent_Y said:
Hey there, i erased the Misc partition, it's still bootlooping,
I tried to un-brick my device from the Xiaomi Mod Tool,
Yes i did try flashing a outdated TWRP image,
It got hard bricked, and i tried to fix it,
through some good luck, i managed to get into "fastboot"
And, nothing, it just got soft bricked,
I guess that's proggress?
My device: merlinnfc (Redmi Note 9/10X 4G)
Click to expand...
Click to collapse
Erasing misc only works if you are frozen in a black screen after flashing misc partition.
Recovery partition can't break boot.
Probably your problem is vbmeta.
Vbmeta can break the boot.
Did you flash it too?
I flashed the entire ROM,
So yes,
Every single partition, except misc since it's gone now,
When i say "Every Single Partition", I mean every single one,
this includes,
Scp1/2
super
..etc.
TheMagnificent_Y said:
I flashed the entire ROM,
So yes,
Every single partition, except misc since it's gone now,
When i say "Every Single Partition", I mean every single one,
this includes,
Scp1/2
super
..etc.
Click to expand...
Click to collapse
Misc partition is not present in original stock rom.
It contains a variable data/parameter for boot.
Did you solve the bootloop after flash full rom?
No,
Here are the full details:
1. I tried flashing the recovery partition, Nothing.
2. I used an unnofficial TWRP ROM that hard bricked my device, this includes the following partitions:
Misc Opt Vbmeta Recovery
3. I managed to get into ADB recovery, i got into fastboot, then flashed the stock rom.
4. Boot loop
TheMagnificent_Y said:
No,
Here are the full details:
1. I tried flashing the recovery partition, Nothing.
2. I used an unnofficial TWRP ROM that hard bricked my device, this includes the following partitions:
Misc Opt Vbmeta Recovery
3. I managed to get into ADB recovery, i got into fastboot, then flashed the stock rom.
4. Boot loop
Click to expand...
Click to collapse
You need to avoid the misc partition.
If you've flashed it, you REALLY need to erase it.
Or, it will make your device to enter in recovery forever.
Vbmeta needs to be flashed with disababled verification.
Here you can find safe and secure vbmeta with disabled verification: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218909/
Or, it will detect modification on partitions and will reboot the device forever.
I think Opt doesn't change anything.
I'm not sure, but I think it only matter for devices without vbmeta partition. (I'M NOT SURE.)
Because it modifies the system, and obviously you will get in a bootloop.
If you want to modify the system, you need to debloat your system before.
Try to flash the whole system again.
Or just try to flash the whole rom again.
I've done that twice, and i deleted misc afterwards,
What about...:
fastboot flashall -w ?
Shouldn't that help flashing the system?
Also what does Vbmeta verify?
Thanks.
PS: I tried flashing the un-official and official versions, both leave a brick, and nothing really changes, i haven't tried your "Patched" version tho.
TheMagnificent_Y said:
I've done that twice, and i deleted misc afterwards,
What about...:
fastboot flashall -w ?
Shouldn't that help flashing the system?
Also what does Vbmeta verify?
Thanks.
Click to expand...
Click to collapse
I'm not sure.
Just flashing the system should solve it.
Or just flashing the whole rom using the flashing scripts inside the original stock rom.
Vbmeta checks if boot, recovery and dtbo partitions keeps untouched and unmodified.
I flashed the whole rom using the Xiaomi Mod Tool which is coded in java script,
i'll try to flash your "Patched" vbmeta image and see if that helps, if not, i'll re-flash the stock rom.
TheMagnificent_Y said:
I flashed the whole rom using the Xiaomi Mod Tool which is coded in java script,
i'll try to flash your "Patched" vbmeta image and see if that helps, if not, i'll re-flash the stock rom.
Click to expand...
Click to collapse
Flashing the whole stock rom, certainly solves everything.
And then, if you want TWRP again, try this first: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4227751/
Good luck
Related
Hi
I was trying to install Lineage OS on my device, but I failed, now the phone does not have TWRP anymore, and when I power up, it goes into fast boot only.
I have done quite a lot of work to save my phone, and the last thing that I did was download the stock fastboot rom and run flash_all.bat from it.
(I can not get the Miflash tool working on my PC because when I startup the program, it asks me to download 5 drivers, but it failed to download and throw me an error)
luckyvictor said:
Hi
I was trying to install Lineage OS on my device, but I failed, now the phone does not have TWRP anymore, and when I power up, it goes into fast boot only.
I have done quite a lot of work to save my phone, and the last thing that I did was download the stock fastboot rom and run flash_all.bat from it.
(I can not get the Miflash tool working on my PC because when I startup the program, it asks me to download 5 drivers, but it failed to download and throw me an error)
Click to expand...
Click to collapse
First of all - if your phone boots to fastboot, there seems to be a problem with your bootloader or kernel.
To fix that, you need to reflash aboot.img and boot.img via fastboot.
Boot.img depends on the version, you want to install. Copy both files into your fastboot folder and
Code:
fastboot flash boot_a boot.img
Code:
fastboot flash boot_b boot.img
Code:
fastboot flash aboot_a aboot.img
Code:
fastboot flash aboot_b aboot.img
Now your phone shouldn´t stuck @ fastboot anymore.
Ok, to save your data, you could try to boot twrp:
Code:
fastboot boot twrp.img
If you´re lucky, it can decrypt your data - then you can backup data and internal storage...
If it´s not able to decrypt, you need to install twrp.
To install a fastboot rom without miflash look here
I suggest you to install caf-kernel via twrp. Sometimes your phone boots up with it - magic
Voodoojonny said:
First of all - if your phone boots to fastboot, there seems to be a problem with your bootloader or kernel.
To fix that, you need to reflash aboot.img and boot.img via fastboot.
Boot.img depends on the version, you want to install. Copy both files into your fastboot folder and
Code:
fastboot flash boot_a boot.img
Code:
fastboot flash boot_b boot.img
Code:
fastboot flash aboot_a aboot.img
Code:
fastboot flash aboot_b aboot.img
Now your phone shouldn´t stuck @ fastboot anymore.
Ok, to save your data, you could try to boot twrp:
Code:
fastboot boot twrp.img
If you´re lucky, it can decrypt your data - then you can backup data and internal storage...
If it´s not able to decrypt, you need to install twrp.
To install a fastboot rom without miflash look here
I suggest you to install caf-kernel via twrp. Sometimes your phone boots up with it - magic
Click to expand...
Click to collapse
Thanks, will give it a try.
Just for my knowledge, what are these boot_a and boot_b please? they relate to the two sim slot in this device?
luckyvictor said:
Thanks, will give it a try.
Just for my knowledge, what are these boot_a and boot_b please? they relate to the two sim slot in this device?
Click to expand...
Click to collapse
Boot.img from fastboot rom... To be flashed in partition boot_a and boot_b. Our device is a AB-device. That means all partitions are doubled (except of data). If your system breaks, you can switch to the other slot by "fastboot set_active a" or b if you are on a.... Btw perhaps that fixes your phone too! Boot twrp and you can see which slot is active (under reboot)
Hello everyone,
I need help to start on flashing g7 play etc. In the old days I flashed phones like galaxy s3, s4, s5 and Note 4, but I'm not an expert in all of this.
Then I changed to iPhone 6s and now I want to come back to Android.
My goal:
de-googled moto g7 play
Android 9/10 -> would prefer 10
if possible -> root
My Device:
moto g7 play - XT1952-1
(bootloader unlocked)
---
Build number:
PPYs29.105-134-7
---
If have read most of the Threads for the g7 play, but at the moment I'm a little scared to brick it.
I have some questions:
1. I copied together for myself a Instruction (at the end of post). Could you tell me if this is OK like this, or do I have to do additional things before start?
2. In my copied instruction, at the point of flashing the GSI (Instruction ROM: -> Step 1)
What does "Dirty flashing your g7 play" mean? Do I have something additional to do, before following the instruction, or is dirty flashing the following instruction of the post?
3. Modded phh -> I have no information about this, could you explain, or give me link?
4. Overlay -> I have no information about this, could you explain, or give me link?
Thanks for your help
---
INSTRUCTION: (it is a quick&dirty instruction)
ROM:
lineage-17.1-20200309-UNOFFICIAL-treble_a64_bvN.img.xz
DTBO:
dtbo.img
(https://drive.google.com/file/d/1pV6-LbNoMG0J8vcyAWN0QWYGx67vxBgT/view?usp=sharing)
---
---
Instruction ROM:
step 1
Dirty flashing your g7 play -> what does that mean, what to do???
step 2
extract the gsi
step 3
put phone in fastboot mode and enter the commands
$ fastboot -w
$ fastboot flash dtbo dtbo.img
$ fastboot flash system [this is where you put your android 10 img]
$ fastboot boot twrp.img
(https://forum.xda-developers.com/g7-play/development/gsi-images-g7-play-t3980807
#1)
------------------------
TWRP:
twrp.img
---
Instruction TWRP:
step 1
Fastboot boot twrp.img
step 2
Copy twrp to your external sdcard, or use adb push twrp.img /tmp/twrp.img
step 3
Go to Advanced > install recovery ramdisk then navigate to tmp or your external sdcard and select the twrp.img you copied
step 4
Use wipe > format > type "yes" to continue then use reboot > recovery from twrp's menus
step 5
Once twrp starts up again, wipe data & system, make sure system is mounted, then flash a GSI. Flash the universal disabler afterwards.
If you get a failed to unmount error, manually mount all partitions and reflash whatever it errored on
step 6
Optional: Flash my modded phh for root. (Install the apk after.) Never use Magisk! It will fail to root, cause a bootloop, or break twrp
FIX navbar on a GSI:
$ adb root
$ adb shell
$ setprop persist.sys.phh.mainkeys 0
$ reboot
(https://forum.xda-developers.com/g7...ery-dirty-ported-twrp-g7-play-t3947205/page41
#403)
------------------------
Modded phh: -> LOS16 & 17
modded-phh-superuser.zip
phh-su.apk
(https://forum.xda-developers.com/showpost.php?p=81503713&postcount=240)
------------------------
Overlay: -> what does that mean???
treble-overlay-moto-g7play.apk.zip
(https://forum.xda-developers.com/g7...ery-dirty-ported-twrp-g7-play-t3947205/page41
#404)
------------------------
@ggg777
First make sure you install the stock OS to both slots, including the bootloader. I forgot to flash bootloader_b, and got stuck in EDL last week. You don't want that to happen and it's not easy to get out of. If you do this first, you will not have to worry about getting bricked.
Use my instructions found here for twrp. Inside the instructions you'll also find a link to my modded phh. Flashing a GSI can be done with twrp or fastboot. You also don't need the dtbo.img anymore since it's embedded inside of twrp. The trickiest part really, is just getting twrp installed. If you're using twrp to install a GSI, wipe system, data, dalvik, then flash the image to system. (You'll get a location prompt.) After installing a GSI, copy the overlay to /vendor/overlay, and set permissions on it to 0644, then reboot. Flash modded phh for root if you're using LOS 16 or 17. I think it's already included in Phh's AOSP builds.
There's also a trick to dual boot your OS. I keep one slot with stock installed, that's debloated and rooted with magisk. The other slot I use for flashing GSIs. Twrp can't restore encrypted data for stock, but you can format /data using "yes" then switch slots and use "reboot recovery" to boot up stock with magisk. To swap back to the GSI, fastboot boot twrp, format data, switch slots from the reboot menu, reboot to recovery. If twrp starts, you changed slots successfully. Then just restore data for lineage and bootup.
Oh by the way, "dirty flashing" is just flashing an OS update without wiping data first. I don't recommend it though. Sometimes bugs from older builds will get carried over. You don't need to do that to install LOS 17 or Android 10. It might've been true at one time, but it isn't now. You can just do your wipes and flash the latest build.
Thanks for your Help
How can I check if both partitions are with stock and bootloader?
Is there a trick to copy a working partition to the oter?
I would flash like it is written in this: [Guide][Channel][Stock]Moto g7 play Factory Firmware Images
(https://forum.xda-developers.com/g7-play/how-to/channel-moto-g7-factory-firmware-images-t3996303)
Would it flash both partitions (if only one is written)?
Thanks for your help
ggg777 said:
Thanks for your Help
How can I check if both partitions are with stock and bootloader?
Is there a trick to copy a working partition to the oter?
I would flash like it is written in this: [Guide][Channel][Stock]Moto g7 play Factory Firmware Images
(https://forum.xda-developers.com/g7-play/how-to/channel-moto-g7-factory-firmware-images-t3996303)
Would it flash both partitions (if only one is written)?
Thanks for your help
Click to expand...
Click to collapse
Typically if you've taken an OTA then you already have both slots filled. You can check with...
Code:
fastboot getvar all
Near the bottom you'll see some slot information. If slot b is active, then you should already be covered. I still think it's best to manually flash both slots though. If you've never updated then slot b is definitely empty. This is what I do...
Code:
fastboot flash boot_a boot.img
fastboot sending image boot_a...
Successful!
Image not signed blah blah something that isn't important...
Hit the up arrow on the keyboard then just change _a to _b
Code:
fastboot flash boot_b boot.img
Same with system, only I run through the list of sparse chunks in one shot, then hit the other slot. Use the big series of sparse chunks (0-7) on both slots. Skip the two that would normally go to system_b.
Code:
fastboot flash system_a system.image_sparsechunk.0
fastboot flash system_a system.image_sparsechunk.1
fastboot flash system_a system.image_sparsechunk.2
etc...
Then on the other side the same way.
Code:
fastboot flash system_b system.image_sparsechunk.0
fastboot flash system_b system.image_sparsechunk.1
fastboot flash system_b system.image_sparsechunk.2
etc...
When you get to oem, do not use oem_other.img, flash oem.img to both slots instead. Basically just make sure you do that with everything. E.g. dsp_b modem_b. I'm sure you get the idea by now.
Hello Spaceminer,
I have little knowledge in working with terminal in debian (I used man fastboot and tried some things like changing slots but this did not work). And then I tried some of these things and was to scared to brick it so I flashed it with RDS Lite (I hate to use Windows ) last night.
With RDS Lite flashing was no problem and I got a OTA, so slots a and b are not empty. After that I used your TWRP-Guide which you linked and it worked
BUT
Then I was trying to flash a GSI (arm32binder64ab):
lineage-17.1-20200309-UNOFFICIAL-treble_a64_bvN.img
Havoc-OS-v3.0-20191226-A64AB-Unofficial.img
system-quack-arm32_binder64-ab-vanilla.img
it completed but failed to boot:
Start Up Failed:
---
AP Fastboot Flash Mode (Secure)
No bootable A/B slot
Failed to boot Linux, falling back to fastboot
Fastboot Reason: Fall-through from normal boot mode
No bootalbe A/B slot
Failed to boot Linux, falling back to fastboot
Boot up failed
---
TWRP is always available with:
fastboot -> recovery
Could you please help me to handle this?
I would really love to use this phone de-googled with root permission cause I'm sad of spying on me by Gafa and the moto g7 play (I hate the size of the bigger ones) looks like the perfect model for me
PS: I have some screenshot's if you need
ggg777 said:
Hello Spaceminer,
I have little knowledge in working with terminal in debian (I used man fastboot and tried some things like changing slots but this did not work). And then I tried some of these things and was to scared to brick it so I flashed it with RDS Lite (I hate to use Windows ) last night.
With RDS Lite flashing was no problem and I got a OTA, so slots a and b are not empty. After that I used your TWRP-Guide which you linked and it worked
BUT
Then I was trying to flash a GSI (arm32binder64ab):
lineage-17.1-20200309-UNOFFICIAL-treble_a64_bvN.img
Havoc-OS-v3.0-20191226-A64AB-Unofficial.img
system-quack-arm32_binder64-ab-vanilla.img
it completed but failed to boot:
Start Up Failed:
---
AP Fastboot Flash Mode (Secure)
No bootable A/B slot
Failed to boot Linux, falling back to fastboot
Fastboot Reason: Fall-through from normal boot mode
No bootalbe A/B slot
Failed to boot Linux, falling back to fastboot
Boot up failed
---
TWRP is always available with:
fastboot -> recovery
Could you please help me to handle this?
I would really love to use this phone de-googled with root permission cause I'm sad of spying on me by Gafa and the moto g7 play (I hate the size of the bigger ones) looks like the perfect model for me
PS: I have some screenshot's if you need
Click to expand...
Click to collapse
Hey im in a smiliar situation with the G7 Play (XT1952-2)
I have the same goal of running this phone without google..
I would like to install LineageOS with microG (signature spoofing)
Have you been successful with this? Do you have a A-Z list of instructions for a fellow newbie?
Our old twrp have been great compared to nothing but it isn't exactly fully working and freezes a lot on splash screen.
Thanks to @Stricted and @deadman96385 we now have a more functional twrp.
Support for A/B slots.
ADB working.
No need to flash full firmware. Just flash the vbmeta_patch.img and boot twrp.
!!BOOTLOADER MUST BE UNLOCKED!!
YOUR DATA WILL BE WIPED!!
Code:
fastboot flash vbmeta vbmeta_patch.img
fastboot boot twrp-3.3.1-test3.img
Now that we booted to TWRP it's time to format data.
Go to wipe -> format data -> type yes.
"Permanent" install of TWRP (optional):
Copy "twrp-3.3.1-test3.img" to your device.
Boot "twrp-3.3.1-test3.img" from fastboot and go to advanced settings.
Use the option to install recovery ramdisk. In the "file manager" you pick the "twrp-3.3.1-test3.img"
This will extract the twrp ramdisk and install it to your boot.img.
When it's done, tap the "fix recovery bootloop" in advanced settings so that it won't reboot to recovery instead of system..
Since this replaces the ramdisk in boot.img you'll have to reflash magisk afterwards if you want root.
This must be done every time you update your boot.img.
-------------------------------------------------------------------------------------------------------------------------------------------------------
# ROOT:
-----------
# First time:
# Method 1: Root, forced encryption disabled. Full access to data from twrp:
Flash Magisk and Disable_Dm-Verity_ForceEncrypt.zip.
# Method 2: Root only. Device still encrypted and won't be able to decrypt / mount data in twrp.
Magisk modules through Magisk manager still works:
Flash only Magisk.
----------------------------------------------------------------------------------------------------
# Fastboot flash update without loosing root or data:
----------------------------------------------------------------------------------------
# Already rooted with encryption disabled:
Extract the firmware zip to your adb/fastboot folder.
You already have the patched vbmeta flashed so just remove the stock vbmeta.img from the folder after extraction to avoid flashing it by mistake.
Flash full firmware without wipe. (Use cmds from below. Save as .bat to make it more simple.)
Boot twrp and then install it, fix recovery bootloop.
Reboot recovery, flash Magisk and Disable_Dm-Verity_ForceEncrypt.zip.
Boot system.
Code:
echo off
echo - UPDATE AND PRESERV ROOT -
fastboot flash pit diskmap.pit
fastboot flash fwbl1 fwbl1.img
fastboot flash ldfw_a ldfw.img
fastboot flash ldfw_b ldfw.img
fastboot flash keystorage_a keystorage.img
fastboot flash keystorage_b keystorage.img
fastboot flash bootloader_a bootloader.img
fastboot flash bootloader_b bootloader.img
fastboot flash modem_a modem.bin
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot flash logo_a logo.bin
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.10
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_a system.img_sparsechunk.9
fastboot flash system_b system_other.img_sparsechunk.0
fastboot flash system_b system_other.img_sparsechunk.1
fastboot flash system_b system_other.img_sparsechunk.2
fastboot flash vendor_a vendor.img
fastboot reboot bootloader
pause 10
fastboot boot twrp-3.3.1-test3.img
echo TWRP is booting..
echo - install recovery ramdisk, fix bootloop, flash magisk & dm-verity zip.
echo - alternatively flash only magisk and Disable_Dm-Verity_ForceEncrypt.zip if you want to keep stock recovery.
pause
# Already rooted with device still encrypted:
Flash firmware update, except vbmeta.
Boot twrp and flash Magisk with adb sideload.
(alternative method: boot twrp and flash magisk patched boot.img)
Download TWRP: https://images.stricted.net/test/troika/twrp-3.3.1-test3.img
Download Magisk: https://github.com/topjohnwu/Magisk/releases
Download vbmeta_patch.img & Disable_Dm-Verity_ForceEncrypt.zip attached below.
PLEASE, DON't QUOTE THE WHOLE OP.
Great guide @tys0n and thank you to @Stricted and @deadman96385 for his work !
tys0n said:
Code:
fastboot flash vbmeta vbmeta_patch.img
fastboot boot twrp-3.3.1-test3.img
Click to expand...
Click to collapse
My Vision is already unlocked and rooted by the old TWRP method. Should I just do this step so I can update to the new TWRP, and then I can follow "encryption disabled" steps to update to a new firmware?
I suppose I can't enable encryption anymore without resetting data.
daekdroom said:
My Vision is already unlocked and rooted by the old TWRP method. Should I just do this step so I can update to the new TWRP, and then I can follow "encryption disabled" steps to update to a new firmware?
I suppose I can't enable encryption anymore without resetting data.
Click to expand...
Click to collapse
You're right. You can't switch between encrypted / non encrypted without a reset.
This update method have been working for me with the old twrp as well, but this new build is much better and more stable that I see no reason not to switch to the new one.
Actually, I think it may be better to first fastboot flash the new firmware (except vbmeta) so that you have a "clean" boot.img to start with if you're planning to use the install recovery ramdisk. At least if you have the old one installed already.
That's how I switched and I've had no problems.
Worked to my, Thnx
Good afternoon,
I'm trying to "patch" the TWRP as you indicate at the beginning of the first post.
When you say:
"For permanent install, use the" flash recovery ramdisk "option in twrp advanced settings"
What file do I have to flash?
Regards
gonzo1963 said:
Good afternoon,
I'm trying to "patch" the TWRP as you indicate at the beginning of the first post.
When you say:
"For permanent install, use the" flash recovery ramdisk "option in twrp advanced settings"
What file do I have to flash?
Regards
Click to expand...
Click to collapse
Sorry, I could have been more clear about this step in the description.
Copy "twrp-3.3.1-test3.img" to your device.
Boot "twrp-3.3.1-test3.img" from fastboot, go to advanced settings.
There's an option to install recovery ramdisk. In the "file manager" you pick the "twrp-3.3.1-test3.img"
This will extract the twrp ramdisk and install it to your boot.img.
When it's done, tap the "fix recovery bootloop" in advanced settings.
Since this replaces the ramdisk in boot.img you'll have to reflash magisk afterwards if you want root.
tys0n said:
Sorry, I could have been more clear about this step in the description.
Copy "twrp-3.3.1-test3.img" to your device.
Boot "twrp-3.3.1-test3.img" from fastboot, go to advanced settings.
There's an option to install recovery ramdisk. In the "file manager" you pick the "twrp-3.3.1-test3.img"
This will extract the twrp ramdisk and install it to your boot.img.
When it's done, tap the "fix recovery bootloop" in advanced settings.
Since this replaces the ramdisk in boot.img you'll have to reflash magisk afterwards if you want root.
Click to expand...
Click to collapse
Good evening,
One last question:
Currently I have permanently installed the TWRP.
Is it also necessary to do these last steps that you have added?
Regards
Enviado desde mi unknown mediante Tapatalk
gonzo1963 said:
Good evening,
One last question:
Currently I have permanently installed the TWRP.
Is it also necessary to do these last steps that you have added?
Regards
Enviado desde mi unknown mediante Tapatalk
Click to expand...
Click to collapse
Good afternoon,
Any answer?
Regards
Enviado desde mi unknown mediante Tapatalk
Bootloop
Dude, my phone was encrypted and unrooted. I flashed vbmeta then booted into twrp. Then I flashed twrp using the ramdisk method, then I clicked to patch the recovery loop, then I flashed Magisk then I flashed the Disable DM Verity. Now I'm stuck in a recovery loop. The phone turns on, then android one screen, then reboots then goes to twrp...
What did I do wrong / miss?
"Then I flashed twrp using the ramdisk method, then I clicked to patch the recovery loop."
Agter this restart the phone in recovery mode and then continue as explained.
Sorry in bad english
First of all, @tys0n thank you very much for your work. I got this phone for work, but since an unrooted Android device is almost useless to me, this is very much appreciated. Just a few annotations from my side, maybe they help someone.
1. Permanent TWRP install didn't work for me. TWRP was installed sucessfully but just like the dude above me, it would not boot to system, even after appying the bootloop fix. I had to reflash to fix this, so better be careful here!
2. I didnt want to lose encryption, so i chose method 2 for rooting. This works fine, but still I had to wipe data in the first place. Otherwise it would again not boot to system, but at least this time it told me that wiping would possibly fix this. However, after wiping encryption IS active. Maybe I did something wrong here but I don't know... Chosing method 1 seems to be the more straightforward option here.
3. Despite these issues, flashing updates seems to work just fine as described described in the OP, preserving data and root. I have only tried this once, from QSA30.62-24-6 to QSA30.62-33, which is currently the most recent patchlevel for RETEU devices. I even got the "successfully updated" notification afterwards, as if it was an OTA update
Preceptor said:
Dude, my phone was encrypted and unrooted. I flashed vbmeta then booted into twrp. Then I flashed twrp using the ramdisk method, then I clicked to patch the recovery loop, then I flashed Magisk then I flashed the Disable DM Verity. Now I'm stuck in a recovery loop. The phone turns on, then android one screen, then reboots then goes to twrp...
What did I do wrong / miss?
Click to expand...
Click to collapse
same here !
sennator said:
First of all, @tys0n thank you very much for your work. I got this phone for work, but since an unrooted Android device is almost useless to me, this is very much appreciated. Just a few annotations from my side, maybe they help someone.
1. Permanent TWRP install didn't work for me. TWRP was installed sucessfully but just like the dude above me, it would not boot to system, even after appying the bootloop fix. I had to reflash to fix this, so better be careful here!
2. I didnt want to lose encryption, so i chose method 2 for rooting. This works fine, but still I had to wipe data in the first place. Otherwise it would again not boot to system, but at least this time it told me that wiping would possibly fix this. However, after wiping encryption IS active. Maybe I did something wrong here but I don't know... Chosing method 1 seems to be the more straightforward option here.
3. Despite these issues, flashing updates seems to work just fine as described described in the OP, preserving data and root. I have only tried this once, from QSA30.62-24-6 to QSA30.62-33, which is currently the most recent patchlevel for RETEU devices. I even got the "successfully updated" notification afterwards, as if it was an OTA update
Click to expand...
Click to collapse
Hi. Yes, you're right. After flashing the patched vbmeta we need to format data. I've made it more clear in OP now.
Thanks for pointing it out.
kArLiN_dRaKE_MX said:
same here !
Click to expand...
Click to collapse
Format data in twrp
It doesn't work for me (XT1970-1).
I did the process according to information method 2.
the system boots normally.
however magisk is not 'GREEN' like two pieces of information.
How is it going without ROOT, how do I put ROOT?
have another process after this information?
Thank you.
It worked.
I performed the process again.
and everything went well.
Thanks to everyone involved. :good:
gambiarraweb1 said:
It doesn't work for me (XT1970-1).
I did the process according to information method 2.
the system boots normally.
however magisk is not 'GREEN' like two pieces of information.
How is it going without ROOT, how do I put ROOT?
have another process after this information?
Thank you.
Click to expand...
Click to collapse
Just a quick question, when I have TWRP and root I can't pass the SafetyNet check, right?
Hello all. When I click on Internal storage, there are folders with names like "a16sgyx462" and so on, so I am not able to install TWRP permanently. Can somebody help me with this?
simije97 said:
Hello all. When I click on Internal storage, there are folders with names like "a16sgyx462" and so on, so I am not able to install TWRP permanently. Can somebody help me with this?
Click to expand...
Click to collapse
You probably have Data encrypted. You need to execute Format Data in TWRP.
Has anyone used the official TWRP version? I've been thinking of transitioning from the older, unofficial, TWRP to that, but I haven't found any comment about it at all.
Preparation:
Notes are important, please pay attention
ONLY use stock USB-A to USB-C cable
I have tried the stock cable from Axon 7, fail fail and more fail, don't make this mistake
DON'T store flash files on USB storage.
fastboot will timeout if your flash files are stored at a slow storage device such as a USB drive, or slow computer with eMMC drive
Download and extract the patched MSM download tool and related flash files (credit)
Download and extract TWRP 3.4.0-2 Test by mauronofrio (credit)
Download and extract 10.0.13-GLOBAL-OnePlus7TOxygen_14.O.19_OTA_019_all_2009281709_1026-FASTBOOT.zip (credit)
Optional: Unlock bootloader at this official OnePlus page with those steps
automated process you have to wait 1 whole week for
if you take this route, you will have an easier time get into EDL
Optional for Driver and boot into EDL: Download and extract the TOOL ALL IN ONE (credit) (untested) (can skip this step if you have driver and completed preparation step 7)
Flash Operations:
Run the MSM executable with Administrator Privilege
Boot into bootloader on 7T (if you already have adb connection, adb reboot bootloader would work as well)
Restart device: Vol Up + Power
Boot into recovery: when system reboot from step 4, immediately press and hold Vol Down + Power until recovery screen
Boot into fastboot: English -> Advanced -> fastboot
Boot into EDL on 7T
If you have OnePlus unlock token from Preparation step 7
Connect USB cable to both PC and 7T
on MSMDownloadTool, click Enum to display your device
fastboot flash cust-unlock unlock_token.bin
fastboot oem unlock
fastboot boot twrp.img
when TWRP boot: adb reboot edl
on MSMDownloadTool it will now show connected
If you don't want to wait for token (untested)
Use TOOL ALL IN ONE
Or, hold down the buttons then click start in MSM. If you release the volume buttons early it will kick you out of EDL--well at least for me. you can release the buttons once MSM starts (credit)
When MsmDownloadTool display connected, hit Start until 7T display CORRUPT message (normal behavior) and reboot into fastboot by ITSELF. If your 7T doesn't get into fastboot screen automatically, something is wrong with previous step, redo EDL flashing and do NOT proceed.
Start Power-Shell with Administrator Privilege and go to the extracted path of 10.0.13-global-oneplus7toxygen_14.o.19_ota_019_all_2009281709_1026-fastboot.zip (DO NOT USE DOS, it will fail you miserably)
Unlock bootloader: .\fastboot flashing unlock_critical (suggested, because it works, so I didn't test the oem unlock method)
To avoid potential conflict with installed fastboot binary (possibly lower version), you can either
edit the flash-all.bat, and change fastboot to .\fastboot, such that only the local fastboot binary will be invoked instead of pathed binary
OR run those identical commands with copy and paste
Code:
.\fastboot -w
.\fastboot flash boot boot.img
.\fastboot flash dtbo dtbo.img
.\fastboot flash modem modem.img
.\fastboot flash reserve reserve.img
.\fastboot flash recovery recovery.img
.\fastboot --disable-verity flash vbmeta vbmeta.img
.\fastboot --disable-verity flash vbmeta_system vbmeta_system.img
.\fastboot reboot fastboot
.\fastboot flash abl abl.img
.\fastboot flash aop aop.img
.\fastboot flash bluetooth bluetooth.img
.\fastboot flash cmnlib cmnlib.img
.\fastboot flash cmnlib64 cmnlib64.img
.\fastboot flash devcfg devcfg.img
.\fastboot flash dsp dsp.img
.\fastboot flash hyp hyp.img
.\fastboot flash imagefv imagefv.img
.\fastboot flash keymaster keymaster.img
.\fastboot flash LOGO LOGO.img
.\fastboot flash multiimgoem multiimgoem.img
.\fastboot flash odm odm.img
.\fastboot flash oem_stanvbk oem_stanvbk.img
.\fastboot flash opproduct opproduct.img
.\fastboot flash qupfw qupfw.img
.\fastboot flash storsec storsec.img
.\fastboot flash tz tz.img
.\fastboot flash uefisecapp uefisecapp.img
.\fastboot flash xbl xbl.img
.\fastboot flash xbl_config xbl_config.img
.\fastboot flash system system.img
.\fastboot flash vendor vendor.img
.\fastboot flash product product.img
.\fastboot reboot
Few notes
User data is wiped, again, lol
reserve partition flashing can produce error msg: FAILED (remote: '(reserve_a) No such partition'), it is OK but others should not Fail
Device will reboot once during the flashing process
After reboot, device will NOT go into fastboot screen but instead go into stock recovery screen, however fastboot will pick up and resume flashing the rest, ONLY IF YOU ARE UNDER POWER-SHELL, so DO NOT flash under DOS
if anything else fails besides the reserve partition, repeat step 7
Device will boot into system, you may use the OS updater to upgrade to the lastest firmware then relock bootloader or proceed with root with Magisk
Hope this will save you some precious time. Major kudos for previous contributions from post 1 and post 2.
All steps are recorded from memory, please let me know if any mistakes are in need of correction.
Tested working on Dec 5, 2020
I have followed this method (and literally anything else I can find) to a T and the farthest I get is when flashing the ROM, I get "Flashing is not allowed for critical partitions" - which I can only find people saying that means the bootloader needs to be unlocked, but it is?! It's definitely, fully unlocked. No matter what I try I can't get around that error during the flashing process and it stays stuck on the T-Mobile ROM.
I had the same issue with the critical partition error when I was under DOS and during the reboot process, 7T will only boot into the normal fastboot screen. In here, I always gets that error over and over. I stopped getting it when 7T boot into the recovery screen under power-shell.
Few things to make sure:
Stock cable
Power-shell in admin priv
Use local fastboot binary
If things still not looking up, I would try a different PC.
Good luck.
Yup, those are all correct and I have tried another PC. Now I'm scared I may have bricked it, because other than booting it into FastBoot it just loops on the "Your device is corrupted" screen. Any thoughts? It did this after I re-locked the bootloader to try unlocking Critical again.
Is your device is corrupt screen the one that gets displayed after the MSM EDL flashing?
If so, does your device auto boot into fastboot afterwards?
My thinking is after MSM tool, your device is corrupted, then you unlock critical flashing. Afterwards, the partitions being flashed in by the fastboot should prevent the corrupt msg being displayed. If you are all getting corrupt msg after the fastboot reboot, then something is off with the first part of your fastboot flashing.
It's that same screen, yes, but the phone is just stuck in a boot loop. It says "Your device is corrupt. It can't be trusted and will not boot." and goes black and says it again, over and over. It will not automatically boot to Fastboot, but if I mess with the volume/power keys, I can get it to the fastboot screen. But no matter what else I do it goes back to an endless loop with the corrupt message.
I think some error could have been carried over from the MSMDownloadTool flashing process. My 7T always auto boot into fastboot screen after the corrupt msg display without interaction on my end.
Try your EDL flashing part again, and at the same time, re-download the preparation step 4 file over again and try use that instead afterwards if you are still stuck on the boot loop, just to prevent possible discrepancies might be caused by corrupted file (unlikely, but it doesn't hurt right?)
Gotcha, thanks. Got it into EDL mode and am running MSM right now.
Okay, EDL/MSM was successful, then I tried flashing the ROM per the instructions again but got the same error of being unable to flash to Critical. It no longer does the "device is corrupt" error boot loop, but the phone ONLY boots to Fastboot now, no matter what I do.
Best of luck. Hope the pain stops for you soon, hah.
Can you post your power-shell display message for the last flash-all.bat invocation?
Also, are you using .\fastboot flashing unlock_critical in admin priv power-shell to unlock the bootloader after MSM flashing?
Yes, that's what I was using. Unlocking it wasn't an issue, and when I try any type of unlock command it says it's already unlocked, which I believe to be true. But it still refuses to write to critical.
I can post my powershell message when I get back home. But basically it ran fine at first, it did fail at the "reserve" portion which I read to be normal, but after that it kept saying cannot flash to critical.
I just got the phone today so I hope it's not already bricked. But the fact that I got it out of the "corrupt" loop gives me hope I can fix it. Is there any place to download the stock T-Mobile ROM so I can try and start over? Assuming it will even let me flash it. I couldn't find any by searching.
One observation I found to be very interesting.
The device should have been locked by the MSM tool through EDL flashing; yet, your device shows it's already unlocked.
I think the issue is still with your EDL flashing process as it should lock the bootloader then use flashing unlock critical to prevent critical partition flashing errors.
Also, your device is not bricked as long as you can still perform EDL flash. Just kept going and you can get it working without having to EDL flash anything else.
I see, thanks for the insight. So just so I don't mess anything up further, exactly what steps in what order do you recommend I perform?
My first instinct is to keep trying the EDL flashing until you can perform flashing critical unlock properly.
If things keep on failing, try to change your PC, driver, or other environmental variables.
It's just a painful process of elimination that you have to stick to.
Also, unless there are potential hardware issues, flashing like this shouldn't carry any more risk to brick your device compare to just using your device regularly. You aren't changing the hardware/software that is responsible for facilitating EDL.
EDL is fine, unlock_critical is fine, but flash-all gives me the same 'Flashing is not allowed for Critical Partitions' error on some partitions, and then I get stuck on the T-Mobile boot screen after. I'd think it wouldn't be the TMo screen by that point, right?
I've gone through this twice with the OEM cable and a different cable. The device was up to date with the latest TMo OTA before I started.
I'm about to try the TMo MSM to see if I can get it back to a working state.
Do you want to wipe all the data ( Reccomended )[Y/N]?nSending 'boot_a' (98304 - Pastebin.com
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
pastebin.com
seryniti said:
EDL is fine, unlock_critical is fine, but flash-all gives me the same 'Flashing is not allowed for Critical Partitions' error on some partitions, and then I get stuck on the T-Mobile boot screen after. I'd think it wouldn't be the TMo screen by that point, right?
I've gone through this twice with the OEM cable and a different cable. The device was up to date with the latest TMo OTA before I started.
I'm about to try the TMo MSM to see if I can get it back to a working state.
Do you want to wipe all the data ( Reccomended )[Y/N]?nSending 'boot_a' (98304 - Pastebin.com
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
pastebin.com
Click to expand...
Click to collapse
Edit:
[GUIDE][WIP]T-Mobile Brand Conversion to Rooted Global Firmware
First, let me say that this is only an attempt to pull this information out from a lot of different threads that require a bunch of research and a lot of institutional knowledge of Android. The idea of this thread is going from 100% T-Mobile...
forum.xda-developers.com
Apparently I'm not getting into FastbootD, so it's not flashing on the proper place. I'm going to try again. I noticed earlier when it runs "fastboot reboot fastboot" it's not working properly.
seryniti said:
Edit:
[GUIDE][WIP]T-Mobile Brand Conversion to Rooted Global Firmware
First, let me say that this is only an attempt to pull this information out from a lot of different threads that require a bunch of research and a lot of institutional knowledge of Android. The idea of this thread is going from 100% T-Mobile...
forum.xda-developers.com
Apparently I'm not getting into FastbootD, so it's not flashing on the proper place. I'm going to try again. I noticed earlier when it runs "fastboot reboot fastboot" it's not working properly.
Click to expand...
Click to collapse
Let me know what you find. I didn't even know there was other versions of MSM so I'll try that as well. I'd love to just at least get mine out of only being able to boot to Fastboot.
seryniti said:
Edit:
[GUIDE][WIP]T-Mobile Brand Conversion to Rooted Global Firmware
First, let me say that this is only an attempt to pull this information out from a lot of different threads that require a bunch of research and a lot of institutional knowledge of Android. The idea of this thread is going from 100% T-Mobile...
forum.xda-developers.com
Apparently I'm not getting into FastbootD, so it's not flashing on the proper place. I'm going to try again. I noticed earlier when it runs "fastboot reboot fastboot" it's not working properly.
Click to expand...
Click to collapse
Your 7T should be on the stock recovery screen when fastboot reboot fastboot completes. If your device boots into T-Mobile boot screen or bootloader, something is wrong with your env on PC.
You should never see T-Mobile boot screen at any given time during fastboot flashing process.
The final reboot should complete the conversion and boot into the intentional version OS.
so I've been trying to install a gsi for 5+ hours, I can never even get to the system boot animation. I've used permissiver, disable dm-verity, I've tried phh, erfans miui, oneui, oos, but cant get to the bootanimation. here are the steps i followed:
1. format
2. flash lineageos
3. wipe cache, dalvik, system, data
4 flash system.img gsi to system
5. flash permissiver and disable dmverity
6. reboot system
7. I get a redmi logo for 4 seconds, a black screen for 1 second and it keeps looping.
pls somebody help
You need to create a vendor.
hussain_mdj said:
You need to create a vendor.
Click to expand...
Click to collapse
pls elaborate, do i need to backup my current vendor, and then restore after installing the system.img?
I don't know why you have process steps like above, but basically the steps should be ( tested and used by me and all 2k members of my grp ) :
1st, you should be on stock, because GSI has only System images, and for a device to work, it need more than just a System images.
Boot into system, using adb reboot bootloader to get into bootloader mode ( or you can use hard keys, its up to you ). Execute these command in correct order :
fastboot devices ( check if device is connected )
fastboot reboot fastboot
fastboot --disable-verification flash vbmeta vbmeta.img ( remember to use patched vbmeta.img )
fastboot erase system
fastboot flash system system.img ( change to gsi's image file name )
fastboot -w
fastboot reboot bootloader
fastboot erase userdata
fastboot reboot
It may depends on what kind of device u have, but basically it should be like this. Try and feedback.