Database Develop

[Q] Milestone flashing recovery issue

Ok, so bit of background here.
I installed MIUI Rom using GOT OpenRecovery.
Its very cool and I really enjoy using it. Much better (IMO) than CM7.
It got to Saturday and it said there was an OTA update to install which I couldn't work out how to install. On researching it a bit around the internet it turns out that you need to have ClockworkMod Recovery flashed in order to install OTA updates.
So I tried to install ClockworkMod Recovery. I did a few different things. Firstly I downloaded the ClockworkMod Rom Manager and chose the option in there to flash. It said "Downloaded successfully" but it didn't flash. I rebooted into recovery and tried to "Apply update.zip" but it said something about it not being signed properly and wouldn't open.
So onto the next bit. I tried to flash it using one of the many manual instructions on the internet. eg:
Code:
adb shell
# flash_image recovery /sdcard/recovery.img
and
Code:
fastboot-mac flash recovery /path/to/recovery.img
The first one seems to be quite quick and just goes to the next # line. There's no error or confirmation or anything. This one broke the stock recovery. Now when I boot into recovery there's just a bootloader screen with an error on it (Err:A5,69,35,00,2F).
The second one doesn't do anything. Well it goes onto a new line and it says "sending 'recovery' (2798 KB)..." and just stays like that indefinitely until I do Ctrl+C and cancel it. Similarly doing:
Code:
fastboot-mac erase recovery
shows: "erasing 'recovery'..." and stays at that indefinitely.
So now I'm stuck. My system works - I can boot into MIUI and use the phone normally, but I don't know how to get the recovery partition working properly.
The best thing that could happen is that I get ClockworkMod Recovery installed so that I can flash MIUI updates, but failing that I would at least like to get the stock recovery back so I can continue to use GOT OpenRecovery.
What can I do to sort this?
Thanks for any help you can give me.

tclayson said:
Ok, so bit of background here.
I installed MIUI Rom using GOT OpenRecovery.
Its very cool and I really enjoy using it. Much better (IMO) than CM7.
It got to Saturday and it said there was an OTA update to install which I couldn't work out how to install. On researching it a bit around the internet it turns out that you need to have ClockworkMod Recovery flashed in order to install OTA updates.
So I tried to install ClockworkMod Recovery. I did a few different things. Firstly I downloaded the ClockworkMod Rom Manager and chose the option in there to flash. It said "Downloaded successfully" but it didn't flash. I rebooted into recovery and tried to "Apply update.zip" but it said something about it not being signed properly and wouldn't open.
So onto the next bit. I tried to flash it using one of the many manual instructions on the internet. eg:
Code:
adb shell
# flash_image recovery /sdcard/recovery.img
and
Code:
fastboot-mac flash recovery /path/to/recovery.img
The first one seems to be quite quick and just goes to the next # line. There's no error or confirmation or anything. This one broke the stock recovery. Now when I boot into recovery there's just a bootloader screen with an error on it (Err:A5,69,35,00,2F).
The second one doesn't do anything. Well it goes onto a new line and it says "sending 'recovery' (2798 KB)..." and just stays like that indefinitely until I do Ctrl+C and cancel it. Similarly doing:
Code:
fastboot-mac erase recovery
shows: "erasing 'recovery'..." and stays at that indefinitely.
So now I'm stuck. My system works - I can boot into MIUI and use the phone normally, but I don't know how to get the recovery partition working properly.
The best thing that could happen is that I get ClockworkMod Recovery installed so that I can flash MIUI updates, but failing that I would at least like to get the stock recovery back so I can continue to use GOT OpenRecovery.
What can I do to sort this?
Thanks for any help you can give me.
Click to expand...
Click to collapse
GOT recovery? You have a Milestone then? You are on the wrong path then. Clockwork Recovery Mod doesn't work on the Milestone, nor does ROM Manager.
You need to reflash the stock sbf for your country, then flash the rootable sbf, place OpenRecovery on your SD Card, and root the phone, flash a custom ROM and reboot. Look at the tutorials in the Milestone development forum and ask here if you have any other questions.

I do have a milestone - sorry, I forgot it was the Droid AND Milestone forum.
Motorola milestone is included in the list of recovery images on the clockworkmod website (clockworkmod[dot]com/recovery_images.html). Plus when installing the ROM Manager and clicking "flash recovery" it says "Confirm phone" with "Motorola Milestone" in the options.
I'm pretty sure as well from reading around on the internet and looking at different forums and such that Clockworkmod does work on the Milestone... maybe I'm completely wrong.
Thanks

tclayson said:
I do have a milestone - sorry, I forgot it was the Droid AND Milestone forum.
Motorola milestone is included in the list of recovery images on the clockworkmod website (clockworkmod[dot]com/recovery_images.html). Plus when installing the ROM Manager and clicking "flash recovery" it says "Confirm phone" with "Motorola Milestone" in the options.
I'm pretty sure as well from reading around on the internet and looking at different forums and such that Clockworkmod does work on the Milestone... maybe I'm completely wrong.
Thanks
Click to expand...
Click to collapse
It doesn't work, even though it shows it as supported. Because the bootloader is not unlocked on the Milestone, it will cause a soft brick. You will need to follow my instructions to get your Milestone running on MIUI again. The OTA update for MIUI works for devices with CWM installed, so it doesn't really work with Milestone. You'll need to manually update MIUI when DannyDroid posts the updates.

