Related
Dear XDA Members,
I currently run stock 5.1.1 (14.6.A.1.236) with no modifications whatsoever and a locked bootloader.
I would like to install a custom rom (PAC-ROM LP-MR1 5.1.1) on my Z1C.
I did some research and these are the steps i came up with:
1. install sdk and drivers
2. unlock bootloader
3. fastboot flash recovery "fota.img" (shouldn't it specify somehow that i need it to be flashed on the fota partition?)
4. factory reset/wipe
5. install custom rom + gapps
Coming from a locked bootloader a fully stock phone is there anything else i need to do like a new bootloader or something?
Also I'll be doing it through Win 10 64bit, I hope that isn't a problem.
Any advice will be highly appreciated.
Thank you very much
ursidae1 said:
Dear XDA Members,
I currently run stock 5.1.1 (14.6.A.1.236) with no modifications whatsoever and a locked bootloader.
I would like to install a custom rom (PAC-ROM LP-MR1 5.1.1) on my Z1C.
I did some research and these are the steps i came up with:
1. install sdk and drivers
2. unlock bootloader
3. fastboot flash recovery "fota.img" (shouldn't it specify somehow that i need it to be flashed on the fota partition?)
4. factory reset/wipe
5. install custom rom + gapps
Coming from a locked bootloader a fully stock phone is there anything else i need to do like a new bootloader or something?
Also I'll be doing it through Win 10 64bit, I hope that isn't a problem.
Any advice will be highly appreciated.
Thank you very much
Click to expand...
Click to collapse
First things first... Root. If you already did that then you're on the right track.
1. If you're not doing major development stuff, don't install the whole sdk. See here - http://forum.xda-developers.com/showthread.php?p=48915118 There may be issues you'll have to work with on newer versions of Windows. I haven't done it on anything later than 7. Keep in mind, though, that you won't need the computer to flash your boot img or rom, but you will need it to unlock the bootloader.
2. -
3. You can do this with an app called Rashr on your phone with root. Just download a recovery img, then open Rashr and follow the instructions.
4-5. Boot into recovery, full wipe, (system data and caches), flash rom zip and gapps zip. Maybe best to not flash more than that at once to start, in case there's a problem and you have no way to figure out what it is.
BTW, PacMan is a great choice. I've been using it for months.
levone1 said:
First things first... Root. If you already did that then you're on the right track.
1. If you're not doing major development stuff, don't install the whole sdk. See here - http://forum.xda-developers.com/showthread.php?p=48915118 There may be issues you'll have to work with on newer versions of Windows. I haven't done it on anything later than 7. Keep in mind, though, that you won't need the computer to flash your boot img or rom, but you will need it to unlock the bootloader.
2. -
3. You can do this with an app called Rashr on your phone with root. Just download a recovery img, then open Rashr and follow the instructions.
4-5. Boot into recovery, full wipe, (system data and caches), flash rom zip and gapps zip. Maybe best to not flash more than that at once to start, in case there's a problem and you have no way to figure out what it is.
BTW, PacMan is a great choice. I've been using it for months.
Click to expand...
Click to collapse
Thanks a lot for your reply.
I was reading on the cyanogen mod wiki how-to for our phone and it doesn't require a prior root.
I did those steps on my xperia m and it worked and i had never rooted it, the only difference is that i flashed cyanogen recovery and install cm12 which basically roots the phone and then flashed fota recovery.
Should i go this way again to gain root or would you recommend an easier root method for my stock build which is the newest.
If you recommend another root method when should it occur? prior unlocking the bootloader or afterwards?
Thanks
If this is your first time unlocking your bootloader, make sure you backup your DRM-Keys! You need to be rooted for that.
They are lost when bootloader gets unlocked. Some features in regards of camera performance are lost for example.
ursidae1 said:
Thanks a lot for your reply.
I was reading on the cyanogen mod wiki how-to for our phone and it doesn't require a prior root.
I did those steps on my xperia m and it worked and i had never rooted it, the only difference is that i flashed cyanogen recovery and install cm12 which basically roots the phone and then flashed fota recovery.
Should i go this way again to gain root or would you recommend an easier root method for my stock build which is the newest.
If you recommend another root method when should it occur? prior unlocking the bootloader or afterwards?
Thanks
Click to expand...
Click to collapse
True, if bl is unlocked, then you can flash the kernel and recovery via fastboot, then flash your rom. You may need the boot.img from your rom zip file. Then use commands 'fastboot flash boot' for the boot img, and 'fastboot flash recovery' for recovery. If you're rooted already, you can just do it on the phone.
levone1 said:
True, if bl is unlocked, then you can flash the kernel and recovery via fastboot, then flash your rom. You may need the boot.img from your rom zip file. Then use commands 'fastboot flash boot' for the boot img, and 'fastboot flash recovery' for recovery. If you're rooted already, you can just do it on the phone.
Click to expand...
Click to collapse
This is fantastic.
Do you think itll be ok to fastboot flash boot boot.img from cm12.1 rom zip then fastboot flash recovery fota.img instead of the cyanogen recovery that comes with cm12.1?
Do you think that might cause an issue?
ursidae1 said:
This is fantastic.
Do you think itll be ok to fastboot flash boot boot.img from cm12.1 rom zip then fastboot flash recovery fota.img instead of the cyanogen recovery that comes with cm12.1?
Do you think that might cause an issue?
Click to expand...
Click to collapse
Should be fine. It's also a 1 second operation to extract boot.img from your rom zip, which you need already downloaded and on your SD card before you flash imgs. You might even be fine without flashing the boot img - can't hurt to try. Just flash the recovery and reboot and see if you get a purple light. Then, volume button changes purple to orange, and you're in recovery. Some recoveries don't work with some kernels, (been my experience).
levone1 said:
Should be fine. It's also a 1 second operation to extract boot.img from your rom zip, which you need already downloaded and on your SD card before you flash imgs. You might even be fine without flashing the boot img - can't hurt to try. Just flash the recovery and reboot and see if you get a purple light. Then, volume button changes purple to orange, and you're in recovery. Some recoveries don't work with some kernels, (been my experience).
Click to expand...
Click to collapse
I now have cm12.1 with cyanogen recovery.
Which recovery is best for our phone, which one do you use?
I can find 2 options:
FOTA TWRP 2.8.6.0 (http://forum.xda-developers.com/sony-xperia-z1-compact/general/fota-twrp-recovery-amami-t2909719)
XZDualRecovery (http://forum.xda-developers.com/showthread.php?t=2647480)
Thanks a lot
ursidae1 said:
I now have cm12.1 with cyanogen recovery.
Which recovery is best for our phone, which one do you use?
I can find 2 options:
FOTA TWRP 2.8.6.0 (http://forum.xda-developers.com/sony-xperia-z1-compact/general/fota-twrp-recovery-amami-t2909719)
XZDualRecovery (http://forum.xda-developers.com/showthread.php?t=2647480)
Thanks a lot
Click to expand...
Click to collapse
I have only used xzdr with stock rom. I think in the past I've had it not work for me on CM, so I just stick to straight twrp by default. I know NUT has always been hard at work and has made steady improvements, so maybe not an issue now. Personally I realized that I only need 1 recovery anyway. There's a newer Twrp here - http://forum.xda-developers.com/crossdevice-dev/sony/twrp-v2-8-6-0-f2fs-z1-z1c-z2-z3-z3c-t3098573
One important fact that has already been probably mentioned is that installing custom roms on your XPERIA will worsen your camera, esp the front one. Keep this in mind.
I have a brand new Pixel XL from Verizon that I received today and was successful in unlocking. However, I tried to root and now I am stuck on bootloop. I cannot post in DEVELOPMENT because I haven't posted here in years (haven't had ANDROID in a while). Can anyone help? I am able to access via fastboot (I believe) but I must be flashing the wrong images. I don't want to brick this nice new day-old device. I have been at it for 5 hours via research on my own, but now I am looking for someone that can help me via P.M. or what it may take. I really want to get back to enjoying this device! Thanks in advance!
bdsuser said:
I have a brand new Pixel XL from Verizon that I received today and was successful in unlocking. However, I tried to root and now I am stuck on bootloop. I cannot post in DEVELOPMENT because I haven't posted here in years (haven't had ANDROID in a while). Can anyone help? I am able to access via fastboot (I believe) but I must be flashing the wrong images. I don't want to brick this nice new day-old device. I have been at it for 5 hours via research on my own, but now I am looking for someone that can help me via P.M. or what it may take. I really want to get back to enjoying this device! Thanks in advance!
Click to expand...
Click to collapse
Read the third post in the thread below to get set up and back to stock. Then we will work on root. If you tried to root and you bootlooped it then you used the wrong SU.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242
1. Download a ROM. A stock version is probably in the forums somewhere if that's what you want.
2. Download TWRP image and zip from the TWRP thread.
3. Download SuperSU from the SuperSU thread.
4. Download a vendor image. There's no "official" vendor image thread AFAIK, but you can grab one from the Pure Nexus rom thread. NMF26V is compatible with all 7.1.1 ROMs & stock.
Now you have two options:
Fast: Put the ROM, TWRP(zip only), SuperSU and vendor image on USB flash drive, then connect the USB 3 to USB C adapter to your flash drive. Don't connect it to the phone yet. An external HDD/SSD should also work if that's all you've got.
Slow: While in TWRP(Instructions below) push the ROM, TWRP(zip only), SuperSU and vendor image files to your phone through ADB with "adb push C:\file_path\ /sdcard/" sans quotes. You will need to do this for each file, or alternatively push a folder containing the four files. adb file transfer is very slow.
5. Boot your phone to the bootloader, and connect it to your computer. This can be achieved by holding volume down and power from an off state.
Note: If your device is still bootlooping you won't be able to get to the bootloader. Hold volume up and power until the device shuts off to get out of the bootloop temporarily, then boot to bootloader.
6. In a command window, "fastboot boot twrp.img"
7. Connect your flash drive to your phone if you chose that option, or push the files through adb if you chose that option
8. Flash TWRP zip, ROM and vendor image. STAY IN TWRP
9. Return to TWRP's home screen > advanced > file manager. Scroll down until you see 'fstab.marlin'(in the root '/' directory). Tap on 'fstab.marlin' and delete it. Skipping this step means SuperSU won't install.
10. Flash SuperSU zip, reboot to system and you're done.
SDK
TonikJDK said:
Read the third post in the thread below to get set up and back to stock. Then we will work on root. If you tried to root and you bootlooped it then you used the wrong SU.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242
Click to expand...
Click to collapse
Just thought I'd update you...And I know I sound like I have no idea what I'm doing but traditionally I've never had issues like this But I am trying to get ADB to show the flash-all command. The one I have installed doesn't show that feature so I can't follow the tutorial. If you have a direct link to what I may be missing I would appreciate it otherwise I will update you once I figure it out.
bdsuser said:
Just thought I'd update you...And I know I sound like I have no idea what I'm doing but traditionally I've never had issues like this But I am trying to get ADB to show the flash-all command. The one I have installed doesn't show that feature so I can't follow the tutorial. If you have a direct link to what I may be missing I would appreciate it otherwise I will update you once I figure it out.
Click to expand...
Click to collapse
The link to the proper adb and fastboot are in the post i pointed you to.
Help with root and TWRP
TonikJDK said:
The link to the proper adb and fastboot are in the post i pointed you to.
Click to expand...
Click to collapse
Thanks for your assistance. I now have root installed and I think I'm good except for one thing. I keep thinking TWRP is installed but for some reason when I reboot to bootloader, then select reboot recovery mode, it takes me to android recovery. I am used to recovery taking me to TWRP. I know TWRP works but I feel like I'm temporarily flashing it each time or something. I even installed the twrp app and I see I can flash zips that way, etc, but I wanted to know if you knew how to make the phone boot to TWRP in recovery? Or is that necessary?
bdsuser said:
Thanks for your assistance. I now have root installed and I think I'm good except for one thing. I keep thinking TWRP is installed but for some reason when I reboot to bootloader, then select reboot recovery mode, it takes me to android recovery. I am used to recovery taking me to TWRP. I know TWRP works but I feel like I'm temporarily flashing it each time or something. I even installed the twrp app and I see I can flash zips that way, etc, but I wanted to know if you knew how to make the phone boot to TWRP in recovery? Or is that necessary?
Click to expand...
Click to collapse
I dont do it that way on this phone. TWRP and SU are modifying the same parts of the phone, and there are cases where it could conflict. Rare, not a big deal, but since i don't need TWRP installed i don't.
To install it ypu first boot to it.
Fastboot boot twrpFilename.
Then from within TWRP you install the TWRP zip.
Make sure it is TWRP RC1
All set
Thanks again for your help. I am running pure ROM as I mentioned and I seem to like it. Do you K or if Franco works with Pure or do you have a suggestion on a good rom/kernel? Is there anything else that you can suggest I should be using with the new phone? I remember there used to be tools that you could install that allowed you to customize the system even further but the name escapes me. . Is there anything like that or even a theme tool which is a must have when you are rooted and running custom roms? No big deal if not. Very happy with where I stand now. Really appreciate you getting me back up and running!
You are most welcome. I don't ROM so I don't know what kernels work with what roms for sure. But my understanding is that they are all pretty universal. I run stock with Franco.
Other than that i dont mod much. Ad blocker, black themes and a few adjustments to Franco.
TonikJDK said:
You are most welcome. I don't ROM so I don't know what kernels work with what roms for sure. But my understanding is that they are all pretty universal. I run stock with Franco.
Other than that i dont mod much. Ad blocker, black themes and a few adjustments to Franco.
Click to expand...
Click to collapse
Perfect! Thanks yet again. Have a great remainder of the day!
bdsuser said:
Thanks again for your help. I am running pure ROM as I mentioned and I seem to like it. Do you K or if Franco works with Pure or do you have a suggestion on a good rom/kernel? Is there anything else that you can suggest I should be using with the new phone? I remember there used to be tools that you could install that allowed you to customize the system even further but the name escapes me. . Is there anything like that or even a theme tool which is a must have when you are rooted and running custom roms? No big deal if not. Very happy with where I stand now. Really appreciate you getting me back up and running!
Click to expand...
Click to collapse
Im running pure and elementalx with excellent results.
?Tapped from my pure pixelXl?
have you ever seen an issue where the phone boots to twrp even though everything was working fine? It starts happening if I do a restart. Then no matter what it boots into TWRP unless I wipe again? I believe it's happening after I flash root but I'm going out of my mind with trial and error. Any help would be appreciated.
bdsuser said:
have you ever seen an issue where the phone boots to twrp even though everything was working fine? It starts happening if I do a restart. Then no matter what it boots into TWRP unless I wipe again? I believe it's happening after I flash root but I'm going out of my mind with trial and error. Any help would be appreciated.
Click to expand...
Click to collapse
HELLO!!! I understand any frustrations you may be having, as the pixel devices have changed a good bit for us as far as development. Anyways. I'm just going to throw some knowledge out there, then proceed to help get you up and running!
You couldn't post in the development section because of your post count, but even if you could, it would have been in the wrong section and it would have been removed, or moved to the questions section.
Also, I see someone has pointed it out earlier, but I'll say it again just to make sure everything is clear. The command you were running "fastboot boot TWRP.img" only boots TWRP temporarily. You are suppose to have two files, one IMG file and one zip file. You boot the IMG file, then once you're in TWRP, you flash the zip file, then reboot to recovery and you will have installed TWRP properly.
With root, flashing wrong files or using the outdated root method will cause boot loops. The correct way to root (again already been said) is the get TWRP up and running, delete the fstab file (see earlier post) then flash SuperSU and reboot. Just throwing this out there Incase someone comes across it, if you manage to boot loop your device due to to rooting, you can fastboot flash franco's kernel and it will fix the bootloop (,but you won't have root) this isn't the correct way to fix it, but it will get you back up and running without downloading the large factory image.
***About to edit this post to continue giving more info***
Here is a correct guide and good template to get you running.
start by flashing a clean factory image, then let it boot and get it set up.
Reboot to fastboot, fastboot boot TWRP IMG then flash TWRP zip using the latest versions (RC1 is latest, pm me for more info).
Reboot the phone to recovery to ensure TWRP stuck.
Go-to advanced, file manager in TWRP and find the fstab.marlin file and delete.
Then you can go ahead and flash the latest SuperSU (I use 2.79 sr3) and when it's done reboot to system and verify root.
After rooting you can go ahead and flash a kernel if you want, I use elemental which you can flash in TWRP, but see the kernel instructions prior to flashing.
Reboot and you have a nice stock ROM with root and kernel.
For flashing Roms, kind of follow the same template, most Roms require you to flash part of or the whole latest factory image.
If your on a clean install, go ahead and install TWRP as mentioned above.
Then use TWRP to install whatever ROM you want per ROM developer instructions.
Side note, some Roms replace the TWRP with cwm or stock recovery, so it's always nice to flash the TWRP zip after flashing a ROM.
After flashing ROM, boot to system to make sure all is well, then boot back to recovery and follow instructions above for root/kernel.
As far as the problem you're having now, it usually comes from flashing outdated SuperSU images. Do a search for 2.79 sr3 and use it to root (pm me if you need help)
You might have to start clean one more time, And flash factory image.
noidea24 said:
HELLO!!! I understand any frustrations you may be having, as the pixel devices have changed a good bit for us as far as development. Anyways. I'm just going to throw some knowledge out there, then proceed to help get you up and running!
You couldn't post in the development section because of your post count, but even if you could, it would have been in the wrong section and it would have been removed, or moved to the questions section.
Also, I see someone has pointed it out earlier, but I'll say it again just to make sure everything is clear. The command you were running "fastboot boot TWRP.img" only boots TWRP temporarily. You are suppose to have two files, one IMG file and one zip file. You boot the IMG file, then once you're in TWRP, you flash the zip file, then reboot to recovery and you will have installed TWRP properly.
With root, flashing wrong files or using the outdated root method will cause boot loops. The correct way to root (again already been said) is the get TWRP up and running, delete the fstab file (see earlier post) then flash SuperSU and reboot. Just throwing this out there Incase someone comes across it, if you manage to boot loop your device due to to rooting, you can fastboot flash franco's kernel and it will fix the bootloop (,but you won't have root) this isn't the correct way to fix it, but it will get you back up and running without downloading the large factory image.
***About to edit this post to continue giving more info***
Here is a correct guide and good template to get you running.
start by flashing a clean factory image, then let it boot and get it set up.
Reboot to fastboot, fastboot boot TWRP IMG then flash TWRP zip using the latest versions (RC1 is latest, pm me for more info).
Reboot the phone to recovery to ensure TWRP stuck.
Go-to advanced, file manager in TWRP and find the fstab.marlin file and delete.
Then you can go ahead and flash the latest SuperSU (I use 2.79 sr3) and when it's done reboot to system and verify root.
After rooting you can go ahead and flash a kernel if you want, I use elemental which you can flash in TWRP, but see the kernel instructions prior to flashing.
Reboot and you have a nice stock ROM with root and kernel.
For flashing Roms, kind of follow the same template, most Roms require you to flash part of or the whole latest factory image.
If your on a clean install, go ahead and install TWRP as mentioned above.
Then use TWRP to install whatever ROM you want per ROM developer instructions.
Side note, some Roms replace the TWRP with cwm or stock recovery, so it's always nice to flash the TWRP zip after flashing a ROM.
After flashing ROM, boot to system to make sure all is well, then boot back to recovery and follow instructions above for root/kernel.
As far as the problem you're having now, it usually comes from flashing outdated SuperSU images. Do a search for 2.79 sr3 and use it to root (pm me if you need help)
You might have to start clean one more time, And flash factory image.
Click to expand...
Click to collapse
There is absolutely no need to delete the fstab file anymore. That only needed to be done when TWRP was still alpha 2, and almost three versions of su earlier.
ALL roms replace TWRP with stock recovery unless you are using lineage then you will get Cyanogenmod recovery, so reflashing TWRP before booting into system is a must.
If you are flashing root and or custome kernel and end up in a bootloop, flashing the stock boot.img to both slots via:
'fastboot flash --slot _a boot boot.img'
'fastboot flash --slot _b boot boot.Img'
will fix the issue and you will be able to boot up just fine. Again you will have to reboot into TWRP from the bootloader and reflash the zip. When you are done flashing the boot.img's you might as well just
'Fastboot boot TWRP-file.img'
Then install the zip!
So as the title says, need collective experience to make the move, and be preemptive along the way of the possible pitfalls and limitations.
Havent experimented much with my XL 128GB lying circa 2018 when i bought it and it still runs fine. As of now it is :
1. Google model (not any carrier branded unit).
2. Android V 8.0.0
3. Bootloader Unlocked (OEM Unlocking enabled int he Developer Options)
4. Rooted.
5. Custom recovery TWRP 3.2.0.-0 installed.
My primary intended use was to make it my music player with AptX-HD and LDAC enabled via the Developer Options, for my wireless hifi headphones and it has been doing so.
As an semi-audioholic I have Viper4Android and Dolby ATMOS working fine on it, with Sony Walkman App, these were only found to work correctly on 8.0.0 as i did spent a great deal of time to make them work with 8.1.1 back in the day.
So I am looking for the most safest route to upgrade to 10.0.0 with the possibility of knowing if the below would remain applicable.
1. Should I go for OTA update as-is OR Do i need to relock bootloader or Un-root before the OTA update. (Any sequence or specific steps to be followed).
2. Will the OTA update lock the bootloader and will remove the root privileges.
3. Is it possible to unlock the bootloader and re-root the device on v.10.0.0 (any guide link appreciated).
4. Will the OTA overwrite the TWRP recovery, is there any newer/better recovery + kernel available with V.10.0.0 (any guide link appreciated).
5. Will ARISE audio (Viper + Dolby + Sony Music Apps) work on the latest android version.
6. Is all the hassle recommended, if the experience is significantly better on v.10.0.0. Any known issues with the latest android, which I should be aware of.
7. Any alternate way and/or newer/better DSP recommended to work with v.10.0.0 for sound enhancements.
8. Is Magisk framework and module working with v.10.0.0.
Thanks for reading and replying , as it would chalk out a path not only for me but for community at large for someone on a similar quest as mine.
Appreciate your input.
1. Download a pixel factory image from Google(latest is Dec 2019) and flashed it using fastboot( u will find guide on xda or YT)
2 Do not relock botloader if you want to root or install custom rom
3. Dolby Atmos will not work,if you flash Dolby Atmos mod zip in magisk it may cause bootloop .viper fx may work never tried
4. Android 10 is much better in user experience it is smooth
5. You can root your phone using latest magisk in twrp
6. There are some good kernel available for android 10 for pixel like Elemental x 5.6, king kernel v6.1, etc.
7. There is no sound enhancement mod for android 10, viper may work
8. U can't do some system modification like changing boot animation, system sound, font by yourself. If u want customization u can install custom rom though
My english is bad
hope this will help u
bhaskarjyotisarmah51 said:
1. Download a pixel factory image from Google(latest is Dec 2019) and flashed it using fastboot( u will find guide on xda or YT)
2 Do not relock botloader if you want to root or install custom rom
3. Dolby Atmos will not work,if you flash Dolby Atmos mod zip in magisk it may cause bootloop .viper fx may work never tried
4. Android 10 is much better in user experience it is smooth
5. You can root your phone using latest magisk in twrp
My english is bad
hope this will help u
Click to expand...
Click to collapse
Thanks
Sure just few last questions :
1. Will pixel factory image also overwrite the recovery.
2. Can I install a custom recovery after v10.0.0.
3. Do i install custom recovery first after V10.0.0. or should I root first. Sorry I am outta practice for some time
4. Any issues in v10.0.0 which I should be aware of. (Battery Drain, Lags or anything else).
5. Any guide for installing Magisk on V10.0.0
Thanks for your response
HyperEscape said:
Thanks
Sure just few last questions :
1. Will pixel factory image also overwrite the recovery.
2. Can I install a custom recovery after v10.0.0.
3. Do i install custom recovery first after V10.0.0. or should I root first. Sorry I am outta practice for some time
4. Any issues in v10.0.0 which I should be aware of. (Battery Drain, Lags or anything else).
5. Any guide for installing Magisk on V10.0.0
Thanks for your response
Click to expand...
Click to collapse
1 Yes pixel factory image will overwrite custom recovery
2. You can install a custom recovery as well as custom rom after 10
3. You don't need custom recovery permanently installed to root your phone. ( Temporary boot into twrp using fastboot and twrp.img and install magisk)
4. If you pixel is old consider a Battery drain as battery life decreases with age
5. Follow the link
https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-10-0-q-t3964112
bhaskarjyotisarmah51 said:
1 Yes pixel factory image will overwrite custom recovery
2. You can install a custom recovery as well as custom rom after 10
3. You don't need custom recovery permanently installed to root your phone. ( Temporary boot into twrp using fastboot and twrp.img and install magisk)
4. If you pixel is old consider a Battery drain as battery life decreases with age
5. Follow the link
https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-10-0-q-t3964112
Click to expand...
Click to collapse
I cant get the latest TWRP to actually stay flashed on Android 10... Have you had any issues?
GalaxyWhy said:
I cant get the latest TWRP to actually stay flashed on Android 10... Have you had any issues?
Click to expand...
Click to collapse
Actually I never permanently install TWRP. If the latest TWRP not works for you try using earlier version and see if that works.
bhaskarjyotisarmah51 said:
Actually I never permanently install TWRP. If the latest TWRP not works for you try using earlier version and see if that works.
Click to expand...
Click to collapse
Can you please elaborate on the reasons of it, and how do you do a non-permanent install.
Thanks.
HyperEscape said:
Can you please elaborate on the reasons of it, and how do you do a non-permanent install.
Thanks.
Click to expand...
Click to collapse
TWRP is Optional. It's written over there in the OP of each Rom
I always did USB debugging option enabled in developer option and give my PC Authorization. So if something goes wrong I can always flash a factory image. In Android 10 I can't make a nandroid backup of the stock rom before flashing any custom rom. so there no point to install TWRP permanently because if something goes wrong u can't restore a backup. If I want in flash any zip in TWRP I always temporary boot into it using fastboot and flash.
TWRP will be permanently needed when you want to install ota updates for the ROM.
I am not an expert though
Please follow the OP :good:
Hello.
I have the Samsung A22 4G (SM-a225m) And want to custom rom it, but how? I am hating one ui and really want to change to a custom rom, I know how to install custom recoveries like TWRP but I dont really know the custom rom installation. If someone could help me do it and send me the link of the file and how to install it. Thanks anyway.
if you follow this guide https://forum.xda-developers.com/t/...axy-a22-sm-a225f-a225m-android-11-12.4333305/ after installing twrp, there should be a gsi installing method and follow that, but be warned, bluetooth headphones dont output audio from my knowledge and you have to go into phh setttings, samsung features and alternative audio policy, speakers will work but you cant control audio, thats why you follow this guide https://forum.xda-developers.com/t/...stem-that-wont-let-you-change-volume.4550239/ for a workaround to control audio. Hope it helps!
It does not work, I had to reflash stock rom again, I would prefer someone having the a225m with a custom rom to tell me how to do it, the guide doesnt work
cervigil said:
It does not work, I had to reflash stock rom again, I would prefer someone having the a225m with a custom rom to tell me how to do it, the guide doesnt work
Click to expand...
Click to collapse
I have the A225M, some custom roms do not boot, for example project elixer does not boot but spark os 13 gsi is working and boots fine, just go into twrp and click restart restart fastboot then you type fastboot devices to check if the device is detected, then you type fastboot flash system pathtogsi.img then type fastboot reboot, if the device keeps rebooting, the gsi is not bootable, hope it helps!
what version do you used? bvn or bgn?
cervigil said:
what version do you used? bvn or bgn?
Click to expand...
Click to collapse
I believe you should try to go with BgN whenever you can
I installed it and wifi and bluetooth doesnt work
go to this guide https://forum.xda-developers.com/t/fusion-kernel-for-a225f-a225m-android-11-12.4337511/ and flash the kernel via twrp, has wifi drivers but bluetooth should work by default
I was trying to get dolby atmos on awakenOS, the device is unlocked and was rooted.
I was trying to get a magisk module going for the dolby atmos. As instructed I flashed the magisk 26.0 and all was good but as soon as I flashed the miui core module the device started bootlooping.
To try to fix that I reflashed the boot.img and vendor.boot for the awakenos to reflash the rom and to get the device back . but as soon as I reached the part of adb rebooting to sideload, I reached the sideload but after dragging the rom zip it always says cannot read anymore. Every time I manually boot into recovery I still find the device in sideload. adb commands such as adb reboot and reboot to recovery seem to be doing nothing to the device anymore
Hidden_Iye said:
I was trying to get dolby atmos on awakenOS, the device is unlocked and was rooted.
I was trying to get a magisk module going for the dolby atmos. As instructed I flashed the magisk 26.0 and all was good but as soon as I flashed the miui core module the device started bootlooping.
To try to fix that I reflashed the boot.img and vendor.boot for the awakenos to reflash the rom and to get the device back . but as soon as I reached the part of adb rebooting to sideload, I reached the sideload but after dragging the rom zip it always says cannot read anymore. Every time I manually boot into recovery I still find the device in sideload. adb commands such as adb reboot and reboot to recovery seem to be doing nothing to the device anymore
Click to expand...
Click to collapse
Hello.
The Modules work perfect for me. You need to unbrick your device now by going back to MIUI. Are you able to go to Fastboot Mode?
nabulsi08 said:
Hello.
The Modules work perfect for me. You need to unbrick your device now by going back to MIUI. Are you able to go to Fastboot Mode?
Click to expand...
Click to collapse
Yeah I've tried to reflash the boot.img and the vendor from awakenos devs. And was also successful in flashing the rom but the device still bootloops
Hidden_Iye said:
Yeah I've tried to reflash the boot.img and the vendor from awakenos devs. And was also successful in flashing the rom but the device still bootloops
Click to expand...
Click to collapse
If you are able to go to Fastboot Mode, do the Following things: Download the official Mi Flash Tool and the latest MIUI Version. Flash the extracted ROM and choose the option "Clean all". Your device needs to be back on MIUI to be unbroken safely. You may find a way to unbrick it without flashing MIUI but what I said is what I recommend.
nabulsi08 said:
If you are able to go to Fastboot Mode, do the Following things: Download the official Mi Flash Tool and the latest MIUI Version. Flash the extracted ROM and choose the option "Clean all". Your device needs to be back on MIUI to be unbroken safely. You may find a way to unbrick it without flashing MIUI but what I said is what I recommend.
Click to expand...
Click to collapse
Thank you it worked! I'm back on MIUI and will be going back to AwakenOS. btw so for now is there no other way of getting Dolby on AwakenOS?
Thank you for your time, you guys make this place better with all the help you share.
Hidden_Iye said:
Thank you it worked! I'm back on MIUI and will be going back to AwakenOS. btw so for now is there no other way of getting Dolby on AwakenOS?
Thank you for your time, you guys make this place better with all the help you share.
Click to expand...
Click to collapse
Sure, no problem! I don't know why it didn't work for you. For me it works perfectly fine. I even attached some pictures in the Awaken OS Thread. I can provide the Dolby Atmos of Motorola if you want which I've tried on some devices but not on this one so I cannot say that it will work. I'm not responsible for any bricks too.
I'm still waiting for unlock, but I would like to try if Viper Atmos will deliver the similar effect
Which is reverse engineering on Dolby Atmos I guess?