[STOCK] Boot images with verity removed - ZTE Axon 7 Mini ROMs, Kernels, Recoveries, & Other

The stock ROM has a feature called verity, which ensures that the system partition is not modified. It uses a cryptographic signature to verify each sector on the partition. If any sector is modified, it is treated as corrupt.
In other words, any changes to the system partition will render it unbootable. This includes mounting /system read-write in recovery, even once.
In order to modify your system partition or recover from accidentally mounting your system partition read-write, you must download and flash the correct boot image using tuliptool.
You can find stock boot images with verity removed here:
US model, version 7.1.1 b12
md5=71428e4957763858f47bc9540e848d5e
US model, version 7.1.1 b14
md5=c6a67411e81f27d798eea035ddf4261e
EU model, version 7.1.1 b09
md5=ba210d332d3527b81f652dd0d2ce962e

i tried to see what would happen if i adb sideload supersu and my results came out that the went to zte screen and went into a bootloop didnt boot up but i have root priv in twrp....hmm. so i re-edl boot to after that i was able to boot back in to my android without root or supersu and twrp went back to normal aswell i was in the mood to test thankfully i was able to fix what ever had any issues

What would we need to provide for you to make one for v1.0.0B06?

I can make one for any firmware version. I just need the following:
* any relevant regional or model info.
* firmware version (including android version).
* the backup boot image, eg. from tuliptool.
parawizard said:
What would we need to provide for you to make one for v1.0.0B06?
Click to expand...
Click to collapse

So if I were to want to stay on the current ZTE rom (for now) would I need to flash this in order to root or currently root is only supported on the incomplete rom you are working on?

Depends how you root. I don't run stock so someone else should answer with details.
fallen00sniper said:
So if I were to want to stay on the current ZTE rom (for now) would I need to flash this in order to root or currently root is only supported on the incomplete rom you are working on?
Click to expand...
Click to collapse

tdm said:
Depends how you root. I don't run stock so someone else should answer with details.
Click to expand...
Click to collapse
i'm not a fan of the stock image, i do like to keep features which the stock seems devoid other than atmos which used to be hit or miss lol
i am sure someone out there likes the stock look, i used nova launcher and made things smaller, neater and tried to make it look a little better.

Done some experiments with SuperSU 2.82 (unsuccessfully, got bootloop).
In other words, any changes to the system partition will render it unbootable. This includes mounting /system read-write in recovery, even once.
Click to expand...
Click to collapse
And was able restore phone to work only with this EU boot.
Thanks, for making and publishing it!

Hi tdm, my 7 mini is USA hardware version but with European 6.0.1 firmware (build number ZTE B2017G V1.0.0B12). I tried to go back to USA Nougat firmware but unsuccessfully. Basically my phone was turned into P852A11 from P852A12. Do I need a new boot image with verity removed so that I can flash USA firmware? If I have to use Tuliptool, can you build a Windows32 version? Thanks in advance.

Sure thing, I'll make a firmware package. Please get me your partition checksums as in this post:
https://forum.xda-developers.com/showpost.php?p=74134639&postcount=52
I'll look into a win32 version of tuliptool.
bao_gg said:
Hi tdm, my 7 mini is USA hardware version but with European 6.0.1 firmware (build number ZTE B2017G V1.0.0B12). I tried to go back to USA Nougat firmware but unsuccessfully. Basically my phone was turned into P852A11 from P852A12. Do I need a new boot image with verity removed so that I can flash USA firmware? If I have to use Tuliptool, can you build a Windows32 version? Thanks in advance.
Click to expand...
Click to collapse

tdm said:
Sure thing, I'll make a firmware package. Please get me your partition checksums as in this post:
https://forum.xda-developers.com/showpost.php?p=74134639&postcount=52
I'll look into a win32 version of tuliptool.
Click to expand...
Click to collapse
Thank you tdm. You are awsome. I will provide you the checksums tomorrow.

Hey @tdm
Wanted to ask if you just removed the "verify" option in the fstab file to strip the dm verity checks? I might have read something like this before

Yes that's exactly it.
TheSSJ said:
Hey @tdm
Wanted to ask if you just removed the "verify" option in the fstab file to strip the dm verity checks? I might have read something like this before
Click to expand...
Click to collapse

I had finally gotten around to unlocking the bootloader and flashing TWRP.
Would flashing one of your custom ROMs without flashing the verity-free boot images affect anything?

I would suggest flashing the no verity boot just to avoid the headache