Ah gutted, ok thank you for that. I will follow your instructions. Thanks for clearing it up for me.

Just out of interest - a quick search on google shows that it IS possible to update MIUI OTA for the Milestone... Any ideas how that works? Is there a different recovery or something?

tclayson said:
Just out of interest - a quick search on google shows that it IS possible to update MIUI OTA for the Milestone... Any ideas how that works? Is there a different recovery or something?
Click to expand...
Click to collapse
People say that ROM Manager MIGHT work on Milestone. I don't think so and I wouldn't risk it just for OTA updates, seeing as the miuiAndroid build is very basic compared to the one Danny releases. Better to just wait for his releases, a lot more worthwhile!

Ok, well thank you very much! Restored to stock and gonna keep on top of danny's releases. Thanks skadude.

Accidently selected read only in TWRP how do I undo it???

So I was following this guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684 and when it came to the step to allow modification in twrp I had already goofed up and kept it read only. How do I change this. I cannot find the setting anywhere in twrp???

CombustLemonz said:
So I was following this guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684 and when it came to the step to allow modification in twrp I had already goofed up and kept it read only. How do I change this. I cannot find the setting anywhere in twrp???
Click to expand...
Click to collapse
Reflash TWRP.
Sent from my Droid Turbo.
Resurrection Remix.
Straight Talk/Verizon.
Tapatalk.

Reflashing did not work at first so I went to reboot and selected bootloader. It loaded up TWRP again and gave me the option! We are good! Thanks!

CombustLemonz said:
Reflashing did not work at first so I went to reboot and selected bootloader. It loaded up TWRP again and gave me the option! We are good! Thanks!
Click to expand...
Click to collapse
No problem señor!
Sent from my Droid Turbo.
Resurrection Remix.
Straight Talk/Verizon.
Tapatalk.

CombustLemonz said:
Reflashing did not work at first so I went to reboot and selected bootloader. It loaded up TWRP again and gave me the option! We are good! Thanks!
Click to expand...
Click to collapse
Could you please be more specific about how you got the option to reappear. I have the exact same issue. Thanks

Not sure if this will fix it or not... but I did the same thing when I first loaded twrp, I didnt allow system mods (or whatever it said) but in recovery if you go to Mount... theres a selection "Mount system partition read-only" that had a check and I unchecked it.
I am only assuming this corrects that issue... hopefully someone can come along and confirm.

jlang11 said:
Not sure if this will fix it or not... but I did the same thing when I first loaded twrp, I didnt allow system mods (or whatever it said) but in recovery if you go to Mount... theres a selection "Mount system partition read-only" that had a check and I unchecked it.
I am only assuming this corrects that issue... hopefully someone can come along and confirm.
Click to expand...
Click to collapse
I can confirm that unchecking that option solves this. I tried to flash a ROM update once and it gave me an error saying my system partition was read only, and after unchecking that option it flashed correctly.

The reason for having to run adb flash recovery.img (the TWRP custom recovery) is because you chose the read-only mode introduced in v2.8.7.0 of TWRP. It means that the stock recovery will overwrite it if you reboot without selecting keep modifications on that first screen. Tapping on the Keep Read Only button will keep it temporary, but swiping the blue arrows to the right (like I did in the video), will install TWRP permanently. Reference: http://www.androidexplained.com/oneplus-3-install-twrp/

Latiken said:
I can confirm that unchecking that option solves this. I tried to flash a ROM update once and it gave me an error saying my system partition was read only, and after unchecking that option it flashed correctly.
Click to expand...
Click to collapse
omg thank you so much, that was driving me mental.

can anyone confirm if this works? also, if i flash a new nightly via TWRP is CM going to overwrite the TWRP recovery? or I just have to wipe the cache and the update is done?

i91004ever said:
can anyone confirm if this works? also, if i flash a new nightly via TWRP is CM going to overwrite the TWRP recovery? or I just have to wipe the cache and the update is done?
Click to expand...
Click to collapse
It will overwrite TWRP if you have the developer option checkmark to use CM Recovery. Go into Settings/Developer Options and UNcheck that box.

Hi guys i have the twrp but i flashed a rom called cm13 on my galaxy s5 sm-g900p and i want to go back to touch wiz but the restore says at the twrp
"Cannot restore Modem -- mounted read only. What should i do also the "Mount system partition read-only" box was already unchecked

Wazup20 said:
Hi guys i have the twrp but i flashed a rom called cm13 on my galaxy s5 sm-g900p and i want to go back to touch wiz but the restore says at the twrp
"Cannot restore Modem -- mounted read only. What should i do also the "Mount system partition read-only" box was already unchecked
Click to expand...
Click to collapse
You should probably ask in the Galaxy S5 help section. That SM-G900p model is for Sprint.
Sprint Galaxy S 5 Q&A, Help & Troubleshooting
http://forum.xda-developers.com/sprint-galaxy-s5/help

