When I go to about phone in my settings then update, I get a message that says IN2025_11.C.11 is ready to be downloaded and installed. When I click download and install it fills up the bar about 10% then crashes and says it was unable to be installed. Anyone have any advice or the update I can download to take care of it locally?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I installed it on mine today. So far so good, but I haven't been using it a bunch.
mkennedy455 said:
I installed it on mine today. So far so good, but I haven't been using it a bunch.
Click to expand...
Click to collapse
Did yours update normally? Did you have to local upgrade?
I just did the ota through system update in settings.. I read on here that there was an update so I manually checked and it showed up so installed it and it worked I was on open beta 1 Android 12 not rooted used incremental update. I used oxygen updater to install the beta I was on before. I'm a little confused because I thought I had to factory reset to go back to stable builds. Is this actually a stable build now or is it still a beta?
mkennedy455 said:
I just did the ota through system update in settings.. I read on here that there was an update so I manually checked and it showed up so installed it and it worked I was on open beta 1 Android 12 not rooted used incremental update. I used oxygen updater to install the beta I was on before. I'm a little confused because I thought I had to factory reset to go back to stable builds. Is this actually a stable build now or is it still a beta? View attachment 5565839
Click to expand...
Click to collapse
As far as I know its a stable but its only being rolled out to the beta users at the moment. I could be wrong
mkennedy455 said:
I just did the ota through system update in settings.. I read on here that there was an update so I manually checked and it showed up so installed it and it worked I was on open beta 1 Android 12 not rooted used incremental update. I used oxygen updater to install the beta I was on before. I'm a little confused because I thought I had to factory reset to go back to stable builds. Is this actually a stable build now or is it still a beta? View attachment 5565839
Click to expand...
Click to collapse
Idk why mine wont let me update through updates even tho it shows it there
it simply because you're rooted.. it's already known from a long time.
there're 2 way if you wanna update from OTA:
1. simple uninstall magisk, and restore image. then do update. then back install magisk again
2. localupdate again C.10 and because you're now lose root, then you should be able to update fine
dewa5227 said:
it simply because you're rooted.. it's already known from a long time.
there're 2 way if you wanna update from OTA:
1. simple uninstall magisk, and restore image. then do update. then back install magisk again
2. localupdate again C.10 and because you're now lose root, then you should be able to update fine
Click to expand...
Click to collapse
Oh alright. How would I install magisk again since I wont be able to patch ota?
dewa5227 said:
it simply because you're rooted.. it's already known from a long time.
there're 2 way if you wanna update from OTA:
1. simple uninstall magisk, and restore image. then do update. then back install magisk again
2. localupdate again C.10 and because you're now lose root, then you should be able to update fine
Click to expand...
Click to collapse
Did what you said, it updated. Rebooted. Then after a reboot again my phone only boots into recovery now....
H411UCIN093NIC said:
Did what you said, it updated. Rebooted. Then after a reboot again my phone only boots into recovery now....
Click to expand...
Click to collapse
what step that you actually do ?
If you like to do an OTA;
Go to Magisk, uninstall Magisk - restore Image
Download and Install the OTA but DONT reboot
Go to Magisk, install magisk to inactive slot after ota
Reboot
xtcislove said:
If you like to do an OTA;
Go to Magisk, uninstall Magisk - restore Image
Download and Install the OTA but DONT reboot
Go to Magisk, install magisk to inactive slot after ota
Reboot
Click to expand...
Click to collapse
Thank you
H411UCIN093NIC said:
Did what you said, it updated. Rebooted. Then after a reboot again my phone only boots into recovery now....
Click to expand...
Click to collapse
Try to change slot via fastboot
xtcislove said:
Try to change slot via fastboot
Click to expand...
Click to collapse
Yea I tried that. I had to use msm tool loose all data then start from scratch apply all updates then I was able to do what you said and it worked. I'm on the latest A12 with root but unfortunately I lost all data in the meantime.
Installing magisk in an inactive slot will result in a softbrick.
Maruli said:
Installing magisk in an inactive slot will result in a softbrick.
Click to expand...
Click to collapse
So lets say I am on the latest Android 11 stable build and I want to flash the C11 stable Android 12 build (full zip, not incremental) and keep root and data. Is there a way to do that?
Previously as others have said, we restore images in Magisk. Install the OTA, then direct install Magisk, then to inactive slot, reboot, and all is well. Does this no longer work? Can someone please give a full explanation of their understanding?
xgerryx said:
So lets say I am on the latest Android 11 stable build and I want to flash the C11 stable Android 12 build (full zip, not incremental) and keep root and data. Is there a way to do that?
Previously as others have said, we restore images in Magisk. Install the OTA, then direct install Magisk, then to inactive slot, reboot, and all is well. Does this no longer work? Can someone please give a full explanation of their understanding?
Click to expand...
Click to collapse
Do you have the IN2021 version? Because NA/global doesn't have a full ROM yet. I can only confirm what the guy above me has experienced - installing magisk (v24.3) into the updated slot will result in a softbrick. Without that step it's working fine (I managed to switch slots in fastboot and redo the update from previous slot again).
It seems like the boot.img from the IN2021 C11 ROM does work with the IN2025 software, since I couldn't extract the incremental OTA and patch the boot.img. That actually saved my phone and I almost used MSM tool.
Maybe it's different if you update from A11 to A12 - I updated from OB1 C10 to C11 and magisk messes something up in the process.
Maruli said:
Do you have the IN2021 version? Because NA/global doesn't have a full ROM yet. I can only confirm what the guy above me has experienced - installing magisk (v24.3) into the updated slot will result in a softbrick. Without that step it's working fine (I managed to switch slots in fastboot and redo the update from previous slot again).
It seems like the boot.img from the IN2021 C11 ROM does work with the IN2025 software, since I couldn't extract the incremental OTA and patch the boot.img. That actually saved my phone and I almost used MSM tool.
Maybe it's different if you update from A11 to A12 - I updated from OB1 C10 to C11 and magisk messes something up in the process.
Click to expand...
Click to collapse
Thanks, that helps a lot. I think I'm going to wait until the dust settles because I need my phone available for work. I can't be stuck in a bootloop for 3 hours trying to fix it.
I tried to extract the BOOT.IMG from the OTA file, trying many tools without success, although in the log of one of the extraction tools it told me that the boot had 100MB, in the output only a boot.img appeared with 0MB
Related
Here's the new update that came out today - XNPH25R. This has the assert junk removed so you can flash it in TWRP.
NOTHING has been changed in this other than the ability to flash it in TWRP.
Reboot to recovery, flash .zip. Reboot to system. Nothing fancy required. *Flash SuperSU if you want root access.
https://www.4shared.com/download/4UoLVwKIce/cm-bacon-XNPH25R_fix.zip?lgfp=3000
I'm getting binary update script error by flashing with TWRP
I flashed the stock OTA in TWRP right from my phone. Go to Developer settings adn uncheck the update CM recovery setting and OTA will flash in TWRP. I kept root. I'm not sure if the 4.4 update will kill root, but I doubt it. Thanks for providing the zip!
With the option to update CM recovery via OTAs does that mean we can take OTAs with TWRP installed?
Hey Guys Can I flash this zip file through CWM ???? Please suggest...........
Update = flashed the official cm-11.0-XNPH22R-bacon-signed file & then received the OTA & it's installed successfully even with CWM install.
iamacronym said:
With the option to update CM recovery via OTAs does that mean we can take OTAs with TWRP installed?
Click to expand...
Click to collapse
I think you have to disable that option in developer settings menu, if you want to be able to flash the OTA with TWRP.
Works for me
Updated it using TWRP but once booted it tells me there's an udpate, over and over... update in TWRP seems to work (no fails, only message is "radio image updated")
I flashed the file and when I reboot i´m still on XNPH22R and it also does prompt for the update. I flashed it on twrp, everything seemed ok
Flashed the file with both TWRP and Philz, no error but the Rom version is still 22R !
Can someone post the stock recovery img please?
ToRvaLDs said:
Flashed the file with both TWRP and Philz, no error but the Rom version is still 22R !
Can someone post the stock recovery img please?
Click to expand...
Click to collapse
Yeah I get the same issue where it shows as the flashing being successful,but reboots back to 22R.
housry23 said:
I flashed the stock OTA in TWRP right from my phone. Go to Developer settings adn uncheck the update CM recovery setting and OTA will flash in TWRP. I kept root. I'm not sure if the 4.4 update will kill root, but I doubt it. Thanks for providing the zip!
Click to expand...
Click to collapse
Which folder was the OTA located in? Is it the cache one at root level?
Sent from N5 or OPO
truckroot said:
Which folder was the OTA located in? Is it the cache one?
Sent from N5 or OPO
Click to expand...
Click to collapse
I couldn't tell you. I got a notification that an update was available, tapped install and it booted into twrp and installed the update. I had to reinstall xposed but kept root and twrp.
Sent from my OnePlus One
housry23 said:
I couldn't tell you. I got a notification that an update was available, tapped install and it booted into twrp and installed the update. I had to reinstall xposed but kept root and twrp.
Sent from my OnePlus One
Click to expand...
Click to collapse
OK thx. Wasn't sure if u had to navigate to a certain folder when twrp booted up. Stock OTAs in a custom recovery is new territory for me.
Sent from N5 or OPO
truckroot said:
OK thx. Wasn't sure if u had to navigate to a certain folder when twrp booted up. Stock OTAs in a custom recovery is new territory for me.
Sent from N5 or OPO
Click to expand...
Click to collapse
I would say it's new territory for all of us. I do have the option to update cm recovery unchecked in developer settings.
Sent from my OnePlus One
housry23 said:
I would say it's new territory for all of us. I do have the option to update cm recovery unchecked in developer settings.
Sent from my OnePlus One
Click to expand...
Click to collapse
True. I have that unchecked and also had the system update apk frozen just out of habit.
Leave it to CM to allow OTAs to be installed thru twrp/cwm. Living this phone more and more each day.
Sent from N5 or OPO
Is it supposed to be about 23.55 mb only? Everytime i flash nothing changes...
Sent from my One using XDA Free mobile app
truckroot said:
Which folder was the OTA located in? Is it the cache one at root level?
Sent from N5 or OPO
Click to expand...
Click to collapse
The downloaded OTA is located in \cache and can be flashed trough TWPR. Unfortunately I get an error of missing apks in \system due to deleting some of them (CM File Manager, PrintSpooler, ...).
I'll try to throw them back to \system and retry flashing.
Nope nope nope, doesn't work. He says blabla build.prop because of changed DPI, but it gave me an error on executing the update binary anyway.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is what happens when you try to flash the original OTA .zip in TWRP. When flashing the provided zip in OP I don't get an error but like everybody said it doesn't update to 25.
fiz:ik said:
Nope nope nope, doesn't work. He says blabla build.prop because of changed DPI, but it gave me an error on executing the update binary anyway.
Click to expand...
Click to collapse
Someone has the original build.prop? We can try to restore it and update.
ToRvaLDs said:
Someone has the original build.prop? We can try to restore it and update.
Click to expand...
Click to collapse
I've got it. Do you need? Texdroider DPI makes an backup of the original build.prop. I restored it and the issue is solved but nevertheless the update binary can't be executed.
Flashed CWM over TWRP: with CWM same problem. I restored original build.prop and it's still complaining about in the build prop.
Okay, seems that my backup of build.prop isn't the stock build.prop but an updated version with DPI of 380, damn. Can anyone upload the original one?
Can you upload the original build.prop please? Are you sure that the old file has the correct cm revision?
Inviato dal mio One utilizzando Tapatalk
When i root my S7 Edge, how to get OTA updates?
Is there any page to download it?
You can't get ota updates with root, you have to go into the dev section and basically download a rom with the current updates already installed.
crack00r said:
When i root my S7 Edge, how to get OTA updates?
Is there any page to download it?
Click to expand...
Click to collapse
1. You can't get OTA updates if you are rooted.
2. You have to flash the correct firmware via ODIN if you are rooted. One page to download the firmwares is this ONE.
crack00r said:
When i root my S7 Edge, how to get OTA updates?
Is there any page to download it?
Click to expand...
Click to collapse
never trust an OTA update it will just patch your FW and in time your device will become too slow,I always used this site to download and install the latest full updates using Odin.
http://www.sammobile.com/firmwares/database/SM-G935F/
http://www.sammobile.com/firmwares/
I installed TRWP and rooted my S7 Edge. What happens if I download the new stock rom from sammobile.com and flash it using TWRP or ODIN? Will I loose all apps/settings and will the phone still be rooted?
hagba said:
never trust an OTA update it will just patch your FW and in time your device will become too slow,I always used this site to download and install the latest full updates using Odin.
http://www.sammobile.com/firmwares/database/SM-G935F/
http://www.sammobile.com/firmwares/
Click to expand...
Click to collapse
I don't understand this. Isn't OTA full updates and flashes firmware, ROM and everything to newest versions?
Sent from my A0001 using Tapatalk
MrMooselover said:
I installed TRWP and rooted my S7 Edge. What happens if I download the new stock rom from sammobile.com and flash it using TWRP or ODIN? Will I loose all apps/settings and will the phone still be rooted?
Click to expand...
Click to collapse
If somebody would like to answer this guy, I'd be the happiest.
I'm wondering the same thing. Though I get by with Titanium Backup for now (even though I don't trust it that much anymore, it just swallowed all my backups when I moved the files through the app, I had to reinstall evything by hand, and I lost most of my SMS/MMS).
Actually you can get OTA updates when you are rooted there is option in xTouchWiz Module when you have Xposed installed that changes the device status from Custom to Official and for me it worked and then i can install the update using flashfire. But i dont know if it works you too
jark99 said:
I don't understand this. Isn't OTA full updates and flashes firmware, ROM and everything to newest versions?
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
OTA is a Over the air package.
Contains just the nessesery code to patch the current firmware.
You cannot flash a OTA, Simple.
What you can do, is what others have advised. Download the full Firmware and flash away.
There is two ways to do this. Flash everything and have the device wipe all data.
Flash the necessary files for odin with a patched csc file (This will avoid any data being wiped)
Second method:
Flashfire.
You can download the whole firmware package from Sammy (Link the guys posted above)
Then use flashfire to flash these packages straight on the device.
You will retain all Data and Settings etc. You can also replace bootloader
and then flash TWRP again after.
(If i have used flashfire since i have had the device. I have updated Dirty (Dirty is when i dont wipe and keep all Data)
I have done this around 5 times, and noticed my device starting to become slow at responding.
Today i installed the latest Firmware with a Full wipe. (Its advisable once in a while)
Iradj said:
Actually you can get OTA updates when you are rooted there is option in xTouchWiz Module when you have Xposed installed that changes the device status from Custom to Official and for me it worked and then i can install the update using flashfire. But i dont know if it works you too
Click to expand...
Click to collapse
Can you explain how you did it i have all installed flashfire, xtouchwiz, ota how do i flash it where is the file?
tonyafc said:
Can you explain how you did it i have all installed flashfire, xtouchwiz, ota how do i flash it where is the file?
Click to expand...
Click to collapse
Its Simple in XTouchWiz go to Security Hacks and then tick the Box "Fake System Status" Now close XTouchWiz and go to Settings and Status, now it should be Official and Thats it. You can download your OTAs but obviously you can't install it, Open Flashfire go to Flash Zip or OTA.... Done.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Your OTAs should be saved in DATA -> FOTA
Iradj said:
Its Simple in XTouchWiz go to Security Hacks and then tick the Box "Fake System Status" Now close XTouchWiz and go to Settings and Status, now it should be Official and Thats it. You can download your OTAs but obviously you can't install it, Open Flashfire go to Flash Zip or OTA.... Done.
Your OTAs should be saved in DATA -> FOTA
Click to expand...
Click to collapse
Thanks for replying done all above couldn't locate the file in data but found it in cache but the file has corupted in brackets?
tonyafc said:
Thanks for replying done all above couldn't locate the file in data but found it in cache but the file has corupted in brackets?
Click to expand...
Click to collapse
Yeah, I tested it myself and there is now chance to flash the update.zip from the fota folder. It did what is recommended: Just flash the whole firmware with the home_csc.
GerasVille said:
Yeah, I tested it myself and there is now chance to flash the update.zip from the fota folder. It did what is recommended: Just flash the whole firmware with the home_csc.
Click to expand...
Click to collapse
I did that with the last update i got it from sammobile but it wiped my phone
tonyafc said:
I did that with the last update i got it from sammobile but it wiped my phone
Click to expand...
Click to collapse
Really? Even with the home_csc file? Did the device ask you for a pin or something or did it just a wipe after flashing?
GerasVille said:
Really? Even with the home_csc file? Did the device ask you for a pin or something or did it just a wipe after flashing?
Click to expand...
Click to collapse
No pin i downloaded file from sammobile and got 6 files using odin i put them all in labelled boxes and it wiped my phone there was another csc file
TWRP (NO ROOT) and Official Firmware with OTA updates possible (S7 EDGE 935FD)
Hey, If I am posting here irrelevant, please guide me to the best Thread where I should post it.
I recently installed Resurrection Remix rom on s7 edge. Them ram was good, however, camera wasn't working with stock rom as well as open camera and candy camera apps. It was just showing blank screen when I open any camera app. I reinstalled the stock rom via Smart Switch.
I require a few solutions:
1. How can I get my camera working with Resurrection Remix? Is there anyone who had the same problem?
2. Can I install TWRP to have custom recovery with official rom? And while having TWRP (without root), would I be able to have OTA?
3. How can I use smart switch backup via any other app or software to get it into my phone (which is installed with custom rom) because custom rom do not catch smart switch.
Thanks!
crack00r said:
When i root my S7 Edge, how to get OTA updates?
Is there any page to download it?
Click to expand...
Click to collapse
Give it a try
https://forum.xda-developers.com/ga...dates-root-t3837898/post77519099#post77519099
Alright.
I had this problem for a while and I figured out how to flash the update without the need to factory reset or change the update script of the update file.
Even if you get the user/release-keys error message. EXAMPLE:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You have to be using the latest lollipop release before updating. That means you have to be on YOG7DAS2K1 before attempting.
This worked out for me. But it might not work for you. I do not believe it can destroy your phone and switch some satellites off, but still, not responsible if it did so.
Requirments:
You have to have TWRP now or you at least have ROOT and any flashing app like flashify.
Download COS 13 update file. here https://www.androidfilehost.com/?fid=24459283995316311
Download the latest CyanogenMod Recovery https://download.cyanogenmod.org/?device=bacon
Download the cm-12.1-YOG7DAS2K1 full ROM [url]https://www.androidfilehost.com/?fid=24369303960686198[/URL]
Guide:
Make sure the update cyanogen recovery option is checked in developer options.
Flash CyanogenMod Recovery downloaded before.
Reboot into it.
Use the update function in CyanogenMod Recovery and choose cm-12.1-YOG7DAS2K1 as the update file. It might take a while.
Now reboot to your phone. When booted and running, reboot to recovery.
Now you are running COS recovery. Update with the incremental.
That is it.
I hope this works out for you.
EXTRA: How to ROOT and have TWRP as a recovery:
Requirements:
A laptop.
Download TWRP and adb drivers on the laptop and the SuperSU and TWRP on your phone
Download Oneplus One TWRP Recovery [url]https://dl.twrp.me/bacon/twrp-3.0.2-0-bacon.img.html[/URL]
Get any adb divers. This one suffice [url]http://forum.xda-developers.com/google-nexus-5/development/adb-fb-apx-driver-universal-naked-t2513339[/URL]
Download the latest SuperSu [url]https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip[/URL]
Guide:
Reboot into bootloader: you can do this in many ways. A simple google search will show you how. Easiest way is to turn the phone off and hold the volume up and power long enough for the phone to boot into bootloader.
Connect your phone to your laptop
Run the adb: I assume you are using windows of course. First put the TWRP .img file in this folder. Hold shift and right click in the folder downloaded above. A 'Open command window here' option will be there. Click it and write in the window
Code:
fastboot boot twrp-3.0.2-0-bacon.img
. A hint: you can just write twrp and hit TAB, it will complete the filename. Or you can rename the downloaded file to just twrp.img
Check your phone, you will be running TWRP temporarily. You now have the option to ROOT only by flashing the SuperSU file downloaded on your phone. If you reboot now you will lose TWRP and get back to the official COS Recovery. If you want TWRP for good flash the TWRP file downloaded on your phone before.
I hope this is easy. It actually is. just follow it step by step.
If you could provide us the guide to root and come back to twrp I would be extremely happy
bisio971 said:
If you could provide us the guide to root and come back to twrp I would be extremely happy
Click to expand...
Click to collapse
fastboot flash latest twrp and flash SuperSU BETA
THANK the post if I deserve
bisio971 said:
If you could provide us the guide to root and come back to twrp I would be extremely happy
Click to expand...
Click to collapse
if you need a guide to root, this means you are not rooted, and if you are not rooted most probably you already have stock recovery, which means you can just install the OTA update without any issues.
bisio971 said:
If you could provide us the guide to root and come back to twrp I would be extremely happy
Click to expand...
Click to collapse
Added as requested. I hope you find it easy.
y2kkingboy said:
Added as requested. I hope you find it easy.
Click to expand...
Click to collapse
Thank you, you made my life easier, but when I tried to run the twrp through fastboot I got an error and I got the solution writing "fastboot boot twrp.img" (after renaming the file).
bisio971 said:
Thank you, you made my life easier, but when I tried to run the twrp through fastboot I got an error and I got the solution writing "fastboot boot twrp.img" (after renaming the file).
Click to expand...
Click to collapse
Yeah. I mad a mistake there. Thank you and glad it helped.
If I do this what happens to my data?? I'm on cm 12. 1.1, rooted & running twrp.
---------- Post added at 12:20 AM ---------- Previous post was at 12:18 AM ----------
Link for cos13 that works with this method?
thinleytsering9 said:
If I do this what happens to my data?? I'm on cm 12. 1.1, rooted & running twrp.
---------- Post added at 12:20 AM ---------- Previous post was at 12:18 AM ----------
Link for cos13 that works with this method?
Click to expand...
Click to collapse
As I stated before you have to be on COS 12.1 YOG7DAS2K1. This method should not format your phone or remove any data as there is no factory reset step.
As for the link they are all over the place now. I used the official one. I'll link it for your convenience.
can anyone please pull the stock recovery from COS 13, not 12. I kinda screwed up while updating and now stuck in bootloop.
Update: The issue is resolved. The issue was because of SuperSu 2.46. Installing the latest TWRP and SuperSu 2.66 fixed it. Marshmallow is now rooted!
Thank you very much! After going back to stock and still not receiving the update for more than a week (well at least it felt like a week, Lol) I decided to flash a full COS 13 zip floating around. Instantly liked the new ROM but it had root/symlink issues only to be resolved when flashing a custom kernel it seems. Not what I really wanted so then I stumbled onto your thread and this technique worked 100%! I was on DAS2K1 (flashed thru a custom recovery) already and had several failed attempts flashing just the incremental outright (thru stock recovery)., but by flashing DAS2K1 thru stock recovery first as you suggest then the incremental seems to do the trick.
I did it all the steps, but my phone doesn't not start. After optimizing aplications I have bootloop at "cyanogen modready".
L.E. I think the problem was one of old aplications. After a clean install everything works.
This is the best thing Oneplus one i ever experience.COS13 give my Oneplus one a new breathe of life .This update better than crap lolipop.No Bug for me until now,only google play service need to update twice in play store,its auto reboot itself twice and wholla,super speed UX.The best thing i ever have.I apply update from CM-12-0-YNG1TAS17L Build LRX22G using this method and it works flawlessly
I don't need to factory reset or wipe cache .
I flash full stock ROM cm-12.1-YOG7DAS2K1 and apply update through CyanogenMod Recovery only and nothing else.
Now my oneplus one is rooted and TWRP install using ADB and its fly.All rooted apps is working together with Adaway.
Thanks Cyanogen team for make this 2 years old flagship killer a beast .
Only thing not satisfied is gone signal and wifi status (connectivity indicator ).I need to swipe down to see my transfer data working (what a bummer ).
Thanks so much for this magical guide (y2kkingboy) Yours truly Oneplus one diehard fan.
I was already on cm-12.1-YOG7DAS2K1, however rooted. So even if I had been offered the OTA it would have failed.
Your guide got me updated, first time with no problems.
6.0.1 is such an improvement on 5.1.1, I tried a couple of other 6.0 roms, however this has by far been the most stable and bug free.
Cheers for the tutorial!
u can also add a trick i saw online i.e to remove lines of code from assets to - in updater file
#sychrome# said:
u can also add a trick i saw online i.e to remove lines of code from assets to - in updater file
Click to expand...
Click to collapse
Can you provide more info? i've always had trouble updating when rooted.
InsaneNutter said:
Can you provide more info? i've always had trouble updating when rooted.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2522762
u can also add a trick i saw online i.e to remove lines of code from assets to - in updater file
Click to expand...
Click to collapse
Can you provide more info? i've always had trouble updating when rooted.
Click to expand...
Click to collapse
I had tried this before and it did not work for me. Kept getting an error saying "the signature file was not a complete file" and therefore it didn't flash. But it may have been editing error on my part. This method works just fine and no need to give up your data either.
Having tried many other ways, I got it done with this instruction.
Thank you!
marxu said:
Having tried many other ways, I got it done with this instruction.
Thank you!
Click to expand...
Click to collapse
Glad I helped.
First off, a HUGE thank you to @autoprime (for paving the way) and @waylo (for his assistance on getting this going after I found the KDZ)
I am currently storing these in my google drive account, so please be gentle till I have a better host location:
Below are the downloads for the LG-H83020N firmware
Folder with all the LG830 firmware I have so far:
LG830 (G5)
LG-H83020N-Flashable.COMPLETE-ARB01.zip
As always, COMPLETE is 100% stock
Flash COMPLETE zip -> wipe cache partition -> flash Magisk ZIP (or SuperSU if you insist) to root and keep TWRP
OPTIONAL: After flashing, remount /system RW -> delete recovery-from-boot.p to guarantee TWRP sticks
LG-H83020N-Flashable.Bootloader-ARB01
LG-H83020N-Flashable.Modem-ARB01.zip
LG-H83020N-Flashable.Boot.zip
H830N_00_1017.kdz (HUGE Thank you to @Azul Baseem for the upload)
For instructions, follow the same instructions as you would in any other KDZ/ZIP thread. For Example
Feel free to hit thanks.
Also feel free to hit up autoprime's All in One thread HERE
Thank you very much bedwa!
Kdz link updated!
Thank you @bedwa as always.
I fear my only true contribution here is MD5 confirmation of the files:
LG-H83020N-Flashable.COMPLETE-ARB01.zip 8a49733028bef23d775bf542eb62b726
LG-H83020N-Flashable.Boot.zip ddea9d814f66266de34a154f0c7f6b41
H830N_00_1017.kdz 732b717af8d77501342be445002c4fae
Edit: Also, since someone will definitely miss it in the title, this is confirmed to still be on Anti-Rollback 1. You're free to flash back and forth between 20A if you need to Dirtycow your phone again.
Keeping me honest, I swear I'll remember them next time.
Thanks for the upload. I was able to update just fine thanks to this.
BTW... It still has H83020m mentioned in the body of the OP instead of H83020n.
shinji257 said:
Thanks for the upload. I was able to update just fine thanks to this.
BTW... It still has H83020m mentioned in the body of the OP instead of H83020n.
Click to expand...
Click to collapse
Fixed. That's what I get for using the copypasta method. Missed the one. :silly:
help me
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i had this issues when i try to flash it i already use uppercut
solved
running 20N , so far so good, just notice a small problem with GPS , it is a bit spotty today. @bedwa : Can you make a slim down version ? like removing LG/TMO/Google stuffs ? and reduce /system partition size ?
abced123 said:
running 20N , so far so good, just notice a small problem with GPS , it is a bit spotty today. @bedwa : Can you make a slim down version ? like removing LG/TMO/Google stuffs ? and reduce /system partition size ?
Click to expand...
Click to collapse
That would be trickier. All of these are the partition images. To make a slim zip like that I'll have to either unpack and build or unpack and attempt to repack. I might, but not likely at this time.
Thank you so much for making this. So happy to be rooted and on the latest build thanks to your hard work. =)
fc3211 said:
Thank you so much for making this. So happy to be rooted and on the latest build thanks to your hard work. =)
Click to expand...
Click to collapse
Quite welcome... It's more time consuming than hard work, but the appreciation and thanks is greatly appreciated as well.
@bedwa
I am running on rooted H83020a with TWRP and SuperSU installed. In order to upgrade to 20N by keeping all my current settings and data along with root and TWRP, what are the steps should I follow?
1. Take a complete backup using LG Backup
2. Boot into TWRP
3. Flash Complete Zip (H83020N) from TWRP
4. Flash SuperSU Zip
5. Reboot System
6. Restore the complete backup from LG Backup
Does this work okay? Or, do I need to do anything else, like Wipe Data/Partition etc.? Sorry for the noob question.
Hello,
If I flash boot and bootloader, will it lock my bootloader and brick the phone if I am on LineageOS?
nizarp said:
@bedwa
I am running on rooted H83020a with TWRP and SuperSU installed. In order to upgrade to 20N by keeping all my current settings and data along with root and TWRP, what are the steps should I follow?
1. Take a complete backup using LG Backup
2. Boot into TWRP
3. Flash Complete Zip (H83020N) from TWRP
4. Flash SuperSU Zip
5. Reboot System
6. Restore the complete backup from LG Backup
Does this work okay? Or, do I need to do anything else, like Wipe Data/Partition etc.? Sorry for the noob question.
Click to expand...
Click to collapse
Backup is always good, shouldn't have to restore it as it's updating from a previous version and doesn't wipe data when upgrading. But that's the correct process with or without #6.
azizo07 said:
Hello,
If I flash boot and bootloader, will it lock my bootloader and brick the phone if I am on LineageOS?
Click to expand...
Click to collapse
Shouldn't, but it would always be a good idea to backup beforehand. I would however only flash the bootloader, as the boot is the kernel and will be different than what LineageOS uses though.
I just boot into TWRP and flashed the complete zip and then flashed the latest SuperSU Zip. I pressed Reboot System after that, but, I am now stuck in a boot loop. Phone shows LG logo and reboots again and again.
I tried the Power button + Vol Down method, but, it doesn't work too. It gets to Factory reset screen, and after Yes and Yes, it goes to back to boot loop again. I am able to get into Download Mode and Fastboot Mode. Can I do something from here?
Can someone help please? Anyway to get into TWRP or recovery?
Sounds like you will need to LGUP or Uppercut your phone back to stock 20A. Then dirtycow back TWRP. Then try flashing the new ZIP again. Skip Supersu this time and try Magisk instead.
Thanks. I flashed back to 20A using LGUP and KDZ file. Need to dirtycow back TWRP now. I'm still wondering what went wrong in my process.
1. Take a complete backup using LG Backup
2. Boot into TWRP
3. Flash Complete Zip (H83020N) from TWRP
4. Flash SuperSU Zip
5. Reboot System
Click to expand...
Click to collapse
Do I need to reboot to TWRP once after flashing instead of Reboot System directly after flash? Any idea?
No, rebooting into TWRP wouldn't do anything. There's a script you might need to get into and delete prior to rebooting. But that only ensures that TWRP stays.
"After flashing, remount /system RW -> delete recovery-from-boot.p to guarantee TWRP sticks"
That having been said, I've done this before and STILL not had TWRP stay. Some recommend wiping /cache as well.
OR, again, use Magisk instead and don't use SuperSU.
Even if TWRP didn't stick, you should have been booting into system fine. You wouldn't be rooted, TWRP would be gone, but system shouldn't have been messed up. So something got borked, I'd have to guess, because of SuperSU.
New security patch update alert
Hello Everyone
HAVE A PROBLEM WITH MY 8PRO...
now i was on oxygen 11.0.4.4 for a while
i got an OTA update for 11.0.10.10 about 550MB
after downloading i found that installation failed
i tried to download it full via oxygen updater 2.9GB
after 44% in installation give me the same msg (failed)
i tried many ways to install it but all not working
and i didn't found any msm tool newer than 11.0.4.4
tried download 11.0.5.5 full and install but also failed
Note: I CANT UNLOCK BOOTLOADER CUZ I NEED THE PERSONAL DATA AND I CANT MAKE FULL BACKUP THESE DAYS
can anyone help ?!
Whats the fail message?
xtcislove said:
Whats the fail message?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How much space do you have left on your device?
Please note if you use MSM Tool you loose your data too
xtcislove said:
How much space do you have left on your device?
Please note if you use MSM Tool you loose your data too
Click to expand...
Click to collapse
100 GB FREE
MSM WILL LOSE I KNOW
FOR NOW I WANT TO UPDATE MANUALLY
Now i tried to install 11.0.9.9
But also failed
You need stock rom (not root) to install patch update.
dangtoi1993 said:
You need stock rom (not root) to install patch update.
Click to expand...
Click to collapse
I need any way to force update to 11.0.10.10
Eslam.hanafy said:
I need any way to force update to 11.0.10.10
Click to expand...
Click to collapse
download full OTA file ( size about 3GB) put in phone and manual update.
But the 11.0.10.10 dont have Zip available for download yet.
dangtoi1993 said:
download full OTA file ( size about 3GB) put in phone and manual update.
But the 11.0.10.10 dont have Zip available for download yet.
Click to expand...
Click to collapse
I found it yesterday 2.9GB
And i tried to update it manually via local upgrade
But it failed in 99% and tried it again failed at 44%
I'm searching for msm tool for 11.0.10.10 but no results
Tried to found fastboot installation via cmd but also no results
Eslam.hanafy said:
View attachment 5536013
Click to expand...
Click to collapse
Eslam.hanafy said:
Now i tried to install 11.0.9.9
But also failedView attachment 5536941
Click to expand...
Click to collapse
I know this is old, but I am having the same issue with the OTA update failing at 18%
I have an OP8 Pro and it is on Android 12 stock from with rooted boot.img. My device has down all the Android 11 updates and I use Oxygen Updated and use Magisk to patch the boot.img before rebooting. Has always worked.
But I cannot update from C.21 to the C.33 it fails in the process. Did you all come up with a fix or found a solution?
parcou said:
I know this is old, but I am having the same issue with the OTA update failing at 18%
I have an OP8 Pro and it is on Android 12 stock from with rooted boot.img. My device has down all the Android 11 updates and I use Oxygen Updated and use Magisk to patch the boot.img before rebooting. Has always worked.
But I cannot update from C.21 to the C.33 it fails in the process. Did you all come up with a fix or found a solution?
Click to expand...
Click to collapse
Are you using the LocalUpdate.apk or the build in updater under "About the phone"?
xtcislove said:
Are you using the LocalUpdate.apk or the build in updater under "About the phone"?
Click to expand...
Click to collapse
Yes. Once I download the OTA, I go to local update to install but it fails to complete.
parcou said:
Yes. Once I download the OTA, I go to local update to install but it fails to complete.
Click to expand...
Click to collapse
Again my question is: Do you go to the About Phone screen or do you use the manually installed local update?
Did you try the full package instead of ota?
xtcislove said:
Again my question is: Do you go to the About Phone screen or do you use the manually installed local update?
Did you try the full package instead of ota?
Click to expand...
Click to collapse
My apology
I would have to say no...
I am aware if I go to the "About device" and click on the banner above, it takes me to the update. And it shows C.33, but in the past, I never downloaded it that way I manually downloaded with Oxygen Updated.
But I do come back to the System Update "about" app to click the gear icon to manually install so I can keep root before rebooting.
Also I have for the hell of it tried the "About device" and did the download and install, knowing it will reboot and remove the root....But that also fails, and in the process
parcou said:
My apology
I would have to say no...
I am aware if I go to the "About device" and click on the banner above, it takes me to the update. And it shows C.33, but in the past, I never downloaded it that way I manually downloaded with Oxygen Updated.
But I do come back to the System Update "about" app to click the gear icon to manually install so I can keep root before rebooting.
Also I have for the hell of it tried the "About device" and did the download and install, knowing it will reboot and remove the root....But that also fails, and in the process
Click to expand...
Click to collapse
Did you try to update via full package or only ota?
Try to follow this guide too:
[Guide] OxygenOS 12 C.21 update for OnePlus 8 Pro EU
OxygenOS 12 C.21 update for OnePlus 8 Pro EU (How to make this update.) 1.) Download C.21 EU (3.99 GB) with Oxygen Updater 2.) Edit it with TotalCommander on your phone or 7zip on your computer. Inside the zip file: open "payload...
forum.xda-developers.com
Its mainly about this part:
Inside the zip file: open "payload properties.text"
and change one line from:
oplus_update_engine_verify_disable=0
to:
oplus_update_engine_verify_disable=1
And save it.
xtcislove said:
Did you try to update via full package or only ota?
Try to follow this guide too:
[Guide] OxygenOS 12 C.21 update for OnePlus 8 Pro EU
OxygenOS 12 C.21 update for OnePlus 8 Pro EU (How to make this update.) 1.) Download C.21 EU (3.99 GB) with Oxygen Updater 2.) Edit it with TotalCommander on your phone or 7zip on your computer. Inside the zip file: open "payload...
forum.xda-developers.com
Its mainly about this part:
Inside the zip file: open "payload properties.text"
and change one line from:
oplus_update_engine_verify_disable=0
to:
oplus_update_engine_verify_disable=1
And save it.
Click to expand...
Click to collapse
Thx for the link, my friend....
I will get into this or look at it tonight when I get off work.
I did NOT try the full update I could not download it. I have a global OP8 Pro, and all I can download in Oxygen Updater is only the C.33 incremental. If I change the app option, the only full download I can get is C.16
I think TechiBee posted it when he talked about C.33, but when I looked at these links, only full C.33 was IN/EU version. I am not sure of this, but I think I can use India (IN) or EU firmware to do a manual update. Have you heard or know if that is doable...just asking, not holding you to it ?
Thx
parcou said:
Thx for the link, my friend....
I will get into this or look at it tonight when I get off work.
I did NOT try the full update I could not download it. I have a global OP8 Pro, and all I can download in Oxygen Updater is only the C.33 incremental. If I change the app option, the only full download I can get is C.16
I think TechiBee posted it when he talked about C.33, but when I looked at these links, only full C.33 was IN/EU version. I am not sure of this, but I think I can use India (IN) or EU firmware to do a manual update. Have you heard or know if that is doable...just asking, not holding you to it ?
Thx
Click to expand...
Click to collapse
Thats odd. I cant find a full update for IN2025 too.
Maybe you can try this with the OTA too?
Code:
Inside the zip file: open "payload properties.text"
and change one line from:
oplus_update_engine_verify_disable=0
to:
oplus_update_engine_verify_disable=1
And save it.
I think you can use the EU version but i dont know if you will face problems but i dont think you will. Its doable for sure.