Related
Hey all,
I noticed many people seem to be having problems with the new OTA update (174.44.1 US). I also tried to update and my Moto G went into a bootloop. After much tinkering, I found a possible solution.
As far as I can tell, the update problems are caused by:
- Xposed modules like Gravitybox (not really sure why)
- Hacks like the H/H+ hack that replaces SystemUI.apk
- Any other mod that changes something in /system
This is what I did:
(Note that I have 4.4 Stock, rooted and PhilZ CWM recovery. Xposed, Gravitybox, H/H+ hack and Logo hack)
- Downloaded the zip from http://forum.xda-developers.com/showthread.php?t=2653978
- Placed it in the SD of the phone
- Unchecked all modules in Xposed and rebooted
- Rebooted again, this time into PhilZ and installed the update zip from the SD
It showed me an error with SystemUI.apk (and I remembered changing it for the H,H+ hack). So I went and restored the original.
Then I tried again. It went smoothly. And I still have root
Now I'm just waiting to see if the new SystemUI.apk is different from the old one before I restore the hack.
NOTE: For those who can't remember any/all changes made to /system, the stock system.img should be flashed in fastboot mode.
Hope this is useful...
(FIRST THREAD!:laugh
[UPDATE]: I have included my stock SystemUI.apk and .odex. Copy into /system/priv-app, overwrite existing files and set permissions to rw-r--r--.
All Xposed tweaks can be undone by unselecting the modules in the Xposed framework and rebooting.....before rebooting again into recovery..
UPDATE: Added the version of Philz recovery I use, for those with the "this package is for falcon_umts devices : this is a xt1034" error.
Extract into your fastboot folder and issue command:
fastboot flash recovery PhilZ.img
That should set all that straight...
When you say stock system.img do you mean system.img_sparsechunk1 2 and 3? Would I just flash them with fastboot flash system system.img? Would it wipe anything other than mods made in the system folder?
draco259 said:
When you say stock system.img do you mean system.img_sparsechunk1 2 and 3? Would I just flash them with fastboot flash system system.img? Would it wipe anything other than mods made in the system folder?
Click to expand...
Click to collapse
It will return the system folder to default. All changes should be reset, as far as I can tell...
secretkloud said:
Hey all,
I noticed many people seem to be having problems with the new OTA update (174.44.1 US). I also tried to update and my Moto G went into a bootloop. After much tinkering, I found a possible solution.
As far as I can tell, the update problems are caused by:
- Xposed modules like Gravitybox (not really sure why)
- Hacks like the H/H+ hack that replaces SystemUI.apk
- Any other mod that changes something in /system
This is what I did:
(Note that I have 4.4 Stock, rooted and PhilZ CWM recovery. Xposed, Gravitybox, H/H+ hack and Logo hack)
- Downloaded the zip from http://forum.xda-developers.com/showthread.php?t=2653978
- Placed it in the SD of the phone
- Unchecked all modules in Xposed and rebooted
- Rebooted again, this time into PhilZ and installed the update zip from the SD
It showed me an error with SystemUI.apk (and I remembered changing it for the H,H+ hack). So I went and restored the original.
Then I tried again. It went smoothly. And I still have root
Now I'm just waiting to see if the new SystemUI.apk is different from the old one before I restore the hack.
NOTE: For those who can't remember any/all changes made to /system, the stock system.img should be flashed in fastboot mode.
Hope this is useful...
(FIRST THREAD!:laugh
Click to expand...
Click to collapse
Hi can you include your original systemui.apk i lost mines >.<
serophia said:
Hi can you include your original systemui.apk i lost mines >.<
Click to expand...
Click to collapse
Added to first post...
secretkloud said:
Added to first post...
Click to expand...
Click to collapse
i restored recovery, disabled all mods, unrooted, and did a factory reset when i try to install update i get an "error" in stock recovery? Any other suggestions i should do?
EDIT: nvm fixed by flashing system.img adaway was the problem for me >.<
Error when in recovery
I downloaded the zip but when I go to CWM recovery and try to install it from the SD it shows me an error.
it says; This package is for "falcon_umts" devices; this is a xt1032.
any help?
Maybe you'll find the solution to your problem here.
thanks!!
mokkami said:
Maybe you'll find the solution to your problem here.
Click to expand...
Click to collapse
thanks dude, now I just gotta know how to change the recovery haha
Thanks
Thanks :laugh:
This guide allowed me to apply the latest OTA update on Retail GB (uk version). At first I was on regular CWM (not phil's touch version).
My phone was identified as XT1034 and the OTA update is for XT1032, so I flashed phil's CWM for XT1032.
After that it said my phone was XT1032 and the update was intended for Falcon, so I flashed Phil's CWM for falcon.
After that applied the update from within Phil's CWM and all worked perfectly.
Note: I didn't modify system, all I modified was: Custom recovery, root and xposed framework (gravitybox etc.)
mdentener said:
Thanks :laugh:
This guide allowed me to apply the latest OTA update on Retail GB (uk version). At first I was on regular CWM (not phil's touch version).
My phone was identified as XT1034 and the OTA update is for XT1032, so I flashed phil's CWM for XT1032.
After that it said my phone was XT1032 and the update was intended for Falcon, so I flashed Phil's CWM for falcon.
After that applied the update from within Phil's CWM and all worked perfectly.
Note: I didn't modify system, all I modified was: Custom recovery, root and xposed framework (gravitybox etc.)
Click to expand...
Click to collapse
Why root??
OP says he kept root after update was applied??
Sent from my Nexus 7 using Tapatalk
mdentener said:
Thanks :laugh:
This guide allowed me to apply the latest OTA update on Retail GB (uk version). At first I was on regular CWM (not phil's touch version).
My phone was identified as XT1034 and the OTA update is for XT1032, so I flashed phil's CWM for XT1032.
After that it said my phone was XT1032 and the update was intended for Falcon, so I flashed Phil's CWM for falcon.
After that applied the update from within Phil's CWM and all worked perfectly.
Note: I didn't modify system, all I modified was: Custom recovery, root and xposed framework (gravitybox etc.)
Click to expand...
Click to collapse
Same thing for me!
Is this gonna be worked with the last update 176...
i have used ur system ui but i still get the error
serophia said:
i restored recovery, disabled all mods, unrooted, and did a factory reset when i try to install update i get an "error" in stock recovery? Any other suggestions i should do?
EDIT: nvm fixed by flashing system.img adaway was the problem for me >.<
Click to expand...
Click to collapse
Adaway modifies the "system/etc/hosts" file. It should also be disabled before updating.
irishpancake said:
QUOTE=mdentener;50672956]Thanks :laugh:
This guide allowed me to apply the latest OTA update on Retail GB (uk version). At first I was on regular CWM (not phil's touch version).
My phone was identified as XT1034 and the OTA update is for XT1032, so I flashed phil's CWM for XT1032.
After that it said my phone was XT1032 and the update was intended for Falcon, so I flashed Phil's CWM for falcon.
After that applied the update from within Phil's CWM and all worked perfectly.
Note: I didn't modify system, all I modified was: Custom recovery, root and xposed framework (gravitybox etc.)
Click to expand...
Click to collapse
Why root??
OP says he kept root after update was applied??
Sent from my Nexus 7 using Tapatalk[/QUOTE]
I kept my root also after the update. Those mods were installed before the OTA and remained installed after. I only disabled xposed modules temporarily and changed CWM to Phil's CWM to install the OTA.
Sent from my Moto G using Tapatalk
Hi all!
Is there any way to regain system R/W access on stock lollipop rom?
Or is there any "fixed" flashable prerooted ROM to download?
I was on rooted 4.4 LB and flashed this rom http://forum.xda-developers.com/z3/development/d6603-5-0-2-flashable-stock-23-1-0-690-t3056361 , ROOT is working fine without system R/W access so i cannot edit build.prop
Also, since recovery isnt working anymore it is quite difficult to revert to prevous 4.4 ROM.
"Turn off mount namespace, reboot, reinstall your choice of file explorer" doesent work for me, i use root explorer.
Any ideas?
mad_max911 said:
Hi all!
Is there any way to regain system R/W access on stock lollipop rom?
Or is there any "fixed" flashable prerooted ROM to download?
I was on rooted 4.4 LB and flashed this rom http://forum.xda-developers.com/z3/development/d6603-5-0-2-flashable-stock-23-1-0-690-t3056361 , ROOT is working fine without system R/W access so i cannot edit build.prop
Also, since recovery isnt working anymore it is quite difficult to revert to prevous 4.4 ROM.
Click to expand...
Click to collapse
You must have an unlocked bootloader
Justo go here: http://nut.xperia-files.com/
Click on XZDualRecovery Kernel and download the proper kernel for your device. On Flashtool (PC/Mac) flash a previous kernel with recovery (just google it). After, boot your devie in recovery (it will not boot on system because of the kernel) and flash the file you have downloaded first. You should have R/W system access, but no recovery (kernel and recovery are links).
You can roll back to KitKat with flashtool
DJPops said:
You must have an unlocked bootloader
Justo go here: http://nut.xperia-files.com/
Click on XZDualRecovery Kernel and download the proper kernel for your device. On Flashtool (PC/Mac) flash a previous kernel with recovery (just google it). After, boot your devie in recovery (it will not boot on system because of the kernel) and flash the file you have downloaded first. You should have R/W system access, but no recovery (kernel and recovery are links).
You can roll back to KitKat with flashtool
Click to expand...
Click to collapse
Yes, only problem is that my boot-loader is not unlock-able. Furthermore i would not unlock it anyway because of DRM and warranty.
So, i am waiting for solution on LB and lollipop. Kitkat has full RW access to system.
mad_max911 said:
Yes, only problem is that my boot-loader is not unlock-able. Furthermore i would not unlock it anyway because of DRM and warranty.
So, i am waiting for solution on LB and lollipop. Kitkat has full RW access to system.
Click to expand...
Click to collapse
So I'm sorry, IDK what to do with LB...
DJPops said:
You must have an unlocked bootloader
Justo go here: http://nut.xperia-files.com/
Click on XZDualRecovery Kernel and download the proper kernel for your device. On Flashtool (PC/Mac) flash a previous kernel with recovery (just google it). After, boot your devie in recovery (it will not boot on system because of the kernel) and flash the file you have downloaded first. You should have R/W system access, but no recovery (kernel and recovery are links).
You can roll back to KitKat with flashtool
Click to expand...
Click to collapse
Not true. I am on locked bootloader and have full system rw in lollipop.
Sent from my D6603 using XDA Free mobile app
ondrejvaroscak said:
Not true. I am on locked bootloader and have full system rw in lollipop.
Sent from my D6603 using XDA Free mobile app
Click to expand...
Click to collapse
I hope somebody figure this out...
Some are saying you need unlocked BL and for somebody you don't...
mad_max911 said:
I hope somebody figure this out...
Some are saying you need unlocked BL and for somebody you don't...
Click to expand...
Click to collapse
My experience is that usually people are running into problems when:
1. Not following instructions properly
2. Altering instructions
3. Not doing clean wipes or installs
Sent from my D6603 using XDA Free mobile app
I had the problem, that /system was shown as mounted r/w, but after a reboot all changes were gone. I had to lower the SELinux policy to permissive, after that all changes were permanent. However, you have to do that every time you reboot, so if some add-ons (like XPosed framework) need /system r/w at boot time, you have to alter the kernel package. Since I went back to 4.4.4, I can't help you with the latter one.
Forget that, just try this:
http://forum.xda-developers.com/z3-...-sgp621-lollipop-23-1-0-690-noba-ftf-t3058400
Have now done the following .
1. Cell unroot per SuperSU ( If only a short note, then the app closed )
2. boot into TWRP manually and flashed Magisk - v6
3. next phh 's systemless superuser ) with Super SU magisk version already tried )
4. Mobile launched new
5. After that, it will not boot - When loading only the LED that flashes red and I have to flash a new firmware ...
Anyone know what I'm doing wrong ?
Have a Sony Xperia Z3 D6603
gerooted and SuperSU ( 2.78 )
TWRP 3.0.2-0
Rom : PureX v5 ( Android 6.0.1 - 23.5.A.1.291 )
Locked Blootloader
would be great if he had a solution for me ...
smellz said:
Have now done the following .
1. Cell unroot per SuperSU ( If only a short note, then the app closed )
2. boot into TWRP manually and flashed Magisk - v6
3. next phh 's systemless superuser ) with Super SU magisk version already tried )
4. Mobile launched new
5. After that, it will not boot - When loading only the LED that flashes red and I have to flash a new firmware ...
Anyone know what I'm doing wrong ?
Have a Sony Xperia Z3 D6603
gerooted and SuperSU ( 2.78 )
TWRP 3.0.2-0
Rom : PureX v5 ( Android 6.0.1 - 23.5.A.1.291 )
Locked Blootloader
would be great if he had a solution for me ...
Click to expand...
Click to collapse
I had the same, but maybe the SU can't uninstall. I'm on existenz Rom...
Don't you need an unlocked bootloader?
Sent from my D6633 using Tapatalk
at magisk was nothing about it because that an unlocked bootloader is required.
Yes unlocked Bootloader is required. My Bootloader is unlocked. But can't delete the superuser.apk. That's bad
Exactly the same happened to me. I tried SLiMM 3.1 and PureX V5. After installing Magisk in TWRP device is like dead - only led flashes. If I used Elite kernel, system boots, but the system gets random restarts. Now flashing eXistenZ.
Maybe cause you need to be on stock rom and stock kernel
I use the stock kernel with custom Rom based on the latest official version
Got same issue when using stock kernel on my Xperia Z2, switched to Advanced stock kernel Marshmallow 6.0.1 'cause it has Systemless root support and SElinux permissive and now everything works.
I have try it again, with unroot and install Magisk. Now it works with the advanced stock kernel. But I have some reboots when root is enabled.
Hi All,
I have the same problem, I can see S1 /SOMC Flash Device in Device Manager.
Could someone please post step by step instructions to restore a to Marshmellow?
Will I have to download an Image and a Flashtool?
I have D6603 with TWRP, I am not able to boot to recovery.
Z3- said:
Hi All,
I have the same problem, I can see S1 /SOMC Flash Device in Device Manager.
Could someone please post step by step instructions to restore a to Marshmellow?
Will I have to download an Image and a Flashtool?
I have D6603 with TWRP, I am not able to boot to recovery.
Click to expand...
Click to collapse
Resolved using Emma. I installed the S1 SOMC Flash Device Drivers and I was able to download lollypop.
I will attempt now to reinstall recovery, new rom, and Magisk
Hello there,
I hope someone can help me. I got a Sony Xperia XZ today and I wanted to have it rooted of course. That I got to work pretty easily, but I now have the problem that in the Service Info almost everything is "Unknown". Also in the Developer options "OEM unlocking" is disabled (which I find weird) and when I want to enable it it jumps back to disabled. Not sure any of it will cause problems, but that's also why I posted this Thread.
Here's what I've done:
Downgraded from Oreo / 41.3.A.2.99 to Marshmallow 6.0.1 with Flashtool
Created a TA-Backup using Guide: TA Backup v2 | Universal (Dirtycow-based)
Downloaded and flashed to Oreo / 41.3.A.2.107 through Flashtool
Pulled fstab.qcom, init.qcom.rc and init.target.rc
Unlocked Bootloader through Flashtool
Created Kernel.elf from the downloaded Oreo Firmware through Flashtool Sin Editor
Created boot.img as it's decribed in [GUIDE][Oreo 8.0] Stock Kernel + ROOT + TWRP + DRM Fix | 41.3.A.2.99 with my TA.img
and flashed everything as described in the [Guide] above and in Rootkernel V5.23 (UNOFFICIAL 2.5) - OREO - Xperia X, X Comp., X Perf., XZ and XZs and with help of Install TWRP and Root Xperia XZ on Android 8.0 Oreo [DRM Fix] | ThemeFoxx:
Reflashed Oreo 41.3.A.2.107 through Flashtool with checked everything in "Sin"
Flashed my created boot.img through "fastboot flash boot boot.img"
Flashed TWRP through "fastboot flash recovery twrp-3.2.1-0-kagura.img"
Wiped data and formated userdata through TWRP, because TWRP was asking for decryption code
Skipped "Step 6" / flashing DRM-fix_System_Mode.zip through TWRP, because I used munjeni's TA PoC option (But tried it the 2nd time with the DRM-fix too)
Flashed Magisk Magisk-v14.5(1456) through TWRP (Edit: Also tried with v16.1 now)
Installed TWRP app as System App and rebooted normally
Now phone is rooted as I want it, but in *#*#7378423#*#* almost everything in Sercive Info is now "Unknown". When I click the menu "SIM Lock" the Service Menu App crashes, though I don't have inserted a SIM Card yet (but it worked before at the very beginning before I downgraded to Marshmallow)
I've done all this 3 times already, always the same result.
I've searched through this forum and googled for a solution, but I didn't find anything that matches my case/problem.
Screenshots added.
I flashed a Telecom branded 41.3.A.2.99 now with all the files in the Google Drive link from [GUIDE][Oreo 8.0] Stock Kernel + ROOT + TWRP + DRM Fix | 41.3.A.2.99 and now everything looks fine in the Service Menu.
I compared the files. fstab.qcom, init.qcom.rc and init.target.rc are binary indentical as well as kernel.elf. And when I creating the kernel with the files from the Google Drive link (and with DRM-fix instead of my TA.img) it creates a boot.img that is binary different to the one from the Google Drive link.
So every boot.img I have created causes my problem, so it looks like I create wrong boot.img files... I guess I'll post my problem in [ROOT][Kernel][TWRP] repack of the stock kernel with dm-verity and SONY RIC off
I'll leave this thread open for a few days in case anyone has any idea what I can do or until my problem got solved in the meantime.
Edit: I also tried to create a working boot.img with the files from Rooted Kernels F8331 & F8332 41.3.A.2.107 OREO 05APRIL2018, tried with and without my TA.img - both didn't work.
After many tried I'm now just using the KERNEL_F8331_41.3.A.2.107_CLEAN.img from that thread and followed the instructions. I'd like to use my TA.img backup so that under "FIDO KEYS" it doesn't says "not provisioned, provision failed" anymore.
PS: Did a post here now
I had to downgrade to Nougat, because of too many other problems occurred (which still haven't all been solved with Nougat. On Marshmallow they would all be solved, but I don't really want to stay on Marshmallow...)
So this Thread can be closed. If I can help solve that problem, I'll post it in [ROOT][Kernel][TWRP] repack of the stock kernel with dm-verity and SONY RIC off
Two useful things on coloros 6.01 A20
Must have unlocked bootloader. DO NOT RELOCK BOOTLOADER or you may end up with a bootloop.
I take no responsibility for your actions. You have agreed yourself to take these steps and fully responsible for your actions.
Lock screen fix
Magisk fix
Flash in this order in TWRP
1.Flash rom_ provided in the next post
2.fastboot_
3.vbmeta_
4.twrp_
5.magisk_
6.magisk fix_
7. fix locksreen
Proof in Screenshots
Previously Posted here. Posting in this section so everyone can access it!
https://forum.xda-developers.com/showpost.php?p=81263825&postcount=5
Update :
I have only 1 user confirming it works for him, while three users say it does not work for them. I am not sure if that due to difference in the region or something. I think I need to look it up more. It works for me so I am not sure what is different for others that it won't work.
Some others have said it worked after flashing this stock ROM via twrp and then following the above guide.
https://drive.google.com/file/d/16SxkonLfPmJ4qR7beQchvCrwyLXhPj5J/view?usp=sharing
In meanwhile, anyone who wants to experiment :
https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228
Bro its not working for me
1st i wiped system data dalvik and cache
2nd format data by typing yes
3 install stock rom
But its wont boot
So flashed boot.img
its working so i continued method
* Fastboot vbmeta
* Twrp magisk
*Twrp lock fix
But not worked
i am the one who vote works for GSI 9 .
Just to clarify, yes we can set pattern lock. But it won't stick. It revert back to swipe to unlock or none lock only.
bro i tried this just now
my software version is now A.23
and try this lockscreen fix zip but not worked
plz bro fix this issue
confirmed magisk works on A.20 version, but lockscreen DOES NOT works
any potential fix?
Update for A25 please
not working
not working Update for A25
boot.img
FathanRidhwan said:
confirmed magisk works on A.20 version, but lockscreen DOES NOT works
any potential fix?
Click to expand...
Click to collapse
bro can u give me the boot.img file for A20plss
Solution for Lockscreen and Fingerprint
I've made a mistake when flashing my phone with newer gsi, so i decided to go back to stock. I flashed the stock recovery with twrp. Then i installed the stock rom A20 using the stock recovery. After that i updated to Realme UI.
On the Realme UI i decided to lock my bootloader. Then i made up my mind to unlock my bootloader again. And the lockscreen and fingerprint works.
To install gsi i used this post's patched vendor, then u can install your desired custom gsi rom.
https://forum.xda-developers.com/realme-5/development/rom-lineageos-16-0-t4116675
Try at your own risk.
Sorry for my bad english. Hope this help you and please let me know if this work on your phone.
TL;DR : Re-unlock your bootloader. (You dont need the In-depth test if you already unlocked your bootloader before. And make sure ur on stock rom and recovery.)
Not working for me on ColorOS A.20 sadly. I already had TWRP, vbmeta and Magisk 20.4 installed and tried flashing the lockscreen fix but then it wouldn't boot and just kept booting into TWRP until I formatted Data.
After rebooting, I reinstalled Magisk 20.4, then the Magisk fix and then the lockscreen fix and it boots OK but I still can't enable the Lock Screen password/PIN.
The weird thing is I had the Lock Screen password working on A.20 before I had to send my phone off for repair. I can't remember whether I followed this method before though.
I saw another suggestion to flash the stock recovery, relock the bootloader and then unlock it again but that doesn't work for me either and when you lock the bootloader it wipes Data and I don't think there's any way to get back to fastboot to relock it without booting into the OS, going through the setup screens, enabling USB debugging and running "adb reboot bootloader" and then after unlocking again it wipes Data again so you have to go through the setup again before you can check whether it's worked or not.
EDIT: Doh! Just realised this is for Realme 5 and I have 5i