Latiken said:
I can confirm that unchecking that option solves this. I tried to flash a ROM update once and it gave me an error saying my system partition was read only, and after unchecking that option it flashed correctly.
Click to expand...
Click to collapse
Confirmed ! :highfive:

zefir738 said:
Reflash TWRP.
Sent from my Droid Turbo.
Resurrection Remix.
Straight Talk/Verizon.
Tapatalk.
Click to expand...
Click to collapse
how can i reflash it again? i am having trouble with swipe to modification. swipe is not working i wiped data cache dalvik and system and the backup which i created is not restoring it says system--mounted read only. now i can neither boot to old OS nor the new OS is installing in my phone. im in great trouble please could you help me.

sizzlingsuraj said:
how can i reflash it again? i am having trouble with swipe to modification. swipe is not working i wiped data cache dalvik and system and the backup which i created is not restoring it says system--mounted read only. now i can neither boot to old OS nor the new OS is installing in my phone. im in great trouble please could you help me.
Click to expand...
Click to collapse
Either
how you flashed in the first place, probably fastboot via PC?
or if it's still in your download folder, go to TWRP "install" and check install "image". Flash it TWRP (reinstall) from there, boot to bootloader and then go back to "recovery".
I use the 2nd method all the time to update to newer versions of TWRP.

ChazzMatt said:
Either
how you flashed in the first place, probably fastboot via PC?
or if it's still in your download folder, go to TWRP "install" and check install "image". Flash it TWRP (reinstall) from there, boot to bootloader and then go back to "recovery".
I use the 2nd method all the time to update to newer versions of TWRP.
Click to expand...
Click to collapse
very important to do int hese order
fastboot flash recovery twrp-3.0.3-0-hammerhead.img
fastboot reboot-bootloader
enter the twrp
:good:

ironia. said:
very important to do int hese order
fastboot flash recovery twrp-3.0.3-0-hammerhead.img
fastboot reboot-bootloader
enter the twrp
:good:
Click to expand...
Click to collapse
That's basically what I said. But for this phone, you would want QUARK TWRP recovery – not hammerhead.
Latest QUARK TWRP:
https://www.androidfilehost.com/?w=files&flid=39562
(Use most recent date.)

yes, sorry for the wrong model

Ran into the same problem.
Made my device read only at the start up of TWRP by mistake.
Then I followed the advice by unticking the "mount system partition read only" option.
That's when the menu with the question came up again.
I swiped to the right to allow system modifications.
Rebooted into my phone.
Everything working fine phonewise.
Rebooted into bootloader.
Selected recovery.
Stock Recovery appears. :/
Any idea why stock recovery is returning despite having swiped right for allowing modifications on TWRP?

[Recovery][LG-H960A] TWRP v3.0.2-0 (unofficial)

This is an unofficial TWRP port for LG-H960A.
Thanks to @KAsp3rd and @GROGG88
I DON'T TAKE ANY RESPONSIBILITY. YOU DO EVERYTHING AT YOUR OWN RISK.
READ EVERYTHING and MAKE A BACKUP BEFORE YOU START.
Instructions:
1. You must be on newest stock Marshmallow: H960A20a_00_0316.kdz
You can use LG Bridge to install official update, or download .kdz file HERE
2. You need to have bootloader ulocked.
Official instructions are here: ( Unlocking the Bootloader @ LG Developer )
Remember that this will completely WIPE YOUR DATA, you will LOSE WARRANTY and this operation is IRREVERSIBLE.
3. Flash TWRP.
I assume you got ADB and FASTBOOT drivers working and adb is paired (it should be if you completed step 2).
Connect your phone to your pc, open command prompt and reboot to bootloader:
Code:
adb reboot bootloader
Your phone should reboot and you should be welcomed by Fastboot Mode screen.
Now download the recovery file (below) to your pc, unpack (to get .img) and rename it to recovery.img and put it in folder where you got command prompt open and:
Code:
fastboot flash recovery recovery.img
4. Boot to TWRP.
As on Marshmallow some fastboot commands are not working and LG is restoring recovery on every boot (so you cant use "adb reboot recovery" right now) you need to use one trick.
DO NOT REBOOT YOUR PHONE.
When still in fastboot from step 3 you need to turn off your phone completely. You can do that by holding power button or if that is not working take the battery out.
Now (put the battery in) and press POWER + VOL DOWN buttons. When you see LG logo release the POWER button (while still holding VOL DOWN) and press POWER button again.
You should see a screen which is asking you if you want to factory reset your phone. Don't worry - if you made everything correctly it should not wipe your phone.
Use volume and power buttons to choose YES (twice) - and you should see a TWRP screen (after a while)
WARNING: IF YOU REBOOTED YOUR PHONE AFTER FLASHING RECOVERY THIS STEP WILL REALLY ERASE ALL DATA. You need to flash recovery again (step 3)
5. (optional) flash SuperSU to get root.
Get SuperSU from official thread and put it in your phone.
While in TWRP from step 4 your phone should be recognized by ADB. Use below to move file to sdcard.
Code:
adb push BETA-SuperSU-v2.74-2-20160519174328.zip /sdcard/supersu.zip
Now in TWRP click Install, go to /sdcard/ and chooose supersu.zip. Follow instructions. After install you should choose to wipe cache/dalvik and reboot to system.
Your phone should be rooted now.
Download:
twrp-3.0.2.0-0-h960a.img.zip
(unpack .zip to get flashable .img)
Issues:
- Layout is wrong, status bar is being drawn on second screen.
- Date/time is wrong.

