Database Develop

Flashing twrp on stock v20i

So I came from a stock lollipop Tmobile h811 non rooted
To stock MM v20i.
Ive tried flashing twrp 3.0 for cm13, and no matter what,
I get failed: (remote unknown command at the end after it sends recovery.
Its already unlocked(bootloader)
Thanks.

[email protected] said:
So I came from a stock lollipop Tmobile h811 non rooted
To stock MM v20i.
Ive tried flashing twrp 3.0 for cm13, and no matter what,
I get failed: (remote unknown command at the end after it sends recovery.
Its already unlocked(bootloader)
Thanks.
Click to expand...
Click to collapse
Type: fastboot boot (path goes here)
You can drag and drop the twrp img into the command window. This will ensure you have the correct path

[email protected] said:
So I came from a stock lollipop Tmobile h811 non rooted
To stock MM v20i.
Ive tried flashing twrp 3.0 for cm13, and no matter what,
I get failed: (remote unknown command at the end after it sends recovery.
Its already unlocked(bootloader)
Thanks.
Click to expand...
Click to collapse
Follow this instruction
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227

mingkee said:
Follow this instruction
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
Click to expand...
Click to collapse
That link doesn't really solve the OP's issue. I have the same issue. BUT - your link did show me that I can BOOT the .img file, I can't flash the .img file. I've verified the bootloader is unlocked by the fastboot getvar command.
I'm not sure what to do next. Installing OpenGapps causes a boot loop and the only thing I can do at this point is a factory reset with the OEM recovery since in the boot loop adb is unresponsive.

joesee said:
That link doesn't really solve the OP's issue. I have the same issue. BUT - your link did show me that I can BOOT the .img file, I can't flash the .img file. I've verified the bootloader is unlocked by the fastboot getvar command.
I'm not sure what to do next. Installing OpenGapps causes a boot loop and the only thing I can do at this point is a factory reset with the OEM recovery since in the boot loop adb is unresponsive.
Click to expand...
Click to collapse
The instruction shows how to flash recovery.img with TWRP though I have no clue how to do it.

I got that error the first time I did it, it was because of a misspelling of the command.

If you already unlocked the bootloader, while in fastboot, you only type "fastboot boot" + "path to twrp img on computer" OR instead of typing out the path, you may drag and drop the file into the command window.
Once it boots to twrp, flash twrp from within the booted img. That ensures you have permanent twrp.
If you were able to unlock your bootloader, the only thing stopping you from loading twrp is improper spelling and path to the img. Almost every error I have seen is from not following the directions.

Vseprz said:
If you already unlocked the bootloader, while in fastboot, you only type "fastboot boot" + "path to twrp img on computer" OR instead of typing out the path, you may drag and drop the file into the command window.
Once it boots to twrp, flash twrp from within the booted img. That ensures you have permanent twrp.
If you were able to unlock your bootloader, the only thing stopping you from loading twrp is improper spelling and path to the img. Almost every error I have seen is from not following the directions.
Click to expand...
Click to collapse
OK, just so I understand correctly, the proper sequence of events is to use fastboot to boot TWRP (which I can do) then, once in TWRP, I can then flash the twrp .zip file, right? Does anyone know if the LG's bootloader overwrites the recovery partition upon boot (in other words, do I have to boot straight to recovery after I flash to ensure it sticks?)
Sorry for the obtuse questions, I've got a lot of experience with Samsung flashing back in the KK and LP days, but not MM.
Thanks in advance!!

joesee said:
OK, just so I understand correctly, the proper sequence of events is to use fastboot to boot TWRP (which I can do) then, once in TWRP, I can then flash the twrp .zip file, right? Does anyone know if the LG's bootloader overwrites the recovery partition upon boot (in other words, do I have to boot straight to recovery after I flash to ensure it sticks?)
Sorry for the obtuse questions, I've got a lot of experience with Samsung flashing back in the KK and LP days, but not MM.
Thanks in advance!!
Click to expand...
Click to collapse
So you have flashed 20i which overwrites twrp with the stock recovery.
You then go through the steps for unlocking the boot loader.
After the boot loader is unlocked, you may boot into twrp with the fastboot boot command.
When that boots into twrp, flash twrp from within that to have it stick.

Have a question and maybe someone can help. Me getting carried away installed twrp from external partition. Now i cannot boot into recovery. Tried flashing using flashify and twrp manager. but flashify does not install after reboot and there is no option for h811 in twrp manager. Anyway to fix this?
Sent from my LG-H811 using Tapatalk

Vseprz said:
So you have flashed 20i which overwrites twrp with the stock recovery.
You then go through the steps for unlocking the boot loader.
After the boot loader is unlocked, you may boot into twrp with the fastboot boot command.
When that boots into twrp, flash twrp from within that to have it stick.
Click to expand...
Click to collapse
Yes, that's exactly the steps I do. I've flashed 20i. I used fastboot to boot into twrp. I then "install" the twrp zip file. Says it flashes with no issues. I then reboot the phone. Still has stock recovery.
I've confirmed my bootloader is unlocked with the fastboot getvar all. I've also tried all three versions of twrp available (.1, .2 and .3) and still doesn't work. Yet twrp works fine if I boot it.

joesee said:
Yes, that's exactly the steps I do. I've flashed 20i. I used fastboot to boot into twrp. I then "install" the twrp zip file. Says it flashes with no issues. I then reboot the phone. Still has stock recovery.
I've confirmed my bootloader is unlocked with the fastboot getvar all. I've also tried all three versions of twrp available (.1, .2 and .3) and still doesn't work. Yet twrp works fine if I boot it.
Click to expand...
Click to collapse
How did you confirm you have stock recovery? Did you use adb reboot recovery? Or did you use hardware keys to boot to it? Because if you use hardware keys you still get the initial confirm factory reset. You just have to accept then it boots to twrp.
---------- Post added at 10:44 AM ---------- Previous post was at 10:22 AM ----------
99problemz said:
Have a question and maybe someone can help. Me getting carried away installed twrp from external partition. Now i cannot boot into recovery. Tried flashing using flashify and twrp manager. but flashify does not install after reboot and there is no option for h811 in twrp manager. Anyway to fix this?
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
If boot loader is unlocked you should load twrp from fastboot.

Vseprz said:
How did you confirm you have stock recovery? Did you use adb reboot recovery? Or did you use hardware keys to boot to it? Because if you use hardware keys you still get the initial confirm factory reset. You just have to accept then it boots to twrp.
---------- Post added at 10:44 AM ---------- Previous post was at 10:22 AM ----------
If boot loader is unlocked you should load twrp from fastboot.
Click to expand...
Click to collapse
Hahaha now that's funny!! I bet I've been through 50 blog posts on various sites to try to figure this out. Having successfully installed Viper I didn't want to take the chance and pass that confirm wipe factory question.
I feel like a complete tool. Seriously, thank you for taking the time to respond to me!

joesee said:
Hahaha now that's funny!! I bet I've been through 50 blog posts on various sites to try to figure this out. Having successfully installed Viper I didn't want to take the chance and pass that confirm wipe factory question.
I feel like a complete tool. Seriously, thank you for taking the time to respond to me!
Click to expand...
Click to collapse
I'm glad it all worked out! :good:

finding I have to re-flash with flashify each time
using twrp-2.8.7.1, I get only the first reboot from there with hardware keys letting me into twrp after accepting the first factory reset prompt and denying the second. After that cant do it again unless I re-flash. Same thing happens if I flash it from within twrp. Can use terminal, su, boot recovery and I am in., or ADB/fatsboot Primarily worried about a soft brick condition. H-811, v1 20i stock, unlocked bootloader and rooted. DE-bloated,
Any Ideas, Thanks

jdoebean said:
using twrp-2.8.7.1, I get only the first reboot from there with hardware keys letting me into twrp after accepting the first factory reset prompt and denying the second. After that cant do it again unless I re-flash. Same thing happens if I flash it from within twrp. Can use terminal, su, boot recovery and I am in., or ADB/fatsboot Primarily worried about a soft brick condition. H-811, v1 20i stock, unlocked bootloader and rooted. DE-bloated,
Any Ideas, Thanks
Click to expand...
Click to collapse
You drop the twrp file
In fastboot folder open command prompt and flash twrp first just rename it simply to recovery.img while in the fastboot folder
Type fastboot flash recovery recovery.img
Or just fastboot flash recovery.img
Then it should boot you into twrp
Once booting into twrp flash the supersu zip in your internal sd
Once you have root and reboot all you have to do is use flashify app and download twrp from the app and flash it Twrp sticks from there.
Sent from my LGMS631 using XDA Free mobile app

Unlocking Bootloader from Flashboot?

I was flashing the new OTA from adb, and it failed at 70%.
Stock image, locked bootloader, not TWRP, not rooted
Now on bootup, I see nothing but the google logo.
I can reboot to bootloader/recovery mode, but can't flash anything since I hadn't unlocked the bootloader. Any way to proceed? Can I flash another bootloader that will let me unlock from fastboot?

Bootloader can only be unlocked after allowing it in the developers options. Perhaps you can boot into TWRP from the bootloader, fastboot boot xxx. Where xxx is the name of the TWRP IMG. You may be able to side load the OTA that way and flash it. I'm not 100% sure of that though.

Larzzzz82 said:
Bootloader can only be unlocked after allowing it in the developers options. Perhaps you can boot into TWRP from the bootloader, fastboot boot xxx. Where xxx is the name of the TWRP IMG. You may be able to side load the OTA that way and flash it. I'm not 100% sure of that though.
Click to expand...
Click to collapse
How do I push TWRP to the device? I can't flash recovery (it's still stock).

You don't. If you've got fastboot working, just type, fastboot boot (the name of the TWRP IMG) and it should boot on the device.
Sent from my Nexus 6 using Tapatalk

Larzzzz82 said:
You don't. If you've got fastboot working, just type, fastboot boot (the name of the TWRP IMG) and it should boot on the device.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I was getting errors when trying to boot from the twrp image. But I figured out that I can boot to recovery, select update from adb, and get adb running again.
I was able to reflash the OTA, looks like it's working now.
I guess the lesson for today is that I should just leave the bootloader unlocked.
Thanks for the help

Excellent!
Sent from my Nexus 6 using Tapatalk

Javi_in_1080p said:
I was errors when trying to boot from the twrp image. But I figured out that I can boot to recovery, select update from adb, and get adb running again.
I was able to reflash the OTA, looks like it's working now.
I guess the lesson for today is that I should just leave the bootloader unlocked.
Thanks for the help
Click to expand...
Click to collapse
That's the 1st commandment! Leave the bootloader unlocked.
Sent from my Pixel XL using Tapatalk

No recovery, no boot partition and a non-booting OOS.. HELP PLEASE

I somehow managed to have a non-booting OS, no Recovery and no boot partition..
ADB doesn't recognise my OP3T, fastboot does. Installing the driver doesn't make any difference, but I don't know if it is the correct one, because i obviously can't install drivers without OOS booting..
There is a OOS Zip located in the Download Folder, but I don''t know the name of the folder and the path to it..
Can someone help me? I'm really frustrated and I don't know what to do..

rEApEr_TGB said:
ADB doesn't recognise my OP3T, fastboot does.
Click to expand...
Click to collapse
This is normal and expected. adb only works when the phone is booted to OS; or alternately to custom recovery TWRP. Neither of which you are able to do. Only fastboot command will work in bootloader-fastboot mode.
It's not clear whether you are running stock, or with mods (unlocked bootloader, TWRP, etc.). But in either case, fastboot is the most useful for recovering from the current condition.
If stock, use fastboot to flash a stock recovery image.
If modified (unlocked bootloader) then use fastboot to flash TWRP. You can then use TWRP to flash a ROM, copy files to storage, use adb commands, etc.

redpoint73 said:
This is normal and expected. adb only works when the phone is booted to OS; or alternately to custom recovery TWRP. Neither of which you are able to do. Only fastboot command will work in bootloader-fastboot mode.
It's not clear whether you are running stock, or with mods (unlocked bootloader, TWRP, etc.). But in either case, fastboot is the most useful for recovering from the current condition.
If stock, use fastboot to flash a stock recovery image.
If modified (unlocked bootloader) then use fastboot to flash TWRP. You can then use TWRP to flash a ROM, copy files to storage, use adb commands, etc.
Click to expand...
Click to collapse
Omg thanks, I managed to get TWRP installed, now I'm going to flash the rest ;D

rEApEr_TGB said:
Omg thanks
Click to expand...
Click to collapse
There's a button for that.
You're quite welcome, and glad it worked out for you!

Not sure if you ended up finding a fix but try this:
https://www.google.com/amp/www.andr...-3-3t-5-mega-unbrick-guide-twrp-flashing/amp/

Help! I really screwed up...

It all started when I tried to temporarily boot into the TWRP img file. It didn't work so I tried flashing the file to boot_a. Then I installed TWRP through the installer (stupidly didn't wipe the caches) and... Well. When I try to boot into System through TWRP, it gets COMPLETELY stuck at the powered by Android logo screen. No amount or combination of button holding will shut it off and I actually had to let the battery (thank you SO MUCH for non-removable batteries by the way, smartphone manufacturers >_>) drain before it would actually boot again. Rebooting it into Download mode will get it stuck in there too where every time I hold the power button and shut it off, it will just reboot right back into Download mode again. And now, here's probably the worst part. I CAN'T UNLOCK the critical partition to flash when in Download mode, so I can't use the OST tool! When I try to unlock it, it just complains that flashing unlock is not allowed even though the rest of the bootloader is completely unlocked.
TL;DR - When I power the phone up it goes straight into TWRP. Booting to System totally freezes it and the Bootloader puts it in a loop when I try to power it off. Critical partition is locked for some reason. I CAN get around the bootloader loop though and get back to TWRP by switching active slots and rebooting.

Did you flash the TWRP installer to your active boot partition or your inactive one? If you flashed it to the active one, you can't get into system anymore because TWRP is your boot partition.
If you are on Oreo, and you flashed to the inactive slot, and then patched the active slot, you have to reboot into the active slot recovery and flash the Magisk installer to disable verification of the partitions.
If you can get into the bootloader, and you still have the unlock key from nokia, do fastboot flash unlock <unlock.key>, and then fastboot oem unlock_critical. Then you should be able to flash using OST.

THMSP said:
do fastboot flash unlock <unlock.key>, and then fastboot oem unlock_critical. Then you should be able to flash using OST.
Click to expand...
Click to collapse
This unlocked it! Thank you! <3
I also did have an issue with the OST tool complaining that the updater was out of date, but changing the .mlf file and leaving it unpacked when I opened it in OST seemed to make it work perfectly. My phone is now booting just fine and back to stock!
Now I just need to solve the original problem I had. How can I install TWRP to recovery since the img file wouldn't temporarily boot last time?
EDIT: Apparently unlocking the critical partition seemed to solve the problem of the TWRP image file not temporarily booting as well!

S5Guy said:
EDIT: Apparently unlocking the critical partition seemed to solve the problem of the TWRP image file not temporarily booting as well!
Click to expand...
Click to collapse
No, thats because you flashed back the May firmware, where fastboot boot was still working properly. It only broke after the august update. If you want TWRP on newer security patch versions, you can get it here: https://bit.ly/nokia-nb1 in the folder "Boot Images". Those images are prepatched, you can safely flash them to your active boot partition. It also contains stock images for restoring before updating.

THMSP said:
No, thats because you flashed back the May firmware, where fastboot boot was still working properly. It only broke after the august update. If you want TWRP on newer security patch versions, you can get it here: https://bit.ly/nokia-nb1 in the folder "Boot Images". Those images are prepatched, you can safely flash them to your active boot partition. It also contains stock images for restoring before updating.
Click to expand...
Click to collapse
Yeah looks like you're right. Letting it update back to Android 9 deleted TWRP and made fastboot boot for TWRP nonfunctional again.
Wait, so can I use that TWRP boot image you specified to boot temporarily to TWRP and then run the installer zip? Or will that not work and I'll have to flash the img directly from the bootloader?

S5Guy said:
Wait, so can I use that TWRP boot image you specified to boot temporarily to TWRP and then run the installer zip? Or will that not work and I'll have to flash the img directly from the bootloader?
Click to expand...
Click to collapse
You have to flash it directly to your boot partition. fastboot boot will work for nothing (and even if it worked those images would just send you directly into the system)

THMSP said:
No, thats because you flashed back the May firmware, where fastboot boot was still working properly. It only broke after the august update. If you want TWRP on newer security patch versions, you can get it here: https://bit.ly/nokia-nb1 in the folder "Boot Images". Those images are prepatched, you can safely flash them to your active boot partition. It also contains stock images for restoring before updating.
Click to expand...
Click to collapse
Alright! fastboot flash boot_a (TWRP image) worked! Thank you so much for all the help. <333

moto x4 softbricket wih motorola smart tools

After using the motorola smart tools and trying to flash the smartfone
the device only starts up to the bootloader
the bootloader is locked
I'm not in the recovery mode he always jumps back to the boot loader.
if I connect the device to the pc then it starts without turning up in the boot loader.
is there still a solution, or do i have a new paperweight

tomtom_38 said:
After using the motorola smart tools and trying to flash the smartfone
the device only starts up to the bootloader
the bootloader is locked
I'm not in the recovery mode he always jumps back to the boot loader.
if I connect the device to the pc then it starts without turning up in the boot loader.
is there still a solution, or do i have a new paperweight
Click to expand...
Click to collapse
Did you try blank flash yet?

Forget everything, and try to manually boot into TWRP.
Download TWRP for payton from the TWRP site (Img and Zip files for V3.2). Download and install Minimal ADB, Copy TWRP img file into the ADB install directory, put your phone into bootloader mode, connect to PC and run "fastboot boot twrp-3.2.3-1-payton.img" on the ADB commandline. The phone will boot into TWRP. You'll have to mount the storage and copy the TWRP .zip file into your phone and flash that from TWRP. Now you got TWRP flashed as the recovery.
Now it's a matter of flashing a ROM. I'm not really sure about stock firmware because i haven't flashed them before, but if you want to flash a custom ROM, make sure you flash TWRP after flashing the ROM without rebooting into system or recovery.
PS: I assumed you know how to do this with this explanation. Let me know if you need more instructions.

the bootloader is locked and I cant unlock them
because oem unlock option is not activ
the last time my pattern was requested, nevertheless
I havent access to twrp. it was blocked
is there another option?

tomtom_38 said:
the bootloader is locked and I cant unlock them
because oem unlock option is not activ
the last time my pattern was requested, nevertheless
I havent access to twrp. it was blocked
is there another option?
Click to expand...
Click to collapse
Do you try to get the unlock code on Moto website to unlock bootloader?
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a

yes the problem ist that you have to switch on the oem bootloader option in the dev menü, but I cant do that anymore