Database Users

New update available for KIW-L24

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.

Please Recommend Me The Top 2/3 Most Stable Slim Roms - New Axon 7 User!

I hate asking this as each has his own preference, however, I have only just ordered my ZTE Axon device as it was such a good offer, being even cheaper than brand new 2018 mid rangers! I purchased the device brand new and sealed for just £193 ($274) so you cannot go wrong.
My current phone was the Sony Xperia XZ Premium but I am giving it away to my wife and need another to replace it.
After some reading it seems the first thing I need to do is install all drivers and run the Axon 7 Tool kit. This will unlock bootloader, root and flash recovery from my understanding.
Then I can proceed to installing a custom rom of my choice followed by immediately flashing a modem otherwise I will not have any signal. Would this be everything needed to successfully running a custom rom trouble free?
Lastly, I would like a simple rom, preferably based on stock/vanilla Android, slim and bloat free. Something very basic, bug free and made for pure speed and decent battery. What are the top recommended roms with this regard? I did look into these, anything better? What are the differences? Thank you so much for your advise.
https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3716825
https://forum.xda-developers.com/axon-7/development/rom-slm-version-t3704143
https://forum.xda-developers.com/axon-7/development/rom-dark-rom-t3654264

kanej2006 said:
I hate asking this as each has his own preference, however, I have only just ordered my ZTE Axon device as it was such a good offer, being even cheaper than brand new 2018 mid rangers! I purchased the device brand new and sealed for just £193 ($274) so you cannot go wrong.
My current phone was the Sony Xperia XZ Premium but I am giving it away to my wife and need another to replace it.
After some reading it seems the first thing I need to do is install all drivers and run the Axon 7 Tool kit. This will unlock bootloader, root and flash recovery from my understanding.
Then I can proceed to installing a custom rom of my choice followed by immediately flashing a modem otherwise I will not have any signal. Would this be everything needed to successfully running a custom rom trouble free?
Lastly, I would like a simple rom, preferably based on stock/vanilla Android, slim and bloat free. Something very basic, bug free and made for pure speed and decent battery. What are the top recommended roms with this regard? I did look into these, anything better? What are the differences? Thank you so much for your advise.
https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3716825
https://forum.xda-developers.com/axon-7/development/rom-slm-version-t3704143
https://forum.xda-developers.com/axon-7/development/rom-dark-rom-t3654264
Click to expand...
Click to collapse
As for the SL!M roms i made ( making some advertisement here ) i only can advise looking at these ones as they are aroma roms and can be debloated further. Battery tweak is included and choice between SuperSU and Magisk is possible. These roms are stock-based as to preserve, imo, the sound quality of the phone as it came out of the box. No bug issues imo and fully up to date :
https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3716825
Based on MiFavor5.0 (CN) but fully applyable on all versions
https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3735003
Based on stock G version but fully applyable on all versions and with the latest security patches of the A2017G-N(ougat)-B09
But then again others can comment on my slim roms better then i can perhap :cyclops:
Futhermore i do not advice https://forum.xda-developers.com/axon-7/development/rom-slm-version-t3704143 as it is was my first version of MiFavor 5.0. Instead use the first link.
Didn't used the last one you mentioned based on LOS but others can advice more into this.
Good Luck and ENJOY !

raystef66 said:
As for the SL!M roms i made ( making some advertisement here ) i only can advise looking at these ones as they are aroma roms and can be debloated further. Battery tweak is included and choice between SuperSU and Magisk is possible. These roms are stock-based as to preserve, imo, the sound quality of the phone as it came out of the box. No bug issues imo and fully up to date :
https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3716825
Based on MiFavor5.0 (CN) but fully applyable on all versions
https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3735003
Based on stock G version but fully applyable on all versions and with the latest security patches of the A2017G-N(ougat)-B09
But then again others can comment on my slim roms better then i can perhap :cyclops:
Futhermore i do not advice https://forum.xda-developers.com/axon-7/development/rom-slm-version-t3704143 as it is was my first version of MiFavor 5.0. Instead use the first link.
Didn't used the last one you mentioned based on LOS but others can advice more into this.
Good Luck and ENJOY !
Click to expand...
Click to collapse
^ Thank you very much raystef66 for your speedy response! I will go for this version - https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3735003
Fingers crossed I should receive my Axon 7 Sunday or Monday at the very latest. First Thing I'll run the Axon 7 Toolkit so that I can unlock the bootloader, have recovery and root then I'll be able to flash your rom, looking forward into doing so!
I'll keep you informed in the coming days when complete. :good:

kanej2006 said:
^ Thank you very much raystef66 for your speedy response! I will go for this version - https://forum.xda-developers.com/axon-7/development/rom-slm-dfnr-t3735003
Fingers crossed I should receive my Axon 7 Sunday or Monday at the very latest. First Thing I'll run the Axon 7 Toolkit so that I can unlock the bootloader, have recovery and root then I'll be able to flash your rom, looking forward into doing so!
I'll keep you informed in the coming days when complete. :good:
Click to expand...
Click to collapse
Yeah, very exciting isn't it :good: It's a damn good phone, quick, nice quality screen and an amazing sound... !
I assume you'll get the G version ? The SL!M➃ is based on this G-version (btw, take a look at the DownloadCenter to have all necessary files) and keeps all things to stock. Just some minor mods and improvements, nothing fancy as to stay stock. With the battery tweak included i always get >7h SOT. But that depends of course on usage. But then again i do alot in a day . Some others have no benefit on the battery tweak but i'll hope you end up with a descent SOT.
Keep us posted :good:

raystef66 said:
Yeah, very exciting isn't it :good: It's a damn good phone, quick, nice quality screen and an amazing sound... !
I assume you'll get the G version ? The SL!M➃ is based on this G-version (btw, take a look at the DownloadCenter to have all necessary files) and keeps all things to stock. Just some minor mods and improvements, nothing fancy as to stay stock. With the battery tweak included i always get >7h SOT. But that depends of course on usage. But then again i do alot in a day . Some others have no benefit on the battery tweak but i'll hope you end up with a descent SOT.
Keep us posted :good:
Click to expand...
Click to collapse
Sounds good! I would be happy with around 7 hours SOT. Once received I'll let you know what version I receive, however, I'm guessing I'll get the Chinese version as it's coming from Dubai, UAE (Middle East) and most likely it'll come from China and not EU as it's much closer.
I have everything ready accept for a flashable TWRP. The link appears down for me and I was not able to find a flashable version, could you please give me a link of a working one? I was only able to find a non flashable version which is run via CMD/fastboot commands.
I would much rather a flashable recovery in which I can flash once installing your rom along with SuperSU or Magisk. Regards!

kanej2006 said:
Sounds good! I would be happy with around 7 hours SOT. Once received I'll let you know what version I receive, however, I'm guessing I'll get the Chinese version as it's coming from Dubai, UAE (Middle East) and most likely it'll come from China and not EU as it's much closer.
I have everything ready accept for a flashable TWRP. The link appears down for me and I was not able to find a flashable version, could you please give me a link of a working one? I was only able to find a non flashable version which is run via CMD/fastboot commands.
I would much rather a flashable recovery in which I can flash once installing your rom along with SuperSU or Magisk. Regards!
Click to expand...
Click to collapse
The TWRP is inside the toolkit, so you can flash it downthere imo. Never done this that way though as in those early days i used this one to do everything. But use the toolkit and you're good to go.

raystef66 said:
The TWRP is inside the toolkit, so you can flash it downthere imo. Never done this that way though as in those early days i used this one to do everything. But use the toolkit and you're good to go.
Click to expand...
Click to collapse
Ah good to hear, glad it's included in the kit. So I can simply use the one from the kit to flash recovery after flashing your rom? Because in the instructions it mentions we have to manually flash recovery after the rom.

kanej2006 said:
Ah good to hear, glad it's included in the kit. So I can simply use the one from the kit to flash recovery after flashing your rom? Because in the instructions it mentions we have to manually flash recovery after the rom.
Click to expand...
Click to collapse
That depends. I dont know what version of twrp is installed via the toolkit. Perhaps it checkes for the latest when it updates but not sure. But if a certain version is installed which is not the latest, put the latest twrp.img onto your int or extSD and flash via your twrp you've installed.
Second, if your phone would be an CN version and not a G, you'll have to install the Universal BL and your specific modem as described in the rom thread. You can find them in the link of the rom thread. So, after installing the Universal BL (which has an older version of twrp !) , you'd have to install the latest via twrp too. So just flash the twrp image and you're good to go.
Btw, i made a flashable zip before of that Universal BL which replaces the old twrp with the 3.1.1.0 version, which will do fine too.
Here's the link : https://androidfilehost.com/?fid=673791459329066038 (it also works on the SLIM4 as it just replaces twrp)
So after installing this version, you dont need to flash another twrp (as it brings you to the 3.1.1.0 as said)