broken url

OK, now if we have recovery, is it possible to dump rooted system and pack it to .tot file for people who don't want to lose warranty?

11868 said:
broken url
Click to expand...
Click to collapse
Oh, true. Fixed.
rascal0pl said:
OK, now if we have recovery, is it possible to dump rooted system and pack it to .tot file for people who don't want to lose warranty?
Click to expand...
Click to collapse
Maybe.

Thank You it worked!

Great. Just bought it 2 days ago for good price. Will try it.
Sent from my LG-H955 using Tapatalk

Hi,
that's just great, thanks a lot.
As root is now possible has anyone tried to install xposed on th H960A?
I'm wondering if the second screen fix for the Telekom V10 also works with the H960A.
What about Viper4Android and AdAway?

rudi666 said:
This is an unofficial TWRP port for LG-H960A.
Thanks to @KAsp3rd and @GROGG88
I DON'T TAKE ANY RESPONSIBILITY. YOU DO EVERYTHING AT YOUR OWN RISK.
READ EVERYTHING and MAKE A BACKUP BEFORE YOU START.
Instructions:
1. You must be on newest stock Marshmallow: H960A20a_00_0316.kdz
You can use LG Bridge to install official update, or download .kdz file HERE
2. You need to have bootloader ulocked.
Official instructions are here: ( Unlocking the Bootloader @ LG Developer )
Remember that this will completely WIPE YOUR DATA, you will LOSE WARRANTY and this operation is IRREVERSIBLE.
3. Flash TWRP.
I assume you got ADB and FASTBOOT drivers working and adb is paired (it should be if you completed step 2).
Connect your phone to your pc, open command prompt and reboot to bootloader:
Code:
adb reboot bootloader
Your phone should reboot and you should be welcomed by Fastboot Mode screen.
Now download the recovery file (below) to your pc, unpack (to get .img) and rename it to recovery.img and put it in folder where you got command prompt open and:
Code:
fastboot flash recovery recovery.img
4. Boot to TWRP.
As on Marshmallow some fastboot commands are not working and LG is restoring recovery on every boot (so you cant use "adb reboot recovery" right now) you need to use one trick.
DO NOT REBOOT YOUR PHONE.
When still in fastboot from step 3 you need to turn off your phone completely. You can do that by holding power button or if that is not working take the battery out.
Now (put the battery in) and press POWER + VOL DOWN buttons. When you see LG logo release the POWER button (while still holding VOL DOWN) and press POWER button again.
You should see a screen which is asking you if you want to factory reset your phone. Don't worry - if you made everything correctly it should not wipe your phone.
Use volume and power buttons to choose YES (twice) - and you should see a TWRP screen (after a while)
WARNING: IF YOU REBOOTED YOUR PHONE AFTER FLASHING RECOVERY THIS STEP WILL REALLY ERASE ALL DATA. You need to flash recovery again (step 3)
5. (optional) flash SuperSU to get root.
Get SuperSU from official thread and put it in your phone.
While in TWRP from step 4 your phone should be recognized by ADB. Use below to move file to sdcard.
Code:
adb push BETA-SuperSU-v2.74-2-20160519174328.zip /sdcard/supersu.zip
Now in TWRP click Install, go to /sdcard/ and chooose supersu.zip. Follow instructions. After install you should choose to wipe cache/dalvik and reboot to system.
Your phone should be rooted now.
Download:
twrp-3.0.2.0-0-h960a.img.zip
(unpack .zip to get flashable .img)
Issues:
- Layout is wrong, status bar is being drawn on second screen.
- Date/time is wrong.
Click to expand...
Click to collapse
Are there any other known issues? I don`t need to install any custom roms. I need it only for root and xposed on Marshmallow. Is there something that can surprise me?

Hi,
"OK, now if we have recovery, is it possible to dump rooted system and pack it to .tot file for people who don't want to lose warranty? "
Ohh, thats sounds nice if this realy possible.
i love my v10.

orbitandre said:
hi,
"ok, now if we have recovery, is it possible to dump rooted system and pack it to .tot file for people who don't want to lose warranty? "
ohh, thats sounds nice if this realy possible.
i love my v10.
Click to expand...
Click to collapse
+1 ??

cyvr1 said:
As root is now possible has anyone tried to install xposed on th H960A?
I'm wondering if the second screen fix for the Telekom V10 also works with the H960A.
What about Viper4Android and AdAway?
Click to expand...
Click to collapse
Didn't try xposed but I think it should work (if it's working on other V10 models - they are not that different). I just recently bought V10 and was disappointed in dpi, so I needed root to patch second screen to be dpi-independent.
Also: why would you want things like Viper4Android when you got really good sounding hifi dac onboard?
fixxxer102 said:
Are there any other known issues? I don`t need to install any custom roms. I need it only for root and xposed on Marshmallow. Is there something that can surprise me?
Click to expand...
Click to collapse
For sure it's enough to flash packages and get root. Xposed is independent from recovery so I can't say anything about that.
Testing are up to you guys. Don't be afraid as this phone is not easy to brick.

