Related
Honor released an update today for its KIW-L24
This will upgrade your system to KIW-L24C567B351 from any of the versions given below.
If you are in KIW-L24C567B331CUSTC567D003 - Download the package from http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v74510/f1/full/update.zip
If you are in KIW-L24C567B334 - Download the package from http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v74512/f1/full/update.zip
This update consists of latest January Google security patches and few important bug fixes for device.
vsriram92 said:
Honor released an update today for its KIW-L24
This will upgrade your system to KIW-L24C567B351 from any of the versions given below.
If you are in KIW-L24C567B331CUSTC567D003 - Download the package from http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v74510/f1/full/update.zip
If you are in KIW-L24C567B334 - Download the package from http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v74512/f1/full/update.zip
This update consists of latest January Google security patches and few important bug fixes for device.
Click to expand...
Click to collapse
Thanks for the note, but either there is an issue with the update or the file got corrupted on the download. I flashed it and emui went through the update process, rebooted and then said my SD card was corrupt and to format it.
I have a 128GB card full of music TBU and saved ROMs that I did not want to lose. Went back via TWRP to previous and no damaged SD card and all is well.
Might have been the file was corrupted but just be caareful and always backup before you make any changes.
So nice of their support site to be down...
tomlogan1 said:
Thanks for the note, but either there is an issue with the update or the file got corrupted on the download. I flashed it and emui went through the update process, rebooted and then said my SD card was corrupt and to format it.
I have a 128GB card full of music TBU and saved ROMs that I did not want to lose. Went back via TWRP to previous and no damaged SD card and all is well.
Might have been the file was corrupted but just be caareful and always backup before you make any changes.
Click to expand...
Click to collapse
Instructions > https://forum.xda-developers.com/honor-5x/how-to/guide-force-installing-stock-ota-t3502874
What are the bug fixes???
Are there any new features???
I am currently on custom ROM and would like to know the answers to these questions to see if it's worth it to go back to stock rom
Hi, is there a full firmware package for this new version? Tried to upgrade and got soft-bricked and I don't know if it's safe to flash the full B331 package.
[EDiT]
Flashed the full B331, booted and applied the B351 update by powering off and pressing Vol+ & Vol -. After booting it still says B331 and my WiFi is dead.
m0ndul said:
Hi, is there a full firmware package for this new version? Tried to upgrade and got soft-bricked and I don't know if it's safe to flash the full B331 package.
[EDiT]
Flashed the full B331, booted and applied the B351 update by powering off and pressing Vol+ & Vol -. After booting it still says B331 and my WiFi is dead.
Click to expand...
Click to collapse
So much miss information .. no one bothers to find the truth
Can I ask where/when/how you found these files? There seems to be nothing official available, nor will Huawei provide any information about any prospective update.
animeme said:
Can I ask where/when/how you found these files? There seems to be nothing official available, nor will Huawei provide any information about any prospective update.
Click to expand...
Click to collapse
Link below or install the Huawei Firmware Finder form the Google Play Store and set it up to get OTA files in settings.
http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=kiw-l24
deleted
So did anyone ever take a wack at this? I've done a lot of googling and haven't been able to find anything official off the support site about this update so I was wondering if it was legit or not? I know how the update zip suppose to work and how to make it work. Just wondering if anyone used this.
GrimReaper24 said:
So did anyone ever take a wack at this? I've done a lot of googling and haven't been able to find anything official off the support site about this update so I was wondering if it was legit or not? I know how the update zip suppose to work and how to make it work. Just wondering if anyone used this.
Click to expand...
Click to collapse
What he said.
I'm hoping it's nothing more than a VoLTE update that LOS maintainers warn against anyway, if there's actually no one to further explain what it is
received this B351 update over B331, also did factory reset, GUI lag seems gone, not noticing new feature
my kiwi-L24 got re-flashed today, it is weird that this B351 update is no longer available from B331's update check
searched on internet, there is news about "honor 5c" getting a B351 nougat update
This came up on one of the 5X's that I have. Updated and forgot to put back stock recovery. Don't be like me and forget to do that. Now it won't work properly and I can't get to start any apps to try and fix it. I can put back TWRP and wipe it, but I don't want to lose my data. I also have that problem now where it keeps telling that the SD card is corrupted. I backed up the data and scrubbed the card in the phone but it keeps coming back with the same thing.
If someone did an actual successful update properly (with stock recovery) then please update and say if everything is working. If not, I'm going to have to find some way to backup the data and then scrub it.
*EDIT*
I believe something like this happened to me before. I was on B151 and went to B331 with TWRP installed by accident. What happened was that the OS was still running EMUI 3.1 but the build was saying B331. After fighting with it (and community support) I managed to get it to B331 fully and EMUI 4.0 - since then and a few custom ROMs I'm back on B151 EMUI 3.1 due to stability. Games and some apps just didn't work on the new one. The second phone was on B331 fully though - then I made the same mistake and it went to B351. This time though, the phone seems screwed. No apps will load. I can get into settings and the file manager, but no Titanium Backup and no Flashify. Going to put back TWRP and try to flash GAPPS and see if it will help me get into Play Store. From there I'll try to reinstall Flashify and flash the ZIP of the update. Will post back once done.
*EDIT*
Well that didn't work. Even after going back and trying to root the device again - then checking the option for it to not detect the dirty flash - still didn't work. Kept complaining that stock apps are already present.
I'm going to try and get some files off the device, but keep having issues. Not sure why. May just have to scrub. Will update again.
*EDIT*
With TWRP on I used "ADB PULL" to get certain files from the root system which I couldn't access otherwise for some reason. Then copied the other things (photos and such) and will now be using the UPDATE.APP to get it working. For this I formatted the SD from within TWRP and created the DLOAD folder (with no caps - so that's dload - but I'm not sure if it matters) and will be copying the UPDATE.APP. Not sure which version yet, because there was some problem with one I had downloaded before. So I need to double-check and re-download.
*EDIT*
So I've successfully flashed the UPDATE.APP from the SD card (same one the phone was claiming is corrupted). Just for reference, here is the file information and hashes.
File Name: Honor 5X_Firmware_KIW-L24_Android 6.0.1_EMUI 4.0_C567D003_United States.zip
Size: 1762266487 bytes
ADLER32: 27cb0c31
CRC32: 1d9379b9
MD2: 6517c34dc9bac0cd8680e3c4fd09d8d9
MD4: 4a803765c0ed54cb5d6853a9f365cd3b
MD5: 04f60b067d546ad71f556e44a7934dc7
SHA1: 8d2718568ac6509a40c95e42857d400395eb88d2
SHA256: 82975923172b3800d3f09f76691f2a694ab98110e3f909084a02bd566448386f
SHA384: da53b58b8e20395595590fd0cec30e56fa6a62e638ec53e46a74ebf58d051fdd7576602019bd3130ca5c00cc432715a0
SHA512: 806e0e8969c293ca8b497a786699ee306352ad6ef434552f2d23decff8a5279c7fd605e046c13f11c2f87947f5a2bdf23d78fdec6263661e68f023fd72bf4381
RIPEMD128: 9d963e5d51c9df9554fa3422da84dd27
RIPEMD160: a1e5b8f08b65dd2bb08e04d62db270ad8f4cf51a
TIGER128: 66fb4e4e4ce11cb30626aea807355f83
TIGER160: 66fb4e4e4ce11cb30626aea807355f8345f1dd79
TIGER192: 66fb4e4e4ce11cb30626aea807355f8345f1dd79dbb39488
GOST: 93774537f6ca49d4406f9d3a0316d014e1e099b34fc1cd9b968dacc870700827
The file name may be different, but as long as you got the right one you should be OK. If you have issues when copied to an SD card - verify that the file on the SD card has the correct hashes. To make it faster use CRC32. For more surety, use MD5. You can get a tool like WinMD5 to check. It's free.
So now that it's done, I'm going to set it up as a new phone and wait to see if the update comes back on. If it does, I'll get it down and upload the B351 recovery. After that I'll need to remember that I have to put back the stock recovery before running any updates. Flashify FTW.
BTW - during the initial setup after connecting to wireless it came back with the update. Pics to follow.
Files will be uploaded here: https://drive.google.com/open?id=0BzqEmGyNP_v6aTZTZDN6bWo2ZEk
*EDIT*
So the files are uploading to the folder. The screenshot is attached. Had one issue where after the update I couldn't get back into the phone. Had to wipe/factory reset. I've used FASTBOOT BOOT TWRP.IMG to take the backups of the BOOT and RECOVERY. Hopefully one of the gurus can use that and give the IMG files. I'm going to try root and get FLASHIFY to backup the stock recovery and add to the folder.
khat17 said:
This came up on one of the 5X's that I have...............
Click to expand...
Click to collapse
I don't really like to do double replies, but I guess for ease of finding the info it's better this way. Unless a mod thinks differently and wants to merge all the info.
Google Drive Link With Files
https://drive.google.com/open?id=0BzqEmGyNP_v6aTZTZDN6bWo2ZEk
This contains TWRP backups of the recovery and boot images. There's also a file called KIW-L24-B351 which was created with Flashify. I assume you can add the IMG extension to it and flash as needed.
Basically I had this update run on another phone (my wife's) and it messed with the phone due to the recovery being TWRP and not stock. My fault - forgot to do that before handing the phone back to her. I believe it happened to me before but it never messed up the phone this way. Nothing would work except core apps like settings and the stock file manager. The Play Store wouldn't even open.
Anyways - back to factory with UPDATE.APP then run the automatic update from an OTA update on wireless, then FASTBOOT BOOT TWRP.IMG and capture the backups. Then flash SuperSU to get root. Then Flashify. Files are uploaded for your convenience.
Warning that during the initial OTA it took a while. And after it was done I couldn't get into the phone with the password. Had to factory wipe/reset again and setup again. Disable passwords just in case I guess. Hope this helps others - have fun.
No major differences. I haven't really used the stock OS6 but some things look a little different. Nothing major. Will see when she's using it if it lags or has improved memory and such. Not sure if I'll be able to test with apps that wouldn't run previously for me, but will see. Tested with TransDrone and it failed. Once SeedBox information is loaded it still crashes. Only happens on OS6 so I'm sticking with OS5 on mine. Does not happen with custom roms however (from what I recall - would have to check back).
Hello every one,
I have the Honor 5X KIW-L24 rooted with TWRP, stock ROM.
I received this OTA update and saddly i pressed the update button. Now the phone is in TWRP loop.
What can I do please help. I already wipe cache and Dalvik, didnt work.
raulpcamara said:
Hello every one,
I have the Honor 5X KIW-L24 rooted with TWRP, stock ROM.
I received this OTA update and saddly i pressed the update button. Now the phone is in TWRP loop.
What can I do please help. I already wipe cache and Dalvik, didnt work.
Click to expand...
Click to collapse
Follow this video if don't know how to flash back stock recovery through adb. Then take a look at those threads how to downgrade, here, here, here. Hope it helps.
bluesky299 said:
received this B351 update over B331, also did factory reset, GUI lag seems gone, not noticing new feature
Click to expand...
Click to collapse
Same here.
It had been too many months of the Honor 5X in the closet so i almost lost track what to do but what i did was revert all the way back to Stock ROM (had to flash an extracted/saved Recovery.IMG) and then do the UPDATE.APP from Dload complete and repeat on up to the current B351.
Of course lost Root but when ready can add that back too.
Yes the Honor 5X runs much smoother now than before plus that Battery Drain issue (Remember That?) where we had to dig deep to change 4 to 0 i think, well Battery Life is also greatly improved on mine.
GrimReaper24 said:
So did anyone ever take a wack at this? I've done a lot of googling and haven't been able to find anything official off the support site about this update so I was wondering if it was legit or not? I know how the update zip suppose to work and how to make it work. Just wondering if anyone used this.
Click to expand...
Click to collapse
I tried to update as the previous user did using TWRP and got the corrupted SD card message. I then tried to go back to stock ROM. Went into bootloop.
Been having a hell of a time getting anything to work properly since.
Hi guys,
So, this is a last resort. I've followed a number of different guides and methods, but nothing has worked. The closest "success" I've had is with a Chainfire auto root; it flashes, it breaks Knox, but I still don't have SU. Could it be because I don't have an SD card? I saw it as a prerequisite in some guide but didn't really put much stock in it as that was a single mention which also involved loading it with verity, which I'm more interested in removing.
I've also tried twrp, which that looked like it had bricked my device, though I managed to recover it by flashing the auto root again. I'm speculating that it's something to do with the latest updates, but really I'm just clueless and frazzled after 4+ hours of wracking my brains. I'm not sure what other info you'd find helpful anymore without going full splurge, so I'll keep it sweet and let you question me or berate me for my vile, witholding ways as you see fit. Any help is greatly appreciated!
Edit:
My SU checker says that I've not got the binaries or root user account. The .tar from firmware.mobi is only 54mb. I tried turning off suhide, but changed no other options. Trying to use fastboot straight up fails, the device isn't recognised after adb booting (despite having tried the correct drivers and some random others multiple times over.) I've been unable to locate a release for the T585 on twrp site, though a version is out there on these forums from a year or so back.
Smellfungus said:
Hi guys,
So, this is a last resort. I've followed a number of different guides and methods, but nothing has worked. The closest "success" I've had is with a Chainfire auto root; it flashes, it breaks Knox, but I still don't have SU. Could it be because I don't have an SD card? I saw it as a prerequisite in some guide but didn't really put much stock in it as that was a single mention which also involved loading it with verity, which I'm more interested in removing.
I've also tried twrp, which that looked like it had bricked my device, though I managed to recover it by flashing the auto root again. I'm speculating that it's something to do with the latest updates, but really I'm just clueless and frazzled after 4+ hours of wracking my brains. I'm not sure what other info you'd find helpful anymore without going full splurge, so I'll keep it sweet and let you question me or berate me for my vile, witholding ways as you see fit. Any help is greatly appreciated!
Edit:
My SU checker says that I've not got the binaries or root user account. The .tar from firmware.mobi is only 54mb. I tried turning off suhide, but changed no other options. Trying to use fastboot straight up fails, the device isn't recognised after adb booting (despite having tried the correct drivers and some random others multiple times over.) I've been unable to locate a release for the T585 on twrp site, though a version is out there on these forums from a year or so back.
Click to expand...
Click to collapse
The only way I know of to successfully root a Tab A is by flashing TWRP and then using it to flash SU or Magisk. What version of TWRP are you using and what version of Odin? Using the correct ones won't brick a T585.
When I got my Tab A a couple of weeks ago I did a LOT of reading first ... but then it took less than 24 hrs from receiving it to having it rooted + running RR Oreo
Following the guide HERE I enabled OEM Unlocking and installed Odin.
Using Odin I flashed twrp-3.2.3-4-gtaxllte-OMNI6.tar from HERE.
Using the freshly installed TWRP I flashed RR-O-v6.2.1-20181210-gtaxllte-Unofficial.zip from HERE, Gapps from HERE and the latest Magisk from HERE.
That was it - rooted and ready to go :victory:
The first guide pretty much covers all the steps you need, I simply used a different TWRP version. You can't brick your device flashing TWRP unless you flash something that's not for your device. Make SURE to enable OEM Unlock first - and don't use SuperSU but Magisk.
Good luck :fingers-crossed:
Nimueh said:
When I got my Tab A a couple of weeks ago I did a LOT of reading first ... but then it took less than 24 hrs from receiving it to having it rooted + running RR Oreo
Following the guide HERE I enabled OEM Unlocking and installed Odin.
Using Odin I flashed twrp-3.2.3-4-gtaxllte-OMNI6.tar from HERE.
Using the freshly installed TWRP I flashed RR-O-v6.2.1-20181210-gtaxllte-Unofficial.zip from HERE, Gapps from HERE and the latest Magisk from HERE.
That was it - rooted and ready to go :victory:
The first guide pretty much covers all the steps you need, I simply used a different TWRP version. You can't brick your device flashing TWRP unless you flash something that's not for your device. Make SURE to enable OEM Unlock first - and don't use SuperSU but Magisk.
Good luck :fingers-crossed:
Click to expand...
Click to collapse
I am about to try this.... was you device on Android 7 (nougat) or Android 8 (Oreo) when you did this?
Thanks for your time.
webzo said:
I am about to try this.... was you device on Android 7 (nougat) or Android 8 (Oreo) when you did this?
Thanks for your time.
Click to expand...
Click to collapse
I honestly don't remember
But it should work on either one - only difference now is that we have an official recovery that can be downloaded from twrp.me directly :highfive:
Nimueh said:
When I got my Tab A a couple of weeks ago I did a LOT of reading first ... but then it took less than 24 hrs from receiving it to having it rooted + running RR Oreo
Following the guide HERE I enabled OEM Unlocking and installed Odin.
Using Odin I flashed twrp-3.2.3-4-gtaxllte-OMNI6.tar from HERE.
Using the freshly installed TWRP I flashed RR-O-v6.2.1-20181210-gtaxllte-Unofficial.zip from HERE, Gapps from HERE and the latest Magisk from HERE.
That was it - rooted and ready to go :victory:
The first guide pretty much covers all the steps you need, I simply used a different TWRP version. You can't brick your device flashing TWRP unless you flash something that's not for your device. Make SURE to enable OEM Unlock first - and don't use SuperSU but Magisk.
Good luck :fingers-crossed:
Click to expand...
Click to collapse
Does this need twrp-3.2.3-4-gtaxllte-OMNI6.tar to go from Oreo to Pie?
I am not finding -OMNI.tar anywhere. All links are dead.
Can I use a newer version of TWRP?
Thanks.
webzo said:
Does this need twrp-3.2.3-4-gtaxllte-OMNI6.tar to go from Oreo to Pie?
I am not finding -OMNI.tar anywhere. All links are dead.
Can I use a newer version of TWRP?
Thanks.
Click to expand...
Click to collapse
Ok, so I went ahead and tried with the latest TWRP (3.3.1.1), RR (v7.0.2).
Everything seemed to go well..... except, tablet is now stuck in boot animation. It won't startup.
I double checked and I don't think I missed any steps.... Any ideas on what I can try?
Thanks.
webzo said:
Ok, so I went ahead and tried with the latest TWRP (3.3.1.1), RR (v7.0.2).
Everything seemed to go well..... except, tablet is now stuck in boot animation. It won't startup.
I double checked and I don't think I missed any steps.... Any ideas on what I can try?
Thanks.
Click to expand...
Click to collapse
Update:
I tried to restore the backup via TWRP and ended up with a "unable to mount /system" error.
My /system partition was showing zero size.
Many wipes and restores didn't help.
Eventually, what seemed to help was to choose repair the system partition, change file system to FAT, change file system back to ext4. Saw it in a youtube video- https://www.youtube.com/watch?v=T-7neHzSIvc
After /system error was fixed, I did an install of RR again and it went smooth.
All is well now.
Hope this helps someone.
webzo said:
Does this need twrp-3.2.3-4-gtaxllte-OMNI6.tar to go from Oreo to Pie?
I am not finding -OMNI.tar anywhere. All links are dead.
Can I use a newer version of TWRP?
Thanks.
Click to expand...
Click to collapse
Back then we had no working official version and the Omni6 one was the only one without issues. Now we have the official and it should work just fine.
No idea why you had those problems, but I'm glad you got it all sorted
[UPDATE]:
**********
I got sick of my phone telling me I needed to update but I couldn't because I'm rooted. So finally got around to patching the last full ROM today w/ the incremental.
This is the fastbootd w/ flash_all.bat script to update to 11.0.12.12.KB05AA. The package for KB05AA (Global/US) is not yet available, hence I'm still making it available here. Be sure to alter the flash script (remove the "rem" before boot.img and recovery.img if you DO NOT want to keep your custom kernel + TWRP) ****************
3.14 GB file on MEGA
mega.nz
THIS IS ONLY FOR 11.0.9.9.KB05AA, BUT READ IT ANYWAY!!!!: ***************
I think this is the first time anyone has actually made a working incremental update for a rooted OOS device, or any with a payload.bin update method that I know of. This method doesn't require any wiping and TWRP / rooted boot.img / custom OOS kernel can be installed right after the script finishes (or left on the device), and you don't even change your active slot (usually, incremental updates will flash to the inactive slot).
I won't get into that many specifics except it was EXTREMELY DIFFICULT, but it works now. Read here if you want to do it yourself in the future, or on another phone. Should work on just about any phone that uses payload.bin files https://forum.xda-developers.com/t/...11-0-9-9-kb05aa-posted.4314677/#post-85425949
You may have to edit the .bat file to pick your RAM type (the lp5 ones are for devices with LPDDR5; it is preset for most of the phones using the LPDDR4 RAM). On the Op8T at least you can do this from adb shell:
adb shell getprop ro.boot.ddr_type; where a 0 is LPDDR4 and 1 is LPDDR5 ram. If it's 1 returned, you need to flash the lp5 files instead of the same named otherwise files in the .bat file (so edit it).
That weird -cow stuff is temp files that prevented the update from working. Not documented anywhere I could find (well, minimally explained by Google), took hours to figure out they were filling the super partition up. I had to re-engineer a Linux project (linked above) to get this working, and have officially updated from 11.0.8.13 to 11.0.9.9 COMPLETELY now. While rooted, without switching slots, and TWRP installed.
You just have to ensure you're on the latest ADB and Fastboot tools and an adb reboot bootloader, followed by a fastboot reboot fastboot should get you there. You can check with: fastboot getvar is-userspace
If it says yes, you're in fastbootd. It actually will work with TWRP installed, I found out later, as long as you reboot in TWRP to fastboot and confirm with the command above you're in fastbootd.
https://github.com/fawazahmed0/Latest-adb-fastboot-installer-for-windows/releases/tag/v1.7 has a script that will get you the Latest ADB and Fastboot and put it in a folder for you.
I uploaded it to Mega. Just use some common sense and look at the flash_all.bat file before flashing. I'd write more but I'm tired as hell from getting this working. Now we'll never have to wait for an incremental update while rooted again, at least in the foreseeable future.
I'm just going to leave this here
https://forum.xda-developers.com/t/...1-kb2003-kb2005.4178675/page-25#post-85386145
g96818 said:
I'm just going to leave this here
https://forum.xda-developers.com/t/...1-kb2003-kb2005.4178675/page-25#post-85386145
Click to expand...
Click to collapse
That never worked for me and others, Always resulted in either bootloop or booting back to previous build
nujackk said:
That never worked for me and others, Always resulted in either bootloop or booting back to previous build
Click to expand...
Click to collapse
I've mentioned it multiple times for people having issues. They need to use the unbrick tool cause there is something wrong with the original rom install from OnePlus.
g96818 said:
I've mentioned it multiple times for people having issues. They need to use the unbrick tool cause there is something wrong with the original rom install from OnePlus.
Click to expand...
Click to collapse
This Devs solution works and i appreciate his work. And appreciate your attempts but didn't work for me So ....
nujackk said:
This Devs solution works and i appreciate his work. And appreciate your attempts but didn't work for me So ....
Click to expand...
Click to collapse
It's good that you found a band-aid fix.
nujackk said:
That never worked for me and others, Always resulted in either bootloop or booting back to previous build
Click to expand...
Click to collapse
Of course I tried that solution first, it didn't work on my device.
I'm glad it did on others' devices, kudos to you for posting it (and I DO appreciate your work), but this is the only one that worked on mine. Why? Who knows. I also followed another guide that didn't work. Or else I wouldn't have wasted all my time making this (it took many, many hours to assemble). I'm not saying it's the best solution (I really hope someone just uses what I put in the other thread and assembles it into an easier format for others to use), but I have a full time job (2 actually) so I can't work on it anymore. But it works, no data loss, and TWRP can be installed. Until the next incremental update comes out, then I'll post another version using the tools I used for this, if your build doesn't work on my device. But only when I have the time...
g96818 said:
It's good that you found a band-aid fix.
Click to expand...
Click to collapse
LoL band-aid fix... Call it whatever you want, it works.
It's actually a patched 11.0.8.3.KB05AA with the incremental update applied to it for 11.0.9.9.KB05AA. So it flashes to the active slot and TWRP / rooted custom kernel can all be installed at the same time, even while you are still rooted with Magisk, and even if TWRP is installed. No data loss. I never claimed perfection on this project, just that it works for me.
Keep doing what you're doing, I'll keep doing what I'm doing. We both just aim to help others anyway. I just couldn't get any other method to work so I came up with this one, extending on the incomplete / abandoned work of others. I didn't come up with Payload extraction. Never claimed to. I didn't come up with fastbootd flashing either.
All the forked and modified code is at my GitHub repo. The fork goes back to several other devs' forks (mine is the 3rd modified fork).
Someone want to point me to the right download for the incremental update to 11.0.9.9.KB05AA? I got a download link but if it's not for this exact ROM, it would be dangerous (I don't know what would break) if I applied it and patched the incremental 11.0.9.9 (which is like a full ROM in the way I distribute it here). I believe the update is 11.0.10.10.KB05AA. I tried downloading as illustrated in the linked thread and it halfway installed (Op8T's don't seem to like the "remove Magisk images" and then install the update method, it totally jacked up my system (like long boot time, alarms didn't work, numbers wouldn't always appear to login to the phone after reboot, etc.), luckily I had backed up Super in TWRP and that fixed it (upon a restore). The one someone told me was the official link to the incremental update did not work with the Linux program I hacked, so it's either incapable of patching an incremental 2x, or I got the wrong file downloaded. My life is so crazy at the moment I don't have time to screw up my phone just to get the incremental update downloaded on my phone and extract it, so if anyone has already done that, please let me know.
mslezak said:
Someone want to point me to the right download for the incremental update to 11.0.9.9.KB05AA? I got a download link but if it's not for this exact ROM, it would be dangerous (I don't know what would break) if I applied it and patched the incremental 11.0.9.9 (which is like a full ROM in the way I distribute it here). I believe the update is 11.0.10.10.KB05AA. I tried downloading as illustrated in the linked thread and it halfway installed (Op8T's don't seem to like the "remove Magisk images" and then install the update method, it totally jacked up my system (like long boot time, alarms didn't work, numbers wouldn't always appear to login to the phone after reboot, etc.), luckily I had backed up Super in TWRP and that fixed it (upon a restore). The one someone told me was the official link to the incremental update did not work with the Linux program I hacked, so it's either incapable of patching an incremental 2x, or I got the wrong file downloaded. My life is so crazy at the moment I don't have time to screw up my phone just to get the incremental update downloaded on my phone and extract it, so if anyone has already done that, please let me know.
Click to expand...
Click to collapse
Better to install the full ROM
Download Oxygen Updater in app store and select your device AA for global and Ba for European device.
Go to settings, system update wait til 100% and Don't reboot yet if you want to keep Root
Go to Magisk and install ota in inactive slot
5star02707 said:
Better to install the full ROM
Download Oxygen Updater in app store and select your device AA for global and Ba for European device.
Go to settings, system update wait til 100% and Don't reboot yet if you want to keep Root
Go to Magisk and install ota in inactive slot
Click to expand...
Click to collapse
I think maybe you misunderstood what I did in this thread. I patched a full ROM with the incremental update of 11.0.9.9.KB05AA. So while OnePlus does not have a full ROM available for download (yet), it is available for download here.
Yeah the method you propose is the "normal" rooted way, but if you're rooted already it forces you to full ROMs not OTAs. You'll be on 11.0.8.3.KB05AA. The goal here is to get on 11.0.10.10.KB05AA (someone NOT ROOTED could download the OTA update using Oxygen Updater and upload it here so I could make a patched version for those that want to keep their root / custom kernel / TWRP / etc and avoid the hassle of unrooting first, which wipes your data partition). At least my Oxygen Updater won't let me download incremental updates even with Magisk Images removed (don't try this unless you're on Op8 / Op8 Pro; some people are having big system update issues on Op8T incremental hence why this thread exists.) It jacked up my system pretty bad (Magisk images removed, Settings / System / System Updates method) until after a boot.img and super restore from TWRP. Not all devices were setup the same (mine is a US carrier converted to US KB05AA). To my knowledge, no direct download has been posted for KB05AA incremental update. Here or on TG. If you have found one, please post a link here. The only one out I've seen works on European ROMs. OnePlus always does KB05AA last for whatever reason.
11.0.10.10.KB05AA posted with caveats - please back up your data as suggested in case the Phone Services APK doesn't fix your SIM after a flash, and you end up formatting the data partition. You may want to try some other methods or just plan on restoring (not with TWRP Alpha in my experience).
mslezak said:
Guys, bad news. So 11.0.10.10.KB05AA incremental does something to the data partition and kills your SIM access.
...
Click to expand...
Click to collapse
I successfully update from 9.9 to 10.10 including keeping root. I have no issues with my Sim card. So, for me, the update is fine.
However, I believe that the 10.10 update includes a key change. This results in the data partition being unreadable if you swap back to the previous slot after the update. I found this out by doing just that using TWRP.
But syncing the 10.10 firmware to the inactive slot fixes this. It might be possible (I haven't tried it) to just sync the keymaster partition to the inactive slot and then restore 9.9 (excluding keymaster).
BillGoss said:
I successfully update from 9.9 to 10.10 including keeping root. I have no issues with my Sim card. So, for me, the update is fine.
However, I believe that the 10.10 update includes a key change. This results in the data partition being unreadable if you swap back to the previous slot after the update. I found this out by doing just that using TWRP.
But syncing the 10.10 firmware to the inactive slot fixes this. It might be possible (I haven't tried it) to just sync the keymaster partition to the inactive slot and then restore 9.9 (excluding keymaster).
Click to expand...
Click to collapse
Can you explain how you managed to update it? I'm screwed at this point anyhow, would like to hear how you did it. Are you just saying when you update flash to both slots and the data is still readable? Instead of flashing to active only? I still have the extracted / patched ROM, not going to try it out now (or for a while) unless I know someone has figured out a way to make it not break the system data. (Note: I'm on a very hacked phone; it's a carrier T-mobile originally fastbootd converted to Global, then updated on Global since then). I realize most people probably don't have a phone that's been altered this much. Then the easier methods are more likely to work. I'm also running a custom fork (mine) of RadioActive kernel (just tweaked how I like it, wakelocks blocked to save idle battery, some GPU frequencies added, etc). I tried running just the patched boot.img with Magisk but still Phone Services was busted.
@mslezak, When I get an update I:
- use a terminal session (you could also use ADB) to restore the stock boot and recovery (this way I don't lose root yet)
- install the update but don't reboot
- copy the new boot image and patch it
- turn on airplane mode (to avoid SafetyNet and certification issues in the next step)
- reboot the phone and the updated system comes up
- flash the patched boot image and TWRP in fastboot/bootloader
- reboot and disable airplane mode
This is basically @osm0sis' process from https://forum.xda-developers.com/t/...ices-platforms.2239421/page-149#post-84764713
No, I'm not saying flash to both slots, because that will make it impossible to fall back to the current system if the update fails (though this is meaningless if you're manually flashing partitions).
I've got into the habit of syncing active to inactive (after I'm happy with the update) simply because it's required when going from OOS to a custom ROM (I use a shell script based on the LineageOS sync zip). And, after the sync, I can now access the data partition from the inactive slot (which wasn't the case just after the update due to the different keys).
mslezak said:
Can you explain how you managed to update it? I'm screwed at this point anyhow, would like to hear how you did it. Are you just saying when you update flash to both slots and the data is still readable? Instead of flashing to active only? I still have the extracted / patched ROM, not going to try it out now (or for a while) unless I know someone has figured out a way to make it not break the system data. (Note: I'm on a very hacked phone; it's a carrier T-mobile originally fastbootd converted to Global, then updated on Global since then). I realize most people probably don't have a phone that's been altered this much. Then the easier methods are more likely to work. I'm also running a custom fork (mine) of RadioActive kernel (just tweaked how I like it, wakelocks blocked to save idle battery, some GPU frequencies added, etc). I tried running just the patched boot.img with Magisk but still Phone Services was busted.
Click to expand...
Click to collapse
Thats not very hacked/hacked at all, and quite a few use that setup
xstefen said:
Thats not very hacked/hacked at all, and quite a few use that setup
Click to expand...
Click to collapse
LoL I gave up fastbootd flashed to 11.0.10.10.KB05AA and formatted data, let Google download everything it backed up, and am back in business. Just have a lot of apps to login to / Magisk modules to add / etc.
So yeah my patched 11.0.10.10.KB05AA works but the data must be formatted or the SIM doesn't work (at least for me; I don't know if anyone else has tried it since I just posted it a few hours ago; it could be that it works for some without causing issues, I don't have any idea). The goal was to not have to mess up the data partition.... but I can't control what OnePlus does in their updates... Try what worked for others posted here first I'd suggest, or just make solid backups of everything knowing you're going to likely need to reinstall / re-login to everything and format the data partition. New pin, new fingerprint, etc. Re-login to your wifi blah blah.
It's still a full unreleased ROM so I posted it for those that don't mind taking backups (outside of TWRP) if they want to keep root & TWRP on the new release... Yeah a pain to setup if you aren't warned to use another backup method (maybe there is a better backup method, maybe Migrate (app store early access) is developed enough for easy transfer now, I know many people said it worked well in the past but haven't been following the updates. Still free).
It dawned on me later that since the only thing that didn't work using this method going from 11.0.9.9.KB05AA to 11.0.10.10.KB05AA was phone services, that I should just include the working version in this post. Since I already did it the hard way and restored everything back to normal. AS I SAID ABOVE, IF PHONE SERVICES ISN'T ENOUGH TO FIX THE ISSUE, PM ME AND I CAN EXTRACT MORE RELATED FILES UNTIL IT WORKS AGAIN. Unfortunately, I can't just downgrade to 11.0.9.9.KB05AA and keep trying fastbootd over and over again as I don't have the time.
g96818 said:
I've mentioned it multiple times for people having issues. They need to use the unbrick tool cause there is something wrong with the original rom install from OnePlus.
Click to expand...
Click to collapse
The whole point of this is to AVOID the unbrick tool, reinstalling an outdated version, updating each new ROM build since the brick tool was made, and starting over clean. I think... Have a hunch at least we're almost there on 11.0.10.10.KB05AA with an APK install... Although just backing up everything first will always work (if you don't mind formatting your data partition) just as it's posted here already. Always an issue for us rooted users (especially on Global) since we're always last in line to get a full ROM. This IS a full ROM, payload extracted and patched with incremental updates. Still not available from OnePlus Global (KB05AA) as I checked today, so still relevant.
Ladies and Gents,
I have removed some off topic posts from this thread because I believe we could express the same meaning in more civil words. Please try to do that from now on.
Thanks.
Jerry
FSM
Hello, I tried to root via magisk patched boot image route and I attempted to load into slot A and slot B but no method worked. All roads lead to a soft brick even if I load boot images uploaded on here. If anyone has a working root method I would love to hear it. If there is already a post on this just link me to it please, I looked and could not find one that worked
spider876 said:
Hello, I tried to root via magisk patched boot image route and I attempted to load into slot A and slot B but no method worked. All roads lead to a soft brick even if I load boot images uploaded on here. If anyone has a working root method I would love to hear it. If there is already a post on this just link me to it please, I looked and could not find one that worked
Click to expand...
Click to collapse
Need some help rooting my one plus 6t
Hey peeps, Its been about a 7-8 years since i last tinkered with an android phone so im totally out the loop. My one plus 6t recently went up in flames due to the latest update and I had to wipe it. I've been wanting to root my phone and...
forum.xda-developers.com
s.seila said:
Need some help rooting my one plus 6t
Hey peeps, Its been about a 7-8 years since i last tinkered with an android phone so im totally out the loop. My one plus 6t recently went up in flames due to the latest update and I had to wipe it. I've been wanting to root my phone and...
forum.xda-developers.com
Click to expand...
Click to collapse
I saw that and I did try loading the magisk patched boot file from there to the same result
spider876 said:
I saw that and I did try loading the magisk patched boot file from there to the same result
Click to expand...
Click to collapse
What version you're on ? 11.xxxx
s.seila said:
What version you're on ? 11.xxxx
Click to expand...
Click to collapse
11.1.1.1
Hi, I've been struggling big time to update my device to Android 13. I bought mine when only 1.1.7 hotfix was out and therefore, now that I have unlocked the bootloader (yes, even unlock critical) and rooted the device, I'm not able to install 1.1.8, let alone Android 13. I have already bricked one and managed to get a new one but I don't want to risk it again. I've searched all over Google to a proper guide to update to Android 13, even with sideload, but it gives me an error regarding the payload file, at about 48% of the progress. Tried the *#*#682#*#* method but it stops with error code 20. I have tried flashing the stock boot file but same thing, code 20 from manual update. I'm pretty much desperate at this point and I'm even thinking about unrooting, lock the bootloader again and hopefully update it without an itch, but I really wouldn't want to wipe the device, so, if there's somebody there that could help me through a 100% working process, I'll always be in your debt.
Enzucuni said:
Hi, I've been struggling big time to update my device to Android 13. I bought mine when only 1.1.7 hotfix was out and therefore, now that I have unlocked the bootloader (yes, even unlock critical) and rooted the device, I'm not able to install 1.1.8, let alone Android 13. I have already bricked one and managed to get a new one but I don't want to risk it again. I've searched all over Google to a proper guide to update to Android 13, even with sideload, but it gives me an error regarding the payload file, at about 48% of the progress. Tried the *#*#682#*#* method but it stops with error code 20. I have tried flashing the stock boot file but same thing, code 20 from manual update. I'm pretty much desperate at this point and I'm even thinking about unrooting, lock the bootloader again and hopefully update it without an itch, but I really wouldn't want to wipe the device, so, if there's somebody there that could help me through a 100% working process, I'll always be in your debt.
Click to expand...
Click to collapse
The best part of this whole thing is that you're rooted.
Do a backup with Swift Backup or what ever your backup app you prefer. Wipe it back to stock without locking the bootloader, make sure your sim card is not inserted then do your OTA updates.
As for the second device you bricked, there's a unbrick tool here:
unbrick tool- EDL Flash-Read-Repair Region Change tool
unbrick tool Now available for Nothing Phone1.. Features: Read Firmware (EDL) (locked bootloader) Flash Firmware (EDL) (locked bootloader) backup EFS (EDL) (locked bootloader) Wipe FRP & userdata (EDL) (locked bootloader) Size: 2.7GB Version...
forum.xda-developers.com
Just need to get or make a EDL cable then flash and you'll be back in business.
HermitDash said:
The best part of this whole thing is that you're rooted.
Do a backup with Swift Backup or what ever your backup app you prefer. Wipe it back to stock without locking the bootloader, make sure your sim card is not inserted then do your OTA updates.
As for the second device you bricked, there's a unbrick tool here:
unbrick tool- EDL Flash-Read-Repair Region Change tool
unbrick tool Now available for Nothing Phone1.. Features: Read Firmware (EDL) (locked bootloader) Flash Firmware (EDL) (locked bootloader) backup EFS (EDL) (locked bootloader) Wipe FRP & userdata (EDL) (locked bootloader) Size: 2.7GB Version...
forum.xda-developers.com
Just need to get or make a EDL cable then flash and you'll be back in business.
Click to expand...
Click to collapse
First bricked device was replaced in RMA. But yeah, rooted, unlocked and yet nothing works. I was thinking about wiping it, even if I don't really want to because it's a pain every time. Man, Android modding when to ****e and I'm leaning more and more towards getting an iPhone and call it a day, maybe with a jailbreak
Enzucuni said:
First bricked device was replaced in RMA. But yeah, rooted, unlocked and yet nothing works. I was thinking about wiping it, even if I don't really want to because it's a pain every time. Man, Android modding when to ****e and I'm leaning more and more towards getting an iPhone and call it a day, maybe with a jailbreak
Click to expand...
Click to collapse
Swift does their backups well so from wipe to setup depending on how many apps ya got took like 20 mins to do?
Once you get to A13 tho, my god the battery life is amazing. I don't use my NP1 as a daily driver but it sits in my pocket along with my daily OP7Pro and it out lasts it by a mile. Really hyped for the NP2 and what they bring optimization wise.
Or in your case you could carry both and see how you feel about it xD
Oh and it's likely the patched boot image (while rooted) that's causing the update errors. Once you restore the stock boot image you should be able to update without issue.
HermitDash said:
Swift does their backups well so from wipe to setup depending on how many apps ya got took like 20 mins to do?
Once you get to A13 tho, my god the battery life is amazing. I don't use my NP1 as a daily driver but it sits in my pocket along with my daily OP7Pro and it out lasts it by a mile. Really hyped for the NP2 and what they bring optimization wise.
Or in your case you could carry both and see how you feel about it xD
Oh and it's likely the patched boot image (while rooted) that's causing the update errors. Once you restore the stock boot image you should be able to update without issue.
Click to expand...
Click to collapse
I actually restored it but to no avail. Same errors as described
Enzucuni said:
I actually restored it but to no avail. Same errors as described
Click to expand...
Click to collapse
Welp, back to stock you go then haha ADB it to EDL then run the unbrick tool and you should be at 0
I might be actually lazy enough to wait for a hint of a custom twrp-like recovery and go from there
Enzucuni said:
I might be actually lazy enough to wait for a hint of a custom twrp-like recovery and go from there
Click to expand...
Click to collapse
Might not be stable on first release but yea that's in the rumor pipelines
Yeah, I think I'll wait. A12 is still really nice. Some bugs here and there but perfectly usable and battery is basically infinite.
First of all, to jailbreak the iPhone and set it up correctly with all the needed software that jailbreaking provides nowdays ... is actually harder than it was a few years ago.
Secondly, if you had just read through the full topic containing the Nothing OS repo, you would have found several people with the same problem that u had, who had solved it successfully.
Go back to stock, wipe, and redo the official step-by-step of updating, will work like a charm. if you want to jailbreak. First, read through the posts of others to see if there are any problems that you would like to avoid, and if there are, don't do it.
You are lucky enough to have had your first device replaced by a new one just like that. Updating while rooted was always a problem for Android, and it always varied per device. it was up to the one who is rooting to check the situation regarding his/her specific model
You could try flashing the fastboot ROMs made by @ot_inc (it's not 100% safe for your data so make a backup in any case).
[Restore NothingOS & Magisk] Nothing Phone(1) Fastboot ROM(Full ROM) & boot.img Global v1.1.6
Fastboot ROM and boot.img for NothingPhone(1) are now available. v1.1.6 is available. Sorry for my poor English, I'm Japanese. https://reindex-ot.github.io/
forum.xda-developers.com
kriistofor said:
First of all, to jailbreak the iPhone and set it up correctly with all the needed software that jailbreaking provides nowdays ... is actually harder than it was a few years ago.
Secondly, if you had just read through the full topic containing the Nothing OS repo, you would have found several people with the same problem that u had, who had solved it successfully.
Go back to stock, wipe, and redo the official step-by-step of updating, will work like a charm. if you want to jailbreak. First, read through the posts of others to see if there are any problems that you would like to avoid, and if there are, don't do it.
You are lucky enough to have had your first device replaced by a new one just like that. Updating while rooted was always a problem for Android, and it always varied per device. it was up to the one who is rooting to check the situation regarding his/her specific model
Click to expand...
Click to collapse
Where is the step by step ? The one that actually works ?
hmm, honestly it may be on somewhere in the first few pages (not the first one) but you can also search the google, now there are several sites quoting options for updating nothing phone.
sorry if i sounded harsh
anyways, if you go back to stock, and update the device from 1.1.7 to 1.5 incl. all hotfix updates, it should go smoothly.
I also said if you want to jailbreak in one moment in my post when i meant to say if you want to root.
Rooting nowdays is easy and hard at the same time. easy to pull off, but hard to understand that now there are several different steps that need to be done to turn the rooted device into a fully functional one. and for many it is not worth it, but for those that are interested, I would just advise reading through all the posts carefully and learning to search efficiently. Not only will you find the answer yourself, thus remembering it more clearly, but you will also be introduced to facts you were unaware of.
good luck, the most important step is to go back to stock succesfully, read the whole nothing os repo thread just to make sure you are not missing something
kriistofor said:
hmm, honestly it may be on somewhere in the first few pages (not the first one) but you can also search the google, now there are several sites quoting options for updating nothing phone.
sorry if i sounded harsh
anyways, if you go back to stock, and update the device from 1.1.7 to 1.5 incl. all hotfix updates, it should go smoothly.
I also said if you want to jailbreak in one moment in my post when i meant to say if you want to root.
Rooting nowdays is easy and hard at the same time. easy to pull off, but hard to understand that now there are several different steps that need to be done to turn the rooted device into a fully functional one. and for many it is not worth it, but for those that are interested, I would just advise reading through all the posts carefully and learning to search efficiently. Not only will you find the answer yourself, thus remembering it more clearly, but you will also be introduced to facts you were unaware of.
good luck, the most important step is to go back to stock succesfully, read the whole nothing os repo thread just to make sure you are not missing something
Click to expand...
Click to collapse
Umm.. no, you're not sounding harsh. And I've already done that: "google it" and stuff. This is why I post teh question here. This is not my first time at this lol !
kriistofor said:
hmm, honestly it may be on somewhere in the first few pages (not the first one) but you can also search the google, now there are several sites quoting options for updating nothing phone.
sorry if i sounded harsh
anyways, if you go back to stock, and update the device from 1.1.7 to 1.5 incl. all hotfix updates, it should go smoothly.
I also said if you want to jailbreak in one moment in my post when i meant to say if you want to root.
Rooting nowdays is easy and hard at the same time. easy to pull off, but hard to understand that now there are several different steps that need to be done to turn the rooted device into a fully functional one. and for many it is not worth it, but for those that are interested, I would just advise reading through all the posts carefully and learning to search efficiently. Not only will you find the answer yourself, thus remembering it more clearly, but you will also be introduced to facts you were unaware of.
good luck, the most important step is to go back to stock succesfully, read the whole nothing os repo thread just to make sure you are not missing something
Click to expand...
Click to collapse
You said, "Go back to stock, wipe, and redo the official step-by-step of updating, will work like a charm."
Where are you getting this from ?