Related
OK...I have/had an stock nexus 7 running 4.4.2....until it decided to stop working last night. It was stuck on boot loop. So I decided to try a few things. I tried skipsoft toolkit and I followed a few instructions that other people said worked for them. To make a long story short, things went wrong. Im not sure how but they did. I'm not super knowledgeable about all this but I'd say I know a good amount. I rooted my OG Droid and have my GS3 rooted so I'm not completely in the dark about this but I feel like a idiot at this point. In the skipsoft menu/"command prompt", i was able to get TWRP working through skipsoft but it says I dont have a OS loaded. So apparently I erased everything and Im not sure how to get it back. I've been trying to load a boot img on it but its not letting me. Im lost and would love some help. Here is the screen on my next and also what Im getting on the step of "writing radio" in skipsoft. Anybody know anything about this? Where do I need to go from here? Thanks so much!
Topdroid01 said:
OK...I have/had an stock nexus 7 running 4.4.2....until it decided to stop working last night. It was stuck on boot loop. So I decided to try a few things. I tried skipsoft toolkit and I followed a few instructions that other people said worked for them. To make a long story short, things went wrong. Im not sure how but they did. I'm not super knowledgeable about all this but I'd say I know a good amount. I rooted my OG Droid and have my GS3 rooted so I'm not completely in the dark about this but I feel like a idiot at this point. In the skipsoft menu/"command prompt", i was able to get TWRP working through skipsoft but it says I dont have a OS loaded. So apparently I erased everything and Im not sure how to get it back. I've been trying to load a boot img on it but its not letting me. Im lost and would love some help. Here is the screen on my next and also what Im getting on the step of "writing radio" in skipsoft. Anybody know anything about this? Where do I need to go from here? Thanks so much!
Click to expand...
Click to collapse
Hi, Topdroid01...
Looking at your first screenshot, where it says (amongst other things)....
Code:
.....
BASEBAND VERSION = N/A
.....
Or in other words, your Nexus 7 is WiFi only, and has no 'radio' 3G/GSM component.
...which may explain this 'FAILED' error message, in your second screenshot...
Code:
sending 'radio' (16384 KB )...
OKAY [ 1.983s]
writing 'radio'...
FAILED (remote: (BadParameter))
finished. total time: 2.005s
You can not flash a 'radio' baseband component to a device that doesn't support it.
Without more details, I suspect your skipsoft toolkit is attempting to flash the 'Nakasig' (WiFi/3G/GSM/mobile) factory image... instead of the correct 'Nakasi' factory image, for a WiFi only device.
You can download either from here.
So I strongly suspect, given the 'BASEBAND VERSION = N/A' reference in your first screenshot, that you have a WiFi only 'grouper' Nexus 7, and accordingly you need the 'Nakasi' factory image.
Hope this makes sense.
Rgrds,
Ged.
GedBlake said:
Hi, Topdroid01...
Looking at your first screenshot, where it says (amongst other things)....
Code:
.....
BASEBAND VERSION = N/A
.....
Or in other words, your Nexus 7 is WiFi only, and has no 'radio' 3G/GSM component.
...which may explain this 'FAILED' error message, in your second screenshot...
Code:
sending 'radio' (16384 KB )...
OKAY [ 1.983s]
writing 'radio'...
FAILED (remote: (BadParameter))
finished. total time: 2.005s
You can not flash a 'radio' baseband component to a device that doesn't support it.
Without more details, I suspect your skipsoft toolkit is attempting to flash the 'Nakasig' (WiFi/3G/GSM/mobile) factory image... instead of the correct 'Nakasi' factory image, for a WiFi only device.
You can download either from here.
So I strongly suspect, given the 'BASEBAND VERSION = N/A' reference in your first screenshot, that you have a WiFi only 'grouper' Nexus 7, and accordingly you need the 'Nakasi' factory image.
Hope this makes sense.
Rgrds,
Ged.
Click to expand...
Click to collapse
Thanks for getting back to me so quick! As for the skipsoft toolkit, I think Im using the correct version. Ive went back and checked a few times but Ill triple check when I get home. I do have a wifi only version btw...so Ill go home and give your advice a try. It makes a lot of sense. Ill get back to you and let you know. Thank you so much!
CAUTION TO NOT LOOSE TWRP
I read two posts that say v21, now again on V8.5, put the stock recovery back instead of twrp. This is probably a side effect of a fresh stock /system and wipe of /data.
As a preventive step, when done flashing and wiping reboot to recovery FIRST, before booting the system It will allow recovery to handle removing the recovery-from-boot.p that flashes stock recovery.
I just patched the modified V7.4.2 up to the newly released 8.3 now 8.4. 8.5, 8.7,9.0 -V9.2 Patch
New update has been made from V17 to V21 of the non prime version of R1-HD, Non prime is behind on security patch (2017-05-05)
Copied ROM from phone and made twrp install ROM from it.
* No preloader change (official updates change the preloader to block your ability to use sp flash tools for rom flashing)
* No lk.bin change __ this part is what allows you to choose boot options(boot menu when power and volume pressed together)
* No "FOTA" app Fota has now been left in to make it easier to get next update, if that ever happens.
* No opera browser
* No adds (removed in the modified 7.4.2)
* Custom boot logo (only done on v8.3, there was no interest in this so abandoned)
--Newer versions of rom left stock, Leaving mods up to user.
** while it is not necessary to do a wipe with this ROM, I still recommend it.
**Thanks:
** @vampirefo needed his patched v7.4.2 in order to apply this new 8.3 patch and again for 8.4
** @ColtonDRG OR @jasonmerc I do not remember which one made it: For the image used in the custom logo
and the modified zip is here .
Roms are rootable with SuperSU, flashed in twrp after install. Must be done in systemless mode. In order to patch system veridy in boot.img
Logo update did not work on original rom changing link to updated version
BLU rolled v8.3 back to v7.4.2 because of app compatability issues. V8.4 is there fixed release. Both 8.3 and 8.4 are modified prime roms with ads stripped
V21 is the non prime update.
Unmodified V6.1
==>NON-ROOTED-logo-not-replaced-modified-V8.3
==>Fixed Logo modified NON_ROOTED V8.3
==>>modified V8.4
==>>modified V8.5
==>>Full with Ads V8.7
==>>Full with Ads V9.0
==>>Patch For V9.2 must be flashed on top of fresh V9.0
****Run debloat ==>script to remove ads if you need/ want to, or remove from zip before flashing ****
alt. manual example: before reboot, while still in twrp. Select mount and put checkmark next to system. Then run these two commands in adb terminal
Code:
adb shell rm /system/priv-app/com.amazon.*/com.amazon.*.apk
adb shell rm /system/app/Adups*/*.apk
==>>Modified V21
** stand alone logo installs
I flashed this but I didn't get the custom boot logo.
mendelgordon said:
I flashed this but I didn't get the custom boot logo.
Click to expand...
Click to collapse
I had that happen to my second phone too.
I don't have an explanation yet.
I even made a separate update.zip , that one didn't make the logo change either. I did eventually change it with sp flash tool.
I tried with both recoveries.
and multiple /dev location formats. and for whatever reason my one phone did not accept the logo change from recovery.
And the other test phone it worked.
mendelgordon said:
I flashed this but I didn't get the custom boot logo.
Click to expand...
Click to collapse
Neither did I but it all seems to be working fine
Been using this for about a day now, likewise no custom boot logo, but that's fine. Otherwise, it's been running super well. A lot better than the previous mostly stock version did for me with the bloatware APKs removed after the install. A lot of the general idiosyncrasies of the previous version of the stock rom seem to have gone away for me. It seemed to have weird storage management issues, errors moving to SD, broken symlinks that prevent apps from moving or being reinstalled, and a lot of other little non-storage issues, but so far, none off that here.
Long story short, good work! I hope we eventually see proper 7.x roms through some of the efforts going on, but in the meanwhile, your work here has made life a little bit better on 6.
It seems that I was able to get the logo.bin to update when I applied the original update patch, but not when I used the same line in the rom install.
It is no big deal that it did not work, I was just trying to make it look different at boot time.
edit:
I think i found the problem with the logo not updating.
i used the update-binary from the official patch update. (the one that allowed the logo to change the first time)
and it changes . so since the ROM seems to install the way it is , only the logo didn't flash I put it in a separate update.zip if anyone is interested in it.
EDIT 2:
clarification.
It was not so much the binary allowing the logo to change but the format of the partition location I had been using that needed that binary.
Further test had shown me that I could have used the binary I was using but just change the partition naming line
Code:
package_extract_file("logo.bin", "/dev/block/mmcblk0p9")
the above code works with the same update-binary as rom install
But I was using
Code:
package_extract_file("logo.bin", "/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo")
Taken straight from the official patch, and thats why it needed the update-binary also.
I dont know what is different in the binary other than , major size difference.
The powered by me logo was just a test file to see changes in the logo.
**logo-update is same as composite but with alt updater-binary
**composite-logo screenshot is in op
**stock logo will return to original BLU logo
mrmazak said:
It seems that I was able to get the logo.bin to update when I applied the original update patch, but not when I used the same line in the rom install.
It is no big deal that it did not work, I was just trying to make it look different at boot time.
edit:
I think i found the problem with the logo not updating.
i used the update-binary from the official patch update. (the one that allowed the logo to change the first time)
and it changes . so since the ROM seems to install the way it is , only the logo didn't flash I put it in a separate update.zip if anyone is interested in it.
EDIT 2:
clarification.
It was not so much the binary allowing the logo to change but the format of the partition location I had been using that needed that binary.
Further test had shown me that I could have used the binary I was using but just change the partition naming line
Code:
package_extract_file("logo.bin", "/dev/block/mmcblk0p9")
the above code works with the same update-binary as rom install
But I was using
Code:
package_extract_file("logo.bin", "/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo")
Taken straight from the official patch, and thats why it needed the update-binary also.
I dont know what is different in the binary other than , major size difference.
The powered by me logo was just a test file to see changes in the logo.
Click to expand...
Click to collapse
Hahaha the scribbled "ME" is hilarious. Your work is awesome, I don't think anyone using this rom will have an issue with the boot image but thanks for being so helpful and explaining.
P. S. Do you have any plans with the Nougat update?
Serenitybs said:
Hahaha the scribbled "ME" is hilarious. Your work is awesome, I don't think anyone using this rom will have an issue with the boot image but thanks for being so helpful and explaining.
P. S. Do you have any plans with the Nougat update?
Click to expand...
Click to collapse
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )
linuxsociety said:
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )
Click to expand...
Click to collapse
Somebody already tried this out
linuxsociety said:
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )
Click to expand...
Click to collapse
It was just wishful thinking. I have no idea how all of this is done. All I know is @mrmazak has helped me to fall in love with my phone again with this V8.3. The 7.4.2 did seem a bit buggy for my phone but this update works beautifully and I didn't even root it. If this remains true I will be happy with this phone for awhile even on 6.0
Really confused right now.
I was browsing through the settings menus. And found in the Settings-security- menu a toggle labeled "quick boot" ( not to be confused with "fastboot") . I enabled it then rebooted to see if it booted quicker. Didn't seem to make much if any difference. So I went back to turn it back off. And it wasn't there. I checked in my other phone , it wasn't there on that one either.
Did any body see this menu item, and if so where is is it?
Edit 1:
Few more power off , power on cycles to compare times. With other phone and defiantly seems to have turned on some faster boot option.
This phone goes from off to on in 5-6 seconds other phone takes about 20.
Edit 2:
OK , I panicked for a minute.
Couldn't find the setting and thought that it was another way to block sp flash tool by preventing you from ever being fully powered off.
But the setting was in accessibility not security.
Mrmazak, first of all, thanks for the ROM, installed it yesterday. But I have a problem with SELinuxModeChanger app. First, I'm getting a security warning when installing it, then - when running it. And another message, with this app running - "can't obtain root", although SuperSU shows its status with green #, like every other app it gives root privileges to. On my other Prime phone, running 6.1 out of the box stock ROM, FM radio works just fine with SELinuxModeChanger app behaving flawlessly (no security warnings whatsoever). Any ideas?
detroitredwings said:
Mrmazak, first of all, thanks for the ROM, installed it yesterday. But I have a problem with SELinuxModeChanger app. First, I'm getting a security warning when installing it, then - when running it. And another message, with this app running - "can't obtain root", although SuperSU shows its status with green #, like every other app it gives root privileges to. On my other Prime phone, running 6.1 out of the box stock ROM, FM radio works just fine with SELinuxModeChanger app behaving flawlessly (no security warnings whatsoever). Any ideas?
Click to expand...
Click to collapse
The mode changer app is technically a security issue. I did have that warning a few times when using mode changer app from the XDA thread of the developer, then when I used the app downloaded from f-droid it worked with systemless root and didn't give the security warning.
The app downloaded from f-droid worked for me as well, many thanks!
Big thanks for getting this out, updated from previous debloated, rooted version to this modified 8.3 stock rom, rooted with SU v2.79 SR3, all is good - only App that won't show up nor install, even tried the ones off APK Mirror site - is my Dunkin Donuts App, LOL. Play Store now said it's not compatible and the APK started to install then failed - any ideas or suggestions on what to do ??
Otherwise, it's all good - I will survive without DD App, just run that from another device when I need my caffeine fix.
Letitride said:
Big thanks for getting this out, updated from previous debloated, rooted version to this modified 8.3 stock rom, rooted with SU v2.79 SR3, all is good - only App that won't show up nor install, even tried the ones off APK Mirror site - is my Dunkin Donuts App, LOL. Play Store now said it's not compatible and the APK started to install then failed - any ideas or suggestions on what to do ??
Otherwise, it's all good - I will survive without DD App, just run that from another device when I need my caffeine fix.
Click to expand...
Click to collapse
I also had an app that previously work, say is not compatible now.
Maybe has to do with apps that have links to pay accounts. And that has something to do with trustzone. (Tee1 & tee2)
Those sections I left out of the update. I will add it back in and test. Update when I do. It is also possible this problem is why Blu rolled back there update.
**EDIT**
well that didn't go well at all.
I flashed the new trustzone.bin files from the official update. Now phone no longer turns on and no longer connects to flash tool
**EDIT 2**
After much persistence and many failed attempts to get phone recognized in pc again. Finnaly got to a point that phone was cycling between "preloader" driver and "usb serial device", and with careful timing was able to start sp flash tool at just right time and the flashing back to original trustzone files seems to have recovered phone.
for the record i am not sure what steps made it work. But I was shifting back and forth between leaving phone sit on charge, then on charge with rubber band wrapped around power button, then not plugged in , and not plugged in with rubber band on power button.
Okay... persistence is key in customization, i guess! I am getting somewhere here!
mrmazak said:
The first link is needed to get phone unlocked so you can install twrp.
Click to expand...
Click to collapse
Finally got thru the steps in order (1-2-3-4) then Step (5) and sub-step 1. I can also boot to TWRP.
Now this brings me to this thread, 8.3 Stock ROM. The thread assumes one knows how to install it and I suspect this could be as easy as uploading it to a folder in the phone then booting to TWRP and INSTALLING the ZIP file? Could someone clarify the steps to install this 8.3 ROM?
Thanks!
OldSkewler said:
Okay... persistence is key in customization, i guess! I am getting somewhere here!
Finally got thru the steps in order (1-2-3-4) then Step (5) and sub-step 1. I can also boot to TWRP.
Now this brings me to this thread, 8.3 Stock ROM. The thread assumes one knows how to install it and I suspect this could be as easy as uploading it to a folder in the phone then booting to TWRP and INSTALLING the ZIP file? Could someone clarify the steps to install this 8.3 ROM?
Thanks!
Click to expand...
Click to collapse
Yes. You are correct
Either put the zip file on external sd card , put card into phone boot into recovery mode and install , or put file directly onto phone .
Many ways to do that.
Easiest is to copy to phone while phone is connected to PC.
Cam also download file from internet with your phone.
Bottom line is get zip file to the phone boot to recovery and install
Anyone else having wifi issues after upgrading? While watching videos it seems the internet cuts out. The phone says it's still connected but I have to turn wifi off and back on for anything to work. Could be my router also but it didn't seem to be doing this until I installed 8.3
mrmazak said:
Yes. You are correct
Either put the zip file on external sd card , put card into phone boot into recovery mode and install , or put file directly onto phone .
Easiest is to copy to phone while phone is connected to PC.
Bottom line is get zip file to the phone boot to recovery and install
Click to expand...
Click to collapse
Right on man! I am officially running 8.3 ROM with April 5th 2017 Security Patch Level! Geez.. it was not easy but I got this working!
MrMazak, I followed all your instructions on both links, so could you tell me what exactly I have on my phone? Is it rooted? Bootloader Unlocked? The phone seems to be working fine but I don't know what level of access I have. Honestly I don't even know exactly what the differences between all these terms are.
Also, do I have or not SU? One of the steps under the .bat I believe install it. How do I access it?
Thanks again!
---------- Post added at 10:19 PM ---------- Previous post was at 10:18 PM ----------
Weasel0 said:
Anyone else having wifi issues after upgrading? While watching videos it seems the internet cuts out. The phone says it's still connected but I have to turn wifi off and back on for anything to work. Could be my router also but it didn't seem to be doing this until I installed 8.3
Click to expand...
Click to collapse
My install is pretty fresh, couple of hours, but as far as I can tell all is working fine with Wifi, As a matter of fact this is a new device only connected with Wifi and no SIM Card.... internet works fine.
TWRP thread here
https://forum.xda-developers.com/u11/development/recovery-twrp-touch-recovery-t3617028
I clone the repo from @Captain_Throwback and built TWRP recovery for U11 (ocndugl).
It can work well but have some issue with OTG function and touch not work while boot into TWRP (press power button and unlock lockscreen could get touch back to work).
#built with ocndugl kernel, it may not boot on ocnuhl or ocndtwl variant
#version 1
twrp-3.1.1-0-ocn_TEST.img
https://www.androidfilehost.com/?fid=817550096634770756
#version 2
I fix the external_sd and otg issues but USB function still not work.
twrp-3.1.1-0-ocn_TEST_2.img
https://www.androidfilehost.com/?fid=817550096634772885
Well, when you create device files without a device and can't test what you build, you end up with a TWRP that isn't fully functional...
If I'm able to get one, I will certainly do my best to work out any of the issues and make sure the device gets official TWRP support. Thanks for testing my device tree.
Captain_Throwback said:
Well, when you create device files without a device and can't test what you build, you end up with a TWRP that isn't fully functional...
If I'm able to get one, I will certainly do my best to work out any of the issues and make sure the device gets official TWRP support. Thanks for testing my device tree.
Click to expand...
Click to collapse
Plz read the thread carefully. He lives in Taiwan and U11 is selling there for a couple of days, there are many user reviews on TW forums already. Next place comes to Hong Kong around 5/6th June and I pre-ordered an U11 6+128GB. Finger crossed.
TheEndHK said:
Plz read the thread carefully. He lives in Taiwan and U11 is selling there for a couple of days, there are many user reviews on TW forums already. Next place comes to Hong Kong around 5/6th June and I pre-ordered an U11 6+128GB. Finger crossed.
Click to expand...
Click to collapse
well, there is no information about that he lives in taiwan or not. so no need to read it carefully
Captain_Throwback said:
Well, when you create device files without a device and can't test what you build, you end up with a TWRP that isn't fully functional...
If I'm able to get one, I will certainly do my best to work out any of the issues and make sure the device gets official TWRP support. Thanks for testing my device tree.
Click to expand...
Click to collapse
Hope you could get one and maintain this device.
I'm still a noob with this :laugh:
Sent from my HTC One M9 using XDA Labs
DeeZZ_NuuZZ said:
well, there is no information about that he lives in taiwan or not. so no need to read it carefully
Click to expand...
Click to collapse
His home country stated Taiwan
Sent from my LG-D855 using XDA Free mobile app
TheEndHK said:
His home country stated Taiwan
Sent from my LG-D855 using XDA Free mobile app
Click to expand...
Click to collapse
yea saw that now, because it wasn't visible cause he's OP. didn't even knew taiwan sells it earlier, just remembered in EU it solds from first june I think
DeeZZ_NuuZZ said:
yea saw that now, because it wasn't visible cause he's OP. didn't even knew taiwan sells it earlier, just remembered in EU it solds from first june I think
Click to expand...
Click to collapse
No offense indeed and thanks Captain_Throwback for his hard working on HTC. In my experiences, HTC guys on xda board are usually nice and helpful, mostly better than those who I met on sony, samsung, lg xda board.
I've sent a pull request to https://github.com/CaptainThrowback/android_device_htc_ocn that fixes the sd card and screen not responding at first boot issues. The usb one I'll look at later, need to do some real life stuff for a bit
I expect the problem is in init.recovery.usb.rc as it sets mtp,adb
One thing though... whilst I can fastboot boot recovery.img I can't flash recovery with an unlocked bootloader but S-ON.
$ fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (34772 KB)...
OKAY [ 0.778s]
writing 'recovery'...
FAILED (remote: Not allowed on PRODUCTION device)
finished. total time: 0.778s
Flinny said:
I've sent a pull request to https://github.com/CaptainThrowback/android_device_htc_ocn that fixes the sd card and screen not responding at first boot issues. The usb one I'll look at later, need to do some real life stuff for a bit
I expect the problem is in init.recovery.usb.rc as it sets mtp,adb
One thing though... whilst I can fastboot boot recovery.img I can't flash recovery with an unlocked bootloader but S-ON.
$ fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (34772 KB)...
OKAY [ 0.778s]
writing 'recovery'...
FAILED (remote: Not allowed on PRODUCTION device)
finished. total time: 0.778s
Click to expand...
Click to collapse
interesting...looks like we'll need s-off sooner than later... when u fastboot boot it, is twrp still functional?
OMJ said:
interesting...looks like we'll need s-off sooner than later... when u fastboot boot it, is twrp still functional?
Click to expand...
Click to collapse
Yeah, backups to internal and sdcard is as far as I've gone. I might give flashing my SlimRoms build a go later.. or maybe I'll see if my built ramdisk with a few bootclass path alterations for stock boots first
I also got TWRP compiled and running, stuck at MTP and USB Mass storage too.
BTW, I rooted my device before flashing any custom recovery... using something about to be released in the Magisk forum
Guess I should open a TWRP thread with my mostly working version now that we have a working kernel . We can continue working on MTP/UMS, though I suspect MTP will require a patch or two in TWRP upstream to add support for configfs. I think fixing UMS will require kernel source.
Haha guys, I figured out the way to fix both UMS and MTP. Yay!
I provided the info to Captain, and him, nkk71 and I are working on it now
topjohnwu said:
Haha guys, I figured out the way to fix both UMS and MTP. Yay!
I provided the info to Captain, and him, nkk71 and I are working on it now
Click to expand...
Click to collapse
nice!
topjohnwu said:
Haha guys, I figured out the way to fix both UMS and MTP. Yay!
I provided the info to Captain, and him, nkk71 and I are working on it now
Click to expand...
Click to collapse
That's awesome!!
Flinny said:
I've sent a pull request to https://github.com/CaptainThrowback/android_device_htc_ocn that fixes the sd card and screen not responding at first boot issues. The usb one I'll look at later, need to do some real life stuff for a bit
I expect the problem is in init.recovery.usb.rc as it sets mtp,adb
One thing though... whilst I can fastboot boot recovery.img I can't flash recovery with an unlocked bootloader but S-ON.
$ fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (34772 KB)...
OKAY [ 0.778s]
writing 'recovery'...
FAILED (remote: Not allowed on PRODUCTION device)
finished. total time: 0.778s
Click to expand...
Click to collapse
BTW, I figured out that you must be flashing recovery in fastboot mode.
Boot into download mode, then you can flash the recovery without an issue
(reboot with power button down, or adb reboot download)
Interesting, that's new my last phone was a m9 :/
TWRP thread is up. Thanks @Flinny and @topjohnwu for helping work out the issues with TWRP!
Still hoping to be able to get my hands on one so I can maintain for it properly .
Captain_Throwback said:
TWRP thread is up. Thanks @Flinny and @topjohnwu for helping work out the issues with TWRP!
Still hoping to be able to get my hands on one so I can maintain for it properly .
Click to expand...
Click to collapse
I missed the m10.. after getting the m7/m8/m9 but I have to say I'm REALLY enjoying the u11 everything is just INSTANT.
Read First: This method is relatively drastic, and will hurt device performance some. You should only use this as a last resort, if the more basic methods of fixing a soft brick didn't work (e.g, factory reset, flash stock firmware, etc.)
*Update 7/30: On my 6P, I found that the original kernel with this mod was using pretty much 1.5 cores, instead of all 4. People with the 5X were also reporting this, so I modified the images to utilize all 4 cores better. It helps performance a lot (able to beat stock 6P in some Antutu marks now, and play intensive games), try it out if you haven't yet!
*Petition:
I made a petition for Google to officially release and sign modified boot.imgs, so that people with locked bootloaders can fix their devices too. Check it out here. (I apologize for dumbing it down so much, I wanted to make sure everyone could understand it)
*Changelog:
8/26 - EX kernel for Android O uploaded.
8/22 - Android O working, boot.img and source uploaded.
8/08, 2nd Change - Added boot.img for 48C firmware (August security patch).
8/08 - Updated EX kernel to version 4.1.2. This updated zip adds the CPU utilization patch to the init.elemntalx.rc, instead of removing the old init.angler.rc and copying the new init over. That should mean more compatibility with Roms/kernels that modify the init.angler.rc. I also modified the camera-daemon to use cpus 0-3 instead of 0-2, so hopefully this should make the a camera bit faster too.
8/07 - Added boot.img for 1 core, just to see if it would work for devices that didn't work with the 4 core image.
7/30, 2nd Change - Added universal EX zip, this zip should modify your kernel to use only 4 cores, and it should modify it to utilize all 4 cores. You can flash this over most ROMs and it should work. Also added a donation url, and this changelog.
7/30 - Updated this fix to greatly improve performance. Before this fix, the device was only using 1 core for foreground tasks, now it will use all 4 cores. Also revamped OP, and added Marshmallow images.
7/23- Created this fix, stock boot.img, twrp, and EX kernel added.
*What this fix does, and how to apply it:
The problem:
The problem with most of the devices in a BLOD, is that a hardware failure related to the BIG cluster has occurred. This fix remedies the problem by disabling the BIG cores. Unfortunately, this does mean that you will take a performance hit. However, I am continually working on ways to improve the device's performance.
The update: If anyone remembers device performance with the first fix, it was hurt a lot, however, after finding out that the device was only using 1 core for all foreground tasks, I modified the ramdisk to utilize all 4 cores more effectively, and it helps a lot.
Requirements: For this fix to work, you need:
A brain
A computer
A bootlooping 5X with an unlocked bootloader/OEM unlocking enabled
The modified files of your choice.
Fastboot on your computer (preferably installed system wide). If you do not know what this is, or do not have it, look at this post. Answer yes to all of the prompts to install it.
How to apply the fix:
Boot your phone into bootloader (hold power and volume down).
Connect your phone to the computer.
Go to the folder where you have the modified files, then hold shift and right click in a blank space, click on "open command prompt here" in the menu that pops up.
In the command prompt: type "fastboot flash boot [name of the file here]" and then press enter. If you're flashing TWRP, replace boot with recovery. (Linux users, make sure you're running as root)
Edit: with the new universal EX zip, you don't have to flash the modified boot.img now, you can just flash TWRP, and then flash the EX zip, and everything should work.
Boot up your phone, and hopefully it should work!
*If your phone is bootloader locked/OEM locked:
You can try to get your phone to boot long enough to enable OEM unlocking. Some users have reported success by freezing their phone for a bit, then booting it. Others have let their battery drain all the way, and then tried to boot their phone, but the most successful method seems to be heating up your phone (a lot).
If you do attempt any of these methods, make sure you have time and patience, as it will take a long time.
To enable OEM unlocking and unlock bootloader:
Go to settings.
Go to developer options, if you do not see that, go to "about phone", scroll to build number, and then tap it 7 times. You should now see developer options in settings.
Once you're in developer options, click on "OEM unlocking" and accept the prompt.
Now reboot your phone to bootloader, connect your phone to the computer, and type "fastboot flashing unlock" Your bootloader should now be unlocked.
*Downloads:
Boot.img from Android O DP6: Download | Mirror. This Image is the from the first official release of Android O, and is modified to use 4 cores. As a bonus, it also disables forced encryption. Thank you to @xls654 for figuring out how to get Android O to work.
Boot.img from stock 48C, 7.1.2 firmware (August security patch): Download | Mirror. This Image is modified to use only 4 cores, and is modified to utilize the 4 cores more effectively. I have had multiple people on the 6p say that first boot takes a while after flashing this, so just wait about 20 minutes before you declare something is wrong with it.
Boot.img from stock 47Z, 7.1.2 firmware: Download | Mirror. This Image is modified to use only 4 cores, and is modified to utilize the 4 cores more effectively. I have had multiple people on the 6p say that first boot takes a while after flashing this, so just wait about 20 minutes before you declare something is wrong with it.
TWRP version 3.1.1: Download | Mirror. This TWRP image is modified to use only 4 cores.
EX kernel version 5.03, for Android O: Download | Mirror. EX kernel for Android Oreo, modified to use 4 cores. You must flash it over the 4 core boot.img for it to work.
EX kernel version 4.12, universal zip: Download | Mirror. This zip is modified to use only 4 cores, and it will also apply the speed fix. Flash this in TWRP. I highly recommend you flash this, as it improves device performance notably, and disables forced encryption. This kernel should work with almost any other ROM, and it applies the core utilization mod from the first image, thanks to AnyKernel.
Boot.img modified to use only 1 Core. Some people were reporting that the 4 core images weren't working for them, someone suggested that I make a 1 core version to see if that helps at all. Here it is: Download | Mirror
For Marshmallow:
Boot.img from the latest 6.0.1 20K firmware: Download | Mirror. This boot.img is modified to use only 4 cores, and is modified to utilize those 4 cores more effectively. Untested as of now.
Ex kernel version 1.2.0 for Marshmallow: Download | Mirror. This is the latest EX kernel for marshmallow, it will keep the core utilization mod from the above image, and should work on almost any other ROM, thanks to any kernel. Untested as of now.
*Source Code:
Source for 4 core Android O DP6: Source.
*Tested custom ROMS/kernels
you should be able to use almost any ROM with a stock based kernel, just flash the EX zip over it.
If you have a custom ROM/kernel that worked for you, let me know and I'll put it up here.
*To improve performance slightly:
Flash a custom kernel. I will upload more kernels as people request more, so stay tuned.
Flash a custom ROM. Once again, I will upload more as people request more, so stay tuned.
Overclock the little cores. It can slightly help offset the lost performance, on my 6P, I have mine overclocked to 1632MHz, and it works perfectly for me. Edit: I actually recommend not overclocking. Many people have reported their Little cores failing, so I would go for longevity on this device, and keep it at stock clocks, or even underclock it. The speed difference you get from overclocking is negligible anyways.
Disable animations in developer options. Seriously, as soon as I found out about this tweak, I've used it on ever single device I've owned, it helps a ton.
*Credits:
@rchtk, His post here gave me the idea for how to modify the images.
@flar2, He built the Elemental X kernel for this device, I merely made a small modification to his kernel to use 4 cores. In no way am I trying to steal and/or discredit his work.
The TWRP development team, they built the TWRP recovery for this device, I merely made a small modification to their recovery to use 4 cores. In no way am I trying to steal and/or discredit their work.
@xls654, He found out how to get Android O working with 4 cores.
*FAQs:
What's the password for TWRP/Why is TWRP asking for a password? - In android 7.0, Google added forced encryption to the data partition. To get around this, click cancel when TWRP asks you for a password, and then factory reset the device. Then you can flash EX kernel/Magisk to disable forced encryption.
Why am I getting an error when I try to flash the images? - Your bootloader is probably not unlocked, try running the command "fastboot flashing unlock", If you get an error there too, then you will have to enable OEM unlocking before you can continue.
It's not working for me, how do I fix it? - My only advice for that is: "Flash the stock firmware for whatever version image you're trying to flash, then reflash the images again" If you're stuck on the boot animation, wait at least 20 minutes before you declare it's not working. If none of that works, chances are you have a different problem.
Does EX kernel have the new speed fix? - Yep, the EX kernel zip should apply the 4 core fix, and the speed fix. It should also work with almost any ROM, including stock.
I would like to help as many people as I can, however, I am much more likely to be able to easily help you/reply to your post if you clearly state your problem and the steps you attempted to fix it. I will be much less likely to reply to posts such as "omggg i flashed the image and my phone won't boot helppp" Please read through post first, I did not spend time typing up this OP for no one to read it. If I can see that you read through the OP and have attempted all the steps, then I will be much more willing to help you.
I set up donations on my profile, for those of you who want to donate. I have spent countless hours modifying, flashing, testing, and helping, don't get me wrong, I love doing this and helping y'all out, but donations really keep me motivated to keep going, and donations also will help me fund new equipment and devices that will help further my android development. Every single donation is appreciated Donate to me here!
If this guide helped you, please click thanks, it means a lot to me
Didn't work
I flashed the image and the bootloop is still there, thanks for the effort though. Anything else you'll need for the 5X to continue your research ?
Acelogic_ said:
I flashed the image and the bootloop is still there, thanks for the effort though. Anything else you'll need for the 5X to continue your research ?
Click to expand...
Click to collapse
dang :/ If you can get into twrp, pulling the "console-ramoops" would be helpful, but I don't think you can boot to twrp.
this actually fixes my phone, i do the same with elementalx kernel i disable the big cores as soon as my phone boots up so this img is really handy
TheIronLefty said:
this actually fixes my phone, i do the same with elementalx kernel i disable the big cores as soon as my phone boots up so this img is really handy
Click to expand...
Click to collapse
Awesome! Glad to hear it.
XCnathan32 said:
dang :/ If you can get into twrp, pulling the "console-ramoops" would be helpful, but I don't think you can boot to twrp.
Click to expand...
Click to collapse
Yeah Twrp is not working.
So I just flashed this over the May 2017 build and my phone boots and is working just fine, albeit a bit slowly.
I'll update to the latest build and reflash but for now you can say it works as intended. Thanks for the effort
Gonna try this
Sent from my EVA-L09 using Tapatalk
It's worked for me. Phone is slower, and taking picture with hdr+ is okey but processing is very slow. I turned off animation, is there anything else I can change so phone can perform faster ?
Any idea how long this should take? I managed to get into my 5x and enable debug mode / OEM unlocking
I ran the fastboot flash boot N2G47Z_4Cores.img command and its been stuck for about 5 minutes
This works, thanks. First time I've been able to boot my 5X in months.
Acelogic_ said:
I flashed the image and the bootloop is still there, thanks for the effort though. Anything else you'll need for the 5X to continue your research ?
Click to expand...
Click to collapse
I uploaded a custom TWRP image and EX kernel zip. Try flashing the modified TWRP, and then flashing the modified EX kernel, and see if that works.
after trying again I was able to get it to write successfully however the nexus 5x is still bootlooping, this is an original hardware revision nexus 5x if that helps
ragdoll96 said:
So I just flashed this over the May 2017 build and my phone boots and is working just fine, albeit a bit slowly.
I'll update to the latest build and reflash but for now you can say it works as intended. Thanks for the effort
Click to expand...
Click to collapse
X-calibar said:
It's worked for me. Phone is slower, and taking picture with hdr+ is okey but processing is very slow. I turned off animation, is there anything else I can change so phone can perform faster ?
Click to expand...
Click to collapse
I updated the OP with a modified EX kernel, and some tweaks to make your device faster, check it out to see if it helps your device.
stipo42 said:
Any idea how long this should take? I managed to get into my 5x and enable debug mode / OEM unlocking
I ran the fastboot flash boot N2G47Z_4Cores.img command and its been stuck for about 5 minutes
Click to expand...
Click to collapse
My first time took around 10 minutes to boot I think, if it takes over 20 minutes, reboot your device and reflash, and if that fails, update your firmware to the latest version.
stipo42 said:
after trying again I was able to get it to write successfully however the nexus 5x is still bootlooping, this is an original hardware revision nexus 5x if that helps
Click to expand...
Click to collapse
Are you upgrading from stock firmware or a custom rom? This boot.img is for the latest 7.1.2 build. Unless you have files that you can't afford to delete, I would recommend reflashing your stock firmware with the latest version.
flar2 said:
This works, thanks. First time I've been able to boot my 5X in months.
Click to expand...
Click to collapse
Awesome! I just want to say how much I love your kernel, it makes this fix much more viable.
update: I was able to install twrp and boot into that, but its asking for a password.... @XCnathan32 is there a specific password you set or should "default_password" work?
stipo42 said:
update: I was able to install twrp and boot into that, but its asking for a password.... @XCnathan32 is there a specific password you set or should "default_password" work?
Click to expand...
Click to collapse
default_password didn't work for me, I just clicked cancel when it asked for the encryption, and then I factory reset the device through TWRP. If you have important files you can't delete, you can try just flashing EX Kernel, as I don't think EX needs to access the /data partition.
Update 2 : Seems I was able to just cancel out of the password prompt. Flashed Elemental X and it looks like its booting!
Awesome job my friend, you fixed the (temporarily) unfixable. I'll play around with this for a few days and report back.
Thanks!
XCnathan32 said:
So I found a bootloop fix for the Nexus 6p here, and some users reported having the same problem with their Nexus 5X.
I do not own a Nexus 5X, but I made a modified boot.img the same way I made the modified 6P image. It simply disables the big cores, as that's what was preventing the 6P from booting.
Please report if this works/does not work for you, that way I can get a good sample size to determine how effective this is.
Disclaimer: I have not tested this, I uploaded this image so testers could flash it and report if it works or not. If your device breaks/spontaneously combusts after flashing this, you accepted that risk.
Edit: A few people have reported this working, so it should be safe.
N2G47Z_4Cores.img, this image is based on the latest 7.1.2 firmware for the Nexus 5X, modified by me to only use 4 cores. 4 reported working, 2 reported not working.
To flash it: you must have an unlocked bootloader and fastboot on your PC. Boot your device into bootloader, and then run the command fastboot flash boot N2G47Z_4Cores.img Hopefully, your device will now boot up.
TWRP3_1_1_5X.img, modified to use only 4 cores, will get working TWRP on your device. Not tested yet
To flash, navigate to the folder where it is downloaded, make sure you have fastboot installed, and then run this command: fastboot flash recovery TWRP3_1_1_5X.img.
EX4_10_5X.zip, Elemental X kernel V4.10 for android 7.1.2, modified to use only 4 cores, I highly recommend you flash this, as EX kernel is faster, and you can overclock to the little cluster to make up for some speed. Not tested yet.
To flash, copy the zip to your device, then flash it in the modified TWRP, just go through the AROMA installer as usual. Changing the BIG cpu frequency in the installer will not change anything, as the cores are disabled.
Additional notes:
Root worked on my 6p by flashing the regular SuperSu zip just as normal. None tested for 5X yet
To improve performance slightly:
Disable animations in developer options, it helps a lot.
Overclock little cores with EX kernel, I have mine set to 1632 MHz and everything is working fine so far.
Set CPU governor to performance (or some aggressive governor), with the BIG cores disabled, the battery is already much better, so using a better performance governor shouldn't be a problem for battery life.
Doing a fresh flash of the firmware/factory reset can help a lot too.
Fast custom roms can also help.
Roms that me/other users have found working with this fix:
Pure Nexus worked well for me on the 6p, insane battery life and very little lag. If you are going to flash a rom, be sure to flash the modified EX kernel over it.
If you find a rom that works with this fix, tell me, and I'll put it here.
Credits:
@rchtk, his post here gave me the idea for how to modify the images.
@flar2, He built the Elemental X kernel for this device, I merely made a small modification to his kernel to use 4 cores. In no way am I trying to steal and/or discredit his work.
The TWRP development team, they built the TWRP recovery for this device, I merely made a small modification to their recovery to use 4 cores. In no way am I trying to steal and/or discredit their work.
Feel free to ask me for help, If you have a favorite ROM/Kernel that you want to use, tell me and i'll modify it to use 4 cores.
Please click thanks if I helped you, it means a lot to me
Click to expand...
Click to collapse
Hey man I tried this method, and I can confirm that this works! Although it is slow, it's better than nothing I truly do appreciate your efforts. SCREW LG
[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