Develop Bugs

Help needed ! stuck in Bootloop

Hey guys. Today I tried rooting for the first time using this guide
In the third step of the article "3.Flashing TWRP and Rooting via TWRP" I pressed cancel when it asks for an encryption password(I hadn't put one yet). I also flashed the english TWRP( Recovery file) and not the one provided in the article . Now the phone just wont boot. Whenever I try to boot it, it gives me the error message:
"Your device has been unlocked and cannot be trusted.
ID: N/A"
And TWRP comes up everytime .
When i try booting from factory it shows:
"Your device has been unlocked and cannot be trusted.
ID: bad key"
and TWRP comes up.
The phone is still recognized in adb.I still haven't flashed SuperSU if that helps.
Should i Flash stock recovery and try again ?
Please send help, guys.

porthumor said:
Hey guys. Today I tried boot for the first time using this guide
In the third step of the article "3.Flashing TWRP and Rooting via TWRP" I pressed cancel when it asks for a password. I also flashed the english TWRP( Recovery file) and not the one provided in the article . Now the phone just wont boot. Whenever I try to boot it, it gives me the error message:
"Your device has been unlocked and cannot be trusted.
ID: N/A"
And TWRP comes up everytime .
When i try booting from factory it shows:
"Your device has been unlocked and cannot be trusted.
ID: bad key"
and TWRP comes up.
The phone is still recognized in adb.I still haven't flashed SuperSU if that helps.
Should i Flash stock recovery and try again ?
Please send help, guys.
Click to expand...
Click to collapse
I have similar problem like yours. The solution to boot your drvice. If your in twrp go to advance - reboot - bootloader. And in bootloader menu click start. And your phone now is booted
This is a alternative solution. But it wont damage your device. Trust me

Kap_Tutan said:
I have similar problem like yours. The solution to boot your drvice. If your in twrp go to advance - reboot - bootloader. And in bootloader menu click start. And your phone now is booted
This is a alternative solution. But it wont damage your device. Trust me
Click to expand...
Click to collapse
Tried this . It displays :
"Your device has been unlocked and cannot be trusted.
ID: bad key"
Reboots to show :
"Your device has been unlocked and cannot be trusted.
ID: N/A"
and goes into TWRP .

I think you need to flash new logo bin from here
https://forum.xda-developers.com/moto-z-play/themes/logo-bin-t3538153

mijing said:
I think you need to flash new logo bin from here
https://forum.xda-developers.com/moto-z-play/themes/logo-bin-t3538153
Click to expand...
Click to collapse
How will flashing a new logo help me get out of boot loop ? AFAIK it only replaces the warning.

porthumor said:
How will flashing a new logo help me get out of boot loop ? AFAIK it only replaces the warning.
Click to expand...
Click to collapse
I am not sure but
Yes
If showing "Your device has been unlocked and cannot be trusted"
I fix my device flashing new logo bin .

mijing said:
I am not sure but
Yes
If showing "Your device has been unlocked and cannot be trusted"
I fix my device flashing new logo bin .
Click to expand...
Click to collapse
Well thank you for the tip but that's not the problem here.The problem is that my phone never boots into OS ,it is stuck in recovery.Any Indication as to why would be a huge help !

porthumor said:
Well thank you for the tip but that's not the problem here.The problem is that my phone never boots into OS ,it is stuck in recovery.Any Indication as to why would be a huge help !
Click to expand...
Click to collapse
Are you sure OS is even there?

flashallthetime said:
Are you sure OS is even there?
Click to expand...
Click to collapse
I don't think I messed with the OS . I just unlocked the bootloader and flashed TWRP without flashing SuperSU.(done it for the first time for my Moto Z play). Used Wipe to clear davlik,cache and that's it.haven't done anything in the recovery since then.
The only thing i remember messing up was to not input the encryption key when it prompt me for it by clicking cancel.
I've read in some forums that it doesn't boot if it doesn't have SuperSU flashed,but I'm not sure if it's safe since i don't exactly know what might or might now permanently brick my phone.
Also some forums had something to do with patching the kernels (don't know if that's what you call it) but i don't know if it's a safe thing to do since it might also permanently brick my phone.
Running Nougat April Security Patch.

porthumor said:
I don't think I messed with the OS . I just unlocked the bootloader and flashed TWRP without flashing SuperSU.(done it for the first time for my Moto Z play). Used Wipe to clear davlik,cache and that's it.haven't done anything in the recovery since then.
The only thing i remember messing up was to not input the encryption key when it prompt me for it by clicking cancel.
I've read in some forums that it doesn't boot if it doesn't have SuperSU flashed,but I'm not sure if it's safe since i don't exactly know what might or might now permanently brick my phone.
Also some forums had something to do with patching the kernels (don't know if that's what you call it) but i don't know if it's a safe thing to do since it might also permanently brick my phone.
Running Nougat April Security Patch.
Click to expand...
Click to collapse
You used the Chinese TWRP originally? Now you have alberto97 TWRP? Is this correct?
I would flash a custom ROM, why I'm saying that is it's far safer flashing a zip ROM than trying to flash the stock firmware.
Again I will remind people the flashing bootloaders on moto devices will inevitably cause hard bricks if you downgrade and the accept an ota.
---------- Post added at 06:47 PM ---------- Previous post was at 06:39 PM ----------
The only solution and this applies only if you want to remain on the stock ROM.
Download the retail firmware and only manually flash the boot.img, the 10 sparsechunks and the OEM.img.
Do not use rsdlite!!
This should boot your phone.

flashallthetime said:
You used the Chinese TWRP originally? Now you have alberto97 TWRP? Is this correct?
Click to expand...
Click to collapse
Yes,exactly.
flashallthetime said:
I would flash a custom ROM, why I'm saying that is it's far safer flashing a zip ROM than trying to flash the stock firmware.
Click to expand...
Click to collapse
Which Custom ROM do you think is the safest possible alternative?
flashallthetime said:
Again I will remind people the flashing bootloaders on moto devices will inevitably cause hard bricks if you downgrade and the accept an ota.
Click to expand...
Click to collapse
Can you explain this a bit better ? I would like to understand what i'm getting into !
flashallthetime said:
The only solution and this applies only if you want to remain on the stock ROM.
Download the retail firmware and only manually flash the boot.img, the 10 sparsechunks and the OEM.img.
Do not use rsdlite!!
This should boot your phone.
Click to expand...
Click to collapse
Could you,if possible, link to me to the respective article ? Do I need to Get the firmware for Nougat or does it depend on security patch as well?
Gotcha,No rsdlite !

porthumor said:
Yes,exactly.
Which Custom ROM do you think is the safest possible alternative?
Can you explain this a bit better ? I would like to understand what i'm getting into !
Could you,if possible, link to me to the respective article ? Do I need to Get the firmware for Nougat or does it depend on security patch as well?
Gotcha,No rsdlite !
Click to expand...
Click to collapse
I would install the aosp ROM as it is bare bones android.
As for bootloaders, when you receive an ota it flashes a new bootloader.
What some folks have done is because they feel like a new ota isn't working to their liking, they have downgraded their firmare, either by flashing the firmware package that can be downloaded. They flash the entire package including bootloader, what this does is set up a perfect hard brick scenerio for moto devices.
They accept an ota or for reasons that are beyond uderstanding, sideload the package and bam as soon as they restart there device it bricks their device due to the mismatched bootloaders.
You are unlocked and the easiest way to prevent hard bricks is to for go flashing firmware.
I'm running validus 7.1.2 on the original bootloader that was installed on MM.
---------- Post added at 07:19 PM ---------- Previous post was at 07:17 PM ----------
I'm attempting to build a stock flashable TWRP stock 7.1.1 ROM.
You may also flash any flashable TWRP stock 7 rom, either bye me or dedracks

flashallthetime said:
I would install the aosp ROM as it is bare bones android.
As for bootloaders, when you receive an ota it flashes a new bootloader.
What some folks have done is because they feel like a new ota isn't working to their liking, they have downgraded their firmare, either by flashing the firmware package that can be downloaded. They flash the entire package including bootloader, what this does is set up a perfect hard brick scenerio for moto devices.
They accept an ota or for reasons that are beyond uderstanding, sideload the package and bam as soon as they restart there device it bricks their device due to the mismatched bootloaders.
You are unlocked and the easiest way to prevent hard bricks is to for go flashing firmware.
I'm running validus 7.1.2 on the original bootloader that was installed on MM.
---------- Post added at 07:19 PM ---------- Previous post was at 07:17 PM ----------
I'm attempting to build a stock flashable TWRP stock 7.1.1 ROM.
You may also flash any flashable TWRP stock 7 rom, either bye me or dedracks
Click to expand...
Click to collapse
Is it fine if i go ahead with this and see if it works ?
I will try to flash a custom ROM if it doesn't.

porthumor said:
Is it fine if i go ahead with this and see if it works ?
I will try to flash a custom ROM if it doesn't.
Click to expand...
Click to collapse
That's fine and it's my ROM lol.
You may want to format your data but first try to flash the ROM and see if it boots.
That Chinese TWRP is a nasty thing

porthumor said:
How will flashing a new logo help me get out of boot loop ? AFAIK it only replaces the warning.
Click to expand...
Click to collapse
Bro are you sure you followed my instruction? In twrp menu click on reboot>bootloader
Then it will boot the device in bootloader mode. And in the bootloader menu click on "start" using the power button. Then it will boot your phone. Everytime you reboot your phone do the same step. If you want to get rid of that thing you need to flash official rom via rsd lite

Kap_Tutan said:
Bro are you sure you followed my instruction? In twrp menu click on reboot>bootloader
Then it will boot the device in bootloader mode. And in the bootloader menu click on "start" using the power button. Then it will boot your phone. Everytime you reboot your phone do the same step. If you want to get rid of that thing you need to flash official rom via rsd lite
Click to expand...
Click to collapse
Rsdlite sucks, never flash any firmware with resdlite unless you know which lines need to be removed from the text file that tells rsdlite what to flash.
manually flashing firmware is IMO much safer and all you need to flash is the boot.img all the spareschunks and oem.img

Kap_Tutan said:
Bro are you sure you followed my instruction? In twrp menu click on reboot>bootloader
Then it will boot the device in bootloader mode. And in the bootloader menu click on "start" using the power button. Then it will boot your phone. Everytime you reboot your phone do the same step. If you want to get rid of that thing you need to flash official rom via rsd lite
Click to expand...
Click to collapse
I did what you had asked me to ,unfortunately it doesn't work. I would be happy just being able to boot using the above method.
Thanks for the suggestion tho !
flashallthetime said:
That's fine and it's my ROM lol.
You may want to format your data but first try to flash the ROM and see if it boots.
That Chinese TWRP is a nasty thing
Click to expand...
Click to collapse
I'll try to get this done by tomorrow and see if it helps !

porthumor said:
I did what you had asked me to ,unfortunately it doesn't work. I would be happy just being able to boot using the above method.
Thanks for the suggestion tho !
I'll try to get this done by tomorrow and see if it helps !
Click to expand...
Click to collapse
Hopefully it does

flashallthetime said:
Rsdlite sucks, never flash any firmware with resdlite unless you know which lines need to be removed from the text file that tells rsdlite what to flash.
manually flashing firmware is IMO much safer and all you need to flash is the boot.img all the spareschunks and oem.img
Click to expand...
Click to collapse
When flashing the boot the sparsechunk and the oem then can i able to receive a OTA in my device? Or do i need to flash the recovery.img also?
Anyways thanks bro i learned again something from you

Kap_Tutan said:
When flashing the boot the sparsechunk and the oem then can i able to receive a OTA in my device? Or do i need to flash the recovery.img also?
Anyways thanks bro i learned again something from you
Click to expand...
Click to collapse
You also need to flash the recovery image as well

[RECOVERY] Unofficial build of TWRP by wzsx150

wzsx150's TWRP was released but I didn't see a thread here, so here's recovery that everyone would flash.
MEGA mirror: https://mega.nz/#F!g4NX3QQD!mU5-gR9Eu4A8YSR9jEu5PQ
DISCLAIMER:
This is build for the CN variant of ROG Phone 2, I don't know if it works on other variants, but it's possible to restore the official recovery back to your phone.
Current version is 3.3.1-1004.
Original post on https://weibo.com/6033736159/I9XKmocRd

I am on latest ww rom, and it boots to twrp, then instantly reboots to stock recovery.
Nevermind, jut did a backup!!!!!!!!!!!!!!

How do we flash this?

Cammarratta said:
How do we flash this?
Click to expand...
Click to collapse
Fastboot flash boot recovery.img

suzook said:
Fastboot flash boot recovery.img
Click to expand...
Click to collapse
The whole process requires ROM's boot.img to participate and I think recovery-TWRP-3.3.1-1004-ASUS_ROG2-CN-wzsx150.img-tmp isn't a complete file, so you shouldn't just flash that directly to your phone. I wish I know how to decrypt the batch file and localize it in English so non Chinese speakers would use it too. I'll make a simple guide if the original developer doesn't make a English one.
FYI: The current build of this TWRP only has Simplified Chinese and English language, also has a modified splash image with author's info on it.

zestybaby said:
The whole process requires ROM's boot.img to participate and I think recovery-TWRP-3.3.1-1004-ASUS_ROG2-CN-wzsx150.img-tmp isn't a complete file, so you shouldn't just flash that directly to your phone. I wish I know how to decrypt the batch file and localize it in English so non Chinese speakers would use it too. I'll make a simple guide if the original developer doesn't make a English one.
FYI: The current build of this TWRP only has Simplified Chinese and English language, also has a modified splash image with author's info on it.
Click to expand...
Click to collapse
Rename the file...delete the -tmp. That should be self explanatory, and the 1st screen that pops up when twrp boot. CLEARLY has a language button. press it, select english. Simple. The Author of this, has been around forever.

suzook said:
I am on latest ww rom, and it boots to twrp, then instantly reboots to stock recovery.
Nevermind, jut did a backup!!!!!!!!!!!!!!
Click to expand...
Click to collapse
So does it work on ww?

is there a way to fix touch input not working on twrp?

Cammarratta said:
is there a way to fix touch input not working on twrp?
Click to expand...
Click to collapse
Working fine here

Cammarratta said:
is there a way to fix touch input not working on twrp?
Click to expand...
Click to collapse
So i had to reflash and now my touch isnt working. You gets yours working?

Yeah. I reflashed and made sure there was no lock screen set or fingerprint and now it's working. Makes updating Roma really easy since since I'm in the latest we rom.

Cammarratta said:
Yeah. I reflashed and made sure there was no lock screen set or fingerprint and now it's working. Makes updating Roma really easy since since I'm in the latest we rom.
Click to expand...
Click to collapse
So I've bought the tencent version CN, which will arrive soon but with WW rom flashed on it. So I can just download latest WW update and flash the zip through TWRP, correct?

Yes. If you have this twrp you can flash and it'll update it.

Can I just check, with ROG phone II we don't use 'fastboot flash recovery recovery.img' , we instead use 'Fastboot flash boot recovery.img' to flash this twrp? Sorry, but I'm used to the fastboot flash recovery, so just wanted to make sure... Thanks
It's just that @suzook said it needs to be 'fastboot flash boot recovery.img'
Oh yes, and also, I'm guessing BL must be unlocked to flash this recovery?
EDIT: Nevermind about the flashing process, I see there is no seperate recovery partition to flash and the twrp img is the same size as the extracted rom boot img, so yes, it should be as @suzook mentioned.
I'd still like to confirm that flashing twrp MUST have BL unlocked, or not?

@reg66 I suggest you use this method first https://forum.xda-developers.com/rog-phone-2/how-to/flashing-ww-rom-changing-cn-fingerprint-t3969765

reg66 said:
Can I just check, with ROG phone II we don't use 'fastboot flash recovery recovery.img' , we instead use 'Fastboot flash boot recovery.img' to flash this twrp? Sorry, but I'm used to the fastboot flash recovery, so just wanted to make sure... Thanks
It's just that @suzook said it needs to be 'fastboot flash boot recovery.img'
Oh yes, and also, I'm guessing BL must be unlocked to flash this recovery?
EDIT: Nevermind about the flashing process, I see there is no seperate recovery partition to flash and the twrp img is the same size as the extracted rom boot img, so yes, it should be as @suzook mentioned.
I'd still like to confirm that flashing twrp MUST have BL unlocked, or not?
Click to expand...
Click to collapse
Bl absolutely needs to be unlocked, otherwise the recovery won't flash.

ermacwins said:
@reg66 I suggest you use this method first https://forum.xda-developers.com/rog-phone-2/how-to/flashing-ww-rom-changing-cn-fingerprint-t3969765
Click to expand...
Click to collapse
Yep, no worries, I'll use that apk to unlock BL, but is the rest of it necessary? My phone will already have FP changed to WW by seller (Giztop)..

reg66 said:
Yep, no worries, I'll use that apk to unlock BL, but is the rest of it necessary? My phone will already have FP changed to WW by seller (Giztop)..
Click to expand...
Click to collapse
My opinion? Bl unlock, completely reflash the ww rom yourself, this way your fresh, and know it's done properly.

Now we need custom roms ??

This recovery installs OK for me on my CN phone converted to WW rom, but if I use the TWRP "Root Phone" option in Advanced to root and install Magisk, it disables the Wifi, and after rebooting the phone it goes into a bootloop that I can't recover from (not even restoring from TWRP backup) and I have to reflash WW rom to recover. I repeated this refleash/reroot process 3 or 4 times and it happened every time with breaking wifi and then reboot failing.
So it works, but I wouldn't use the built-in rooting yet until it is ironed out.

Pre-rooted Boot Image OP7T European HD65BA 10.0.7

Hello,
I have seen few requests about providing pre-rooted boot image file for OP7T European version for firmware 10.0.6 so here you go.
Steps :
1) Reboot your phone in bootloader mode (fastboot mode).
2) Execute command fastboot boot magisk_patched.img
3) Reboot the device
4) Install Magisk Manager
5) Click on Install, then direct install and wait the end of the process
6) Reboot the device
Also attaching the stock boot file in case anything goes wrong.
P.S : I don't own European OP7T.
Link : https://www.androidfilehost.com/?w=files&flid=303273

