Related
Edit: Solution found look below!!!
As I posted in a different thread:
I managed to do it, but it was hackish
How I did it:
Used a terminal directly on the tablet, no adb.
I installed the acer chinese update. I 'dd'ed my old system and flexrom and rebooted. After that I checked for updates, and as luck had it, there was one. I tried it, but it failed half way through the procedure.
I rebooted again, then I 'dd'ed a boot.img on mmcblk0p2 from a 1.016 that matched my original system.img and flexrom.img. WITHOUT REBOOTING (I tried that before, it gives a bad kernel checksum and stops, but I assumed on update it would just patch if the file corresponds and re-sign), I then proceeded to do the update. It rebooted, entered recovery, and lo and behold, IT WORKED! So I'm 100% back to stock.
I would imagine that the same procedure would work when manually updating through recovery (using an extracted update.zip).
I used the kernel from here:
http://forum.xda-developers.com/showpost.php?p=14033507&postcount=27
EDIT: The kernel is stock for ACER_A500_1.016.05_COM_GEN1
Take a look at the thread linked below, get the 1.016.05_COM_GEN1 files (system, flexrom, and boot). If you are not offered an online update (System>About>Check for updates), you need the official update.zip from Acer. Extract the update.zip from the official Acer update THAT MATCHES YOUR FLEX VERSION using the XOR 12 method (see here - http://forum.xda-developers.com/showthread.php?t=1065360&page=20 - note in that post the link is for 03_COM_GEN1, NOT 05_COM_GEN1. For 04_COM_GEN1 and 05_COM_GEN1 see here - http://forum.xda-developers.com/showpost.php?p=14052165&postcount=184. For 03 and 04 you will need to find system.img, flexrom.img and boot.img, for 05 they are linked in the thread below).
EDIT: The thread with the images for ACER_A500_1.016.05_COM_GEN1 is here:
http://forum.xda-developers.com/showthread.php?t=1086785
EDIT: You might pull this off for other flex versions as well, but you would need all the files (system.img, flexrom.img, boot.img AND update.zip) from those versions.
PLEASE NOTE THAT THIS ONLY WORKS IF YOU HAVE THE OFFICIAL UPDATE.ZIP FOR YOUR SPECIFIC FLEX VERSION
Wow, I was about to try that!!!
I'll do that now and see how it goes.
Thanks mate!
EDIT: Worked!
I would expect that the reason an update fails on the Chinese one is that it tries to patch the kernel (which is different from the one expected). The update is a bunch of diffs and patches, and almost no full files, so it cannot be applied over anything but the right files.
Yes that is true. The old kermel checksum check was failing.
huxflux2003 said:
EDIT: Worked!
Click to expand...
Click to collapse
Glad to hear it Take that, you sneaky Acer bastards!
adancau said:
As I posted in a different thread:
I managed to do it though, but it was hackish
How I did it:
Used a terminal directly on the tablet, no adb.
I installed the acer chinese update. I 'dd'ed my old system and flexrom and rebooted. After that I checked for updates, and as luck had it, there was one. I tried it, but it failed half way through the procedure.
I rebooted again, then I 'dd'ed a boot.img on mmcblk0p2 from a 1.016 that matched my original system.img and flexrom.img. WITHOUT REBOOTING (I tried that before, it gives a bad kernel checksum and stops, but I assumed on update it would just patch if the file corresponds and re-sign), I then proceeded to do the update. It rebooted, entered recovery, and lo and behold, IT WORKED! So I'm 100% back to stock.
I would imagine that the same procedure would work when manually updating through recovery (using an extracted update.zip).
I used the kernel from here:
http://forum.xda-developers.com/showpost.php?p=14033507&postcount=27
Take a look at the thread, get the 1.016 files, system, flexrom, and boot, and try it.
Click to expand...
Click to collapse
Ahhhh a true milestone, well done.........
Nice work! Two questions:
Does the update work in the US?
I assume gingerbreak still works after the OTA update?
Thx
gingerbreak works
_motley said:
Does the update work in the US?
I assume gingerbreak still works after the OTA update?
Click to expand...
Click to collapse
A warning first: You DO NOT need to do this if you haven't installed the chinese update.zip (update.acer.zip) before, as that is the only one that changes kernels. Also, if you have anything other than ACER_A500_1.016.05_COM_GEN1, it's debatable if you want to do this (if you do read below), it might be better to wait for an official update.
The kernel above is stock for ACER_A500_1.016.05_COM_GEN1
So it works if you have ACER_A500_1.016.05_COM_GEN1 images, or are ok with changing your flex to that (in which case you would need to flash a system.img and a flexrom.img for ACER_A500_1.016.05_COM_GEN1, reboot, and then flash the kernel from the post above before heading off to recovery and updating - HOWEVER as far as I know no one has tried this, though IN THEORY it should work).
Gingerbreak still works, you can get root back after updating.
Just so I'm clear...
I'm at version 1.139.05 but I got here via the Chinese update.zip.
What do I need to do to get back to stock? Do I need to go back to my old system image and flexrom plus a new kernel?
Could someone post clearer instructions?
Thanks
adancau said:
A warning first: You DO NOT need to do this if you haven't installed the chinese update.zip (update.acer.zip) before, as that is the only one that changes kernels. Also, if you have anything other than ACER_A500_1.016.05_COM_GEN1, it's debatable if you want to do this (if you do read below), it might be better to wait for an official update.
The kernel above is stock for ACER_A500_1.016.05_COM_GEN1
So it works if you have ACER_A500_1.016.05_COM_GEN1 images, or are ok with changing your flex to that (in which case you would need to flash a system.img and a flexrom.img for ACER_A500_1.016.05_COM_GEN1, reboot, and then flash the kernel from the post above before heading off to recovery and updating - HOWEVER as far as I know no one has tried this, though IN THEORY it should work).
Gingerbreak still works, you can get root back after updating.
Click to expand...
Click to collapse
Thanks guys, I did restore using the Chinese update.zip last week and I am currently sitting at kernel 2.6.36.3 with flashed system img=Acer_A500_1.104.05_COM_GEN1, but with recovered Chinese kernel modules for wifi etc. I also flashed a flexrom.img from this build as well. I didn't flash the boot.img from this build, but was thinking about it until huxflux2003 reported the check-sum failure.
So, I am trying to decide what I am going to do. It sounds easy enough to get back to stock now, but I may wait for the official update next month that has 3.1. At this point, I suppose we are assuming that it will be a full update.zip that will work on any tablet (god I hope so). It's about time they gave us a full recovery image...I will be beyond disappointed if they don't. Let's also just hope we can still gain root easily after this.
One more question, if I use all the images from ACER_A500_1.016.05_COM_GEN1 that were posted, does this have to match what I had originally had in any shape or form? It sounds like since all the pieces are from the same build, everything will be fine regardless of what you had to begin with. Is this right?
Thx
To your last question - Theoretically yes, it should work, and I guess you don't need to match what you originally had. I can only speculate, logically though it would makes sense. You definitely need all the images to be from the same build (system+flexrom+boot.img). You also need the official update for that build.
heyoh said:
Just so I'm clear...
I'm at version 1.139.05 but I got here via the Chinese update.zip.
What do I need to do to get back to stock? Do I need to go back to my old system image and flexrom plus a new kernel?
Could someone post clearer instructions?
Thanks
Click to expand...
Click to collapse
To get back to stock you need the three images for your build - system, flexrom, and boot. If there is no online update available, you also need the update.zip for that build (extracted from an official acer update using the XOR 12 method - do a search).
Alternatively, I suppose you could switch to a new build for which you could find all the necessary files (but it hasn't been tried).
Flash system.img using dd. You might need to re-root. Reboot, flash flexrom.img. Reboot once more. Make sure your wifi works (you might need different kernel modules).
Look to see if there is an online update (Settings > About > Check for updates). If there is, cancel it. Flash boot.img on mmcblk0p2. DO NOT REBOOT.
If there was an online update available, now it's the time to perform it. After it's done you will get you back to stock 1.139.05.
If there isn't any update, make sure you have the update.zip on the root of your microSD. Turn off the tablet, then turn it back on holding the volume key closest to the power button. Do not let go of that button until you see some text in the corner. At that moment the update would begin. Once rebooted you will be back to stock.
Hope I've explained it better this time, and it works ok for you. If not, you need to go through the chinese update again. Good luck.
adancau said:
To your last question - Theoretically yes, it should work, and I guess you don't need to match what you originally had. I can only speculate, logically though it would makes sense. You definitely need all the images to be from the same build (system+flexrom+boot.img). You also need the official update for that build.
Click to expand...
Click to collapse
It worked for me too! Thanks again for the tip. I am now at the latest build and ahead of the US update schedule from what I can gather
It asked me to update after I flashed the ACER_A500_1.016.05_COM_GEN1 build system.img and flexrom.img. Even from the US it prompted just fine since I was on ACER_A500_1.016.05_COM_GEN1 build and not ACER_A500_1.104.05_COM_GEN1 as the former is what the differential patch targets.
I cancelled the update once I saw it presented and then blew on the boot.img from the ACER_A500_1.016.05_COM_GEN1 build. Then, without rebooting, I downloaded and applied the update (but with a little hiccup, see below). Now I am at Acer_A500_1.139.05_COM_GEN1 and didn't lose any user apps or settings etc.
Had a scary point though that I will share as it may help others. The first time I tried, the zip wouldn't downloadload and I was getting an HTTP 403 error. I cleared the systemupdater app and FWUpdateService data. I also killed the services and then I was stuck. Instead of conceding to reflashing the Chinese update.zip and starting over, I unzipped the Chinese update.zip and grabbed the boot.img from it. I then dd'ed that image back to the boot partition and rebooted again. It came back up and I this time I was able to do the system update successfully. Whew!
Followed instructions by OP and it worked perfectly! Back to stock and updated.
I think I'll be keeping these system images for next time I brick and have to flash the Chinese update.
Any chance of someone uploading the extracted update.zip for the new Acer_A500_1.139.05_COM_GEN1 so I can update manually using this method.
Thanks in advance
I used the above method to update to 1.139.04 from 1.016.04.
However my kernel is still 2.6.36.3-00001-gf991e5d instead of the 2.6.36.3 everyone else is reporting?
tianqi said:
I used the above method to update to 1.139.04 from 1.016.04.
However my kernel is still 2.6.36.3-00001-gf991e5d instead of the 2.6.36.3 everyone else is reporting?
Click to expand...
Click to collapse
If you directly flashed a 1.139.04 image your kernel has not been updated. You had to flash a 1.016.04 image, flexrom and boot, and then run the update.
You MIGHT have some luck regardless by running the update.zip now (I used it on mine one time when I updated like you did, and it seemed to work, but I have not noticed the kernel number). Be prepared to have to reflash if something goes wrong though.
I did reflash system, flexrom, and boot from 1.016.04...
Second time is still the same...
Kernel is still 2.6.36.3-00001-gf991e5d...
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.
Went to update "YB1-X90L_170420" and as I have been normally doing I removed root, ran the update, and all was well. It installed fine and worked no problem.
I was then prompted for update "YB1-X90F_USR_S000408_1704201342_WW06_BP_ROW_TO_YB1_X90F_USR_S000426_1705080316_WW06_BP_ROW" So I started the download and when the device reboots it then fails with this string, note the error about the "build fingerprint"
Supported API: 3
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Package expects build fingerprint of Lenovo/yeti_10_row_wifi/yeti:6.0.1/MMB29M/LenovoYB1-X90F_S000408_170420:user/release-keys or Lenovo/yeti_10_row_wifi/yeti:6.0.1/MMB29M/LenovoYB1-X90F_S000426_170508:user/release-keys; this device has Lenovo/yeti_10_row
E:Error in @/cache/recovery/block.map
(Status 7)
Installation aborted.
I foolishly after some googling and not finding enough info opened a chat with Lenovo. The rep asked what the error was and once I showed it said that was just related to my fingerprint scanner .... really?!?!? I knew the chat was a dead spot at this point but tried to state this device has no fingerprint reader, etc.. and so on. Hope they could really tell me what the error was. Anyway the rep told me to 'ignore' the update and just carry on since my device is actually working. They then went on to state they are hardware only on the chat session, which the Lenovo site says nothing about that. They then also told me to take this up with Google as they make Android not Lenovo. So much for warranty helping anything but possibly replacing a physically broken device. Their techs are useless, seriously.
So anywho, as you see in the error the update is trying to apply but looks for "Lenovo/yeti_10_row_wifi" and is finding somewhere (in the update or my device?) "Lenovo/yeti_10_row", notice the missing "wifi" on the end of that. My 'build.prop' and other system files are untouched. I even tried resetting the device. Which after the reset I was able to once again install the "YB1-X90L_170420" update but this next update "YB1-X90F_USR_S000408_1704201342_WW06_BP_ROW_TO_YB1_X90F_USR_S000426_1705080316_WW06_BP_ROW" fails again on that same fingerprint mismatch.
Any clue what I should be looking for here? Has anyone else installed that update successfully?
Will anyone here supply me with the original (or as close as original) clean stock ROM without paying for it? I know I should have backed up with TWRP before I started doing updates, and this may well be my issue, but I didn't and not I can only restore back to an already rooted backup. Though I assume doing a reset of that rooted restore is considered clean (no root or 3rd party anything)?
thanks for any help or ideas!
MarkAllen said:
Went to update "YB1-X90L_170420" and as I have been normally doing I removed root, ran the update, and all was well. It installed fine and worked no problem.
I was then prompted for update "YB1-X90F_USR_S000408_1704201342_WW06_BP_ROW_TO_YB1_X90F_USR_S000426_1705080316_WW06_BP_ROW" So I started the download and it the device reboots then fails with this string, note the error about the "build fingerprint"
Supported API: 3
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Package expects build fingerprint of Lenovo/yeti_10_row_wifi/yeti:6.0.1/MMB29M/LenovoYB1-X90F_S000408_170420:user/release-keys or Lenovo/yeti_10_row_wifi/yeti:6.0.1/MMB29M/LenovoYB1-X90F_S000426_170508:user/release-keys; this device has Lenovo/yeti_10_row
E:Error in @/cache/recovery/block.map
(Status 7)
Installation aborted.
I foolishly after some googling and not finding enough info opened a chat with Lenovo. The rep asked what the error was and once I showed it said that was just related to my fingerprint scanner .... really?!?!? I knew the chat was a dead spot at this point but tried to state this device has no fingerprint reader, etc.. and so on. Hope they could really tell me what the error was. Anyway the rep told me to 'ignore' the update and just carry on since my device is actually working. They then went on to state they are hardware only on the chat session, which the Lenovo site says nothing about that. They then also told me to take this up with Google as they make Android not Lenovo. So much for warranty helping anything but possibly replacing a physically broken device. Their techs are useless, seriously.
So anywho, as you see in the error the update is trying to apply but looks for "Lenovo/yeti_10_row_wifi" and is finding somewhere (in the update or my device?) "Lenovo/yeti_10_row", notice the missing "wifi" on the end of that. My 'build.prop' and other system files are untouched. I even tried resetting the device. Which after the reset I was able to once again install the "YB1-X90L_170420" update but this next update "YB1-X90F_USR_S000408_1704201342_WW06_BP_ROW_TO_YB1_X90F_USR_S000426_1705080316_WW06_BP_ROW" fails again on that same fingerprint mismatch.
Any clue what I should be looking for here? Has anyone else installed that update successfully?
Will anyone here supply me with the original (or as close as original) clean stock ROM without paying for it? I know I should have backed up with TWRP before I started doing updates, and this may well be my issue, but I didn't and not I can only restore back to an already rooted backup. Though I assume doing a reset of that rooted restore is considered clean (no root or 3rd party anything)?
thanks for any help or ideas!
Click to expand...
Click to collapse
From what i recall the fingerprint is what is shown in the buildprop. You could try editing this but i would tread carefully if its just a minor update as it may justmess up your system if there are other mismatches during the update process.
Lenovo technical support is a complete joke, you get much better help here. Lol
Sent from my F5121 using Tapatalk
Nope every line of my build.prop, where listed, has the proper "Lenovo/yeti_10_row_wifi" that the update claims is wrong. I personally think it is this update itself but no confirmation from other users if the update
"YB1-X90F_USR_S000408_1704201342_WW06_BP_ROW_TO_YB1_X90 F_USR_S000426_1705080316_WW06_BP_ROW"
has installed for them yet.
And I certainly knew how far I was *not* going to get with Lenovo but figured it couldn't hurt. I was really trying to get a stock ROM download from them or anywhere. I would love to just revert this to how it was out of the box and start over.
Well for reference I think I finally realize what is causing this (unconfirmed, but sounds feasible).
I did at one time try the "YB1-X90L_USR_S000155_1609272258_WW06_BP_ROW" noted in another thread here from Easy firmware. I figured since it was a free download and others have done it, what could it hurt? lol (I think I know now). Anyway I forget what it was at the time but something with that rom just wasn't right for me and I decided to restore back to my TWRP backup I had made. I'm assuming my backup doesn't overwrite something that "L" version rom did and leaves some residue that reports itself as the "L" model now?
Anyway that is the only thing to me that makes sense to me that could be happening. Of course I have no original stock rom with IMG files to flash again to fix this. :/
Can anyone here confirm Easy Firmware is safe to use? Can anyone confirm their YB1-X90F rom is really that models rom?
MarkAllen said:
Well for reference I think I finally realize what is causing this (unconfirmed, but sounds feasible).
I did at one time try the "YB1-X90L_USR_S000155_1609272258_WW06_BP_ROW" noted in another thread here from Easy firmware. I figured since it was a free download and others have done it, what could it hurt? lol (I think I know now). Anyway I forget what it was at the time but something with that rom just wasn't right for me and I decided to restore back to my TWRP backup I had made. I'm assuming my backup doesn't overwrite something that "L" version rom did and leaves some residue that reports itself as the "L" model now?
Anyway that is the only thing to me that makes sense to me that could be happening. Of course I have no original stock rom with IMG files to flash again to fix this. :/
Can anyone here confirm Easy Firmware is safe to use? Can anyone confirm their YB1-X90F rom is really that models rom?
Click to expand...
Click to collapse
Hi,
I registered for the free account. Had to email there support team to get it activate as there were problems their end. The 90F firmwares were not in the free tier so I paid the $15 through paypal to be safe, and got the 90F firmware fine. It was old and I had to run a lot of updates to get it up to date. But it got everything back to how it should be.
I blame Lenovo that we have to jump through theese hoops, but the files are legit.
Broomfundel said:
Hi,
I registered for the free account. Had to email there support team to get it activate as there were problems their end. The 90F firmwares were not in the free tier so I paid the $15 through paypal to be safe, and got the 90F firmware fine. It was old and I had to run a lot of updates to get it up to date. But it got everything back to how it should be.
I blame Lenovo that we have to jump through theese hoops, but the files are legit.
Click to expand...
Click to collapse
Thanks for that confirmation! I did end up getting a registered account ($15) used Paypal and all looked good. I ended up downloading two versions of firmware. Initially I thought I would start with the oldest knowing many updates awaited but really wanted to be sure in erasing all my previous steps just in case it didn't work or the same thing happened again.
Used "YB1-X90F_USR_S000036_1607280616_WW6_BP_ROW-flashfiles.zip" from Easy Firmware. I opted to follow the included "installer.cmd" but did not do the "unlock" or "lock" as I already was unlocked of course and did not want to lock it again. When it completed I first noted my Halo keyboard not working and things were in Chinese here and there. This post resolved both items (thanks vimalbhimani!). Pretty sure that was because I formatted all the various partitions including "country", duh. Sadly however this version was showing no further OTA updates were available at all. Maybe Lenovo has deleted some of the really old OTA downloads and they are no longer available? Not sure.
I then installed the most recent rom "YB1-X90F_USR_S000196_1611040312_WW06_BP_ROW-flashfiles.zip". This time I did not format and only flashed this newer roms boot, bootloader, factory, recovery, and system images. After the system was backup everything was in great shape and updates were available. I made a TWRP backup straight away. Then I let the first and second updates listed below download and install via OTA and had no issues. The final two I opted to save time and installed using the standard recovery from my SD card after I downloaded them from my PC. Here are direct links to those if anyone wants them and they are in order of install (descending) based on already having "YB1-X90F_USR_S000196_161104"
http://tabdl.ota.lenovomm.com/dls/v...S000239_1612091428_WW06_BP_ROW_WCAC703BC6.zip
http://tabdl.ota.lenovomm.com/dls/v...S000340_1702251540_WW06_BP_ROW_WC365253B3.zip
http://tabdl.ota.lenovomm.com/dls/v6/YB1-X90F_170420_WC76FD00EF.zip
http://tabdl.ota.lenovomm.com/dls/v...S000426_1705080316_WW06_BP_ROW_WC80C2A0F2.zip (this is the failed update that incited this thread)
All updates went great and all is well at this point. Made another TWRP backup and I plan to root again now and see if any upcoming updates later have some issue?
I just wanted to report back here if anyone was interested that I unrooted, updated the June OTA update, and was able to root again without issue.
i got the same error message and now i'm stuck. I cant install any updates and so i bought a account from easy-firmware to get the firmware ... the firmware: YB1-X90F_USR_S000036_1607280616_WW6_BP_ROW-flashfiles.zip
doesnt not work with twrp or the stock recovery... it tells me "zip file is corupt"
@MarkAllen: Can you provide a guide how you got back to the stock rom? just flashing the zips doesnt work....
i really need help...
FreddeHamm said:
i got the same error message and now i'm stuck. I cant install any updates and so i bought a account from easy-firmware to get the firmware ... the firmware: YB1-X90F_USR_S000036_1607280616_WW6_BP_ROW-flashfiles.zip
doesnt not work with twrp or the stock recovery... it tells me "zip file is corupt"
@MarkAllen: Can you provide a guide how you got back to the stock rom? just flashing the zips doesnt work....
i really need help...
Click to expand...
Click to collapse
You cannot flash the ZIP file with TWRP or stock recovery. You have to unzip the file and then flash each IMG file that you need manually while in fastboot mode (there are seven of them).
**** IF YOU FOLLOW THESE DIRECTIONS IT IS NO ONES FAULT BUT YOUR OWN IF IT SCREWS UP SOMETHING!!! ****
**** WILL TRY TO HELP PROVIDE INFO IF I CAN BUT CANNOT GUARANTEE ANYTHING. ALSO THIS ERASE ALL YOUR DATA ****
First be aware as noted in the previous post above that I tried using "YB1-X90F_USR_S000036_1607280616_WW6_BP_ROW-flashfiles.zip" intially and it worked fine to get me back up and running but once I was done no new OTA updates were showing at all. No clue why so I ended up doing it again but used the ROM named "YB1-X90F_USR_S000196_1611040312_WW06_BP_ROW-flashfiles.zip". Also note I had erased my "country" partition and flashed "country.img" which requires the info posted by vimalbhimani again linked above in my previous post. It has to be used to correct for your country, no biggie at all and worked fine for myself.
1) Unzip the ROM you downloaded to a folder on your PC
2) From command prompt go to that folder
3) Make sure from the command prompt that ADB and fastboot commands are working properly
4) Put your tablet in fastboot mode ("adb reboot bootloader")
(these next commands are directly from the "install.cmd" included with the ROM from EasyFW, I just opted to run them manually one at a time in order and I omitted the unlock and lock commands)
fastboot flash gpt gpt.bin
fastboot erase misc
fastboot erase persistent
fastboot erase frp
fastboot erase metadata
fastboot format config
fastboot format country
fastboot format cache
fastboot format data
fastboot format factory
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash config config.img
fastboot flash country country.img
fastboot flash system system.img
fastboot flash bootloader bootloader
fastboot flash oemvars bootloader_policy-oemvars.txt
fastboot continue
That's it. Minus the Intel error code 03 for being unlocked, it should be a normal out of the box setup when it boots back up into Android.
good luck!
People that are looking for the YB1-X90F_USR_S000196_1611040312_WW06_BP_ROW-flashfiles.zip may want to take a look at this post.
In contrast to my experiences with devices made by other OEMs, it seems like the files can directly be used for downgrading the Yoga Book if you're currently using a newer version.
Moved...
[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
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.