rudi666 said:
Also: why would you want things like Viper4Android when you got really good sounding hifi dac on board?
Click to expand...
Click to collapse
Quite simple answer. The onboard Hifi DAC only works with cable headphones. Viper4Android also supports Bluetooth devices.

rudi666 said:
I just recently bought V10 and was disappointed in dpi, so I needed root to patch second screen to be dpi-independent.
Click to expand...
Click to collapse
Could you write a small guide about the dpi change (I prefer 540-580)?
Thanks in advance.

cyvr1 said:
Quite simple answer. The onboard Hifi DAC only works with cable headphones. Viper4Android also supports Bluetooth devices.
Click to expand...
Click to collapse
Ah, you are right, that makes perfect sense. Sorry, I forgot about that.
paschalism said:
Could you write a small guide about the dpi change (I prefer 540-580)?
Click to expand...
Click to collapse
There is still a long way, right now second screen FCs are fixed, but layouts are still wrong. I don't know if I can fix it to be truly dpi-independent but I think 560 is optimal value for this screen.

Is this working with
H960a
V20a-AME-xx??

1k views and only 11 "thanks"??? Really? Guys! We need support devs! Big THANK YOU for ur hard work @rudi666. I haven't try ur method yet but I am happy with the fact that something is beginning to happen with v10
Wysłane z mojego LG-H960 przy użyciu Tapatalka

asmoroth said:
I haven't try ur method yet but I am happy with the fact that something is beginning to happen with v10
Click to expand...
Click to collapse
I did try his method and it worked like a charm. Ok, you'll have to reflash TWRP if you want to use it but I'm sure it's just a matter of time until we have permanent TWRP like th T-Mobile V10 obviously has.
Thanks to rudi666 I have root, xposed, adaway and viper4audio up and running on my V10. And as there are no interesting custom roms to flash in my opinion it does not matter that I'd need to reflash TWRP. If you plan your flashing in advance you can flash all zip files in one go. No real need for TWRP afterwards.

Thanks guys. Unfortunately I see there is not much going on in V10 scene, and it's a shame.
cyvr1 said:
Ok, you'll have to reflash TWRP if you want to use it but I'm sure it's just a matter of time until we have permanent TWRP like th T-Mobile V10 obviously has.
Click to expand...
Click to collapse
Hm.. if you follow instructions you should get permanent TWRP, just try "adb reboot recovery" to test it if you don't want to risk clearing data when using button combination. There is a file called /system/boot-from-recovery.p which is 'restoring recovery' on every boot (that's why there is an info in instruction about not rebooting your phone the first time), but after all the steps this file will be patched. I don't remember if the first use of TWRP or flashing SuperSU does it, but you should get permanent recovery. If not you can always rename this file manually.

rudi666 said:
Hm.. if you follow instructions you should get permanent TWRP, just try "adb reboot recovery" to test it if you don't want to risk clearing data when using button combination. There is a file called /system/boot-from-recovery.p which is 'restoring recovery' on every boot (that's why there is an info in instruction about not rebooting your phone the first time), but after all the steps this file will be patched. I don't remember if the first use of TWRP or flashing SuperSU does it, but you should get permanent recovery. If not you can always rename this file manually.
Click to expand...
Click to collapse
Hi,
I will try that again and see if I can get permanent TWRP. But as I said currently there is no real requirement for that. I flashed SuperSU and both files for xposed when I first booted into recovery and that is all I need at the moment.

i cant enter bootloader
h960A
after adb reboot booloader it keeb restart to soft

[How to]: going from China ROM to a working, rooted international ROM (2016/06/20)