*delete*

Can you do one for the 10.0.6 USA Version? I can't find one anywhere. Thanks so much. I can't even find a copy of the stock 10.0.6 US boot img

Worked well, got my phone rooted yesterday.
Lähetetty minun HD1903 laitteesta Tapatalkilla

click4dylan said:
Can you do one for the 10.0.6 USA Version? I can't find one anywhere. Thanks so much. I can't even find a copy of the stock 10.0.6 US boot img
Click to expand...
Click to collapse
USA version is HD65AA ? Can you send the product code and I will try

Yes, my build number is 10.0.6.HD65AA and model number is HD1905. Thank you so very much! Also, can you show me how you are getting the boot image for these new versions so I can do it myself in the future? Thanks again. SKU on the box says 5011100751

Hi!
Sorry for this question, flashing this boot image will wipe my device?
Thanks.

paulo_snower said:
Hi!
Sorry for this question, flashing this boot image will wipe my device?
Thanks.
Click to expand...
Click to collapse
NO! First time you unlock your bootloader thats wipe your device, not when flashing a boot.img

it's not working for me with Oxygen 10.0.6 HD65BA.
If i try to boot the magisk patched boot image the phone just reboot within fastboot mode, and if i try to normally boot i just can't update magisk.
-----
Update:
I found this surfing the net :
Unlike older OnePlus phones, the current bootloader of the OnePlus 7 Pro doesn’t allow ‘fastboot boot’ (also known as tethered booting) command. The situation is same as Essential PH-1 as well some other phones where you can’t temporarily boot a kernel or recovery.

