So i'm trying to install a new custom rom. I was following a guide i had found on this website.
I was successful in unlocking the bootloader and rooting the device but something went wrong along the way.
I'm trying to sideload the rom.zip folder onto the device so i can install it. I'm able to get it on there but immediatly it attempts to install and it fails, this is what i get after the zip file hit's 100% sent...
Restarting adbd
Finding update package...
Opening update package...
Installing update...
Warning No file_contextsTarget: google/occam/mako:5.1.1/LMY48T/2237560:user/release-keysChecking size of the /system partition...Too Small/systempartition detected (must be at least 1333788672 bytes). You need to repartition your device before installing this ROM.E:unknown command [Log]
(Status 7)
Installing aborted.
I was following this guide here https://forum.xda-developers.com/nexus-4/general/nexus-4-guide-unlock-bootloader-root-t2266654
however some of the attatched links to install stuff were missing so i had to hunt elsewhere for what i needed.
But i am stumped on what to do next. i'm not overly worried as it's not my main phone, just a backup i was trying to replace a Not working so well previous OS it had on it. Any help would be very appreciated
Obviously you are trying to install an Android 9 or 10 based ROM using 7 years old installation instructions.
The given error message already tells you what to do:
"Too Small/systempartition detected (must be at least 1333788672 bytes). You need to repartition your device before installing this ROM".
Look e.g. here in the initial post:
https://forum.xda-developers.com/nexus-4/development/rom-lineageos-15-1-t3758779
There you'll find some hints for how to repartition, I used the directly linked script. It just increases the system partition by decreasing the cache partition (it doesn't have to be that big anymore) and leaves the data partition as it is.
Ty for the response. I decided that's not the route i want to take and simple just want to flash a stock OS back onto the device. The phone is using Clockwork Recovery mod v6.0.4.7 witch the phone will always go to via recovery mode.
Everytime i try to sideload a factory image from https://developers.google.com/android/ota
i get errors
i get
restarting adbd
Finding update package...
Opening update package...
Installing update...
This package is for "hammerhead" devices; this is a "mako".
E:Error in /tmp/update.zip
(Status 7)
Installation aborted
I also have gotten this as well
restarting adbd
Finding update package...
Opening update package...
Installing update...
Installation Aborted.
There is only one OS a custom rom that seams to ever work and that is Lineage OS 15.0.1
but i don't like it because regardless of everything i have tried i simply cannot get Google apps on it.
Just would like to get a factory Android OS back onto it.
Thank you
Again there's an absolute clear error message. Please find out what a "Hammerhead" device is, just type it in the search field of XDA...
If you have problems with Gapps and LOS 15 (most probably due to system space problems), I would recommend you to try LOS 14.1 - there are current builds here in the forum.
The stock rom is very old and thus has a very outdated security patch level.
Holzhacker said:
Again there's an absolute clear error message. Please find out what a "Hammerhead" device is, just type it in the search field of XDA...
If you have problems with Gapps and LOS 15 (most probably due to system space problems), I would recommend you to try LOS 14.1 - there are current builds here in the forum.
The stock rom is very old and thus has a very outdated security patch level.
Click to expand...
Click to collapse
i'm aware of witch device each one is for i just wanted to see if it would work as i did initially want a newer version of the OS on the phone as i had issues with the previous ones, i appear to be having zero device issues with the current 8.1 ore lineage OS variant.
I even tried "occam" witch is the stock flavors for this device, i'd get the same message and or just a simple "installation aborted"
i'm doubtful of it being a space issue as i am showing 12gbs of free space with the current operating system on it. I can't get the g apps to sideload onto the device, i even tired manually downloading the google play apps and such onto the phone from my computer via APK files downloaded online, it installs but immediately crashes and won't run.
i'm certain i've tried other and older rom packs on this site as well and i run into the same issue where it just aborts install, for some odd reason this one Lineage OS 8.1 variant works but nothing else does.
Gibson295 said:
i'm aware of witch device each one is for i just wanted to see if it would work as i did initially want a newer version of the OS on the phone as i had issues with the previous ones, i appear to be having zero device issues with the current 8.1 ore lineage OS variant.
I even tried "occam" witch is the stock flavors for this device, i'd get the same message and or just a simple "installation aborted"
i'm doubtful of it being a space issue as i am showing 12gbs of free space with the current operating system on it. I can't get the g apps to sideload onto the device, i even tired manually downloading the google play apps and such onto the phone from my computer via APK files downloaded online, it installs but immediately crashes and won't run.
i'm certain i've tried other and older rom packs on this site as well and i run into the same issue where it just aborts install, for some odd reason this one Lineage OS 8.1 variant works but nothing else does.
Click to expand...
Click to collapse
So does this mean you were fully aware that you were trying to install a Nexus 5 ROM on a Nexus 4? You can't expect this to work.
Regarding the Gapps: They are installed on the SYSTEM partition. What you can see in the OS as free space is only related to the DATA partition. So it doesn't matter how much free space is shown there. LOS 15.1 uses much more space on the system partition so that it's hard to get even the pico version of OpenGapps on it. Some builds worked, some not - as I experienced myself. I've had every version of LOS on my Nexus 4 and 15.1 was the hardest to get the Gapps installed.
This could also be a problem of the recovery. I don't know much about Clockwork as I've always used TWRP.
Holzhacker said:
So does this mean you were fully aware that you were trying to install a Nexus 5 ROM on a Nexus 4? You can't expect this to work.
Regarding the Gapps: They are installed on the SYSTEM partition. What you can see in the OS as free space is only related to the DATA partition. So it doesn't matter how much free space is shown there. LOS 15.1 uses much more space on the system partition so that it's hard to get even the pico version of OpenGapps on it. Some builds worked, some not - as I experienced myself. I've had every version of LOS on my Nexus 4 and 15.1 was the hardest to get the Gapps installed.
This could also be a problem of the recovery. I don't know much about Clockwork as I've always used TWRP.
Click to expand...
Click to collapse
Hm well i admit my failure with that, but I did say that i tried Stock roms for the Nexus 4 themselves and they still were not installing. I will try to sideload an Older LineageOS Variant then, but as before it was never giving me a Storage or space issue when trying to load the GApps.
Well i have some good news now i seam to have succeeded in getting Lineage OS 14.1 (Android 7.1.2) Installed on the device along with Google apps, seams to be running fairly well so far, shame it's not supported OS anymore but it's a backup phone and i simply just wanted to be able too have my Spotify on it in case i ever have to use it otherwise lol.
:good:
I will not require help further thank you for your comments
Related
I've been using Quarx's CyanogenMod 11.0 (KitKat 4.4.2) since its January 20 release. However, my phone starting to become slow with the time (nothing related to the build but the extensive device use & data exchanging). Today i decided to upgrade to most recent build (NIGHTLY 23/03). Of course i wiped everything before. I installed the build directly from TWRP with no big problems, however, i disliked this "new"? recovery interface (this one that shows two options (RECOVERY) and (ANDROID) and this "Press search to load the system" thing. I Would like to disable it and return to the old M logo, where i had the blue led to warn me about the recovery thing. Is this possible? I mean, take this thing out?
Now the most important. As i said, i've been on the development thread since the beginning, but i didn't found any working answer to my situation. After trying both GAPPS 4.4.2, i see a black screen on first boot with the Standard GAPPS and only a "Choose your laguage" with Minimal, after chosen i get a "Launcher stopped working".I cant add the google account without the GAPPS, as some peoples suggested to another on that topic. I remember that i read something related to install the previous working build (20/01) and then upgrade to the newer, after setting the account on the older build. But theres no january 20 on quarxs ftp, what now? HELP PLS
System + data + cache wipe, use core gapps 2-26. If you encounter issues, then again install rom after full wipe, but don't install gapps immediately. Reboot, and delete unwanted system apps to free up space, and then flash gapps and wipe cache
No easy way to backport safestrap (replacement for boot menu)
Sent from my MB526 using Tapatalk
johnaddams83 said:
I've been using Quarx's CyanogenMod 11.0 (KitKat 4.4.2) since its January 20 release. However, my phone starting to become slow with the time (nothing related to the build but the extensive device use & data exchanging). Today i decided to upgrade to most recent build (NIGHTLY 23/03). Of course i wiped everything before. I installed the build directly from TWRP with no big problems, however, i disliked this "new"? recovery interface (this one that shows two options (RECOVERY) and (ANDROID) and this "Press search to load the system" thing. I Would like to disable it and return to the old M logo, where i had the blue led to warn me about the recovery thing. Is this possible? I mean, take this thing out?
Now the most important. As i said, i've been on the development thread since the beginning, but i didn't found any working answer to my situation. After trying both GAPPS 4.4.2, i see a black screen on first boot with the Standard GAPPS and only a "Choose your laguage" with Minimal, after chosen i get a "Launcher stopped working".I cant add the google account without the GAPPS, as some peoples suggested to another on that topic. I remember that i read something related to install the previous working build (20/01) and then upgrade to the newer, after setting the account on the older build. But theres no january 20 on quarxs ftp, what now? HELP PLS
Click to expand...
Click to collapse
do not use standard gapps..system partition not big enough to store standard gapps..install core gapps
I recently acquired a Nexus 6P.
TWRP is properly installed as the Recovery - twrp-3.2.3-0-angler
First thing I did with the device was flash the latest Android 8.1 Oreo version to it - angler-ota-opm7.181205.001-abb36a2f
I then installed Lineage OS 15.1, Open G Apps 8.1 (nano), and SU
From there I've done nothing but struggle with bugs and quirks. The device has been re-imaged several different times, with different variations of the above setup, and one of the main things I need to get working (Android Auto) keeps failing. Does anyone have any idea why Android Auto keeps pulling up the error "Google Play Services doesn't seem to be working right now"
All of the suggestions I've found online have failed. Screenshots have been provided for the version info and error. I've already cleared the data caches and tried to re-install and re-flash the device.
I got pissed and went back to JUST the stock OTA for testing/verification. With the stock rom there are no issues. Seems like Lineage OS 15.1 on the Nexus 6P has some bugs to work out. A fully functional stock phone is better then being frustrated.
If anyone can confirm I'm not crazy or explain what I missed while troubleshooting that would be awesome.
GTF696 said:
I got pissed and went back to JUST the stock OTA for testing/verification. With the stock rom there are no issues. Seems like Lineage OS 15.1 on the Nexus 6P has some bugs to work out. A fully functional stock phone is better then being frustrated.
If anyone can confirm I'm not crazy or explain what I missed while troubleshooting that would be awesome.
Click to expand...
Click to collapse
Try magisk as root method insted of su...
Other than that, cant think any other solution
GTF696 said:
I recently acquired a Nexus 6P.
TWRP is properly installed as the Recovery - twrp-3.2.3-0-angler
First thing I did with the device was flash the latest Android 8.1 Oreo version to it - angler-ota-opm7.181205.001-abb36a2f
I then installed Lineage OS 15.1, Open G Apps 8.1 (nano), and SU
From there I've done nothing but struggle with bugs and quirks. The device has been re-imaged several different times, with different variations of the above setup, and one of the main things I need to get working (Android Auto) keeps failing. Does anyone have any idea why Android Auto keeps pulling up the error "Google Play Services doesn't seem to be working right now"
All of the suggestions I've found online have failed. Screenshots have been provided for the version info and error. I've already cleared the data caches and tried to re-install and re-flash the device.
Click to expand...
Click to collapse
I got error when installed lineageos15.0 on twrp 3.2.3 , suddenly automatic restart. Can you help me dude ?
I have an SM-N900V (Note 3, Verizon variant, hltevzw).
Detailed timeline:
- I flashed it back to firmware OB6 using Odin 3.09.
- I rooted it using ArabicToolApp.
- I used this tool to unlock the bootloader
- I installed a build of LineageOS 14.1 for hlte
- It didn't recognize the SIM so I did a dirty flash of this build of LineageOS 15.1 for hltetmo on top (hltetmo actually has different hardware than hlte, and the correct one for SM-N900V)
- Messed around with the APNs until it recognized and connected to Verizon's network. I DO have functioning SMS and LTE data, but I have not tested phone calls yet
- Messed around some with SuperSU in system- and systemless-mode. Bricked my device more times than I could count, then unbricked over and over using SuperSU's impeccable installer. Messed around with this quite a bit
- Also messed around with Xposed some. The OS is too unstable to run Xposed Installer correctly, so I uninstalled it
- Removed SuperSU, installed Magisk. Phone now passes SafetyNet
So, my phone now runs 8.1 and a Lineage build from 9 days ago. Cool. But, if I was satisfied I wouldn't be making this post. There are multiple instances of the same kind of "app freeze" - App screen freezes, sometimes it'll go completely black. Interactivity doesn't work, obviously, the app is completely frozen. Hold Back to kill doesn't work (Application Killed toast shows, but nothing happens). ANR (when it comes up) Close doesn't work. Home button works and brings me away from the app, but it's still there. Swipe away in Overview doesn't actually kill the app. Even in App Info, Force Stop doesn't work. The app is forever frozen. Tapping the icon from the launcher no longer does anything, it doesn't even bring up the app. The app is permanently crashed and inaccessible until a reboot.
Issues:
- Sometimes when booting the phone will not recognize the SIM until a reboot. As in, "No SIM" message and everything
- Sometimes it will get stuck at boot, I have foxy-boot installed, so I can see the logs. I don't remember what it was all about, if it comes up again I'll update the post
- Google Chrome sometimes crashes when trying to download a file. I've gotten my phone to self-host before, but this issue always seems to come back, and when it does Google Chrome ALWAYS crashes when trying to download a file. App Freeze
- Netflix installs and logs in but freezes at the "can't connect to service (-9)" message. App Freeze
- Certain apps like NativeScript Playground get stuck at the splash screen. App Freeze
- Xposed Installer did this when opening the Settings, whether Xposed was installed or not. App Freeze
- F-Droid also sometimes crashes, although it's somewhat arbitrary, I can't reproduce it reliably. App Freeze
I have tried reflashing the ROM, flashing Xposed uninstaller, reinstalling Magisk, none of it seems to work. I have TWRP 3.3.0 so I can do pretty much anything that doesn't involve the SD card (the SD card is probably broken in hardware, it's so read-only that Android and TWRP both can't write to it at all, but they can both read the same half-broken filesystem).
I fear that this OS is just too unstable for the phone and there's nothing I can do. I sincerely hope this is not the case.
Try other ROMs or perform a clean installation.
Make sure you are on PL1 bootloader/modem.
Currently using Resurrection Remix v5.8.5 Nougat because it was the last Android version for this device with working Bluetooth calls but if you don't use that feature you could use their Pie version as well.
RR ROMs are solid and work extremely well.
Do a clean installation via TWRP if you go this route.
terminator911 said:
Try other ROMs or perform a clean installation.
Make sure you are on PL1 bootloader/modem.
Currently using Resurrection Remix v5.8.5 Nougat because it was the last Android version for this device with working Bluetooth calls but if you don't use that feature you could use their Pie version as well.
RR ROMs are solid and work extremely well.
Do a clean installation via TWRP if you go this route.
Click to expand...
Click to collapse
I did a clean installation of RR 6.0.0 (Android 8.1) and it works a lot better than LineageOS did, with even more configuration options. I really really hate Pie and its gesture-based gimmicks (Screw you Google for copying more of Apple's bad design decisions), so I assumed Oreo would be more stable, but the ROM I installed still has crashing apps. Google Chrome still won't download most things (I've gotten it to download before), trying to change the accent color crashes the 'LineageOS Settings' app, and F-Droid is seriously messed up, but most other things are stable, including the Verizon network which required no pesky APN setup.
I'm on the OB6 bootloader/modem, is that a problem? I doubt that would be an issue, but I can always back up and reflash via Odin. The cool thing is that I installed a patch to TWRP which backs up /data/media along with everything else, after installing the custom ROM. So, really, I can do anything and be perfectly fine. There's, AFAIK, no way to ruin the phone unless something exploits the eMMC brick bug.
If there's another ROM you'd recommend me install, I'd be happy to try it out. I would really like to have a stable OS on here, where Chrome will work and download files. I'd also love Camera2 API since the phone has the chip for it (Snapdragon 800), but none of the ROMs I have support it and there's been no discussion online other than some years-old threads with no answers. I know there have been some articles online listing Note 3 as a phone that'd support Camera2 API with a software update. Would updating the bootloader/modem do anything on that front?
I would upgrade to PL1 bootloader/modem for your device. This is what I have and have had 0 issues. I'd recommend you trying the Samsung Internet browser over Google Chrome; it's much better in my opinion.
You can find the modem here:
https://androidfilehost.com/?w=files&flid=160694
As far as ROMs are concerned you can either try the Nougat version of RR which is what I am currently using as my daily driver with no issues at all including Bluetooth calls:
[ROM][HLTE\TMO\CHN][OFFICIAL]*** Resurrection Remix N 5.8.5 ***[13.03.2018]
https://forum.xda-developers.com/ga...-resurrection-remix-n-v5-8-3-vanilla-t3615227
See here to check whether or not your phone has the Camera2 API capabilities; if not use OpenCamera.
https://www.androidexplained.com/camera2-api-support/
terminator911 said:
I would upgrade to PL1 bootloader/modem for your device. This is what I have and have had 0 issues. I'd recommend you trying the Samsung Internet browser over Google Chrome; it's much better in my opinion.
You can find the modem here:
https://androidfilehost.com/?w=files&flid=160694
As far as ROMs are concerned you can either try the Nougat version of RR which is what I am currently using as my daily driver with no issues at all including Bluetooth calls:
[ROM][HLTE\TMO\CHN][OFFICIAL]*** Resurrection Remix N 5.8.5 ***[13.03.2018]
https://forum.xda-developers.com/ga...-resurrection-remix-n-v5-8-3-vanilla-t3615227
See here to check whether or not your phone has the Camera2 API capabilities; if not use OpenCamera.
https://www.androidexplained.com/camera2-api-support/
Click to expand...
Click to collapse
Excuse me but custom ROMs don't have "the Samsung Internet browser". Additionally the modem shouldn't cause app crashes (if it does, correct me please).
I might try the Nougat ROM. Bluetooth calls don't matter to me, but stability does. I just kinda really like Oreo and all its customization options but it may be too new for this old phone from 2013. It still works as a phone though, Messages and phone calls work fine, so I may just deal with it.
I use Open Camera, and I've tried multiple Camera2 API enablers. The phone has a Qualcomm Snapdragon 800 and the necessary links (in hardware, between the camera/other things) to support Camera2, but nobody seems to have tried it. Probably because the Verizon Note 3 is really locked down, and can only be rooted on a special version of the samsung ROM, and can only be bootloader-unlocked via the eMMC brick bug... There are Magisk modules for Camera2 on Exynos-based devices, but none for the Verizon Note 3 AFAIK.
I just found out that RR 7 officially supports `hltetmo`, but RR 6 doesn't. That's kinda sad, I hate Pie, but I might try it...
I've had the SEPL stuff before, that's the one that can't be rooted. I suppose I didn't consider upgrading again after I unlocked my bootloader. I'll try SEPL1 firmware again, but with a custom ROM...
You can install the Samsung browser from the Play Store. Again, highly recommended.
As far as SEPL1 just update the modem to it; that shouldn't cause any issues but it will ensure your SIM is recognized and data works with the latest ROMs. That is one requirement you will see listed on all of these ROMs.
Not sure which one you are trying to install but here are all the Resurrection Remix versions:
Nougat:
https://forum.xda-developers.com/ga...-resurrection-remix-n-v5-8-3-vanilla-t3615227
Oreo:
https://forum.xda-developers.com/galaxy-note-3/development/rom-resurrection-remix-n-6-0-0-t3748689
Pie:
https://forum.xda-developers.com/galaxy-note-3/development/rom-resurrectionremix-v7-0-0-t3894244
If you don't care about Bluetooth audio during calls then you can safely use Oreo and Pie options.
terminator911 said:
You can install the Samsung browser from the Play Store. Again, highly recommended.
As far as SEPL1 just update the modem to it; that shouldn't cause any issues but it will ensure your SIM is recognized and data works with the latest ROMs. That is one requirement you will see listed on all of these ROMs.
Not sure which one you are trying to install but here are all the Resurrection Remix versions:
Nougat:
https://forum.xda-developers.com/ga...-resurrection-remix-n-v5-8-3-vanilla-t3615227
Oreo:
https://forum.xda-developers.com/galaxy-note-3/development/rom-resurrection-remix-n-6-0-0-t3748689
Pie:
https://forum.xda-developers.com/galaxy-note-3/development/rom-resurrectionremix-v7-0-0-t3894244
If you don't care about Bluetooth audio during calls then you can safely use Oreo and Pie options.
Click to expand...
Click to collapse
Yeah but, data and calling worked fine on the LineageOS and RR roms, so there's no reason to update the modem.
Besides, I flashed SEPL1 6 times using Odin (multiple times by flashing, rebooting directly into download mode and flashing it once more) and it doesn't want to update. Still on OB6. On the latest (official Pie) RR rom, data worked on first boot but doesn't work anymore (I'm going to mess around with the data settings until it works), but I have no reason to believe that my phone needs a modem update to function.
I did, many times, make calls to various phone numbers and they all worked flawlessly. SEPL1 is therefore not needed if that's all it does.
And I do know about all the Resurrection Remix versions: One is Nougat from their archive, one is the Oreo version I had installed just yesterday before flashing Pie, and the other one is Pie which is now officially supported.
I am currently working on getting RR7 to work, it's only crashed a few times, and I don't even remember what those times were (I think it was using the Back button in Overview/Recents at the same time as the Overview button?)
When updating modem via Odin you have to pull the battery and don't let it reboot the phone for it to stick (disable that option in Odin) and flash it again and then reboot. If you look at the ROM threads for anything newer than Android v5 they all recommend updating to the latest bootloader & modem for your device which in this case is PL1. This can be to prevent crashes/no signal /no SIM, etc...
Are you dirty flashing these ROMs? I have never experienced any crashes with any of the RRs on my phone but I always do a clean install and make sure to also delete the "Android" folder on my SD Card via TWRP after doing the "Advanced" wipe and deleting everything listed there except for the External SD Card.
terminator911 said:
When updating modem via Odin you have to pull the battery and don't let it reboot the phone for it to stick (disable that option in Odin) and flash it again and then reboot. If you look at the ROM threads for anything newer than Android v5 they all recommend updating to the latest bootloader & modem for your device which in this case is PL1. This can be to prevent crashes/no signal /no SIM, etc...
Are you dirty flashing these ROMs? I have never experienced any crashes with any of the RRs on my phone but I always do a clean install and make sure to also delete the "Android" folder on my SD Card via TWRP after doing the "Advanced" wipe and deleting everything listed there except for the External SD Card.
Click to expand...
Click to collapse
"pull the battery and don't let it reboot the phone for it to stick (disable that option in Odin) and flash it again and then reboot"
So...
- Reboot phone into Download mode
- Pull battery while in Download mode
- Flash thingy
- Reboot back into Download mode
- Flash thingy again
? That will be very difficult to do with my dodgy charging cable that doesn't like being repositioned...
I do that without pulling the battery, but I could try it with.
I'm downloading the full SEPL stock image to flash. Once that's done, I'll flash it, reflash TWRP, restore my backup, and see if the baseband has updated.
And no, never dirty flashed the ROM. Always completely wiped data, system, cache and everything. I always backup first. I currently have 3 backups: Lineage OS (before installing RR), RR6 (Oreo), and RR7 (right now before that stock image I'm going to flash).
My external SD card is nonfunctional and read-only with some trash files from the previous phone.
I flashed the stock SEPL ROM. Baseband still didn't change. Restored from backup, SIM now works. Network is detected, SMS and data both work reliably on all reboots.
I will mention that I did brick my phone by using Odin to erase the eMMC, but I fixed that from TWRP, and now everything works flawlessly. There are still some app crashes, but most things are very stable. Camera2 API still nonexistent, which is sad because I got used to it on my old phone, but I shouldn't hope for it.
Hi All,
I am the owner of a stock OnePlus 6T, which was recently running the latest version of Android 10 (v10.3.x) and also not rooted.
I was experiencing a jittery graphics issue with one of my favourite games, which was Mad Skills BMX 2. I contacted Turborilla Support in which they isolated the issue to the fact that Mad Skills BMX 2, had an issue with running on Android 10 and they suggested that I roll back to Android 9, which I did.
The rollback to Android 9 did not fix the jittery issue I was experiencing so I attempted to upgrade back to the latest "Official" version of Android 10 but no matter, how I try installing the Android update ZIP file whether it be version 10 or 9, I get to 99% of the installation then the process ends with an error that states "System Update Installation Failed"
I rolled back to Android 9 using the below installation file and I later found that this is beta version of OxygenOS ie OxygenOS Version.... OP6T_O2_Beta_17
Fulldowngrade_wipe_18801_181024_2027_user_MP2_release.zip
I have tried so many different fixes, ranging from OTA updates to downloading various ZIP installs and applying them using the "Local Upgrade" feature but no matter which method I try and keep on experiencing the "System Update Installation Failed" error.
I obviously installed a roll back ROM that has some how stuffed up my phone preventing, now preventing me to upgrade back up to Android 10.
Please help...
Thanks guys
why failed ?
Anyone?
two5om said:
Anyone?
Click to expand...
Click to collapse
Have you tried update to 10.3.2 using MSM Tool?
Oxygen Updater
two5om said:
Hi All,
I am the owner of a stock OnePlus 6T, which was recently running the latest version of Android 10 (v10.3.x) and also not rooted.
I was experiencing a jittery graphics issue with one of my favourite games, which was Mad Skills BMX 2. I contacted Turborilla Support in which they isolated the issue to the fact that Mad Skills BMX 2, had an issue with running on Android 10 and they suggested that I roll back to Android 9, which I did.
The rollback to Android 9 did not fix the jittery issue I was experiencing so I attempted to upgrade back to the latest "Official" version of Android 10 but no matter, how I try installing the Android update ZIP file whether it be version 10 or 9, I get to 99% of the installation then the process ends with an error that states "System Update Installation Failed"
I rolled back to Android 9 using the below installation file and I later found that this is beta version of OxygenOS ie OxygenOS Version.... OP6T_O2_Beta_17
Fulldowngrade_wipe_18801_181024_2027_user_MP2_release.zip
I have tried so many different fixes, ranging from OTA updates to downloading various ZIP installs and applying them using the "Local Upgrade" feature but no matter which method I try and keep on experiencing the "System Update Installation Failed" error.
I obviously installed a roll back ROM that has some how stuffed up my phone preventing, now preventing me to upgrade back up to Android 10.
Please help...
Thanks guys
Click to expand...
Click to collapse
TLDR
Use Oxygen Updater App to download the update then follow the Local Upgrade Method
Oxygen Updater: https://play.google.com/store/apps/details?id=com.arjanvlek.oxygenupdater&hl=en
What happened in my case:
I unlocked Bootloader. regretted
Relocked it:
Using MSM Tool Restore Method https://forum.xda-developers.com/oneplus-6t/how-to/how-to-update-return-to-stock-oneplus-6-t3870795
I removed the rev_OverSeas~*** file from MSM Tool~.rar EXPORT don't know if that makes a difference or not.
***"rev_OverSeas_190403_2100_release_disable_OTA-BLOCK_Signed_fp1904032100_cve2019-03-01_ufs_9.0.13"
ended up rolling back to 9.
Installed Oxygen Updater: https://play.google.com/store/apps/details?id=com.arjanvlek.oxygenupdater&hl=en
It downloaded: OnePlus6TOxygen_34_OTA_024_all_1909112343_9fd6e0057b8747dc.zip
installed using the Local upgrade Method
rebooted
It was still on 9
used Oxygen Updater to check for updates again.
found: OnePlus6TOxygen_34_OTA_024_all_2005052113_26a111bd1040285.zip
Installed the updated.
DONE.
:silly:
two5om said:
Hi All,
I am the owner of a stock OnePlus 6T, which was recently running the latest version of Android 10 (v10.3.x) and also not rooted.
I was experiencing a jittery graphics issue with one of my favourite games, which was Mad Skills BMX 2. I contacted Turborilla Support in which they isolated the issue to the fact that Mad Skills BMX 2, had an issue with running on Android 10 and they suggested that I roll back to Android 9, which I did.
The rollback to Android 9 did not fix the jittery issue I was experiencing so I attempted to upgrade back to the latest "Official" version of Android 10 but no matter, how I try installing the Android update ZIP file whether it be version 10 or 9, I get to 99% of the installation then the process ends with an error that states "System Update Installation Failed"
I rolled back to Android 9 using the below installation file and I later found that this is beta version of OxygenOS ie OxygenOS Version.... OP6T_O2_Beta_17
Fulldowngrade_wipe_18801_181024_2027_user_MP2_release.zip
I have tried so many different fixes, ranging from OTA updates to downloading various ZIP installs and applying them using the "Local Upgrade" feature but no matter which method I try and keep on experiencing the "System Update Installation Failed" error.
I obviously installed a roll back ROM that has some how stuffed up my phone preventing, now preventing me to upgrade back up to Android 10.
Please help...
Thanks guys
Click to expand...
Click to collapse
Hey there,
I think the fastboot method https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516 is still the cleanest method to get things back up and running, saved my device quite some times now.
Have a good one
Hi everyone, I discovered something that might be already known to everyone else out there but me... but probably is not known to many.
There is something everyone should know when updating.... DO NOT rename the update file, or else Oxygen OS will refuse to install it.
In my case, I was using the full OnePlus6TOxygen_34.J.55_OTA_055_all_2107132253_b2cbbb97b4eee.zip file as a local upgrade file from within the "system Updates", which is about 2 gigs in size, to upgrade to OxygenOS 10.3.12. I added the words "OxygenOS 10.3.12" to the end of the file but before the ".zip" extension.... and it would not work and I got the "System Update Installation Failed" message. I thought the file was corrupt. I re-downloaded. I checked file sizes in Windows Properties. I cleared caches. I chanted. I prayed... I thought maybe I need to change religions. Then, when just out of curiosity, I changed the file name back to its original... bingo! I did the filename change from within Android. I wonder how many other people learned this the hard way? This should be in the top 100 things that all android tinker-ers should know. "What You Should Know" for Android/OnePlus. Like an FAQ but the reverse... because an faq assumes you know what to ask, whereas a WYSK tells you what you will eventually find out the hard way . So there is my little contribution, and I hope someone else who was in a similar position finds this and it makes their day All the best You All! - Chad May
two5om said:
Hi All,
I am the owner of a stock OnePlus 6T, which was recently running the latest version of Android 10 (v10.3.x) and also not rooted.
I was experiencing a jittery graphics issue with one of my favourite games, which was Mad Skills BMX 2. I contacted Turborilla Support in which they isolated the issue to the fact that Mad Skills BMX 2, had an issue with running on Android 10 and they suggested that I roll back to Android 9, which I did.
The rollback to Android 9 did not fix the jittery issue I was experiencing so I attempted to upgrade back to the latest "Official" version of Android 10 but no matter, how I try installing the Android update ZIP file whether it be version 10 or 9, I get to 99% of the installation then the process ends with an error that states "System Update Installation Failed"
I rolled back to Android 9 using the below installation file and I later found that this is beta version of OxygenOS ie OxygenOS Version.... OP6T_O2_Beta_17
Fulldowngrade_wipe_18801_181024_2027_user_MP2_release.zip
I have tried so many different fixes, ranging from OTA updates to downloading various ZIP installs and applying them using the "Local Upgrade" feature but no matter which method I try and keep on experiencing the "System Update Installation Failed" error.
I obviously installed a roll back ROM that has some how stuffed up my phone preventing, now preventing me to upgrade back up to Android 10.
Please help...
Thanks guys
Click to expand...
Click to collapse
This is why I use twrp
I am running LineageOS 17.1 (ver. 0.2.11.202414 ) with microg on my oneplus 6T.
I am totally happy with it except that sometimes my nfc is not working on my yubikey but with this i can life.
My main problem i have with updates to newer builds. They are released every week and under settings->system->advanced->updater I can see the builds that i could download and install. Also the OS is reminding me that i should update to newer versions.
I did it once and I softbricked my phone and i dont understand why...
On the LOS guide the steps mentioned are these:
Open Settings, navigate to “System”, then “Updater”.
Click the Refresh Icon in the top right corner.
Choose which update you’d like and press “Download”.
When the download completes, click “Install”. Once the update process has finished, the device will display a “Reboot” button, you may need to go into the Updater menu in Settings, “System” to see it. This will reboot you into the updated system
This is for shore not working with my version and microg variant.
How should i proper update my OS to a newer build version?
Does nobody have a hint for me?
marsxxl said:
Does nobody have a hint for me?
Click to expand...
Click to collapse
Maybe try asking in the Lineage thread.
marsxxl said:
I am running LineageOS 17.1 (ver. 0.2.11.202414 ) with microg on my oneplus 6T.
Click to expand...
Click to collapse
The updater had issues originally. Although since you are using microg, you might have issues anyways. Now it would probably work if you were using a stock version of Lineage. Personally I still just use TWRP to update.
I have a guide here: Installing Lineage, it covers updating.
The only time I ran MicroG for any length of time was Omni, but it was still updated the same way.
You should be able to just flash the new build in recovery, flash the TWRP installer, reboot to recovery, flash Magisk if you use it, reboot to system. Since at this point, most modules will cause problems if flashed in TWRP.
I don't know how old your phone's firmware is, but there was a point in there LOS started checking for the updated firmware, so you maybe forced to update too. It should check before it flashes anyways. So just know if it errors out, you'll be updating everything. Be prepared to backup and clean install if you have to.
Thank you a lot @OhioYJ !
I was able to do the Update
If someone is interested in the NFC problem that I have, i will post it here:
https://forum.xda-developers.com/t/nfc-not-working.3945659/#post-84280433