Database Users

Yoga Tab 2 (830,1050,1380) - TWRP 2.8.7.0(6)

'what? lol'

1050F - All Good!
Thanks!

YamYam

ionioni said:
you tried to flash a partition from dnx mode
Click to expand...
Click to collapse
Doh... Been so confused lately....

workdowg said:
Doh...
Click to expand...
Click to collapse
maybe you should put that SMT AoL on a break... the YT2 one is almost forgotten.

ionioni said:
maybe you should put that SMT AoL on a break... the YT2 one is almost forgotten.
Click to expand...
Click to collapse
Probably... I had 3 or 4 more people interested... I posted the working MicroSD install files... But I do feel lonely...

Thanks brother, I will test in upcoming Saturday and will revert back.

a beginner's guide....tnx[emoji1] [emoji1]

@workdowg now that we have a permanent recovery does this mean we can start building cm and kernels? I am almost setup with my machine (just configuring Ubuntu). From what I have read on lenovo website is they messed something up with the charging and battery life in the last update

pug1 said:
@workdowg now that we have a permanent recovery does this mean we can start building cm and kernels? I am almost setup with my machine (just configuring Ubuntu). From what I have read on lenovo website is they messed something up with the charging and battery life in the last update
Click to expand...
Click to collapse
Since the bootloader is unlocked you may do what you wish. Permanent TWRP will make the job easier. Have at it!
As far as the current ROM from Lenovo.... It is really stable for me. I froze the usual suspects and I get about 3-4 days with 8-9hrs SOT. I don't game on this tablet and keep the brightness down to about 1/3.

updated: added compilation from 6.0 sources - TWRP 2.8.7.0(6)

ionioni said:
updated: added compilation from 6.0 sources - TWRP 2.8.7.6
Click to expand...
Click to collapse
Pretty... all good on the 1050F.

1050F (Latest LP OTA): I am able to flash it (bl is unlocked), but cannot access it after that. Stock recovery is still present... am I missing sth??

dtrail1 said:
1050F (Latest LP OTA): I am able to flash it (bl is unlocked), but cannot access it after that. Stock recovery is still present... am I missing sth??
Click to expand...
Click to collapse
it works in the 'live' mode? from dnx (PwrOn with both Vol pressed, screen shows 'fastboot starting...' message):
fastboot flash osloader bootx64.efi
fastboot boot twrp-1050f-b.img
you should also try to boot in the recovery right AFTER you flash it and if it goes twrp means that recovery from boot is still active on your build (and will write the recovery partition with a fresh image that he builds from the boot partition on each normal android start)
what is the OTA you're on?

ionioni said:
it works in the 'live' mode? from dnx (PwrOn with both Vol pressed, screen shows 'fastboot starting...' message):
fastboot flash osloader bootx64.efi
fastboot boot twrp-1050f-b.img
you should also try to boot in the recovery right AFTER you flash it and if it goes twrp means that recovery from boot is still active on your build (and will write the recovery partition with a fresh image that he builds from the boot partition on each normal android start)
Click to expand...
Click to collapse
Already figured it, but thx!! I forgot to FIRST boot it from DNX mode once, and then flash it permanently from fb mode. thx

I have followed each steps mentioned to flash perm. twrp recovery on my YOGA Tablet 2-830LC lollipop, unlocked bootloader; the process of flashing completes successfully yet I am unable to enter into recovery... When ever I try to enter into recovery it simply boots up normally... I have tried entering recovery by both hardware and software modes, but it fails... Kindly help me out of this mess...
Thank you

QuazIqbal said:
I have followed each steps mentioned to flash perm. twrp recovery on my YOGA Tablet 2-830LC lollipop, unlocked bootloader; the process of flashing completes successfully yet I am unable to enter into recovery... When ever I try to enter into recovery it simply boots up normally... I have tried entering recovery by both hardware and software modes, but it fails... Kindly help me out of this mess...
Thank you
Click to expand...
Click to collapse
while i don't know 100% whether it is working or not on your model and since those who download the files don't give their feedback...
try rebooting in recovery, when in normal android, send a adb reboot recovery or boot in fastboot mode and chose the RECOVERY as target with Volkeys and activate with Power button
check also that you flashed the correct img file (you did unzipped the file before flashing no? ) fastboot flash recovery twrp....img