kanej2006 said:
Ah good to hear, glad it's included in the kit. So I can simply use the one from the kit to flash recovery after flashing your rom? Because in the instructions it mentions we have to manually flash recovery after the rom.
Click to expand...
Click to collapse
Uuhh. I think you'll get the G version. Anything else than China and US gets G. With that said, I recommend you two things:
- (If you get a G) Use Controllerboy's guide instead of the toolkit. Lately a lot of stuff is going wrong with the toolkit
-Whatever happens, DO NOT ATTEMPT TO RELOCK THE BOOTLOADER.
-Once you have TWRP, just follow the instructions on each ROM. Never flash stuff from other models.
-Take the TWRP img either from raystef66's download center or from twrp.me

raystef66 said:
I dont know what version of twrp is installed via the toolkit. Perhaps it checkes for the latest when it updates but not sure. But if a certain version is installed which is not the latest, put the latest twrp.img onto your int or extSD and flash via your twrp you've installed.
Second, if your phone would be an CN version and not a G, you'll have to install the Universal BL and your specific modem as described in the rom thread. You can find them in the link of the rom thread. So, after installing the Universal BL (which has an older version of twrp !) , you'd have to install the latest via twrp too. So just flash the twrp image and you're good to go.
Btw, i made a flashable zip before of that Universal BL which replaces the old twrp with the 3.1.1.0 version, which will do fine too.
Here's the link : https://androidfilehost.com/?fid=673791459329066038 (it also works on the SLIM4 as it just replaces twrp)
So after installing this version, you dont need to flash another twrp (as it brings you to the 3.1.1.0 as said)
Click to expand...
Click to collapse
Will do. You are right, the toolkit automatically checks for the latest update and it finds version 3.1.1.0.
Choose an username... said:
Uuhh. I think you'll get the G version. Anything else than China and US gets G. With that said, I recommend you two things:
- (If you get a G) Use Controllerboy's guide instead of the toolkit. Lately a lot of stuff is going wrong with the toolkit
-Whatever happens, DO NOT ATTEMPT TO RELOCK THE BOOTLOADER.
-Once you have TWRP, just follow the instructions on each ROM. Never flash stuff from other models.
-Take the TWRP img either from raystef66's download center or from twrp.me
Click to expand...
Click to collapse
I did see on the forum users attempting to relock the bootloader and it worsened things, I will not attempt this.
Should be able to let you know tomorrow or the day after what version I get and hopefully when I successfully gain recovery and root access!
I just hope I don't get the dead microSD bug that many people have mentioned. Top of the range 64Gb/128Gb MicroSD cards can be costly so I would not like to have them corrupted!

@raystef66, Do you have any other download links for your rom aside from androidfilehost? I tried several different servers but all keep randomly freezing otherwise saying 5 hours, 6 hours, 11 hours and 15 hours. Extremely slow download.

If you want to try a more Android vanilla ROM, then I suggest AICP. Be sure to use the unofficial builds by genesixxbf3. They are very stable and have good features.
https://forum.xda-developers.com/axon-7/development/rom-aicp-12-1-t3611013

kanej2006 said:
@raystef66, Do you have any other download links for your rom aside from androidfilehost? I tried several different servers but all keep randomly freezing otherwise saying 5 hours, 6 hours, 11 hours and 15 hours. Extremely slow download.
Click to expand...
Click to collapse
Yeah, sometime AFH can be cruel. Just depends. I tried the Washington DC just a moment and no problems there. I just advice, take one and let it take it's time. Some way or another the download speed gets stable enough And then again, you still have a bit of time don't you or has it dropped of yet with the postman :cyclops: Do I Hear a heartbeat there ? :good:

raystef66 said:
Yeah, sometime AFH can be cruel. Just depends. I tried the Washington DC just a moment and no problems there. I just advice, take one and let it take it's time. Some way or another the download speed gets stable enough And then again, you still have a bit of time don't you or has it dropped of yet with the postman :cyclops: Do I Hear a heartbeat there ? :good:
Click to expand...
Click to collapse
Haha, no, not yet received! Where I am living at the moment, the weekend is Friday and Saturday, Sunday to Thursday work, strange but that's the way it is.
The seller estimates the item to arrive on Sunday or Monday, hopefully Sunday.
In the end the Netherland's sever finally managed to get me the 2.1Gb download complete. I did try others but were slower. Good thing in your rom you included the 3 different models for the Axon 7. I'm yet to see which one I receive!