nicoilboss said:
it's not working for me with Oxygen 10.0.6 HD65BA.
If i try to boot the magisk patched boot image the phone just reboot within fastboot mode, and if i try to normally boot i just can't update magisk.
-----
Update:
I found this surfing the net :
Unlike older OnePlus phones, the current bootloader of the OnePlus 7 Pro doesn’t allow ‘fastboot boot’ (also known as tethered booting) command. The situation is same as Essential PH-1 as well some other phones where you can’t temporarily boot a kernel or recovery.
Click to expand...
Click to collapse
click4dylan said:
Yes, my build number is 10.0.6.HD65AA and model number is HD1905. Thank you so very much! Also, can you show me how you are getting the boot image for these new versions so I can do it myself in the future? Thanks again. SKU on the box says 5011100751
Click to expand...
Click to collapse
zanderzone said:
USA version is HD65AA ? Can you send the product code and I will try
Click to expand...
Click to collapse
Sorry for being late. Please try this : https://forum.xda-developers.com/oneplus-7t/how-to/pre-rooted-boot-image-op7t-global-t4009305

Thanks, I found the instructions on how to do it already and took the Global boot image. I am just booting it with fastboot boot instead of flash. Just being cautious is all.

Same situation over there, trying either boot or flash the image, the phone reboots itself into bootloader. Stock 10.0.6.
Enviado desde mi HD1903 mediante Tapatalk