ionioni said:
while i don't know 100% whether it is working or not on your model and since those who download the files don't give their feedback...
try rebooting in recovery, when in normal android, send a adb reboot recovery or boot in fastboot mode and chose the RECOVERY as target with Volkeys and activate with Power button
check also that you flashed the correct img file (you did unzipped the file before flashing no? ) fastboot flash recovery twrp....img
Click to expand...
Click to collapse
I tried all the ways including 'adb reboot recovery and also tried to enter recovery through droidboot but each time it simply rebooted without going into recovery.... I also tried the temp recovery, by these commands "fastboot flash osloader bootx64.efi" & "fastboot boot twrp-830f-b.img" in this case also it simply rebooted in to android os.
P. S. I am able to enter twrp recovery through social design recovery.

any 830 owner can confirm if it is working or not on his device?

QuazIqbal said:
I tried all the ways including 'adb reboot recovery and also tried to enter recovery through droidboot but each time it simply rebooted without going into recovery.... I also tried the temp recovery, by these commands "fastboot flash osloader bootx64.efi" & "fastboot boot twrp-830f-b.img" in this case also it simply rebooted in to android os.
P. S. I am able to enter twrp recovery through social design recovery.
Click to expand...
Click to collapse
1. when you are entering the above two commands are you in DNX mode? ('fastboot starting' on screen)
2. when you upgraded to Lollipop did you used the OTA update process or you just flashed a stock Lollipop rom?
3. boot to your normal Android OS and open Contacts and in the search contacts box enter ####0000# it will open a VersionInfo window, tell me what it says under BIOS version line
by these commands "fastboot flash osloader bootx64.efi" & "fastboot boot twrp-830f-b.img" in this case also it simply rebooted in to android os.
Click to expand...
Click to collapse
4. right after you entered the commands it rebooted (ie you heard the tab buzzing as if you power on from off state) or just continued and booted t Android?

How to Stock FW and Relock Bootloader? OP5

Hi all,
I've wanted to go back to Stock OS but when i type "fastboot oem lock" it says "FAILED <remote: Flashing Lock is not allowed."
Everything boots normally to OS 4.5.2. In DEV options the Unlock Bootloader is greyed out and says bootloader is already unlocked.
What can i do?
Cheers

These instructions did work for me with the OnePlus 3/3T. They should also work for the OnePlus5, just make sure that you download the OnePlus5 version of the software and recovery.
https://forums.oneplus.net/threads/...-3-3t-and-go-back-completely-to-stock.456232/
Use this link for the stock recovery: https://forum.xda-developers.com/showpost.php?p=72748921&postcount=5

reayard said:
These instructions did work for me with the OnePlus 3/3T. They should also work for the OnePlus5, just make sure that you download the OnePlus5 version of the software and recovery.
https://forums.oneplus.net/threads/...-3-3t-and-go-back-completely-to-stock.456232/
Use this link for the stock recovery: https://forum.xda-developers.com/showpost.php?p=72748921&postcount=5
Click to expand...
Click to collapse
Hi i tried but does the same when i get to fastboot oem lock (it says Flashing Lock is not allowed).

r1card0amr said:
Hi i tried but does the same when i get to fastboot oem lock (it says Flashing Lock is not allowed).
Click to expand...
Click to collapse
Thanks I asked the same question earlier glad u tried it..I want to make sure we can relock it before I get the phone. Did u enable oem unlocking in the developer options before doing a fastboot oem lock? Also, make sure you are on stock everything including recovery..

