Develop Bugs

[RECOVERY][MT6735] TWRP-3.0.2 for Lenovo Tab3 7 (TB3-730X)

Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired. Please
* do some research if you have any concerns about features included in this Recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
[/CENTER]
Credits:
- TWRP Team
Device: Lenovo Tab3 7 Tablet - TB3-730X
Do not flash this on TB3-730F. The F model has different chipset and this recovery will softbrick it.
@sun_dream reported that 730F is working. So you can probably flash it, but be prepared with OFW, in case something goes wrong.
Instructions:
IMPORTANT: read all instructions at least once, before starting.
Note: If you're are a newbie, you can read more detailed instructions by honzazkrumlova here
- Download from link below.
- Enable "USB debugging" from developer options.
- Enable "OEM Unlocking" from developer options.
- Reboot device in Fastboot Mode (Bootloader mode), either with "adb reboot bootloader" or with VolDown+Power, to enter Recovery mode and then select "Reboot into bootloader"
- Unlock the bootloader with "fastboot flashing unlock" or "fastboot oem unlock" and follow the instructions on the tablet. (WARNING: This will erase all your data - Factory Reset)
- Once unlocked, you can use "fastboot boot TWRP_3.0.2_Lenovo_TB3-730X_Android-6.0_recovery.img" to start TWRP.
- When TWRP ask to modify system partition, answer "NO". Otherwise you will soft-brick your device and you will have to flash the original firmware and start from the beginning.
- If you want root - flash SuperSU, or as the user @Kellicros reported, you can flash Magisk 11.1.
- If you want XPosed, get it here.
- If you want to permanently flash the recovery, use "fastboot flash recovery TWRP_3.0.2_Lenovo_TB3-730X_Android-6.0_recovery.img".
- If you use it on any other Lenovo Tab3 7 device, please post the model.
- Thanks is always welcome.
Downloads:
TWRP_3.0.2_Lenovo_TB3-730X_Android-6.0_recovery.zip (well tested, consider it stable)
TWRP_3.1.1_Lenovo_TB3-730X_Android-6.0_recovery.zip
Unbrick your device:
Follow this thread

Hello
I have the same tablet (TB3-730X) and I tried this recovery, but something I did wrong.
Recovery by my works without problems, but now I can no longer boot into the system, I probably deleted it ...
After restarting the tablet always I return to Recovery and you can not flash the firmware because they can not find a version of the 730X (MTK MT8735P)
Can I use the firmware version for TB3-710 or 730F (MTK MT8161P)
Thanks for any advice, and thanks for Recovery.)

beldy said:
Hello
I have the same tablet (TB3-730X) and I tried this recovery, but something I did wrong.
Recovery by my works without problems, but now I can no longer boot into the system, I probably deleted it ...
After restarting the tablet always I return to Recovery and you can not flash the firmware because they can not find a version of the 730X (MTK MT8735P)
Can I use the firmware version for TB3-710 or 730F (MTK MT8161P)
Thanks for any advice, and thanks for Recovery.)
Click to expand...
Click to collapse
Hi.
When TWRP is started for the first time, it asks to modify the system partition.
I answered NO, NEVER. I saw some posts about other MTK devices and other people seems to have problems like yours when TWRP modify the system partition.
Is this your case?
If yes, then you need to download the original firmware and flash it on the device. After that you need to flash the recovery again.
I've downloaded the original firmware from Russian forum (this post: http://4pda.ru/forum/index.php?showtopic=731493&st=20#entry52434543). Here is direct link: https://cloud.mail.ru/public/Fjd9/u7e8mUbhq )
This is the last TB3-730X firmware. Do not try 710 firmwares, they should not work and it is probably dangerous to flash it. I dont know for 730F, this one could work, but anyway, download the the 730X firmware from the link above.
I guess you will need the SPFlash Tool to flash the firmware.
Hope this helps.

Thank you for the link ...
so probably it is my case that TWRP modify the system partition ... try this firmware and send the result ..
Thanks again for your help, I appreciate it.

I can confirm that Tab3 730x is checking if even TWRP is running (fastboot boot twrp.bin) and delete/modify system partition. TWRP not ask for modify system partition after first boot. Tablet stay on Lenovo logo forever. My firmware version is TB3-730X_S030_160509_ROW. Also in my model is not possible to read/write flash by FlashTool. I always get error 0x7D4, no matter what version I use, even after unlock bootloader. I have also try descibed firmware TB3-730X_S033_160707_ROW but this one cannot be flashed in fastboot mode. It says wrong binary (all files have in name _signed so probably different structure). It's seems that Polish Tab3 tb3-730X tablets are better protected than Russian.
0xAF can You post link to FlashTool what you used to flash your tablet?
[EDIT]
This time i get it working 0xAF are you mean first screen when TWRP start and there is swipe button? I Always swipe and this killed system partition I think. Btw do you both can flash this tablet with FlashTool?

DonKapselo said:
I can confirm that Tab3 730x is checking if even TWRP is running (fastboot boot twrp.bin) and delete/modify system partition. TWRP not ask for modify system partition after first boot. Tablet stay on Lenovo logo forever. My firmware version is TB3-730X_S030_160509_ROW. Also in my model is not possible to read/write flash by FlashTool. I always get error 0x7D4, no matter what version I use, even after unlock bootloader. I have also try descibed firmware TB3-730X_S033_160707_ROW but this one cannot be flashed in fastboot mode. It says wrong binary (all files have in name _signed so probably different structure). It's seems that Polish Tab3 tb3-730X tablets are better protected than Russian.
0xAF can You post link to FlashTool what you used to flash your tablet?
[EDIT]
This time i get it working 0xAF are you mean first screen when TWRP start and there is swipe button? I Always swipe and this killed system partition I think. Btw do you both can flash this tablet with FlashTool?
Click to expand...
Click to collapse
When you start the TWRP for the first time, it will ask to do something on system partition. I cannot remember if it was "Yes/No" answer, or a swipe. Just don't let TWRP touch the system partition.
After unlocking the bootloader with fastboot, you can flash the recovery with fastboot if you want, but first try to boot it, as described in the first post.
If you're going to flash the original firmware from the links above, then you will need SPFlash Tool, because the images (dumps) are made with SPFlash Tool and you cannot directly flash them with fastboot.
For bootloader unlocking, you can try this command: "fastboot oem unlock", while you're in the bootloader.
Did you enabled the "OEM Unlocking" from the "Developer Options" menu?
On my device, I was able to unlock it (after enabling "OEM Unlocking" option) with "fastboot flashing unlock".

