Hi,
On my Mi5 I wanted to put TWRP as recovery in order to flash a custom ROM. Device was unlocked using the chinese dev. rom( checked settings - root access)
I go into bootloader flash the latest twrp 3.0.2-1-gemini and boot into it. Nothing more happens then the splash screen.
Any suggestions what I maybe did wrong? Tried more than one step-by-step guide but can't make it.
Thx
I have the same issue. I thought I solved it by using the previous version (3.0.2.0), which worked the first time, but not the following ones
yes i also experience this problem. It got stuck on TWRP logo. And when i try to reboot and enter recovery mode, the stock recovery replaces TWRP. Hope someone can help us? I'm using twrp-3.0.2-1-gemini.
This is a well known problem. Flash 3.0.2-0 and it will go away.
Sent from my MI 5
yoocharns tip worked - installed that version from twrp gemini section and got into TWRP.
TY
Related
hello.
since last week I blocked my memul I did some more search and followed the following howto:http://forum.xda-developers.com/showthread.php?p=64018011#post64018011
And used the firmware from here: http://forum.xda-developers.com/one-mini-2/general/stock-ruu-rom-recovry-htc-one-mini-2-t3250020
At the end, my phone is blocked again.. I certainly did something wrong, but I don't know what.
I've followed the guide and flashed the sock firmware for my phone but now when it boot up, I'm stuck on the boot screen (HTC , powered by android - attached image1.jpg) and nothing append. If I try power+vol down it take a screenshot (attached - image2.png).
I managed to flash back the TWRP but my backup are gone. I've a copy on my computer, but I don't know how to restore my phone.
What's the best option? flash a new rom or restore my backup? Either way, how I do that?
Thanks for your answer,
ciao
Problem solved. I managed to flash a CM rom through the adb sideload in the TWRP recovery!
deleric said:
Problem solved. I managed to flash a CM rom through the adb sideload in the TWRP recovery!
Click to expand...
Click to collapse
I am back to stock rom can you help me ?
Hey,
I'm not really sure were to post this, hope it's not wrong here.
I have an elephone p8000 running Cyanogenmod 12.1.
I installed xposed framework (https://forum.xda-developers.com/xposed/super-alpha-posted-permission-xposed-t3072979) via twrp using the app fllashify, everything was still working. Then I activated the module from this link https://forum.xda-developers.com/xposed/super-alpha-posted-permission-xposed-t3072979, wanted to reboot and got stuck in a bootloop.
Now I can enter the screen were you can choose Recovery, Fastboot or Normal boot, but alle three options lead to a bootloop.
Also got no AdbDrivers on my computer, as I entered TWRP custom recovery via flashify.
Can anybody help me what to do get out of the boot loop?
Would be so thankful!
Cheers,
tie
How did you solve it??
after losing my mind because all the methods to install twrp and root my device, i decided to start from here: https://twrp.me/xiaomi/xiaomiredmi4x.html
and use the Fastboot Install Method, i followed the tutorial, boot my phone, have the "password issue" > wipe data > and reboot again to a bootloop nightmare.
now its a bit tricky, but i can enter into twrp, if i put new rom on my SD card and flash it with twrp, will it solve the problem ? any suggestions ?
my phone BL is unlocked but its not rooted yet, any restart attempt via twrp, ends with endless mi logo
thank you.
clean flash new rom from twrp, issue will be solved.
i have try to flash new rom (miui_HM4XGlobal_V8.5.2.0.MAMMIED_973da51a2e_6.0), the process went well but my device is still in bootloop. is there any recommended rom for that situation ?
psoneseven said:
clean flash new rom from twrp, issue will be solved.
Click to expand...
Click to collapse
inCider said:
i have try to flash new rom (miui_HM4XGlobal_V8.5.2.0.MAMMIED_973da51a2e_6.0), the process went well but my device is still in bootloop. is there any recommended rom for that situation ?
Click to expand...
Click to collapse
new rom bootup takes 7- 15+ mins, give it time, or try to flash any custom rom.
Flash stock ROM via mi flash then it boots up,it takes little longer time to boot.
All the best....
An update...
As a professional noob, i have installed twrp and then reboot without rooting, so the device went into loop, rooting the device solved the problem, now i am happy.
Thank you and sorry for the hassle.
inCider said:
An update...
As a professional noob, i have installed twrp and then reboot without rooting, so the device went into loop, rooting the device solved the problem, now i am happy.
Thank you and sorry for the hassle.
Click to expand...
Click to collapse
Or you needed just simple wipe dalvik/cache
tried that of course and it didn't help .
Jakuza001 said:
Or you needed just simple wipe dalvik/cache
Click to expand...
Click to collapse
inCider said:
An update...
As a professional noob, i have installed twrp and then reboot without rooting, so the device went into loop, rooting the device solved the problem, now i am happy.
Thank you and sorry for the hassle.
Click to expand...
Click to collapse
The weird thing is how could you achieve rooting the device if when in a bootloop because TWRP + reboot leads an zero SD storage and you cant mount anything... I mean, how could you flash the zip from nowhere? and solve the storage thing btw (its encrypted)
inCider said:
after losing my mind because all the methods to install twrp and root my device, i decided to start from here: https://twrp.me/xiaomi/xiaomiredmi4x.html
and use the Fastboot Install Method, i followed the tutorial, boot my phone, have the "password issue" > wipe data > and reboot again to a bootloop nightmare.
now its a bit tricky, but i can enter into twrp, if i put new rom on my SD card and flash it with twrp, will it solve the problem ? any suggestions ?
my phone BL is unlocked but its not rooted yet, any restart attempt via twrp, ends with endless mi logo
thank you.
Click to expand...
Click to collapse
Here are the steps I followed:
Go to fastboot (volume down + power)
Go to twrp by running `fastboot boot twrp-3.2.1-0-santoni.img`. i.e. Flashing and getting into recovery is a tricky thing.
Install miui if it is not installed, by downloading miui rom from their site.
Install lazy flasher to disable dm-verity. - https://forum.xda-developers.com/xi...very-recovery-redmi-4x-redmi-4-india-t3613560
Restart the phone. You should see 3 moving dots in the bottom area of the screen. It took around 7 mins to boot.
Hello guys!
Yesterday I tried to flash the newest Lineage-built to my new G7+ (XT1965-3, bought in Germany via Amazon), but something went wrong and now I'm afraid, I bricked my phone.
It's not my first flash of Lineage, as I did this in the past already on some older Phones (SII, SIII, S5), but it's the first time, that I have a major issue.
So I followed all the steps on the Lineage-Wiki (on Win10).
After flashing the recovery (the lineage-recovery, not TWRP) I wasn't able to enter the recovery-mode, so the phone booted to StockRom. And probably this was the problem: As it didn't react to VolumeDown+Power, I reflashed the recovery a second time. After that the touch-screen is not working any more.
I am able to enter the recovery-mode and I can boot to Stock-Rom, but in both modes the phone does not react to touch, so I can only use the Volume- and Power-Buttons.
Probably I made more mistakes after that: I thought, that a factory-reset would help, but It didn't. I also relocked the bootloader, but as I saw, that it also did not bring any solution, I unlocked it a second time.
Conclusion: I have a brand new phone, with lineage-recovery, an unlocked bootloader but without touch working.
I also tried to flash Lineage, but the sideload got stuck at 47%. So Lineage is not installed and it boots into Stock, where I can not get any further without touch.
Has anyone any idea, what could be the issue and how I can fix it? I would like to start from scratch, but I don't know, what is the exact problem and if i can for example return to stock recovery.
Thank you!
---- EDIT ----
If it helps: I am able to boot TWRP via "fastboot boot twrp-xxx.img". And in TWRP the touch works!
I could flash lineage directly via TWRP from external sd-card, but i am afraid that after that I won't be able to return if something goes wron.
probably your best bet is to go right back to stock using the LMSA tool and starting fresh. I've seen others encounter similar issues on different devices and always the cleaneast solution was just to role back everything and start over.
Thank you so much. With LMSA I managed to restore everything to stock and touch is working!
So I'm going to start from scratch and finally install Lineage.
Is is indicated to use the Lineage-Recovery, as the Lineage-Wiki says, or would it better to use TWRP?
TWRP gives me the option to flash from sd-card, which seems to me better than via sideload.
joglxv said:
Thank you so much. With LMSA I managed to restore everything to stock and touch is working!
So I'm going to start from scratch and finally install Lineage.
Is is indicated to use the Lineage-Recovery, as the Lineage-Wiki says, or would it better to use TWRP?
TWRP gives me the option to flash from sd-card, which seems to me better than via sideload.
Click to expand...
Click to collapse
Glad your back up and running. Take a look in the lineage thread, but it does appear most people lean towards using twrp, shouldnt have an issue with either however.
digitaljeff said:
Glad your back up and running. Take a look in the lineage thread, but it does appear most people lean towards using twrp, shouldnt have an issue with either however.
Click to expand...
Click to collapse
I'm having a similar problem. At first touch was fubar but I was able to return to stock using LMSA and now touch works. I can load TWRP with fastboot and even install a custom ROM and TWRP, but installing any custom ROM results in a boot loop during the finding and installing updates part of the phone setup during first boot. I'm tried Evolution X which I was running previously(for about a month, and then a boot loop started yesterday), PixelOS 10, and AncientOS, but all result in the boot loop on first boot after connecting to wifi.
Fixed
I fixed this somehow by manually flashing the latest stock firmware to slot a, and then extracting the evolution x Rom and manually extracting the IMG files inside and manually fastboot flashing those to slot b. I then set b as the active slot and booted up, patched the boot image with magisk, flashed that, and everything works. Not sure why twrp wouldn't do the trick.
Finally had the time to install Lineage. Now everything works.
I followed the instructions someone posted in the [ROM][OFFICIAL] LineageOS 17.1 [nightlies]-thread and the instructions of the lineage-wiki:
1. fastboot boot TWRP
2. sideload the copy-partitions.zip from lineage-wiki
3. factory reset via TWRP (wipe cache, dalvik and data)
4. sideload lineage
5. reboot bootloader
6. fastboot boot TWRP
7. sideload magisk
8. reboot system
Had a little bootloop the first time rebooting the system, but that was because I forgot to wipe data-partition in step 3. Wiping data and rebooting did it for me.
So I have a working Lineage17.1 with root via Magisk.
Thank you for the help!
I had exactly the same problem like you had. Bought a brand new moto g7 plus and after recovery flash, Touchscreen was not working anymore. I could manage to go back to the bootloader, sideloaded TWRP, but side loading lineage worked for me then. It seemed to be stuck on 47 percent, but this seems to be a normal issue, the file was there and after installing, touchscreen worked normally.
Hi,
I decided to try to install the custom lineage ROM that was here.
I downloaded the ROM, followed the steps to install orange fox custom recovery. I flashed the ROM, rebooted and got stuck on the realme logo. Luckily I was able to bypass this boot loop and get back into recovery. Now that I am there, I just want to revert my phone to stock to avoid any more issues. My Bootloader is unlocked.
Question: How do I revert my phone to completely stock Realme X2 Pro / realme ui 1.0. I have an .ozip file containing the stock ROM. I do not want to permanently brick my device, please help. How do I revert all the partitions/ROM back to normal. Thank you.
EDIT: I tried flashing the ozip file, but when I rebooted it was still stuck on the logo screen. What should I do?
The issue has been solved, thank you.
Try to help me
realmenewb said:
The issue has been solved, thank you.
Click to expand...
Click to collapse
What did you do, brother? I want to return from ligaeos to the official rum?
realmenewb said:
The issue has been solved, thank you.
Click to expand...
Click to collapse
Please try to post how did you solve it before just signing off. Thats the purpose of posting in forums - that information is archived and available to anyone in need in the future. :highfive:
Relevant comic https://xkcd.com/979/
I had the same problem just yesterday and i have successfully locked the bootloader and am back to stock rom.
Now this is not my method i read it here on xda but cant find that thread now.
First of all go to fastboot and in cmd type fastboot -w (this should wipe internal storage)
Then boot into recovery
Go to advanced wipe(cache, dalvik, system,data)
Go back into wipe menu and do format data and press yes.
Then reboot to recovery through reboot menu in recovery
It will ask for conformation as no rom is installed but continue to reboot.
Then flash the ozip(if you have a recovery compatibe to flash ozip otherwise use alpropriate zip file for flashing rom. In my case i had unofficial twrp).
After flash completes dont do anything and just reboot to system this should replace custom recovery with stock one.
Then reboot to recovery to check if it is replaced with a stock one.(Never try to lock bootloader with custom recovery installed it will hard brick your device.)
Then if stock recovery is installed reboot to bootloader and in cmd type
Fastboot flashing lock
Then accept the msg on phone to lock bootloader it will wipe your data and then you will have a phone with locked bootloader.
I again want to inform you that this is not my post but i had read it somewhere on xda i will try to find it and then put a link to it here.