Hey guys, I'm a longtime XDA browser but hardly ever post. I have the MXPE rooted with the newest TWRP build and has been running great since I got it. last night flashed the Deodexed 6.0 build from AICPs 5.1.1. I had some issues with the SD card being mounted as internal storage and erasing something so I tried to flash back to stock as my nandroids weren't seen as usable.
Long story short when I flashed back to stock, the recovery would never take. I've flashed the stock recovery and twrp to no avail. For some reason it wont actually stick. Everything else is back to stock but that. When I used the win toolkit and tried to flash twrp again it said something about the folder locations so I'm wondering if I messed something in the partitions.
Question is, have you guys ran into this issue or have any insight on where to go from here? I've looked around but I couldn't find a post that the same as this issue. As a side note, I can get into the bootloader just fine.
I appreciate any info that someone can provide.
Flash twrp. Reboot back to recovery from recovery. Reboot system.
Hopefully it's that easy. Stock os flashes stock recovery on boot. Rebooting recovery from recovery prevents that from happening.
From TWRP:
"Note many devices will replace your custom recovery automatically during first boot.... Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."
mxpe 6.0
Thanks for the info ffejy462. What happens when I try to flash TWRP and it doesnt stick? I know for a fact that I can boot into it temporarily with fastboot boot and the recovery file. Should I just flash it from there?
THEFILLTER said:
Thanks for the info ffejy462. What happens when I try to flash TWRP and it doesnt stick? I know for a fact that I can boot into it temporarily with fastboot boot and the recovery file. Should I just flash it from there?
Click to expand...
Click to collapse
I'm sorry I didn't see this sooner. Flash recovery with fastboot. Boot into recovery. From reboot menu in recovery, select reboot recovery. Twrp will patch so recovery isn't lost again.
mxpe 6.0
That did it. thanks alot ffejy462!
Hello all, I unlocked my nexus 4 installed TWRP ( tried several versions) currently 3.0.3 and now TWRP bootloops..
Any thoughts or fixes for this ?
I added a screen capture, " could not mount /data and unable to find crypto footer" unable to mount storage, etc.
Did you try 2.87? Is the phone encrypted?
I haven't tried 3.0.3, but 3.0.2 works flawlessly on my N4, with device encryption.
TWRP seems to be failing at decrypting your data partition.
Does Android boot in normal mode?
I will try 3.0.2 and report back... thanks for the help!
precisely yesterday i was in the same situation when i was trying to downgrade to 4.4.4 oem.... i fix it installing other recovery, recovery-clockwork-touch-6.0.4.7-mako http://www.4shared.com/zip/6v3Z7Ghrba/recovery-clockwork-touch-6047-.html
but i install in MAC, in windows i don´t know if is the same process, i was follow this video about how to unlock bootloader in mac
when i install the recovery and enter in fastboot, i put in restart, it will request for fix (yes or no, you choose) the root, i choose NO, and the nexus 4 wake up again in the Cooked Rom, so i try again downgrade :fingers-crossed:
hope it work for u like me
So here is my problem i can't flash any custom rom i tried twrp cwm philz edition and the problem is the same i get stuck at* patching system image unconditionally at the very beginning of the blue line i tried with resurrection remix, slimrom, and other ROMs and when trying MIUI 8 i get an error couldn't mount system rw
Itried with adb sideload get stucked at 45%.
I e2fsck -y /dev/block/mmcblk0p23 wich is my system partition and fixed so many error but the problem stay the same ... i can flash a recovery or a kernel with no problem with TWRP the problem as i think when dealing with the system partition .. so im stuck with a stock rom that i flashed with odin btw who works great .. so is it my system partition messed up or the gpt table isnt right or is there a way to flash custom rom using odin
It could actually be the permissions. Other problem could be the recovery.
hi i know it's been a while since, but have you found a solution? I am getting exactly the same problem and tried everything possible. at the stage ready to sell it off ebay and upgrade if this doesn't work.
I had same problem with galaxy note 3 sprint variant and twrp 2.8.7.0 helped
If you are not getting twrp 2.8.7.0 try two or three lower versions
Don't use the latest twrp it won't work
1. Try to put custom rom to external storage microSD card or USB otg
2. If not helped 1. solution try older version TWRP 2.5.xx
This 2 solution help for me sometimes
You need to flash the latest TWRP.
Drhedphuk said:
You need to flash the latest TWRP.
Click to expand...
Click to collapse
Thanks, and I was on the latest already at the time of posting. Will try the two suggestions with getting the older versions of TWRP 2.8.7.0. Interestingly enough the CWM has done the same thing, as well as TWRP's sideload.
Will post back later.
tried all the possible versions of twrp, sideload, cwm, different roms, fixing permissions and formatting the partitions...no luck, still gets stuck at 45%. I guess it is time to give up and get myself a new xmas present.
I'm a relative beginner to flashing and rooting I used the ZTE axon 7 toolkit and now my phone is stuck in the boot animation. I can get into TWRP but when I flash the LineageOS zip in TWRP I get the following in red: Updater Process ended with Error: 7 Error Installing zip file '/external_sd/lineage-14.1-20170605-nightly-axon7-signed.zip' Updating Partition details....
....done Not sure what I'm doing wrong any help appreciated.
Did you fully wipe system before installing lineage? Did you make a back up of stock before installing in TWRP? Did you make sure your specific model is supported for that particular ROM?
Bad download?
Install Nougat bootloader.
I installed Nougat and tried to flash it using TWRP it installed successfully but when I turn the phone on I see this error image imgur.DOTcom/a/1EljH I can't insert links because I'm under 10 posts it seems)
How could I flash a stock rom if the recovery is now stock?
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