Hey guys,
I recently purchased a Mi5 in China and had a hellish experience trying to get a working rooted international ROM on it even though I am definitely not a noob at android. I found out that most issues I had were result of small/stupid mistakes that can be easily avoided with the proper knowledge, so I decided to write a super quick how to on the process for anyone that might need it in the future. There are similar guides out there, and I will refer to some (all credit goes to original posters) but I found that most are incomplete/not updated/plain wrong. Please also note that this guide is updated to June 20th, newer ROM versions might require different steps.
This how to assumes you are familiar with the standard ROM flashing process, in case anyone needs a more detailed explaination of some of the steps, you can reply or search XDA elsewhere, most of the stuff has been mentioned here and there before.
1. Check that your hardware is ok (dial *#*#64663#*#* in dialer, you will enter hardware test mode, check every single item carefully)
2. Request a bootloader unlock from Xiaomi, unlock the bootloader: follow instructions here http://forum.xda-developers.com/mi-5/how-to/unlocking-xiaomi-mi-5-bootloader-t3336243
3. Now that Your bootloader is unlocked, you have 3 main options for working ROMs: Xiaomi's Global Stable, Xiaomi's Global Dev, Xiaomi.eu's unofficial Stable. If you want to play it safe, I suggest to go with the Xiaomi's Global Stable, otherwise choose Xiaomi.eu's unofficial Stable. I did not test extensively all three, so this is just a general recommendation.
4. In any case, you will need to use the official Xiaomi's flashing tool (Miflash) to do your first ROM flash. Just follow the process here: http://en.miui.com/a-234.html and you'll have flashed your new ROM. In case you want to flash Xiaomi.eu's unofficial Stable, follow the same process but get the flashable ROM here: https://xiaomi.eu/community/threads/xiaomi-eu-multilang-rom-for-xiaomi-mi5-unlocked-bl-only-released.31231/
5. Boot into your newly flashed ROM, check once again that hardware is ok (see step 1.). Please also see step 10b for a tidbit of additional info if You're in China.
6. Reboot into bootloader, boot (only boot, no need to install) TWRP, which you can find here as part of Xiaomi.eu's thread above in step 4. inside a zip packaged with a modded bootloader image. do NOT install the modded bootloader image. Also, this is the only version of TWRP that I found working for my device. There are a couple more versions from chinese developers (cofface, ganfan), but booting either resulted in blank screen.
7. Once you are in TWRP, the recovery will ask you for a decryption password, just press cancel, then "Swipe to allow modifications"
8. Sideload (you cannot install from internal storage since you will not be able to access it at the moment) the latest SuperSU stable, which you can find here: http://forum.xda-developers.com/showthread.php?t=1538053. Please note that you WILL need the latest version, anything earlier might just get you a bootloop. And please do NOT format /Data to make it accessible to TWRP as that will also likely result in bootloop. Just sideload whatever you need.
9. Do NOT wipe Dalvik or Cache, reboot into System.
10. Congrats, You're done. Have a beer/coffee/tea and pat yourself on the back.
10b. In case You're in China, and this is Your first Android 5.0+ ROM, you will happen into a "bug" (it's not really a bug, but a result of China's Great Firewall), where whenever you connect to a Wifi, the phone will think you have no internet access and that will cause a whole host of issues (won't reconnect automatically, will try to default to 4G etc.). If so, just enable ADB Debugging and type adb shell "settings put global captive_portal_server httpstat.us/204" . That will mostly solve it (you might still get some weird result with some APs, but toggling Wifi should solve the problem for that AP forever.

Lazer Bear said:
6. Reboot into bootloader, boot (only boot, no need to install) TWRP, which you can find here as part of Xiaomi.eu's thread above in step 4. inside a zip packaged with a modded bootloader image. do NOT install the modded bootloader image. Also, this is the only version of TWRP that I found working for my device. There are a couple more versions from chinese developers (cofface, ganfan), but booting either resulted in blank screen.
Click to expand...
Click to collapse
How do you boot into twrp without flashing it? fastboot boot recovery.img doesn't work for me.. the command was successfull, downloading to the phone, then it's telling me booting, but the phone stay in fastboot.. thx

m_adnan said:
How do you boot into twrp without flashing it? fastboot boot recovery.img doesn't work for me.. the command was successfull, downloading to the phone, then it's telling me booting, but the phone stay in fastboot.. thx
Click to expand...
Click to collapse
After it says booting, does the screen light up? If so please check wether "adb devices" and "fastboot devices" return anything. If adb returns "recovery" or if both return empty, you're likely bumping into my same issue where the recovery won't boot (to me this happened regardless of whether I flashed or booted it). Are you using the specific recovery version from my point 6?

Lazer Bear said:
After it says booting, does the screen light up? If so please check wether "adb devices" and "fastboot devices" return anything. If adb returns "recovery" or if both return empty, you're likely bumping into my same issue where the recovery won't boot (to me this happened regardless of whether I flashed or booted it). Are you using the specific recovery version from my point 6?
Click to expand...
Click to collapse
no, nothing happens on the screen, it stays in fb mode without any reaction. adb and fb devices doesn't return any device connected.. if i do an fb reboot it told me "waiting for any device" so the only option to get it run again is to power off.. yes of course, it's the recovery.img with the modified boot.img..

Lazer Bear said:
After it says booting, does the screen light up? If so please check wether "adb devices" and "fastboot devices" return anything. If adb returns "recovery" or if both return empty, you're likely bumping into my same issue where the recovery won't boot (to me this happened regardless of whether I flashed or booted it). Are you using the specific recovery version from my point 6?
Click to expand...
Click to collapse
i want only to inform you, i get it to work.. the problem was my rom, miui 8.. for miui 8 you will need a new version of twrp, which you can download here: https://yadi.sk/d/oj6Z-0u7sXdw6 after that, i was able to boot to the twrp recovery without flashing it, so i keept everything original like it was and was able to sideload the supersu and get root without to format my data.. when you start the recovery it came in chinese, but when you click on the right button you can choose your language.. that's it.. thank you for you support dude!!

Is it only way to switch from chinese ROM to official global ROM to have unlocked bootloader? If it is, is there any other way of unlocking it, waiting 15 days to get permission seems ridiculous.

Lovely step by step guide. But, any idea if it will wipe the user data and/or internal sdcard when moving from the chinese to international version?

[RECOVERY][X704F][OFFICIAL] TWRP 3.3.X for Lenovo Tab4 10 Plus

Official Downloads
https://twrp.me/lenovo/lenovo_X704F.html
Unofficial Downloads
https://www.androidfilehost.com/?w=files&flid=295687
Changelog for unofficial builds
twrp-3.3.1-0-X704F-20190604-codeworkx.img
- Updated to twrp 3.3.1
- Updated prebuilt kernel
- Removed lenovocust from backup
twrp-3.3.0-0-X704F-20190523-codeworkx.img
- initial build
Sources
Device tree: https://github.com/Teamwin/android_device_lenovo_X704F
Kernel: https://github.com/lenovo-devs/android_kernel_lenovo_msm8953

I've seen you are working with yener90 for this device. His TWRP is valid for F, L and few other variants.
Are you able to let us know if yours is the same? Or still testing and too early to know?
Thank you (I follow you in the OnePlus 5 project too).

Flowah123 said:
I've seen you are working with yener90 for this device. His TWRP is valid for F, L and few other variants.
Are you able to let us know if yours is the same? Or still testing and too early to know?
Thank you (I follow you in the OnePlus 5 project too).
Click to expand...
Click to collapse
That seems to be the case
"TARGET_OTA_ASSERT_DEVICE := TB-X704A,TB-X704F,TB-X704L,TBX704,tb_x704a,tb_x704f,tb_x704l"
(https://github.com/codeworkx/android_device_lenovo_X704F/blob/android-9.0/BoardConfig.mk)

There's official support now.
https://twrp.me/lenovo/lenovo_X704F.html

twrp-3.3.1-0-X704F.img verified working on a new TB-X704V. Everything seems to be working.
---------- Post added at 19:36 ---------- Previous post was at 19:04 ----------
Maybe I spoke too soon.
I tried installing Yener90's Lineage OS 16 image only my TB-X704V device and it failed to boot. That's fine, but then I tried to restore the OEM image that I had backed up previously. Unfortunately, I am not able to get back to a booting system.

black.kahder said:
twrp-3.3.1-0-X704F.img verified working on a new TB-X704V. Everything seems to be working.
---------- Post added at 19:36 ---------- Previous post was at 19:04 ----------
Maybe I spoke too soon.
I tried installing Yener90's Lineage OS 16 image only my TB-X704V device and it failed to boot. That's fine, but then I tried to restore the OEM image that I had backed up previously. Unfortunately, I am not able to get back to a booting system.
Click to expand...
Click to collapse
Look at the other thread. 3.3.0 works as expected. Use the old twrp for my current ROM or wait for the next update, which will support 3.3.0

I don't have experience customizing TWRP images for specific devices, so let me apologize in advance for my n00b questions...
How similar are the x704f and x705f tablets? I'm wondering if it might be possible to use an x704f TWRP image on an x705f. Lenovo recently released a stock ROM for Pie on the x705f. Now I'm finally able to unlock the bootloader. The previous stock ROM would not respond to fastboot oem unlock commands. I was then able to fastboot flash a bootloader image pre patched with Magisk so now the tab is rooted and happy. However, I still feel insecure without TWRP as it seems to be a key tool that I use for emergency ADB access, flashing, and making nandroid backups. How big of a project do you think it would be to make a customized image for the x705f? Do you think that is something where I would have to start from scratch? Or could the x704f image be used as a template that I could easily modify with information specific to the x705f?
Thanks for your time. I truly appreciate any help or advice you can give me on this.
Chaser

on my tb-x704f twrp on starts in landscape orientation. the last version i used was 3.2.3 and here i could use both orientations.
i also can't restore an backup because i can't write to the system partition. can this https://forum.xda-developers.com/showpost.php?p=79681018&postcount=259 fix the problem?

gene2 said:
i also can't restore an backup because i can't write to the system partition. can this https://forum.xda-developers.com/showpost.php?p=79681018&postcount=259 fix the problem?
Click to expand...
Click to collapse
No, it won't, it's a magisk module that allows R/W to the system partition after boot up to
facilitate some apps. that require it for full root access.

The problem was that i had no r/w to system partition. the restore works, but the system doesn't start. i have a boot loop with the lenovo logo. i have wiped dalvik, cache and system. after that i also made the normal wipe. then i restored the backup and after restart i have the boot loop. is there anything more to do? this was all i have to do on my other devices.

gene2 said:
The problem was that i had no r/w to system partition. the restore works, but the system doesn't start. i have a boot loop with the lenovo logo. i have wiped dalvik, cache and system. after that i also made the normal wipe. then i restored the backup and after restart i have the boot loop. is there anything more to do? this was all i have to do on my other devices.
Click to expand...
Click to collapse
Sounds like encryption is compromised, restore stock ROm, re-boot and start again.
See my other post to you here:-
https://forum.xda-developers.com/showpost.php?p=80273515&postcount=5

Hello, I have tried TWRP for TB-X704F on TB-X704A, but though my bootloader is unlocked, I have the latest SDK tools, and fastboot flash recovery recovery.img seems to take, nothing I do causes the device to boot into TWRP. I cannot sideload lineagos using stock recovery, and so for now I seem to be stuck. Any suggestions? I'd like to move past Android 7.1 for a more secure OS.

I've had the EXACT same problem with a TB-X704A. I've been waiting for someone else to say so. I'm sorry I don't have a solution but I'm hoping someone more knowledgeable then me sees our problem. Thanks to everyone, especially codeworkx who does this stuff!

Mddaddy said:
Hello, I have tried TWRP for TB-X704F on TB-X704A, but though my bootloader is unlocked, I have the latest SDK tools, and fastboot flash recovery recovery.img seems to take, nothing I do causes the device to boot into TWRP. I cannot sideload lineagos using stock recovery, and so for now I seem to be stuck. Any suggestions? I'd like to move past Android 7.1 for a more secure OS.
Click to expand...
Click to collapse
You have to reboot to recovery manually not via fastboot. Unplug from pc and hold power and volume up it should boot into twrp this way cus f version should work
---------- Post added at 04:02 AM ---------- Previous post was at 03:55 AM ----------
kirknado18 said:
You have to reboot to recovery manually not via fastboot. Unplug from pc and hold power and volume up it should boot into twrp this way cus f version should work
Click to expand...
Click to collapse
Twrp for tb x704f should work on all 704 versions but you have to boot into recovery manually not through adb fastboot it wont boot up that way for some reason. Let me know if this solves the problem.

I wanted to update from LineageOS 16 to LineageOS 17. Instructions there say to upgrade to latest TWRP (https://forum.xda-developers.com/th...m-lineageos-17-0-lenovo-tab4-10-plus-t4016705). I downloaded the unofficial twrp-3.3.1-0-X704F-20190604-codeworkx.img, flashed using adb, but when trying to go into recovery mode - will not go into recovery. Tries, then reboots again, and goes into LineageOS 16.
Downloaded the "official" version form (https://dl.twrp.me/X704F/), version twrp-3.4.0-0-X704F.img, again flashed using adb - again same results. Cannot get into recovery mode, boots twice and goes back into LineageOS 16.
So - something didn't go quite right - how do I get into recovery mode?

tundrwd said:
I wanted to update from LineageOS 16 to LineageOS 17. Instructions there say to upgrade to latest TWRP (https://forum.xda-developers.com/th...lineageos-17-0-lenovo-tab4-10-plus-t4016705). I downloaded the unofficial twrp-3.3.1-0-X704F-20190604-codeworkx.img, flashed using adb, but when trying to go into recovery mode - will not go into recovery. Tries, then reboots again, and goes into LineageOS 16.
Downloaded the "official" version form (https://dl.twrp.me/X704F/), version twrp-3.4.0-0-X704F.img, again flashed using adb - again same results. Cannot get into recovery mode, boots twice and goes back into LineageOS 16.
So - something didn't go quite right - how do I get into recovery mode?
Click to expand...
Click to collapse
Unplug from USB. Hold power and volume up buttons until the bootloader loads. Use the volume rocker to select "Recovery mode". Press power button to confirm.

jfaheyfan said:
Unplug from USB. Hold power and volume up buttons until the bootloader loads. Use the volume rocker to select "Recovery mode". Press power button to confirm.
Click to expand...
Click to collapse
I'm aware of how to get into recovery - it WON'T go into recovery. Starts up, the Moto screen flashes, it reboots, Moto screen again, then loads LineageOS. So I simply cannot get into recovery once selecting "Recovery Mode".

tundrwd said:
I'm aware of how to get into recovery - it WON'T go into recovery. Starts up, the Moto screen flashes, it reboots, Moto screen again, then loads LineageOS. So I simply cannot get into recovery once selecting "Recovery Mode".
Click to expand...
Click to collapse
What model is your tablet?

I have an A model and an F model. I've used the same TWRP on both the A and F. This particular instance is just the A model - TBX-704A

tundrwd said:
I have an A model and an F model. I've used the same TWRP on both the A and F. This particular instance is just the A model - TBX-704A
Click to expand...
Click to collapse
You're not the first:
https://forum.xda-developers.com/showpost.php?p=81254945&postcount=12
https://forum.xda-developers.com/showpost.php?p=82183753&postcount=13
Not sure of the significance, but "Moto" doesn't appear in the boot sequence of my TB-X704N (changed to TB-X704L after I installed LOS 17.1). I get "Lenovo" in an orange rectangle.
My next step would be to try https://dl.twrp.me/X704F/twrp-3.3.1-0-X704F.img . Better yet would be to hear from someone who's installed LOS 17.1 on an "A" model.
---------- Post added at 08:03 PM ---------- Previous post was at 07:42 PM ----------
I installed TWRP 3.4.0 on my TB-X704N (Chinese Tab 4 10+ with 4G) three weeks ago. I went on to install LOS 17.1 (https://forum.xda-developers.com/th...7-0-lenovo-tab4-10-plus-t4016705/post81141501). Everything went well just by following instructions. Thank you, codeworkx!