mohan_kr said:
Thanks I asked the same question earlier glad u tried it..I want to make sure we can relock it before I get the phone. Did u enable oem unlocking in the developer options before doing a fastboot oem lock? Also, make sure you are on stock everything including recovery..
Click to expand...
Click to collapse
Hello. I first thing I do always is to install drivers. I start by connecting the phone to the laptop in charge mode, then in transfer files mode, MTP or camera. In this way he will recognise all the drivers your laptop needs.
Also I enter in fastboot mode and recovery so the laptop can recognise the drivers and always reboot laptop and phone just to double check.
What I did was: go to Developer Options and enabled Unlock Bootloader and USB Debugging.
Then I accepted the laptop request on my phone and all drives were OK.
I run CMD and typed fastboot devices to see if it recognises my phone and it displayed a serial number. So I proceed next to type fastboot oem unlock and the process went OK and on my phone it asked Yes or No to unlock and I choose yes.
Then I flash a twrp image by typing on CMD: fastboot flash recovery recovery.img (my twrp I'm had other name so I rename it. You need to enable "Show file extensions" in Windows so you can see what the extension is).
I then type fastboot boot recovery.img and the phone entered in Recovery Mode in this case TWRP.
My phone was always connected to the laptop and he open the internal storage window so I drag the supersu inside.
Then on TWRP I wiped dalvik and cache and I went to Install and installed the SupeSU on my internal memory root.
The phone then rebooted and ready to go.
But then I went to developer options and the Unlock bootloader was greyed out. I unroot my phone and flashed a stock recovery for OP5 and the stock image 4.5.2 and when I type fastboot oem lock it always says it can't be flashed.
I need to stock it since I'm giving to a family member and they don't understand much about phones and If there's a problem the warranty doesn't cover.
Just installed supersu to try an app. I never install 3rd party roms.

r1card0amr said:
I need to stock it since I'm giving to a family member and they don't understand much about phones and If there's a problem the warranty doesn't cover.
Click to expand...
Click to collapse
the warranty is not voided with unlocked bootloader..
https://oneplus.net/hk/support/answer/will-rooting-or-unlocking-the-bootloader-void-my-warranty

I found now that if i take pictures or screenshots the Album Folder is empty. I think my phone is bricked. Hence i can't lock the bootloader.

r1card0amr said:
I found now that if i take pictures or screenshots the Album Folder is empty. I think my phone is bricked. Hence i can't lock the bootloader.
Click to expand...
Click to collapse
if your phones boots its not bricked... My guess is that you data is corrupted, i would wipe everything including userdata en reflashing the stock with recovery.

Hogyoku said:
if your phones boots its not bricked... My guess is that you data is corrupted, i would wipe everything including userdata en reflashing the stock with recovery.
Click to expand...
Click to collapse
Hi right before your comment i managed lol.
I re-flash the stock recovery and in recovery i reset and wipe everything. then i install the OS4.5.3 by ADB Sideload and it's working now.
Just wanted to get rid of the inital warning that my bootloader is unlocked. I want to lock again.

I rooted my device with Magisk, and now I want to restore it to factory state.
I flashed stock recovery and OOS several times, wiped everything but fastboot oem lock failed all times (FAILED (remote: Flashing Lock is not allowed)).
Can you help me?
What should I do to relock bootloader?

here is your solution
r1card0amr said:
Hi right before your comment i managed lol.
I re-flash the stock recovery and in recovery i reset and wipe everything. then i install the OS4.5.3 by ADB Sideload and it's working now.
Just wanted to get rid of the inital warning that my bootloader is unlocked. I want to lock again.
Click to expand...
Click to collapse
here in this video u can see in detail how to lock bootloader. hope this help you
https://www.youtube.com/watch?v=CQYCSdDUdAU

HOW TO RELOCK..
Install TWRP and Magisk if you don't have them yet.
Magisk should allow you to slide "OEM unlocking" to "enabled"
Reboot to fastboot
Flash stock recovery via fastboot.
Run locking via fastboot flashing lock
Allow it to reboot and upon start up it will say device corrupted (THIS IS NORMAL)
Boot to recovery via the warning start screen.
Once in recovery, sideload latest FW.
Profit.

I usually do it this way (successfully):
Wipe everything but OTG in TWRP
Format data
Reboot to TWRP
Flash the full stock OOS zip
Reboot to fastboot
Flash stock recovery
Lock bootloader with the fastboot lock command

Has anyone made any progress with this? I too am having the issue as described and have tried the solution by Ricyksydhu, along with solutions from various other places around the net.

Lenovo K6 without OS

Hi, I already had my phone rooted and with TWRP installed, but I needed to restore my phone. First I did this trough the system, but I noted that a lot of old files still were there, and I went to TWRP and did a wipe, but selected /system and /cache, now I don't have a OS on my phone.
The phone doesn't turn off, everytime I try to power off, he turn on again, and stay on Lenovo logo. The only thing I can acess is Fastboot mode (via Power down + power), I cant acess TWRP trough the phone, but I found a .bat file, that when I'm in fastboot mode, it flashes twrp on my phone and I can acess it . The other problem is that I always get an error when trying to flash any rom. Things like Error:255 or ".zip file not valid". Tried 2 roms and nothing.
Can someone please help me? I would prefer a stock rom for Brazil, but now I just want any rom, dont even mind if it's not stock.

Crolys said:
Hi, I already had my phone rooted and with TWRP installed, but I needed to restore my phone. First I did this trough the system, but I noted that a lot of old files still were there, and I went to TWRP and did a wipe, but selected /system and /cache, now I don't have a OS on my phone.
The phone doesn't turn off, everytime I try to power off, he turn on again, and stay on Lenovo logo. The only thing I can acess is Fastboot mode (via Power down + power), I cant acess TWRP trough the phone, but I found a .bat file, that when I'm in fastboot mode, it flashes twrp on my phone and I can acess it . The other problem is that I always get an error when trying to flash any rom. Things like Error:255 or ".zip file not valid". Tried 2 roms and nothing.
Can someone please help me? I would prefer a stock rom for Brazil, but now I just want any rom, dont even mind if it's not stock.
Click to expand...
Click to collapse
Error 255 is caused because you are trying to install a 64bit ROM over TWRP (32bits), you need to upgrade TWRP to 64bit, just so you will be able to install a ROM. Remember that you should use Gapps in 64bit [ARM64]
TWRP: https://dl.twrp.me/karate/twrp-3.1.1-1-karate.img
Gapps: http://opengapps.org/ (ARM64)

J.D.M said:
Error 255 is caused because you are trying to install a 64bit ROM over TWRP (32bits), you need to upgrade TWRP to 64bit, just so you will be able to install a ROM. Remember that you should use Gapps in 64bit [ARM64]
Click to expand...
Click to collapse
I already had this version of twrp, but downloaded anyway and got the same error when tring to sideload a ROM "Updater process ended with ERROR: 255" . I don't know what to do anymore, I tried with 4 different ROMs, also I searched for a method to erase the lines with asserts on "update-scripts" in META-INF, but then I got a "Invalid ZIP file" error.

Crolys said:
I already had this version of twrp, but downloaded anyway and got the same error when tring to sideload a ROM "Updater process ended with ERROR: 255" . I don't know what to do anymore, I tried with 4 different ROMs, also I searched for a method to erase the lines with asserts on "update-scripts" in META-INF, but then I got a "Invalid ZIP file" error.
Click to expand...
Click to collapse
Try to go back to the 32bits version and erase everything and format the data and return to the 64bit version because here I had this problem it was because of the TWRP that I was using, it was the 32bits version, after that I upgraded to the 64bits version I did not have this problem. Remembering that in the site https://dl.twrp.me/karate/ has two versions of TWRP, the version twrp-3.1.1-0-karate.img is 32bits and the version twrp-3.1.1-1-karate. img is 64bit.

J.D.M said:
Try to go back to the 32bits version and erase everything and format the data and return to the 64bit version because here I had this problem it was because of the TWRP that I was using, it was the 32bits version, after that I upgraded to the 64bits version I did not have this problem.
Click to expand...
Click to collapse
Well, that kinda worked(?), now I have another error it says that my firmware is incompatible with the ROM version, and I need to update it (I dont know how to do this), and give me ERROR: 7 now

Crolys said:
Well, that kinda worked(?), now I have another error it says that my firmware is incompatible with the ROM version, and I need to update it (I dont know how to do this), and give me ERROR: 7 now
Click to expand...
Click to collapse
MAN, the ERROR: 7 now could be solved by deleting the lines with ASSERT in "\META-INF\com\google\android\updater-script".
So, thanks for helping me, the problem with 64/32bits worked. I'm really glad that this worked, had stuck for 3 days without OS, now i'm never messing with this stuff again haha.

Crolys said:
MAN, the ERROR: 7 now could be solved by deleting the lines with ASSERT in "\META-INF\com\google\android\updater-script".
So, thanks for helping me, the problem with 64/32bits worked. I'm really glad that this worked, had stuck for 3 days without OS, now i'm never messing with this stuff again haha.
Click to expand...
Click to collapse
I've been researching and was going to tell you to delete the above lines mentioned, I am glad you have succeeded.

got same 255 error,just now i reflashed stock rom and issue resolved

vasu009 said:
got same 255 error,just now i reflashed stock rom and issue resolved
Click to expand...
Click to collapse
how did you reflashed the stock rom, please reply cause im stuck with the twrp and unable to do it. my phone doesn't have an os now

what s the password of the trwp

J.D.M said:
I've been researching and was going to tell you to delete the above lines mentioned, I am glad you have succeeded.
Click to expand...
Click to collapse
Can install this ROM on any Lenovo K6 Power device ??

dushd95 said:
Can install this ROM on any Lenovo K6 Power device ??
Click to expand...
Click to collapse
Yeah

J.D.M said:
Yeah
Click to expand...
Click to collapse
It says device not supported why??

Dont forget to reboot again into twrp - after flashing 64bit twrp . This is a step that is very important if you will not reboot your phone into twrp after flashing 64 bit twrp then , it will keep showin you the error 255.
So check that .

wacccim said:
what s the password of the trwp
Click to expand...
Click to collapse
Go for 3.2.1.0 it is better then 3.1.1.1 in 64 bits it ain't ask password i use it to flash all roms

Tere 3.1.1-1 asking for password to encrypt data
I flashed my Lenovo k6 power with twrp 3.1.1-1 after I was not able to flash crdroid,lineage is,pixelized stock ROM to my phone. Now the twrp is asking for password to encrypt data and I am surprised because I hadn't set a password. I tried to unlock it with my phone password but I it is saying to enter correct password.
Please someone help me. I am not able to flash other things too please somebody help me.:

Erase the data
Shrestha Kumar said:
I flashed my Lenovo k6 power with twrp 3.1.1-1 after I was not able to flash crdroid,lineage is,pixelized stock ROM to my phone. Now the twrp is asking for password to encrypt data and I am surprised because I hadn't set a password. I tried to unlock it with my phone password but I it is saying to enter correct password.
Please someone help me. I am not able to flash other things too please somebody help me.:
Click to expand...
Click to collapse
Use erase the data from wipe option then you will be able to install rom and g-apps.
Every time you will need password, I don't know why but after erasing data you install all files otherwise you need to erase data again and again

Crolys said:
Hi, I already had my phone rooted and with TWRP installed, but I needed to restore my phone. First I did this trough the system, but I noted that a lot of old files still were there, and I went to TWRP and did a wipe, but selected /system and /cache, now I don't have a OS on my phone.
The phone doesn't turn off, everytime I try to power off, he turn on again, and stay on Lenovo logo. The only thing I can acess is Fastboot mode (via Power down + power), I cant acess TWRP trough the phone, but I found a .bat file, that when I'm in fastboot mode, it flashes twrp on my phone and I can acess it . The other problem is that I always get an error when trying to flash any rom. Things like Error:255 or ".zip file not valid". Tried 2 roms and nothing.
Can someone please help me? I would prefer a stock rom for Brazil, but now I just want any rom, dont even mind if it's not stock.
Click to expand...
Click to collapse
I Faced same problem. It's ok that your phone is in weird state for time now. And also possible to recover.
Hopefully you have adb-tool, custom-rom & gapp, twrp.img on your PC.
1) Boot your mobile in fastmode using Power ON with Volume down key for 5 sec (Lenovo log with left hand side sayinh fastboot mode)
2) Connect the mobile to PC using USB & Go to adb tool folder. Open command prompt in this folder & Execute the follow step by step execution
fastboot oem reboot-recovery
3)Wait for mobile to boot in to recovery mode with TWRP
Now need to flash custom-rom followed by gapps installion.
I) You can use pendrive with otg to flash custom-rom followed by gapps
OR
II)You can use phone storage/SD card to flash the custom-rom followed by gapps
OR
III)adb sideload command as fallow
a)In TWRP recovery on mobile, goto Adavanced->ADB Sideload & Swipe to start the sideload
Now on PC execute . Specify custom rom path inside ""
adb sideload "C:\adb\images\MyCustomROM.zip"
Have a patience to complete the operation.
Click back for Adavanced Menu again.
b) Select ADB Sideload & Swipe to start the sideload
Now on PC execute . Specify Gapp path inside ""
adb sideload "C:\adb\images\open_gapps-arm-7.1-pico-20180611.zip"
c)Have a patience to complete the operation.
Once complete go to TWRP Screen.
d)Now go back TWRP main menu & select wipe->format Data.
Go to Reboot->system.
How to install TWRP if no OS there
1) Boot your mobile in fastmode using Power ON with Volume down key for 5 sec (Lenovo log with left hand side sayinh fastboot mode)
2) Connect the mobile to PC using USB & Go to adb tool folder. Open command prompt in this folder & Execute the follow step by step execution
a) To check the device is connected to PC or not
fastboot oem device-info
b) To flash the recovery. Give twrp path inside the ""
fastboot flash recovery "C:\adb\images\twrp.img"
c) To boot into recovery mode
fastboot oem reboot-recovery
---------- Post added at 10:03 PM ---------- Previous post was at 09:57 PM ----------
[/COLOR]
Shrestha Kumar said:
I flashed my Lenovo k6 power with twrp 3.1.1-1 after I was not able to flash crdroid,lineage is,pixelized stock ROM to my phone. Now the twrp is asking for password to encrypt data and I am surprised because I hadn't set a password. I tried to unlock it with my phone password but I it is saying to enter correct password.
Please someone help me. I am not able to flash other things too please somebody help me.:
Click to expand...
Click to collapse
In my case, It worked with PIN.

