[Discussion/Guide][k6 power][HotPlug] Stock + Root + Customizations - Lenovo K6 / K6 Power / K6 Note Guides, News, & Dis

Stock ROM 7.0 + Magisk + Xposed
Code:
This might be my first ever thread on xda, but am a part of this community sincebirth of galaxy y, that makes me aware of most of the android ROM terms and functioning.
So recently I rooted my 4 months old Lenovo k6 power to boost up my little beast. Tried different custom offical ROMs which includes RR, AOSPX, etc.
What I observed among them was:
Performance:Overwhelming
Stability: Up to the mark
Customizations: Sufficient
Battery? : HUNGRY!
My stock 7.0 used to give 2x times battery compared to what I was getting through these ROMs. //I confirm that it was a clean flash.
Now in order to understand whats wrong with these ROMs I opened CPU-Z and had a look on it.
Everything seemed perfect except one thing!
The phone inherits a SnapDragon 430 octa-core processor AND the observation was none of the cores were STOPPED even while my phone was IDLE completely.
Check attachment to see how it looks in STOCK. I didnt take any SC while on a custom ROM but I remember it well. One may provide with in comments?
Now here comes the problem, there seems NO HOT PLUG extension.
Qualcomm by default provides it by its "mpdecison" - but the ROMs failed to provide that option nor it was available through Kernel Auditor.
Pretty sure I'm not the only one facing it.
So here's what I did to acheive my desires:
NOTE: This will ENCRYPT your device again, you need to FORMAT DATA for TWRP fucntioning!
Reverted back to Stock ROM through this wonderful guide: https://forum.xda-developers.com/k6-power/how-to/guide-t3663065
Updated to latest via OTP
Installed Magisk for ROOT
https://forum.xda-developers.com/apps/magisk
This way I got stock which gives me day long BATTERY and root which passes SAFETY NET CHECK. (Attached)
And for customizations I'll by relying on systemless magisk Xposed Module.
Any thoughts on this?

Related

Ulefone Power costume rom??????????????

Hi well today I here that the Ulefone Power will be out in some places and its a very good battery life 4 dayds with out charging it so I want to know is their any plans for costume rom this baby as this phone is very affordable and was wondering if any one is planing this me be 64bit rom?????????????????????
Dude! I second this motion! The phone's a beast but boy does the stockrom suck.
Cant wait for some talented guys to do a custom rom for this phone. Im very happy with the hardware, only the rom is a little bit wanky.
I have had this phone for three weeks now.
It's a truly fantastic device! Hardware is good, makes great pictures and the massive battery can last me for 12 hours without changing it. Let me clarify that my Note 4 was able to stay alive without my spare 3000mAh Samsung battery for no more than 4-6 hours.
The only complaint i have with the Power is that YouTube, as well as RadioYouTube are lagging here and there. I tried few tweaks form the Developer options to reduce the lag, but not much improve was noticed.
So, a good custom ROM to eliminate the issues and make it even better would make this device a real leader in reliability and satisfacton.
i dont know but i have a feeling one 6.0 is released some custom roms should come out, no point making them yet with it coming out in the next week or two (or three with the current delays), cant wait though, getting mine today hopefully!
I would like to notice that front camera on stock android 5.1 really sucks! It's just terrible, when I flashed android 6 it's way better but still it's sharphing photos to much... In video recording there is no problem so I am 100% sure that's software problem. Hope it will get solved with some custom android 6 rom . This is just an info for future developers.
custom rom
I found custom rom on needrom. It's ported from leagoo shark. I'am using it and better than stock rom. If anyone build a custom rom, i will try.
acemimerakli said:
I found custom rom on needrom. It's ported from leagoo shark. I'am using it and better than stock rom. If anyone build a custom rom, i will try.
Click to expand...
Click to collapse
how did you root/flash phone?
btijet said:
how did you root/flash phone?
Click to expand...
Click to collapse
I load twrp with sp flash and then load supersu zip file.
You can use this link http://blog.ulefone.com/how-to-root-ulefone-power/
acemimerakli said:
I found custom rom on needrom. It's ported from leagoo shark. I'am using it and better than stock rom. If anyone build a custom rom, i will try.
Click to expand...
Click to collapse
please any link , I found only ROM version from ulefone (update already received)
Is there any CM version ? Could be good to have CMTE (Theme engine)
brunoisa10 said:
please any link , I found only ROM version from ulefone (update already received)
Is there any CM version ? Could be good to have CMTE (Theme engine)
Click to expand...
Click to collapse
http://www.needrom.com/download/leagoo-port-for-power/
No CM version.
I heard that Ulefone Compagny has given some devices (Ulefone Power) to ROM Developpers.
So We could maybe get some custom roms or port from another devices in a early future
Rooting uleFone Power
Hi all. As posted earlier, there are instructions on the Ulefone blog on how to root the device.
http://blog.ulefone.com/how-to-root-ulefone-power/
Here's a quick rundown. I'm also uploading all the tools I downloaded and used to my Google Drive.
https://drive.google.com/open?id=0BzqEmGyNP_v6cWdZVU5rRnpmbDQ
If you rather get the things directly from the Ulefone Blog then do so.
DRIVERS
Based on checks, it's probably best to install the driver directly. One of the instructions given is to turn off the phone and connect it to the PC. When I did this nothing happened, and I only started to get some results when I turned on the phone while connected. At this point it flashed very quickly that there was an MTK device but drivers weren't installed. After installing the drivers on the system and doing this again, it managed to install the drivers properly. I also noticed that booting the device with VOL+/POWER gave me the option of installing the drivers also. As stated on the site - you may need to disable driver signing for Windows 8/10.
TWRP
This part is pretty straightforward. Unzip all of the files. Run the SP FLASH TOOL. Enable USB CHECKSUM in the options for SP FLASH TOOL. Locate the scatter file for TWRP and hit the download button while the phone is off. If nothing happens for you, simply turn the phone on while it's connected and the download button is already pressed. It will prevent the phone from booting and flash TWRP directly. You may go into TWRP by holding VOL+/POWER until you get the menu for normal/fastboot/recovery and select recovery. Please bear in mind that at this menu, the VOL+ cycles the options and the VOL- selects/confirms the option.
ROOT
Once you've completed the TWRP installation, start TWRP and allow modification of the system partition. Select the options to reboot into the system and then swipe to install SuperSU and root the device. That's it - you're done!
Screenshots and photos will follow.
Hey there!
Any news of a custom ROM for the ulefone power?

Help!!! I am Confused!!

