Anyone has had luck getting the Pixel Experience ROM working?
Site can be found here:
https://download.pixelexperience.org/j9110
I am on 8170 and would like to test it out.
Really interested in your feedbacks!
How do we flash it without a working twrp?
https://wiki.pixelexperience.org/devices/j9110/install/
Follow these instructions it should work....
chaitanya.krishna said:
Follow these instructions it should work....
Click to expand...
Click to collapse
...
TrustAugustus said:
How do we flash it without a working twrp?
Click to expand...
Click to collapse
Instructions do not Help if there is no way to follow them. Just use GSIs... There is also a Pixel Expierence One around...
joeminati said:
Anyone has had luck getting the Pixel Experience ROM working?
Site can be found here:
https://download.pixelexperience.org/j9110
I am on 8170 and would like to test it out.
Click to expand...
Click to collapse
I tried the June and July builds on my Dual SIM J9110. They are constantly improving so some things that I mention below may have changed. The SODP guys working on it are awesome.
The builds worked well for the most part, performance is not quite as good as stock, there are some stutters and frame drops, but it's still daily driver material.
Some things to keep in mind:
-There is no Dolby Audio. Volume from the speakers is slightly lower than stock.
-The display runs in always 4K mode, it looks great. Doesn't have a huge effect on battery life either.
-The notification LED only displays one colour, which is sort of a bluey-white.
-You have to use Raizen's HyperCam build for photos. A little bit of tweaking within the app and it takes fantastic photos. Supports all 3 cameras as well.
-It will not have any proprietary Sony features like Battery Care.
For flashing you have to use Payload_Dumper on the payload.bin file included within the ROM zip. It will give you dtbo.img, boot.img, system.img, vendor.img and so on.
First make sure you're on the latest Android 10 (55.1.x) firmware on both A and B slots. You can use NewFlasher to flash, and fastboot to switch between slots.
Then flash the latest Sony Open Device Binaries for Kumano (Xperia 1 / Xperia 5) which you can get from here:
https://developer.sony.com/file/dow...-aosp-android-10-0-kernel-4-14-kumano-latest/
Then flash dtbo, boot and vendor. Then boot into AOSP recovery with Power + Vol down. From there you can use adb sideload to install the ROM .zip file and your phone will reboot into PE.
If it bootloops, run fastboot format userdata or boot back into AOSP recovery and do a factory reset.
For updates, it does support OTAs since the device is officially supported by PE and hosted on their servers.
@MeltdownSpectre
Thanks for the info! I'm definitely going to try it.
Would you mind pointing me to the exact hypercam raizen file
TrustAugustus said:
@MeltdownSpectre
Thanks for the info! I'm definitely going to try it.
Would you mind pointing me to the exact hypercam raizen file
Click to expand...
Click to collapse
Here you go:
https://f.celsoazevedo.com/file/cfiles/gcm1/HyperCam-RaizenA-10.apk
MeltdownSpectre said:
Here you go:
https://f.celsoazevedo.com/file/cfiles/gcm1/HyperCam-RaizenA-10.apk
Click to expand...
Click to collapse
Thanks! It doesn't work with stock Sony. Is that normal?
I realized that the ROM is for the DSDS. I have the 802SO version. I wonder if I'll end up borking the phone.
TrustAugustus said:
Thanks! It doesn't work with stock Sony. Is that normal?
I realized that the ROM is for the DSDS. I have the 802SO version. I wonder if I'll end up borking the phone.
Click to expand...
Click to collapse
Not sure if 802SO is supported.
Yes it's normal for it to not work with stock ROM.
MeltdownSpectre said:
I tried the June and July builds on my Dual SIM J9110. They are constantly improving so some things that I mention below may have changed. The SODP guys working on it are awesome.
The builds worked well for the most part, performance is not quite as good as stock, there are some stutters and frame drops, but it's still daily driver material.
Some things to keep in mind:
-There is no Dolby Audio. Volume from the speakers is slightly lower than stock.
-The display runs in always 4K mode, it looks great. Doesn't have a huge effect on battery life either.
-The notification LED only displays one colour, which is sort of a bluey-white.
-You have to use Raizen's HyperCam build for photos. A little bit of tweaking within the app and it takes fantastic photos. Supports all 3 cameras as well.
-It will not have any proprietary Sony features like Battery Care.
For flashing you have to use Payload_Dumper on the payload.bin file included within the ROM zip. It will give you dtbo.img, boot.img, system.img, vendor.img and so on.
First make sure you're on the latest Android 10 (55.1.x) firmware on both A and B slots. You can use NewFlasher to flash, and fastboot to switch between slots.
Then flash the latest Sony Open Device Binaries for Kumano (Xperia 1 / Xperia 5) which you can get from here:
https://developer.sony.com/file/dow...-aosp-android-10-0-kernel-4-14-kumano-latest/
Then flash dtbo, boot and vendor. Then boot into AOSP recovery with Power + Vol down. From there you can use adb sideload to install the ROM .zip file and your phone will reboot into PE.
If it bootloops, run fastboot format userdata or boot back into AOSP recovery and do a factory reset.
For updates, it does support OTAs since the device is officially supported by PE and hosted on their servers.
Click to expand...
Click to collapse
Thanks for Your Post! Is there any reason for flashing the ZIP again after flashing it already via Fastboot? Sounds more Like a Option for coming Updates (I hope update.zip Files Work from the Storage too?). Great to have at least a stable Recovery Base!
Miustone said:
Thanks for Your Post! Is there any reason for flashing the ZIP again after flashing it already via Fastboot? Sounds more Like a Option for coming Updates (I hope update.zip Files Work from the Storage too?). Great to have at least a stable Recovery Base!
Click to expand...
Click to collapse
The developers had given me these flashing instructions. We only flash dtbo, boot and vendor first. Then sideloading the zip flashes them again, as well as flashing system.img which was not flashed through fastboot.
I'm using this build now, everything works fine. But the animation seems not very smooth,a little lag
Xperia 1 - J8110, J8170, J9110, 802SO, SO-03L, SOV40
what variant support by PE rom?
JOKER.SOHA said:
Xperia 1 - J8110, J8170, J9110, 802SO, SO-03L, SOV40
what variant support by PE rom?
Click to expand...
Click to collapse
PE supports J8110 (single SIM) and J9110 (dual SIM).
i have no mobile data.
no SIM detected.
i have no mobile data.
no SIM detected.
the camera is very poor, almost cannot use, even scan a qrcode is difficult
Sketch. said:
I'm using this build now, everything works fine. But the animation seems not very smooth,a little lag
Click to expand...
Click to collapse
camera is not function as better as the stock one
Related
Hi all,
Just thought i share a little something i came across from playing about with the phone, I found you can flash any of the ROMs that the HiSilicon Kirin 650 chip set uses. Currently only two phones (5c and P9 lite)
First off you'll need the huawei update extractor http://forum.xda-developers.com/showthread.php?t=2433454 and the ROM from the model of phone you want to flash.
Use the update extractor to extract the boot.img and system.img file from the update.app file, then just flash the files on you phone (fastboot flash boot boot.img and fastboot flash system system.img)
Currently im using a stripped down P9 lite VNS L31 B130 ROM with GAPPS on a honor 5c nem-ul10 chinese phone. Working pretty good, seems fast and smooth. Battery life is not better or worse. Everything seems to be working fine.
Post any questions and i'll try to answer
Cheers
Paul
Liffeyman said:
Hi all,
Just thought i share a little something i came across from playing about with the phone, I found you can flash any of the ROMs that the HiSilicon Kirin 650 chip set uses. Currently only two phones (5c and P9 lite)
First off you'll need the huawei update extractor http://forum.xda-developers.com/showthread.php?t=2433454 and the ROM from the model of phone you want to flash.
Use the update extractor to extract the boot.img and system.img file from the update.app file, then just flash the files on you phone (fastboot flash boot boot.img and fastboot flash system system.img)
Currently im using a stripped down P9 lite VNS L31 B130 ROM with GAPPS on a honor 5c nem-ul10 chinese phone. Working pretty good, seems fast and smooth. Battery life is not better or worse. Everything seems to be working fine.
Post any questions and i'll try to answer
Cheers
Paul
Click to expand...
Click to collapse
Could you post the rom here..and does it support the fingerprint
How did you do that
PalakMi said:
How did you do that
Click to expand...
Click to collapse
First off you need fastboot tools installed and the Huawei Update Extractor downloaded http://forum.xda-developers.com/showthread.php?t=2433454
Download b131 p9 lite rom http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1164/g104/v53991/f1/full/update.zip. There is a later ROM for the p9 lite (b151) but the finger print sensor doesn't work with this ROM
Use the extractor to extract the boot.img and system.img files.
Use trwp to complete backup of phone to the micro SD card. Use trwp and select advanced wipe, wipe everything except the micro SD
Reboot to bootloader
Open command prompt from the folder you have extracted the boot and system images, type the following commands
fastboot flash boot boot.img
fastboot flash system system.img
fastboot reboot
If you have the 5c chinese phone this rom is great, much more stock feel.
If like me you are having issues with the POB trwp, use the trwp made for the p9 lite
Any question let us know
Great, no questions now so far
Can I port a P9 Lite Rom to an european Honor 5c (without finger print sensor and NFC) ??
minisaurio said:
Can I port a P9 Lite Rom to an european Honor 5c (without finger print sensor and NFC) ??
Click to expand...
Click to collapse
Not sure, don't have the european phone. Once you have a complete backup to revert to, you can't really do much harm testing
has anyone figured out, if this works for european copies of the phone as well?
and if yes, is there a chance to run the CM ROM from Meticulus?
i'd really love to see CM on my phone
Thx nice work
johdost said:
has anyone figured out, if this works for european copies of the phone as well?
and if yes, is there a chance to run the CM ROM from Meticulus?
i'd really love to see CM on my phone
Click to expand...
Click to collapse
Yes, I've got the beta build of CM running on my european 5C - you need to follow the install instructions carefully, and there's a couple of extra steps for the 5C - you need to change the install script as described in this post to get it to install (this goes for the TWRP install too):
http://forum.xda-developers.com/showpost.php?p=69989870&postcount=225
Once you've booted up, to get the camera to work you need to follow the instructions in this post:
http://forum.xda-developers.com/showpost.php?p=69990309&postcount=226
I've added the camera fix to a boot script so that I don't need to do it after every reboot. Once you've done that the ROM is working brilliantly (though with the same small issues the P9-lite users are having).
Malcolm52 said:
Yes, I've got the beta build of CM running on my european 5C - you need to follow the install instructions carefully, and there's a couple of extra steps for the 5C - you need to change the install script as described in this post to get it to install (this goes for the TWRP install too):
http://forum.xda-developers.com/showpost.php?p=69989870&postcount=225
Once you've booted up, to get the camera to work you need to follow the instructions in this post:
http://forum.xda-developers.com/showpost.php?p=69990309&postcount=226
I've added the camera fix to a boot script so that I don't need to do it after every reboot. Once you've done that the ROM is working brilliantly (though with the same small issues the P9-lite users are having).
Click to expand...
Click to collapse
Have tried the following from an adb shell, but the camera still doesn't work. It doesn't give the error about not been able to connect, it just hangs and displays nothing.
How did you go about adding the fix to the boot script?
Thanks
Paul
Here's the script I used, there may have been a typo in Meticulous' original:
#!/system/bin/sh
stop HwCamCfgSvr
HwCamCfgSvr hi6250 NEMO &
restart media
If you put those 4 lines in a file called:
/system/etc/init.d/99camerafix
Then make sure it's executable (chmod +x /system/etc/init.d/99camerafix) it should run on startup.
Malcolm52 said:
Here's the script I used, there may have been a typo in Meticulous' original:
#!/system/bin/sh
stop HwCamCfgSvr
HwCamCfgSvr hi6250 NEMO &
restart media
If you put those 4 lines in a file called:
/system/etc/init.d/99camerafix
Then make sure it's executable (chmod +x /system/etc/init.d/99camerafix) it should run on startup.
Click to expand...
Click to collapse
Should i name the file 99camerafix.sh or just 99camerafix?
Thanks again
Paul
Liffeyman said:
Should i name the file 99camerafix.sh or just 99camerafix?
Thanks again
Paul
Click to expand...
Click to collapse
Not sure it matters, but I created it without the .sh
Malcolm52 said:
Not sure it matters, but I created it without the .sh
Click to expand...
Click to collapse
Cool, im using the app solid explorer to give the file permissions. I gave it 777, were i think it should be 775. Let me try again.
Just out of curiosity, did you dirty flash the CM over an earlier version? Just reading some of the posts over on the p9 forms. Users are reporting a smoother rom when dirty flashing
Thanks
Paul
Liffeyman said:
Cool, im using the app solid explorer to give the file permissions. I gave it 777, were i think it should be 775. Let me try again.
Just out of curiosity, did you dirty flash the CM over an earlier version? Just reading some of the posts over on the p9 forms. Users are reporting a smoother rom when dirty flashing
Thanks
Paul
Click to expand...
Click to collapse
No, beta was the first build I tried. Nice and smooth for me, except when night mode is on or occasionally when balanced battery mode is selected - but performance battery mode seems to have reasonable battery life so I'm using that for now.
solved problem already, had some troubles packing the zip together again (mac issues...)
it works fine on my phone now (including camera) thanks a lot for the help!
With a little help.... http://forum.xda-developers.com/honor-5c/help/dev-info-support-honor-5c-cm-13-builds-t3517159
Thanks @Liffeyman.
Gonna try installing ur twrp backup of the p9-lite rom (stripped down of bloat + xtra app goodies). My model is the honor 5c Nem-l51. It's the uk 2gb ram/16gb storage without fingerprint sensor. I realize yours was the Chinese model so I'll let u know how I get on and hopefully it works just as well . Like u says, as long u perform a backup, there should be nothing to worry about :fingers-crossed:
If all goes well with that....I might download the B151 rom and extract the boot&system images and flash them as per your instructions previously. Hopefully that build will be even more stable/fast and the fact that the fingerprint sensor does not work is no problem for me as the uk model has no such sensor ?
Will post the outcome of my efforts in the next few days....
iantechie1979 said:
Thanks @Liffeyman.
Gonna try installing ur twrp backup of the p9-lite rom (stripped down of bloat + xtra app goodies). My model is the honor 5c Nem-l51. It's the uk 2gb ram/16gb storage without fingerprint sensor. I realize yours was the Chinese model so I'll let u know how I get on and hopefully it works just as well . Like u says, as long u perform a backup, there should be nothing to worry about :fingers-crossed:
If all goes well with that....I might download the B151 rom and extract the boot&system images and flash them as per your instructions previously. Hopefully that build will be even more stable/fast and the fact that the fingerprint sensor does not work is no problem for me as the uk model has no such sensor
Will post the outcome of my efforts in the next few days....
Click to expand...
Click to collapse
Just noticed with this, you will need to disable the Wi-Fi privacy police or it'll keep disbaling you wifi. I'll try upload a newer version of this shortly
SamFail presents...
PartCyborgActiveRom
ARA1
A Rooted Custom Rom
For SM-G892A/U on V1 and V2 Bootloaders
FAQ
What is my Bootloader Revision?
Your bootloader revision is part of the baseband build number of the firmware you are currently running. For example, let's consider this firmware version: G892ASQS2BQL1
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. All Samsung firmware follow this formula for all devices.
Using this formula, What is the bootloader version for G892UEU4GHK1?
Answer: Bootloader revision is 4
Updates
Please see below for a a new update to both the V1 and V2 releases.
It is a new BL "part 2" tarball that contains a fix for the issues reported by
many of you with the finger print and other various sensors. It has replaced
the original firmware Part2 link in the following post .
Featured Modifications
Deodexed
Deodexed for all devices.
I found a way that works!
It should continue working as long
as we care about nougat
Xposed Preinstalled
Forget that extra flash, 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 Custom Boot Animation
Another great one from @rayan-refoua himself.
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 gotten me using it for a while. Specifically it has a better convolver (IRS processing) implementation, and its bass boost is WAY better than v4a. However you can use both at the same time to get the best of both worlds.
ITYBP Modded YouTube
A last minute addition, this is a really nice youtube mod brought to you by XXXXXX ADD SOURCE XXXXX. It features some cool features like native adblocking (no more xposed module), override your max youtube resolution (so you can watch 4k videos on your phone), and, not as important to us, spoofing different device types to get true hdr videos. 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
I did a lot more digging this round, and was able to add back a few things that I had taken out without loading the system more. This rom feels snappier than any before it. As usual, if you find something missing that you want back, pull it from the stock rom and install it in /system.
Improved Battery Life
Thanks to some fine battery sleuthing work 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 to a large batch of personally tested build.prop tweaks make the ui a lot more responsive. Part of that is the data optimisation scripts that now run at boot to make sure things are cleaned up and in tip top shape. You wont notice those, but they are there doing their thing.
Other Features
- 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. If a large number of people want something back, I will include it in the next version, but by now I think we have covered all those possibilities and now the list will only get shorter. No I will not put Bixby back
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. Better safe than sorry.
Prepare the Following:
- complete stock rom at your bootloader rev in case things dont work
- Everything backed up (see above)
- 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.
[/size]
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, connect to your pc
4) Open Comsy Odin and add ONLY the AP Part1.tar.md5 file. Select the following options only:
- "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.
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 ub ports as you have suffered from the usb3 corruption.
When you see the upload mode page, use the 3 button reboot to go back to download mode.
WARNING: When you reboot from upload mode, your phone will show an error instead of download mode.
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.
It is safe to continue
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. Click "Start" and flash the BL (part 2) to your device.
8) Wait for the flash to finish . It won't take very long at all all the files are small.
9) When it has finished, Odin will say PASS and your device will reboot into recovery.
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 partition that is valid, and that the csc is processed correctly. Failure to do the reset could cause issues with either.
All done!
Donations/Root Bounty
Pledged a donation for the root bounty? Send it here. Thank you!
IF YOU GET 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.
Kernel Panic, Invalid Argument
Start the process over
Go back to the beginning and do everything again. If it fails in a new way this time, you may have hardware caused corruption, or maybe you missed a step. Change hardware, and keep trying.
Help
If you get stuck, some of us will be here to help. Check out our telegram channel, where people will be around that can help you. Come Check it out.
Enjoy!
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
V1 Bootloader Revision
PartCyborgRom.G892A-ARA1.Part1.zip
[Alternate Mirror]
PartCyborgRom.G892A-ARA1.Part1b.zip
[New: Fingerprint/Sensors all working]
V2 Bootloader Revision
PartCyborgRom.G892A-2ARA1.Part1.zip
[Alternate Mirror]
PartCyborgRom.G892A-2ARA1.Part2b.zip
[New: Fingerprint/Sensors all working]
(New!) V3 Bootloader Revision
SM-G892A: PCR_G892A_BLV3.7z
SM-G892U: PCR_G892U_BLV3.7z
Odin
Prince Comsy Odin
One more time
I'm gonna celebrate it
Oh boy I'm first in the thread lol. No bagsssss.
I'm outa thanks for the day but they is comin
How to I know what version of Bootloader I have?
Yu-Ra said:
How to I know what version of Bootloader I have?
Click to expand...
Click to collapse
What is your baseband version
Mine has the u2 in it means I'm v2 look in pic
Can't unzip part 1, re DLed it multiple times can only extract 518mbs then crc error.
Pjs187 said:
Can't unzip part 1, re DLed it multiple times can only extract 518mbs then crc error.
Click to expand...
Click to collapse
I will let him know this was a issue the other day as well
That would be the AP part right
TheMadScientist said:
I will let him know this was a issue the other day as well
That would be the AP part right
Click to expand...
Click to collapse
Yes sir. TY.
Pjs187 said:
Yes sir. TY.
Click to expand...
Click to collapse
He may be busy I dropped him a note It happened a while back while he did the reg s8 betas also something with the zip file is corrupt
The downloads worked for me, no issues. If you're on a tmobile variant this rom will work fine also if you're on BL 1 att you'll be fine not sure about sprint, my fingerprint scanner, iris scanner & face recognition don't work but everything else running perfect.
Purest said:
The downloads worked for me, no issues. If you're on a tmobile variant this rom will work fine also if you're on BL 1 att you'll be fine not sure about sprint, my fingerprint scanner, iris scanner & face recognition don't work but everything else running perfect.
Click to expand...
Click to collapse
Hmmm the download extract was broken for me as well. But should be fixed sometime soon.
TheMadScientist said:
Hmmm the download extract was broken for me as well. But should be fixed sometime soon.
Click to expand...
Click to collapse
What mirror did you use? Some of the mirrors were giving me issues, the Texas mirror was the only one working properly for me.
Purest said:
What mirror did you use? Some of the mirrors were giving me issues, the Texas mirror was the only one working properly for me.
Click to expand...
Click to collapse
Lol that's the one I used
Purest said:
What mirror did you use? Some of the mirrors were giving me issues, the Texas mirror was the only one working properly for me.
Click to expand...
Click to collapse
TheMadScientist said:
Lol that's the one I used
Click to expand...
Click to collapse
Pjs187 said:
Can't unzip part 1, re DLed it multiple times can only extract 518mbs then crc error.
Click to expand...
Click to collapse
Sorry for the trouble folks! The zip extracts fine on my end, so it must be an AFH issue. Ill do what i can as im s paying customer, but we will see. In the meantime, i posted another link under "Alternate Mirror", so download from there if you are having issues.
ill reupload it to afh as well
Bootloader V2 support is now up in the OP!
Hey what version of xposed did you use, note 8 xposed isn't working wondering if you used a modified version or what you might have used?
partcyborg said:
Sorry for the trouble folks! The zip extracts fine on my end, so it must be an AFH issue. Ill do what i can as im s paying customer, but we will see. In the meantime, i posted another link under "Alternate Mirror", so download from there if you are having issues.
ill reupload it to afh as well
Click to expand...
Click to collapse
Awesome work OP thank you very much, got everything up and running now very nice, let me know where to send money for the bounty.
Pjs187 said:
Awesome work OP thank you very much, got everything up and running now very nice, let me know where to send money for the bounty.
Click to expand...
Click to collapse
I knew I forgot something!!!
https://www.paypal.me/partcyborg is the link. I will add it to the op too.
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...
I'm looking for a way to TWRP flash a Pie GSI (Resurrection Remix, to start with), and am getting the TWRP error "E:Cannot flash images to file systems" using @Pretoriano80's TWRP https://forum.xda-developers.com/p10-lite/development/recovery-twrp-3-2-1-0-t3783447
[EDIT] TWRP is actually v3.2.2-1 from @schwabe93
I remember there were at least two different TWRPs that worked on my M5 8.5 (SHT-W09 C567 in my case), and one of them was for a device similar to the M5 8.4, ?P10 Lite maybe?
Anyways, I'm looking for any guidance that will allow me to flash a Pie (and eventually Q) GSI img via TWRP.
THANKS
why TWRP for GSI??
you can simpely flash the gsi rr using fastboot methode
THE MAXIMUM POWER said:
why TWRP for GSI??
you can simpely flash the gsi rr using fastboot methode
Click to expand...
Click to collapse
No computer. ?
TiTiB said:
No computer.
Click to expand...
Click to collapse
Ohh, my bad, btw never install any images instead of erecovery because you will not be able to recover your tablet as you do not have PC
THE MAXIMUM POWER said:
Ohh, my bad, btw never install any images instead of erecovery because you will not be able to recover your tablet as you do not have PC
Click to expand...
Click to collapse
Thanks @THE MAXIMUM POWER
The "no computer" thing is only temporary, thankfully.
I don't fully understand your post. Do you mean the image overwrites erecovery? When I first rooted my tablet (3-4 months ago) I installed a bunch of gsi's but didn't like them, so went with LOS 15.1 and still have erecovery working—it even started it's download (I was curious).
I'm happy with LOS, but, well TiTiB stands for Tweak it Til it Breaks, sooo....I just can't help myself—gotta have something to, uh, tweak. And, as I said, I want to eventually use Android Q.
TiTiB said:
Thanks @THE MAXIMUM POWER
The "no computer" thing is only temporary, thankfully.
I don't fully understand your post. Do you mean the image overwrites erecovery? When I first rooted my tablet (3-4 months ago) I installed a bunch of gsi's but didn't like them, so went with LOS 15.1 and still have erecovery working—it even started it's download (I was curious).
I'm happy with LOS, but, well TiTiB stands for Tweak it Til it Breaks, sooo....I just can't help myself—gotta have something to, uh, tweak. And, as I said, I want to eventually use Android Q.
Click to expand...
Click to collapse
Yes, i meant do not overwrite any images over erecovery, nice name btw, i used Q on my M5 and it was very buggy, i couldn't even connect to wifi, also im verrrrrry addicted to installing gsis on my tablet, i can not stuck one week without playing around with the Tablet, e. G. Yesterday i was on resurrection remix from openkirin because it it customizable, today i reinstalled the original firmware because it is more beautiful than the stock, tomorrow im going to reinstall rr because i like the stock, after two days lineage and so on and so on.
THE MAXIMUM POWER said:
Yes, i meant do not overwrite any images over erecovery, nice name btw, i used Q on my M5 and it was very buggy, i couldn't even connect to wifi, also im verrrrrry addicted to installing gsis on my tablet, i can not stuck one week without playing around with the Tablet, e. G. Yesterday i was on resurrection remix from openkirin because it it customizable, today i reinstalled the original firmware because it is more beautiful than the stock, tomorrow im going to reinstall rr because i like the stock, after two days lineage and so on and so on.
Click to expand...
Click to collapse
Thanks for clarification. It'll be at least a few months b4 I consider Q—still too new.
Still, I want to track down the "E:Cannot flash images to file systems". I figured out that the TWRP I'm using doesn't have "System Image" as one of the options for flashing, so I was trying to flash the GSI to "System", but need to flash it to "System Image".
The quest continues!
TiTiB said:
Thanks for clarification. It'll be at least a few months b4 I consider Q—still too new.
Still, I want to track down the "E:Cannot flash images to file systems". I figured out that the TWRP I'm using doesn't have "System Image" as one of the options for flashing, so I was trying to flash the GSI to "System", but need to flash it to "System Image".
The quest continues!
Click to expand...
Click to collapse
Well, in order to see the "install as system image", you MUST decrypt your device first and then use the latese petroin twrp, but if your device was stolen by somebody, you will regret the decryption as all your data will be available for him
So i advice u touse the fastboot mode
THE MAXIMUM POWER said:
Well, in order to see the "install as system image", you MUST decrypt your device first and then use the latese petroin twrp, but if your device was stolen by somebody, you will regret the decryption as all your data will be available for him
So i advice u touse the fastboot mode
Click to expand...
Click to collapse
Already decrypted—my M5 almost never leaves the house.
I initially used @Pretoriano80's TWRP. Is that the one? I don't remember why, or even if, I didn't like it at the time. Could be that I just wanted to try something different—very typical for me.
TiTiB said:
Already decrypted—my M5 almost never leaves the house.
I initially used @Pretoriano80's TWRP. Is that the one? I don't remember why, or even if, I didn't like it at the time. Could be that I just wanted to try something different—very typical for me.
Click to expand...
Click to collapse
Good, last time i used this twrp i liked it very much, but i also uninstalled it because it did not install the system images as it should, sometimes it worked, sometimes doesnt
Installed @Pretoriano80's TWRP, RR GSI, and had loops at the RR boot screen. I let it cycle 4 times b4 giving up. Think I'll uninstall Magisk and Xposed (might be a requirement anyway) and try again.
THE MAXIMUM POWER said:
Yes, i meant do not overwrite any images over erecovery, nice name btw, i used Q on my M5 and it was very buggy, i couldn't even connect to wifi, also im verrrrrry addicted to installing gsis on my tablet, i can not stuck one week without playing around with the Tablet, e. G. Yesterday i was on resurrection remix from openkirin because it it customizable, today i reinstalled the original firmware because it is more beautiful than the stock, tomorrow im going to reinstall rr because i like the stock, after two days lineage and so on and so on.
Click to expand...
Click to collapse
So what is your verdict on the GSIs? Is there a pie one with the magnetic cover working for wakeup?
I have the SHT-AL09 C636 on Pie and I have been itching on flashing the GSIs, but I really don't have too much time nowadays to tinker :crying:
Thanks!
jgaviota said:
So what is your verdict on the GSIs? Is there a pie one with the magnetic cover working for wakeup?
I have the SHT-AL09 C636 on Pie and I have been itching on flashing the GSIs, but I really don't have too much time nowadays to tinker :crying:
Thanks!
Click to expand...
Click to collapse
The GSIs are basically and in principle good, but you can not compare them to the original firmware is well built for our device and support all features, take this for example, PUBG run on EMUI way smother than the GSI.
unfortunately, i do not have the magnetic keyboard to test it, btw yours shouldn't support it as the SHT version does not have the conection dots at the buttom
jgaviota said:
So what is your verdict on the GSIs? Is there a pie one with the magnetic cover working for wakeup?
I have the SHT-AL09 C636 on Pie and I have been itching on flashing the GSIs, but I really don't have too much time nowadays to tinker :crying:
Thanks!
Click to expand...
Click to collapse
I haven't tried any since they first came out months ago. I've read good things about EMUI 9.1, though.
BTW, still no success flashing GSI via TWRP. ?
THE MAXIMUM POWER said:
The GSIs are basically and in principle good, but you can not compare them to the original firmware is well built for our device and support all features, take this for example, PUBG run on EMUI way smother than the GSI.
unfortunately, i do not have the magnetic keyboard to test it, btw yours shouldn't support it as the SHT version does not have the conection dots at the buttom
Click to expand...
Click to collapse
Thanks for your reply, I'm talking about a magnetic cover (not the keyboard). Any case with the proper magnets will wake up the device when you open it, it is a very convenient feature in any tablet
jgaviota said:
Thanks for your reply, I'm talking about a magnetic cover (not the keyboard). Any case with the proper magnets will wake up the device when you open it, it is a very convenient feature in any tablet
Click to expand...
Click to collapse
My apologize for misunderstanding, i do not have magnetic cover, i think the openkirin.net roms might work, not sure
So i just succeded in downgrading my A3 by flashing boot.img and system.img through OrangeFox recovery, theres not much more to it(and magic probably).
The phone initially didn't boot and just bootlooped not even showing the boot animation only the A3 screen then i let it sit in my backpack for at least a month or two and went to charge it to continue my testing, and to my suprise i got to see the Samsung boot animation just waited and let it boot and there it was succesfully downgraded.
downgraded from S9CTK1 to U1AQF7
internal storage was formatted beforehand
All apears normal so far
apps work
bluetooth works
wifi works
nfc untested
imei/mac all fine
modem untested but didnt get overwritten and is shown correctly so it should work
Hello mate. Any tips on how to do it? Where did you get Boot and system.img from?
download the stock firmware (for example from here https://sfirmware.com/de/samsung-sm-a320fl/ ) then unzip them then open the contained tar.md5 files with 7zip and extract all the files in them.
(they may still be img.lz4 so download it from here https://github.com/lz4/lz4/releases and drag your files onto the exe)
Good job mate! I got it working. Android 6. Cheers!
gone66 said:
Good job mate! I got it working. Android 6. Cheers!
Click to expand...
Click to collapse
Why is this a good thing?
sketaful said:
Why is this a good thing?
Click to expand...
Click to collapse
downgrading samsung phones was looked at to be impossible, some devices (note 7 for extreme example) lost functionality with newer software. downgrading like this can fix stuff like that.
the note 7 cant charge the battery anymore with the latest software even if the battery was swapped to a safe smaller battery so you can downgrade and still use it with stock firmware as it never really received any custom roms.
Is this works?
Hubertos2002 said:
Is this works?
Click to expand...
Click to collapse
not guaranteed to work, as its pretty much just a janky workaround.
worked fine for my a320fl and a520f may not work on newer models