TWRP stuck at splash screen, fastboot not working, don't know how to boot into EDL...

Hello, i've got a big problem:
i've tried to install 8.1 Oreo, but it asked for password, i've tried to format data and it showed me an error, i've tried to reboot recovery but it stuck on splash TWRP screen... And also fastboot mode from bootloader can't be launched - it just starting system which i can't access. I have a2017g btw.
Hoping for help and happy new year to everybody!

kingracer said:
Hello, i've got a big problem:
i've tried to install 8.1 Oreo, but it asked for password, i've tried to format data and it showed me an error, i've tried to reboot recovery but it stuck on splash TWRP screen... And also fastboot mode from bootloader can't be launched - it just starting system which i can't access. I have a2017g btw.
Hoping for help and happy new year to everybody!
Click to expand...
Click to collapse
uuhh.. MiFlash?
If you can get TWRP 3.2.1-0 to work, try to format data again. If it fails follow raystef66's method on how to get rid of the 5 second screen (you'd be doing it only to restore fastboot) then boot to fastboot and issue 'fastboot erase userdata'

Choose an username... said:
uuhh.. MiFlash?
If you can get TWRP 3.2.1-0 to work, try to format data again. If it fails follow raystef66's method on how to get rid of the 5 second screen (you'd be doing it only to restore fastboot) then boot to fastboot and issue 'fastboot erase userdata'
Click to expand...
Click to collapse
Where can i find that method? I've already got it figured out but i still can't install Oreo because after using the instruction I've had the same problem