I bought a LG V10 today i dont know if its used or new (LOL) any way to find that out i checked IMEI says its orignal talked to people at LG USA they said its Original Here are my questions:
1) How to know if your phone is Legit like New + Lasting?( in my country they replicate used to orignal or fake to orignal)
2) How to Root LG V10? (i tried it with other phones i broke them)
3) Suggest Some Recommended Apps and ROMS?
4)I have seen a youtube video of xdadevelopers they were talking how you can overclock or under clock your device can i do that with my phone?
5)Last Question How can i myself from the infamous Bootloop? (Any Suggestion, Tricks Ways)
I am new here i need your help for not doing a rookie mistake....
1) Get the LG Phone Info app on the Google Play Market and as long as that shows "OK" in the Original info (the first box after you click the Get Information button) then your device is an original and not something that's been modified on a firmware level.
2) If you have Lollipop or Marshmallow rooting is fairly easy by comparison to Nougat. If you have Nougat on it already things are basically a stop - there is no working root for Nougat at this moment IF the device has been upgraded to Nougat using T-Mobile's OTA direct from them. Once that's been installed there's no turning back and no working root at this point but some devs are working on it, no guarantees they'll ever be able to create one.
If the device has Lollipop or Marshmallow on it you can get it rooted. The best course of action is to go from Lollipop to Marshmallow (the last Marshmallow build is 20l and that's an "L" there, lowercase, not 1 or i/I) and then what you'll need to do is get TWRP on it (that step is critical) then you would flash this modified update.zip to get to Nougat build 30b on it. runningak3d modified that update.zip file so it does NOT overwrite the recovery partition and you get to keep TWRP installed for flashing purposes. If you use T-Mobile's official OTA update.zip you'll be stuck, not able to flash anything including TWRP, or get rooted, etc.
So, again, the process is get to Marshmallow 20l, then get TWRP installed - at that point root is not necessary just to get the modified 20b update.zip on it. Then use TWRP to flash that modified 20b update.zip at which point it'll be Nougat, and THEN you can flash SuperSU with TWRP and you end up with a V10 running Nougat and rooted, that's the only method at this point.
runningak3d said he (or she, sorry, I just don't know) would try to create another modified update.zip which is pre-rooted so when installed you've got root/SuperSU ready to go but it's barely a minute to install SuperSU manually after flashing that modified 20b update.zip so it's not really a big issue there.
3) There are no custom ROMs for the V10 at this point, no Lineage, no AOSP, nothing really. There are some modified stock ROMs iirc but nothing that's totally custom and we V10 owners are still hoping some dev will take some time and create an unofficial Lineage build for the V10 based on Nougat (or even Marshmallow, I don't really care which Android version it's based on just that it's Lineage through and through). It seems pretty screwy that nobody seems to care about the V10 enough to have created a custom ROM but that's how it goes sometimes. The V10 is like an LG G4 on steroids in some respects, basically the same hardware overall with some minor differences (the second screen, of course, but I don't even use that on mine so I don't care about it at all).
I just wanted Lineage because it's so lean and efficient compared to any stock ROM and of course the potential for having a custom kernel with more governor support and other aspects is the big draw for me so, the hope remains that someone out there will take some pity on us woeful V10 owners and drop a Lineage build someday.
As for apps, well, that's entirely up to you and what you use your V10 for, and since nobody knows that but you then it'll be up to you to decide what kinds of apps you're going to be looking for.
4) Over-and-underclocking requires a custom kernel that allows for such things, and the stock kernel that's available (I think there was one custom kernel but it's just a modified stock one with limited additional capabilities) simply doesn't allow for such alterations. The V10 is quite fast on its own natively so, I can't imagine why someone would need to overclock it - I can understand WHY someone would WANT to do it, of course, but as for an actual need to do it, nope.
As for underclocking, that would save battery and be what I'd call a need in some respects, but again there just doesn't seem to be any developer out there that gives a damn about the V10 sadly. I wish I had spent more time learning how to create custom ROMs over the years and trick out some kernels as well using the provided source from manufacturers of these smartphones but I never did.
5) There is no way to prevent the potential bootloop issue which affects the G3/G4/G5/G6 (I saw one report so it could be bogus for the G6) and also the V10/V20 (seen two reports for the V20) and the Nexus 5x because it's a hardware manufacturing defect related to how the Snapdragon SoCs are mounted on the motherboards. There's nothing that you can do about it and there's no way to know for sure if the V10 you have will develop problems because of it or not, all you can do is use it and be done with it and hope for the best. Again, there is no fix and there's no way to know or prevent it from happening so, no matter what so called "fix" you read about or see a video about, it's all BS and best avoided.
My recommendation: since you just got the V10, go to LG's website and register the V10 in your name (might have to create an account) and then say you bought it in March, April, or May of 2017 (just a few months ago) and that will give you warranty protection through at least mid-2018. If you do that and it does bootloop on you, LG will replace it through the warranty period. Don't register it and you're out of luck if it does bootloop on you.
Hope this helps...

[V2][Root][G950U/W]PartCyborgRom - Root for Snapdragon S8 with Custom Rom

