Hey everyone.
I'm really hoping someone can help me. I just got my Redmi 2 Prime today, and before even properly setting it up I had rooted it. It wasn't long before I decided to try a different ROM. I decided on Resurrection Remix and TWRP recovery, both of which I flashed an ran flawlessly. RR booted up, everything was great.
I then tried flashing SuperSU again, after installing RR. Flashing the .zip file resulted in a boot loop, with no access to recovery, only fastboot.
What I've tried (with no success):
- Re-flashing TWRP (through Fastboot).
- Flashing CWM instead (through Fastboot).
- Flashing stock recovery (through Fastboot).
None of these have proven successful..... Can anyone give any advice on how to get out of this mess? I hardly feel up for having to take my phone into a shop without even having had it for 24 hours.....
TIA!
Fastboot flash Redmi 2 ROM. Download ROM file from MIUI forums and read the instructions there. Go to this link http://en.miui.com/a-234.html
i dont know if this comes at the right time,since fastboot is accesbile ,boot into fastboot, and flash recovery into boot(this may sound foolish but you can do it)
fastboot flash boot recovery_twrp.img
reboot,you will be taken into twrp
you can take a backup here,
now wipe all and flash the ROM.zip
anfd it should all work fine
I had the same problem when I switched from MIUI 8 4.4Kitkat to CM13 6.0
But I was able to solve it without fastboot.
RessurectionRemix and most roms esepecially CM based have "built-in" superSU manager.You just have simply to re-enable it on the developer settings.No need to flash supersu.zip,it would just make things worse.Download Flashify to boot in TWRP manually since flashing different ROMs will temporarily remove the TWRP(doing the button combination wouldn't boot into recovery,instead bootloop like you mentioned).
Then I was able to perform a restore on stock MIUI 8.
You have to download Flashify in order to manually force the phone to boot in recovery mode,since doing to volume up+power wouldn't let you.
I don't know if this is because my TWRP version only supports KitKat....or switching from 4.4-6.0 is a big gap.
Thanks for the responses!
I ended up solving the issue, though there wasn't really an issue to begin with. Turns out the button combination to enter recovery is different than stock (both volume buttons and power), though I did re-flash to the latest version of TWRP.
I'm now running Resurrection Remix without flaws!
But yeah, I realize now that CM based ROMs have a baked-in SU manager, it was foolish of me to flash the file without doing proper reading up beforehand!
Hi guys, been using my rooted but otherwise stock OOS rom with TWRP and Magisk for the past few weeks. Today I decided to take the plunge and try either the Lineage OS or Resurrection Remix roms.
I'm using the latest OFFICIAL TWRP.
So I decrypted following the instructions to flash "no-verity-opt-encrypt-5.1.zip", then format data. All went well, so I then sent over the ROMS I wanted to try out. I started with the official ResurrectionRemix. Bootloop. Then the unofficial LineageOS. Bootloop.
Ok, well I guess I'm not gonna get to use any of the cool new OS's for awhile. I'll install the full stock firmware zip so I can have a working phone again. Bootloop.
Now when I say bootloop, the phone is booting to the BootAnimation and just repeating it. It shows the proper boot animation for whatever zip I have installed (resurrection/LOS/OOS), but it stays on there for up to 20 minutes before I have to hard reboot to the recovery again.
I decided to install the stock recovery trying a few methods. I first tried the ALL-IN-ONE tool. It said it flashed the recovery fine, so I booted to the recovery and after staying on a black screen for too long, the language options came up and I sighed a breath of relief. But before I could select English with the volume buttons, it rebooted by itself. It did this again when I manually entered recovery. So I figured maybe the tool flashed the wrong version, so I googled stock recovery for OnePlus 5, I found a few random links for stock recoveries for the OP5 and flashed them, but they more or less do the same thing or not boot at all.
I've tried changing the filesystem for both Data and System using any combinations of EXT4 and F2FS. Everything results in boot animation bootloops.
I have been flashing Roms since the Samsung Galaxy S3 and every phone since and never had any problems.
Currently when trying to install the stock Full OOS official zip with TWRP, the phone won't even go to the boot animation, it only goes to a black screen with the top LED in a light blue color.
I have also tried every version of TWRP there is for the OnePlus 5. Unofficial, Official, 3.1.1-0 and 3.1.1-1.
So I guess my question is....What filesystem is each partition supposed to be on and for which OS?
Lineage based:
System: ?
Data: ?
OOS Based:
System: ?
Data: ?
And any ideas on getting my phone running again?
And anyone have an official confirmed working version of the stock recovery? The one from ALL-IN-ONE TOOL doesn't work for me. It loads the language selection, then the screen goes black with a light blue LED on the top of the phone.
Actually I'm getting that on some roms instead of the bootanimation, like FreedomOOS. What does it mean when you have a black screen and a white LED?
Man, I really thought I was getting somewhere. If I boot into TWRP, change the Data partition to "F2FS", then flash the stock recovery, the stock recovery will boot, however, when inside the stock recovery and I try to flash the stock zip, it says "Flashing, don't turn off your device" for about 5 seconds and then goes back to the list of roms on the SD card, not having flashed anything at all.
Ok, I have the official stock recovery from the OnePlus site, but still can't use it. Here is was happens depending on how I left it with TWRP:
System: F2FS
DATA: F2FS
- Stock recovery will load after some time, freeze, then the screen goes black with white LED on top.
System: EXT4
DATA: F2FS
- Stock recovery loads fine, I can go through the settings and install from SD card, but when I do it says "Flashing, don't turn off your device" for about 5 seconds and then goes back to the list of roms on the SD card, not having flashed anything at all.
System: EXT4
DATA: F2FS
- If I try to flash stock rom through TWRP, it just boot loops on the animation forever.
I have now also tried flashing the stock boot.img, but no difference.
I have 2 things you can try!
First, replace the bootloader with stock and do a factory reset:
1. flash the stock recovery over
2. then in fastboot mode enter, fastboot oem lock (This forces the phone to wipe cache and data, and also do a complete reset)
Did it work? if yes YAY if not go to Second!
Second if your system.img is ****ed up you have to replace it!
Download the newest version of the stock rom from oneplus link here
Unpack it
research how to use an extractor to convert the system.new.dat to system.img
once thats completed enter fastboot mode and flash the new system.img over with Fastboot flash system system.img
now go into recovery and do a factory reset and wipe cache, and dalvik
Please reply back wether or not this work
"Ihave 2 things you can try! First, replace the bootloader with stock and do a factory reset..."
Is the bootloader simply the boot.img?
After doing the first thing, it simply says that the device is corrupt and will not boot. But it is locked again.
But I will have to unlock it again to do any further flashing.
Hmm, I think I may have gotten it. After unlocking again, flashing the stock recovery and boot.img, then locking again and wiping in the stock recovery, I have finally booted into the stock rom.
I still have no idea what went wrong, and I really want to know, so that in the future I can flash other Roms, like LineageOS.
I mean, I followed the steps exactly.
If it says the device is corrupt it simply means you got something else besides stock rom.
So now unlock it and try the system.img instead
It was because I still had TWRP with the stock rom.
I got it working though, thanks for your help.
Do you have any idea on what might have went wrong when trying to flash the lineageOS based roms and why it got messed up so royally?
Great to hear you fixed it ^_^
Probably some minor bug, if you wanna try installing lineageos again use the 3.1.1 TWRP build that supports backups and do a full backup so you don't have to go thru all this again
---------- Post added at 12:17 AM ---------- Previous post was at 12:13 AM ----------
Not really just try again but remember to use TWRP 3.1.1, as 3.1.0 don't support backup and probably have been part of your problem
If your trying again and gets it successfully installed could you do me a favor and test if Drivedroid works on it? And pm me the result, I'm looking for a rom where Drivedroid will work... Haven't found one so far
You know, I did do a backup with the OFFICIAL TWRP, but it also resulted in a bootloop. I made the backup after decrypting, so I don't know why it bootlopped.
https://forum.xda-developers.com/oneplus-5/development/rom-unified-lineageos-7-1-2-t3635483
Is this the one you tried installing?
I tried like every ROM at one point yesterday, but I think I started with
https://forum.xda-developers.com/oneplus-5/development/rom-resurrection-remix-n-7-1-2-t3636578
Did you remember Gapps?
Also in some cases its better not to root before you have the custom rom running, you usually only need a custom bootloader like TWRP
Yeah, I tried with Gapps, and I never rooted before first trying to boot.
As of yesterday Ressurrection remix, released the first official stable build so try again your should'nt have any problems if you follow the guide 100%
Ever find a solution? I'm stuck here now. Can't get any ROM to boot up, they all get stuck on the boot animation
Bump. I am also stuck in this state
I'm new to this device and already I'm extremely confused. I tried flashing TWRP the old school method and found out very fast that it was a no go. Upon reading around, I fount the following guide and booted TWRP:
https://forum.xda-developers.com/mi-a1/how-to/lineageos-gapps-magisk-twrp-dolbyatmos-t3762939
The problem? I can install DotOS, but as soon as I try to flash the GAPPS, I get an error (it claims that I am on 7.1.2, but I'm using the latest DotOS version which is 8.1.0 based). Since from what I understand the recovery seems to be tied to the boot.img (like the Sony Ericsson Xperia Play), I believed simply rebooting into recovery would help. Unfortunately this boots into stock recovery for 8.0.0 (mind you I was on 8.1.0 stock). Upon reading around on how to install TWRP on the phone itself, I found this thread:
https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-1-1-0-touch-recovery-t3688472
This is the bigger headache. After following the instructions which are clear as day, I encounter similar issues to half of the replies in that thread. Another issue is that there is no explanation on whether you should be on stock first or...? Secondly, nothing is said on which "slot" (a or b) to flash your desired rom. So my default slot was b, I switched to a to flash the TWRP installer and so on as per instructions. I then assume I am to switch back to slot b for my rom to be installed. The issue is that after trying to install the GAPPS, I am faced with the issue again of the 7.1.2 detected. The only way to get around this is to flash it in slot a, but then the device will never boot. I'm very confused?
Use this twrp. Then you flashed twrp, wipe, install ROM, reboot into recovery again and flash gapps.
Crossvxm said:
I'm new to this device and already I'm extremely confused. I tried flashing TWRP the old school method and found out very fast that it was a no go. Upon reading around, I fount the following guide and booted TWRP:
https://forum.xda-developers.com/mi-a1/how-to/lineageos-gapps-magisk-twrp-dolbyatmos-t3762939
The problem? I can install DotOS, but as soon as I try to flash the GAPPS, I get an error (it claims that I am on 7.1.2, but I'm using the latest DotOS version which is 8.1.0 based). Since from what I understand the recovery seems to be tied to the boot.img (like the Sony Ericsson Xperia Play), I believed simply rebooting into recovery would help. Unfortunately this boots into stock recovery for 8.0.0 (mind you I was on 8.1.0 stock). Upon reading around on how to install TWRP on the phone itself, I found this thread:
https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-1-1-0-touch-recovery-t3688472
This is the bigger headache. After following the instructions which are clear as day, I encounter similar issues to half of the replies in that thread. Another issue is that there is no explanation on whether you should be on stock first or...? Secondly, nothing is said on which "slot" (a or b) to flash your desired rom. So my default slot was b, I switched to a to flash the TWRP installer and so on as per instructions. I then assume I am to switch back to slot b for my rom to be installed. The issue is that after trying to install the GAPPS, I am faced with the issue again of the 7.1.2 detected. The only way to get around this is to flash it in slot a, but then the device will never boot. I'm very confused?
Click to expand...
Click to collapse
To install twrp, use twrp 3.2.3 from abishek (lineageOS) or from cosmicdan.
This phone have slot a/b. For installing twrp it doesn't matter from which slot you install as it will install in the boot partition, not in system.
First do facory reset, you don't have to be on stock.
For custom rom zip if you are in slot a it will be installed in the slot b. After installing rom install twrp again as it's deleted when you install new rom and change slot, reboot and install gapps according with the rom 8.1 or 9.0 and magisk, it installs on the same slot..
Cosmicdan twrp have an option to install rom zip on the same slot and have a survival option for twrp, so you don't have to install twrp when you install a rom or a new kernel.
ccalixtro said:
Use this twrp. Then you flashed twrp, wipe, install ROM, reboot into recovery again and flash gapps.
Click to expand...
Click to collapse
This is the link for twrp:
https://forum.xda-developers.com/mi-a1/development/treble-twrp-installer-treble-manager-t3793637
Reboot recovery after u flash rom, then flash gapps,magisk
I was using PIXEL EXPERIENCE 9.0. Then to update Rom i tried to install Twrp. I mistakenly booted nougat twrp from fastboot
Then after i noticed that i was trying nougat twrp instead of Oreo..i downloaded oreo twrp and booted...but when i tired to touch is was faulty..mean for suppose i triede to open mount menu it touch on Reboot in twrp.
Then i decided to flash stock rom.
I downloaded latest one and flashed but result was same... Touch problem...
PLEASE TELL.ME FIX
Recently I tried flashing custom recovery but when I tried to flash it,it end at step one and a message pops up saying to flash additional zips reboot to recovery to change to updated slots and the process stop I have 3.4.0-1 of twrp please help me asap
I wouldn't recommend using TWRP 3.4.x personally. If it were me I would stick to 3.3.1-32, but it's already installed so take your chances if you want. Rebooting to install other zips is just a warning because ROMs are installed to opposite slots, so you must reboot recovery to switch the active slot. Even if you switch the slot in TWRP the change won't happen until you reboot. Also note many ROMs include a recovery. If PA includes a recovery you need to re-install TWRP before you reboot.
My Lineage Guide works for most custom ROMs.
Normally you would reboot recovery, and install Gapps, Magisk, those sort of things. I did a quick google search and think I found the ROM thread, and it looks like Gapps is included so you wouldn't reboot for that. If you are installing just PA, you would just reboot to the system.