Database Users

Problem with installing TWRP

My phone came with version 66.77.... (MIUI 6) from the reseller.
I have installed TWRP, rooted the device using adb and then flashed 5.9.24. So far so good.
After some time i decided to try AOSP ROM. I made a backup in TWRP and then flashed AOSP using TWRP. No problems so far (cleared cache, dalvik etc)
Then I wanted to revert back to 5.9.24. I cleared cache dalvik etc, and then I cannot remember anymore if i have reflashed 5.9.24 or restored the backup made previously from TWRP, the thing I wasn't able to boot into recovery anymore. The phone was stuck on the teamwin logo if booted into recovery but normal boot was working fine.
Then i reflashed twrp using adb.
After doing that, my phone was still stuck on the teamwin logo when booting into recovery, but with normal booting i was getting infinite boot loops at Mi logo screen.
After several ours of tries, i was able to solve the normal booting problem by flashing the stock recovery (so the phone is now back on the 5.9.24 - and working fine) but when I try to flash twrp using adb the same symptoms as before:
- Recovery boot - stuck on teamwin logo screen
- Normal boot - boot loops
I already tried to flash via Updater app, Flashify and Windroid nothing worked.
Can anyone help me to get this custom recovery working, please?
Thanks
Regards,
Nick

lukke04 said:
My phone came with version 66.77.... (MIUI 6) from the reseller.
I have installed TWRP, rooted the device using adb and then flashed 5.9.24. So far so good.
After some time i decided to try AOSP ROM. I made a backup in TWRP and then flashed AOSP using TWRP. No problems so far (cleared cache, dalvik etc)
Then I wanted to revert back to 5.9.24. I cleared cache dalvik etc, and then I cannot remember anymore if i have reflashed 5.9.24 or restored the backup made previously from TWRP, the thing I wasn't able to boot into recovery anymore. The phone was stuck on the teamwin logo if booted into recovery but normal boot was working fine.
Then i reflashed twrp using adb.
After doing that, my phone was still stuck on the teamwin logo when booting into recovery, but with normal booting i was getting infinite boot loops at Mi logo screen.
After several ours of tries, i was able to solve the normal booting problem by flashing the stock recovery (so the phone is now back on the 5.9.24 - and working fine) but when I try to flash twrp using adb the same symptoms as before:
- Recovery boot - stuck on teamwin logo screen
- Normal boot - boot loops
I already tried to flash via Updater app, Flashify and Windroid nothing worked.
Can anyone help me to get this custom recovery working, please?
Thanks
Regards,
Nick
Click to expand...
Click to collapse
Tried this: http://en.miui.com/thread-152550-1-1.html?mobile=2
Sent from my 2014817 using Tapatalk

timberwolf60 said:
Tried this: http://en.miui.com/thread-152550-1-1.html?mobile=2
Sent from my 2014817 using Tapatalk
Click to expand...
Click to collapse
i saw the request of the message but i am not using a custom recovery on my phone,i use a custom dev rom made by miui france.
i think some china dev rom comes rooted by default with custom installer updater and gapps like mine.
i think twrp is not fully compatible with this device yet.

Have you try with sp flash tool method ?
http :// en.miui.com/forum.php?mod=viewthread&tid=156838&extra=page%3D4&mobile=2

I just installed TWRP for the first time ever. I used the Flashify App from the Play Store, installed it and gave it root permissions and just selected the TWRP image on the phones internal store. Seemed to work just fine and did not have to plug my phone into a computer

Trying to install cyanogenmod to nexus 4, I cannot flash it through TWRP recovery

I am trying to flash my N4 with cyanogenmod following the official wiki.
I'm at the point where I've installed TWRP into recovery, I've wiped everything (I've even formatted them since I couldn't wipe all of it initially), and the only error I see is "unable to mount /usb-otg".
Then, I've "installed" the CN zip files for the 13 and 12 versions, none of them works in the sense that when I reboot the system, I'm always coming back to TWRP.
What's wrong? Any suggestion?
Thanks

I've the same problems with my nexus 4
gerardgerard said:
I am trying to flash my N4 with cyanogenmod following the official wiki.
I'm at the point where I've installed TWRP into recovery, I've wiped everything (I've even formatted them since I couldn't wipe all of it initially), and the only error I see is "unable to mount /usb-otg".
Then, I've "installed" the CN zip files for the 13 and 12 versions, none of them works in the sense that when I reboot the system, I'm always coming back to TWRP.
What's wrong? Any suggestion?
Thanks
Click to expand...
Click to collapse
Hi gerardgerard,
I also wanted to flash my Nexus 4 with Cyanogenmod 12.1. So I installed TWRP into recovery and wiped everything, like it's explained in the wiki. I can also see the error "unable to mount /usb-otg". When I want to reboot the system I always get back to TWRP. Cyanogenmod doesn't boot correctly. Did you find a solution for the problem?