SamFail presents...
PartCyborgRom
BQL1
A Rooted Custom Rom
For G950U/W, Bootloader Revisions 1 or 2 only any higher are not currently rootable or vulnerable to this exploit ​
Updates
New Release and a new OP that I hope is easier to read.
Send feedback or suggestions on improvements to me via pm here or on telegram.
Heads Up
You may notice that the BL version of this release is different than the system rom part.
The rom version is in fact BQL1, but the BL is a new version of AQK2. The reason for this is because
the latest combination, ARA1, has a number of sensors not working. I figured out a fix but it requires splicing
stuff in from other versions, and it didnt feel like the battery lasted as well. I am still testing though and
the next release if its ready will come with ARA1. This is not the same BL as the previous
release though, so if you upgrade also flash this new BL!
Thanks!
Featured Modifications
Deodexed
Deodexed for all devices.
I found a way that works!
It should keep working as long as nougat
(is that a haiku?)
Xposed Preinstalled
PCR now comes out of the flasher with xposed pre-installed!
NOTE: Xposed Installer may crash on first boot. It will not crash after setup finishes and you reboot
New Boot Animation
Another great one from @Ryan-refoua.
This one is my favorite so far.
JamesDSP
I added another DSP style audio mod. JamesDSP is similar to V4A in how it operates and what features it has, but it has some really awesome features that have made me a fan and a regular user. Among other things, it has a better convolver (IRS processing) implementation, and its bass boost is significantly better than v4a. If there are things you like about V4A you can use both at the same time.
ITYBP Modded YouTube
A last minute addition, this is a really nice youtube mod brought to you by @laura almeida, @Razerman and @ZaneZam. It features some cool additions like native adblocking (no more xposed module), overriding your max youtube resolution (you can watch 4k videos on your phone, but not 4k hdr). I have been using it for a while and really like it. A big thanks to them for letting me include it with PCR
Improved Debloating
Found better stuff to delete. Added back some stuff I took out before that some of you asked for.
If you find something missing that you want back, pull it from the stock rom and install it in /system/app or /system/priv-app, wherever you got it from.
Improved Battery Life
Thanks to some battery sleuthing by @TheMadScientist, this release comes with a nice big bump in efficiency. With just some very minor tuning using amplify and a service disabler, I can get around 1%/h drain.
Performance Improvements
That increased battery life does not come at the cost of performance. In fact performance is better too. Part of that is due some personally tested build.prop tweaks. Another part is some data optimisation scripts that now run at boot. You wont notice those, but they are there doing their thing.
Other Features
New for first time flashers
- Pre-Rooted with SuperSU installed
- CSC OYN pre-installed. Tested working on several carriers
- RCS and VoLTE icons removed from status bar.
- High quality audio mods, including
- Viper Audio (V4A)
- Dolby Atmos from the Axon 7
- Pandora hifi audio framework
- Native Google Dialer & Contacts support, including local search, spam call blocking
- Oreo 8.1 Emoji Icon Set
- Custom Lockscreen Clock font
- Stock system display fonts replaced with Apple's original San Francisco Font
Special Thanks
- @ahiron and @Zackptg5 for the killer sounds from V4A and Dolby Atmos Mods!
- The Aiur crew for Pandora (now a legacy mod but works great on the s8)
- @syndre for the Google Dialer and Contacts framework mod
- @rayan-refoua for the beautiful Tech Lines Custom boot and shutdown animations!
- Last but not least, my new friend @laura almeida, along with @Razerman amd @ZaneZam for letting me include the iYTBP - injected YouTube Background Playback Mod
- everyone who tested
Warnings/Disclaimers/Known Issues
- 80% Battery life like every other rooted US snapdragon device
- Flashing on a USB 3.0 port will likely cause corruption in your flash that can cause kernel panics, loss of root, and occasionally very strange other errors. If you get something like this, its not the rom its a hardware conflict that can only show up with larger images like are used in SamFail flashing. See the section below on Kernel Panics for more.
- If there is an app or apk from the stock rom that you wish you had installed, the best solution is to extract it from your stock rom image and copy it to the same place in /system using a root file manager.
SamFail Rooting Process
and Rom Installation
WARNING: THE FOLLOWING WILL ERASE YOUR WHOLE PHONE
If you have a SDCard, remove it from your device. Occasional firmware incidents have wiped SDCards in the past. It has neer happened to me, but I have a backup of my sdcard so I can be a little more risky. Better safe than sorry.
Prepare the Following:
- complete stock rom at your bootloader rev in case things dont work
- Everything backed up
- Both Prince Comsy Odin, and Regular Odin for flashing stock
- A USB 2.0 Port. If you attempt to flash with a USB 3.0 port it may work, but if you get kernel panics, or unexpected bad behavior and/or crashes your usb3 is absolutely to blame. some people get lucky and suceed after a few tries, YMMV. If you can not acquire a machine with a usb2.0 port, get a usb2.0 hub and run your phone into that & that into your machine. Reports are that has made things work for some, but we get few reports back.
What is my Bootloader Revision?
Your bootloader revision is part of the baseband build number of the firmware you are currently running. Lets use this rom as our example. The full build number is as follows: G950USQS2BQL1
Start from the right and count 5 characters back. See that 2? That is the bootloader revision for the firmware that came with this rom. But we are not flashing the BQL1 firmware (or Baseband), We are using an older version because it works better. The version we are flashing is: G950UEU2AQK2. Can you tell which revision it is?
Is my Phone Compatible?
Is it a G950U? Is it a G950W? If you answered "yes" to one of those questions, then the answer is "yes". That being said, flashing this rom if you are on bootloader revision 1 will upgrade your bootloader revision to 2, which means that any previous rom you were running wont work, so be prepared by having a copy of stock for bootloader version 2. If you don't want to move to version 2, you can still run the latest PartCyborgRom though, just use the G950UEU1AQk1 BL_ tar under Old Downloads in place of the one that came with this one. It will work just fine. However if you are unsure I suggest you go ahead and upgrade, there are not really any benefits to staying on 1 at this point.
Steps to Root
1) Download and unzip AP Part 1 and BL Part 2 zip files.
2) Download and unzip Prince Comsey Odin and start it up
3) Reboot device into Download mode and connect it to your pc
4) Open Comsy Odin and only add the AP Part1.tar.md5 file. Select only the following options:
- "Auto-Reboot"
- "F-Reset Time"
- "Nand Erase All"
NOTE: Odin will freeze while checking the AP tar.md5 hash.
Be patient, it will come back. If your computer is old this will take even longer.
5) Click "Start" and wait for the system.img.ext4 file to flash fully to your device. This will take a while too.
ATTENTION
When the flash finishes, this is when the SamFail magic happens. Instead of saying "Failed (Auth)" like it should, the device will crash into upload mode with "Unknow Error".
If your device does not do this, and just says "Failed (Auth)" or something similar and stays in download mode, you need to start again from the beginning, but using a different set of usb ports as you have suffered from the usb3 corruption.
When you see the upload mode page, do the 3 button salute to reboot into download mode again.
WARNING: When you reboot from upload mode, it wont look like download mode. You will see an error.
When you reboot back into download mode, your screen will say that you had a failed update and you need to do emergency repair or take your device to a service center.
Rest assured, your phone is actually in download mode, and Odin will have recognized it and said "Added!" along with the com port lighting up underneath the progress bar. Just continue the process. It is safe to do so and that error will go away after the next step.
6) Close and re-open Comsy Odin or hit the reset button, and add BL_PartCyborgRom-BootLoopEdition-<version>.tar.md5 to the BL section.
7) Leave the default checkboxes for "F Reset Time" and "Auto Reboot" checked. Uncheck "Nand erase all". Click "Start" and flash the BL (part 2) to your device.
Note: If you forgot to uncheck nand erase all, don't worry. You are just wasting time doing something again that you already did, the outcome is the same. "All" in "Nand Erase All" means "all userdata", which means cache and, well, userdata. Nothing else is deleted.
8) Wait for the flash to finish . It won't take very long at all as the files are small.
9) When it has finished, Odin will say PASS and your device will reboot into recovery.
From this point forther the scary download error message will be gone for good (or until next flash). Don't go looking yet though, you have more work to do to get root.
Warning: Failure to follow this step could lead to a corrupted instance with no cell coverrage
10) When in recovery issue a factory reset. This ensures that your device has a userdata and cache partitions that are valid, and that the csc is processed correctly. Failure to do the reset could cause issues with either.
11) Boot the device as normal. Wait for it to come up. Its deodexed so it will take longer than even your average odexed rom.
All done!
FlashFire Instructions
- Get the ROM on your phone and unzip it
- Open up FlashFire
- Add a Wipe task, select the top 3 items only
- Select Flash Firmware and load up the AP_PartCyborgRom-BootLoopEdition-<version>.Part1.tar.md5 file to flash your new system
- Select Reboot to Recovery
- Make sure "Inject Root" is NOT checked
- Press go. Wait for the rom to flash and your device to reboot into recovery
- From recovery do a factory reset
- Then select reboot to Download Mode
- When device reboots into Download mode, flash BL_PartCyborgRom-BootLoopEdition-<version>.Part2.tar.md5
You have to use odin for the BL file because flashing bootloaders in FlashFire is a bad idea.
Dirty Flashers
Yes, you can dirty flash this rom to upgrade, however it is problematic and can cause issues. I did it for a long time, but my install was a mess by the time I gave up and reset.
To dirty flash, follow your preferred method of flashing above, but skip the Wipe step.
Odin
Skip "Nand Erase All" during the Part 1 flash. Do everything else the same
FlashFire
For the first Wipe task, instead of selecting the top 3, select only Dalvik like the second wipe task.
NOTE: This procedure is ONLY for people upgrading from an earlier PartCyborgRom version. If you are coming from stock you can not dirty flash because you userdata is encrypted which is not supported by the Factory firmware. If you are coming from other rom, or stock, I have no idea man but don't look at me if it blows up.
ANOTHER NOTE: This method of flashing is unsupported! If you do this and you have issues, you are on your own. If you think they are the rom, then back up your entire rom, wipe and reproduce them.
Help! I Got a Boot loop!
If you get a boot loop or your device hangs at boot, try the following:
1) Reboot to recovery and factory reset again.
To get to recovery hold power+vol-down until screen goes black, then wait till upload mode (press power key for 7+ secs) comes up. Then press vol-down+power again and hold it till it reboots and as SOON as the screen goes black switch to holding vol-up+power+bixby. Hold it for 5-7sec then let go and you will wind up in recovery mode. If this doesnt help, or you can't get to recovery because you cant press the buttons right, proceed to the next step.
2) Try flashing just Part 2 (the BL) again. not only will this get you back in recovery, it will also format your cache again. Its worth a shot and doesnt take long.
Kernel Panic, Invalid Argument
Start Over
Go back to the beginning and do everything again. If it fails again, even in a slightly different way this time, bad interaction between the s8 and your USB port/controller/cable/etc are causing the image to be corrupted as its being written to disk. Try the following:
1) New USB Ports. If you have them, use a different set of usb ports (not the one next to it, but one further away). Its possible that that will be your "good" port, and that will be enough. Lots of machines also have some USB3 ports and some USB2.
2) New Cable. Its less likely, but maybe a new cable will help. Do the whole thing over with a new cable.
3) Try a few times. It sounds silly, but people who have had this issue have reported that eventually it just works. Try a few times until you get sick of trying. If you try like 10 times it probably wont work on the 11th though.
I Dont Have Another USB Port!
Try to borrow your partner/spouse/roommate/friends computer for a quick flash. Ask about the USB ports though, because another 3.0 port may not help you.
If you can't get someones computer, you can purchase a USB2.0 Hub online or at your friendly neighborhood electronics store. They arent very expensive, and I have heard positive reports from people saying it did the trick.
None of that Worked! I'm Screwed!
No you probably arent. I can count on one hand the number of people who someone couldnt get this working eventually. Some of us will be here to help. Check out our telegram channel, where people will be around that can help you. Its right here!.
And they all rooted happily ever after.
The End.​
XDA:DevDB Information
PartCyborgRom, ROM for the Samsung Galaxy S8
Contributors
partcyborg
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 4.x
Based On: TouchWiz/Samsung Experience
Version Information
Status: Stable
Current Stable Version: BQL1
Stable Release Date: 2017-12-10
Created 2017-12-11
Last Updated 2018-2-10
Downloads
BQL1 (G950U and G950W)
AP_PartCyborgRom_G950U_BQL1.Part1.zip
[Alternate Mirror]
BL_PartCyborgRom_G950U_BQL1.Part2.zip
[Alternate Mirror]
Other Downloads
Remove OTA apps, downloads and debug messages
Remove RCS and VoLTE Icons Zip (Flash in FlashFire)
Odin3-v3.12-PrinceComsy-.zip
[/SIZE]​
Previous Versions
G950USQU2BQK5
Bootloader Version 2
AP_PartCyborgRom-G950USQU2BQK5_Part1.zip
BL_PartCyborgRom-G950USQU2BQK5_Part2.zip
Alternate Download Links
Bootloader Version 1
AP_PartCyborgRom-BootLoopEdition-G950USQU1AQK3.Part1.zip
BL_PartCyborgRom-BootLoopEdition-G950USQU1AQK3b.Part2.zip
SM-G950W
AP_PartCyborgRom_G950WVLU1AQJ4.Part1.tar.md5.zip
BL_PartCyborgRom_G950WVLU1AQJ4.Part2.tar.md5.zip
SM-G950U AQI6v2
AP_PartCyborgRom-AQI6_Part1.tar.md5.zip
[This was updated from the original Part2]
Download BL_PartCyborgRom-AQI6_Part2r3.tar.md5
​
Flashed fine through flashfire(AP only) was a bit worried because after I flashed the bootloader I got a kernel panic upload mode, but I reflashed the bootloader and it worked out fine. Running it for a few hours now and I noticed right away the difference in battery drain, as in, amazing job at extending the battery life. Thanks for your work, look forward to Future updates :good:
Update: only bug I've found is auto rotate doesn't really work, and internet connection issues(might be my network)
I'm new to SIM unlocked and haven't rooted since s4 so possible newb question but
Can I use this rom to root unrooted AQH3?
I'm on sim-unlocked G950U.
Thanks for any help.
Sent from my SM-G950U1 using Tapatalk
Followed everything and when it went to go reboot the SAMSUNG GALAXY S8 logo popped with the little custom lock but its almost as if its just there like its not really rebooting just a screenshot of it it wont go away after a certain time period or anything,I also tried re-flashing the BL and it still didn't boot up as it should of. Any idea on what I should do?
I will test this with my unlocked g950u1 on tmobile
OMEGAHORSE said:
Followed everything and when it went to go reboot the SAMSUNG GALAXY S8 logo popped with the little custom lock but its almost as if its just there like its not really rebooting just a screenshot of it it wont go away after a certain time period or anything,I also tried re-flashing the BL and it still didn't boot up as it should of. Any idea on what I should do?
Click to expand...
Click to collapse
Same here.
I tried the first method (fully stock) and it failed badly to where download mode did not work, had to use Smart Switch emergency recovery
First attempt without flashing CSC on TMo resulted in Kernel Panic after reboot from Download mode. I ended up flashing the CSC and now the Tmobile boot splash is showing up and seems to be working, will update to confirm in a few minutes.
Update: booted just fine now into Setup Wizard...
Will someone upload the files elsewhere? I cannot download it tells me that the OP has reached daily traffic limit on website
TimelessPWN said:
Will someone upload the files elsewhere? I cannot download it tells me that the OP has reached daily traffic limit on website
Click to expand...
Click to collapse
Sorry about that! I'm taking care of it now
@partcyborg.
So... I just got an S8 from Boost Mobile after my LG Optimus f7 started FINALLY failing. Had it rooted and cwm thanks to the genius and hard work of devs like GameTheory and PlayfulGod!
1. Should it be safe to use this method and flash this particular ROM?
2. Do I need to do anything special because it's Boost n not vzw?
3. It was mentioned that in spite of 80% battery issue, battery life is extremely well optimised. Anyone else with S8 on Boost try this? Worth it to take the plunge?
Don't care about Knox, Safety Net, etc. I don't use my device for transactions via Samsung/Android Pay, nor Gaming. Wondering if this will nix Playstore purchases via credit card on file? NOT a deal beaker by any means. Just curious.
I desperately miss having root and custom recovery. siiiiiigggghhhh...
Anyway, Thanks for any info and THANK YOU @partcyborg for all the time and hard work you've put into trying to help us get the most out of these phones!
This is my first $700 phone and I'll probably have her as long as I did my f7. ( as log as battery doesn't die or I can have it replaced at a repair shop when the time comes, for less than a fortune. lol)
Attached is a screen of my phone's specs if it helps.
Thanks again,
- TheJackalsMARK
TimelessPWN said:
Will someone upload the files elsewhere? I cannot download it tells me that the OP has reached daily traffic limit on website
Click to expand...
Click to collapse
The links work again. Sorry for the temp issue!
thejackalsmark said:
@partcyborg.
So... I just got an S8 from Boost Mobile after my LG Optimus f7 started FINALLY failing. Had it rooted and cwm thanks to the genius and hard work of devs like GameTheory and PlayfulGod!
1. Should it be safe to use this method and flash this particular ROM?
2. Do I need to do anything special because it's Boost n not vzw?
3. It was mentioned that in spite of 80% battery issue, battery life is extremely well optimised. Anyone else with S8 on Boost try this? Worth it to take the plunge?
Don't care about Knox, Safety Net, etc. I don't use my device for transactions via Samsung/Android Pay, nor Gaming. Wondering if this will nix Playstore purchases via credit card on file? NOT a deal beaker by any means. Just curious.
I desperately miss having root and custom recovery. siiiiiigggghhhh...
Anyway, Thanks for any info and THANK YOU @partcyborg for all the time and hard work you've put into trying to help us get the most out of these phones!
This is my first $700 phone and I'll probably have her as long as I did my f7. ( as log as battery doesn't die or I can have it replaced at a repair shop when the time comes, for less than a fortune. lol)
Attached is a screen of my phone's specs if it helps.
Thanks again,
- TheJackalsMARK
Click to expand...
Click to collapse
This is about all we have as far as ROMs go. We don't have a custom recovery because our bootloader is locked and it's not looking like it's going to be unlocked ever. You can flash this on any G950U phone, carrier doesn't matter.
thejackalsmark said:
@partcyborg.
So... I just got an S8 from Boost Mobile after my LG Optimus f7 started FINALLY failing. Had it rooted and cwm thanks to the genius and hard work of devs like GameTheory and PlayfulGod!
1. Should it be safe to use this method and flash this particular ROM?
2. Do I need to do anything special because it's Boost n not vzw?
3. It was mentioned that in spite of 80% battery issue, battery life is extremely well optimised. Anyone else with S8 on Boost try this? Worth it to take the plunge?
Don't care about Knox, Safety Net, etc. I don't use my device for transactions via Samsung/Android Pay, nor Gaming. Wondering if this will nix Playstore purchases via credit card on file? NOT a deal beaker by any means. Just curious.
I desperately miss having root and custom recovery. siiiiiigggghhhh...
Anyway, Thanks for any info and THANK YOU @partcyborg for all the time and hard work you've put into trying to help us get the most out of these phones!
This is my first $700 phone and I'll probably have her as long as I did my f7. ( as log as battery doesn't die or I can have it replaced at a repair shop when the time comes, for less than a fortune. lol)
Attached is a screen of my phone's specs if it helps.
Thanks again,
- TheJackalsMARK
Click to expand...
Click to collapse
I'm happy enough with the battery. Bonus is that you won't wear it out charging to 80% only apparently.
It's a multi CSC so you should be fine on boost. I can't test it though I only have VZW. Worst case flash the CSC but only do that if it fails to boot.
adj998 said:
This is about all we have as far as ROMs go. We don't have a custom recovery because our bootloader is locked and it's not looking like it's going to be unlocked ever. You can flash this on any G950U phone, carrier doesn't matter.
Click to expand...
Click to collapse
Yeah, Bootloader's a major buzzkill.
Root and decent custom ROM would be a nice consolation prize.
What's your take on the battery afterwards? I practically live on my phone and with not being able to swap batteries, a major hit to battery life is pretty much a deal breaker. BTW, thx for the quick reply!
- TheJackalsMARK
Sent from my Samsung SM-G950U using XDA Labs
reggie cheeks said:
I'm new to SIM unlocked and haven't rooted since s4 so possible newb question but
Can I use this rom to root unrooted AQH3?
I'm on sim-unlocked G950U.
Thanks for any help.
Sent from my SM-G950U1 using Tapatalk
Click to expand...
Click to collapse
No but you can install rooted aqi6 with it. This literally flashes /system and replaces what you have installed. I find aqi6 much improved TBH
OMEGAHORSE said:
Followed everything and when it went to go reboot the SAMSUNG GALAXY S8 logo popped with the little custom lock but its almost as if its just there like its not really rebooting just a screenshot of it it wont go away after a certain time period or anything,I also tried re-flashing the BL and it still didn't boot up as it should of. Any idea on what I should do?
Click to expand...
Click to collapse
Factory reset. Sorry I should have mentioned that in the op. I will update
partcyborg said:
I'm happy enough with the battery. Bonus is that you won't wear it out charging to 80% only apparently.
It's a multi CSC so you should be fine on boost. I can't test it though I only have VZW. Worst case flash the CSC but only do that if it fails to boot.
Click to expand...
Click to collapse
Thx, man!
And Great Work, again, on this!
- TheJackalsMARK
Sent from my Samsung SM-G950U using XDA Labs