kingracer said:
Where can i find that method? I've already got it figured out but i still can't install Oreo because after using the instruction I've had the same problem
Click to expand...
Click to collapse
On the guides section of course

soft brick help, adb help

was running the xiaomi.eu rom beta then flashed to stable and now soft brick
adb devices shows "recovery" instead of "device"
adb reboot fastboot and the phone goes into an encrypted twrp 3.3.0.0
I have miflashtool

Aaagogo said:
was running the xiaomi.eu rom beta then flashed to stable and now soft brick
adb devices shows "recovery" instead of "device"
adb reboot fastboot and the phone goes into an encrypted twrp 3.3.0.0
I have miflashtool
Click to expand...
Click to collapse
Hey there!
I kinda new here so forgive me if I gave you a wrong guide, but from what i read across forums, if you're phone get soft bricked, you just need to flash the stock firmware. try to find latest xiaomi stock firmware.
Adb devices shows "recovery" means your device was in recovery mode. Try "adb reboot recovery" and you'll end up in your custom recovery (I assume you installed one). If your recovery was encrypted try to install push "disable dm variety" command on adb and when your custom recovery asks for password, just press cancel or enter and you'll enter recovery mode.
From your recovery mode, you can enter sideload and install everything from there using adb from your computer.
Hopefully your phone will get better soon! lol
P.S.: sorry for my bad English, I'm not a native speaker.