Confirmed G version received.

kanej2006 said:
Confirmed G version received.
Click to expand...
Click to collapse
The AcTiOn can begin :good:
Use this guide like said above and you'll be ok.

raystef66 said:
The AcTiOn can begin :good:
Use this guide like said above and you'll be ok.
Click to expand...
Click to collapse
Not working, been trying for hours.
Not connecting despite all drivers installed, including Qualcom driver. Followed all instructions as stated. Stuck from number 20. When entering this command I get ''failed to connect''
When typing in adb devices it finds my device.
1) Backup all the data of your phone's internal memory that you don't want to lose. Copy it to your PC
2) Download the axon7tool from here: http://www.filedropper.com/axon7tool-15-win64
3) Download minimal adb and fastboot from here: https://www.androidfilehost.com/?fid=457095661767103465
4) Unzip the minimal adb and fastboot file, place the folder with the files in it somewhere you can easily find it
5) Place the axon7tool exe in the same folder as adb.exe and rename it to "axon7tool.exe" (it's easier to work with that way)
6) Download the TWRP .img and .bin files from here: https://drive.google.com/open?id=0B4...nlaZU1NRldoRjA
7) Place the TWRP .img file in the same folder as "adb.exe" and "axon7tool.exe", rename it to "recovery.img"
8) Make a copy of the "recovery.img" file and name it "recovery.bin". Leave it in the same folder
9) Go to settings in your phone and go to "About Phone". Tap "Build Number" 7 times to make the Developer Options available
10) Go to "Developers options" and tick "Allow OEM unlock" and "Android Debugging"
11) Connect your Axon 7 to your PC
12) Open a command window by holding shift and right-clicking in a blank space in the folder where the "adb.exe", " axon7tool.exe", "recovery.img" and "recovery.bin" files are located. Click "Open command window here"
13) Type "adb devices" and hit enter. You should see one device with some code listed
14) Type "adb reboot edl" and hit enter. Your device will reboot to EDL mode. It appears to be off, but it is in fact in EDL mode.
15) Go to Device Manager on your pc and verify your Axon 7 is listed as "QUSB_BULK"
16) In command, type "axon7tool -r gpt boot recovery" and hit enter
17) After it is executed, your phone will reboot. Wait until it has fully booted.
18) In command, type "adb reboot edl"
19) Verify you now have 3 backup files in your ADB folder for gpt, recovery and boot. These are backup files in case something goes wrong
20) In command, type "axon7tool -w recovery" - STUCK HERE - FAILED

kanej2006 said:
Not working, been trying for hours.
20) In command, type "axon7tool -w recovery" - STUCK HERE - FAILED
Click to expand...
Click to collapse
You're on nougat ? Look into about phone for that.
Afaik, you'll have to be on MM. So downgrade/rollback if on Nougat (look into DownloadCenter for B10 or B11) and do the procedure all over again.
Imo it's due to that.
edit: sure you have the recovery.img and bin in your adb folder ?

raystef66 said:
You're on nougat ? Afaik, you'll have to be on MM. So downgrade/rollback if on Nougat (look into DownloadCenter for B10 or B11) and do the procedure all over again.
Imo it's due to that.
edit: sure you have the recovery.img and bin in your adb folder ?
Click to expand...
Click to collapse
No, I am on stock MM.

kanej2006 said:
No, I am on stock MM.
Click to expand...
Click to collapse
Should work then.
Can you download recovery again. Check all characters if they're all written ok.
Sure the toolkit cannot bring enlightment too ?

Android 10 Beta T-Mobile Variant

I have tried twice on my OnePlus 6T T-Mobile variant to upgrade to the newest Open Beta. It runs the current open beta released in September just fine. But then when I do a local upgrade to the Android 10 open beta, right after it finishes installing and I press reboot, I get a message that says Build Version and HW version do not match and it ets stuck in a bootloop. To fix it, I have to use MSMDownloadTool to fix it. I have tried doing a local upgrade using a locked and unlocked bootloader and both lead to the same problem. Has anyone succesfully updated their TMo variant because i hate having to keep restoring my device?