[GUIDE][TREBLE] Axon 7 Custom OREO ROM installation for newbies - 2018.08.05

INTRODUCTION
I posted my configuration before inside a couple of threads. After that, I have received a lot of questions about the same issues. I have also been asked to create a thread so newbies could have an easy way of having an Oreo system up and running in the Axon 7. So I am doing it. Newbies will have an easy entry point to the world of custom Oreo ROMs and a single point to clarify any question. We have a healthy and active Axon 7 scene here at XDA. This guide provides a path to have a custom Oreo system with the latest features available for this device requiring a minimum effort. It applies to any of the 3 Axon 7 flavors: A2017 (China), A2017G (Europe) and A2017U (Americas) with any memory and storage capacity. At this time there are 3 groups of ROMs depending on the Bootstack and GSI support:
1. B32+B10 ROMs use the reliable Nougat bootstack. They are very stable and battery efficient. On the other hand, none of them support dual SIM or HDR+ camera. However they support HDR and Camera2 API.
2. B12 without GSI support ROMs use the Oreo beta B12 bootstack. Full support for Camera2 API and HDR+ but very poor battery performance and stability issues.
3. B12 with GSI support ROMs also use the same Oreo beta B12 bootstack. They also require a separated vendor partition. They share the same benefits and limitations of the previous group. So far they are experimental and the Treble ROMs don't support yet all the Axon 7 Hardware when using them along with a GSI image. They are examples of a Work-In-Progress that is yet to be finished.
WHAT THE HECK IS TREBLE AND GSI?
Since Oreo, all the new devices must have a separated vendor partition to fulfill Google's Treble project requirements. This way the OS is structured in two parts:
1. Treble ROM: includes all the device drivers and vendor related files in the vendor and boot partitions. The Treble ROM is owned and updated by the device vendor or a custom ROM developer.
2. Generic System Image (GSI): Includes the Android OS, it is controlled by Google and allow generic and frequent security and system feature updates directly from Google. It uses the system partition.
So far, custom Android distributions such as LineageOS, Resurrection Remix, AOKP, Dirty Unicorns, AEX, etc... had to create specific ROMs for each supported device. This was painful and it all was depending on the willingness of a developer to maintain a version for each device. Thanks to Treble project, now Android distributions just release a single GSI able to be installed in any device using a Treble ROM. This way they can properly maintain all the devices with a single GSI image by focusing on frequent updates of a single GSI. These custom distributions will also deliver the security and feature updates by Google. So a fully Treble ROM for the Axon 7 will open the door to virtually all the Android distribution out there.
@NFound in the AEX ROM thread) is the only one working in developing a Treble ROM for our device. He has released some incomplete Treble ROMs coupled with non-generic system images. Others like @Kranoner in the Hellsgate Kernel thread or @OrdenKrieger in the LineageOS 15.1 are building and kindly sharing unofficial releases of several custom Oreo 8.1 ROMs that are used in the EDL packages below.
@Victor13f has also created guides on how to install the leaked Stock Oreo 8.0 Beta B12 ROM. I really advise to upgrade to any of the current Oreo ROMs since the current unofficial releases work way better than the previous Nougat versions. The custom AOSP Oreo 8.1 ROMs offer a wider spectrum for tweaking for better performance and battery. Custom kernels are adding full featured and optimized drivers for custom ROMs. They support almost everything, including backported drivers from the latest Linux 4.xx official kernel sources.
BACKUP:
Please note that a dirty flash won't work when coming from any non Treblerized Axon 7 (Axon 7 without the vendor partition). So, if you want to keep your information, then you should do a backup of your data before continuing with this guide. You can use the file manager to move your Documents, Downloads, Music, Pictures, Videos, etc... from your internal storage to an external SD card. You can upload them to a cloud service such as Google Drive, One Drive, MEGA, DropBox, etc. Or use the USB connection to move your information to your PC.
DEVICE UNLOCK:
Unlocking your bootloader will trigger a factory reset, and will delete the internal storage along with all the information in your phone. If your Axon 7 bootloader is still locked, you have to follow this guide before proceeding to the rest of this guide. It works for Marshmallow and Nougat stock phones. Please use that thread to ask any question related to unlocking your device.
INSTALLATION INSTRUCTIONS:
WARNING, THIS GUIDE WILL WIPE ALL THE DATA IN YOUR DEVICE, INCLUDING THE INTERNAL STORAGE.
IT REQUIRES YOUR DEVICE TO BE UNLOCKED, OTHERWISE YOUR DEVICE COULD BE BRICKED.
!!! Whatever you do, it is at your own risk !!!​
In case you get stuck at any point in this guide, do not panic! There is a straightforward way to go back to stock. Just follow this Unbrick/Restore guide. I've tried to make things as easier as possible for everyone, specially newbies not used to deal with the Axon 7. So, I have created stable custom EDL packages. In order to reduce the risk and complexity, this one Stop ROM Shop performs all the following actions in a single flash:
- installs TWRP custom recovery
- installs my customized Bootstack
- removes unlocked bootloader annoying warning message.
- installs custom Oreo ROM.
- installs google apps.
- installs custom kernel.
- installs magisk root
- creates vendor partition to treblerize your phone, this way it will be futureproof.
- formats vendor partition as ext4 filesystem to complete the previous task.
- And the guide also helps you to format data and cache as f2fs in case you haven't done it already. It provides better battery, performance and extends the lifespan of the internal flash.
I provide here 2 basic EDL package options. Both of them include the vendor partition so you won't have to perform any additional formatting and backup when upgrading to treble roms. Both options are this way future proof, just choose one of them:
OPTION 1: B32+B10 based EDL Package if you prefer stability. It includes:
- N+O custom Bootstack (B32+B10)
- TWRP 3.2.1-7 recovery by NFound
- Resurrection Remix Oreo 6.0.0 2018.05.11 ROM By Kranoner
- Google apps (ARM64, 8.1, micro)
- HellsGate v3.0 Kernel by Kranoner
- Magisk root 16.7
OPTION 2: B12 based EDL Package If you require dual SIM or full support for HDR+ camera apps. It includes:
- O custom Bootstack (B12)
- TWRP 3.2.2 recovery
- AEX 5.7 20180711 ROM by NFound
- Google apps (ARM64, 8.1, micro)
- HellsGate X12 GClang Kernel by Kranoner
- Magisk root 16.7
Once you had chosen your preferred option then proceed with these steps:
Download and Un7zip the chosen package to a folder in your computer, ensuring there are no errors. I have an A2017U, so the American modem is the package default. If you have an A2017 or A2017G just copy your modem firmware, from the corresponding provided modem subfolder, to the main folder. Just overwrite the default American modem file.
Install MiFlash in your PC. It includes the Qualcomm Snapdragon SoC drivers, nonetheless you can always install the latest Qualcomm drivers.
Enter EDL mode using one of the following options:
by pressing VolUp+VolDn+Power until the power led flashes briefly
Installing a terminal app and typing reboot edl at the app prompt.
connecting your phone to your PC and typing adb reboot edl at your computer's command prompt.
While your phone is completely off, press VolUp+VolDn while connecting your phone to your PC.
If you haven't done yet, it's time to connect your phone to your computer.
Open MiFlash in your computer.
Click Browse button and select the folder you created with the firmware files.
Click Refresh button and your device will appear listed as virtual COM port.
Click Flash button and wait for a few minutes until it finishes. Note the bottom options are not applicable.
Wait a few seconds until the boot animation begins and press again VolUp+Power until the phone vibrates to enter again into recovery. Go to Advanced > Terminal and now type: reboot "dm-verity enforcing"
Press VolUp+Power until the phone vibrates to enter into recovery, then release both buttons. Go to Advanced > Terminal and type: reboot disemmcwp
Wait a few seconds until the boot animation begins and press again VolUp+Power until the phone vibrates to enter again into recovery for a 3rd time. To ensure everything is clean you should format the DATA partition, including internal storage. Go to settings and ensure "Use rm -rf instead of formatting" option is not selected. Then go to Wipe > Advanced Wipe, select Data partition and tap on Repair_or_Change_File_System button and then on Change_File_System button. Select F2FS and confirm action. Do the same to apply F2FS to the Cache Partition. Now, from the main menu > Wipe, select and clean dalvik.
NOTE: If you receive an error while formatting data, then go to Wipe > Advanced Wipe, select Data partition and tap on Repair_or_Change_File_System button and then on Change_File_System button. Format DATA as EXT4 first and, without leaving TWRP do it again as F2FS. That will fix the issue.
Go to main menu and reboot system.
Complete the setup process so you can continue with the rest of the customizations not included in the basic package:
SOUND EXPERIENCE:
The following steps will provide you with Dolby ATMOS and Viper4Audio pre-processors along with the HiFi DAC output. Please note that the activation of these features will drain your battery faster since both will use your CPU. Nonetheless the benefits are evident. if you want to fully enjoy the audio capabilities of the Axon 7 you should go ahead and use them. The steps are:
Download Mixer_AK4490.zip and Dolby-Oreo.zip to your phone.
Open Magisk Manager app, go to the Download section and Download (do not install yet) Ainur Sauron, Viper4Android FX and Audio Modification Library.
Reboot to recovery the same way you did during System installation, press install, navigate to /sdcard/MagiskManager folder and install Ainur Sauron, Viper4Android (I prefer 2.5.0.5 and traditional interface, however it is all up your personal preference) and Audio Modification Library zip files in that order. Do not reboot after flashing these files, just navigate now to the /sdcard/Download folder and flash Dolby-Oreo.zip and Mixer_AK4490.zip
SCREEN COLOR ENHANCEMENT:
Download and install KCAL Color Calibration/enhancement app. I only modify the Saturation to 62 to get amazing vibrant colors from this AMOLED screen, nonetheless this is a very personal configuration. At the end this has to please your own eyes. . This app optional since Kernel Adiutor and EX Kernel Manager apps can also configure Qualcomm SoC Color Control.
AVOID BATTERY DEGRADATION:
Install Battery charge Limit [ROOT] app. Open it and set Limit charge to 85% and recharge below 79%. Do you want to avoid your battery to wear as the time go by? do not miss this guide to understand why this step is so important for the health of your device.
BETTER CAMERA:
+ Snap Camera App
I am using, and heavily recommend the paid version of Snap Camera HDR. It supports Camera2 API with full manual and HDR support. Find recommended settings here.
Testing now GCAM v4.0. Nonetheless so far I am just starting testing.
Bacon Camera is another Camera I am now actively testing.
The next level of this guide will provide with instructions on how to change recovery, ROM, kernels and all the details and options you have. It is late today so I'll finish it later.
Hope it helps. I will be updating this guide in the future as soon my configuration changes or I find new technologies, apps or patches. If you know about a better option just post your suggestions!
Thanks and credits go to @NFound, @Kranoner, @Infy_AsiX, @roisuke, @Skrem339, @djkuz and you too for bringing up issues and valuable solutions.
Yes! I almost pm'd you like 3 times to ask if you would do exactly this. By far, I am not a noob, but honestly, i can finally take the plunge now knowing i have a place to look back and proper steps. I still have yet to flash TWRP 3.1.1-7 because of the [no bet removing inscription] bit on that thread, but reading over it like a dozen times, im fairly confident the only thing that will not work correctly on my a2017u is removing the warning that my bootloader is unlocked. Correct me if Im wrong on that one. Thank you, @Oki. Many thanks, brother.
kitcostantino said:
Yes! I almost pm'd you like 3 times to ask if you would do exactly this. By far, I am not a noob, but honestly, i can finally take the plunge now knowing i have a place to look back and proper steps. I still have yet to flash TWRP 3.1.1-7 because of the [no bet removing inscription] bit on that thread, but reading over it like a dozen times, im fairly confident the only thing that will not work correctly on my a2017u is removing the warning that my bootloader is unlocked. Correct me if Im wrong on that one. Thank you, @Oki. Many thanks, brother.
Click to expand...
Click to collapse
Removing the message at boot is easy. If you already have TWRP Exclusive v3.2.1-7 and the aforementioned bootloader, then you just have to boot TWRP Advanced menu > More > Del inscription. Easy, Isn't it? It works in my A2017U so It should work for you too.
Oki said:
Removing the message at boot is easy. If you already have TWRP Exclusive v3.2.1-7 and the aforementioned bootloader, then you just have to boot TWRP Advanced menu > More > Del inscription. Easy, Isn't it? It works in my A2017U so It should work for you too.
Click to expand...
Click to collapse
This was actually why:
NFound said:
TWRP Exclusive™​
For "U" models pacth cleaning inscriptions bootloader NO BET!
Warning! "Del Inscription" - only for A2017 and A2017G !!!
Click to expand...
Click to collapse
^^^^^^^^This was actually why I thought it didn't work. Honestly, I don't mind the warning. I just had to ascertain if that was the only issue. Nfound had already confirmed it worked on a2017u. And removing that warning hasn't ever mattered to me that much.)
kitcostantino said:
This was actually why:
^^^^^^^^This was actually why I thought it didn't work. Honestly, I don't mind the warning. I just had to ascertain if that was the only issue. Nfound had already confirmed it worked on a2017u. And removing that warning hasn't ever mattered to me that much.)
Click to expand...
Click to collapse
Well NFound just tried to say that his solution was not tested at that time in an A2017U. Actually the 2017U is unbrickable thanks to the hardware EDL mode of the Qualcomm SOC.
By the way, I have updated the OP. Now it matches my current configuration. I have also mentioned my current testing efforts in the battery and camera areas.
Regards
Hi. Any fix for Dual Sim? I read through XDA and it seems dual sim is still not fixed. I am getting tired with nougat ROMs but without dual sim I have to stick with it...
@kitcostantino, there's also another method to get rid of that startup message that might work.
http://forum.xda-developers.com/showthread.php?p=74445757
ZTE Axon 7 A2017U, AospExtended v5.4 ROM, HELLSGATE Kernel, Multiboot, Tapatalk 4.9.3
Hello,
just a little question: Does this guide work on the Axon 7 2017G too? The RR Oreo Rom are for the 2017U....
Thx
Dave_XDA said:
Hello,
just a little question: Does this guide work on the Axon 7 2017G too? The RR Oreo Rom are for the 2017U....
Thx
Click to expand...
Click to collapse
Yes, the guide is valid for any Axon 7 flavor: Chinese, Euro and Americas.
marcdw said:
@kitcostantino, there's also another method to get rid of that startup message that might work.
http://forum.xda-developers.com/showthread.php?p=74445757
ZTE Axon 7 A2017U, AospExtended v5.4 ROM, HELLSGATE Kernel, Multiboot, Tapatalk 4.9.3
Click to expand...
Click to collapse
It is actually the same method. TWRP flashes that aboot image when selecting the option I mentioned. I still see the TWRP method a lot better since it doesn't require any extra download. You can see all the images and add-ons when exploring the filesystem while in TWRP Exclusive.
Thx for your answer.
I got this Axon 7 from my brother with the AEX Oreo Rom install'd. I wanne try out the RR Oreo because i use'd the RR on my old ASUS Phone.
Do i need to install the Bootloader you linke'd in your guide or can i install the RR Oreo with a clean install over the AEX Oreo Rom?
Thx again
Dave_XDA said:
Thx for your answer.
I got this Axon 7 from my brother with the AEX Oreo Rom install'd. I wanne try out the RR Oreo because i use'd the RR on my old ASUS Phone.
Do i need to install the Bootloader you linke'd in your guide or can i install the RR Oreo with a clean install over the AEX Oreo Rom?
Thx again
Click to expand...
Click to collapse
There is no problem as long you have an Oreo Bootloader. Since you are already running a custom Oreo ROM it means you already have a valid bootloader. Thus, you only need to flash the RR-O ROM. Should you find any problem you can just flash the latest bootloader I link in the OP or go back to AEX. It is important to do a clean install when switching Oreo flavors, as you plan, otherwise you will face problems.
Thanks for this. Been running stock since I got the phone, but missing the old phone days where I used to flash something new like once a week. Gonna try this out tonight I think. Really appreciate the concise directions
Are there known issues in returning to B35 Stock, should the RR(O) prove unsatisfactory?
amphi66 said:
Are there known issues in returning to B35 Stock, should the RR(O) prove unsatisfactory?
Click to expand...
Click to collapse
No issues, you can always go back to B35.
Oki said:
It is actually the same method. TWRP flashes that aboot image when selecting the option I mentioned. I still see the TWRP method a lot better since it doesn't require any extra download. You can see all the images and add-ons when exploring the filesystem while in TWRP Exclusive.
Click to expand...
Click to collapse
Thanks for the info.
Never used/explored TWRP Exclusive's extras really. In my environment I might break something [emoji39] but cool that everything is there.
ZTE Axon 7 A2017U, AospExtended v5.4 ROM, HELLSGATE Kernel, Multiboot, Tapatalk 4.9.3
How long does the first boot after flashing the bootloader take? I don't seem to get past the ZTE powered by android screen.
Never mind. Just hold Power + Volume Up at boot.
Thanks !! Oreo AND RR together !!
I will flash it tomorrow on my A2017G !!
(maybe you should write the A2017G compatibility on the first page because this :
RR-O-v6.0.0-20180422-axon7-Unofficial.zip
for the ZTE Axon 7(2017U), by Kranoner
on androidfilehost almost made me missed it )
EDIT : Does this ROM+kernel have the dualsim problem ?
Oki said:
Removing the message at boot is easy. If you already have TWRP Exclusive v3.2.1-7 and the aforementioned bootloader, then you just have to boot TWRP Advanced menu > More > Del inscription. Easy, Isn't it? It works in my A2017U so It should work for you too.
Click to expand...
Click to collapse
After doing this, I can't unlock my phone after restart by entering password. On A2017U and AEX Oreo latest. Any1 had this issue?
If anyone does, here's the fix: https://forum.xda-developers.com/axon-7/help/to-remove-screen-unlock-pattern-t3768575
ashishv said:
After doing this, I can't unlock my phone after restart by entering password. On A2017U and AEX Oreo latest. Any1 had this issue?
If anyone does, here's the fix: https://forum.xda-developers.com/axon-7/help/to-remove-screen-unlock-pattern-t3768575
Click to expand...
Click to collapse
What have you really done my friend? This guide requires a complete cleanup so it is impossible that you had any locksettings after a clean install. If you follow all the steps and follow the guide then you shouldn't have any problem.
The lock settings get corrupted after migrating to f2fs, and you can also find that problem when dirty flashing some roms or kernels. For that reason, to take care of that step, in the f2fs migration link, there is a link to a very detailed way to cleanup the lock settings. You can find that guide here: https://forum.xda-developers.com/axon-7/how-to/guide-access-locked-axon-7-how-to-t3525403 but, it shouldn't happen when following the steps of this guide. By the way, this guide requires RR Oreo ROM, and you mention you are using AEX Oreo...

