**Currently this method only works for Oneplus 7 beta.**
You can install Magisk using this method if you or on Oneplus 7 beta 5/6 and have an unlocked bootloader.
Please make a backup before using this. There is a stock boot.img pulled from each release zip in my Gdrive folder if you forget to back yours up.
Make sure you have updated Fastboot from here before flashing.
Downloads: Android 10 Images.
Note:- Currently only for O2 beta 5 and O2 Beta 6 i.e. android 10 beta 5 and beta 6. Try it on your own risk if you do it for other versions. And I can assure you something will break if you are not on these versions.
Code:
1. Download the patched boot.img from the link above
2. Using CMD or Powershell flash the image with this command:
fastboot flash boot magisk_patched.img
3. Reboot to os.
4. Install Magisk Manager Apk after booting to os.
5. (Optional) To flash [URL="https://forum.xda-developers.com/oneplus-7/development/recovery-unofficial-twrp-recovery-t3932943"]TWRP[/URL] grab the latest installer and flash it as a module in Magisk Manager reboot to recovery and install Magisk 20 zip.
7. To return to stock boot image "Non" rooted either grab your own backup boot.img download the stock boot.img from the link above and run this command:
fastboot flash boot boot.img
*Please do this if you are not on beta 5/6*
If you are unable to this, backup your boot.img and send it to me OR if you can do any of this contact me I will find some way
Instructions to patch your own images.
Code:
1. Download [URL="https://androidfilehost.com/?fid=818070582850510260"]payload_dumper-win64.zip[/URL] And extract/copy it to Desktop.
2. Extract your payload.bin from the stock ROM zip and copy it into the payload_input folder.
3. Run the payload_dumper exe.
4. When it's finished open the payload_output folder and copy the Boot.img to Desktop keep it there as a backup.
5. Copy the same boot.img to your internal storage on your phone.
6. Install the Magisk Manager Apk from here: [URL="https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445"]Magisk Manager[/URL]
7. Open Magisk Manager and go to settings and change Update Channel to Beta and go back to the main screen and choose to install and select "Select and Patch a file"
8. Navigate to where you copied your boot.img on the phone.
9. Once it's patched you'll have a magisk_patched.img on your phone in the folder it says on the screen when done.
10. Copy that image to your Fastboot folder on your PC and flash it with
fastboot flash boot magisk_patched.img
Done!
As the great XDA people's saying goes '' I'm not responsible for any issues nuclear attacks or massive explosions from your device."
*Updated for beta6*
Credits:
topjohnwu for Magisk/Manger
geminids14 for payload_dumper-win64
Why exactly does this have a poll and what are we supposed to vote on???
Not sure why this thread was needed at all, the regular root method from the guide still worked when I rooted my OP7 last week
THREAD CLOSED! If interested in the subject please follow this already existing thread:
https://forum.xda-developers.com/oneplus-7/how-to/guide-unlock-bootloader-flash-twrp-root-t3954559
@DevilDipan
XDA Forum Rules (excerpt):
...
5. Create a thread topic or post a message only once, this includes external links & streaming media.
As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer.
You can bump your unanswered question once every 24 hours
Duplicate threads and posts will be removed
Always post in an existing thread if a topic already exists, before creating a new thread.
Use our search function to find the best forum for your device.
Links to an external source are only allowed if relevant to the topic in hand. A description must be included, no copy & pasting from the original source.
Self-promotion is forbidden, this includes blogs, social media and video channels etc. Random links will be removed.
...
15. Keep threads / posts on-topic
Whilst a minor amount of off-topic posting may be overlooked, the general rule is that your posts / threads must be relevant to the Forum / thread in which you are posting.
General Forums - For news and announcements relating to your device.
Q&A Help & Troubleshooting Forums - For all question / request threads and posts. If there is no Q&A Help & Troubleshooting forum, use the General Forum of the relevant device
Accessories Forum - For posts related to accessories relevant to the device
Development Forums (ones with the word development in the title) - For Developers to post release threads e.g. ROMs and Kernels including modifications to kernels, bootloaders, ROMs, etc., as well as R&D development discussion threads designed with an end goal
Themes and Apps Forums - For the posting of Themes and / or Apps as well as announcements & discussions including modifications made to Themes and Apps.
...
Click to expand...
Click to collapse
Related
[Q&A] [YU Yuphoria][ROM][OTA] Mirrors for official Cyanogen roms & OTA updates
Q&A for [YU Yuphoria][ROM][OTA] Mirrors for official Cyanogen roms & OTA updates
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [YU Yuphoria][ROM][OTA] Mirrors for official Cyanogen roms & OTA updates. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
How to roll back everything at STOCK?
Simply put - if i **** up, how to roll back everything including:
# recovery
# bootloader
# kernel
# rom, and stuff, everything to STOCK?
@_NinjaThug
http://forum.xda-developers.com/showpost.php?p=61640119&postcount=11
Titokhan said:
@_NinjaThug
http://forum.xda-developers.com/showpost.php?p=61640119&postcount=11
Click to expand...
Click to collapse
<3 U Tito Thanks!
And BTW, whenever we use Fastboot mode via USB - where should we place the ".ZIP" and ".IMG" files when we're flashing or hot booting recoveries etc.?
In the SDCard or in the fastboot/adb folder in pc?
I wasn't sure so I've placed in both When I rooted.
And one more thing - Do I've to extract that "fastboot flashable zip" file to be able to provide all those files (.img, .bin, .mbn) to the fastboot console when I type those commands?
_NinjaThug said:
<3 U Tito Thanks!
And BTW, whenever we use Fastboot mode via USB - where should we place the ".ZIP" and ".IMG" files when we're flashing or hot booting recoveries etc.?
In the SDCard or in the fastboot/adb folder in pc?
I wasn't sure so I've placed in both When I rooted.
And one more thing - Do I've to extract that "fastboot flashable zip" file to be able to provide all those files (.img, .bin, .mbn) to the fastboot console when I type those commands?
Click to expand...
Click to collapse
Yes, you need to EXTRACT those files ONTO YOUR PC / LAPTOP and run the fastboot commands from the laptop while the phone is connected un FASTBOOT USB mode ....
I don't get the YU logo at start up after flashing zip through fastboot
Iget the battery icon how do i get back YU logo in yuphoria
I recently bought YU yuphoria on android 5010a. I want cynogen on my yuphoria on android how to get it plz tell me about in easy way
HELLO GUYS AGAIN
TODAY IM SHOWING YOU HOW TO ROOT MICROMAX C1 2018
XDA AND IM NOT RESPONSIBLE ANY KIND OF ISSUE WITH YOUR PHONE SO DO IT YOUR OWN RISK
1--DOWNLOAD MAGISK MANAGER APK
2--DOWNLOAD C1 boot.img IMAGE
3--DOWNLOAD SCATTER FILE OF C1
A--COPY BOOT.IMG IN INTERNAL STORAG
B--INSTALL MAGISK MANAGER APK AND OPEN
C--CLICK INSTALL
D--THEN CHOOSE PATCH BOOT IMG
E--CHOOSE INTERNAL STORAGE AND TAP boot.img
F--ZIP FILE DOWNLOAD AND FLASH PROCESS AUTOMATIC FLASH
G--THEN CLOSE IT
H--NOW OPEN FILE MANAGER----MAGISK FOLDER
J--THERE U SEE PATCHED BOOT.IMG FILE
K--RENAME IT ONLY boot.img
l--NOW COPY BOOT.IMG AND SCATTER FILE ON PC MAKE NEW FOLDER {PLACE BOT FILE TOGETHER}
M--OPEN SP FLASH TOOL
N--CLICK SCATTER LOADING OPTION AND SELECT C1 SCATTER
O--ON SP FLASH TOOL U SEE ONLY BOOT OPTION TICK
P--POWER OFF PHONE AND FLASH IT AND REBOOT
Q--NOW YOUR IS ROOTED INSTALL ANY ROOTED APK AND CHECK
watch video
MOD Edit -Links Removed & closed.
5. Create a thread topic or post a message only once, this includes external links & streaming media.
As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer.
You can bump your unanswered question once every 24 hours
Duplicate threads and posts will be removed
Always post in an existing thread if a topic already exists, before creating a new thread.
Use our search function to find the best forum for your device.
Links to an external source are only allowed if relevant to the topic in hand. A description must be included, no copy & pasting from the original source.
Self-promotion is forbidden, this includes blogs, social media and video channels etc. Random links will be removed.
Click to expand...
Click to collapse
boot image
http://www.mediafire.com/file/yr81q4u0c7ql1jj/boot.img/file
scatter file
http://www.mediafire.com/file/idukqwbu9i3don7/MT6737M_Android_scatter.txt/file
Actual steps
I am not running the default version of Micromax c1 it is a developer ROM meaning it does not have root access but it allows me root access through adb
So according to your post to root the device I am supposed to get the boot image of the device to create a patched version of it using magisk and flash it in the boot partition
am I right?
I did that everything is running normally now no root access but magisk won't start now that the only difference
here is what I did
used adb shell to locate the boot image
copied the boot image physically from the device using adb pull
got it patched in magisk
got into fastboot
used "fastboot flash boot boot.img"
this one was the patched file
however, I observe no changes
I cannot use the SP flashtools as in the developer ROM the mt scatter file is different and I get the PMT error or partition error as some call it
do you have any other way to root this device
I made several backups of the boot images just in case and still have a way to flash ROM through fastboot and SP flash tools but I prefer fastboot
if possible I would like to avoid getting my phone factory reset in process of rooting it
I can flash the later Micromax C1 ROM then use your method exactly but I would rather not since it will ease my data on phone and since I have no root access I cannot make a complete backup
Hello,
I have been looking for an answer to this for a while and can't find something.
Current state: Huawei Honor 6X with LineageOS 14.1 (Thanks to the user HassenMirza01 Forum Thread here) and Elite TWRP (Forum Thread here)
Aim: LineageOS 15.1
Problem:
1: There is a Forum Thread on cyanogemods.org talking about a development build. The given download link there is androidfilehost.com.
The problem is that I can't use that file for flashing the OS because there is just a system image called "system_a.img" in the zip-file, nothing else. As far as I know there has to be some more files and folders to be able to flash the OS. When I try to flash the zip with TWRP it says "Invalid zip file format".
2: I tried a different file given on getdroidtips.com, but the given download link ends up here sourceforge.net with an empty project.
My question: Is there a way I am not aware of to flash a single image file?
Alcatel Tetra (5041C) All In One Thread
##############################################################################
UPDATE: 4-20 2020 added direct link to folder with free tools for linux and windows
new Url for our site with the tools and roms:
https://a-team-solutions-downloads.myddns.rocks/Site/ UPDATED 4-20 2020
this is active as of 2/26/20
OUR TG Chat Group for all our best advice and where our book of development Notes live,
Check it out.
https://t.me/Android_General_Chat UPDATE: still live on 4-20 2020
UPDATE:
direct shortcut to free version of our AIOtoolkit tools
Live on 4-20 2020
https://a-team-solutions-downloads.myddns.rocks/Free/AIO-ToolKit/
###############################################################################
This is where you want to start for the Alcatel tetra,
Here you will get root ,
You will get the latest fastboot fix to get a custom recovery and bootloader unlock,
Learn how to flash a gsi on the tetra and get it working correctly.
You will see our tool to get magisk working correctly on a pie gsi 's
You may find gsi images here that are modded to be device specific for the tetra.
You will find links to a device support group where u can get help with trouble shooting if you get into a jam.
And you will find access to a factory tool to unbrick a tetra in the last resort.
There will be no disrespectful language in this thread.
It will not be tolerated here you will be reported to the moderation team if you post
disrespectful/flame-war comments here.
This is not a general discussion thread.
This is The place to find everything you need for your tetra :
ROMs
Recovery
Mods/flashable zips
And precise correct instructions for the use of these.
Disclaimer :
I nor anyone at XDA nor any of the devs who's work you find here are responsible for your actions in choosing to use the tools and methods laid out in this thread.
If you follow the instructions here ,
you do so at
You're Own Risk.....
Bricks and loss of data may happen to your device as a result
You have been warned.
This thread is a work in progress please be patient.
Credits go to :
@diplomatic for mtk-su and his awesome kernel exploitation work which allowed me write access to the device partitions ! Thanks Man!
@clcombs262 for opening the old root question thread that got my associates and I together to work on this device!
@PizzaG for his work on this device, his trick for SugarMTK to get lk downgrade in the beginning. and giving us Sugar MTK login so we can use it to restore the countless times we bricked developing all of this stuff. You're Awesome Bro !
@Spades99 for tinkering and getting hotspot working without a plan on oreo roms , good Idea Bro!
@topjohnwu for magisk and all the wonderful things we get from that!
@AndyYan for the LOS 16 build I modified to be my daily driver rom.
@phhusson For his excellent work on the treble-project and for giving us gsi's to play with. Thanks Man You Rule!
@LgPWN'd For Fastboot-fix, Magisk-Gsi-Helper.zip, porting P.B.R.P and Red-wolf custom recoveries, fixing adb (kinda) in twrp.
and just about everything else...
Special thanks to a lady called Alexandria and @clcombs262 for getting me access to a server to build roms/recoveries for these devices . Hey Thanks A Million You are the Stuff !!!
Twrp Builder for the fist port of twrp for tetra
Fastboot fix:
Fastboot fix:
So most users don't have fastboot access
We have a fix for this.
Ok the very first thing you're going to want to do is gain some type of temporary root shell so that we can downgrade the bootloader by writing directly to the partition so that we can then issue a command to reboot to bootloader and use fastboot to unlock your bootloader and we're going to want to do that without using sugar mtk so that we don't end up with our unlocked device from eBay being relocked like a brand-new Tetra from Walmart.
So we are going to be using a kernel exploit called mtk-su to gain the temp root access.
Here is the kit
https://drive.google.com/open?id=1JfLzT6F66yBj6Qor_t4P9340CwLz5Y18
Instructions For Windows Users:
Instructions from a booted Tetra that has no reboot to fastboot functionality:
Extract this zip.
open the folder location in a terminel/CMD/Powershell window...
enable developers options.> enable OEM unlocking.>enable USB debugging
make sure the drivers are installed for your phone on windows {likely they are }
first get device recognized by adb
./adb devices
accept the prompt on the device.
after this move on
copy paste these commands one by one into terminal...
Code:
./adb push exploit /data/local/tmp/exploit
Code:
./adb push U8M8Y0Y0CT00.mbn /data/local/tmp/lk.bin
Code:
./adb shell chmod +x /data/local/tmp/exploit
Code:
./data/local/tmp/exploit
NOTE: the file exploit is just Mtk-SU renamed to " exploit "
Wait for it to say new UID 0
should now see # instead of $ in the prompt...
then type this command
Code:
dd if=/data/local/tmp/lk.bin of=/dev/block/platform/bootdevice/by-name/lk
after that completes type this...
Code:
reboot bootloader
Now you should see the fastboot prompt...
ENJOY
Instructions For Linux Users:
instructions for linux are the same except,
remove the
Code:
./
from each adb command...
Unlocking the bootloader
Unlock bootloader:
WARNING THIS WILL ERASE ALL OF YOUR DATA
Well this is done the same as any other device with fastboot.
here's how for the neewbz out there.
Code:
fastboot oem unlock
then confirm by pressing the volume-up key on the device
and then type this code to reboot...
Code:
fastboot continue
Let your device fully boot up then go through the setup wizard again {I always skip through it} and re-enable developers options and adb debugging.
Your bootloader should now be unlocked and you will see a warning message each time it boots. this warning can safely be ignored, In fact it can also be removed completely but that's a subject for a different topic.
NOTE:
though your bootloader is unlocked there are 2 files inside the device that will replace your recovery with the stock one on boot if you don't remove them, but you also have to disable dm-varity in the fstab before you remove the files or you'll get a soft brick.
Fstab lives in /vendor/etc partition
the easiest way for most users to fix this is to follow the instructions in this gsi prep package by @PizzaG ,
https://drive.google.com/file/d/1ir_S_fEX3SU3G-Fk7-YFl2z5NXfsIJ5l/view
the thing to remember is that you only need the backup to restore from his package, and DO NOT DO the LK DOWNGRADE from his package it's old and uses sugar MTK to replace LK and it messes up network stuff in the process.
You already completed the LK downgrade if you followed my instructions in the last post.
You should be ready to flash the recovery of your choice, do a backup from that recovery and then follow PizzaG's instructions on how to replace your backup with his one.
then if you wanted cricket-rom restore it all if not just restore /vendor and /system to get gsi working and fstab fixes and to auto remove the files that are in stock system to replace recovery on booting
Flashing the custom recovery
Flashing recovery and choices of recovery:
You can use any recovery that yourself or anyone else ports to the Tetra.
The TWRP images in the pizzaG package work but adb is broken in those.
So if you want TWRP that has ADB functionality "sideload etc."
grab the version here:
https://forum.xda-developers.com/showpost.php?p=79815342&postcount=253
Other Better Alternatives:
Pitch Black Recovery Project Ported By LgPWN'd:
https://forum.xda-developers.com/android/development/unoficial-pitchblack-recovery-alcatel-t3946122
Red-Wolf recovery ported by LgPWN'd:
https://forum.xda-developers.com/android/development/red-wolfrecovery-alcatel-tetra-5041c-t3946121
So Choose your recovery, and flash it in fastboot...
Code:
fastboot flash recovery recovery-file-name
Example :
Code:
fastboot flash recovery TWRP.Tetra.img
after this to get to recovery without booting all the way back to system
Code:
fastboot oem reboot-recovery
You should now be in a custom recovery environment .
Remember if u want to use userdata partition u need to disable variety in fstab mentioned earlier, and u need to format data to f2fs to
Kill the encryption and then reboot to recovery to be able to use data partition.
Also there is a file that will cause the stock recovery to over write your custom one.
/system/bin/install-recovery.sh
Rename it or delete it from custom recovery before rebooting
Also some people have had errors using the menu to format data
From the p.b.r.p port.
If it happens to you, try it from one of the twrp images in pizzaG prep package
The older version works when the newer ones don't sometimes
Enjoy !
ROMs:
Most of the ones listed Here are good :
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
the thing to remember is that you need an image for an Arm A-only Device
How to root the Tetra
Reserved
To root or not to root....?
How to root the Tetra.
To root the tetra, follow up instructions to unlock Bootloader flash recovery
then flash your choice of root.zip
When using LOS roms I prefer to use the addon-su from LiniageOS extras
{google search that ^^^} which works out of box just flash and reboot
or you can also use Magisk which is many peoples favorite.
But to get magisk to work you'll need a few things,
first the latest magisk zip to flash, secondly to get it to show you a root prompt in gsi's you'll need to add back some missing library files.
Luckily Myself and @PizzaG have made a flashable zip that can be flashed from custom recovery to do just that.
It'll be in the attachments to this post.
AND NO THIS MAGISK FIXER WILL NOT WORK FOR ANYTHING BUT A TETRA 5041C !!!
so to get magisk running:
first flash :
Magisk_17.2+(GSI_Android_9-Helper)[7-12-2019].zip
then reboot back to recovery,
then flash magisk latest zip
reboot and enjoy root
Gapps to flash or not to flash....?
This is solely up to personal preference.
some users like google and the convenience of google apps,
some users Absolutely abhor Google and all of it's policies and data collection.
Where to get Google apps.
https://opengapps.org/
How to make them work with custom rom/GSI .
there's a great article on it already here:
https://www.xda-developers.com/how-to-fix-device-not-certified-by-google-error/
Support Group
Device support:
Where to get help FAST if you're stuck.
We are doing most of our development work on a telegram group, here's the links for that, come ask questions, grab latest updates before they are released here on XDA etc.
https://t.me/Android_General_Chat
EDIT: URL FIXED TO POINT TO CORRECT PLACE 03/08/2020
A word about Carriers and networks
lock/unlock status:
Carriers or other third parties that have unlocked your tetra have done so by manipulating the data contained in your NVRAM and NVCONFIG and Simlock partitions....
so you can factory reset , flash boot.img or system.img or vendor.img and still retain your unlock, though you may need to adjust your APN settings depending on your choice of ROM.
How to keep from accidentally re-locking your network:
The only way this happens is when you flash those protected OEM partitions or corrupt the data in said partitions.
The sure-fire way to relock a tetra to At&t is to flash / upgrade it using SugarMTK tool
as it flashes EVERY partition with the latest stock released from the server in china or where-ever.
What you can do if it happens to you....
There's not a lot you can do about it. Your carrier will likely refuse to help, at least thats what other users have reported to me.
What you can do is contact any reputable Unlocking service and most times they can re-un-lock it for you.
BUT NOTE: you want to use someone that has the cable-unlocks via pc and usb cable, not the ones who offer some code as your device likely will never ask for the code if you changed things to get this far.
And
Why we can't discuss it further here...
WELP, the big deal here is liability and the Forum rules of XDA.
We are not to discus these things because they actively seek to bypass Carrier Network Restrictions
and as such it's against XDA rules.
However if you find yourself in this position, you might want to contact someone at our device support group for help/advice as we have had to fix this situation before.
we can at least point you in the right direction,
since here on XDA i'm not allowed to Promote/recommend anyone to help fix this because it'll cost you money PERIOD and that's basically considered advertising.
Bricked Devices
Bricked Devices.
Un-bricking.....
FIRST-OFF WHY HAVE YOU NOT MADE A COMPLETE BACKUP TO STORE SOMEWHERE OFF THE DEVICE TO HELP YOU IN THESE SITUATIONS?
that will be your saving grace in most soft-brick situations, where you can still get to recovery Via button combo or via
Code:
fastboot flash recovery recovery.img && fastboot oem reboot-recovery
To unbrick from a hard brick our only choice for now is SugarMTK.
you can find it in @PizzaG Gsi Prep package...
NOTE:
flashing with sugar restores ALL partitions of the device to factory stock release...
what this means is that even if your carrier or some service unlocked your device to use on networks other than At&t you will NOW be stuck with At&t or cricket or it's MVNO's
SUGAR MTK WILL LOCK THE NETWORK ON YOUR TETRA EVERY TIME
Reserved.
Tools
Miscellaneous
Reserved
Discussion of dual boot and other stuff
We are currently working on.
I there an updated easy way for root yet preferably without pc
Thanks for the guide and fastboot fix. I'm running the LineageOS gsi based on pie, but along the way I have lost the ability to turn on wifi and bluetooth. I'm new to mtk roms, so I was wondering where the firmware for the radios is living.
Idealxtra
Pureindica said:
Idealxtra
Click to expand...
Click to collapse
??
So anybody struggling along here can ask about help or other devices such as Idealxtra on our support group on telegram
https://t.me/Android_General_Chat
Is there an updated easy way for root yet preferably without pc ?
Nope, you can however use mtk-su with a terminal emulator to get tmp root then u could use DD to make a copy of your boot.img
then u can use magisk manager apk to patch said boot.img, and then u can write that back to the device using mtk-su and terminal emulator. but this still requires you to have the device bootloader unlocked i believe or you'll brick
Thanks for the guide and fastboot fix. I'm running the LineageOS gsi based on pie, but along the way I have lost the ability to turn on wifi and bluetooth. I'm new to mtk roms, so I was wondering where the firmware for the radios is living.
i think its in vendor partition
The link for the gsi prep package does not work. Anyone have a new link?
sazechman said:
The link for the gsi prep package does not work. Anyone have a new link?
Click to expand...
Click to collapse
Visit our Website, TeleGram and get AIO ToolKit
Website Down
PizzaG said:
Visit our Website, TeleGram and get AIO ToolKit
Click to expand...
Click to collapse
I have tried to get to your website "http://a-team-solutions.dynu.net/" to no avail. I have tried from many different sources both with and without vpn. I have posted in the thread for the site but have not received a reply. Is the site still available? I would gladly pay for the registered version if it solves my bricked phone problem.
Thanks
Welcome to my latest Thread. Today for the Official Pixel Expierence Builds from the Official Website. This Guide does include the Installation of a custom Recovery which allows Factory Resets and flashing Updates/ROMs. Enjoy!
1. Download and prepare everything
First of all visit: https://developer.sony.com/file/dow...-aosp-android-10-0-kernel-4-14-kumano-latest/
And download the latest Software Binaries from Sony which You will need to flash together with the Boot Image (Kernel).
After that download the ROM File from here: https://download.pixelexperience.org/ and also download the "Recovery Image" which is a Kernel/Boot Image
Get the Magisk Manager Apk from here: https://github.com/topjohnwu/Magisk
Extract the Software Binaries to get the .img File from it.
2. Flash using Fastboot
After getting the Kernel/Boot Image do a patch with the Magisk Manager App (Your Phone doesn't needs to be rooted for that) (The Output File will get called magisk_patched,img from now)
Flash the Software Binaries from SONY with:
Code:
fastboot flash oem_a SW_binaries_for_Xperia_Android...............img
Repeat that step with:
Code:
fastboot flash oem_b SW_binaries_for_Xperia_Android...............img
Now flash the Kernel You got from the Magisk Manager with:
Code:
fastboot flash boot_a magisk_patched.img
And repeat that again for the Second Slot:
Code:
fastboot flash boot_b magisk_patched.img
3. Install using a SD Card or ADB
After flashing the Kernel. Turn Off Your Device and hold the Volume- (Lower) Button together with the Power Button until You see the SONY Logo. Release both Buttons and wait for the Recovery coming up.
Search now for the Apply Update Option and select based on Your preference the ADB or SD Card Method to flash the ROM. Connect Your Xperia to Your PC again and enter:
Code:
adb sideload filename.zip
(In case of using the ADB Method)
Your Device should now flash the selected ZIP File (In our case the Pixel Expierence ROM).
4. Profit
Wipe Your Device now using the Factory Reset of the Recovery. Install the Magisk Patched Kernel Image again using the commands of the second Step of this Guide to keep Magisk functional. Connect Your Phone to a Charger and install the latest Magisk Manager to Your Phone. That's it! Enjoy
What Works:
VoLTE
Wifi Calls
Video Calls over Carrier
Camera Button (Does not start Camera Apps)
Everything!?
Bugs:
None!?
Do you feel some animation lag
Sketch. said:
Do you feel some animation lag
Click to expand...
Click to collapse
Yes. I think there is some Kernel Panic. Not sure but battery life could also be better right?
Think I can fix some stuff with MARS pretty soon.
Google Camera works just fine from Urnyx btw. First Time we can use GCAM 7.x fully!
Link: https://www.celsoazevedo.com/files/android/google-camera/f/changelog1343/#google_vignette
Are all functions of gcam work normally ? (like HDR+,Night sight,Astrophotography mode )
This guide is too difficult for inexperienced users, please make a guide on your youtube Channel, miustone. We need your help!
naygnosuw said:
Are all functions of gcam work normally ? (like HDR+,Night sight,Astrophotography mode )
Click to expand...
Click to collapse
Almost. Astro isn't available. 4K 60FPs Kills the App (don't toggle the 60FPS Button on 4K)
Tabike said:
This guide is too difficult for inexperienced users, please make a guide on your youtube Channel, miustone. We need your help!
Click to expand...
Click to collapse
It feels so simple but I got You. I'm still not sure how I should do it. I have a PC, a Chromebook and a Xperia 5 for recording. While the Xperia needs to get flashed (not usable as Camera). I could make a Video with My Chromebook maybe in 720p and combine it with Screen recording somehow. I'm not a YouTuber but I will give it a shot this week... Promised!
Xperia 1 - J8110, J8170, J9110, 802SO, SO-03L, SOV40 variants - what are they?
and what variant PE Rom support official?
Updated the Guide.
@JOKER.SOHA It's printed on the back of Your Xperia (Bottom). Model Numbers... Choose the right one for You. Don't understand the rest of Your question... Sorry
我没有移动数据。
未检测到SIM卡。
MOD EDIT: Please post only in English according to the FORUM RULES or at least add an English translation below your foreign language(Google translator for example), translation added below:
I don't have mobile data.
The SIM card was not detected.
Looks promising will try after the battery drain/lag is fixed. Also will this room be maintained or is it just take it how it is? Great work either way!
Term1nator3000 said:
Looks promising will try after the battery drain/lag is fixed. Also will this room be maintained or is it just take it how it is? Great work either way!
Click to expand...
Click to collapse
Yeah the drain sucks, but great ROM so far. I'm satisfied and use it as daily driver. You can find the Device Maintainers over the Pixel Expierence Website. This is just a Guide Thread since we don't have TWRP. So the Maintainer is free to open up a official Development Thread but they haven't yet... Someone could ask maybe, it's just copy and paste and would help to talk about Bugs and such
Miustone said:
Yeah the drain sucks, but great ROM so far. I'm satisfied and use it as daily driver. You can find the Device Maintainers over the Pixel Expierence Website. This is just a Guide Thread since we don't have TWRP. So the Maintainer is free to open up a official Development Thread but they haven't yet... Someone could ask maybe, it's just copy and paste and would help to talk about Bugs and such
Click to expand...
Click to collapse
Ahh okay np. Hopefully things will smooth out.
I found PixelExperience's J9110 Install Step and did some comparison.
(Sorry I'm not allowed to post a link by now, but it's easy to find on PE's website.)
PE's install step mentioned that flash PE need to unlocked BL, but your guide didn't mention.
And your guide have a kernel flash step, but PE's install tutorial missing this.
Here is my question:
Is it necessary to unlock the BL? (Because I did this to my old Xperia XZ once, there's a LOT problem for me lol)
Is it necessary to flash latest kernel?
Thanks in advance.
ceplavia said:
I found PixelExperience's J9110 Install Step and did some comparison.
(Sorry I'm not allowed to post a link by now, but it's easy to find on PE's website.)
PE's install step mentioned that flash PE need to unlocked BL, but your guide didn't mention.
And your guide have a kernel flash step, but PE's install tutorial missing this.
Here is my question:
Is it necessary to unlock the BL? (Because I did this to my old Xperia XZ once, there's a LOT problem for me lol)
Is it necessary to flash latest kernel?
Thanks in advance.
Click to expand...
Click to collapse
It isn't possible to flash anything besides Stock in Flashmode with a locked Bootloader. That's one of the Basic Things on Android. That's why it isn't mentioned here... You should carefully learn how everything works before thinking about to flash anything on Your Device...
The Pixel Expierence Guides for Xperias are wrong and do Not Work btw. That's the reason for My Guides...
Best Regards
Miustone said:
Yes. I think there is some Kernel Panic. Not sure but battery life could also be better right?
Think I can fix some stuff with MARS pretty soon.
Google Camera works just fine from Urnyx btw. First Time we can use GCAM 7.x fully!
Link: https://www.celsoazevedo.com/files/android/google-camera/f/changelog1343/#google_vignette
Click to expand...
Click to collapse
Hi, rom maintainer here, just to precise that a kernel panic would totally freeze your phone and you'll be unable to do anything except force reboot your phone.
Also, responding on another thing I saw on this thread, the only reason I don't open an xda thread per device supported is that I would have to update like 25 threads every month, respond the same questions for all those threads over and over etc
I have my telegram for that t.me/PixelExperienceSony
I might do 1 thread for all devices in cross platform dev section.
Cheers
can someone please make a step by step YouTube YouTube guide? I tried to follow the instructions with little sucess
Totally missed the dtbo.img flashing which prevents the Device from booting. You will need that Tool: https://androidfilehost.com/?fid=818070582850510260
To extract the payload.bin file inside of the Pixel Expierence Zips. Put the Payload Bin in the Input Folder and Start the Exe to extract the Bin File. You will get a dtbo.img file which you will need to flash like:
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
Together with the boot/magisk Images which will allow You to boot into the Recovery Mode by holding VolumeDOWN & the Power Button
Enjoy and sorry for the trouble! I will also update this Threads next just like My Rooting Threads.
Miustone said:
Totally missed the dtbo.img flashing which prevents the Device from booting. You will need that Tool: https://androidfilehost.com/?fid=818070582850510260
To extract the payload.bin file inside of the Pixel Expierence Zips. Put the Payload Bin in the Input Folder and Start the Exe to extract the Bin File. You will get a dtbo.img file which you will need to flash like:
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
Together with the boot/magisk Images which will allow You to boot into the Recovery Mode by holding VolumeDOWN & the Power Button
Enjoy and sorry for the trouble! I will also update this Threads next just like My Rooting Threads.
Click to expand...
Click to collapse
bro can you share the steps how to install.
do i need python to run the payload extract?
i cant flash the rom and cant use the phone, loop in the boot 5sec will restart ..
VOLTE not working in india with JIO network...
Were you able to get the Volte working on Indian networks?.