same problem
Hi
I'm having the same problem. As follows:
Cause (my mistake): I have been using Cyanogen-mod nightlies for a couple of months on my Nexus 4, and made the grave mistake of leaving the phone to upgrade one night but without it being plugged in properly - and it ran out of power part way through! (At least, that's what I think happened).
Fortunately, it would boot into bootloader and I could use adb/fastboot. I (re)installed TWRP 2.8.7.0 (from my Mac, using fastboot). And that works fine - I can boot into twrp ok.
Next I loaded the latest nightly from cm (using fastboot - is this what people call sideloading?) and used twrp to install it. It goes through the installation fine (the only error message is that it can't mount /usb-otg). But when I reboot it just goes back to twrp.
I then tried installing the earlier cm nightly that I know worked, but with the same result.
Finally, before I first installed cm I did a backup (using twrp), and I have tried recovering that. It seems to do all the right things, but again when I reboot it just goes back to twrp.
Any suggestions would be welcome.
Thanks
J

Flash back to a completely stock ROM and run through the set up to make sure everything works. Then copy CM to the phone, reboot to fastboot, flash twrp, immediately boot into recovery using the volume and power button without leaving fastboot, wipe data, cache, system, flash CM, reboot.
If the phone will not boot after flashing a stock ROM, boot to fastboot, flash the userdata.img file, and immediately go to stock recovery without leaving fastboot, wipe data/cache, reboot.

It works now!
I managed to fix the problem ... I found this guide for the Nexus 5:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
and I applied those instructions. It didn't work first time, so I just repeated them and now it's working. I used the 5.1.1 stock downloaded from https://developers.google.com/android/nexus/images#occam.
I guess this is what audit13 means in their post - so thanks are due there.
I will next reinstall twrp and cm and I don't expect any problems with that (having done it successfully before).
Smaje

Mako always booting into recovery

Hi all,
I was running the official Google 5.1.1 version until this morning. I now did an oem unlock using fastboot and installed the latest twrp recovery 3.0.0, and finally copied overy CM-13 nightly (and Chroma-2016-02 for testing purposes) using adb.
Flashing itself work flawless, there is no warning or error message, but when hitting "Reboot" within twrp the Google logo shows up for a few seconds and it directly boots into twrp again. This is with both, CM-13 and the latest Chroma.
So I basically cannot get my Nexus-4 bootet regulary any more.
Any ideas what the problem might be?
Any help is welcome,
regards, mistersixt.

Mmmh, strange, I did a factory installation (latest 5.1.1 from Google) and started the same thing from scratch ... and guess what... the system is booting fine now.
No idea why it did not work on my first attempt .
Regards, mistersixt.
mistersixt said:
Hi all,
I was running the official Google 5.1.1 version until this morning. I now did an oem unlock using fastboot and installed the latest twrp recovery 3.0.0, and finally copied overy CM-13 nightly (and Chroma-2016-02 for testing purposes) using adb.
Flashing itself work flawless, there is no warning or error message, but when hitting "Reboot" within twrp the Google logo shows up for a few seconds and it directly boots into twrp again. This is with both, CM-13 and the latest Chroma.
So I basically cannot get my Nexus-4 bootet regulary any more.
Any ideas what the problem might be?
Any help is welcome,
regards, mistersixt.
Click to expand...
Click to collapse

Same here. Running stock until today, wanted to see a different ROM, flashed TWRP 3.0.0, it refused to boot anything else. Tried to flash DU, then tried Chroma. Did a full wipe, then an advanced wipe selecting everything, then a full format, same thing. Installed TWRP 2.8.7, same thing. Finally installed latest stock, it is now booting, optimizing apps. I don't know if installing a custom rom will work or not yet.
Edit: Yeap, after flashing stock 5.1.1 and installing TWRP 3 again, the phone is now booting into DU.
First time I did a wipe with TWRP, it complained that it couldn't mount /data. Since this is the first time doing it, I assumed it was normal. After going through a full format, it didn't complain about data anymore, but it did complain about something to do with /dev/zero and another file under /dev/. I assume it was trying to dd /dev/zero to a file under /dev/ that didn't exist.

+1
Done the whole process from scratch again and worked like a charm

Hello, same story here.
First I:
- unlocked bootloader
- flashed TWRP (last version)
- flashed Chroma and Gapps
- reboot
=> I consistently rebooted on TWRP. No way to properly install the ROM. No error message at all.
Then I found this thread, and did as described:
- flashed the latest stock ROM
- flashed TWRP again (took me ages to manage to do this: TWRP would not install. I don't know how I finally did it, but at some point it suddenly worked. Probably a driver problem)
- flashed Chroma and Gapps again
Bingo, this time it worked! I don't know why it didn't work the first time. Could it be linked to the bootloader unlock thing?

One Plus two not Loading Recovery Mode (stuck on Logo)

Hi, I need help in installing Recovery.
I unlocked the bootloader, installed TWRP and then CyanogenMod 13 ROM.
After this, Oxygen Os 3 got released. I downloaded the zip file and flashed through TWRP.
Oxygen OS got installed but after this, I couldn't go back in TWRP recovery.
I tried everything. I use "fastboot flash recovery twrp.img"
everything works
but when I boot in recovery, phone gets stuck on the LOGO and nothing happens.
Is there any way to solve this issue.

Almost the same for me.
When I flash oOS 3.0.2, unable to reboot using Grarak'sTWRP or TWRP-3.0.2-1.
Always stuck on boot logo without animation.
I reverted to old TWRP and oOS 2.2.1

piyushmodi01 said:
Hi, I need help in installing Recovery.
I unlocked the bootloader, installed TWRP and then CyanogenMod 13 ROM.
After this, Oxygen Os 3 got released. I downloaded the zip file and flashed through TWRP.
Oxygen OS got installed but after this, I couldn't go back in TWRP recovery.
I tried everything. I use "fastboot flash recovery twrp.img"
everything works
but when I boot in recovery, phone gets stuck on the LOGO and nothing happens.
Is there any way to solve this issue.
Click to expand...
Click to collapse
Try to install OOS recovery or Hybrid recovery.

Nobody ever learns or reads nowadays....
Read up on bootloader versions on Oneplus 2 and you will find the explanation perfectly understandable.

Thank You So much for your help. Finally it worked but I lost my data! Anyways, no issues.

Can you give us the way you fixed your problem .
Thanks

Open Gapps Recovery Script Bootloop

Hi guys,
So I wanted to update my phone to a newer ROM, was using an Android 6.0 ROM that I liked a while ago so I decided to get an updated Android 7.1. The ROM worked fine and OpenGaps Pico installed fine.
Once I knew everything worked I downloaded the Aroma package from the OpenGapps app and then ran the install.
Unfortunately the install crashes almost instantly, then the phone reboots into recovery and runs the installer again. So I am stuck in a bootloop of it failing to install.
It says at the top "Running OpenRecoveryScript - Installing Zip"
Put battery into phone, power on, boots into TWRP recovery, crashes on "Starting AROMA Installer", reboots, LOOP.
Many thanks,
Ollie

OllieCrook said:
Hi guys,
So I wanted to update my phone to a newer ROM, was using an Android 6.0 ROM that I liked a while ago so I decided to get an updated Android 7.1. The ROM worked fine and OpenGaps Pico installed fine.
Once I knew everything worked I downloaded the Aroma package from the OpenGapps app and then ran the install.
Unfortunately the install crashes almost instantly, then the phone reboots into recovery and runs the installer again. So I am stuck in a bootloop of it failing to install.
It says at the top "Running OpenRecoveryScript - Installing Zip"
Put battery into phone, power on, boots into TWRP recovery, crashes on "Starting AROMA Installer", reboots, LOOP.
Many thanks,
Ollie
Click to expand...
Click to collapse
Which version of TWRP do you have?

zlazaar said:
Which version of TWRP do you have?
Click to expand...
Click to collapse
TWRP 3.1.1-0

OllieCrook said:
TWRP 3.1.1-0
Click to expand...
Click to collapse
SEE multiple forum posts .
TWRP 3 + may be your problem use an older version .

OllieCrook said:
TWRP 3.1.1-0
Click to expand...
Click to collapse
It's known that TWRP 3.0.1 can't handle Aroma installer.
I'm not sure if later versions were fixed.
v2.8.7 will not fail for sure.

zlazaar said:
It's known that TWRP 3.0.1 can't handle Aroma installer.
I'm not sure if later versions were fixed.
v2.8.7 will not fail for sure.
Click to expand...
Click to collapse
Thanks! I didn't really look into things, just update everything together. I just ended up making my own gapps config.

i have the same problem, but my note 3 only enter to recovery and try to flash this gapps aroma and crash and reboot and do the same thing, dont enter to system, dont enter to download mode, only boots to recovery and crash, any solution? help me, I think he just passed on to a better life
Sorry for my bad english.

TH3-JUL10 said:
i have the same problem, but my note 3 only enter to recovery and try to flash this gapps aroma and crash and reboot and do the same thing, dont enter to system, dont enter to download mode, only boots to recovery and crash, any solution? help me, I think he just passed on to a better life
Sorry for my bad english.
Click to expand...
Click to collapse
just ODIN it to default stock rom.
then after do the new rom flash procedure from start.