Related
I have successfully unlocked bootloader on 20s and then tried to flash a third-party rom from Cydras, which didn't work out. So in TWRP i chose to restore EUI from backup. After that the phone powers up and everthing works fine until the color-changing EUI logo appears... and that's where it gets stuck, not going beyond this point ever.
I tried to push an image to /sdcard/ but it said the directory is not there? That was when ADB/Fastboot was still able to see the device, it isn't any longer.
This means I can't get to TWRP and/or push a ROM to the device.
I can enter Fastboot Mode by pressing the Vol and Power buttons but this is no help as ADB/Fastboot doesn't see the device in this mode either.
Any ideas would be appreciated. Thanks in advance and good karma to everyone
Anyone?
Would appreciate input! Thanks!
Without ADB or fastboot, I can't think of anything else you can do. If the phone is going into the fastboot mode, you need to figure out why your computer is not connecting to it.
Thank you for your note!
It's going into Fastboot mode by pressing Vol+/Power. It also goes into stock recovery but that one does nothing - it does wipe it seems but the only other option is to install update - which clearly isn't on my phone.
What could be the reasons my computer stopped seeing the device?
Strange: If I put the phone in Fastboot mode, my PC identifies it and starts showing Kedacom USB Device - Android Bootloader Interface in Devices.
Fastboot does actually see it and can perform a few commands. ADB, on the other hand, does NOT see it. What options do I have? I could push TWRP image to the phone. Is there anything else I could do now?
Please help! And thanks!
If you have access to fastboot, either flash or boot TWRP image and see from TWRP if the old backup is still accessible.
Thank you. Did just that but there's nothing there to recover, unfortunately. And I thought about installing system via Fastboot but can't find a system image (.img) anywhere
Please help!
Thanks!
Boot into TWRP and while in TWRP, see if the ADB works.
If ADB works, then push one of the TWRP backup zip file to the data memory and the recover from TWRP.
see guide on leeco . re fourms
crukkh said:
Thank you. Did just that but there's nothing there to recover, unfortunately. And I thought about installing system via Fastboot but can't find a system image (.img) anywhere
Please help!
Thanks!
Click to expand...
Click to collapse
you need to use flashone 2.0 for leeco pro3 google it.
crukkh said:
Thank you. Did just that but there's nothing there to recover, unfortunately. And I thought about installing system via Fastboot but can't find a system image (.img) anywhere
Please help!
Thanks!
Click to expand...
Click to collapse
If you can enter Fastboot mode this will work. You can flash Fastboot rom (stock Eui 5.8.17S China), then you can start all over from there. It will erase everything on the phone so do backup everything. You will need to redo-unlock bootloader and re-install TWRP recovery.
Link for the Fastboot rom with how to flash it here:
https://forum.xda-developers.com/showpost.php?p=73913013&postcount=240
After flash if it show storage free space not correct install TWRP and go to Wipe > Format data, it should fix it.
---------- Post added at 01:26 PM ---------- Previous post was at 01:22 PM ----------
crukkh said:
I have successfully unlocked bootloader on 20s and then tried to flash a third-party rom from Cydras, which didn't work out. So in TWRP i chose to restore EUI from backup. After that the phone powers up and everthing works fine until the color-changing EUI logo appears... and that's where it gets stuck, not going beyond this point ever.
I tried to push an image to /sdcard/ but it said the directory is not there? That was when ADB/Fastboot was still able to see the device, it isn't any longer.
This means I can't get to TWRP and/or push a ROM to the device.
I can enter Fastboot Mode by pressing the Vol and Power buttons but this is no help as ADB/Fastboot doesn't see the device in this mode either.
Any ideas would be appreciated. Thanks in advance and good karma to everyone
Click to expand...
Click to collapse
If you can enter Fastboot mode, you can flash Fastboot rom in the link:
Link for the Fastboot rom with how to flash it here:
https://forum.xda-developers.com/sho...&postcount=240
Hi All,
I have a Zuk Z1 and i used twrp to install lineage and there came a instance of factory reset and finally now my phone's dead with powers. Kindly help me recreate the best out of my phone
I have twrp with terminal access. Adb sideload works , installs cyanogenmod but doesnt boot. Just keeps booting to twrp.
When connected the device has "adb unauthorized".Even after trying all kinds of adb and fastboot install. Official lenovo usb drivers and also from xda's posts.
Now only option for me is to push the cyanogenmod os to sdcard and use terminal from twrp to make things right.
Can anyone kindly help me with this.
Thanks and Regards,
napdrag0n
Which (version)twrp you were useing.
nishu2878 said:
Which (version)twrp you were useing.
Click to expand...
Click to collapse
its TWRP 3.0.2-0
napdrag0n said:
its TWRP 3.0.2-0
Click to expand...
Click to collapse
Firstly if you boot into twrp than flash recovery twrp 2.8.7.0 ham and reboot into recovery.
I also face this problem. when i did reset, phone goes in twrp but the reset command didn't work then i manually factory reset and reboot but its reboot into twrp not system.
Sorry for bad English brother but this will going to solve your problem.
This procedure is intended for oreo users only !
WARNING : This is a Beta Build and is not completely stable. ANY data loss or bricked phones is not my or any of the Telegram members' responsibility. You and only YOU are responsible for the consequences.
The TWRP provided is a Beta Build by Telegram Group member Maanush. All credits go to him and the all other members of Telegram Group.
TWRP(Beta) : http://www.mediafire.com/file/7p7ida6ems0ta9l/TWRP_BETA_BUILD.img
Tutorial :
1. adb reboot bootloader
2. fastboot oem unlock
3. fastboot flash recovery twrp.img
4. fastboot oem reboot-recovery
After flashing TWRP:
1. Flash Force Encrypt Disabler.zip
2. Flash Magisk.zip
3. Wipe Dalvik/Cache
4. Format Data
6. Reboot
Not working
Sir, there is an error with magisk merge.img mount falied. Please help...
Akash.sep28 said:
Sir, there is an error with magisk merge.img mount falied. Please help...
Click to expand...
Click to collapse
If you're facing issues while flashing magisk modules then you might have done something wrong. Remember that you have to flash force encrypt disabler and format data after that
Sir
After flashing twrp my device restore stock recovery.
Sir I want only twrp recovery install on it.
So I can make backup
Help
CodeNameMadmax said:
Sir
After flashing twrp my device restore stock recovery.
Sir I want only twrp recovery install on it.
So I can make backup
Help
Click to expand...
Click to collapse
After successfully flashing image, write 'fastboot oem reboot-recovery'. Your device will boot into a black screen, now double press the power button, swipe to unlock. You will have to flash magisk zip(use adb sideload or flash from sd card) to prevent system from replacing TWRP.
Remember that you'll have to format your device once to be able to access internal storage so that you can restore backups
My phone not entering into the recovery mode
does the twrp3.1.1.0 work for 5 nov security update?
guys will the the old twrp3.1.1.0 for oreo works on latest 5 nov security patch
prashanth_a_r said:
guys will the the old twrp3.1.1.0 for oreo works on latest 5 nov security patch
Click to expand...
Click to collapse
Yes
sarathkrish02 said:
My phone not entering into the recovery mode
Click to expand...
Click to collapse
How are you trying to enter recovery mode?
Anas Rahman said:
How are you trying to enter recovery mode?
Click to expand...
Click to collapse
Now I can enter into twrp but tell me how to fix 0mb internal storage
sarathkrish02 said:
Now I can enter into twrp but tell me how to fix 0mb internal storage
Click to expand...
Click to collapse
Follow the steps that say "After flashing TWRP"
sarathkrish02 said:
Now I can enter into twrp but tell me how to fix 0mb internal storage
Click to expand...
Click to collapse
Or Google the same thing U will get the perfect answer even I had the same issue
About installation on twrp recovery
iam using lenovo k8 note. i have tried to install twrp recovery but i cant able to install it. i hve tried all the ways like using cmd all the cammands. after i complete flashing twrp and booting again it displays like "orange state " ,"device has been unlckd and cant b trusted" ,"your device will boot in 5 sec" after that my phone restarts and nothing happens . i have tried all possible ways . pls hlp me to install twrp .
salam... i m not entering into twrp recovery mode by this command "fastboot oem reboot-recovery" also tried to switch off cel phone with vol up+vol down+pwr btn and then vol+up and pwr btn but not entered... also tried with vol+down and pwr btn and select recovery mode but fail....
Finally i got my cell rooted successfully here is right twrp for lenovo k8 plus. All credit goes to @anasrehman @kqixs
https://androidfilehost.com/?fid=1322778262903998122
Hi, I have the same issue and I tried all the possible ways but nothing. Can anyone tell if got the same issue but got resolved
no usb debugging
currently my phone is switched off. I am able to go into normal recovery mode. I think the USB Debugging mode is off. How can i revive it again. I was thinking of applying from SD Card a custom ROM flashing. But how to unroot it first
Twrp Oreo Manning
I am just facing one major problem, every time I reboot my device It seems to be my recovery keeps installing again and again which means it's always so my internal storage - 0, after the formatting it reads it but after a new reboot, it doesn't.
Is this working now?
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
Hello,
After unlocking my bootloader, I managed to install TWRP. As indicated in the tutorial in fastboot mode (volume + and input) I managed to enter TWRP mode, except during a new boot impossible to start in TWRP mode I find the recovery of MI, after looking on the net, I didn't find anything really concrete I wouldn't want to brick my phone, does anyone have a solution?
Thanking you for your collaboration
(Sorry if this topic has already been covered in this forum but I couldn't find anything concerning the MI 9T), thank you if possible to detail the manipulation, I know nothing about it
This is from the twrp website https://twrp.me/xiaomi/xiaomimi9t.html
Note many devices will replace your custom recovery automatically during first boot.
Click to expand...
Click to collapse
After flashing the recovery :
Code:
fastboot flash recovery twrp.img
enter the code to reboot in recovery :
Code:
fastboot oem reboot-recovery
DELLINSPIRON1958 said:
Hello,
After unlocking my bootloader, I managed to install TWRP. As indicated in the tutorial in fastboot mode (volume + and input) I managed to enter TWRP mode, except during a new boot impossible to start in TWRP mode I find the recovery of MI, after looking on the net, I didn't find anything really concrete I wouldn't want to brick my phone, does anyone have a solution?
Thanking you for your collaboration
(Sorry if this topic has already been covered in this forum but I couldn't find anything concerning the MI 9T), thank you if possible to detail the manipulation, I know nothing about it
Click to expand...
Click to collapse
U have to flash the modified vbmeta.img in order to keep a custom recovery..
Hello ,
There is no other solution ?
DELLINSPIRON1958 said:
Hello ,
There is no other solution ?
Click to expand...
Click to collapse
Have you tried by forcing reboot to Recovery/TWRP right after flashing TWRP (answer from another user, post #2):
>>fastboot oem reboot-recovery
Are you using e.g. the official TWRP 3.4.0, and did you enter in TWRP your Android screen unlock code, for TWRP to be able to properly work with File Systems on Data and Internal memory?
I am a neophyte, can you give me precise details of the method, thanking you
DELLINSPIRON1958 said:
I am a neophyte, can you give me precise details of the method, thanking you
Click to expand...
Click to collapse
Read post #2 - if you are not familiar with Fastboot, please search by Google and read - but how else did you flash TWRP than from Fastboot.
After flashing TWRP from Fastboot (1st command), use 2nd command to force direct rebooting to TWRP - without pinpointing with Vol+&Pow buttons, etc.
But really, nothing else, just that
Search here for thread about Official TWRP 3.4.0, download and flash that TWRP for davinci
When you enter to TWRP, it will ask you for your Android screen unlock pin/password (you should know your own one you use when booting to Android and when you are unlocking the locked screen in Android), enter that one when TWRP prompts you and wait few seconds (it should report success)
There is no rocket science here to teach more about ?, you just need to follow and try
Thanks for the information, I'll try. However, are you sure that I will have TWRP as a start-up recovy and that every time I do Volume + Enter? ( translate google)
DELLINSPIRON1958 said:
Thanks for the information, I'll try. However, are you sure that I will have TWRP as a start-up recovy and that every time I do Volume + Enter? ( translate google)
Click to expand...
Click to collapse
Try as described above:
- download official TWRP for davinci
- flash from Fastboot and reboot to TWRP with the given command
- in TWRP, enter your Android screen unlock code and check does TWRP correctly read your files on Internal memory (e.g. seeing proper file names in Download, not some garbage names)
- try to reboot to recovery (by TWRP command or by using Vol+) and check if it reboots to TWRP, not to stock Recovery
Please don't waste time by further endless questions, until you first try and have concrete questions/results (can't expect that people will pay attention to answer if you at least don't even try - why should then anybody waste the time)
I can't guarantee you 100% but I always have bootable TWRP, properly reading Storage (I also have boot.img patched by Magisk, hence not 100% same environment like you)
Thank you for your "kindness" If I ask myself several questions it is not when the phone is blocked on it is necessary to ask questions
I had the same issue, I tried everything event then wasnt able to boot to Ofox recovery. But someone suggested, to flash the recovery, get into it WITHOUT booting to system, then flash magisk. Now reboot to system and uninstall magisk/Flash/do whatever you want! That worked for me.
thank you for your reply. while searching on the net, I noticed that there are several answers to this problem, but which one is the right one?
without the phone being out
DELLINSPIRON1958 said:
Thank you for your "kindness" If I ask myself several questions it is not when the phone is blocked on it is necessary to ask questions
Click to expand...
Click to collapse
For each member you can simply judge the credibility of his posts by his 'degree' on XDA forum, for which devices and topics he mostly diiscusses about and how many people thanked his posts
E.g. if I ask how to flash Xiaomi, Mi 9T and receive a suspicious 'guide' from somebody who only participated in discussions about Nokia phones, and who even did not get Thanks there for his participation, I will probably fully ignore and not risk to brick my phone
But if I get an answer from somebody who maybe participated for a year or two in topics on Poco and Redmi Note but who got hundreds of Thanks for his posts there, I will consider that he likely very well knows about flashing Xiaomi phones, although maybe never had Mi 9T in his hands.
Moreover, if I see that two or more people guide me in the same direction.
So I would at least google myself for more info (and then ask if still something not clear), and try - specially if that what was suggested does not sound as something to potentially brick my phone
After all, this is hackers forum and everybody is responsible himself for his phone. But on the other side, nobody was born with the knowledge but learnt by searching, reading and trying things herself
Also, everybody helps for free and by his good will, and sooner or later finds useless to waste time to answer for something that was already answered by his best (what else/new to answer), but the other one did not even want to try
Of course (as also in my previous post), things work for me as you wanted but yes, I always immediately flash together the boot image patched by Magisk.
So you can try would it work with the fully stock Boot - if yes, good for you.
If not, you can consider going to root by Magisk (although, being so cautious, it would probably take much more time and many, many more new questions before ?)
Kaiwalya said:
I had the same issue, I tried everything event then wasnt able to boot to Ofox recovery. But someone suggested, to flash the recovery, get into it WITHOUT booting to system, then flash magisk. Now reboot to system and uninstall magisk/Flash/do whatever you want! That worked for me.
Click to expand...
Click to collapse
So just tested the following on my MIUI 12.0.2 QFJEUXM, with (unofficial) TWRP 3.4.0.2 from brigudav and Canary Magisk 20424
- Booted to TWRP and flashed stock 12.0.2 eea Boot.img
- Immediately rebooted back to Recovery - that is to TWRP and (that step is also important!) entered my Android screen unlock pin to assure that TWRP 'touched' the Data
- Rebooted to Android (System), where ofc, Magisk Manager showed that Magisk was no more installed
Then rebooted to Recovery (by keeping pressed Vol+) and phone booted to TWRP, not to the stock Recovery!!!
Hence the stock Boot image did not overwrite my TWRP with stock Recovery (although without having Magisk flashed at the time), because of properly doing each and every step as above!
(At the end, flashed back my patched Boot.img from TWRP, rebooted to Android and continued to use Magisk with all previously installed modules, etc)
Btw, I have never flashed any VBMeta, decrypted storage or so
PS:
And believe me, I lost myself TWRP many times (having to reflash it from Fastboot again and again when I was uninstalling Magisk, updating MIUI from TWRP and so), before learning that every step counts?.