What is the difference between global and European? And can i still update ota after flashing this?

Hello !
Thanks for the guide !
I successfully installed Magisk, but once I install Riru core and EdXposed, my OP7T also gets stuck and boots only into fastboot. After wiping everything to factory reset, my phone is back to normal.
Is EdXposed working with this version of Magisk ?
(OpenPlus 7T HD65BA 10.0.6)
Thanks for help
Edit : problem solved with this method.

Excellent.
Many thanks @zanderzone

Can i still update ota in settings adter installing this version? Or will i loose root everytime?

karayemis said:
Can i still update ota in settings adter installing this version? Or will i loose root everytime?
Click to expand...
Click to collapse
Most likely you won't get any notifications if there are updates. You won't be able to use incremental updates.
But you can keep root flashing magisk right after the update before rebooting your phone.

could someone help me? I got the european version but if i try to boot the magisk_patched.img i just get stuck in fastboot mode and if i try to flash the patched image i get stuck in fastboot mode and i've to flash again the stock boot.
I also tried the global one but without any results.
Thanks
edit. I have the HD65BA 10.0.6 version

I was able to boot using your magisk_patched.img using "fastboot boot magisk_patched.img", but WIFI doesn't work now. I haven't inserted the SIM yet so I am unable to install magisk (it can't connect to download it). Is it only my case, or did it happen to anyone else? Any fixes?
Or is ir a temporary thing and after installing magisk it will work (WIFI)?
EDIT: with "fastboot boot Stock_boot.img" I get the same WIFI problem. Rebooting normally makes WIFI work again.
EDIT2: I tried it with the SIM on and the process was perfect. Thank you for that patched boot image and the tutorial!!!

Any chance @zanderzone that you could put a 10.0.7 version up?
I lost root with the recent update...
I found the detailed instructions too late.
Detailed instructions here: https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Many thanks

Moto g6 forge (XT1922-9) bricked

okay so i am pretty new still to flashing firmwares and using fastboot in general. I have the cricket version of the moto g6 play (forge) and noticed that i could not unlock the bootloader through moto's website . i noticed that the model number for the cricket version of the xt1922-9 was the same as the retail version from motorola . which on the website says has the ability to unlock . so i tried to flash the stock retail firmware for the retail and the most update verision being android pie XT1922-9_JETER_RETUS_9.0_PPPS29.118-68-3_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip and ended up flashing everything succesfully other than the boot.img and all of the system.img files and when i try and reboot the phone to recovery it says failed to pass validation back to fastboot . and the baseband section in fastboot now says not found . can someone help me with how i can flash all the correct files so i can get the phone just to boot up again.

You flashed everything except the boot.img and the system.img files?? That means you mixed up two FWs on one device...
Try flashing this FW for jeter_cricket from mirrors.lolinet.com
https://mirrors.lolinet.com/firmware/moto/jeter/official/Cricket/XT1922-9_JETER_A_CRICKET_9.0_PCPS29.118-63-2_cid1_subsidy-CRICKET_regulatory-DEFAULT_CFC.xml.zip

WoKoschekk said:
You flashed everything except the boot.img and the system.img files?? That means you mixed up two FWs on one device...
Try flashing this FW for jeter_cricket from mirrors.lolinet.com
Click to expand...
Click to collapse
i tried to flash that firmware and still , im only able to succefully flash everything but the system images the bootloader the recovery and the boot image.

jesheesh said:
i tried to flash that firmware and still , im only able to succefully flash everything but the system images the bootloader the recovery and the boot image.
Click to expand...
Click to collapse
What is "not successfully"? Could you explain it more detailed, please? There's always an output message in terminal

jesheesh said:
i tried to flash that firmware and still , im only able to succefully flash everything but the system images the bootloader the recovery and the boot image.
Click to expand...
Click to collapse
You could try LMSA flash rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my ali using XDA Labs

sd_shadow said:
You could try LMSA flash rescue option
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
i'll download it and try it out

jesheesh said:
i'll download it and try it out
Click to expand...
Click to collapse
I'll also go ahead and copy and paste the output for you here as well.
Sorry it takes me so long to reply . Most of my tinkering time is eaten up with my other phone I have that just so happens to be the only model variant that can't unlock its boot loader hence no root or twrp ... :/
But anyway yeah I'm gonna try the tool and paste those lines of fast boot code for you. One sec.

Dtb not found

While unlocking camera 2 api It says failed (remote:dtb not found) in fastboot boot patchedboot.img step, any idea whats wrong?I tried with latest magisk as well as with the one in the patched boot file. Bootloader is unlocked and my phone is in the latest build 11.0.4.0 stock.

Samir 120 said:
While unlocking camera 2 api It says failed (remote:dtb not found) in fastboot boot patchedboot.img step, any idea whats wrong?I tried with latest magisk as well as with the one in the patched boot file. Bootloader is unlocked and my phone is in the latest build 11.0.4.0 stock.
Click to expand...
Click to collapse
I suppose you are trying to flash the patched boot.img. If that's the case, the command is "fastboot flash boot patched_boot.img".

Neon丶 said:
I suppose you are trying to flash the patched boot.img. If that's the case, the command is "fastboot flash boot patched_boot.img".
Click to expand...
Click to collapse
Im trying to install gcam without root. It says fastboot boot patched_boot.img in every guide i have seen so far, are you sure i need to add flash? Im dont have much knowledge in these things dont want to cause problems dor my device.

Samir 120 said:
Im trying to install gcam without root. It says fastboot boot patched_boot.img in every guide i have seen so far, are you sure i need to add flash? Im dont have much knowledge in these things dont want to cause problems dor my device.
Click to expand...
Click to collapse
No, not flash. Just boot.
Sounds like you are not running the command from the folder with the patched boot file. Or the file has a different name.