"I have also try descibed firmware TB3-730X_S033_160707_ROW but this one cannot be flashed in fastboot mode. "
not to flash, always ends with an error 0x7D4 .....

beldy said:
"I have also try descibed firmware TB3-730X_S033_160707_ROW but this one cannot be flashed in fastboot mode. "
not to flash, always ends with an error 0x7D4 .....
Click to expand...
Click to collapse
Is your bootloader unlocked?
see the "fastboot" command manual, to check if it is unlocked.

0xAF said:
When you start the TWRP for the first time, it will ask to do something on system partition. I cannot remember if it was "Yes/No" answer, or a swipe. Just don't let TWRP touch the system partition.
After unlocking the bootloader with fastboot, you can flash the recovery with fastboot if you want, but first try to boot it, as described in the first post.
If you're going to flash the original firmware from the links above, then you will need SPFlash Tool, because the images (dumps) are made with SPFlash Tool and you cannot directly flash them with fastboot.
For bootloader unlocking, you can try this command: "fastboot oem unlock", while you're in the bootloader.
Did you enabled the "OEM Unlocking" from the "Developer Options" menu?
On my device, I was able to unlock it (after enabling "OEM Unlocking" option) with "fastboot flashing unlock".
Click to expand...
Click to collapse
Thanks. Now all working I just swipe button thinking that is locking button.
About flashing problem. I cannot flash with FlashTool because I have 0x7D4 error, same as beldy. I have try different cables, 3 computer, Windows 7, Windows 8 and Windows 10 - same.
I have unlocked bootloader with "fastboot oem unlock". Without it TWRP cannot be installer or booted. Before I enabled "OEM Unlocking" from the "Developer Options" menu. After it, phone format byself but still cannot flash.
I killed pcs one and send to service. Tablet cannot go into recovery. When it back I see some scratches on cover, like was opened. Maybe they used TestPoint to fix it.

DonKapselo said:
Thanks. Now all working I just swipe button thinking that is locking button.
About flashing problem. I cannot flash with FlashTool because I have 0x7D4 error, same as beldy. I have try different cables, 3 computer, Windows 7, Windows 8 and Windows 10 - same.
I have unlocked bootloader with "fastboot oem unlock". Without it TWRP cannot be installer or booted. Before I enabled "OEM Unlocking" from the "Developer Options" menu. After it, phone format byself but still cannot flash.
I killed pcs one and send to service. Tablet cannot go into recovery. When it back I see some scratches on cover, like was opened. Maybe they used TestPoint to fix it.
Click to expand...
Click to collapse
I'm glad you've solved the problem. I dont know what is 0x7D4 error. It could be some sort of extra locking of the device, but I doubt it. It's more likely to be something related to SPFlash Tools. It could be also a broken firmware, I haven't tried to flash the firmware from the links I've provided. I only used the Original Firmware to extract the original recovery from there. I needed the original kernel from the recovery to be able to start the TWRP.
A fast look in google gives this:
Error 0×7D4
Message: BROM ERROR: S_BROM_DOWNLOAD_DA_FAIL
Meaning: SP Flash tool encountered an error writing to the phone
Solution
* Try using a different USB cord, PC port and PC
* Use the latest version of SP flash tool
* Ensure the battery is well charged and the phone's USB port isn't faulty
Click to expand...
Click to collapse
But I guess it's not very helpful.

0xAF said:
I'm glad you've solved the problem. I dont know what is 0x7D4 error. It could be some sort of extra locking of the device, but I doubt it. It's more likely to be something related to SPFlash Tools. It could be also a broken firmware, I haven't tried to flash the firmware from the links I've provided. I only used the Original Firmware to extract the original recovery from there. I needed the original kernel from the recovery to be able to start the TWRP.
A fast look in google gives this:
But I guess it's not very helpful.
Click to expand...
Click to collapse
Just try to read flash, it's safe. I can bet You will get error 0x7D4 or 2004 (depend of version of flashtool). It's extra locked for sure. Btw. why You need original recovery to start TWRP? Maybe You mean that You need it to compile TWRP for this tablet model?

DonKapselo said:
Just try to read flash, it's safe. I can bet You will get error 0x7D4 or 2004 (depend of version of flashtool). It's extra locked for sure. Btw. why You need original recovery to start TWRP? Maybe You mean that You need it to compile TWRP for this tablet model?
Click to expand...
Click to collapse
The easiest way to port TWRP is to get it from another device with the same chipset and cpu. I did not wanted to prepare a toolchain/crosscompiler and start from the beginning to compile TWRP. So I took a TWRP from another tablet (DOOGEE_X6pro_Android6.0_20160707). Since it has a recent version of TWRP and is compiled for android 6.
Then all you need is to replace the kernel in this recovery, so we are booting with the kernel for our device. I needed the kernel from our original recovery for that. Then I've touched some files inside the recovery, fixed the fstab and default.prop and repackaged the recovery image.
This is the easiest way to port the recovery IMO. Took me 15-20 mins with all the testing.
This procedure work for any recovery, not only TWRP.
I guess, I could have dumped the original recovery from the device, but since I was looking for custom recovery for some time, I found the dump in the russian forum and downloaded it. So when I decided to port TWRP, I already had the recovery from the dump.

Thanks for info Any link to step by step how to replace kernet, what data change?

DonKapselo said:
Thanks for info Any link to step by step how to replace kernet, what data change?
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=hwMFBuCY-5k
I saw this video and decided to follow the steps.
You will need some intuition about the files you need to change inside the new recovery, as the video shows that only the fstab is needed, but you need more files, like default.prop and some other device dependent files from the original recovery (mostly in root folder).
In this recovery, I've used the default.prop from the original recovery.
As for the fstab, you will need to convert it by hand to a format understandable by TWRP. I've used the TWRP fstab file from the other device (from which I took the recovery in first place) and adopted it to our device. IIRC, almost nothing had to be changed.
I've copied some other device dependent files from the original recovery too.
Since I'm on linux, I've used these tools:
https://github.com/osm0sis/Android-Image-Kitchen.git
https://github.com/osm0sis/mkbootfs/
https://github.com/osm0sis/mkbootimg/
The tools are also available for windows (as the video shows) and for android itself (I believe the CF-SuperSU uses them on android to repack the boot.img).
These tools can repack recovery.img and boot.img.

