Related
Good Day,
Thanks for taking the time to read my posting.
I am running a Galaxy Note 2 with TWRP v2.8.7.0. Previously, had been running CyanogenMod 12 Latest Release from 2015-11-17.
Had an issue with the phone rebooting, went into TWRP to clear Cache/Davlik Cache, seen an error after this with /Data partition not being mounted(phone was encrypted). Proceeded to go into TWRP and Format Data then reinstall the ZIP listed above from an external SD card, successfully completed installation of ZIP file for CyanogenMod 12. When I reboot the device from TWRP, through Reboot->System, keeps rebooting back into TWRP and not into CyanogenMod.
I have connected the device to a Windows computer, confirmed that I can see it connected through USB. When I issue abd devices, I see the ##### recovery listed for the device, but if I issue fastboot devices, no device is listed.
Any recommendations for what could be done to reinstall the CyanogenMod build on my device so that it can boot properly would be greatly appreciated.
Thanks to everyone on the community for the support, education and feedback over the years and for all the hard work that you do, cheers to you.
Maybe flash back to a completely stock rom, confirm that everything works, flash twrp, and cm again?
I was thinking about recovery to stock recovery when I read your post .
Tried the stock recovery using Odin3-v3.07 pointing to CF-Auto-Root-t0ltetmo-t0ltetmo-sght889.tar.md5(1/20/2015), this appeared to complete from Odin, but the phone still went into a reboot loop into CyanogenMod, but never fully started up, thereafter.
Went to the autoroot.chainfire.eu site, downloaded the latest stock recovery for device.
Pulled the battery, back into TWRP, select Wipe/Factory reset from TWRP. Installed Samsung Kies onto desktop, ran Odin3-v3.10.6 pointing AP to CF-Auto-Root-t0ltetmo-t0ltetmo-sght889.tar.md5 dated from 3/31/2016. Then went to phone and go to download mode (turn off first, press and hold following buttons: vol down + home + power). Then Press Up Volume key to get into Download mode, then connect it to PC via USB. Device shown in Odin under ID:COM. On Option uncheck “Repartition”. After reboot, phone boot into IMG for CyanogenMod. Confirmed access to phone thereafter.
Thanks for the feedback, hope this helps someone down the line, if they run into the same issue.
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.
First I apologize for my English, I do not speak English, and I used google translate to translate my text.
I need your help. Please, anyone who understands TWRP and Recovery on Xiaomi phones, help me.
I'll leave it to you to make it easier for you to understand, because the text is long.
TL; DR my cell phone is neither with TWRP nor with Recovery of xiaomi (I think it is not, because I can not get into any of the 2 at all). Everything I did I left step by step in the text.
I wanted to install the ROM pixel, do root and install GCam on my Xiaomi Redmi Note 5 Pro.
The first step was to unlock the bootloader, and yes, I was able to unlock everything quietly, (I waited 180 hours and then I was saying that I did not have my cell phone long enough to unlock, so I downloaded another version of miunlock and managed to unlock).
The second step was to install TWRP, which started to complicate.
Through a video on youtube of a channel that always posts videos to this phone, I followed the instructions for installing TWRP, I did everything according to the video (in this video he did not ask to install anything in Windows, just use cmd) and the commands he typed were as follows:
fastboot flash antirbpass dummy.img,
fastboot flash recovery twrp-3.2.3-1-whyred.img
From there he had to close the cmd and turn off the cell phone (remembering that the cell phone was already in fastboot mode) and then turn on the cell holding power + volume UP to enter the TWRP, however, did not enter the TWRP, entered the recovery mode standard of xiaomi.
So I left for another video. This time, the video was gringo, in this video, the guy asked to install an Adb on the PC, installed correctly and entered the CMD as the video. The commands that the guy from the video passed were this:
fastboot devices
fastboot boot twrp (twrp from another version)
This time the device entered TWRP, but to my surprise, TWRP was asking for a password (which I had no idea what it was) so I went after another version of twrp.
The alternative version for not asking for a password in TWRP that I used is 3.2.3.0, I used it according to the tips of the second video (the same one that I got to TWRP for the first time), and finally I joined the TWRP and did not asked for no password, end of the second part.
The third step was to install the ROM pixel and the magisk, and that's where it started to disgrace everything, I followed the steps according to another video for ROM installation.
In the video, the guy had to enter WIPE, advanced and check some options that did not include internal memory, I did everything right as in the video. Then he had to go to install and select the ROM, when the installation of my ROM started, it already presented an error, the despair hit and I did not know what to do (since I had no more operating system because I had reset the cell phone ) and by impulse, I decided to download the last version of MIUI 10 Stable (I was using the Beta version of MIUI 10), but I did not look right because I was VERY DESPERATE and I ended up downloading ROM Recovery, not ROM fastboot (I think influence on something, I am layman in that, I do not know), I was able to install the MIUI 10 Stable ROM, and soon after I installed Magisk to do the root, in that he had to restart the device.
After rebooting, I made the initial settings, and according to the video, I would need to turn off the phone to enter the TWRP mode to install the GCAM, but my cell phone HAS NO MORE TWRP, and worse, it does not come in the standard Recovery mode of the xiaomi, it's just written MI (that normal boot screen when you connect the Xiaomi device) and I have to restart it by holding down the power button.
I'm using it normally, it's root. But I can not get into the TWRP nor the normal Recovery of the ceular, that is, I can not even install GCam.
That's where my doubt comes in. Can I install TWRP yet? Remembering that the steps I did for the installation is on the topic so I do not know if I can do it again.
And since I'm without TWRP and without Recovery, I will not be able to update my phone anymore? I'm getting into fastboot and system mode at least.
spoktasy said:
First I apologize for my English, I do not speak English, and I used google translate to translate my text.
I need your help. Please, anyone who understands TWRP and Recovery on Xiaomi phones, help me.
I'll leave it to you to make it easier for you to understand, because the text is long.
TL; DR my cell phone is neither with TWRP nor with Recovery of xiaomi (I think it is not, because I can not get into any of the 2 at all). Everything I did I left step by step in the text.
I wanted to install the ROM pixel, do root and install GCam on my Xiaomi Redmi Note 5 Pro.
The first step was to unlock the bootloader, and yes, I was able to unlock everything quietly, (I waited 180 hours and then I was saying that I did not have my cell phone long enough to unlock, so I downloaded another version of miunlock and managed to unlock).
The second step was to install TWRP, which started to complicate.
Through a video on youtube of a channel that always posts videos to this phone, I followed the instructions for installing TWRP, I did everything according to the video (in this video he did not ask to install anything in Windows, just use cmd) and the commands he typed were as follows:
fastboot flash antirbpass dummy.img,
fastboot flash recovery twrp-3.2.3-1-whyred.img
From there he had to close the cmd and turn off the cell phone (remembering that the cell phone was already in fastboot mode) and then turn on the cell holding power + volume UP to enter the TWRP, however, did not enter the TWRP, entered the recovery mode standard of xiaomi.
So I left for another video. This time, the video was gringo, in this video, the guy asked to install an Adb on the PC, installed correctly and entered the CMD as the video. The commands that the guy from the video passed were this:
fastboot devices
fastboot boot twrp (twrp from another version)
This time the device entered TWRP, but to my surprise, TWRP was asking for a password (which I had no idea what it was) so I went after another version of twrp.
The alternative version for not asking for a password in TWRP that I used is 3.2.3.0, I used it according to the tips of the second video (the same one that I got to TWRP for the first time), and finally I joined the TWRP and did not asked for no password, end of the second part.
The third step was to install the ROM pixel and the magisk, and that's where it started to disgrace everything, I followed the steps according to another video for ROM installation.
In the video, the guy had to enter WIPE, advanced and check some options that did not include internal memory, I did everything right as in the video. Then he had to go to install and select the ROM, when the installation of my ROM started, it already presented an error, the despair hit and I did not know what to do (since I had no more operating system because I had reset the cell phone ) and by impulse, I decided to download the last version of MIUI 10 Stable (I was using the Beta version of MIUI 10), but I did not look right because I was VERY DESPERATE and I ended up downloading ROM Recovery, not ROM fastboot (I think influence on something, I am layman in that, I do not know), I was able to install the MIUI 10 Stable ROM, and soon after I installed Magisk to do the root, in that he had to restart the device.
After rebooting, I made the initial settings, and according to the video, I would need to turn off the phone to enter the TWRP mode to install the GCAM, but my cell phone HAS NO MORE TWRP, and worse, it does not come in the standard Recovery mode of the xiaomi, it's just written MI (that normal boot screen when you connect the Xiaomi device) and I have to restart it by holding down the power button.
I'm using it normally, it's root. But I can not get into the TWRP nor the normal Recovery of the ceular, that is, I can not even install GCam.
That's where my doubt comes in. Can I install TWRP yet? Remembering that the steps I did for the installation is on the topic so I do not know if I can do it again.
And since I'm without TWRP and without Recovery, I will not be able to update my phone anymore? I'm getting into fastboot and system mode at least.
Click to expand...
Click to collapse
id say start from scratch.. upto you to reset to official miui with fastboot rom and mi flash (note if you do check clean all only or ill relock bootloader if clean and lock is selected.. no need to wait again but you must unlock it again)
follow this guide.
https://forum.xda-developers.com/re...ne-xiaomi-redmi-note-5-whyred-unlock-t3778049
just skip steps you already did like adb if already installed.... also install drivers.
for twrp use this 1 click also has miflash
https://drive.google.com/open?id=1XLncxs4UDcSxiefQomwT4yZpWthwfAES
i recommend to use orangefox recovery. when you boot into twrp flash orangefox zip thats it.
thanks for answering. I was able to solve the TWRP part using another version of it. Now I'd like to know if it's possible for me to access TWRP directly from my cell phone, without the need for the computer.
spoktasy said:
thanks for answering. I was able to solve the TWRP part using another version of it. Now I'd like to know if it's possible for me to access TWRP directly from my cell phone, without the need for the computer.
Click to expand...
Click to collapse
use quick reboot app from playstore. it boots into recovery or fastboot .
spoktasy said:
thanks for answering. I was able to solve the TWRP part using another version of it. Now I'd like to know if it's possible for me to access TWRP directly from my cell phone, without the need for the computer.
Click to expand...
Click to collapse
settings > developer options > enable extended power menu
this should work
Hi there,
I think I (soft? hard?) bricked my whyred today after trying to install Pixel Experience (Android 10). At this time, I'm left with a flashed PE Plus that is stuck at the Google logo animation (e.g. unable to access USB debug settings); stock MIUI recovery; and fastboot, which is not recognized by ADB as I haven't had a successful boot since I flashed PE, so I can't turn USB debug on. I think I've exhausted my options, but maybe someone has a smart solution.
For those who think they can help, let me describe in detail what I did:
0) I became a dev, turned USB debug on, installed Minimal ADB and Fastboot, latest Xiaomi drivers, moved flashable zips into internal storage etc.
1) I unlocked my bootloader through Mi Unlock.
2) I successfully flashed TWRP-3.3.1.0-whyred via ADB/Fastboot and rebooted. After getting back into MIUI, I booted into recovery, which was back to stock (MIUI seems to have overwritten my recovery). At that point (probably a big mistake) I gave up on flashing TWRP and went ahead to boot right into it via ADB instead, without flashing.
3) After a successful boot into TWRP 3.3.1.0, it asked me for a decryption password. Nothing worked, so I kept googling and found out that my version of android needs TWRP 3.3.1.1, which was not on the official TWRP website yet, to decrypt automatically. I booted into TWRP 3.3.1.1 via ADB (but didn't flash), made a backup of my stock ROM, did a wipe (art/dalvik cache, cache, data, system, vendor), flashed Pixel Experience and rebooted.
4) Bootloop, I was stuck on the Google loading animation for over 20 minutes, nothing happened.
5) I panicked.
6) I tried to flash TWRP 3.3.1.1 via ABD but my PC didn't recognize my phone - probably because, for lack of successful boots, I have not managed to turn on USB debug.
7) I tried to connect to Mi Assistant through stock recovery. It didn't recognize my phone, probably for the above reason.
8) I did a data wipe through stock recovery and rebooted, hoping for whatever issue kept PE from booting normally to get resolved.
9) I'm stuck on the same Google loading animation for over 40 minutes now, no progress.
Does any of you guys see a way out, or is this story over? To recap, I have: 1) PE Plus in bootloop, no access to dev settings, 2) stock MIUI recovery with options to reboot, wipe data or connect to Mi Assistant, 3) stock fastboot, 4) a backup of my previous system on internal storage, 5) ADB on my computer that doesn't recognize my phone - no USB debugging. I don't know where to turn. I don't care much about data, I have everything in the cloud, but I'd like to save the phone if possible.
Thanks a lot.
Edit: Problem resolved - even though the connected device didn't show up in ADB on PC (adb devices came back empty), the phone was still responsive to fastboot reboot and fastboot flash recovery via PC, so I could flash TWRP 3.3.1.1 & clean flash PE. For anyone struggling with PE bootloops: make sure to 1) use TWRP 3.3.1.1 to flash, 2) do a dalvik/cache wipe after flashing the ROM and 3) not to install the TWRP app before the first successful boot - it was neglecting either 2) or 3) that caused my bootloop. The ROM itself is amazing!
mkohan said:
Hi there,
I think I (soft? hard?) bricked my whyred today after trying to install Pixel Experience (Android 10). At this time, I'm left with a flashed PE Plus that is stuck at the Google logo animation (e.g. unable to access USB debug settings); stock MIUI recovery; and fastboot, which is not recognized by ADB as I haven't had a successful boot since I flashed PE, so I can't turn USB debug on. I think I've exhausted my options, but maybe someone has a smart solution.
For those who think they can help, let me describe in detail what I did:
0) I became a dev, turned USB debug on, installed Minimal ADB and Fastboot, latest Xiaomi drivers, moved flashable zips into internal storage etc.
1) I unlocked my bootloader through Mi Unlock.
2) I successfully flashed TWRP-3.3.1.0-whyred via ADB/Fastboot and rebooted. After getting back into MIUI, I booted into recovery, which was back to stock (MIUI seems to have overwritten my recovery). At that point (probably a big mistake) I gave up on flashing TWRP and went ahead to boot right into it via ADB instead, without flashing.
3) After a successful boot into TWRP 3.3.1.0, it asked me for a decryption password. Nothing worked, so I kept googling and found out that my version of android needs TWRP 3.3.1.1, which was not on the official TWRP website yet, to decrypt automatically. I booted into TWRP 3.3.1.1 via ADB (but didn't flash), made a backup of my stock ROM, did a wipe (art/dalvik cache, cache, data, system, vendor), flashed Pixel Experience and rebooted.
4) Bootloop, I was stuck on the Google loading animation for over 20 minutes, nothing happened.
5) I panicked.
6) I tried to flash TWRP 3.3.1.1 via ABD but my PC didn't recognize my phone - probably because, for lack of successful boots, I have not managed to turn on USB debug.
7) I tried to connect to Mi Assistant through stock recovery. It didn't recognize my phone, probably for the above reason.
8) I did a data wipe through stock recovery and rebooted, hoping for whatever issue kept PE from booting normally to get resolved.
9) I'm stuck on the same Google loading animation for over 40 minutes now, no progress.
Does any of you guys see a way out, or is this story over? To recap, I have: 1) PE Plus in bootloop, no access to dev settings, 2) stock MIUI recovery with options to reboot, wipe data or connect to Mi Assistant, 3) stock fastboot, 4) a backup of my previous system on internal storage, 5) ADB on my computer that doesn't recognize my phone - no USB debugging. I don't know where to turn. I don't care much about data, I have everything in the cloud, but I'd like to save the phone if possible.
Thanks a lot.
Click to expand...
Click to collapse
I'm new to this phone as well (but not to Android). Try the following:
Download TWRP from here -> https://androidfilehost.com/?fid=6006931924117884758
Download Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip from here -> https://zackptg5.com/downloads/Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
Power off phone. Hold down volume down and power button to boot into fastboot
Give the command fastboot flash recovery twrp-3.3.1-1-whyred.img to flash the recovery you downloaded earlier.
Boot into recovery
Flash Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip that you downloaded earlier
The above steps will at least ensure that you retain TWRP and it doesn't get overwritten by stock MIUI recovery
After that, check whether or not your phone/ROM has anti-rollback enabled and take appropriate steps accordingly.
Ok so i flashed PE 10 plus today and was met with the same problem.
Heres how i solved it
Goto fastboot option by pressing volume down and power button
Connect to pc (If it doesnt recognize, reinstall Adb drivers and phone drivers)
If it asks for decryption password just press cancel
Wipe data/internal/vendor (wont be able to wipe dalvik as it wont mount)
Flash PE 10 Plus and nothing else.
It should boot just fine.
However i run into bootloop if i flash latest magisk so i cant root my phone :/
Hope this helps
mkohan said:
Edit: Problem resolved - even though the connected device didn't show up in ADB on PC (adb devices came back empty), the phone was still responsive to fastboot reboot and fastboot flash recovery via PC, so I could flash TWRP 3.3.1.1 & clean flash PE. For anyone struggling with PE bootloops: make sure to 1) use TWRP 3.3.1.1 to flash, 2) do a dalvik/cache wipe after flashing the ROM and 3) not to install the TWRP app before the first successful boot - it was neglecting either 2) or 3) that caused my bootloop. The ROM itself is amazing!
Click to expand...
Click to collapse
hey read your post
actually adb and fastboot are two different things.
and recovery is flashed using fastboot commands not adb.
sometimes if a rom is not booting it may have issues with encryption.
First of all, a Happy HEALTHY New Year to everyone ! !
Would like to bring Whatsapp from Android to iPhone.
Fail, among other things, because some programs need root (Backuptrans).
After the backup on Google Drive and Samsung Cloud I did the following:
1. OEM Unlocked and Factory Reset.
2. USB debugging ON
3. Phone switched off and started in download mode
4. Flashed with ODIN twrp-3.2.3-0-star2lte.img.tar.
5. After the reboot, the phone is set up again for Samsung Cloud, switched off and restarted in recovery mode.
But there is still the old android recovery screen. I also tried the other TWRP versions up to 3.4.0.0.
I have now taken out the reboot tick when flashing TWRP under ODIN and am after flashing
came with the 3 buttons into the TWRP recovery menu. However, I couldn't find the Magisk Zip files in the internal memory there.
So I wanted to start normally again, but after 15 minutes of SAMSUNG writing I got a message ... The version doesn't work and everything has to be reset to the factory settings.
And then the game started all over again.
So now the question to you what am I doing wrong or how do I get Root and TWRP from cell phone?
Regards Klaus