This is my first post, I'm not a pro at roms/kernel/etc, but I've learned something over the years, I guess.
Well, let's do it. This process is the same as reviving a bricked phone. This is an official rom so you don't need to have the bootloader unlocked, unless obviously you want to be rooted. As you know, we only need four things, the motorola universal drivers installed, adb and flashboot drivers, platform tools and the official android 11 Stock Rom (Retail Version), I don't know if it works with the dual sim version but this is easy peasy lemon squeezy.
Tools:
-Motorola drivers: https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/88481/
-Adb and fastboot drivers: https://drive.google.com/file/d/0B0...WkE/view?resourcekey=0-64AHOI-cvO3EHX6xZiOXQg
https://forum.xda-developers.com/attachment.php?attachmentid=4623157&d=1540039037
-Platform Tools: https://developer.android.com/studio/releases/platform-tools
-Stock Rom: https://mirrors.lolinet.com/firmware/moto/odessa/official/RETAIL/
-More Moto G9 Plus Roms: https://mirrors.lolinet.com/firmware/moto/odessa/official/
Instructions:
First, install the drivers, then unzip the platform tools rar, and with the stock rom downloaded, you just have to unzip it and transfer all the files to the platform tools folder, it doesn't matter that all the files get out of order, just make sure that all the files both as the platform tools and stock rom are in the same folder.
Now, make sure that your phone is at least 90%, if you want to have a clean experience, I recommend to do a factory reset, if you don't want that, don't do it, it still works, although it takes a little longer to install, lmao.
Second, turn off your phone and enter to fastboot mode, once you have installed all the drivers, just connect your phone to the PC, it should recognize it. To make sure, open a terminal and type the command "fastboot devices", and it should respond with a code and with the word 'fastboot' next to it. With that we know that the PC recognizes the device.
Third, close the terminal and now open a power shell or cmd with administrator permissions, and inside the terminal enter into the folder where the platform tools and stock rom files are. How to do it? (if you don't already know) There are two ways, you open a terminal directly from the folder, or inside cmd or power shell you write [cd 'insert folder address'] simple as that, hit enter, and then just copy and paste these commands and hit enter:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash dsp dspso.bin
fastboot flash erase userdata
fastboot flash erase ddr
fastboot oem fb_mode_clear
Let everything proceed, there should be no errors or anything like that if you have all your drivers installed correctly. After it finishes processing, reboot the phone and you already have Android 11 installed, then just configured your phone.
What's working (for me) lmaooo:
Everything, this rom seems to be optimized for all moto G9 Plus devices in general, although in system information it says that it is from Brazil, which I heard about it has many bugs and lag.
What's not working:
I don't know, don't tell me because I don't know anything about rom development, lmfao.
Just kidding, it has certain bugs. The default launcher for some reason has a large empty space where the Google widget should be, it's very annoying, but since I use the Nova Launcher, I could easily forget it.
The other thing would be is that sometimes the navigation bar gets bugged, very seldom but it happens, and it gets stuck vertically when you're using horizontal content, you just fix it using the auto-rotate to detect its position, or you use the gesture of recent apps in the position in which you are using it, it has only happened to me in some games like Fortnite or watching a video, very few times, but as I said, it happens from time to time.
Those are the only problems I've had, otherwise I feel it more fluid and faster than the default Android I had, even more, before the battery lasted 8 to 10 hours but now it can last 12 hours of constant use in basic applications such as social networks and media content and I have installed many applications that are open in the background all day long. So that's a pretty good thing.
Now I will teach you how to install root with Magisk.
Magisk Manager Apk: https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.6/MagiskManager-v8.0.6.ap
Credits to the developer and creator of Magisk, TopJohnWu
Link of his GitHub page (So you can keep up with his work):
topjohnwu - Overview
topjohnwu has 46 repositories available. Follow their code on GitHub.
github.com
I hope you have not yet deleted any files from the platform or the stock rom, because we will only need one file, boot.img, the key to everything.
So, once your mobile is configured, (obviously you must have the bootloader unlocked for this), just in case it turned on USB debugging, I don't know, I'm not sure, lmao, but I did it with USB debugging turned on. Copy the boot.img file to the phone memory and install the Magisk Manager apk, open the app and then go to install magisk, it will take you to the section where it says if you want to install magisk by patching a boot file, you click there and then select the boot.img file, it will patch it and then it will download you an img file that you'll gonna found in the download folder. You're going to copy that file and take it to the platform folder in the PC, then you're going to rename it as boot.img, do not replace the original file, just remove the original file from that folder and leave the renamed there.
Now turn off the mobile and enter to fastboot mode, as in the other process, open a terminal with the address of the folder, and put this command:
fastboot flash boot boot.img
And then reboot the system, go to the Magisk Manager and it should show you that you have root installed.
Congratulations, you are now rooted on your new Android 11 system. I hope this tutorial has been helpful to you, and that you have been able to understand me, since english is not my native language, that was it, thank you!
Gg I'll try it tomorrow
UsmanQ said:
Gg I'll try it tomorrow
Click to expand...
Click to collapse
Great! Tell me about your experience with this rom or if something goes wrong!
Friend, thank you very much I was waiting for this method since the update by OTA is taking a long time.
I did the update and everything was fine, only the command "fastboot flash erase userdata" gave me an error but it is not of much importance. I've been using android 11 and everything is perfect.
oscararm10 said:
Friend, thank you very much I was waiting for this method since the update by OTA is taking a long time.
I did the update and everything was fine, only the command "fastboot flash erase userdata" gave me an error but it is not of much importance. I've been using android 11 and everything is perfect.
Click to expand...
Click to collapse
Woah, that's weird, that command simply deletes all files from internal memory that don't belong to the system. Anyway, great that it served you, I also got tired of waiting for the update, lmao.
christjeam said:
Woah, that's weird, that command simply deletes all files from internal memory that don't belong to the system. Anyway, great that it served you, I also got tired of waiting for the update, lmao.
Click to expand...
Click to collapse
Yes, it also made me strange, but what matters is that it worked. This update improves the cell phone a lot, now the battery lasts longer and the cell phone feels faster.
The only bug I have is when I put the full screen in horizontal mode or when I play in horizontal screen the gesture bar remains active which does not allow me to select things that are in that place but I solve it they place the phone horizontally where the gesture bar is next to the camera. It is somewhat difficult to describe this bug, but it is not something that bothers or is very serious
oscararm10 said:
Yes, it also made me strange, but what matters is that it worked. This update improves the cell phone a lot, now the battery lasts longer and the cell phone feels faster.
The only bug I have is when I put the full screen in horizontal mode or when I play in horizontal screen the gesture bar remains active which does not allow me to select things that are in that place but I solve it they place the phone horizontally where the gesture bar is next to the camera. It is somewhat difficult to describe this bug, but it is not something that bothers or is very serious
Click to expand...
Click to collapse
Nice. It's great to know that it improved your experience on your mobile. Yeah, I also have that bug from time to time, but I solved it using the recent apps gesture, I simply do the gesture and go back to the app, and it is already in full screen without the navigation bar nor the notification bar. Another possible solution is to go to the screen settings and use the option to put the apps full screen, maybe that fixes the problem in some apps or games!
christjeam said:
Nice. It's great to know that it improved your experience on your mobile. Yeah, I also have that bug from time to time, but I solved it using the recent apps gesture, I simply do the gesture and go back to the app, and it is already in full screen without the navigation bar nor the notification bar. Another possible solution is to go to the screen settings and use the option to put the apps full screen, maybe that fixes the problem in some apps or games!
Click to expand...
Click to collapse
Super, I will fit certain apps with the full screen option. Thanks
lol, did smth wrong , thought bricked the device,got in bootloop, anyway for those whom this didnt work, there is a save firmware for moto g9 plus if you have the bootloader unlocked https://motostockrom.com/?s=g9+plus ,then just hit flashfile.bat while in fastboot to restore everything
I managed finally to upgrade to Android 11 pretty simple after a few days, just copied all the files from the RPA stock rom (the link in the original post with android 11) to the folder with the save firmware (the one with android 10 link above), renamed the file with the ODESSA_RETAIL_QPAS30.19-Q3-32-50-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.info ( check in the folder , i renamed the RPA to QPA and deleted the original QPA, because otherwise you will have 2 similar files) and just did it like restoring the original firmware (execute flashfile.bat ), only i had Android 11 now )) everything works fine
PS noticed afterwards that adb overscan does not work in any android 11 but managed to hide the navbar with this : https://forum.xda-developers.com/t/how-to-remove-nav-bar-in-android-11.4190469/
Hope helps.
Alex _dDd said:
lol, did smth wrong , thought bricked the device,got in bootloop, anyway for those whom this didnt work, there is a save firmware for moto g9 plus if you have the bootloader unlocked https://motostockrom.com/?s=g9+plus ,then just hit flashfile.bat while in fastboot to restore everything
I managed finally to upgrade to Android 11 pretty simple after a few days, just copied all the files from the RPA stock rom (the link in the original post with android 11) to the folder with the save firmware (the one with android 10 link above), renamed the file with the ODESSA_RETAIL_QPAS30.19-Q3-32-50-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.info ( check in the folder , i renamed the RPA to QPA and deleted the original QPA, because otherwise you will have 2 similar files) and just did it like restoring the original firmware (execute flashfile.bat ), only i had Android 11 now )) everything works fine
PS noticed afterwards that adb overscan does not work in any android 11 but managed to hide the navbar with this : https://forum.xda-developers.com/t/how-to-remove-nav-bar-in-android-11.4190469/
Hope helps.
Click to expand...
Click to collapse
You don't want to use the same bat file without checking the flash_file.xml commands can change with updates.
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
oscararm10 said:
Friend, thank you very much I was waiting for this method since the update by OTA is taking a long time.
I did the update and everything was fine, only the command "fastboot flash erase userdata" gave me an error but it is not of much importance. I've been using android 11 and everything is perfect.doesn't enter fastboot because it is corrupted. You'll have to wait till someone releases a Blankflash for this devices Im afraid.
(Moto g9 plus Odessa xt2087-2)
Click to expand...
Click to collapse
Alex _dDd said:
lol, did smth wrong , thought bricked the device,got in bootloop, anyway for those whom this didnt work, there is a save firmware for moto g9 plus if you have the bootloader unlocked https://motostockrom.com/?s=g9+plus ,then just hit flashfile.bat while in fastboot to restore everything
I managed finally to upgrade to Android 11 pretty simple after a few days, just copied all the files from the RPA stock rom (the link in the original post with android 11) to the folder with the save firmware (the one with android 10 link above), renamed the file with the ODESSA_RETAIL_QPAS30.19-Q3-32-50-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.info ( check in the folder , i renamed the RPA to QPA and deleted the original QPA, because otherwise you will have 2 similar files) and just did it like restoring the original firmware (execute flashfile.bat ), only i had Android 11 now )) everything works fine
PS noticed afterwards that adb overscan does not work in any android 11 but managed to hide the navbar with this : https://forum.xda-developers.com/t/how-to-remove-nav-bar-in-android-11.4190469/
Hope helps.
Click to expand...
Click to collapse
Wow, that's weird, but I see that you could solve it and that makes me happy, enjoy your Android 11!
christjeam said:
-Adb and fastboot drivers: https://drive.google.com/file/d/0B0...WkE/view?resourcekey=0-64AHOI-cvO3EHX6xZiOXQg
Click to expand...
Click to collapse
This link, don't work dude! :-(
ice.modding said:
This link, don't work dude! :-(
Click to expand...
Click to collapse
Use this: https://forum.xda-developers.com/attachment.php?attachmentid=4623157&d=1540039037
hi, what stock roms and other roms do i download? or do i just download them all?
Godfather096 said:
hi, what stock roms and other roms do i download? or do i just download them all?
Click to expand...
Click to collapse
You only download one, let it be one that aligns with your country and smartphone model
Stock rom links are broken please update
adamtarek said:
Stock rom links are broken please update
Click to expand...
Click to collapse
Links are still active, check your connection!
christjeam said:
This is my first post, I'm not a pro at roms/kernel/etc, but I've learned something over the years, I guess.
Well, let's do it. This process is the same as reviving a bricked phone. This is an official rom so you don't need to have the bootloader unlocked, unless obviously you want to be rooted. As you know, we only need four things, the motorola universal drivers installed, adb and flashboot drivers, platform tools and the official android 11 Stock Rom (Retail Version), I don't know if it works with the dual sim version but this is easy peasy lemon squeezy.
Tools:
-Motorola drivers: https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/88481/
-Adb and fastboot drivers: https://drive.google.com/file/d/0B0...WkE/view?resourcekey=0-64AHOI-cvO3EHX6xZiOXQg
https://forum.xda-developers.com/attachment.php?attachmentid=4623157&d=1540039037
-Platform Tools: https://developer.android.com/studio/releases/platform-tools
-Stock Rom: https://mirrors.lolinet.com/firmware/moto/odessa/official/RETAIL/
-More Moto G9 Plus Roms: https://mirrors.lolinet.com/firmware/moto/odessa/official/
Instructions:
First, install the drivers, then unzip the platform tools rar, and with the stock rom downloaded, you just have to unzip it and transfer all the files to the platform tools folder, it doesn't matter that all the files get out of order, just make sure that all the files both as the platform tools and stock rom are in the same folder.
Now, make sure that your phone is at least 90%, if you want to have a clean experience, I recommend to do a factory reset, if you don't want that, don't do it, it still works, although it takes a little longer to install, lmao.
Second, turn off your phone and enter to fastboot mode, once you have installed all the drivers, just connect your phone to the PC, it should recognize it. To make sure, open a terminal and type the command "fastboot devices", and it should respond with a code and with the word 'fastboot' next to it. With that we know that the PC recognizes the device.
Third, close the terminal and now open a power shell or cmd with administrator permissions, and inside the terminal enter into the folder where the platform tools and stock rom files are. How to do it? (if you don't already know) There are two ways, you open a terminal directly from the folder, or inside cmd or power shell you write [cd 'insert folder address'] simple as that, hit enter, and then just copy and paste these commands and hit enter:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash dsp dspso.bin
fastboot flash erase userdata
fastboot flash erase ddr
fastboot oem fb_mode_clear
Let everything proceed, there should be no errors or anything like that if you have all your drivers installed correctly. After it finishes processing, reboot the phone and you already have Android 11 installed, then just configured your phone.
What's working (for me) lmaooo:
Everything, this rom seems to be optimized for all moto G9 Plus devices in general, although in system information it says that it is from Brazil, which I heard about it has many bugs and lag.
What's not working:
I don't know, don't tell me because I don't know anything about rom development, lmfao.
Just kidding, it has certain bugs. The default launcher for some reason has a large empty space where the Google widget should be, it's very annoying, but since I use the Nova Launcher, I could easily forget it.
The other thing would be is that sometimes the navigation bar gets bugged, very seldom but it happens, and it gets stuck vertically when you're using horizontal content, you just fix it using the auto-rotate to detect its position, or you use the gesture of recent apps in the position in which you are using it, it has only happened to me in some games like Fortnite or watching a video, very few times, but as I said, it happens from time to time.
Those are the only problems I've had, otherwise I feel it more fluid and faster than the default Android I had, even more, before the battery lasted 8 to 10 hours but now it can last 12 hours of constant use in basic applications such as social networks and media content and I have installed many applications that are open in the background all day long. So that's a pretty good thing.
Now I will teach you how to install root with Magisk.
Magisk Manager Apk: https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.6/MagiskManager-v8.0.6.ap
Credits to the developer and creator of Magisk, TopJohnWu
Link of his GitHub page (So you can keep up with his work):
topjohnwu - Overview
topjohnwu has 46 repositories available. Follow their code on GitHub.
github.com
I hope you have not yet deleted any files from the platform or the stock rom, because we will only need one file, boot.img, the key to everything.
So, once your mobile is configured, (obviously you must have the bootloader unlocked for this), just in case it turned on USB debugging, I don't know, I'm not sure, lmao, but I did it with USB debugging turned on. Copy the boot.img file to the phone memory and install the Magisk Manager apk, open the app and then go to install magisk, it will take you to the section where it says if you want to install magisk by patching a boot file, you click there and then select the boot.img file, it will patch it and then it will download you an img file that you'll gonna found in the download folder. You're going to copy that file and take it to the platform folder in the PC, then you're going to rename it as boot.img, do not replace the original file, just remove the original file from that folder and leave the renamed there.
Now turn off the mobile and enter to fastboot mode, as in the other process, open a terminal with the address of the folder, and put this command:
fastboot flash boot boot.img
And then reboot the system, go to the Magisk Manager and it should show you that you have root installed.
Congratulations, you are now rooted on your new Android 11 system. I hope this tutorial has been helpful to you, and that you have been able to understand me, since english is not my native language, that was it, thank you!
Click to expand...
Click to collapse
I tried to use that method since I found it in a youtube video but when I used the patched boot.img file the system took too long to start and when I finished loading the device the touch didn't work, and it didn't matter if I repeated the command "fastboot flash boot" with the original boot.img file of the rom since it kept starting but at the same time the touch did not work.
(the boot.img file that I use was extracted from the "Rescue and smart assistant" program).
Hello,
I hope this is the right section for this post.
I've been using a Note 8 Pro with zero issues until one week ago when I accidentally dropped the phone in the water.
After a few seconds submerged the display turned off and I felt an intense heat coming from the zone of the battery.
Having no chance to recover the phone (tried with Isopropyl Alcohol too) I decided to open it and manually dry/clean each component, having seen the situation inside gave me the phone is dead but I still want to recover some pictures/data from it.
Before opening the open Minitool was not detecting any device on my Windows Laptop, after cleaning each component Minitool is instead detecting the phone via USB, but I still can't extract any data because the "Usb debugging" option is not tuned on (and no the device is not rooted).
Is there any option to extract data from the phone? There's a way to turn on USB Debugging via ADB on a non-rooted phone?
Thanks,
Andrea.
how about trying your luck with a service ? most of the time they do have access to special programs, which have a better functionality than adb.
Thanks for the hint, but I am not happy with the idea of someone playing with my data
1. Try reboot phone to recovery
2. Connect it to your computer (download Platform-tools)
3. In the folder with Platform-tools open cmd
4. In cmd - adb shell
5. cd storage/emulated/0
6. ls
7. Now, using the commands, drag files from your phone to your PC
Thanks for your hint.
No luck so far, I think because the phone is not in recovery mode.
I can hear the phone starting up several times (hear the jingle) so I think it's in a reboot loop and I don't know how to boot it into recovery mode wo a working display (tried with power/volume up combination with no luck).
From the windows taskbar I can see that the phone is recognized for a few seconds before it restarts.
EDIT: trying to switch the phone on with the combination "power/volume down" brings to a kind of stable state and I can now see the phone in the windows taskbar recognized as a generic "android device". Still no luck when trying to access the phone as there's no device in windows and no device obtained through "adb devices" command.
EDIT1: I think that the phone is in "FASTBOOT" mode. If I type "fastboot devices" I can see it detected but still can't access it.
Any idea? Should I give up?
If it's popping up and down you need something to keep track.
You can try my UsbLog.exe (in the sig), it just sits there and shows what devices appear (if they have a driver) and disappear.
Try these to see if anything is working:
Code:
C:\>fastboot devices
C:\>fastboot getvar all
C:\>fastboot oem device-info
Yes it's popping up and down when it's booted in recovery mode whilst is stably connected when in fastboot mode but in this case I can't access the internal memory of the device.
I didn't get the purpose of logging the devices connecting to the USB as I can see the device connected for a while and correctly recognized as Redmi Note 8 pro but as it keeps popping out windows have no time to show it's folder.
As for the code you wrote: i will try asap but already tried with "fastboot devices" and I get the phone correctly listed but still can't access its memory as told.
Renate said:
If it's popping up and down you need something to keep track.
You can try my UsbLog.exe (in the sig), it just sits there and shows what devices appear (if they have a driver) and disappear.
Try these to see if anything is working:
Code:
C:\>fastboot devices
C:\>fastboot getvar all
C:\>fastboot oem device-info
Click to expand...
Click to collapse
After rebooting the phone in fastboot mode I can see it recognized as a generic android device from windows (still can't access the storage folder of the device).
fastboot devices----> I get the device listed with a series of numbers/letters
fastboot getvar all---> I get a list of information on token/token version/partition type and size/baseband/bootloader etc.
fastboot oem device-info----> FAILED (remote: unknown command)
So I think it's clear that the device is in Fastboot mode and instead is in a boot loop when started in revocery mode.
Is there a way to extract data from fastboot mode?
Thanks,
Andrea.
If you put a custom recovery on it in the first place you can try reflashing recovery from fastboot.
Fastboot doesn't allow you to read anything.
oem device-info is obviously an oem command that might not be on any device.
You've got a Mediatek processor. That has some low level equivalent to Qualcomm EDL, but I have no experience with that.
If you can get there you can download the user data partition, but it's probably encrypted. Also no experience with that.
The easiest is if you can get the system to mount/decrypt the partition.
You've tried the normal system too?
Is this A/B? Have you tried changing slots?
How much time does it stay up in recovery? Do you have ADB? Maybe try:
Code:
# stop recovery
Does that prevent it from looping?
So I should try to flash a custom recovery like TWRP for example?
What you mean with "normal system too"?
Changing slots you mean changing usb port?
It stays in recovery less than one second so I can't give any command via ADB.
EDIT: cant' flash any custom recovery because the bootloader is locked.
If I Try to unlock the bootloader via MiUnlock I get a warning saying that all data will be erased.
Any idea on how to unlock the bootloader wo wiping all the data?
Sephiroth79 said:
So I should try to flash a custom recovery like TWRP for example?
What you mean with "normal system too"?
Changing slots you mean changing usb port?
It stays in recovery less than one second so I can't give any command via ADB.
EDIT: cant' flash any custom recovery because the bootloader is locked.
If I Try to unlock the bootloader via MiUnlock I get a warning saying that all data will be erased.
Any idea on how to unlock the bootloader wo wiping all the data?
Click to expand...
Click to collapse
There is a mediatek bootloader unlocked you just have to boot in Brom mode and it'll unlock it please follow this
PS: press all buttons
MysticNoOb said:
There is a mediatek bootloader unlocked you just have to boot in Brom mode and it'll unlock it please follow this
PS: press all buttons
Click to expand...
Click to collapse
My bootloader is unlocked!
Thank you very much.
Now I am going to try to flash a custom recovery mode via fastboot in order to access the internal memory of the phone.
EDIT: I've just flashed twrp-3.6.2_9-0-begonia.img but still can't boot into recovery mode.
Any hint on how to extract data from the system now?
You really want to boot the normal system because that's the best way to get decrypted data.
I realized that you don't have ADB enabled there.
You should look at B. Kerler's https://github.com/bkerler/mtkclient/
If you can pull the boot image off your device then I might be able to fix it so that you have ADB.
You'd have to flash it back in fastboot or mtkclient.
You can also pull a copy of userdata off the device with mtkclient.
As far as booting into recovery, there's a way.
Here's how, if you don't have A/B (that is you flashed TWRP into recovery and not recovery_a or recovery_b)
then you can fastboot flash a special file into the misc partition and it wil boot into recovery next reboot.
To return things to normal you have to flash the empty file to the misc partition.
Code:
C:\>fastboot flash misc misc-rec.img
C:\>fastboot reboot
Only do this if you don't have partitions that end in _a or _b
I really don't know if I have partitions A and B as you mentioned and I think there's no way to check actually.
I confirm I don't have "USB Debugging" active on the phone.
So if I understand correctly I should do the following:
- Flash misc-reg.img via Fastboot
- Boot into recovery just rebooting the system after flashing the above file;
- use MTKclient to dump userdata or boot image to enable ADB on (I will need help with mtkclient I suppose).
Is it correct?
EDIT: flashed TWRP first and misc-rec then rebooted via Fastboot/Reboot but nothing happens.
Sephiroth79 said:
My bootloader is unlocked!
Thank you very much.
Now I am going to try to flash a custom recovery mode via fastboot in order to access the internal memory of the phone.
EDIT: I've just flashed twrp-3.6.2_9-0-begonia.img but still can't boot into recovery mode.
Any hint on how to extract data from the system now?
Click to expand...
Click to collapse
TWRP cant boot because you used wrong one. Search again in that unlock bootloader channel and use suitable one.
Kirasu2080 said:
TWRP cant boot because you used wrong one. Search again in that unlock bootloader channel and use suitable one.
Click to expand...
Click to collapse
Hmmm, I am almost sure that the TWRP I've flashed was listed under Redmi Note 8 pro page. Can you please indicate more precisely where should I sera
EDIT: I think I've downloaded and flashed the correct TWRP file.
@Renate can you please detail your method so I can try to extract data from the phone?
Sephiroth79 said:
Hmmm, I am almost sure that the TWRP I've flashed was listed under Redmi Note 8 pro page. Can you please indicate more precisely where should I sera
EDIT: I think I've downloaded and flashed the correct TWRP file.
@Renate can you please detail your method so I can try to extract data from the phone?
Click to expand...
Click to collapse
1/Yeah it's official. You "flashed correct TWRP." Downgrade to Miui Android 9 (_9 in it's name) to boot into that TWRP and lose your data.
2/In unlock bootloader video above, search other video in his channel playlist and find TWRP video suitable for your Miui version.
Kirasu2080 said:
1/Yeah it's official. You "flashed correct TWRP." Downgrade to Miui Android 9 (_9 in it's name) to boot into that TWRP and lose your data.
2/In unlock bootloader video above, search other video in his channel playlist and find TWRP video suitable for your Miui version.
Click to expand...
Click to collapse
Can't find the right video, can you kindly send me a link (I am on the latest Miui version and I am in Europe)?
In all the videos I've seen on his page he is using the device to install TWRP etc.
I think I just need the correct TWRP version for my MIUI release and then I'll flash TWRP and misc-reg.img. Is it right?
Sephiroth79 said:
Can't find the right video, can you kindly send me a link (I am on the latest Miui version and I am in Europe)?
In all the videos I've seen on his page he is using the device to install TWRP etc.
I think I just need the correct TWRP version for my MIUI release and then I'll flash TWRP and misc-reg.img. Is it right?
Click to expand...
Click to collapse
Use brp 3.5.2 v3.1 or V3.6 to decrypt Miui 12.5
I have a LE 2125, didn't like what OOs12 did ( no Android Auto, worse battery life), so I replaced the ROM with Lineage OS 18.1. THAT broke even more things, especially banking apps, ( and still no Android Auto) due to it needing to be unlocked ( but not rooted). Tried factory reset and flashing the OEM recovery. Now I have that in slot b and the Lineage recovery in slot A. Now the phone cannot go into EDL, by pushing the volume buttons I can bring it into Lineage recovery, OR the stock Recovery if I go to Fastboot. I am so confused with how to install TWRP to regain control of my phone.
All the instructions for installing Magisk, or TWRP ( twrp used to be easy to install, either flashing or from the OS) or using MSM seem to be written by programmers talking to other programmers, ie too much knowledge is assumed when giving steps or making references to other things.
I installed the Qualcomm drivers, but the MSM tool ( proper one for my lemonadep, as far as I can tell and launched as ADmin) doesn't see anything, and of course I cannot seem to get EDL, or TWRP running.
When I connect my phone to the USB cable ( stock Oneplus red one connected to USB2.0 port) it brings up the Oneplus logo for about 10 seconds, then blinks, then after 10 more seconds goes blank, then after 5 seconds the pattern repeats.
I am not exactly a noob at this, I installed many OSes on my previous Oneplus ( One, X, 3T, 6T) phones, but none with this slot a/b thing. Admittedly my last OS replacement was on my 6T so it has been a few years, and my how things have changed!
coolvan170 said:
I have a LE 2125, didn't like what OOs12 did ( no Android Auto, worse battery life), so I replaced the ROM with Lineage OS 18.1. THAT broke even more things, especially banking apps, ( and still no Android Auto) due to it needing to be unlocked ( but not rooted). Tried factory reset and flashing the OEM recovery. Now I have that in slot b and the Lineage recovery in slot A. Now the phone cannot go into EDL, by pushing the volume buttons I can bring it into Lineage recovery, OR the stock Recovery if I go to Fastboot. I am so confused with how to install TWRP to regain control of my phone.
All the instructions for installing Magisk, or TWRP ( twrp used to be easy to install, either flashing or from the OS) or using MSM seem to be written by programmers talking to other programs, ie too much knowledge is assumed when giving steps or making reverences to other things.
I installed the Qualcomm drivers, but the MSM tool ( proper one for my lemonadep, as far as I can tell and launched as ADmin) doesn't see anything, and of course I cannot seem to get EDL, or TWRP running.
When I connect my phone to the USB cable ( stock Oneplus red one connected to USB2.0 port) it brings up the Oneplus logo for about 10 seconds, then blinks, then after 10 more seconds goes blank, then after 5 seconds the pattern repeats.
I am not exactly a noob at this, I installed many OSes on my previous Oneplus ( One, X, 3T, 6T) phones, but none with this slot a/b thing. Admittedly my last OS replacement was on my 6T so it has been a few years, and my how things have changed!
Click to expand...
Click to collapse
Can you, in fastboot mode (both volume buttons with power button combo) run command fastboot boot twrp.img or whatever the name you have, boots into TWRP then tap on advanced and tap on flash current TWRP...... That is how I do it!
TheGhost1951 said:
Can you, in fastboot mode (both volume buttons with power button combo) run command fastboot boot twrp.img or whatever the name you have, boots into TWRP then tap on advanced and tap on flash current TWRP...... That is how I do it!
Click to expand...
Click to collapse
That is one of my problems – I cannot find the image file for my device. All the links I followed lead me to source code which I must compile myself. The TWRP installer 3.6.2_11-0-lemonadep zip RAMdisk-twrp.cpio, magisk boot file which is only 300 K bites and a meta-info folder. But it is a zip file not an image file.
Post in thread '[RECOVERY] [3.7.0-12.1] [UNOFFICIAL] TWRP with A12/A13 encryption support' https://forum.xda-developers.com/t/...-a13-encryption-support.4523857/post-87793789
Thus is the latest twrp(unofficial, but decrypts and all functions work) by @der_akinator. U must flash vendor_boot.img 1st, then BOOT boot.img. Then once u get in twrp u can go to advanced and install "latest twrp" permantly if you please. However after that u are suppose to go back to fastboot and flash your stock vendor_boot, for your system to work. However, since you're isn't and you are going to use twrp to install rom/OS I think you can skip last part(stock vendor_boot flashing)
TheGhost1951 said:
Can you, in fastboot mode (both volume buttons with power button combo) run command fastboot boot twrp.img or whatever the name you have, boots into TWRP then tap on advanced and tap on flash current TWRP...... That is how I do it!
Click to expand...
Click to collapse
cant get fastboot to work, but ADB sideload does.
coolvan170 said:
cant get fastboot to work, but ADB sideload does.
Click to expand...
Click to collapse
Then for the sake of giving yourself all options possible, I would work on getting fastboot working first.
TheGhost1951 said:
Then for the sake of giving yourself all options possible, I would work on getting fastboot working first.
Click to expand...
Click to collapse
Found the QPST tool so I will try with that.
Shooter7889 said:
Post in thread '[RECOVERY] [3.7.0-12.1] [UNOFFICIAL] TWRP with A12/A13 encryption support' https://forum.xda-developers.com/t/...-a13-encryption-support.4523857/post-87793789
Thus is the latest twrp(unofficial, but decrypts and all functions work) by @der_akinator. U must flash vendor_boot.img 1st, then BOOT boot.img. Then once u get in twrp u can go to advanced and install "latest twrp" permantly if you please. However after that u are suppose to go back to fastboot and flash your stock vendor_boot, for your system to work. However, since you're isn't and you are going to use twrp to install rom/OS I think you can skip last part(stock vendor_boot flashing)
Click to expand...
Click to collapse
I found the QPST tool I will try working with that.
coolvan170 said:
I installed the Qualcomm drivers, but the MSM tool ( proper one for my lemonadep, as far as I can tell and launched as ADmin) doesn't see anything, and of course I cannot seem to get EDL, or TWRP running.
Click to expand...
Click to collapse
The PC running MSM should be in "test mode" with driver signing disabled. Then MSM will see your phone.
Skynet30 said:
The PC running MSM should be in "test mode" with driver signing disabled. Then MSM will see your phone.
Click to expand...
Click to collapse
Also you can try to side load TWRP img then use TWRP to boot into EDL mode...
The problem with the new A/B Slot solution is (2) things need to match in order to initiate a correct OS boot:
A Stock or (Working) Custom recovery.img
A Stock boot.img
This need to exist in both slots (A & B)
When in a Bootloop, your device is responding to a mismatch of at least one of these, causing corruption and a looping response.
I've made the same mistake and accidentally soft-bricked (what you're currently experiencing) on both my Oneplus 8 Pro and Oneplus 10 Pro
e.g.
Once in Fastboot mode, try flashing a clean boot and recovery to BOTH slots like this :
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash recovery_a recovery.img
fastboot flash recovery_b recovery.img
Try following my guide here to get things on track via Fastboot Mode:
https://forum.xda-developers.com/t/...e-rom-root-and-recovery.4525451/post-87806713
TheGhost1951 said:
Also you can try to side load TWRP img then use TWRP to boot into EDL mode...
Click to expand...
Click to collapse
Also, be sure you have the correct Qualcomm drivers typically packaged with an MSMTool+Stock ROM
Fwiw. Android auto has worked fine on a11, a12, and a13. Wired and wireless. Multiple head units. Wired is picky with cable however. Bluetooth and wifi both need to be on for wireless.