rchmdnglng said:
Hey there!
I kinda new here so forgive me if I gave you a wrong guide, but from what i read across forums, if you're phone get soft bricked, you just need to flash the stock firmware. try to find latest xiaomi stock firmware.
Adb devices shows "recovery" means your device was in recovery mode. Try "adb reboot recovery" and you'll end up in your custom recovery (I assume you installed one). If your recovery was encrypted try to install push "disable dm variety" command on adb and when your custom recovery asks for password, just press cancel or enter and you'll enter recovery mode.
From your recovery mode, you can enter sideload and install everything from there using adb from your computer.
Hopefully your phone will get better soon! lol
P.S.: sorry for my bad English, I'm not a native speaker.
Click to expand...
Click to collapse
going to retry twrp from 10.3.6.0 PFGMIXM

TWRP is encrypted,
i miflashtoll back to 10.3.6.0 PFGMIXM, unlocked bootloader
flash twrp 3.3.0.0 and still the same result, encrypted TWRP.
no twrp means no root, need assistance.

Aaagogo said:
was running the xiaomi.eu rom beta then flashed to stable and now soft brick
adb devices shows "recovery" instead of "device"
adb reboot fastboot and the phone goes into an encrypted twrp 3.3.0.0
I have miflashtool
Click to expand...
Click to collapse
Hello,
And if instead of executing "adb fastboot reboot", you try to access fastboot mode with Vol- and Power?
What happen?