I usually wait for a while until official Android 10 ROM for international OnePlus 6T version (and flash it via TWRP both times so I don't get any conflicts, with same copies of the OS across both slots), then I do whatever I want (I usually upgrade the bootloader and vendor this way so newer flavor of LineageOS 16 or later ROMs work best). I didn't run into hardware mismatch warning, yet I managed to successfully flash the successive OxygenOS updates meant for the international OnePlus 6T on my T-Mobile OnePlus 6T so far without seeing any UEFI bootloader warning at all. I had to be careful, I partly bricked my Google Pixel phone the last time (rendered Slot A completely unbootable by accident, so I had to figure out how to restore it the hard way, without the computer).
Sent from my OnePlus 6T using Tapatalk

bigmikey307 said:
I have tried twice on my OnePlus 6T T-Mobile variant to upgrade to the newest Open Beta. It runs the current open beta released in September just fine. But then when I do a local upgrade to the Android 10 open beta, right after it finishes installing and I press reboot, I get a message that says Build Version and HW version do not match and it ets stuck in a bootloop. To fix it, I have to use MSMDownloadTool to fix it. I have tried doing a local upgrade using a locked and unlocked bootloader and both lead to the same problem. Has anyone succesfully updated their TMo variant because i hate having to keep restoring my device?
Click to expand...
Click to collapse
Here is the solution for the moment.
I already installed it and everything works fine.
https://forum.xda-developers.com/showpost.php?p=80600661&postcount=52

ajnexus5 said:
Here is the solution for the moment.
I already installed it and everything works fine.
https://forum.xda-developers.com/showpost.php?p=80600661&postcount=52
Click to expand...
Click to collapse
I'm not interested in rooting my phone :silly: so is there any work around for unrooted users at the moment? Ty

Not yet. The fastboot ROM is pre-rooted, so there's no additional tinkering needed. Just flash the fastboot ROM and upon reboot, it's rooted. You can always jump back to the stable build when it's released next month if you'd like.

That file was deleted. Is there any other way to flash it?

jaceypoo said:
That file was deleted. Is there any other way to flash it?
Click to expand...
Click to collapse
Yes. Payload.bin decrypt and manual fastboot flash.

1-click T-mobile Android 10 for 6T:
https://drive.google.com/open?id=1jhGVmfC42UyVGDYUQhBFInjYUmZf4lxa

bradhoschar said:
Not yet. The fastboot ROM is pre-rooted, so there's no additional tinkering needed. Just flash the fastboot ROM and upon reboot, it's rooted. You can always jump back to the stable build when it's released next month if you'd like.
Click to expand...
Click to collapse
How is the Zip? I am new to the OnePlus forums do not see the least of two of 0 years ago I do so much trust that this would not happen as with P there were never problems with the V T which Vojo is some without root version?

Installed just fine, I love the new interface. BT isn't working for my Garmin watch. I guess I will have to wait for a full release for this to be fixed up.

Just a heads up to those who haven't made an actual phone call yet, Everyone I've spoken to has told me they can't hear me at all and that the quality comes out pretty garbled. Just something to look out for! If anyone has a fix for it please let us know!

chillaxnphilx said:
Just a heads up to those who haven't made an actual phone call yet, Everyone I've spoken to has told me they can't hear me at all and that the quality comes out pretty garbled. Just something to look out for! If anyone has a fix for it please let us know!
Click to expand...
Click to collapse
No issues on the T-mo fastboot ROM

Well, actually right now I cannot get into recovery. Says Qualcomm Dump. Questions? Should I try flashing TWRP?
---------- Post added at 01:06 PM ---------- Previous post was at 01:05 PM ----------
EspElement said:
Well, actually right now I cannot get into recovery. Says Qualcomm Dump. Questions? Should I try flashing TWRP?
Click to expand...
Click to collapse
I even tried to fastboot boot recovery.img
It didn't work, just sits at fastboot screen.

bradhoschar said:
No issues on the T-mo fastboot ROM
Click to expand...
Click to collapse
You haven't used the gyro, proximity sensor, specialized fonts, or emojis yet.
The OB1 creates a new partition called "reserve". This partition is not present on the Tmobile variants and its not created during install. There are issues with the Tmobile build, and its going to stay that way until an updated MSMtool comes out, Tmobile updates to A10, or some maniac actually goes through and fixes every single symlink that's broken.
OP ran out of space on system partition, so they're solution was to create a new partition and symlink everything from there to system.

hartleyshc said:
You haven't used the gyro, proximity sensor, specialized fonts, or emojis yet.
The OB1 creates a new partition called "reserve". This partition is not present on the Tmobile variants and its not created during install. There are issues with the Tmobile build, and its going to stay that way until an updated MSMtool comes out, Tmobile updates to A10, or some maniac actually goes through and fixes every single symlink that's broken.
OP ran out of space on system partition, so they're solution was to create a new partition and symlink everything from there to system.
Click to expand...
Click to collapse
Gyro and prox works for me.
Emojis work after magisk module flash.

chillaxnphilx said:
Just a heads up to those who haven't made an actual phone call yet, Everyone I've spoken to has told me they can't hear me at all and that the quality comes out pretty garbled. Just something to look out for! If anyone has a fix for it please let us know!
Click to expand...
Click to collapse
I have heard of this from multiuple people in the forums and it is also occuring with the Hydrogen Beta for Android 10. Thats where I first saw it. I dont know if my phone is affected.
hartleyshc said:
You haven't used the gyro, proximity sensor, specialized fonts, or emojis yet.
The OB1 creates a new partition called "reserve". This partition is not present on the Tmobile variants and its not created during install. There are issues with the Tmobile build, and its going to stay that way until an updated MSMtool comes out, Tmobile updates to A10, or some maniac actually goes through and fixes every single symlink that's broken.
OP ran out of space on system partition, so they're solution was to create a new partition and symlink everything from there to system.
Click to expand...
Click to collapse
Gyro and Prox are working fine for me. Dont know about fonts and emoji's as I dont use them. Everything "else" seems fine at this point.

Scott said:
I have heard of this from multiuple people in the forums and it is also occuring with the Hydrogen Beta for Android 10. Thats where I first saw it. I dont know if my phone is affected.
Patching the boot.img with magisk canary is somehow breaking the symlinks to reserve.img (possibly others). reserve.img is where the extra fonts, oneplus specific apks (like weather, launcher icons, etc) are stored. If you wanna check, flip your font to oneplus slate, if its in italics, its hosed. If your font is looking at special characters and your getting boxes with X's in them, your hosed.
only way to fix is a clean flash, and use magisk stable manager to patch your boot.img if your rooting.
Click to expand...
Click to collapse

aer0zer0 said:
Patching the boot.img with magisk canary is somehow breaking the symlinks to reserve.img (possibly others). reserve.img is where the extra fonts, oneplus specific apks (like weather, launcher icons, etc) are stored. If you wanna check, flip your font to oneplus slate, if its in italics, its hosed. If your font is looking at special characters and your getting boxes with X's in them, your hosed.
only way to fix is a clean flash, and use magisk stable manager to patch your boot.img if your rooting.
Click to expand...
Click to collapse
Ok, yeah, I do have the italic font. I thought that was just "new".
So basically, dont root it and it will be fine?

Scott said:
Ok, yeah, I do have the italic font. I thought that was just "new".
So basically, dont root it and it will be fine?
Click to expand...
Click to collapse
root your boot.img using magisk 20.0 stable.
but your going to need to reflash? are you tmob or stable?

bradhoschar said:
1-click T-mobile Android 10 for 6T:
https://drive.google.com/open?id=1jhGVmfC42UyVGDYUQhBFInjYUmZf4lxa
Click to expand...
Click to collapse
is this the pre rooted version
Sent from my ONEPLUS A6013 using Tapatalk

Patched 11.0.12.12.KB05AA ROM for rooted users - install from Fastbootd!!!

[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

Samsung T380 not rooting

Hi,
I have a SM-T380, and I tried to root it using magisk, It patched the boot.img file and I flashed it via odin, but for some odd reason when I open Magisk it says installed N/A.
I have the latest security patch (T380DXS4CUD3) (Android 9) and I already tried using the preserve AVB / preserve force encryption options.
I was wondering, there's no way to root this device on Android 9?I'm just trying out of fun since the tablet was laying around there.
any suggestions really appreciate it,

Waiting for someone to shed some light in to this matter. I tried all the possible procedure I found on google, but no luck.

Barto604 said:
Hi,
I have a SM-T380, and I tried to root it using magisk, It patched the boot.img file and I flashed it via odin, but for some odd reason when I open Magisk it says installed N/A.
I have the latest security patch (T380DXS4CUD3) (Android 9) and I already tried using the preserve AVB / preserve force encryption options.
I was wondering, there's no way to root this device on Android 9?I'm just trying out of fun since the tablet was laying around there.
any suggestions really appreciate it,
Click to expand...
Click to collapse
If your still interested in rooting this device go to @Austcool post it worked for me.
custom-sm-t380-sm-t385-boot
Edit: 2022 I have tested it it fully works as of this year!!!. 😁 disclaimer, I am in no way responsible for this kernel screwing up you tablet so use at your own risk. to flash it simply open up settings enable developer options and enable OEM...
forum.xda-developers.com

Barto604 said:
Hi,
I have a SM-T380, and I tried to root it using magisk, It patched the boot.img file and I flashed it via odin, but for some odd reason when I open Magisk it says installed N/A.
I have the latest security patch (T380DXS4CUD3) (Android 9) and I already tried using the preserve AVB / preserve force encryption options.
I was wondering, there's no way to root this device on Android 9?I'm just trying out of fun since the tablet was laying around there.
any suggestions really appreciate it,
Click to expand...
Click to collapse
Its Defex use my boot.img it's related to Samsungs new Defex anti root privileges security feature you must build the kernel from source; I already built Defex disabled kernel Prerooted with magisk.

Thank you, I already installed a Custom Rom ( I think it was made by you) using the January 2020 Security Patch, I think the latest software update is also a security patch so is redundant.
My question is, is it possible that you can provide me a .zip with the original Samsung Galaxy Boot Logo animations from this tablet? the Rom has custom ones and it didn't had a backup of the originals, I need the:
bootup.qmg
bootloop.qmg
shutdown.qmg
also if you have the original PowerOn.ogg and ShutDown.ogg I would really appreciate it. Thanks for replying this old threat it really means a lot.

Barto604 said:
Thank you, I already installed a Custom Rom ( I think it was made by you) using the January 2020 Security Patch, I think the latest software update is also a security patch so is redundant.
My question is, is it possible that you can provide me a .zip with the original Samsung Galaxy Boot Logo animations from this tablet? the Rom has custom ones and it didn't had a backup of the originals, I need the:
bootup.qmg
bootloop.qmg
shutdown.qmg
also if you have the original PowerOn.ogg and ShutDown.ogg I would really appreciate it. Thanks for replying this old threat it really means a lot.
Click to expand...
Click to collapse
Sure I'll pull them from my device on pie.

Austcool said:
Sure I'll pull them from my device on pie.
Click to expand...
Click to collapse
Barto604 said:
Thank you, I already installed a Custom Rom ( I think it was made by you) using the January 2020 Security Patch, I think the latest software update is also a security patch so is redundant.
My question is, is it possible that you can provide me a .zip with the original Samsung Galaxy Boot Logo animations from this tablet? the Rom has custom ones and it didn't had a backup of the originals, I need the:
bootup.qmg
bootloop.qmg
shutdown.qmg
also if you have the original PowerOn.ogg and ShutDown.ogg I would really appreciate it. Thanks for replying this old threat it really means a lot.
Click to expand...
Click to collapse
Was this my Oreo rom I cannot seem to find the download for it do you mind sharing the download link I was trying to grab some files from the old Oreo rom but I couldn't find it. Also I can get you the pie copys of the bootup.qmg and the bootloop.qmg shutdown.qmg but the files called PowerOn.ogg and ShutDown.ogg don't exist by default on the SM-T380 they are custom added by me you can ether add your own bootsounds files or remove them to boot without a poweron/shutdown sound.

Austcool said:
Was this my Oreo rom I cannot seem to find the download for it do you mind sharing the download link I was trying to grab some files from the old Oreo rom but I couldn't find it. Also I can get you the pie copys of the bootup.qmg and the bootloop.qmg shutdown.qmg but the files called PowerOn.ogg and ShutDown.ogg don't exist by default on the SM-T380 they are custom added by me you can ether add your own bootsounds files or remove them to boot without a poweron/shutdown sound.
Click to expand...
Click to collapse

Thank you so much!!!

And sorry it wasn't your build it was zfk110's build https://forum.xda-developers.com/t/...android-9-bloatware-free-twrp-backup.4243589/

Barto604 said:
Hi,
I have a SM-T380, and I tried to root it using magisk, It patched the boot.img file and I flashed it via odin, but for some odd reason when I open Magisk it says installed N/A.
I have the latest security patch (T380DXS4CUD3) (Android 9) and I already tried using the preserve AVB / preserve force encryption options.
I was wondering, there's no way to root this device on Android 9?I'm just trying out of fun since the tablet was laying around there.
any suggestions really appreciate it,
Click to expand...
Click to collapse
I want to piggyback off of this thread because I'm experiencing the same problem...if anyone can help by giving a step-by-step instruction as to what worked that would be most appreciated
allanseth23 wrote that "this worked," but what did? You follow that link and there are six files, I tried it out and the following screens which I've never seen before showed up (see attached images)
I'm not new to this and I've rooted a wide variety of devices (including using firehose/engineering mode) so I'm really having some trouble understanding why rooting this ancient device five years after its release and almost a year past it's final update is so difficult
if someone can be so kind as to write a step by step "step one, load this via odin (file attached); step two load this via twrp (file attached)" that would be great because the information for this device is scattered across tens of pages and the posts are incomplete (they mention it's for Pie but don't mention on which build they were successful) - no one has collated all of this info to say what works and it would help lots of people, not just myself
I think that's the most frustrating part, the piecemeal information from posters regarding this device--I don't think I've ever waded in an XDA thread that was this broken before (it also doesn't help that all the Tab A models are pushed together into one subforum).
To be clear I'm running the very last software update for this device (AP T380DXS4CUD3) for SM-T380, device is OEM unlocked.
I just want the version rooted, I don't need any TWRP backups that contain additional mods.
Thanks to anyone that can help

cliffswallow said:
I want to piggyback off of this thread because I'm experiencing the same problem...if anyone can help by giving a step-by-step instruction as to what worked that would be most appreciated
allanseth23 wrote that "this worked," but what did? You follow that link and there are six files, I tried it out and the following screens which I've never seen before showed up (see attached images)
I'm not new to this and I've rooted a wide variety of devices (including using firehose/engineering mode) so I'm really having some trouble understanding why rooting this ancient device five years after its release and almost a year past it's final update is so difficult
if someone can be so kind as to write a step by step "step one, load this via odin (file attached); step two load this via twrp (file attached)" that would be great because the information for this device is scattered across tens of pages and the posts are incomplete (they mention it's for Pie but don't mention on which build they were successful) - no one has collated all of this info to say what works and it would help lots of people, not just myself
I think that's the most frustrating part, the piecemeal information from posters regarding this device--I don't think I've ever waded in an XDA thread that was this broken before (it also doesn't help that all the Tab A models are pushed together into one subforum).
To be clear I'm running the very last software update for this device (AP T380DXS4CUD3) for SM-T380, device is OEM unlocked.
I just want the version rooted, I don't need any TWRP backups that contain additional mods.
Thanks to anyone that can help
Click to expand...
Click to collapse
I am piggy backing too because you are someone recently (last week) were messing with this thing too...
I was given a SM-T380 and am trying to make it "useful"
So far I have had fine luck with both oreo and pie (using the build you mentioned T380DXS4CUD3 via twrp restore... and it is fine, but seems slower than I recalled 8.1 being...
Anyway, I have been flashing the v19.0 of magisk (and a v7.1 of magisk manager) and then flashed v21.4 (and v8.x of manager).
Anyway, if you install a newer magisk manager it will show the device as unrooted (N/A) but updating further seems like I would need to extract the boot.img from the twrp backup (which is above my head...) and patch it with newer magisk...
I am not sure that it's needed for what I will be using the tablet for.. but I haven't had luck with safetynet (using magiskhide props) so I am looking into other methods.
Anyway, I'm not sure if I sould go back to oreo 8.1 or not just because pie 9 seems sluggish in comparison..
Anyway, I am going to tinker with it in my spare time over the next few days, so if you want to connect about anything particular I am around.
-g

cliffswallow said:
I want to piggyback off of this thread because I'm experiencing the same problem...if anyone can help by giving a step-by-step instruction as to what worked that would be most appreciated
allanseth23 wrote that "this worked," but what did? You follow that link and there are six files, I tried it out and the following screens which I've never seen before showed up (see attached images)
I'm not new to this and I've rooted a wide variety of devices (including using firehose/engineering mode) so I'm really having some trouble understanding why rooting this ancient device five years after its release and almost a year past it's final update is so difficult
if someone can be so kind as to write a step by step "step one, load this via odin (file attached); step two load this via twrp (file attached)" that would be great because the information for this device is scattered across tens of pages and the posts are incomplete (they mention it's for Pie but don't mention on which build they were successful) - no one has collated all of this info to say what works and it would help lots of people, not just myself
I think that's the most frustrating part, the piecemeal information from posters regarding this device--I don't think I've ever waded in an XDA thread that was this broken before (it also doesn't help that all the Tab A models are pushed together into one subforum).
To be clear I'm running the very last software update for this device (AP T380DXS4CUD3) for SM-T380, device is OEM unlocked.
I just want the version rooted, I don't need any TWRP backups that contain additional mods.
Thanks to anyone that can help
Click to expand...
Click to collapse
I root mine by just loading pie.tar from @Austcool post on odin. We have the same build no.