Related
Hello all!
This morning I updated Magisk Manager.
Once updated (or perhaps only downloaded update) the app prompted a reboot.
I rebooted and ended up in TWRP.
But I did not know what to do in TWRP so I rebooted system...
However, now the phone cannot boot and after one try it reboots into TWRP again.
PLEASE HELP ME!
I need my phone for work! Like now-now! :silly: :crying:
dustylambo said:
Hello all!
This morning I updated Magisk Manager.
Once updated (or perhaps only downloaded update) the app prompted a reboot.
I rebooted and ended up in TWRP.
But I did not know what to do in TWRP so I rebooted system...
However, now the phone cannot boot and after one try it reboots into TWRP again.
PLEASE HELP ME!
I need my phone for work! Like now-now! :silly: :crying:
Click to expand...
Click to collapse
How soon is now ? follow the white rabbit:good:
https://forum.xda-developers.com/zenfone2/help/help-bootloop-to-recovery-t3577504
timbernot said:
How soon is now ? follow the white rabbit:good:
https://forum.xda-developers.com/zenfone2/help/help-bootloop-to-recovery-t3577504
Click to expand...
Click to collapse
Well, that rabbit went into quite the hole... hehe
However, at the other end was a person who restored an old backup to revert this problem... And I -MAYBE- have an old backup on my external hdd, but won't that wipe all data that has been written to my phone since that "MAYBE" backup?
The other suggestion was wiping my MISC-partition using commands through ADB - something I have no clue how to setup and/or execute.
Still, thank you so much for your effort!
Reading all of this made me remember that one time I spaced out and tried to install an official firmware update upon release and prompt, which lead to the same issue. I could then just reinstall an older raw firmware version, which left all my files and data intact. Hopefully this will work here too.
BUT... It still feels very risky. If anyone out there has any sure-fire solution to this update Magisk Manager through the built-in updater no-boot issue, then please feel free to let me know - I would be forever in your debt
The best surefire solution is just don't. And BTW always backup before you flash anything in twrp.
Sent from my ASUS_Z00A using Tapatalk
---------- Post added at 08:49 AM ---------- Previous post was at 08:47 AM ----------
timbernot said:
How soon is now ? follow the white rabbit:good:
https://forum.xda-developers.com/zenfone2/help/help-bootloop-to-recovery-t3577504
Click to expand...
Click to collapse
I love what you did there! Lol
Sent from my ASUS_Z00A using Tapatalk
kenbo111 said:
The best surefire solution is just don't. And BTW always backup before you flash anything in twrp
Click to expand...
Click to collapse
I didn't flash anything in twrp. If you're gonna reply at least read the post. Also, none of what you wrote is a solution, unless you're in possession of a time machine. I'll keep it in mind for the next time though (of which there won't be one). Thanks, captain hindsight.
dustylambo said:
I didn't flash anything in twrp. If you're gonna reply at least read the post. Also, none of what you wrote is a solution, unless you're in possession of a time machine. I'll keep it in mind for the next time though (of which there won't be one). Thanks, captain hindsight.
Click to expand...
Click to collapse
That's what the update does. Reboots to twrp and installs the download. Maybe you should know what you're doing before you snap at us.
Sent from my ASUS_Z00A using Tapatalk
dustylambo said:
However, at the other end was a person who restored an old backup to revert this problem... And I -MAYBE- have an old backup on my external hdd, but won't that wipe all data that has been written to my phone since that "MAYBE" backup?
Click to expand...
Click to collapse
No, just restore the boot partition (16MB).
I learnt the hard way about backup, when years ago I didn't make one for my Galaxy S2 and lost everything (pictures, etc). Now after installing TWRP I always do a backup...
You should be able to reflash your boot partition with a fastboot command like "fastboot flash boot boot.img" (people with more knowledge than me can help you)
EDIT: the problem is that our Zenfone2 needs a signature for the boot partition, this is why we have a special Magisk installer that just add the signature to the image. The automatic update installer of Magisk has no clue about this, me and a few others here made the same mistake as you when Magisk popup "I have an update!" and we clicked "Install"...
All your data and app are still there, do not worry, no need to wipe anything, just reflash a signed boot.
kenbo111 said:
That's what the update does. Reboots to twrp and installs the download. Maybe you should know what you're doing before you snap at us.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Look... I am sorry if I "snapped" as you put it... But let's make one thing clear - I snapped at YOU; there is no "us" in this case, as you tried to skew it. Don't lump yourself together with these other helpful people, because so far you have nothing in common to me. If I were looking for someone to go "Hey, I got a solution - you know that thing you did? - Don't do it again!" I'd just go stand on the street corner with a sign asking for someone to slap my face.
As for your principal of don't do things if your not sure of how they work, I am totally behind that. But it has NOTHING to offer here as we are past that point. A broad comparison would be like "a solution to world hunger = eat food" ("but we don't have any food!" "you should have thought of that before you started starving now shouldn't you...?!").
In your defense, I guess you really believe you are trying to help. But compare your comment to the other ones posted and it is quickly clear that you are not. However, YOU ARE RIGHT, I should've known better and shouldn't do it again. And obviously I am enerved at this situation, but equally obvious (now) is that what you wrote is NOT "the best sure-fire solution" as what was posted afterward seems at least 100% (would have been more if possible) more applicable to my issue.
Anyway, I'll do the right thing here in the end, after having said so many things, and admit, once again, that I was wrong, you were right, I snapped for no good reason and you were just trying to help.
And I sincerely apologize for my rude behaviour. Hopefully now you can at least understand my reaction.
Also, fair is fair - Maybe TWRP flashes the update before it even enters into it. It would be the first I've EVER heard of something like that. But I am out of my element a bit here, so I will withdraw that comment and once again apologize for snapping at you because of it.
Magister54 said:
No, just restore the boot partition (16MB).
I learnt the hard way about backup, when years ago I didn't make one for my Galaxy S2 and lost everything (pictures, etc). Now after installing TWRP I always do a backup...
You should be able to reflash your boot partition with a fastboot command like "fastboot flash boot boot.img" (people with more knowledge than me can help you)
EDIT: the problem is that our Zenfone2 needs a signature for the boot partition, this is why we have a special Magisk installer that just add the signature to the image. The automatic update installer of Magisk has no clue about this, me and a few others here made the same mistake as you when Magisk popup "I have an update!" and we clicked "Install"...
All your data and app are still there, do not worry, no need to wipe anything, just reflash a signed boot.
Click to expand...
Click to collapse
NOW THIS IS HELPING!
THANK YOU SO MUCH!
Basically, you are saying that I would, in theory, just have to use fastboot and flash boot.img (extracted from any firmware?) again, which I am very familiar with how to do, and presto - boot partition restored and working (once again, in theory)?
Sounds amazing!:good:
dustylambo said:
NOW THIS IS HELPING!
THANK YOU SO MUCH!
Basically, you are saying that I would, in theory, just have to use fastboot and flash boot.img (extracted from any firmware?) again, which I am very familiar with how to do, and presto - boot partition restored and working (once again, in theory)?
Sounds amazing!:good:
Click to expand...
Click to collapse
Yes, if you have a Z00A for instance with MM version 223, take the Z00A.zip file from https://forum.xda-developers.com/zenfone2/general/bl-unlock-ze551ml-toolkit-t3546293 and use the file stock\z00a\223\boot.img
This is stock unsigned boot.img file for M .223
http://www.mediafire.com/file/rw73099svgbv0kv/boot.img
timbernot said:
boot.img file for M .223
http://www.mediafire.com/file/rw73099svgbv0kv/boot.img
Click to expand...
Click to collapse
Is there any way to check from TWRP or using fastboot, or otherwise find out what version of the rom I have (had)?
I am definitely still on LolliPo... I think I am one or two official updates from the switch to MarshMallow... But how can I be sure?
WW_ZE551ML_2.20.40.139_sal358-amtech.vn
Last year sometime I ran into a similar problem, where I had to flash raw firmware in order to unbrick the phone... This is the firmware that I downloaded and flashed then.
However, within this .raw-file there is no boot.img ...? There are a couple of .img-files, but none named boot.
On a side-note: When I bricked it last year and had to flash this raw firmware, which I did with Asus Flash Tool, if I am not mistaken... However, whichever way I did it, I managed to flash and then boot as usual. The phone then updated all apps, and I was just blessed with this wonderful sight of "my phone" with all the apps, files and data still intact.
And this problem, which resulted in the same boot issue, came from trying to apply an official OTA update, just after rooting and unlocking the bootloader (forgot myself for just a moment there), which to me seems like a way more serious screw-up than what I just managed to do today...?
@dustylambo
You still boot to TWRP ?
Simple questions
check date of back ups , course you won't be able to restore but title will have builds.
What twrp build ?
Then....
Select reboot in twrp then power off in twrp .
Wait 15 seconds...
Power plus vol+ , you can now boot to bootloader.
What IFWI version ?
0094.0177 or .0173 is LP
0094.0183 is M
Flash relevant raw , without ticking wipe data in AFT.
Check my unbrick thread in my signature for AFT and links to raws
Enjoy
timbernot said:
@dustylambo
You still boot to TWRP ?
Simple questions
check date of back ups , course you won't be able to restore but title will have builds.
What twrp build ?
Then....
Select reboot in twrp then power off in twrp .
Wait 15 seconds...
Power plus vol+ , you can now boot to bootloader.
What IFWI version ?
0094.0177 or .0173 is LP
0094.0183 is M
Flash relevant raw , without ticking wipe data in AFT.
Check my unbrick thread in my signature for AFT and links to raws
Enjoy
Click to expand...
Click to collapse
Yes, I still boot into TWRP.
I can't find my old backup for some reason, but after flashing the previously mentioned raw firmware I never up- or downgraded the ROM, so it MUST be that version. It's the only one I've ever downloaded and flashed.
IFWI version is 0094.0183
But so you are saying I could basically just flash [correct version FW].raw via AFT, without wiping data, and all should be good?
I am on your unbrick thread aws.
I will def bookmark it.
But I already have AFT and the same FW... so I could just go-go-go, right? Or is the IFWI version being M an issue?
Also, I downloaded the official Asus FW from their ZF2 website. In that .zip is in fact a "boot.img" - can I flash this via fastboot you think?
Thanks again for all your help!
You are unbelievable!
@dustylambo
0094.0183 is M
So flash a M raw.
You must've upgraded bootloader since flashing the last raw .139 which is LP to get to M bootloader .0183
In bootloader .0183
You flash raw for M, these have just been added by realyoti
drop him a thanks .
Flash without ticking wipe data in AFT
Damnit! I don't like where this is going... But it's late and I'm dumb
I never upgraded to M because I read that there were several apps that would lose support, MUSIC in particular, but there were others as well.
Will an M raw-file flash and still boot with all my old apps?
@dustylambo
It's simple really , what is the twrp build number ?
You never said
0094.0177
Is locked 5 LP bootloader.
.0173 is 5 unlocked bootloader
.0183 is M
What twrp build is yours ?
Ps , I don't think it matters which version raw you flash , only that it may fail and might have to wipe data to succeed which is better than what you have and are struggling with right now
gnite , enjoy
---------- Post added at 11:45 PM ---------- Previous post was at 11:30 PM ----------
Pls , remember the reason you installed twrp initially ?
For backing up
Sounds like you didn't only update Magisk Manager, you update Magisk itself. A non-signed Magisk update will always result in bootloop.
adobrakic said:
Sounds like you didn't only update Magisk Manager, you update Magisk itself. A non-signed Magisk update will always result in bootloop.
Click to expand...
Click to collapse
To be corrected: Not the Magisk, but the repacked boot.img. ?
Sent from my Redmi 3 using XDA Labs
Hello, I have this weird bug, after a reboot I always get this message. It seems to appear only when flashing magisk, had this issue on LineageOS, CRdroid and AICP.
Only fix is to reboot again until the message is gone.
Also I flashed magisk after phone setup.
Does anybody know a solution, it seems that this happened to more people across the ROM threads but no reports in the magisk tread.
Don't use Magisk 18.1 as of now. Flash Magisk 18.0.
bravonova said:
Don't use Magisk 18.1 as of now. Flash Magisk 18.0.
Click to expand...
Click to collapse
Tried Magisk 18.0 on LineageOS, still get the message.
I have a work around for it. Extract the boot.img file from your ROMs zip file. Transfer it to you phone. Then open magisk manager and tap install, and then install again. Then select the Patch Boot Image File option. Select the extracted boot.img file and let magisk do it's business. After it's done it will save the file as patch_boot.img. Next time you flash your ROM, or upgrade or simply get stuck, reboot into recovery. Then select install and then select image file. Select the patch_boot.img file and flash it as your boot Image. Reboot and everything should be fine.
It's a but annoying but that's what works for me 100% of the time.
dsahai said:
I have a work around for it. Extract the boot.img file from your ROMs zip file. Transfer it to you phone. Then open magisk manager and tap install, and then install again. Then select the Patch Boot Image File option. Select the extracted boot.img file and let magisk do it's business. After it's done it will save the file as patch_boot.img. Next time you flash your ROM, or upgrade or simply get stuck, reboot into recovery. Then select install and then select image file. Select the patch_boot.img file and flash it as your boot Image. Reboot and everything should be fine.
It's a but annoying but that's what works for me 100% of the time.
Click to expand...
Click to collapse
Thanks man, I will try it:laugh:
Does this mean I can flash the ROM, set it up and flash the patched boot.img and this bug should not reappear?
Mr. Cube said:
Thanks man, I will try it:laugh:
Does this mean I can flash the ROM, set it up and flash the patched boot.img and this bug should not reappear?
Click to expand...
Click to collapse
I guess
Whenever I get stuck in the "Phone is starting", I just reboot into recovery and flash the patch_boot.img and it seems to fix the issue The bug may reappear if you flash some Magisk modules, or update. So just keep that img file ready.
bravonova said:
Don't use Magisk 18.1 as of now. Flash Magisk 18.0.
Click to expand...
Click to collapse
I've flashed 18.0, then I updated through the Manger to 18.1 and working great!
TRY Magisk 18.2
https://forum.xda-developers.com/on...l-twrp-xposed-framework-t3910141#post79103367
DoR3M3 said:
I've flashed 18.0, then I updated through the Manger to 18.1 and working great!
Click to expand...
Click to collapse
I tried Magisk 18.0 but got the "phone is starting" bug four times in a row, than I gave up.
Strangely this also happens on OOS to me but there it disappears 10 seconds after boot
Mr. Cube said:
I tried Magisk 18.0 but got the "phone is starting" bug four times in a row, than I gave up.
Strangely this also happens on OOS to me but there it disappears 10 seconds after boot
Click to expand...
Click to collapse
I've been using 18.0 on OOS 5.1.7 and my ROM OOS[microG] which is OOS 5.1.7 and no problems ever...
I'd say install 17.1 then upgrade from there and see how it goes, and you can also try "Canary" Branch of Magisk and might have better luck with it...
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
If Magisk is a cause, it's not the only cause. I don't use Magisk but get the bug on both my OP3T and OP5 running crDroid. I've also seen it reported on Official LOS. Still looking for common factors, but it might be VPN related. Does anyone here use one? Could be a problem with 3rd Party Launchers. What is everyone using? The only logcat information we have to go on so far is:
Code:
03-13 14:44:37.070 1324 2483 W ActivityManager: Service.startForeground() not allowed due to bg restriction: service com.nordvpn.android/de.blinkt.openvpn.core.OpenVPNService
https://forum.xda-developers.com/showpost.php?p=79109320&postcount=492
There's the possibility that it's just a sporadic bug that could happen to anyone at any time. Could just be a gerenic way of saying "phone ran into something it didn't like during boot" I've only seen reports of this on Pie. Only had it myself on Pie.
The best thing we can do is to get a logcat when it happens. Providing you're in front of your PC, have USB Debugging enabled, and can connect to ADB while the phone is stuck on 'Phone Is Starting', running
adb logcat -d > logcat.txt. should work. (Correct the syntax if i've got that wrong)
I had this problem also on my 5T and got rid of it by using magisk uninstaller. I had this problem on MSM Extended AND crDroid, both the latest versions. I do not use any VPN-apps, but I do use a custom launcher, in my case thats Nova premium.
Are you trying to unlock your phone via fingerprint? For me, the behaviour is consistent: on boot, after entering SIM PIN, try to unlock phone with fingerprint, which leads to unclock code entry as this is the first boot and you need to enter your code. Enter code, and "Phone is starting". If, instead, after entering the SIM PIN, without touching the fingerprint sensor in any way, I manually swipe and enter the unlock code, the phone starts, no problem. Tested repeatedly.
If anyone has any idea where to report this bug, I'll gladly do so, but since apparently it isn't tied to Magisk, nor a specific ROM, I have no clue.
Dirk said:
If Magisk is a cause, it's not the only cause. I don't use Magisk but get the bug on both my OP3T and OP5 running crDroid. I've also seen it reported on Official LOS. Still looking for common factors, but it might be VPN related. Does anyone here use one? Could be a problem with 3rd Party Launchers. What is everyone using? The only logcat information we have to go on so far is:
https://forum.xda-developers.com/showpost.php?p=79109320&postcount=492
There's the possibility that it's just a sporadic bug that could happen to anyone at any time. Could just be a gerenic way of saying "phone ran into something it didn't like during boot" I've only seen reports of this on Pie. Only had it myself on Pie.
The best thing we can do is to get a logcat when it happens. Providing you're in front of your PC, have USB Debugging enabled, and can connect to ADB while the phone is stuck on 'Phone Is Starting', running
adb logcat -d > logcat.txt. should work. (Correct the syntax if i've got that wrong)
Click to expand...
Click to collapse
I'm not sure if it's magisk related but for me the only workaround to get it working again is the solution mentioned by @dsahai. When I flash the patched_boot.img it works again.
Also, I don't use any VPN service but a 3rd party launcher.
I will try to take a log on next reboot and report it to the LOS dev. :silly:
Mr. Cube said:
Also, I don't use any VPN service but a 3rd party launcher.
I will try to take a log on next reboot and report it to the LOS dev. :silly:
Click to expand...
Click to collapse
I use a 3rd party launcher too. The only reason i mention it is because the point where the 'phone is starting' message freezes the phone is at the point where the launcher loads. (or fails to load, which is more accurate to say). Of course everything else is trying to load at that point too so it might just be coincidence.
@Dirk
Someone has made a patch trying to fix the phone is starting bug
Just flash the fix-phone-is starting.zip in twrp and reboot
If it does not work, just flash the restore.zip
you can join op5/t official tg group to give your feedback
https://t.me/joinchat/GQS-ghNaf-1YMpjSbh_puQ
huluhola said:
@Dirk
Someone has made a patch trying to fix the phone is starting bug
Just flash the fix-phone-is starting.zip in twrp and reboot
If it does not work, just flash the restore.zip
you can join op5/t official tg group to give your feedback
https://t.me/joinchat/GQS-ghNaf-1YMpjSbh_puQ
Click to expand...
Click to collapse
That's interesting. Someone must think they've found the problem. What do we know about this?
On crDroid for the OP5 there's something in the latest build that's supposed to be a fix too. I assume it's the same changes. I haven't tried that new build yet so i'm happy to try the zip if it's okay to flash on the OP5?
Dirk said:
That's interesting. Someone must think they've found the problem. What do we know about this?
On crDroid for the OP5 there's something in the latest build that's supposed to be a fix too. I assume it's the same changes. I haven't tried that new build yet so i'm happy to try the zip if it's okay to flash on the OP5?
Click to expand...
Click to collapse
Just flash the fix.zip on ur op5
don't worry u can flash the restore.zip if it doesn't work
huluhola said:
Just flash the fix.zip on ur op5
don't worry u can flash the restore.zip if it doesn't work
Click to expand...
Click to collapse
Thanks.
It's infrequent for me. Perhaps once in a dozen or more reboots. Could be a while before i could say definitively that it's helped, but i'll try it and see. :good:
huluhola said:
@Dirk
Someone has made a patch trying to fix the phone is starting bug
Just flash the fix-phone-is starting.zip in twrp and reboot
If it does not work, just flash the restore.zip
you can join op5/t official tg group to give your feedback
https://t.me/joinchat/GQS-ghNaf-1YMpjSbh_puQ
Click to expand...
Click to collapse
I dont use Telegram. Can you keep us updated here with any news from this Patch? Has anybody reported anything yet?
Was checking system updates and found an update.
HermesHidayat said:
Was checking system updates and found an update.
Click to expand...
Click to collapse
Yup, was posted today on telegram group...
(WW)
FOTA (incremental update from 2004.60) ;
Rename to UL-ASUS_I001_1-ASUS-17.0240.2004.9-1.1.185-user.zip
https://fota2.asus.com/delta_packag...2004.60-17.0240.2004.9-06061254-fota-user.zip
Full rom zip ;
https://dlcdnets.asus.com/pub/ASUS/...S_I001_1-ASUS-17.0240.2004.9-1.1.185-user.zip
Raw rom ;
https://drive.google.com/file/d/1T0P8CDJLjPypRAS2HDpdUn8Z-M5tfzKc/view?usp=drivesdk
Stock boot img ;
stock2004.9
Root boot img ;
root2004.9
Place rom in root of storage and reboot. Once detected click to update. Reboot again to finish.
For those with root already and wishing to keep root, simply put the rom in root of storage, reboot and click to update when prompted. BUT, DON'T reboot yet when it finishes updating. Click 'later', go to magisk manager and choose 'install magisk'. When given the options for installing, select 'after OTA' (or words like that). Once magisk is installed again, select reboot. Root will be maintained. Saving the hassle of flashing the root img via fastboot.
-----------------------------------------
For those of you who are not yet rooted but would like to be using the boot img above, see below for guidance. NOTE: if something goes wrong, I am not responsible in any way!! Also, by unlocking bootloader (which is required for root), you will void your warranty.
Also note: you must update to latest 2004.9 rom from above links before starting this process. Should you wish to do this process another time with another update, you MUST ALWAYS match the root boot img for the same rom version you are using.
1. First you need to unlock the bootloader. Download and install the apk from link, then follow instructions. NOTE: doing this wipe the device. Do not power off the device or stop the process once started. I think the device will reboot a couple of times during the process, but ican't remember sorry... Just leave it to do its thing and once finished, proceed to step 2.
Get the bootloader unlock tool, which says in the description that it's compatible with android 10, from here. You'll find it under tools/utilities.
2. Download and install Minimal ADB and Fastboot app (windows). Install it on your PC/laptop to C drive
3. Download the root2004.9 boot img from above and move/save it to (C:\Program Files (x86)\Minimal ADB and Fastboot folder)
4. Switch the phone into fastboot mode (from device being in off/powered down, hold volume up then press and hold power button). Fastboot is the first screen you see with a scrollable menu giving some other options, don't select any options... just stay in that mode. Connect the phone to pc/laptop using the SIDE port of the phone. Navigate to C:\Program Files (x86)\Minimal ADB and Fastboot folder and double click the cmd-here.exe, this will open a cmd window.
5. (optional, but recommended) Once your phone is connected in fastboot mode and you have your cmd window open, type 'fastboot devices' in the cmd window. If your device is recognised then a key/serial will be displayed. Providing this is shown, proceed to step 6.
6. Next you are going to flash the root boot img (which, if you followed the instructions, should be in the Minimal ADB folder). In the cmd window type 'fastboot flash boot magisk_patched2004.9.img'. Once completed without errors, your device will now have a rooted boot img flashed. Yey!!
7. Now you can go ahead and unplug your device and boot it up. I did this months ago when I first got the phone, so you'll have to forgive me.... I can't remember if magisk manager is installed during the above process or if you have to install it manually after. If, when you have booted to system, there is no 'magisk manager' in your app drawer, you'll need to install yourself from here scroll about half way down the page and you'll see the downloads section. Go for the latest stable (currently 7.5.1).
8. Download a root checker app from playstore to verify you have root and you're done. If you need to resort back to original boot img, download it from above and follow the same process, but instead type 'fastboot flash boot boot2004.9.img'.
reg66 said:
Yup, was posted today on telegram group...
(WW)
FOTA (incremental update from 2004.60) ;
Rename to UL-ASUS_I001_1-ASUS-17.0240.2004.9-1.1.185-user.zip
https://fota2.asus.com/delta_packag...2004.60-17.0240.2004.9-06061254-fota-user.zip
Full rom zip ;
https://dlcdnets.asus.com/pub/ASUS/...S_I001_1-ASUS-17.0240.2004.9-1.1.185-user.zip
Stock boot img ;
stock2004.9
Root boot img ;
root2004.9
Place rom in root of storage and reboot. Once detected click to update. Reboot again to finish.
For those with root already and wishing to keep root, simply put the rom in root of storage, reboot and click to update when prompted. BUT, DON'T reboot yet when it finishes updating. Click 'later', go to magisk manager and choose 'install magisk'. When given the options for installing, select 'after OTA' (or words like that). Once magisk is installed again, select reboot. Root will be maintained. Saving the hassle of flashing the root img via fastboot.
Click to expand...
Click to collapse
bro,im not saying youre disturbing or whatsoever,you should make a detailed thread.unlike me im kinda dumb,i dont understand this Root boot img and so on. and making your own thread will allow more people will see your thread as i doubt many people will come to this thread to read...
Can anyone check to confirm whether heating is still on an issue on the new version?
HermesHidayat said:
bro,im not saying youre disturbing or whatsoever,you should make a detailed thread.unlike me im kinda dumb,i dont understand this Root boot img and so on. and making your own thread will allow more people will see your thread as i doubt many people will come to this thread to read...
Click to expand...
Click to collapse
Nah, should be fine here. People will still see the update in your title and click to view content. And for those that want root who are not already rooted I'll add some instructions in a while or tomorrow about how to use the boot img's (on my phone right now, it's easier if I do it on pc). Links and details are only the second post on the page so people will still see the info they need. So yeah, if it's OK with you I'll just leave the content here rather than starting another thread with the same title
---------- Post added at 03:36 AM ---------- Previous post was at 03:35 AM ----------
TikiThePug said:
Can anyone check to confirm whether heating is still on an issue on the new version?
Click to expand...
Click to collapse
I'd like to shed some light on this for you but I'm not a heavy gamer (I assume that's when the device gets hot mainly) and have never had any heating issues with any of the builds
TikiThePug said:
Can anyone check to confirm whether heating is still on an issue on the new version?
Click to expand...
Click to collapse
i dont play games anymore on my phone but the only time it hit 74 degrees was when i left my phone in my car under the sun...
reg66 said:
Nah, should be fine here. People will still see the update in your title and click to view content. And for those that want root who are not already rooted I'll add some instructions in a while or tomorrow about how to use the boot img's (on my phone right now, it's easier if I do it on pc). Links and details are only the second post on the page so people will still see the info they need. So yeah, if it's OK with you I'll just leave the content here rather than starting another thread with the same title
Click to expand...
Click to collapse
of course its fine.i was worried people wouldnt be able to see it.
Issue with Android 10 update on tencent with WW fingerprint
@reg66 tried moving post 2 ROM into root of storage .bit the update is still failing . New update is detected and after reboot, while it initialising install it's failing at the very start
Hi I have a CN Rog2 on ww1910.64-0 and fingerprint on ww. Using Asus updater I am getting 2001.60 .but post reboot while installing it errors out in the very beginning. Any guidance would be much appreciated !
VeeJay1 said:
Hi I have a CN Rog2 on ww1910.64-0 and fingerprint on ww. Using Asus updater I am getting 2001.60 .but post reboot while installing it errors out in the very beginning. Any guidance would be much appreciated !
Click to expand...
Click to collapse
Hmm, you should be able to update from latest A9 (1910.64) to A10. I'm guessing that the updater app only downloads the small incremental updates. These will fail unless you update 1 by 1, going up one version each time.
If you wanna jump straight to latest update (currently this one) download the FULL rom zip from post 2 of this thread. Put that in root of storage and reboot. Should hopefully not fail now and you'll be on latest.
Issue with Android 10 update on tencent with WW fingerprint
@reg66 tried moving post 2 ROM into root of storage, but the update is still failing . New update is detected and after reboot, while it's initialising install it's failing at the very start
Hi I have a CN Rog2 on ww1910.64-0 and fingerprint on ww. Using Asus updater I am getting 2001.60 .but post reboot while installing it errors out in the very beginning. Any guidance would be much appreciated !
Yes, moved to 2004.9
Did the incremental update and now my tencent rog2 on ww2004.9. thanks for the pointers.They really helped.
reg66 said:
I'd like to shed some light on this for you but I'm not a heavy gamer (I assume that's when the device gets hot mainly) and have never had any heating issues with any of the builds
Click to expand...
Click to collapse
Thanks man. Basically I had issues on A10 heating up even while just browsing the web. I would open up Armory Crate > Console and the CPU temp would be around 40+ Celsius. So now I'm back on A9, which shows temps of 30 Celsius with normal use.
well, video recording while connected to usb mic still doesn't work with the asus camera app
VeeJay1 said:
Did the incremental update and now my tencent rog2 on ww2004.9. thanks for the pointers.They really helped.
Click to expand...
Click to collapse
So the incremental worked direct from 1910.64 to latest? Or you had to go through each incremental?
---------- Post added at 07:12 PM ---------- Previous post was at 07:10 PM ----------
TikiThePug said:
Thanks man. Basically I had issues on A10 heating up even while just browsing the web. I would open up Armory Crate > Console and the CPU temp would be around 40+ Celsius. So now I'm back on A9, which shows temps of 30 Celsius with normal use.
Click to expand...
Click to collapse
Man that sucks. I've had zero heating issues even with leaving X mode on permanently @120Hz
Had to do this with each incremental update!
reg66 said:
So the incremental worked direct from 1910.64 to latest? Or you had to go through each incremental?
---------- Post added at 07:12 PM ---------- Previous post was at 07:10 PM ----------
Man that sucks. I've had zero heating issues even with leaving X mode on permanently @120Hz
Click to expand...
Click to collapse
TikiThePug said:
Thanks man. Basically I had issues on A10 heating up even while just browsing the web. I would open up Armory Crate > Console and the CPU temp would be around 40+ Celsius. So now I'm back on A9, which shows temps of 30 Celsius with normal use.
Click to expand...
Click to collapse
I've also suffered from battery and performance issues in A10. A9 was just fabulous, A10 was a step back.
I'm also a heavy gamer and just updated so I'll be sure to let you know what's going on.
P.S I did manage to improve performance and some battery life by installing the only real custom kernel we have, but which is a great one - kirisakura + Naptime with doze on Google play services.
VeeJay1 said:
Had to do this with each incremental update!
Click to expand...
Click to collapse
Ahh ok, bummer!! At least it's sorted now
Hi all, I have problem with the last update, always that's stop at 9% with message error update
dracoolia said:
Hi all, I have problem with the last update, always that's stop at 9% with message error update
Click to expand...
Click to collapse
I had the same problem with the incremental update. Just use the full ROM linked in the op.
Thanks for the Rooted Image.
Hi just chasing the raw rom if anyone has it please!
EDIT: It's too annoying to maintain and edit 6 separate threads. The installer works across all devices, so please visit this post for the latest version: https://forum.xda-developers.com/t/...or-patch-levels-2021-01-05-and-later.4226343/
Thanks!
NOTE: Download link in the OP will install mod for the current patch level down to January 2021. It will detect your current patch level and install the correct file. For earlier system builds from 2020 and prior, please use the official discontinued module on the Magisk Manager repo. I did not clone the entire Active Edge Mod repository; my unofficial repository only hosts January 2021 and later builds.
Changes:
I know, I know... I said I was done with releasing my Unofficial Active Edge Mod installer, yet here's another month's update. I might keep doing it for those that update immediately and want it a bit sooner, so long as it's fortunate enough to happen on a day when I'm able to do it relatively quickly. Since I'm building these anyway and sending them over to the dev, for now, to upload to the official Magisk repo, for now I don't mind also updating it here a bit sooner. Anyway, more on this below and some of the headache involved moving forward...
04-05-2021: Soooo... the script I wrote to churn these out as quickly as possible as Google releases the updates, relied on system image dumps on GitRip... unfortunately the domain was seized by the FBI (lol) and so it looks like the old dumper is no longer updating his Android dumps repo on GitRip. Fortunately, mikalovtch pointed me over to a new source that hosts such system dumps, and I was able to get these done relatively quickly afterwards. OP is updated with the 04-05-2021 installer now!
03-02-2021: Meant to post an update a week or two ago. Noticed the magisk module on the official Magisk repo now says [RE-CONTINUED], so there really isn't much need for me to continue updating this anymore! As a final gift, I ran my batch builder script and built the modded apk's for all variants for the 2021-03-05 patch level, and download link for the module installer is in the OP.
02-02-2021: February 2021 mod is now uploaded. Updated installer is in the link in the OP.
02-01-2021: Modified and uploaded modded SystemUIGoogle.apk files for 3 / 3 XL / 3a / 3a XL to GitHub repository. Updated Magisk installer slightly to accommodate this, and removed a few unnecessary lines. Won't make any difference if you already installed the first release.
Works! Thanks for keeping this alive!
(I'm on Jan. 2021)
newkydawg said:
Works! Thanks for keeping this alive!
(I'm on Jan. 2021)
Click to expand...
Click to collapse
Thanks for the feedback! Like I said, I don't own these devices so it's good to know that it's working properly.
Btw, fyi the current installer will install the correct mod for either patch level (Jan or Feb). I'll update one of the posts to reflect this. Like the old official installer, it will detect your current patch level and install the correct needed file. The major differences between this and the official mod installer (in terms of the installation process) is that I pulled out support for some of the devices (older Pixels and HTC), and it won't install for anything before 01-2021. I mean, I guess I could clone the official mod's files repo, which would also allow installs for older patch levels, but I didn't see the point seeing as how the official installer will still work fine for them as well as those other devices (afaik - don't think they've had system updates in a while).
Just tried your updated script for the March update but it keeps failing. I noticed on the Pixel 3 forum that there was a glitch that you addressed but I just tried again and it still fails. I've attached a screenshot.
newkydawg said:
Just tried your updated script for the March update but it keeps failing. I noticed on the Pixel 3 forum that there was a glitch that you addressed but I just tried again and it still fails. I've attached a screenshot.
Click to expand...
Click to collapse
Hmm, somehow the MD5 filename had the .apk stripped off before getting pushed to github, so the installer couldn't find the MD5 to compare with. Updated the github repo with the proper name; should flash now! No need to redownload, just try flashing again.
Yay! I have my squeeze for flashlight back! And just like you said "No need to redownload, just try flashing again." Thanks so much!
hello, I am getting a similar error as newkydawg with no remote md5.
I'm running the May security patch on pixel 2 xl.
raisins said:
hello, I am getting a similar error as newkydawg with no remote md5.
I'm running the May security patch on pixel 2 xl.
Click to expand...
Click to collapse
Unfortunately the last official security update for Pixel 2 XL was from December 2020. Also my unofficial mod only started supporting firmwares beginning in January 2021.
Either you're on an older (May 2020, not 2021) firmware than the latest, in which case just use the official module in the Magisk repo. Or if you're indeed on May 2021 security patch, I can only assume you're on a custom ROM which unfortunately isn't supported.
i5lee8bit said:
Unfortunately the last official security update for Pixel 2 XL was from December 2020. Also my unofficial mod only started supporting firmwares beginning in January 2021.
Either you're on an older (May 2020, not 2021) firmware than the latest, in which case just use the official module in the Magisk repo. Or if you're indeed on May 2021 security patch, I can only assume you're on a custom ROM which unfortunately isn't supported.
Click to expand...
Click to collapse
Oh yeah - i am on a Pixel Experience custom ROM. Dang I really liked the long squeeze.. oh well. Thanks for the info
Posting this here because I can't find a thread for the recontinued module. There hasn't been an update to that module for the June '21 firmware. Does that mean there were no changes to SystemUI and we can use the previous module?
CSX321 said:
Posting this here because I can't find a thread for the recontinued module. There hasn't been an update to that module for the June '21 firmware. Does that mean there were no changes to SystemUI and we can use the previous module?
Click to expand...
Click to collapse
There were changes to the SystemUI so I wouldn't use the previous module.
CSX321 said:
Posting this here because I can't find a thread for the recontinued module. There hasn't been an update to that module for the June '21 firmware. Does that mean there were no changes to SystemUI and we can use the previous module?
Click to expand...
Click to collapse
Looks like Mikhail hasn't updated the official repository yet. I'll shoot him a reminder. I sent the files a few days ago. He must be busy lately.
Meanwhile, here's another unofficial update (even though the official version will have identical modded files). Gonna only edit the Pixel 4 XL thread from now on. It's too much of a PITA to edit every single post for each variant. The installer is the same for all devices anyway. Here's a link to the thread, and download link will be there too: https://forum.xda-developers.com/t/...or-patch-levels-2021-01-05-and-later.4226343/
Thanks for updating!
August active edge update soft bricked my Pixel 3.
I can dirty flash OTA to get back but obviously root is gone and if I try to install magisk again the same thing happens. How can I remove the bad update without formatting the phone? The previous method only worked on android 10.
I do not recommend anyone flash the recent august update.
Rumsfield said:
August active edge update soft bricked my Pixel 3.
I can dirty flash OTA to get back but obviously root is gone and if I try to install magisk again the same thing happens. How can I remove the bad update without formatting the phone? The previous method only worked on android 10.
I do not recommend anyone flash the recent august update.
Click to expand...
Click to collapse
Yep, the same thing happened to me. I had to manually flash the stock boot image to both slots and reboot. Then use the long-press in power menu Restart option to reboot to safe mode, but as soon as it starts to reboot, hold the volume down button so that it goes to the bootloader. Then you can flash the Magisk patched image, and reboot, and when it reboots this time it will be rooted but still be in safe mode, so the bad Active Edge module will be disabled. It was a pain, but at least I got back to a working state without a factory reset.
Edit...I had to flash stock boot to both slots because I had corrupted the previously inactive one in my attempts to recover from this situation. If you haven't messed with the inactive slot, you shouldn't need to flash stock to it.
Soft bricked here too. Did exactly what @CSX321 did to get back to normal.
CSX321 said:
Yep, the same thing happened to me. I had to manually flash the stock boot image to both slots and reboot. Then use the long-press in power menu Restart option to reboot to safe mode, but as soon as it starts to reboot, hold the volume down button so that it goes to the bootloader. Then you can flash the Magisk patched image, and reboot, and when it reboots this time it will be rooted but still be in safe mode, so the bad Active Edge module will be disabled. It was a pain, but at least I got back to a working state without a factory reset.
Edit...I had to flash stock boot to both slots because I had corrupted the previously inactive one in my attempts to recover from this situation. If you haven't messed with the inactive slot, you shouldn't need to flash stock to it.
Click to expand...
Click to collapse
What is the process for flashing to a slot? Is this done with adb?
Rumsfield said:
What is the process for flashing to a slot? Is this done with adb?
Click to expand...
Click to collapse
fastboot flash boot_a boot.img
or the same with boot_b
You can use:
fastboot getvar current-slot
to find which slot to flash.
CSX321 said:
fastboot flash boot_a boot.img
or the same with boot_b
You can use:
fastboot getvar current-slot
to find which slot to flash.
Click to expand...
Click to collapse
Thanks I'll give it a shot.
Hi, recently I got this a32 from a friend because my phone is broken, but there's a problem. Some time ago she updated this phone from android 11 to 12 and the touchscreen completely stopped working, i got the phone yesterday hoping to fix this problem but i updated to android 13 (oneui 5.1) and it still doesnt work, i tried do downgrade to android 11 but its impossible and for last i tried to install twrp and then a gsi (following a guide here on the forum), i noticed that in twrp the touchscreen does actually work but after installing lineage os 20 it didn't again, is there any hope for this phone?
persifele said:
Hi, recently I got this a32 from a friend because my phone is broken, but there's a problem. Some time ago she updated this phone from android 11 to 12 and the touchscreen completely stopped working, i got the phone yesterday hoping to fix this problem but i updated to android 13 (oneui 5.1) and it still doesnt work, i tried do downgrade to android 11 but its impossible and for last i tried to install twrp and then a gsi (following a guide here on the forum), i noticed that in twrp the touchscreen does actually work but after installing lineage os 20 it didn't again, is there any hope for this phone?
Click to expand...
Click to collapse
Did you contacted the assistance? Seems a bad driver or kernel problem.
zSyntex said:
Did you contacted the assistance? Seems a bad driver or kernel problem.
Click to expand...
Click to collapse
no because i dont know how much it would cost and the phone isnt mine either so if possible i dont want to spend money
persifele said:
no because i dont know how much it would cost and the phone isnt mine either so if possible i dont want to spend money
Click to expand...
Click to collapse
We couldn't provide support for the hardware, mostly because you said that you've tried to reset the device and flash the stock ROM again.
If this doesn't fix the hardware issue, the assistance is the only way.
Probably a failure batch etc.
to be completely honest i flashed the stock rom by a backup i did before flashing lineage os, so if there's a guide on how to flash one ui 5.1 in order to have a clean installation it would be rlly helpful
persifele said:
to be completely honest i flashed the stock rom by a backup i did before flashing lineage os, so if there's a guide on how to flash one ui 5.1 in order to have a clean installation it would be rlly helpful
Click to expand...
Click to collapse
Simply download the latest firmware from SamLoader (Bifrost) and use Odin in order to flash it.
Tell me if you couldn't flash
I tried installing the latest firmware with odin, everything went fine but nothing, touch still doesn't work, i think tomorrow i'll take it to someone to fix it.
persifele said:
Hi, recently I got this a32 from a friend because my phone is broken, but there's a problem. Some time ago she updated this phone from android 11 to 12 and the touchscreen completely stopped working, i got the phone yesterday hoping to fix this problem but i updated to android 13 (oneui 5.1) and it still doesnt work, i tried do downgrade to android 11 but its impossible and for last i tried to install twrp and then a gsi (following a guide here on the forum), i noticed that in twrp the touchscreen does actually work but after installing lineage os 20 it didn't again, is there any hope for this phone?
Click to expand...
Click to collapse
what model of a32 is it? SM-A325F or??
One ui 5.1 firmware cannot be downgraded. I currently daily drive crdroid from nazim on one ui 5.1 firmware. my touch has never had issues. May be a hardware issue. Maybe a custom kernel would solve it. I built one for A325F that works on one ui 5.1 firmware. Give it a try from here. Its permissive btw. Just flash it in twrp. Although take a backup of boot before flashing incase something goes wrong
Captain_cookie_200 said:
what model of a32 is it? SM-A325F or??
One ui 5.1 firmware cannot be downgraded. I currently daily drive crdroid from nazim on one ui 5.1 firmware. my touch has never had issues. May be a hardware issue. Maybe a custom kernel would solve it. I built one for A325F that works on one ui 5.1 firmware. Give it a try from here. Its permissive btw. Just flash it in twrp. Although take a backup of boot before flashing incase something goes wrong
Click to expand...
Click to collapse
Hi, I tried to flash from twrp but it just gives me a series of "unable to unlock /dev/block/mmcblk0p14" and so on, btw yes its a A325F.
persifele said:
Hi, I tried to flash from twrp but it just gives me a series of "unable to unlock /dev/block/mmcblk0p14" and so on, btw yes its a A325F.
Click to expand...
Click to collapse
its fine. those are normal. if the flash suceeds at last that is all that matters
Captain_cookie_200 said:
its fine. those are normal. if the flash suceeds at last that is all that matters
Click to expand...
Click to collapse
The problem is that after flashing it goes in a bootloop where it says that "this phone's bootloader is unlocked, press power button" i do it and it starts the galaxy logo with above the writing "the software you are using isnt official, you may have problems with security and features" and it gets stuck there, rn i flashed the original firmware with odin and the phone is working but touch still isn't.
EDIT: i forgot to add that when i flashed with odin everything was going fine until the phone's screen went from green to red, i've never seen this so idk if i should be worried or not (phone is still running normally).
persifele said:
The problem is that after flashing it goes in a bootloop where it says that "this phone's bootloader is unlocked, press power button" i do it and it starts the galaxy logo with above the writing "the software you are using isnt official, you may have problems with security and features" and it gets stuck there, rn i flashed the original firmware with odin and the phone is working but touch still isn't.
EDIT: i forgot to add that when i flashed with odin everything was going fine until the phone's screen went from green to red, i've never seen this so idk if i should be worried or not (phone is still running normally).
Click to expand...
Click to collapse
oh weird . you are using one ui 5.1 right? whats the firmware name or version. Also those things def look like hardware issue. you should get it checked.
Captain_cookie_200 said:
oh weird . you are using one ui 5.1 right? whats the firmware name or version. Also those things def look like hardware issue. you should get it checked.
Click to expand...
Click to collapse
yes i'm on android 13 one ui 5.1, the firmware is A325FXXU3DWB8_A325FOXM3DWB8_ITV. I got it checked and they said that it cant be fixed because i cant downgrade from android 13 to another one, i could try installing crdroid like you and if you could send me a guide it would be amazing, thanks again.
persifele said:
yes i'm on android 13 one ui 5.1, the firmware is A325FXXU3DWB8_A325FOXM3DWB8_ITV. I got it checked and they said that it cant be fixed because i cant downgrade from android 13 to another one, i could try installing crdroid like you and if you could send me a guide it would be amazing, thanks again.
Click to expand...
Click to collapse
Just flash twrp for this thing from here. Follow steps on that thread to decrypt your storage and stuff. Then download crdroid gsi. Extract it. flash img file to system partition in twrp. Afterwards wipe dalvik, cache, internal storage
(internal storage is not necessary). You should be able to boot into twrp sucessfully.
I also have some workarounds and the stuff i use for my daily driving in this thread here.
If you need any further help i'll be here to assist.
Captain_cookie_200 said:
Just flash twrp for this thing from here. Follow steps on that thread to decrypt your storage and stuff. Then download crdroid gsi. Extract it. flash img file to system partition in twrp. Afterwards wipe dalvik, cache, internal storage
(internal storage is not necessary). You should be able to boot into twrp sucessfully.
I also have some workarounds and the stuff i use for my daily driving in this thread here.
If you need any further help i'll be here to assist.
Click to expand...
Click to collapse
Oh um i am sorry looks like thread doesnt contain instructions to that. I'll write em here myself
When you boot into twrp after flashing go to advanced and go to terminal
type
multidisabler
run it two times. Then go to format. Then press format data and type yes. Once its done reboot back into twrp again. Then flash crdroid as i said in my post above. and format the things i said. you should be able to boot into crdroid normally.
Captain_cookie_200 said:
Oh um i am sorry looks like thread doesnt contain instructions to that. I'll write em here myself
When you boot into twrp after flashing go to advanced and go to terminal
type
multidisabler
run it two times. Then go to format. Then press format data and type yes. Once its done reboot back into twrp again. Then flash crdroid as i said in my post above. and format the things i said. you should be able to boot into crdroid normally.
Click to expand...
Click to collapse
I followed everything you said, flashed crdroid but nothing, touch still doesnt work if not for when im twrp, i tried to flash kernel again and it still didn't so i don't know what to do anymore.
persifele said:
I followed everything you said, flashed crdroid but nothing, touch still doesnt work if not for when im twrp, i tried to flash kernel again and it still didn't so i don't know what to do anymore.
Click to expand...
Click to collapse
So uh looks like you have no options left. I just want to make sure. could you list the exact methods you used to flash the fw. Along with where u got the fw from? Lets see if the fw itself is broken or something.
Also this is very unrelated and time wasting. but you could try download one ui 5 firmware. Then extract super.img from ap. unsparse it and extract vendor.img and flash it to vendor partition using twrp. Then decrypt by typing
multidisabler twice in terminal as said in my previous post. Check if maybe an older version one ui 5 firmware has this issue fixed. one ui 5's kernel boots so one ui 5 vendor should work on 5.1 as well. It may not work but worth a try. you could also try doing this with android 12 firmware if that fixes it. if you do not have a linux machine availible i'll do it for you and upload the files for both firmwares here. Otherwise if its a hardware issue get your phone replaced or try getting the screen replaced. if still nothing happens ig switching to a new phone would be the only optiion.
So, to flash the firmware I used odin, the fw was from sammobile.
For trying to extract super.img and so on idk how to actually do it so if you could explain it would be really helpful. Btw trying to flash android 12 firmware is impossible because samsung made it so,
thank you again for the help.
persifele said:
So, to flash the firmware I used odin, the fw was from sammobile.
For trying to extract super.img and so on idk how to actually do it so if you could explain it would be really helpful. Btw trying to flash android 12 firmware is impossible because samsung made it so,
thank you again for the help.
Click to expand...
Click to collapse
i use samfw mostly for my firmwares. anyways. You need a linux machine nearby. ubuntu or arch. any distro based on them would work.
first you need to unsparse the super.img
for that we use
simg2img super.img super-raw.img
then we can use lpunpack or mount it to get our vendor.
we flash it using twrp and then we run multidisabler twice like we did when we first flashed gsi.
As you said above if you could do it for me it'd be awesome because i don't have a pc with linux rn.