The stock boot images are only for running stock. Custom ROMs all include their own boot images.
JoeGatto said:
I had finally gotten around to unlocking the bootloader and flashing TWRP.
Would flashing one of your custom ROMs without flashing the verity-free boot images affect anything?
Click to expand...
Click to collapse

tdm said:
The stock boot images are only for running stock. Custom ROMs all include their own boot images.
Click to expand...
Click to collapse
Great. Looks like I'll be trying AOKP soon.

JoeGatto said:
Great. Looks like I'll be trying AOKP soon.
Click to expand...
Click to collapse
I've been running it for a couple of days and so far its great. No issues here

MrWhite0429 said:
I've been running it for a couple of days and so far its great. No issues here
Click to expand...
Click to collapse
You weren't kidding. Feels much faster than ZTE's ROM, and so refreshing as long as I've been looking at that MiFavor UI.
EDIT: Battery drain during standby.

tdm said:
Sure thing, I'll make a firmware package. Please get me your partition checksums as in this post:
https://forum.xda-developers.com/showpost.php?p=74134639&postcount=52
I'll look into a win32 version of tuliptool.
Click to expand...
Click to collapse
Hi tdm, my adb can not recognize the mini. And in order to get the partition info, I need to "boot into twrp" as the instruction says. But my recovery is STOCK not TWRP.
Anyway, if you can make a win32 Tuliptool, I can unlock the bootloader and flash the TWRP in. After that, I can flash any firmware that I want. Is it correct?

Related

[XT1575] TWRP Recovery Image for Stock MXP 7.0 Nougat NPH25.200-22

Stock Android 7.0 (Nougat) for the Moto X Pure 2015 XT1575 US NPH25.200-22
TWRP Recovery Image (Includes /boot and /system only)
**Factory reset after restore is advised.**
https://drive.google.com/drive/folders/0B2lKWOIH0bTqc29NbVNWWWhsYVE?usp=sharing
**Not tested coming straight from stock 6.0 MPH24.49-18-16.**
I did an incremental OTA upgrade from stock 6.0 MPH24.49-18-8.
Use at your own risk. If you have TWRP installed your warranty is void anyway. I'm not responsible for bricking your device.
worked great for me 18-16 thanks really appropriate the work
Hi
and thx for sharing.
I have unlocked booloader and rooted, can I just flash this one with twrp?
thx in advance
the-light said:
Hi
and thx for sharing.
I have unlocked booloader and rooted, can I just flash this one with twrp?
thx in advance
Click to expand...
Click to collapse
Yes. Root is nonconsequential. You really just need twrp.
Can i just flash it over TruPureX Android 6?
(I guess i can, just want to be sure)
Where can I find Android 7 modem to flash separately?
Will it work with Android 6 modem?
newHere:) said:
Can i just flash it over TruPureX Android 6?
(I guess i can, just want to be sure)
Where can I find Android 7 modem to flash separately?
Will it work with Android 6 modem?
Click to expand...
Click to collapse
No Nougat modem is available until the flashable (non OTA) full stock 7.0 rom is made available from Motorola. This is not likely to happen. No issues have been mentioned running this update on a 6.0 modem. Not sure what the advantages are honestly. I never had problems with bt, wifi, or calls with the 6.0 modem firmware.
Create a backup beforehand and you can always go back to it.
hi i noob, i speak spanish.
I have moto x pure clark xt1575, android 6 no root, i install twrp an unlock bootloader.
I try to install this "ota" room, but fail. i restore back up and now the phone follow work
mphs24.49-18-16.
Need help how instal android 7 official, or only way custom room "lineage 14"
Thanks.
Can I flash this over Lineage OS 14.1 after a full wipe?
acoupleofdroids said:
worked great for me 18-16 thanks really appropriate the work
Click to expand...
Click to collapse
Hi talk about u experience
Greetings, it counts as you did, I have android 6.0 mphs24.49-18-16 and I can not update. Phone with bootloader unlocked and with twrp, no root
I get "invalid ZIP file format" using TWRP 3.1.1-0 on an XT1575. Was running lineageOS 14.1 but I wiped system and data before trying to install the zip. On my laptop I can open the ZIP fine and extract the files, but that doesn't help.
bussemac said:
I get "invalid ZIP file format" using TWRP 3.1.1-0 on an XT1575. Was running lineageOS 14.1 but I wiped system and data before trying to install the zip. On my laptop I can open the ZIP fine and extract the files, but that doesn't help.
Click to expand...
Click to collapse
See this thread :
https://forum.xda-developers.com/moto-x-style/general/guide-xt1575-update-to-nph25-200-22-t3680477
The OP will need to comment - he may be coming from a rooted stock ; at least according the the thread noted above - if you have installed a custom ROM ; there are other steps besides just trying to flash this
I have NOT tried the OP's method or the referenced thread - so I cannot really speak from experience ; just pointing out other resources that have additional information -
Will this work with XT1572? Just confirming.
This is not a traditional TWRP zip file. It is a backup file. You need to unzip it and put it in the backup directory. You then restore backup, choose the nph25-200-22. . . directory, and away you go!
stevejohnson42 said:
See this thread :
https://forum.xda-developers.com/moto-x-style/general/guide-xt1575-update-to-nph25-200-22-t3680477
The OP will need to comment - he may be coming from a rooted stock ; at least according the the thread noted above - if you have installed a custom ROM ; there are other steps besides just trying to flash this
I have NOT tried the OP's method or the referenced thread - so I cannot really speak from experience ; just pointing out other resources that have additional information -
Click to expand...
Click to collapse
kelru2000 said:
This is not a traditional TWRP zip file. It is a backup file. You need to unzip it and put it in the backup directory. You then restore backup, choose the nph25-200-22. . . directory, and away you go!
Click to expand...
Click to collapse
Ah, sure, OK, that makes sense, just wish that had been explained somewhere. I'll give that a shot tonight, thanks!
bussemac said:
Ah, sure, OK, that makes sense, just wish that had been explained somewhere. I'll give that a shot tonight, thanks!
Click to expand...
Click to collapse
Success? Some people have reported bootloops due to a firmware problem. I'd like to know how it went.
ptn107 said:
Success? Some people have reported bootloops due to a firmware problem. I'd like to know how it went.
Click to expand...
Click to collapse
Well it worked, sort of. It booted to stock but it wasn't stable and the play store kept crashing, I tried all the usual stuff for that, clear services & play store data, uninstall updates, finally tried a factory reset and now I'm stuck in TWRP bootloop, even if I reinstall this image.
So very much YMMV.
bussemac said:
Well it worked, sort of. It booted to stock but it wasn't stable and the play store kept crashing, I tried all the usual stuff for that, clear services & play store data, uninstall updates, finally tried a factory reset and now I'm stuck in TWRP bootloop, even if I reinstall this image.
So very much YMMV.
Click to expand...
Click to collapse
Thankfully the 7.0 stock firmware is available now. I wiped and clean flashed it and it works perfectly.
https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142
the link is dead
someone can help, sharing a new link? thank you