so I got myself a Franklin... X96Max Plus2

it's harder to pin down clear decisive info on this box than I thought.
can someone confirm whether using magisk manager (an older version 7xx or 8xx) will successfully flash magisk onto this box without bricking it ?
I've seen a TV Box Stop video on this box that stated messing with the included SuperSU bricks the box...
can it be done via TWRP or patching a downloaded update zip ?
all knowledge welcome
The amlogic boxes, magisk does not work unless you hexedit your boot image. It will install, but not function.
There is a video tutorial on 4pda (russian site)on how to do so, and I'm writing up a visual tutorial at some point soon.
I did the process myself one time, and it works.
The issue I am currently having is my Amlogic Box is also a new "mystery" box.
Repacked by a company called "CONCEPTUM" for the greek market here.
The Model is X96 Air Extreme. I have disassembled it and got the specs on it and photos, and will make a post soon.
Have you gotten yet photos of your internals?
This particular box is somewhat compatible with the
X96Max_Plus_Q2_20201209-1446.img (I had to flash it with that.. long story), everything internal works but the wifi only connects at 54 mbps, not sure if its because of a firmware driver mismatch or its a POS.
I'm looking to flash slimbox pie eventually, I'd rather not open my box if I can avoid it.
Ex Kernel manager reports:
• available ram @ 3794mbs
• max clock speed @ 1908mhz and 4 cores
• GPU mali-G31 with OpenGL ES 3.2
for testing which box you have slimhouse wrote this:
First of all, you should look at the system information in the settings, it will be displayed there: Plus, Plus2, Plus100, etc. However, crooks can fake this and stickers.
Using Device Info HW, you can determine whether there is a 1000Mb LAN and which radio module (turn on WiFi!). If the device was flashed with firmware for another modification, then the information may be missing or unreliable - you need to open and check the presence of the LAN 1000 chip and which radio module is installed.
#
The radio module can be identified by the marking on the chip or by the sticker on the board
X96 Max Plus2. Availability Of 1000Mb Ethernet RTL8211F. You can make sure by connecting 1Gb-supporting devices to the equipment or using Device Info HW, or visually by the presence of a chip on the board. There are 2 antennas. RTL8822CS Radio Module
#
X96 Max Plus2
There was a modification of Plus2, but 2GB of RAM, only the 202009 flash and the special flash for 2GB RAM from JAW are sewn. Photo
And there is also a Plus2 version with the RTL8822BS radio module (Fn-Link 6222B-SRB), there is a problem with the radio module on the ports of Yugos.
Device Info HW says my box has a Wi-Fi chip numbered RTL88x2cs, that's not exactly the same as listed above...
I flashed slimbox pie on this box yesterday and all is more less well with the rom, but this box has no ramdisk and even though TWRP flashed successfully according to he official TWRP app i cannot boot into it.
the box tries 2 or 3 times and boots back to the system. without TWRP that i can get to there's no chance of magisk.
any thoughts or advice welcome
3mel said:
I flashed slimbox pie on this box yesterday and all is more less well with the rom, but this box has no ramdisk and even though TWRP flashed successfully according to he official TWRP app i cannot boot into it.
the box tries 2 or 3 times and boots back to the system. without TWRP that i can get to there's no chance of magisk.
any thoughts or advice welcome
Click to expand...
Click to collapse
you need to find a firmware to flash, you can then modify it with magisk and flash it, i made a guide here on the process
aidanmacgregor said:
you need to find a firmware to flash, you can then modify it with magisk and flash it, i made a guide here on the process
Click to expand...
Click to collapse
thanks for the response
will this work on any rom suitable for the box ?
I'll have get YouTube to slow down the video a little so it's easier to follow what you're opening but I think I get the general unpack repack idea.
if you know of a TWRP image that's flashable via flashify or TWRP official app and that works on this box, can this technique be shortened by just patching that image pre-flash ?
I dropped back down to this boxes stock image, Slimbox couldn't keep magisk running and at random times root just stopped working. I tried Aidan's rom but the UI is not for me and there's no sideloading allowed ?? and it couldn't see my memory card anyway.
with the help of Aidan's guide above I got magisk working on the stock rom but I still have a default su binary that came with the box and has no visible root switch. if anyone knows of a way to deactivate it please share.
thanks

Categories

Resources