startup problem after installing new ROM by TWRP - Xiaomi Redmi Note 5 Pro Questions & Answers

after receiving a phone with a problem Gyro sensors and aceelérmetre, I tried to solve the problem by installing twrp and trying other ROMs, but one moment the phone does not want to start and stays every time in the start screen installation infinitly
i still have access to twrp, and i tried all knowns solutions except flashing throw EDL mode
Please help me

More details required!
What rom did you try to install.
And before testing other roms. You should have checked that it wasn't a hardware problem (faulty device) with stock rom.
^^^ Tap on kernel version a few times in about would open a service menu, where it is possible to test hardware.
MIUI doesn't boot with TWRP installed if you don't flash lazyflasher or use a TWRP version that includes it.

Question: does your phone stay permanently in this mode? What rom did you install and what type of ARP do you have? What version of twrp do you have? I remember I had the same issue because I force encrypted my phone accidentally but then it just didn't start sometimes. That's why I am asking.
Option 1: go back to twrp -> format your device (should erase all sort of encryption and it has the same effect as a factory reset as well) -> reinstall custom rom and your stuff again -> flash lazy flasher or Magisk (that should take care of dm verity & force encryption as well).
Option 2: check your ARP version (fastboot getvar anti) custom roms usually don't have any firmware whatsoever and as long as you don't downgrade you are safe anyway. Just to be safe: if you are on version 3 everything should be fine, if you are on 4 you have to do some research what to do but it's not a big deal to be honest.
Option 3: Install redwolf instead of twrp (then you don't need to flash lazyflasher as well) -> install rom.
Tell me if anything has worked.
Installing recovery either via fastboot flash recovery recovery.img -> power off -> power on + volume up -> allow modification to system partition.
Or do it like fastboot boot recovery.img -> install (in your recovery) -> select image (bottom right) -> flash recovery.img (works especially good with ARP v4)
Either way after that do your thing in case you want to change/update your twrp or redwolf.

Boot screen problem
I am using orange fox recovery r10. When i flash havoc os 3.0, evolution x os and other os it always stuck in boot screen. It just opens with the pixel experience rom only. And when i tryed to restore my phone rom it shows "mount read only" . I am using redmi note 5 pro (whyred). Please help me to solve my problem.

if i were you, i will boot to twrp - boot to fastboot - flash miui using fastboot. if you're not confident google how to do it.

Related

Device bricked? No adb-access

Hello!
My Oppo Find 7 (international) seems to be bricked.
I'm on stock ROM COS 1.2.5 with stock recovery 1.0
After booting it stuck in the Setup-Wizzard with "settings has stopped"-Loop.
Unfortunately in stock-ROMs the USB-debugging is disabled, so i can't acces via adb fastboot to flash other recoverys.
And cause of the loop i can not enable USB-debugging...
The recovery (stock 1.0) let me only flash 1.2.5, no other ROMs work.
Things that work:
- entering fastboot (but no access via adb as i wrote)
- entering recovery and execute "zip from sd" (while sd means only internal sd here)
- normal boot to the f****** Setup-Assistant, enter PIN. At slect Language the "setting has stopped"-loop starts
- while the device is in loop, i can access the internal and external SD-card via PC, copy and delete files works
Please, has anybody an idea what to do ?
Thanks to all
Marco
Since you can get into fastboot, download a custom recovery, go to fastboot, type
fastboot flash recovery x
Replacing x with the full name and extension of the file, and install a ROM. Alternatively, if you want ColorOS, try downloading 1.2.4i, and installing it through the stock recovery. Then you can update from there
Hmmmm....
Positive! At this moment i learned that USB-debugging is needed for adb-access on a booted device, not for fastboot-access
Yes, i could flash TWRP via fastboot (puuhh, not bricked)
THANKS !!
Now i can mess around the "settings has closed"-Loop, wich is still in place.
(No wiping fixes the problem, even 1.2.1 nor 1.2.3 or whatever)
But i'm on the road again and can check out fixes.
Thanks again!!
That's weird. Did you ever install custom ROMs before having this issue?
Did you try formatting System in TWRP? But be careful, when you format System you have to install stock Color OS BEFORE rebooting your device. That means stay in TWRP after you format and install the ROM, then reboot.

OnePlus 3 bootloader defaulting to recovery

Hello,
I am having a problem where my phone is only, as far as I can tell, willing to boot into recovery. From the system, doing a normal reboot ends up in recovery, from powered off it goes into recovery, rebooting from recovery to system ends up back in the recovery, and the fastboot menu's "Continue" option goes reboots to recovery. The only way I can get into the system is to boot via fastboot -- i.e.,
Code:
fastboot boot boot.img
Where boot.img is the one packaged with the rom I am currently running.
This is not convenient because I need to connect it to a computer!
Is there some way to tell the bootloader to not boot recovery by default?
I have tried simply flashing the boot.img from above with:
Code:
fastboot flash boot boot.img
Which doesn't have any noticeable effect.
I suspect I broke something last night kicking around. I flashed the Open Beta 10 Modem & Firmware, then flashed the Open Beta 10 recovery, before changing my mind and installing TWRP 3-28 and Resurrection Remix v5.8. Somewhere in there, fastboot -w got run, but I don't think I did anything else potentially destructive.
Thanks for reading!
Hmm... Try install boot into recovery partition and recovery into boot? I know it's sound like a joke, but it will probably help you while u wait for a beter solution or just solution to repair that problem.
Anyway - maybe try flash old MM firmware?
A solution for me...
For anyone who rolls along and sees this in the future, my fix was:
0. Take a backup of sdcard AND data -- Step 2 will wipe data and sdcard without asking
1. Download the official recovery for the OnePlus 3
2. Use fastboot to boot (I didn't even have to flash) the official OnePlus 3 recovery AGAIN: WARNING: This step wipes all data without asking for confirmation!!!
I have now installed TWRP-3.0.4.0 and Resurrection Remix v5.8.1-20170202 and everything seems to be working just fine.
Thanks to @sylviohneto for finding this fix here: https://forum.xda-developers.com/oneplus-3/help/critical-bootloader-boot-recovery-fresh-t3530283
I had same problem so for that just take nandroid backup of data and while in turn copy it to pc and any other backup of data you need then format all the partions and reinstall rom and restore data... And if your lock screen have security then check Google you will have to delete a file called locscreen.db from file manager in twrp to access your phone

PLEASE Help | DM-Verity and PASSWORD when loading

Hello. OnePlus 3. Strange problems. I can see DM-Verity 50/50. And 50/50 need type password to start system. Need press "BACK" or type password from system (standard android, pin-code/graphical key, etc.)
I flash stock OxygenOS via stock recovery with full wipe (erase everything) but have bootloop, if force reboot - loading successful, but reboot next time, modem(connection) don't working.
I tried this method and deleted DM verity, but entering the password is also required.
Next reboot DM-Verity remains.
https://forum.xda-developers.com/oneplus-3t/how-to/fix-dm-verity-warning-final-fix-4-0-3-t3555094
Also i tried mega unbrick method, using programm (1GB)
https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
This installed OxygenOS ~3.1.2. But problems remains.
TWRP now. I can't flash stock recovery via fastboot flash recovery recovery_op3.img
Ok it's flashes, but when i try enter - black screen and smartphone off.
What need make, that would completely remove DM-Verity and password. And flash latest stock recovery and OxygenOS.
Mega Please Help.
GO!
SunEpicMist said:
Hello. OnePlus 3. Strange problems. I can see DM-Verity 50/50. And 50/50 need type password to start system. Need press "BACK" or type password from system (standard android, pin-code/graphical key, etc.)
I flash stock OxygenOS via stock recovery with full wipe (erase everything) but have bootloop, if force reboot - loading successful, but reboot next time, modem(connection) don't working.
I tried this method and deleted DM verity, but entering the password is also required.
Next reboot DM-Verity remains.
https://forum.xda-developers.com/oneplus-3t/how-to/fix-dm-verity-warning-final-fix-4-0-3-t3555094
Also i tried mega unbrick method, using programm (1GB)
https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
This installed OxygenOS ~3.1.2. But problems remains.
TWRP now. I can't flash stock recovery via fastboot flash recovery recovery_op3.img
Ok it's flashes, but when i try enter - black screen and smartphone off.
What need make, that would completely remove DM-Verity and password. And flash latest stock recovery and OxygenOS.
Mega Please Help.
Click to expand...
Click to collapse
try this
https://forum.xda-developers.com/oneplus-3/how-to/fix-device-mapper-verity-simple-trick-t3530685
Restore to latest Marshmallow firmware.
Be sure to have locked bootloader (both from ADB and developer settings), then upgrade via OTA.
You just have to check and confirm for update.
It worked for me

Starting to system takes me to recovery

Hi all,
- bootloader is unlocked
- I have latest OOS installed (9.09 I think?)
- twrp codeworx 3.3.1
- Magisk installed
- developer options enabled, adb enabled
And here's my issue:
- downloaded latest magisk as zip file
- selected reboot to recovery
- twrp asks me for password, I enter my NIP but says "Can,t decrypt data'"
- Provides no option to reboot to system...
- rebooted, goes again to twrp
- rebooted to other menu where you can select fastboot, recovery, system when selecting system it goes to recovery...
So right now I'm frigging STUCK going to recovery all the time.
What are my options out of this nightmare?
I'd think:
- flash stock recovery from fastboot?
- other?
Suggestions welcome guys, I'm at the office and can't try anything now but definitely need input before I screw up things even more
Thanks
liberteus said:
So right now I'm frigging STUCK going to recovery all the time.
What are my options out of this nightmare?
I'd think:
- flash stock recovery from fastboot?
- other?
Click to expand...
Click to collapse
So... Got home, booted via fastboot the PREVIOUS twrp recovery (i.e. NOT this one https://sourceforge.net/projects/ch...rkx-signed-forcedecrypt-dumpling.img/download) and it gave me the option to actually cancel the password and keep the system read only. At which point I was able to reboot to system, and that's it, fixed.
I'll flash the twrp version that got me out of my self digged hole now.
Here's the version I used: twrp-3.2.2-0-20180721-codeworkx-dumpling.img (2018)

Can't install MIUI custom ROM on Mi A2 Lite

I'm trying to instal MIUI 11 from this link: https://forum.xda-developers.com/mi-a2-lite/development/rom-daisy-miui-11-hybridos-stable-t4003651
However after flashing the ROM the recovery says there's no OS at all. If I reboot it bootloops.
The only way I can go back to recovery is by using adb commands and flashing a IMG. Then TWRP says it can't open destination log file.
What can I do? Thanks!
I'm not sure what you've done with your device and I'm not sure if you know how to read (because there are a LOT of guides throughout the forum), but here we go :
1 - Flash stock ROM (check the forum again on how to do it or Google it.). Do this before you're trying to flash any ROM, really.
2 - Unlock the bootloader and boot TWRP from your PC.
3 - On TWRP go to Wipe and choose Wipe Data, type 'yes' and confirm it to wipe data.
4 - Now you're gonna need to boot into TWRP again, because TWRP sometimes breaks after wiping data, simply go to Reboot section and choose 'Bootloader' in TWRP. This will get you to Fastboot mode, you will need to boot TWRP from your PC again.
5 - Once you get into TWRP, flash the ROM, flash the TWRP.zip if you want.
6 - Go into Reboot section in TWRP and check your boot slot and change it. (If A make it B, if B make it A) and reboot into system.
7 - If you want to install Magisk or any other mod through TWRP, :
7a - if you've installed TWRP.zip previously, reboot into recovery and install your mods/Magisk and then boot into system
7b - if you didn't install TWRP.zip, reboot to Bootloader/Fastboot and boot TWRP, then flash your mods/Magisk. Finaly boot into system.
marstonpear said:
I'm not sure what you've done with your device and I'm not sure if you know how to read (because there are a LOT of guides throughout the forum), but here we go :
1 - Flash stock ROM (check the forum again on how to do it or Google it.). Do this before you're trying to flash any ROM, really.
2 - Unlock the bootloader and boot TWRP from your PC.
3 - On TWRP go to Wipe and choose Wipe Data, type 'yes' and confirm it to wipe data.
4 - Now you're gonna need to boot into TWRP again, because TWRP sometimes breaks after wiping data, simply go to Reboot section and choose 'Bootloader' in TWRP. This will get you to Fastboot mode, you will need to boot TWRP from your PC again.
5 - Once you get into TWRP, flash the ROM, flash the TWRP.zip if you want.
6 - Go into Reboot section in TWRP and check your boot slot and change it. (If A make it B, if B make it A) and reboot into system.
7 - If you want to install Magisk or any other mod through TWRP, :
7a - if you've installed TWRP.zip previously, reboot into recovery and install your mods/Magisk and then boot into system
7b - if you didn't install TWRP.zip, reboot to Bootloader/Fastboot and boot TWRP, then flash your mods/Magisk. Finaly boot into system.
Click to expand...
Click to collapse
Step 1 is wrong, miui ports have base stock in built, no need to make a clean flash
Step 5 is wrong, miui ports have twrp in built, you don't need flash twrp zip
Step 6 is wrong, miui ports need to be installed in the current active slot, no needed change slot
If your device have unlock bootloader and enable usb debugging, only boot twrp.img, only boot no flash, like the OP did it (fastboot boot twrpname.img)
Wipe> format data> yes
Install> install miui.zip
Install> install magisk (optional)
Reboot>system

Categories

Resources