Hello everyone,
A few weeks ago, I bought a reconditionned OnePlus 5T and installed /e/ on it. Now, I would like to install back OxygenOS.
My problem is that I can’t manage it.
As I couldn’t access to recovery (TWRP) anylonger (don’t know why, maybe something to do with the fact I flashed the 5.1.7 firmware a few days ago, I don't have a clue), I flashed an early Blu Spark one (3.2.1 as the 3.3.x ones won't work on my device). And it worked, I can access recovery through this one.
But when I try to install any OOS zip, via recovery Install menu or by sideloading it (downloaded from the OP website (the most recent one, or from the mirrors referenced on this xda forum, I tried several zips but don't really know which one is really relevant), it fails.
And the only thing I can do is installing back /e/. I tried several ways of doing it, following several guides but even the ones for the ultimate guide available on the One Plus Forum won't work (can't make it recognised by any device manager, maybe the fact that I'm running Ubuntu and not Windows).
So that, for the time being, I’m stuck with /e/OS (based on a LineageOSrunning Android 8.1).
There surely is a step or a file I missed, but which one... Any idea anybody ?
I finally got it working. Through the*********** 's guide.
donatienb said:
I finally got it working. Through the*********** 's guide.
Click to expand...
Click to collapse
Hi !
Im interested in going back to OxygenOS from /e/os because the new builds are on android 11, and my current /e/os build is on android 8.1
The idea is to get OxygenOS back, upgrade using OxygenUpdater, and then install de latest android 11 /e/ build.
So what was the name of that guide ?
Thanks
Related
Hi all, I posted a question in the giant general "ask question here" thread but I'm thinking this might be more nuanced than I realize after I saw that thread about downgrading=brick.
I've got Z00A, I bought it new a month or two ago--'just tested' seller said but it looks like it was used up until october of last year. It was running android 5 and CM 12.1 (I think) and had TWRP 2.7 (I think). When setting it up I saw update about an update "CM13... nightly". Installed it, booted phone and it had no gapps and tried too many half assed solutions so I started over and installed TWRP 3, got Open Gapps and CM13-0522 and started over. Seemed to work great but then I noticed stuff like the camera would freeze or take pics that would come out a blank green screen and the mobile data connection almost never worked (though I'm on new carrier) and a few other problems. Is it possible that since I went from CM12 (and presumably no updates since october) straight to CM13-0522-nightly that I missed or somehow 'skipped' a bunch of firmware updates? Does the latest version not include the updates from previous versions?
I was going to try rolling back to stock via one of the ASUS ROMS but I have no idea what version to get because I cannot determine what I currently have or what the phone had to begin with (version as in "V2.20.##.###"). Also, I don't think I installed any ASUS rom before----I just installed CM13 and OpenGapps. Then I see posts about sideloading the ASUS firmware roms in regard to users trying to revert/reinstall firmware: is this what I should be doing?
I read the FAQ thread and searched what I could but it has only left me more confused. I'm fairly technically apt but cell phones are not at all my usual foray so any help is greatly appreciated.
ohituna said:
Hi all, I posted a question in the giant general "ask question here" thread but I'm thinking this might be more nuanced than I realize after I saw that thread about downgrading=brick.
I've got Z00A, I bought it new a month or two ago--'just tested' seller said but it looks like it was used up until october of last year. It was running android 5 and CM 12.1 (I think) and had TWRP 2.7 (I think). When setting it up I saw update about an update "CM13... nightly". Installed it, booted phone and it had no gapps and tried too many half assed solutions so I started over and installed TWRP 3, got Open Gapps and CM13-0522 and started over. Seemed to work great but then I noticed stuff like the camera would freeze or take pics that would come out a blank green screen and the mobile data connection almost never worked (though I'm on new carrier) and a few other problems. Is it possible that since I went from CM12 (and presumably no updates since october) straight to CM13-0522-nightly that I missed or somehow 'skipped' a bunch of firmware updates? Does the latest version not include the updates from previous versions?
I was going to try rolling back to stock via one of the ASUS ROMS but I have no idea what version to get because I cannot determine what I currently have or what the phone had to begin with (version as in "V2.20.##.###"). Also, I don't think I installed any ASUS rom before----I just installed CM13 and OpenGapps. Then I see posts about sideloading the ASUS firmware roms in regard to users trying to revert/reinstall firmware: is this what I should be doing?
I read the FAQ thread and searched what I could but it has only left me more confused. I'm fairly technically apt but cell phones are not at all my usual foray so any help is greatly appreciated.
Click to expand...
Click to collapse
You can flash mr gouravs work here via twrp
download all his files to phone ... follow his flashing procedure and you will be on the latest stock via twrp ..
http://forum.xda-developers.com/zenfone2/development/stock-rom-ul-z00a-ww-2-20-40-168-t3354526
Hello all,
I recently tried to flash the latest LineageOS (lineage-14.1-20170717-nightly-crackling-signed), but without any luck (stuck in bootloader/recovery mode). I had no backup so I tried a bunch of old CM ROMs until I found a working one (an unofficial CM14 release found on cyanogenmods.org, can't post links yet).
Now I wonder why this particular ROM is the only one I can install.
So far the only difference I found is that it only targets armeabi-v7a and armeabi ABIs, and not arm64-v8a as the LOS ROM does.
So I checked with Droid Hardware Info and it tells me I have indeed an ARMv7 architecture.
But everything I read about the Swift tells me it's a 64 bits architecture.
Could someone tell me what I am missing here? Is it all normal or did I buy a fake Chinese copy of a Swift?
Thanks
Welcome. I doubt anyone would fake a swift. Most likely you didn't flashed a compatible fastboot image and baseband. Unlock your bootloader and fastboot flash https://www.androidfilehost.com/?fid=457095661767123627 then flash twrp 3.1.1.0. https://forum.xda-developers.com/wi...ent/recovery-unofficial-twrp-3-0-1-0-t3350351
Hello Dmitriy.WZR, thanks for the reply.
Indeed I don't really believe I have a bad phone It has to be something I did.
But so far I only flashed a recovery image (twrp-3.1.1-0-crackling), after unlocking the bootloader, as explained in the LineageOS wiki Install LineageOS on crackling. Then I installed LineageOS, GAPPS and the LineageOS addonsu. Then bootloop.
Not sure I know what is a "fastboot image and baseband".
thomas.gillet said:
Hello Dmitriy.WZR, thanks for the reply.
Indeed I don't really believe I have a bad phone It has to be something I did.
But so far I only flashed a recovery image (twrp-3.1.1-0-crackling), after unlocking the bootloader, as explained in the LineageOS wiki Install LineageOS on crackling. Then I installed LineageOS, GAPPS and the LineageOS addonsu. Then bootloop.
Not sure I know what is a "fastboot image and baseband".
Click to expand...
Click to collapse
Same happened to me a few months ago. The solution that worked for me was:
1. Remove the battery and reinsert it.
2.Go to recovery mode.
3.Wipe everything including internal storage.
4.Download a fresh copy of Lineage os and gapps and flash. Try avoiding su.
5.Reboot
Hello nsa02,
I did that several times and it didn't help. Did it again to be sure, but nothing new. Thanks anyway.
I hope I'll have better luck with @Dmitriy.WZR answer, I'll try to figure out what is this radio-20161215-crackling file and what I can do with it.
Ok, got it!
Seems I had an old bootloader (an ugly one with a terminal-like style and a big green START on the top), very different from the Cyanogen one.
Used radio-20161215-crackling file to flash my firmware (or bootloader, no sure what is what yet), as explain in the [RECOVERY][crackling] TWRP 3.1.1-0 [OFFICIAL] thread by @beroid.
Then latest LineageOS and GAPPS installed without problem (didn't try the su addon), and Droid Hardware Info tells me I have an arm64-v8a indeed!
Many thanks to @Dmitriy.WZR
thomas.gillet said:
Seems I had an old bootloader (an ugly one with a terminal-like style and a big green START on the top), very different from the Cyanogen one.
Click to expand...
Click to collapse
That's actually the newest one (the one, that come with Android 7-based firmwares). Sadly enough this one is incompatible with custom ROMs, so you need a cyanogen-besed bootloader, yes.
Glad you make it, wishing you a rock-stable working device
Hey,
I have to apologize, since I am new in this topic. I assumed it to be a bit easier. However.
I bought a OnePlus 7 Pro and went through some up and downs now. Finally I did the following:
I unlocked the bootloader
I updated to OxigenOS 10.X, X I guess was 3 or so.
I managed to find the right TWRP image that worked perfectly: https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
I went into recovery TWRP and installed the zip, additionally magesk or so. Was somewhere suggested to do so.
I rebooted into OxygenOS. So far everything was working.
I rebooted into recovery mode, into the TWRP app.
Now my intention was to install LineageOS, I choose 17 because the OxygenOS 10, I heard was based on Android Q
I wiped out the storage as suggested in the corresponding manuals
I installed LineageOS 17 zip-file via TWRP
I rebooted => Result: Nothing works anymore.
What means Nothing: When I start the phone I come into the FastBoot Bootloader Menu. That's it. No recovery. No TWRP. No OxigenOS and for sure no LineageOS. For sure I can flush img files. But non TWRP image I have chosen worked again like before.
Having spent a day now in this topic as a newbie leavs me a bit weak and disappointed now. Since I probably miss a little bit the appropriate vocabulary I am not able to find something helpful in the net.
So, what am I looking for. I need to bring that phone back into something usable. Maybe into it's original state. Still prefer to have a LineageOS 1X with TWRP installed. It was a great 5 minutes experience. For installing LineageOS 16 I guess I would have needed OxygenOS 9 installed and not 10 (like after my update).
So is there any way to safe my phone?
I was trying to update the OS on my Nexus 7 2013. I was able to connect it to my PC and unlock it and erase user data using adb commands. But after that it will not go past the Google logo in Recovery or regular Start mode. When I run "adb devices" it does not show up, though my computer does see it since I can run the lock/unlock adb commands and they work. I have uninstalled/reinstalled different adb drivers for the devices. I've tried using 2 different PCs. I can not get adb to fully recognize the device. I tried the Skipsoft Android Toolkit, and it too reports "no device detected".
Have I completed bricked the device? Or is there some way out of this that I haven't though of/found on the internet yet?
I hope someone here can help me!
Thanks!
Assuming you're on stock, try flashing a factory image from Google themselves. This reflashes everything, like stock OS, recovery, bootloader, etc. I'd choose the latest version found here: https://developers.google.com/android/images#razor As long as you understand that this wipes data, then give this a shot and let us know the results!
I found the "Nexus Root Toolkit" windows app. It was able to communicate with the Nexus 7 and restore the factory ROM and I could get it to boot! Now, I've tried about a dozen times to install LIneage, but it keeps getting an error the point of trying to install the ROM, and I haven't figured out what the error means or how to correct it. I've tried multiple TWRP versions and Lineage OS versions. It's driving me nuts!
adamwsh said:
I found the "Nexus Root Toolkit" windows app. It was able to communicate with the Nexus 7 and restore the factory ROM and I could get it to boot! Now, I've tried about a dozen times to install LIneage, but it keeps getting an error the point of trying to install the ROM, and I haven't figured out what the error means or how to correct it. I've tried multiple TWRP versions and Lineage OS versions. It's driving me nuts!
Click to expand...
Click to collapse
Are you trying to install the official version of 17.1? If so, you'll need to look at the install guide on the LineageOS website here: https://wiki.lineageos.org/devices/flox/install
As far as I can tell, you cannot use TWRP, or at least the official TWRP, with this image. You'll need to use the LOS 17.1 Recovery found on the downloads page. If you haven't already, you're going to need to repartition the device with the instructions found on the install guide that I linked.
If this isn't the ROM in question check out the thread for that ROM and see if anyone else has any issues with installation.
NTGDeveloper said:
Are you trying to install the official version of 17.1? If so, you'll need to look at the install guide on the LineageOS website here: https://wiki.lineageos.org/devices/flox/install
As far as I can tell, you cannot use TWRP, or at least the official TWRP, with this image. You'll need to use the LOS 17.1 Recovery found on the downloads page. If you haven't already, you're going to need to repartition the device with the instructions found on the install guide that I linked.
If this isn't the ROM in question check out the thread for that ROM and see if anyone else has any issues with installation.
Click to expand...
Click to collapse
Thank you! I did manage to get 18.1 to flash and load, after using a repartiion tool I found. However, I can't get GAspps to load, saying there isn't enough room on the partition. Now, I'm trying to use NRT to get back to stock (like I was able to do earlier) but now it is getting stuck at the Android 6 startup animation (4 round icons). I'm wondering if it is because I ran the partition update and somehow have to put that back to get the stock ROM to work.
The only suggestion that I would have is to flash the smallest GApps package possible, and before flashing LOS 18.1, wiping pretty much everything, then flashing LOS and GApps. Since OpenGApps doesn't make an Android 11 package yet, I don't know much about the other package providers, but that's all that I can think of. Hope this helps!
NTGDeveloper said:
The only suggestion that I would have is to flash the smallest GApps package possible, and before flashing LOS 18.1, wiping pretty much everything, then flashing LOS and GApps. Since OpenGApps doesn't make an Android 11 package yet, I don't know much about the other package providers, but that's all that I can think of. Hope this helps!
Click to expand...
Click to collapse
I wound up flashing Stock Android 5.0 and it worked. Now I'm updating to 6 via the software upgrade in the OS itself. I feel like this thing is just too old and not large enough memory to handle a custom OS.
Hi all,
I am using the weekly xiaomi.eu ROM til almost year now. The latest update from 21.4.28 to 21.5.12 somehow went wrong. I used twrp-3.4.0-2grus.img which was working perfectly for all previous updates. Now my Mi 9 SE is always booting into fastboot mode instead of MIUI. When I try to boot into one of the official TWRP versions v3.5.x the phone strangely boots into MIUI but unfortunately many things don't work (phone calls, fingerprint, WLAN, speaker). I tried to use a newer TWRP (twrp-3.5.A9-grus-geoanto555.img) to flash any of the mentioned images and the latest 21.5.20 but same result.
Is there anything I can do except of resetting to factory default? I would like to avoid loosing all my data and settings.
Thanks for any help!
Buzzy
BuzzyB said:
Hi all,
I am using the weekly xiaomi.eu ROM til almost year now. The latest update from 21.4.28 to 21.5.12 somehow went wrong. I used twrp-3.4.0-2grus.img which was working perfectly for all previous updates. Now my Mi 9 SE is always booting into fastboot mode instead of MIUI. When I try to boot into one of the official TWRP versions v3.5.x the phone strangely boots into MIUI but unfortunately many things don't work (phone calls, fingerprint, WLAN, speaker). I tried to use a newer TWRP (twrp-3.5.A9-grus-geoanto555.img) to flash any of the mentioned images and the latest 21.5.20 but same result.
Is there anything I can do except of resetting to factory default? I would like to avoid loosing all my data and settings.
Thanks for any help!
Buzzy
Click to expand...
Click to collapse
Have you checked on their forum/in the thread:
MIUI 12.6 - 21.5.20/21
Status: RELEASED RULES WHEN POSTING 1. If a ROM is not published DONT ASK ABOUT ITS ETA 2. If a ROM is not published DONT ASK why! 3. If a ROM is available, download it and use it 4. If a ROM has bugs, post the bug to the bug section if the BUG is not already listed 5. If you use any form of...
xiaomi.eu
what is the proper TWRP to use with your device?
I don't have 9 SE but 9 T (and I'm using the latest official 3.5.2_9-0 for my device) but there was a lot of discussion about TWRP versions required for 21.5.20 (and future Xiaomi.eu weeklies) - generally TWRP 3.5+ versions must be used (for some devices n/a and then only specific 3.4 versions can substitute)
Hi zgfg,
thank you for your answer. I just read the whole thread but the update seems to work for the MI9SE in general. Initially I was using the twrp-3.4.0 which worked fine for all previous updates. I also tried the official TWRP version 3.5.x from twrp.me but they did not work for me. Every time I am fastbooting them my phone does not boot to recovery. Strangely after the failed update trying to boot the official TWRP leads to a boot into MIUI instead of fastboot. I dont't know what went wrong.
I also found this thread https://xiaomi.eu/community/threads/official-twrp-for-mi-9-se.58589/page-4. The mentioned twrp version from geoanto boots and lets me install the ROM but with the same outcome.