hugomoya said:
Hello,
And if instead of executing "adb fastboot reboot", you try to access fastboot mode with Vol- and Power?
What happen?
Click to expand...
Click to collapse
i can access fastboot with no problems, it's booting into recovery that doesn't work
i am using twrp from the official thread;
https://forum.xda-developers.com/redmi-note-7/how-to/one-redmi-note-7-unlock-bootloader-t3890751
same thing happen on all 3 methods of rebooting after flashing, all boots into encrypted twrp.
i hope there is a solution, i can't try anything now, there is a 24hour waiting period to unlock more than 1 bootloader a day

IceMan on xiaomi.eu has a working twrp;
TWRP 3.3.2-2 RN7 by IceMan

Aaagogo said:
i can access fastboot with no problems, it's booting into recovery that doesn't work
i am using twrp from the official thread;
https://forum.xda-developers.com/redmi-note-7/how-to/one-redmi-note-7-unlock-bootloader-t3890751
same thing happen on all 3 methods of rebooting after flashing, all boots into encrypted twrp.
i hope there is a solution, i can't try anything now, there is a 24hour waiting period to unlock more than 1 bootloader a day
Click to expand...
Click to collapse
Which is the principal problem?
Does the smartphone not start? I mean, the operating system.
Because if that's the problem, and you can start in "fastboot" mode, you can install your official ROM with MiFlash.
And reinstall TWRP, Orange Fox for example.
Regards!

hugomoya said:
Which is the principal problem?
Does the smartphone not start? I mean, the operating system.
Because if that's the problem, and you can start in "fastboot" mode, you can install your official ROM with MiFlash.
And reinstall TWRP, Orange Fox for example.
Regards!
Click to expand...
Click to collapse
every method of twrp with the "unofficial" twrp from the link to boot into encrypted twrp, can't install magisk for twrp to take
https://forum.xda-developers.com/redmi-note-7/how-to/one-redmi-note-7-unlock-bootloader-t3890751
twrp from link above
normal reboot goes into encrypted android
fastboot no prob

Aaagogo said:
every method of twrp with the "unofficial" twrp from the link to boot into encrypted twrp, can't install magisk for twrp to take
https://forum.xda-developers.com/redmi-note-7/how-to/one-redmi-note-7-unlock-bootloader-t3890751
twrp from link above
normal reboot goes into encrypted android
fastboot no prob
Click to expand...
Click to collapse
Try with Orange Fox R10.0 Stable (Based in TWRP 3.3.1)
https://sourceforge.net/projects/orangefox/files/lavender/
Regards!

hugomoya said:
Try with Orange Fox R10.0 Stable (Based in TWRP 3.3.1)
https://sourceforge.net/projects/orangefox/files/lavender/
Regards!
Click to expand...
Click to collapse
cheers for that, i'm using twrp 3.2.3-2 RN7 by IceMan over at xiaomi.eu