Many thanks!

0xAF said:
Is your bootloader unlocked?
see the "fastboot" command manual, to check if it is unlocked.
Click to expand...
Click to collapse
yes bootloader is unlocked by command fastboot oem unlock...
It managed to someone already listed above to flash firmware in fastboot mode?
When you turn on the tablet remains lit Lenovo logo, and that's the end ...
Tablet can not even charged because, in the power cable connection tablet immediately turn on and loading TWRP or Lenovo logo screen
I am not progressed and I would appreciate if someone added original recovery or something what my tablet to function again
thx

beldy said:
yes bootloader is unlocked by command fastboot oem unlock...
It managed to someone already listed above to flash firmware in fastboot mode?
When you turn on the tablet remains lit Lenovo logo, and that's the end ...
Tablet can not even charged because, in the power cable connection tablet immediately turn on and loading TWRP or Lenovo logo screen
I am not progressed and I would appreciate if someone added original recovery or something what my tablet to function again
thx
Click to expand...
Click to collapse
Hi.
I'll make a dump of my system partition and post a link.
Unfortunately my system partition is not like in the original from the OTA ROM.
I've patched it with xposed and removed some ****ty apps from the OTA ROM.
Meanwhile if someone have OTA ROM, I would appreciate a link.
(you could try asking the Lenovo support for the OTA ROM).

0xAF said:
Hi.
I'll make a dump of my system partition and post a link.
Unfortunately my system partition is not like in the original from the OTA ROM.
I've patched it with xposed and removed some ****ty apps from the OTA ROM.
Meanwhile if someone have OTA ROM, I would appreciate a link.
(you could try asking the Lenovo support for the OTA ROM).
Click to expand...
Click to collapse
Thanks for the answer and advice to try anything that can help me
Thx
//EDIT: I add a few screens that I made an attempt to flash ... maybe you help someone ..

beldy said:
Thanks for the answer and advice to try anything that can help me
Thx
//EDIT: I add a few screens that I made an attempt to flash ... maybe you help someone ..
Click to expand...
Click to collapse
You should try to flash the dump with "fastboot flash system <file>"

Hello,
Got the Lenovo TAB3-730M.
What SuperSU.zip do I have to take to get "root"?
The "SR3-SuperSU-v2.78-SR3-20161103171345.zip" does not work.