Mate9 MHA-L29: OpenKirin experiences

Hey all,
I love stock android! So when i read about OpenKirin I was excited. Did anyone use this to install LineageOS on our mate9 successful? What are your experiences?
I have another question as well: I changed my model to the MHA-L29, rooted with a custom recovery.
OpenKirin says it needs to have the stock one. Does anyone have a link to the stock MHA-L29 recovery and a guide on how to install it?
dekraan said:
Hey all,
I love stock android! So when i read about OpenKirin I was excited. Did anyone use this to install LineageOS on our mate9 successful? What are your experiences?
I have another question as well: I changed my model to the MHA-L29, rooted with a custom recovery.
OpenKirin says it needs to have the stock one. Does anyone have a link to the stock MHA-L29 recovery and a guide on how to install it?
Click to expand...
Click to collapse
First off, this thread probably belongs in Q/A.
Moving on:
I've run all 3 provided ROMs, Carbon as my daily driver and Lineage and RR for testing various things. They all work pretty well.
For stock recovery & ramdisk, download your current firmware (or if you've run other Treble ROMs as well, the version that corresponds to your current build number in Settings / System / About Phone) using Firmware Finder - you only need the main update.zip for this. You'll also need one of the utilities for extracting them. There's Huawei Update Extractor (I think that's what it's called anyway) for Windows, or https://github.com/marcominetti/split_updata.pl for Linux / Mac. Extract the ramdisk and recovery ramdisk images and there you go.
Installing those is a matter of rebooting into the bootloader and running:
fastboot flash recovery_ramdisk recovery_ramdisk.img
fastboot flash ramdisk ramdisk.img
(The name for recovery_ramdisk.img may vary a bit - the windows app will extract it as RECOVERY_RAMDIS.img.)
From there, just follow their instructions. If you have any problems, hit up the Telegram chat linked off the site, someone will be willing to help.
@irony_delerium, thank you very much. That sounds like something even I can do without too much problems
How do you like it, being on LineageOS?
dekraan said:
@irony_delerium, thank you very much. That sounds like something even I can do without too much problems
How do you like it, being on LineageOS?
Click to expand...
Click to collapse
Like I said in my original reply, my daily driver is Carbon; the Lineage builds I've only run briefly because NFC wasn't enabled, but the CarbonROM builds there have it. I use Google Pay every day, so it's kind of a requirement for me.
With that said, the only thing that's got issues for me is the camera app, and most of the blame for that is with Huawei. It generally works, but it'll close & restart often when switching modes or trying to start a recording.
I know there are various other minor issues with recording video in all 3, again because Huawei. (They put together bum codecs, and then patched the system side of the EMUI media stack to deal with the bum codecs, instead of fixing the codecs.)
Also worthy of mention (especially because I see people asking about this all the time): there is no VoLTE support. The devs are aware of it. Unless you're on a network that is pure LTE, it's mostly a non-issue. If you are, it's probably a deal breaker.
Getting on from there, they're all clean Android experiences, without the overbearing weight of EMUI. They don't try to pull some of the things EMUI did - the final breaking point for me was when it insisted on terminating apps in the background regardless of how much you might actually be using them. (In my case, AdGuard as a VPN service.)
Dear Sir
How Can I Revert to Stock Emui?
I am on Lineage baeta 4 ROM.
With Stock Recovery.
Tried Update and Hwota Methods but no Success.
I have Searched Everywhere.
Please Do A Step By Step Guide for Newbies.
Regards
talpur1 said:
Dear Sir
How Can I Revert to Stock Emui?
I am on Lineage baeta 4 ROM.
With Stock Recovery.
Tried Update and Hwota Methods but no Success.
I have Searched Everywhere.
Please Do A Step By Step Guide for Newbies.
Regards
Click to expand...
Click to collapse
Some comments before, Huawei Firmware Extractor. Extract system.img from the stock rom you used before flash Lineage.
Flash stock system.img in fastboot.
I have downloaded and tried to extract 4 roms but The Extractor tool is Giving error.
Its Giving invalid Hearder crc error.
talpur1 said:
I have downloaded and tried to extract 4 roms but The Extractor tool is Giving error.
Its Giving invalid Hearder crc error.
Click to expand...
Click to collapse
Go to settings in the app and disable CRC checking. (Bug in the app.)
I was on OldDroid's OpenKirin, but today switched to Carbon Beta 2 from https://openkirin.net/download/. This installed without problems and I did a hard reset as part of installation. The earlier version worked very well, except there were a few bugs. I haven't found any bugs in this ROM yet.
Random question: Does anyone know if it's safe to go from one build to another directly? I'm trying Lineage but would like to give Resurrection Remix a go. The instructions say that you should be coming from EMUI...
Thanks
jellmoo said:
Random question: Does anyone know if it's safe to go from one build to another directly? I'm trying Lineage but would like to give Resurrection Remix a go. The instructions say that you should be coming from EMUI...
Thanks
Click to expand...
Click to collapse
It's fine to go between them, provided you reload the stock ramdisk (if you installed Magisk) & factory reset before booting into the new ROM.
irony_delerium said:
It's fine to go between them, provided you reload the stock ramdisk (if you installed Magisk) & factory reset before booting into the new ROM.
Click to expand...
Click to collapse
You can switch between the Custom Roms. I always do. Backup your data on the data partition via USB to PC, go to TWRP do a factory reset and then install the new image via fastboot. Reboot and rejoice
mcc2005 said:
You can switch between the Custom Roms. I always do. Backup your data on the data partition via USB to PC, go to TWRP do a factory reset and then install the new image via fastboot. Reboot and rejoice
Click to expand...
Click to collapse
TWRP only works right on a Huawei device if you're either decrypted or running EMUI. (On a custom ROM, with an encrypted device, TWRP doesn't even start up - it locks up at the splash screen.)
Factory reset using stock recovery. Only using stock recovery. The OpenKirin team will not support any other configuration.
yes you are right. but there is still the possibility to do these things with a patched TWRP. I use this for my Mate 9 https://drive.google.com/file/d/1h50RJ6LNNSEVW9CS16C0NjeP7ZZNTECE/view?usp=sharing
mcc2005 said:
yes you are right. but there is still the possibility to do these things with a patched TWRP. I use this for my Mate 9 https://drive.google.com/file/d/1h50RJ6LNNSEVW9CS16C0NjeP7ZZNTECE/view?usp=sharing
Click to expand...
Click to collapse
And the reason why I say anything is because the 2 most common problems I see are:
1) "I'm on Jio, where's my VoLTE?"
2) "I used TWRP and (it's not working | I screwed up | it's broken)".
The response to the first is universally, go back to stock.
The second, restore your entire stock firmware and then follow the instructions exactly as they are written.
With root, you can back up your apps with Titanium. I haven't had good luck with backing up settings with Titanium and after attempting to restore settings, I usually wind up wasting an hour or two and then factory-resetting and just reinstalling the apps. Now I don't even bother backing up settings, but just back up my apps. Even then two or three seem to be botched but uninstalling/reinstalling those will fix that problem. (It isn't always the same ones, either; not sure what causes this). This approach avoids the pain of configuring apps, e.g. travel app usernames and passwords, as well as preserving messages and the like. The biggest nuisance for me is that I carry around 40 unread Amazon books, which have to be sent to the phone (and I'm not so good at remembering which ones I've already read out of the more than 500 in my account), and I carry a bunch of google offline maps, which have to be manually recreated. Lastpass helps with login information too.
In my most recent (Carbon B2) install, I didn't bother with the backup but installed everything fresh and I had a fully functioning phone with 99% of the configuration I like within 2 hours, since I'd been pretty careful to put all the passwords and so on for my roughly 80 apps into a secured text file, as well as backing up my Nova launcher settings.
Hi guy's I got a question if anyone can help me out
I'm on MHA-L29 8.0.0.360 (c567)
No custom rom but I got root with supersu
How can I install this carbon rom I try allready but twrp ask me on what partition I want to install the .img file and It shows bunch of it
I'm running twrp latest by pretoriano
Thank you very much guys
Caguayote said:
Hi guy's I got a question if anyone can help me out
I'm on MHA-L29 8.0.0.360 (c567)
No custom rom but I got root with supersu
How can I install this carbon rom I try allready but twrp ask me on what partition I want to install the .img file and It shows bunch of it
I'm running twrp latest by pretoriano
Thank you very much guys
Click to expand...
Click to collapse
Restore your stock ramdisk and recovery partitions. (I'd actually start with a full restore to stock firmware first: get your vendor patches in order. 8.0.0.369 is available for most phones on c567, 370 might be available.)
Factory reset using stock recovery. Flash with fastboot. Magisk for root & SafetyNet.
irony_delerium said:
Restore your stock ramdisk and recovery partitions. (I'd actually start with a full restore to stock firmware first: get your vendor patches in order. 8.0.0.369 is available for most phones on c567, 370 might be available.)
Factory reset using stock recovery. Flash with fastboot. Magisk for root & SafetyNet.
Click to expand...
Click to collapse
do you know where can i download the stock ramdisk and recovery partition for mate 9 i was running 8.0.0.369 sorry i put 360
im stuck on twrp splash screen and i cant go to access my backup file to restore and i only access fastboot mode
but my phone says unlocked then frp says lock thanks for all your help
Now i'm using android 7.0. based rom aur 2.3, if i want to install that stock android rom, do i have to flash android 8 based twrp?

[H910][Oreo][Stock][Rooted] AT&T LG V20 Stock Oreo rooted flashable zip

Good Morning
New: Well AT&T updated us to Sept Security patch
here's the new Stock rooted rom > H910_20h_Oreo_full_rooted.zip > https://www.androidfilehost.com/?fid=1322778262904015326
Tested by @darkknight200
i dirty flashed over the 20g rooted setup. It booted up fine and works like normal.
Now have to debloat att apps and restore twrp. This time i used twrp app to restore twrp right in system and it worked properly. Saves the hassle to go into fastboot to push twrp.
All in all those are minor inconveniences, The zip is fine.
Thanks allot man.
Click to expand...
Click to collapse
After @NotYetADev posted his VS995 rooted Oreo We decided to give it a try on the H910.
It's not perfect but it does work. You'll need to Format Data and flash the H910_20g_Oreo_full_rooted.zip + the Newest - H910_mk2000 kernel from recovery-twrp-h910-2018-10-18.img
Your phone will be wiped and updated to Stock rooted Oreo so backup your phone first!
If you have never rooted your H910 you'll need to use the guide here first > https://forum.xda-developers.com/v20/how-to/root-h910-v10m-t3664500
Note: when you get where you would flash 10r just use my rom instead. Don't forget to flash the kernel after the rom
Note2: Flash TWRP again before you reboot (Install / Install Image / recovery-twrp-h910-2018-10-18.img to Recovery
It's also recommended to use the new TWRP for Oreo found here > https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239
Note: you'll have to flash TWRP back to the phone after flashing the rom and kernel because it installs stock recovery.
If you have any problems getting DATA on any sim other than AT&T check this post to fix your APN > https://forum.xda-developers.com/showpost.php?p=79619740&postcount=244
Thanks @StrikerTheHedgefox
After your phone is setup be sure and install the Magisk apk
Hide unlocked Bootloader warning boot screen by 4shared < This removes the ugly pink and black screen on reboot. I tested it and it works great
Huge thanks go to @darkknight200 and @askermk2000 for the Idea and the kernel.
thank u. but does the fingerprint work and what are the bugs if any
Yes fingerprint scanner works
Side note you'll have to flash twrp again
Use this version > https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239 and you should have no problems
aminjomaa13 said:
thank u. but does the fingerprint work and what are the bugs if any
Click to expand...
Click to collapse
Sent from my PH-1 using Tapatalk
if i have root then cant i just use flashr or another flashing app for twrp
aminjomaa13 said:
if i have root then cant i just use flashr or another flashing app for twrp
Click to expand...
Click to collapse
I installing twrp img from twrp just after flashing the ROM would do the trick.
if i dont have an at&t sim card ,will this rooted rom restrict some function such as wifispot 。。。。。。
Test flashed this on my h915 device. I have working full data and root and everything works.
Just gotta debloat it myself
running very smooth
zkm15 said:
if i dont have an at&t sim card ,will this rooted rom restrict some function such as wifispot 。。。。。。
Click to expand...
Click to collapse
Its the Stock Oreo rom dump .. only thing changed is a patched_boot.img and the Eng_aboot.img
in fact the original files are in the rom too they just don't get flashed
everything should work as expected
battery life took a hit what are the optimal CPU GPU values to optimize battery without totally crushing performance
anyone else pass both safetynet test on magisk 17.2 on h910 oreo?
It seems to be failing most of the time for me.
aminjomaa13 said:
battery life took a hit what are the optimal CPU GPU values to optimize battery without totally crushing performance
Click to expand...
Click to collapse
this question is better left in the Kernel thread > https://forum.xda-developers.com/v20/development/h918-h910-us996-ucl-mk2000-kernel-t3708330
I never mess with kernel setting aside from the Screen settings
darkknight200 said:
anyone else pass both safetynet test on magisk 17.2 on h910 oreo?
It seems to be failing most of the time for me.
Click to expand...
Click to collapse
safetynet test for non at&t sim card ? it is a problem on android N .
Awesome! Glad this works on other devices! Good job, XDA!
NotYetADev said:
Awesome! Glad this works on other devices! Good job, XDA!
Click to expand...
Click to collapse
ya the zip method you did with modifying only 2 files in the whole firmware should work on all other dirtysanta devices.
Edit:
i re-flashed the h910 oreo and setup and debloated everything again. Now I am passing safetynet with no problems and certified device. very weird.
One thing to note, this is on the early build of Oreo TWRP that I was able to flash properly vs using nouget twrp the first 2 flashes that gave me bugs each time.
darkknight200 said:
ya the zip method you did with modifying only 2 files in the whole firmware should work on all other dirtysanta devices.
Edit:
i re-flashed the h910 oreo and setup and debloated everything again. Now I am passing safetynet with no problems and certified device. very weird.
One thing to note, this is on the early build of Oreo TWRP that I was able to flash properly vs using nouget twrp the first 2 flashes that gave me bugs each time.
Click to expand...
Click to collapse
using Oreo TWRP flash this zip will pass the saftynet test ? it is quite a problem on
android N ,it will disable the wifispot function.
OP, I love you.
If we already have the engineering aboot and TWRP flashed, can we just flash this right over (with a data/system wipe)?
I love SuperROM but I need Wi-Fi Calling to work.
EDIT: I'm an idiot, I misread your instructions. Am I correct in understanding that this is just the stock AT&T Oreo image with aboot and boot swapped out?
sheik124 said:
OP, I love you.
If we already have the engineering aboot and TWRP flashed, can we just flash this right over (with a data/system wipe)?
I love SuperROM but I need Wi-Fi Calling to work
Click to expand...
Click to collapse
yes if you are coming from rooted h910 nougat rom with twrp, you can flash this h910 oreo zip with no problem.
All the bloat from att should be there when u boot up so wifi calling should work.
sheik124 said:
OP, I love you.
If we already have the engineering aboot and TWRP flashed, can we just flash this right over (with a data/system wipe)?
I love SuperROM but I need Wi-Fi Calling to work.
EDIT: I'm an idiot, I misread your instructions. Am I correct in understanding that this is just the stock AT&T Oreo image with aboot and boot swapped out?
Click to expand...
Click to collapse
darkknight200 said:
yes if you are coming from rooted h910 nougat rom with twrp, you can flash this h910 oreo zip with no problem.
All the bloat from att should be there when u boot up so wifi calling should work.
Click to expand...
Click to collapse
Yes just 2 files changed flash right over Nougat > I recommend you use this version of TWRP > https://s3.amazonaws.com/phoenix591/us996/recovery-twrp-us996-2018-09-23.img
it's tested by @darkknight200
clsA said:
Yes just 2 files changed flash right over Nougat > I recommend you use this version of TWRP > https://s3.amazonaws.com/phoenix591/us996/recovery-twrp-us996-2018-09-23.img
it's tested by @darkknight200
Click to expand...
Click to collapse
Awesome, downloading it now. Can you confirm a cpl things?
mk2000 kernel means that we can continue using exFAT on micro SD.
Right now I have unencrypted internal and external storage, this keeps it all the same.
Updates baseband/modem to the radio that came out with Oreo.
Will post results once I'm all set back up. I was literally about to selectively flash back to stock v10v, keep TWRP and root, let it download the OTA, and then try to get updated. This is easier.
sheik124 said:
Awesome, downloading it now. Can you confirm a cpl things?
mk2000 kernel means that we can continue using exFAT on micro SD.
Right now I have unencrypted internal and external storage, this keeps it all the same.
Updates baseband/modem to the radio that came out with Oreo.
Will post results once I'm all set back up. I was literally about to selectively flash back to stock v10v, keep TWRP and root, let it download the OTA, and then try to get updated. This is easier.
Click to expand...
Click to collapse
Yes mk2k Oreo still let's u use exfat.
The zip will update all partition besides the 2 described above. So you will be on Oreo baseband modem.

Rooted. Now wifi doesn't work. Neither do speakers.

I rooted following Maxwell's tutorial (OnePlus 7 Pro - How to Unlock the Bootloader, Install TWRP, and Root with Magisk
).
Now that all is said and done, and my phone is rooted, I noticed that:
1) The wifi does not work. It will not let me enable wifi. Just keeps switching back to off.
2) The speakers don't work.
I need to know how to fix it. What do I do?
I am new to android so I am not sure the steps needed to fix this botched install/operating system/root whatever
U prob flashed the wrong boot.img, make sure to flash the correct model and OS version.
What model and OS version do you have?
download
Bradl79 said:
U prob flashed the wrong boot.img, make sure to flash the correct model and OS version.
What model and OS version do you have?
Click to expand...
Click to collapse
This is probably an error on my end then. I chose "Global 1917 1911" but my about phone page says "1913", however, my phone also says 9.5.1 and there is no 9.5.1 (under 1913) in the link you provided. Do I need to upgrade my OS first before retrying?
jfny100 said:
This is probably an error on my end then. I chose "Global 1917 1911" but my about phone page says "1913", however, my phone also says 9.5.1 and there is no 9.5.1 (under 1913) in the link you provided. Do I need to upgrade my OS first before retrying?
Click to expand...
Click to collapse
yes you will need to upgrade, there was no 9.5.1 full zip released for us to have patched the boot.img. So update and then patch the correct OS and Model version you update to. Let us know if you have any other issues.
I swear nobody reads the threads before starting. Your wifi is disabled because your rooted boot image does not match the version you should have.
Just flash one of the kernels in the roms section, I'm using ElementalX 1.10, wifi will come back up.
Bradl79 said:
yes you will need to upgrade, there was no 9.5.1 full zip released for us to have patched the boot.img. So update and then patch the correct OS and Model version you update to. Let us know if you have any other issues.
Click to expand...
Click to collapse
Okay. That was it (flashing the wrong boot.img) It's working now - I upgraded to latest OS. Downloaded correct boot.img. Redid the root process with correct files this time, and it worked. Wifi is good. Speakers are good. Everything is good. Thanks for the help. Also, I removed any criticism of the tutorial creators in my post since it turns out I was the idiot. I'm brand new to android though so go easy on me.
djsubterrain said:
I swear nobody reads the threads before starting. Your wifi is disabled because your rooted boot image does not match the version you should have.
Just flash one of the kernels in the roms section, I'm using ElementalX 1.10, wifi will come back up.
Click to expand...
Click to collapse
I didn't read the post until after I encountered errors. I was going off of the video. One problem I had was that the video assumed I had a basic knowledge of some steps, so they didn't mention them. I did not have this knowledge since I am brand new to android. Anyways. I was able to fix these errors via the steps discussed in earlier comments. Everything is working now. I removed any criticism of the tutorial creators from this post since it turns out I'm the idiot.
Glad you got it working
Why are people even flashing boot images? Just unlock bootloader, boot twrp from fastboot, flash twrp, flash magisk, all done.
JedixJarf said:
Why are people even flashing boot images? Just unlock bootloader, boot twrp from fastboot, flash twrp, flash magisk, all done.
Click to expand...
Click to collapse
BC that is just an extra step not really needed, I haven't even flashed twrp on my device yet, if I need it I will just boot to it, it's so much easier doing this.
I always thought the same thing u did, until I just flashed the patched boot and updating is so much easier too.
JedixJarf said:
Why are people even flashing boot images? Just unlock bootloader, boot twrp from fastboot, flash twrp, flash magisk, all done.
Click to expand...
Click to collapse
Because I'm just following along with the tutorial xda put on YouTube and that's what they say to do

magisk can't find stock image, how can I upgrade and fix this issue?

I'm not sure why i have Magisk installed in a way that it cannot find the stock boot image, but that seems to be the case.
a quick search didn't turn up the stock boot image for my existing ROM version (IN2025_11_f.15)
I figure it may be easier to just update and lose root, then re-root with the new boot image, but I've had some issues doing what I thought would be easy, but turned into big issues, so before I start down this path, I wanted to ask what may be the best way to go from where I am...
(rooted with Magisk, but no stock boot.img, running build number IN2025_11_F.15, Baseband version Q_V1_P14)
...to getting onto the latest version my phone is offering (IN2025_11.F.62_2620_202301162204) and get Magisk fixed so that it then has a stock boot image, so I can update later by just uninstalling/restoring images, installing the update, then rebooting to the inactive slot, which worked fine for years.
Thanks in advance for any help/guidance doing so.
JustinChase said:
I'm not sure why i have Magisk installed in a way that it cannot find the stock boot image, but that seems to be the case.
a quick search didn't turn up the stock boot image for my existing ROM version (IN2025_11_f.15)
I figure it may be easier to just update and lose root, then re-root with the new boot image, but I've had some issues doing what I thought would be easy, but turned into big issues, so before I start down this path, I wanted to ask what may be the best way to go from where I am...
(rooted with Magisk, but no stock boot.img, running build number IN2025_11_F.15, Baseband version Q_V1_P14)
...to getting onto the latest version my phone is offering (IN2025_11.F.62_2620_202301162204) and get Magisk fixed so that it then has a stock boot image, so I can update later by just uninstalling/restoring images, installing the update, then rebooting to the inactive slot, which worked fine for years.
Thanks in advance for any help/guidance doing so.
Click to expand...
Click to collapse
Does it work if you try to update without unrooting?
JustinChase said:
I'm not sure why i have Magisk installed in a way that it cannot find the stock boot image, but that seems to be the case.
<snip>
Click to expand...
Click to collapse
That happens if you flash a Magisk patched boot image instead of booting it and then using direct install.
TheNewHEROBRINE said:
Does it work if you try to update without unrooting?
Click to expand...
Click to collapse
No. I think the update isn't a full ROM. I believe read somewhere that works when the update is a full ROM
I'm just not sure how to 'start over' to get a stock image saved so Magisk will let me restore again, without having to wipe the phone.
JustinChase said:
No. I think the update isn't a full ROM. I believe read somewhere that works when the update is a full ROM
I'm just not sure how to 'start over' to get a stock image saved so Magisk will let me restore again, without having to wipe the phone.
Click to expand...
Click to collapse
White don't you ask in the 8/8 Pro (I'm assuming that's what you have) forums if someone can provide you with a stock boot image for your current OOS version?
Note that this is an 8T forum so you don't get people here providing you with a copy.
BillGoss said:
White don't you ask in the 8/8 Pro (I'm assuming that's what you have) forums if someone can provide you with a stock boot image for your current OOS version?
Note that this is an 8T forum so you don't get people here providing you with a copy.
Click to expand...
Click to collapse
Oh, sorry.
I did think this was an 8 Pro forum
I'll find that and repost
Thanks

Categories

Resources