I hade AICP installed on my N910f Note 4 and had encrypted it. I found that I could not update my ROM or really flash anything. I tried updating to the latest TWRP reading there may be support for encrypted phones but never got a password prompt. I tried to flash the stock rom with odin hoping if I could load that, samsung has an easy decrypt button but after flashing the german and romanian versions the phone wouldnt boot. Now I am stuck with an encrypted phone with no ROM installed that's bootable. How can I unencrypt it? At this point I would deal with it being encrypted just to get it booting again.
I will point out that my first flash of the stock german ROM worked and it was asking me for a password in German and I thought it wanted my pin to decrypt and it didn't work. I later read that it may have been asking for my google account password which I could provide except now I can't get it to boot after reflashing it a few times. If anyone knows of a way to get a ROM to flash and boot then that would be great or a recovery that works with encrypted phones so I can enter my pin to decrypt it and then simply flash a ROM zip file.
This turned out to be really simple. Flashing the German stock rom worked. It also unencrypted my phone. The problem I was having with the flash was with a custom ROM you need to go back and do a factory reset after the stock ROM flash, then reboot. After that it booted and I was able to flash TWRP with odin and flash my AICP zip, do a titanium restore and all is well.
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
Hey there!
I'll be honest, I don't even know how to start but here I go:
I have a MIA1 since a year ago aprox. when I bought it I rooted it and flashed a couple roms, I usually flash roms mostly beacause of "the volume buttons to skip tracks thing" and I root it beacause I can't live without Viper4Android, so several months ago I flashed Resurrection Remix, wich I believe have the Treble partition system that only works with CoscmicDans twrp. So I think I did everything right and flashed it, but now I wanted to change roms(even to stock as I saw gravitybox runs again) and I couldn't, I got the "unable to mount vendor" Message.
I tried everything, even flashed stock with MIflash and seemed that that did the trick, but... now I can boot twrp through fastboot but when I flash it through twrp and restart to recovery I get "The system is destroyed" wich seems like a very bad message, Its weird but the stock rom runs anyway.
So here comes the question: Can someone tell me what to do to have my phone back to stock, then root it again and be able to flash other roms again? I'm quite sure that it has something to do with the "vendor thing" ,maybe I didn't reverse the treble-conversion or something? with that thing my head just doesn't get it....
Well thanks for reading, have a nice day!
Look, same thing happened to me with that recovery, currently I have no TWRP installed (actually no recovery installed) and I ignore it. If I want to do anything with recovery, I just boot it with fastboot and do what I want because I heard most users can't install TWRP since Pie (or you can, I don't really know).
To flash custom ROM I did following:
If you have any TWRP backup, restore "vendor" partition and untrebalize.
Flash all Pie stock ROMs since January to get modem properly working.
After done, just boot TWRP and flash what you want.
I had few problems with it, but that's how I came from full stock to EvolutionX w/ Magisk and ExtremeKernel
Thanks, I'll do that but, how do I "untrebalize"?
I guess you have to manual load the TWRP on both slots. And make sure you use one with persist function
Thanks, I just read in cosmicdan post that in order to untreble I have to flash in EDL mode with MIFLASH, I'll try that, also, this is weird but I can't find the nandroid backup I made so to restore the vendor part would it work flashing the resurrection remix again? so it creates it again?
For a full stock flash, just use the fastboot version ROM. It takes about 15-20min but will work for sure
Hey y'all, I've been away from the development community and tinkering with this device, work and life got in the way. I've been running a custom rom (sky dragon) and I believe it's based off 9.013 Android for over a year now. It's a great custom rom but it's time for something different.
I'd like to flash the latest and greatest stock oxygen OS which is now Android v10. Being a longtime pixel user, I'm very comfortable updating via fastboot. I was wondering if I downloaded the full ROM from oneplus' website and used the flash-all. bat method if that would be a smooth way to cleanflash the device. I'll make sure to back up everything I need so wiping the device entirely is no issue.
Thanks!
I personally prefer the Fastboot ROMs it will do both slots at once.
OhioYJ said:
I personally prefer the Fastboot ROMs it will do both slots at once.
Click to expand...
Click to collapse
can I flash the latest stock fastboot ROM coming from Android 9 though?
You'll have to choose reset everything option in the factory recovery for it to boot (under advanced IIRC) to get it to boot. Otherwise it will most likely just keep booting to recovery. Thats what happens when you go from a custom ROM to a OOS too.
OhioYJ said:
You'll have to choose reset everything option in the factory recovery for it to boot (under advanced IIRC) to get it to boot. Otherwise it will most likely just keep booting to recovery. Thats what happens when you go from a custom ROM to a OOS too.
Click to expand...
Click to collapse
I figured it wouldn't be a smooth process!!! So if I fastboot flash the latest Android 10 build from a custom Android 9, I'll boot loop into recovery but choosing "reset everything" should allow me to boot into the OS? I'll give it a shot! thanks.
Hey, I'm new here when it comes to writing forum posts, so bare with me.
I've had this tablet for a few years now and I had flashed it with one of Magendanz roms (Nexus Stock) and I wanted to change to the LineageOS rom he had. I downloaded the .zip file and copied it to my sdcard and tried to get into TWRP to flash it. I did restart to recovery in the OS and once it restarted, it's been doing a boot loop ever since. I have tried using Odin to flash the rom that way, but for some reason it'll keep doing a boot loop after it's done flashing and restart. I can try going back to the stock firmware if it's a final option to get this tablet working again, but I would love to see if I can get LineageOS to work.
DengekiMatsuko said:
I did restart to recovery in the OS and once it restarted, it's been doing a boot loop ever since.
Click to expand...
Click to collapse
I had a similar issue once. It turned out that after flashing, not all the partitions mounted properly.
Are you still using TWRP? Boot to recovery, and go into "Mount". Make sure the system and other partitions are actually ticked. That solved the problem for me, and I was able to successfully boot to the system.
Hopefully your issue is that simple!
I managed to brick my Tab A 10.1 (2019) last year by dirty flashing ROMs I shouldn't have. I properly munted it, I couldn't even get into recovery. But I could still get into download mode with a USB cable plugged in to my laptop (it needed to be plugged in for download mode to come up). I flashed the stock ROM, which made it bootable again, which then allowed me to re-flash TWRP and then Magendanz' LOS18.1 ROM.
If you completely break your tablet, reflashing the latest stock ROM for your region is a great way to get back to a familiar starting point. You can then follow people's guides online to get where you want to be.