[ROM][SOFIA*/RAV*][10][UNOFFICIAL] OmniROM

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Supported devices :
sofia
sofiap
sofiap_ao
sofiar
rav
rav_t
Download (GApps included)
Kernel source
Device tree source
MAJOR BUGS:
you tell me
FLASHING
Boot to fastbootd mode (adb reboot fastboot or fastboot reboot fastboot)
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot -w (mandatory if coming from stock, warning tho : it will erase all your data)
UPDATE
Boot to fastbootd mode (adb reboot fastboot or fastboot reboot fastboot)
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot reboot
Telegram support group : https://t.me/Motorola_G_Stylus
20200821 Changelog :
- Add support for g8/g fast
- Add LED support
- Add selinux enforced for all
- Safetynet should pass for all devices (can't check my self, let me know)
- Fix crash when turning off wifi hotspot
XDA:DevDB Information
OmniROM, ROM for the Moto G Stylus
Contributors
vache
Source Code: https://github.com/omnirom/
ROM OS Version: 2.3.x Gingerbread
ROM Kernel: Linux 4.x
ROM Firmware Required: Unlocked bootloader
Based On: AOSP
Version Information
Status: Beta
Beta Release Date: 2020-08-28
Created 2020-08-28
Last Updated 2020-08-28

2.3.x Gingerbread?

Just installed on my device, works great first try, only thing I've found to not work is Moto Audio with any sort of headphones, works with internal speaker tho. great work thanks!

googl-fi sofiap cannot flash to system
I am unable to flash to the system. It will not let me delete the super or system file. not sure what to do tried everything that is listed on the flash gsi. anyone with some help

lightningdude said:
2.3.x Gingerbread?
Click to expand...
Click to collapse
Typo, dude. F

rooted?
is this rom rooted?
vache said:
Supported devices :
sofia
sofiap
sofiap_ao
sofiar
rav
rav_t
Download (GApps included)
Kernel source
Device tree source
MAJOR BUGS:
you tell me
FLASHING
Boot to fastbootd mode (adb reboot fastboot or fastboot reboot fastboot)
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot -w (mandatory if coming from stock, warning tho : it will erase all your data)
UPDATE
Boot to fastbootd mode (adb reboot fastboot or fastboot reboot fastboot)
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot reboot
Telegram support group : https://t.me/Motorola_G_Stylus
20200821 Changelog :
- Add support for g8/g fast
- Add LED support
- Add selinux enforced for all
- Safetynet should pass for all devices (can't check my self, let me know)
- Fix crash when turning off wifi hotspot
XDA:DevDB Information
OmniROM, ROM for the Moto G Stylus
Contributors
vache
Source Code: https://github.com/omnirom/
ROM OS Version: 2.3.x Gingerbread
ROM Kernel: Linux 4.x
ROM Firmware Required: Unlocked bootloader
Based On: AOSP
Version Information
Status: Beta
Beta Release Date: 2020-08-28
Created 2020-08-28
Last Updated 2020-08-28
Click to expand...
Click to collapse

stolirocks said:
is this rom rooted?
Click to expand...
Click to collapse
Nope.

Although not "rooted" you can root after installation just like you would with stock.

Thank you for the ROM. First time using OmniRom and loving it so far. I have not run into any issues so far. Even on t-mobile, my WiFi calling, visual voicemail and text messages all are working without any issues.
Will you be releasing a version with just MicroG instead of gApps? I ended up just uninstalling all the gApps anyways, but just curious.
Keep up the great work!

GApps Dilemma
I am really looking forward to not having Gapps on this device, I haven't installed yet due to this, and wonder. Is this OpenGApps implentation removable using the same instructions as if it were installed manually after the CFW was flashed? Also, if it is not too much extra work, could you post a non GApps build?
Thanks for the hard work!

griz.droidx said:
Although not "rooted" you can root after installation just like you would with stock.
Click to expand...
Click to collapse
I tried rooting with the latest & second latest SuperSU flashable zip, but it didn't work. Do you know what build I could use?

.Solotato said:
I tried rooting with the latest & second latest SuperSU flashable zip, but it didn't work. Do you know what build I could use?
Click to expand...
Click to collapse
Greetings Solotato and Moto/Android community ,
I know this post is long excessively but hopefully it'll get the point across. Please don't think I'm talking down to you or anyone else. This whole process had me baffled at first as well and I've used others work to root and rom fur years. I've used Linux on the desktop by dual and even triple booting (Nix,Xpor2K, and 98 for old hardware slash gaming support) I even wrote a config for a guy's app called js2mouse to use 2 pointers at the same time in X(wanted to use my old logitech wingman cordless as a remote. But I'm no expert and still consider myself a little above novice. This isn't meant to offend anyone. Shew (the us is just too politically correct)
You can use twrp i think with magisk. BUT...im pretty sure i flashed twrp once in the recovery bootloader before but nothing else would take and twrp didn't function correctly.
I agree with many others now that it's easier to put a copy of the boot image on your device after installation. It's simple really
Just boot your device,
Enable developer options first thing then adb, then you can connect with a usb cable and approve adb access in your phone.
Copy the boot image to your phone and use the latest official magisk to patch the boot image. In magisk pick install then pick image, you pick your boot image which is then patched and renamed magisk_patched or similar.
It'll be in your downloads folder. Move it back to your pc, the patched one of course, and then just
fastboot flash boot magisk_patched.img
A TIP if you're new to the command line/powershell(win) or terminal(nix/bsd/mac (which is based on bsd)You can even use the up arrow if you dunt want to retype the commands then just replace boot.img with magisk_patched.img just start typing magis then hit tab and it'll complete it for you..
All this looks complicated but trust me after you do it a few times you'll be doing it in a minute or two.
Good luck take your time and read everything you can find. Don't forget to ask the command line for --help! You can find help in a jiffy that way.
Example
fastboot --help i think is the syntax i can't see it on my phone but there's a space between the two dashes and the command your asking for help. And for more details help is included in Linux with man pages. Those are handy in a pinch.
Even though I've done this since the droidx days on many phones, it still took me a lot of research and reading to get this new a/b partitioning and fastboot stuff down to where i can do it quickly.
Read and search these threads you'll be more likely to get answerers from xda members if they can tell you've been reading up on it.
Good luck!
Practice practice practice. That's the advice my uncle gave me on shooting a bow (instinctive or without sights) and he was right. This applies to everything in life.
Anyway I've preached enough. I know it's a long post but hopefully you and others who are relatively new to these moto's will get some help here.
Don't forget to thank the developers and others who made all this coolness possible for us who benefit from
If i helped any at all or you enjoyed my way too many useless details style, please hit thanks. I appreciate that. Sorry for the delay in posting I'm still setting up my most recent rom and I've doing a lot of stuff outside my home before winter.
Sent from my Moto G Stylus using XDA Labs

Sorry guys that was waaaaay too long.
Sent from my Moto G Stylus using XDA Labs

Could anyone point me in the right direction for recompiling this rom's kernel with a different config? I'm looking to poke around & try to get USB OTG/ACA mode to work (i.e. have the phone charge as well as use a usb device, like a mouse/keyboard/storage), which is apparently possible by setting CONFIG_USB_MSM_OTG and CONFIG_USB_MSM_ACA.
I've never compiled a kernel for another arch before, and I assume I need a toolchain that targets arm64 to begin with - I've also never really built anything for android before, and all the guides I've found thus far seem to either be for a specific device or building an entire system image, which seems to be too much - I'm given to understand I can replace the kernel image in boot.img by itself with a tool like mkbootimg.
Any help with where to start would be appreciated, thanks!

My Screen isn't working anymore... using an OTG to move around....
It's the touch screen

Another user asked this previously without any response ... Could you post a degoogled Omni ROM without gapps? Or give any advice how to remove it ? You were the one to put it all together so surely for you it must be easy removing it? As for me, I've been stuck.

Hi I am really struggeling here ... Everytime I try to flash system it ends with
writing 'system_b' 2/3...
FAILED (remote: Operation not permitted)
my bootloader is unlocked and I am in fastbootd.
I so far tried:
- other USB cables
- other ROM´s
- factory wiping
- flashing stock image again (which does work in both fastboot and fastbootd)
- reflashing recovery with stock one
- relocking and unlocking
- booting in to fastbootd via command and buttons
- diffrent minimal adb and fastboot versions
anyone have any ideas what I am doing wrong?

ianspy1 said:
Hi I am really struggeling here ... Everytime I try to flash system it ends with
writing 'system_b' 2/3...
FAILED (remote: Operation not permitted)
my bootloader is unlocked and I am in fastbootd.
I so far tried:
- other USB cables
- other ROM´s
- factory wiping
- flashing stock image again (which does work in both fastboot and fastbootd)
- reflashing recovery with stock one
- relocking and unlocking
- booting in to fastbootd via command and buttons
- diffrent minimal adb and fastboot versions
anyone have any ideas what I am doing wrong?
Click to expand...
Click to collapse
I am in no way a professional like other members here who probably can give you better advice but I was more successful when I downloaded platform tools version 26.0.0. I wasn't successful on my device but after using a older version I was able to get a different set of errors. But I also at the end was unable to flash. Maybe this will help you ?

gatorz_4z said:
I am in no way a professional like other members here who probably can give you better advice but I was more successful when I downloaded platform tools version 26.0.0. I wasn't successful on my device but after using a older version I was able to get a different set of errors. But I also at the end was unable to flash. Maybe this will help you ? My hope is that with that version you will be successful? Another person told me to redownload the ROM and try with a fresh one.
Click to expand...
Click to collapse

Gotta love how unsupported this ROM is... Or just busy dev...

How To Guide Convert your T-Mobile (LE2127) to EU via MSM, No unlock.bin needed!

*** Use this at your very own risk.
*** You will lose all data
*** Backup your working modemst1/2 and persist. If you lose these for any reason, it's unique to your device and not recoverable if you didn't back up (via MSM or other people).
*** Read the entire post and follow the steps closely before asking for help. Post all error messages and steps you took. If you just ran a bunch of unknown commands, I would tell you to MSM.
*** Know how to use the MSMTool, Don't start before figuring it out. https://forum.xda-developers.com/t/op9pro-repository-of-msm-unbrick-tools-tmo-glo-in.4272549/
*** DO NOT ATTEMPT THIS IF YOU ARE NOT FAMILIAR WITH ANY STEP DESCRIBED IN THIS GUIDE
General notes:
NR and LTE bands are read only and not modifiable, not in modem.img or any other partition. You cannot get global bands by flashing a global ROM, nor can you lose TMO bands by flashing another ROM.
If you wish to unlock the bootloader without unlock_code.bin, you MUST do it from OOS11. If you upgrade to OOS12/OOS13, you will need the unlock_code.
The T-Mobile NON-HLOS is no longer necessary as of OOS13 release. If you must stay on OOS11 or OOS12, make a backup of the T-Mobile modem partition for the OOS version you want to stay on.
Dual-SIM does not work.
Prerequisites:
This conversion will not SIM unlock you. You can only SIM unlock on a T-Mobile ROM, meaning if you want to do that in the future, you must go back to a TMO ROM (and wipe)
Familiarity with MSMDownload tools. If the regular MSM tool doesn't work for you, turn back now.
Back up all data, it will be wiped.
Download:
Conversion: AndroidFileHost (MD5: 8cc3e5e81d15e28bb10dc5f1e7bd4133)
Steps:
Run the MSM file normally.
Unlock your bootloader if necessary. Now is the time if you don't have unlock.bin
Patch up to Android 13 while on Wifi if your mobile data doesn't work. Use this time to go to another variant (GLO, IN, etc) as needed.
Fastboot method:
* The steps in this guide will convert your TMO LE2127 to EU 11.2.3.3. This is intentionally not the latest version to force you to take a FULL OTA.
* You must already have the bootloader unlocked with an unlock_code.bin
* You can use this guide to convert to your own variant by extracting payload and flashing from a full OTA. No support will be given if you choose to manually do it.
* Use the latest platform tools: https://developer.android.com/studio/releases/platform-tools. DO NOT USE MINIMAL ADB, it has not been updated for years.
* Fastboot can't see your device? https://forum.xda-developers.com/t/...stboot-mode-windows-10.4194491/#post-84943553
* Test that you can boot to fastbootd prior to starting, "fastboot reboot fastboot" and you should see the OnePlus logo with the text "fastbootd" on top. Do not continue if this doesn't work.
* When encountering issues, describe all steps you took, paste any outputs, and take screenshots. Make sure to include the output of fastboot --version in your post.
Steps to convert your device to EU
You need your device bootloader and SIM unlocked. See https://forum.xda-developers.com/t/how-to-unlock-the-t-mobile-bootloader.4256319/
Download and unzip the conversion package:
EU 11.2.3.3
MD5: cb949816fa80d5f0d984359b819426c3
Boot to bootloader.
From adb:
Code:
adb reboot bootloader
From fastboot/bootloader:
Code:
fastboot reboot bootloader
Execute "flash_all.bat" from the unzipped directory from step 2.
Reboot into recovery, and wipe everything.
Once fully booted, connect to WiFi and download Oxygen Updater and take the FULL OTA (11.2.4.4 as of this writing)
Do a regular reboot, don't reboot to fastbootd, bootloader, recovery, etc. Reboot to system.
Reboot into bootloader or fastbootd, and flash the T-Mobile modem.
Code:
fastboot flash modem NON-HLOS.bin
After each Full OTA you take in the future, you will need to repeat step 7 & 8
FAQ
Q: The most recent version is 11.2.4.4, why is this guide converting to 11.2.3.3?
A: You didn't read the full post.
Q: Why is there no conversion to Global?
A: Global variant uses the Google incremental OTA server, and full OTAs are not always provided. There's no functional difference, and EU has better privacy requirements anyways. You can do it manually by extracting payload.bin and running the same flash script. No support will be provided if you choose to flash to Global.
Q: Can I re-lock the bootloader after conversion?
A: While you can go ahead lock your bootloader after conversion, I don't recommend it as you will not be able to take incremental OTA due to modem changes, and lose connectivity if you take a full OTA. To fix it, you need to unlock the bootloader and end up wiping.
Q: Where is the Linux guide?
A: Too lazy, if you're using Linux, you can make your own bash script from the Windows batch script.
Q: Help, I see is 'fastboot' is not recognized as an internal or external command.
A: Your fastboot.exe is not in your $PATH. You can either drop fastboot into the same folder as flash-all.bat, or you can fix your $PATH
Q: Help, I cannot boot to fastbootd because previous flashes messed things up.
A: MSM
Q: Help, "not enough space to resize [system, product, system_ext]"
A: MSM. If the error is on Vendor, it might still work and boot with a generic Android boot logo. If so, take the full OTA as described in the guide.
Q: Help, something went wrong!
A: Post in here the starting state of your device (Device model, ROM version, etc), all steps you've taken since unlocking bootloader, and the output of whatever is causing you trouble. Chances are, the answer is MSM, but read my MSM warning.
Q: Help, I see "Invalid sparse file format at header magic"
A: Ignore this message, not an error
Fixing the About Phone page
These steps are optional, and is only applicable for OOS11. It will fix the "About Phone" page. There are no performance differences. All that's done is change build.prop to reflect the correct model.
You need to rooted with Magisk
Download and install the magisk module: here
Reboot, the About Phone page is filled out.
Instructions to Bootloader Unlock a SIM locked device:
In ADB:
Code:
adb shell pm uninstall -k --user 0 com.qualcomm.qti.uim
Reboot
Go to dev settings and enable OEM Unlock
Reboot to bootloader
Code:
fastboot oem unlock
No unlock.bin needed
Issues so far (please post if you run into more):
If your mobile data doesn't work on OOS13, PM me details including HW Revision in About Phone.
What appears to work:
Everything else.
Much appreciation for everyone that help develop and test
@razercortex
@retryfail
@amaroney55

I went straight to the 11.2.4.4 as well, instead of the 11.2.3.3. Probably why I had such an issue also. Dummy me, wanted the latest and greatest right away and paid the price for it.

Goodness man. Presently I see where I wrecked. I did the EU 11.2.4.4 and not the 11.2.3.3. much obliged for this and clearing that up. Likewise, thank you again for assisting me with saving my mobile. JBBattery

Woohoo! Thank you!!

for some reason my Wildvine downgrades to L3, not sure how to fix it, also as other post indicates, voice mail on dialer doesn't work

avid_droid said:
It says to have magisk hiding from Google play services. Have you done that?
Click to expand...
Click to collapse
Yes, I toggled all options under google play services, no luck
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

ok going to give this a go later fingers crossed and just to clarify i only need to backup ModemST1 and ModemST2 img correct?

avid_droid said:
Nope. TRied again and its a no go since every damn thing is failing. fastboot mode and fastbootd is constantly failing on every file thats being flashed. What you need from me.?
Click to expand...
Click to collapse
you mind pasting some errors here? maybe the 1st error you got from cmd

Ultraman666 said:
ok going to give this a go later fingers crossed and just to clarify i only need to backup ModemST1 and ModemST2 img correct?
Click to expand...
Click to collapse
Persist

avid_droid said:
Nope. TRied again and its a no go since every damn thing is failing. fastboot mode and fastbootd is constantly failing on every file thats being flashed. What you need from me.?
Click to expand...
Click to collapse
* Test that you can boot to fastbootd prior to starting, "fastboot reboot fastboot" and you should see the OnePlus logo with the text "fastbootd" on top. Do not continue if this doesn't work.
* When encountering issues, describe all steps you took, paste any outputs, and take screenshots. Make sure to include the output of fastboot --version in your post.
Sounds like you tested that fastboot can't get you to fastbootd, but you continued anyways.
If you want troubleshooting, post the information I said to post

craznazn said:
Persist
Click to expand...
Click to collapse
Thanks for the hint, I backed up the persist.img but that's after root/unlock bl, so you are saying flash persist.img will get me back to L1?

avid_droid said:
everything fails in flashing. it just says FAILED on every .img that is being pushed. Im so confused. It says be in bootloader,but isnt it supposed to be in fastbootd???
Im still getting no response from fastboot reboot fastboot. Only way i can get into fastbootd is by adb reboot fastboot.
Which is it? in bootloader or fastbootd??
Click to expand...
Click to collapse
avid_droid said:
fastboot --version says unkown option
Click to expand...
Click to collapse
sounds to me like you don't get the proper version of fastboot, one thing to notice, if you install the one plus driver you may get the fastboot from C:\Android, DONT use this one. either put the correct platform-tool path to your $PATH or manually modify every fastboot.exe to be full path in script

sunxutian said:
Thanks for the hint, I backed up the persist.img but that's after root/unlock bl, so you are saying flash persist.img will get me back to L1?
Click to expand...
Click to collapse
No, persist just unique to your device. You just need a backup in case yours get wiped for any reason.
Honestly, you are the 2nd person I've heard from that had the L1 issue and we were never able to figure it out. I did these steps to 2 different devices and both kept L1. Does safetynet pass? Do you have magisk canary?

craznazn said:
No, persist just unique to your device. You just need a backup in case yours get wiped for any reason.
Honestly, you are the 2nd person I've heard from that had the L1 issue and we were never able to figure it out. I did these steps to 2 different devices and both kept L1. Does safetynet pass? Do you have magisk canary?
Click to expand...
Click to collapse
Yes, my safetynet passes and I do have magisk canary

avid_droid said:
I have it in C: and am opening powershell from that folder
Click to expand...
Click to collapse
Download a fresh copy of platform tools and unzip it into the folder that has flash_all.bat and .img files

craznazn said:
No, persist just unique to your device. You just need a backup in case yours get wiped for any reason.
Honestly, you are the 2nd person I've heard from that had the L1 issue and we were never able to figure it out. I did these steps to 2 different devices and both kept L1. Does safetynet pass? Do you have magisk canary?
Click to expand...
Click to collapse
what I suspect might be wrong is when I did the BL unlock I use fastboot oem unlock while some people use fastboot flashing unlock (not sure this makes any difference or not)

I did oem unlock, shouldn't make a difference

From that folder, run fastboot --version and share the screenshot

craznazn said:
I did oem unlock, shouldn't make a difference
Click to expand...
Click to collapse
Then anything I can try?

sunxutian said:
Then anything I can try?
Click to expand...
Click to collapse
Hmm, also try the fix about page magisk module, shouldn't affect anything but you never know.
If that doesn't fix it, take the 11.2.4.4 OTA again via local update, and then lock the bootloader and check. You won't have a working modem but I want to make sure your wildvine keys are still there.

How To Guide Nokia G20 boot.img flashing!

Please be aware that this could damage your phone & I'm not responsible for this. So only do this if you really feel comfortable with it & you know about the risks!
This file is only for Nokia G20 TA-1365 and should not be used for any other device.
Download this file to manually Flash partition or partitions using fastboot Command.
For more detailed tutotial on how to flash this file you can read this tutorial here by senior member fipsib at XDA!
Let's say you want to flash boot.img partition so in CMD you will enter.
"fastboot flash boot boot.img" without quotes.
I have extracted OTA stock rom for my Nokia G20 and have all the files in the screenshot below. If you want all the files shown in the screenshot below I have uploaded them to Google Drive for faster and safer downloads rather than using any other file sharing service.
I have compressed all the files in a zip format and here is the Google Drive link for all the files shown below. Please request the access to the file so that I can grant access to you. I have done this to prevent Google setting an limit to download and avoid any unnecessary downloads.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Do you have to unlock bootloader to flash boot.img if you have to can you tell how????

Don't know said:
Do you have to unlock bootloader to flash boot.img if you have to can you tell how????
Click to expand...
Click to collapse
Thankyou buddy but actually this post is a guide.

mvikrant97 said:
Please be aware that this could damage your phone & I'm not responsible for this. So only do this if you really feel comfortable with it & you know about the risks!
This file is only for Nokia G20 TA-1365 and should not be used for any other device.
Download this file to manually Flash partition or partitions using fastboot Command.
For more detailed tutotial on how to flash this file you can read this tutorial here by senior member fipsib at XDA!
Let's say you want to flash boot.img partition so in CMD you will enter.
"fastboot flash boot boot.img" without quotes.
I have extracted OTA stock rom for my Nokia G20 and have all the files in the screenshot below. If you want all the files shown in the screenshot below I have uploaded them to Google Drive for faster and safer downloads rather than using any other file sharing service.
I have compressed all the files in a zip format and here is the Google Drive link for all the files shown below. Please request the access to the file so that I can grant access to you. I have done this to prevent Google setting an limit to download and avoid any unnecessary downloads.
View attachment 5450449
Click to expand...
Click to collapse
Please share download link.I need to unbrick my Nokia G20 that was bricked.I have no firmware

Download this OTA ROM and flash using Apply update from SD CARD in recovery menu.
Use external SD card.
I don't know whether this will work.
ROM link

Don't know said:
Do you have to unlock bootloader to flash boot.img if you have to can you tell how????
Click to expand...
Click to collapse
Yes need to unlock bootloader.

mvikrant97 said:
Download this OTA ROM and flash using Apply update from SD CARD in recovery menu.
Use external SD card.
I don't know whether this will work.
ROM link
Click to expand...
Click to collapse
Hi thanks for the link. But my phone is bricked, can't enter recovery or fastboot mode. So the only solution here is a read firmware or scatter file.

mvikrant97 said:
Please be aware that this could damage your phone & I'm not responsible for this. So only do this if you really feel comfortable with it & you know about the risks!
This file is only for Nokia G20 TA-1365 and should not be used for any other device.
Download this file to manually Flash partition or partitions using fastboot Command.
For more detailed tutotial on how to flash this file you can read this tutorial here by senior member fipsib at XDA!
Let's say you want to flash boot.img partition so in CMD you will enter.
"fastboot flash boot boot.img" without quotes.
I have extracted OTA stock rom for my Nokia G20 and have all the files in the screenshot below. If you want all the files shown in the screenshot below I have uploaded them to Google Drive for faster and safer downloads rather than using any other file sharing service.
I have compressed all the files in a zip format and here is the Google Drive link for all the files shown below. Please request the access to the file so that I can grant access to you. I have done this to prevent Google setting an limit to download and avoid any unnecessary downloads.
View attachment 5450449
Click to expand...
Click to collapse
Kindly grant access to [email protected] need to unbrick my device

I would like to ask how do I extract the boot.img file from the phone? I can access the internals through the adb shell. I would love to learn the strategies used to extract the firmware from android devices that do not make them available. Thanks!!

karangejo said:
I would like to ask how do I extract the boot.img file from the phone? I can access the internals through the adb shell. I would love to learn the strategies used to extract the firmware from android devices that do not make them available. Thanks!!
Click to expand...
Click to collapse
Simply... You can't without root.
To get root (permanent root) you must unlock your bootloader........
Please, read this post to understand what i'm talking about https://forum.xda-developers.com/t/nokia-g21-development.4424031/
I think that today there's no way to unlock G10/G20/G21 bootloader. Then, no root or custom recovery can be build.
Maybe, @mvikrant97 can share with us some info (PM).

I unlocked my g20 TA-1343 by taking a hundred tiny screws out , shorting the test point, and using MTK Client 1.6
hyperlink of the link i pastedhttps://github.com/bkerler/mtkclient
I only took it apart because the other option was send it back to HMD
But I don't know how to flash the bin files with magisk or whatever as they're not valid images. but the thing is basically root if i felt like learning.

jdberkzk said:
I unlocked my g20 TA-1343 by taking a hundred tiny screws out , shorting the test point, and using MTK Client 1.6
hyperlink of the link i pastedhttps://github.com/bkerler/mtkclient
I only took it apart because the other option was send it back to HMD
But I don't know how to flash the bin files with magisk or whatever as they're not valid images. but the thing is basically root if i felt like learning.
Click to expand...
Click to collapse
Do you mean the bootloader unlock?

mvikrant97 said:
Do you mean the bootloader unlock?
Click to expand...
Click to collapse
Yes I unlocked the bootloader with mtk client but i have the G20 ta-1343 and. I didn't have a stom rom for it.. and I bricked it trying to root it and corrupt the gpt it looks like, now I cant get it to load in mtk client anymore. I haven't errased the rest of the phone but it is in a/b format so i dont know if i should flash it? I was stuck in boot loop

jdberkzk said:
Yes I unlocked the bootloader with mtk client but i have the G20 ta-1343 and. I didn't have a stom rom for it.. and I bricked it trying to root it and corrupt the gpt it looks like, now I cant get it to load in mtk client anymore. I haven't errased the rest of the phone but it is in a/b format so i dont know if i should flash it? I was stuck in boot loop
Click to expand...
Click to collapse
mvikrant97 said:
Do you mean the bootloader unlock?
Click to expand...
Click to collapse
I got bootloader unlocked but when i flashed magisk i got stuck on the android one screen and then now it's back to the no OS boot loop and
Error on reading data: MMC error (0xc0040030)
in mtkclient. i cant get to fastboot anymore.

I du
mvikrant97 said:
Do you mean the bootloader unlock
Click to expand...
Click to collapse
I dumped everything from my phone to my computer except userdata super otp and flashinfo i think.
the bins would flash the same as images except I can't get them to flash. should I try another firmware or?

Lg G8 AT&T boot_b.bin lost, fastboot loop

hello my name is petrus and i have a lg g8 LMG820M ATT with unlocked bootloader, i installed a custom rom ArrowOS 12.1 that worked perfectly, however i went to root with qfil and accidentally ended up replacing boot_b.bin by boot_a.bin , now the phone is stuck on fast boot screen
it already starts directly in fastboot and the text "ACTICE A/B slot - _a" no longer appears on the fastboot screen, there was no backup of boot_b.bin so I don't know how to solve it
Is there anything I can do to get it back? Or did he become a piece of garbage?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

vini14zimm said:
hello my name is petrus and i have a lg g8 LMG820M ATT with unlocked bootloader, i installed a custom rom ArrowOS 12.1 that worked perfectly, however i went to root with qfil and accidentally ended up replacing boot_b.bin by boot_a.bin , now the phone is stuck on fast boot screen
it already starts directly in fastboot and the text "ACTICE A/B slot - _a" no longer appears on the fastboot screen, there was no backup of boot_b.bin so I don't know how to solve it
Is there anything I can do to get it back? Or did he become a piece of garbage?
View attachment 5656703
Click to expand...
Click to collapse
No, not a piece of garbage lol. Given the tools available for the G8; qfil, the programmers firehose, engineering abl, it's almost impossible to brick the device.
So, lesson learned; always make a backup. It sounds like you copied the boot partition for the slot that had at&t rom on it, to the slot that had ArrowOS on it? If so, sounds like just finding a copy of the ArrowOS boot partition should work?
Which version are you running? Someone may have that boot partition available.

AsItLies said:
No, not a piece of garbage lol. Given the tools available for the G8; qfil, the programmers firehose, engineering abl, it's almost impossible to brick the device.
So, lesson learned; always make a backup. It sounds like you copied the boot partition for the slot that had at&t rom on it, to the slot that had ArrowOS on it? If so, sounds like just finding a copy of the ArrowOS boot partition should work?
Which version are you running? Someone may have that boot partition available.
Click to expand...
Click to collapse
yes that was exactly it, i understand i will never do anything without backup, i was using Arrow-v12.1-alphalm-UNOFFICIAL-20220627
so if someone has lg g8 and is using Arrow v12.1 alpham send boot_b.bin and I copy it using QFIL will my device boot again?

vini14zimm said:
yes that was exactly it, i understand i will never do anything without backup, i was using Arrow-v12.1-alphalm-UNOFFICIAL-20220627
so if someone has lg g8 and is using Arrow v12.1 alpham send boot_b.bin and I copy it using QFIL will my device boot again?
Click to expand...
Click to collapse
Well, if all that's changed is the boot partition it should boot again. But I checked on tele group and no one responded with it.
You may have to download the rom and see if you can extract the boot partition from it.

II have the same problem, were you able to solve it?

i need help

yonaikymatos said:
II have the same problem, were you able to solve it?
Click to expand...
Click to collapse
I'm trying to extract this boot_b.bin from the room that AsItLies said, but I'm not going to lie I don't have much knowledge of how to do this so I still haven't been able to extract this file
It's very difficult to extract one without knowing how to do it but I'm still trying

vini14zimm said:
I'm trying to extract this boot_b.bin from the room that AsItLies said, but I'm not going to lie I don't have much knowledge of how to do this so I still haven't been able to extract this file
It's very difficult to extract one without knowing how to do it but I'm still trying
Click to expand...
Click to collapse
Okay, think this is what you need. BUT!! I'm not 100% it is... SO! first thing you do is back up the boot image from the slot you want to replace it with this one. That way, if it doesn't work, you can just reflash the one you backed up and you're none the worse.
Second: IF, when flashing this image to the boot partition (loading it in qfil speak), you get a warning message about 'over flow of data' (or something to that effect), immediately stop, do not continue, as that's an indication it will not only not work but make your situation worse. Good luck
sorry, xda not allowing me to attach, follow this gdrive link for file.

vini14zimm said:
I'm trying to extract this boot_b.bin from the room that AsItLies said, but I'm not going to lie I don't have much knowledge of how to do this so I still haven't been able to extract this file
It's very difficult to extract one without knowing how to do it but I'm still trying
Click to expand...
Click to collapse
I already solved it I'm going to attach the boot_b .bin
https://drive.google.com/file/d/1DANvrF-iklHQxr3bIOixv9orD376oG8U/view
the file is boot-a Android 11 Canadienc.bin
flash using qfil on a boot_b

AsItLies said:
Okay, think this is what you need. BUT!! I'm not 100% it is... SO! first thing you do is back up the boot image from the slot you want to replace it with this one. That way, if it doesn't work, you can just reflash the one you backed up and you're none the worse.
Second: IF, when flashing this image to the boot partition (loading it in qfil speak), you get a warning message about 'over flow of data' (or something to that effect), immediately stop, do not continue, as that's an indication it will not only not work but make your situation worse. Good luck
sorry, xda not allowing me to attach, follow this gdrive link for file.
Click to expand...
Click to collapse
I put arrowOS-boot.img in place of boot_b.bin using Qfil but I'm still at the fast boot screen, is there anything else I can do?

yonaikymatos said:
I already solved it I'm going to attach the boot_b .bin
https://drive.google.com/file/d/1DANvrF-iklHQxr3bIOixv9orD376oG8U/view
the file is boot-a Android 11 Canadienc.bin
flash using qfil on a boot_b
Click to expand...
Click to collapse
for some reason it's not being possible to put your boot-a Android 11 Canadienc.bin in place of my boot_b.bin , when I try to get this message Send image fail:Firehose Fail:FHLoader Failrocess fail , it doesn't seem like a good sign

vini14zimm said:
for some reason it's not being possible to put your boot-a Android 11 Canadienc.bin in place of my boot_b.bin , when I try to get this message Send image fail:Firehose Fail:FHLoader Failrocess fail , it doesn't seem like a good sign
View attachment 5659247
Click to expand...
Click to collapse
Don't use a usb 3.0 port when using qfil. You have to use a usb 2.0 port. Qfil is old software and was not designed for the higher speeds.
This is important whether making a backup of a partition of flashing a partition, either way with 3.x ports the image can get corrupted.

AsItLies said:
Don't use a usb 3.0 port when using qfil. You have to use a usb 2.0 port. Qfil is old software and was not designed for the higher speeds.
This is important whether making a backup of a partition of flashing a partition, either way with 3.x ports the image can get corrupted.
Click to expand...
Click to collapse
I put it in a usb 2.0 port and it was the same, this file does not seem to be compatible
Is there anything else I can do to save the device?

vini14zimm said:
I put it in a usb 2.0 port and it was the same, this file does not seem to be compatible
Is there anything else I can do to save the device?
View attachment 5664851
Click to expand...
Click to collapse
I'd suggest joining the tele group for that rom and asking there if anyone can give you the version of the boot partition you need.

AsItLies said:
I'd suggest joining the tele group for that rom and asking there if anyone can give you the version of the boot partition you need.
Click to expand...
Click to collapse
kinda had the same problem lol on 2023... anyways tried to fix it the way of netmsm, deleting all partitions, hard bricked i could say, kinda worked, but as far as i could do, it went to fastboot loop, to LG Bootlloooping lol, any recommendations