Develop Bugs

Moto z problems

Phone - Moto Z play XT1635-02-DS
Android- 7.1.2
Installed TWRP 3.1.1.0
Viper addison 7.1.2
Here are my problem:
1. Flashed with supersu v2.79 and also v2.82, neither works. Phone still not rooted. When i tried toa access supersu app, it says "there is no su binary installed and supersu can't install it..."
2. Camera does open but it doesn't function, it stays dark. (I have custom gapps 7.1.x)
3. Proximity sensor does not seem to be working in other cases, but the phone goes dark as soon as i press dial or as soon as i pick a call and remains so untill the other party cuts the call. Otherwise i need to shut down the phone if i have to end the call from my phone.
4. When i shut down the phone, in order to reboot manually from recovery-reboot-bootloader. Otherwise it remains in twrp recovery.
Can anyone help please?

Have you tried flashing back to stock and seeing if that fixed these issues?

Pal Guite said:
Phone - Moto Z play XT1635-02-DS
Android- 7.1.2
Installed TWRP 3.1.1.0
Viper addison 7.1.2
Here are my problem:
1. Flashed with supersu v2.79 and also v2.82, neither works. Phone still not rooted. When i tried toa access supersu app, it says "there is no su binary installed and supersu can't install it..."
2. Camera does open but it doesn't function, it stays dark. (I have custom gapps 7.1.x)
3. Proximity sensor does not seem to be working in other cases, but the phone goes dark as soon as i press dial or as soon as i pick a call and remains so untill the other party cuts the call. Otherwise i need to shut down the phone if i have to end the call from my phone.
4. When i shut down the phone, in order to reboot manually from recovery-reboot-bootloader. Otherwise it remains in twrp recovery.
Can anyone help please?
Click to expand...
Click to collapse
This is not really a problem with the phone per se but the rom you chose to flash. The reboot issue can be checked by setting a command at bootloader using "fastboot oem fb_mode_clear".

gman88667733 said:
Have you tried flashing back to stock and seeing if that fixed these issues?
Click to expand...
Click to collapse
Thanks. But i don't have the stock rom. I didn't intend to use a custom rom. I tried to root it to recover some deleted photos and the moron that i am, i didn't back up the stock firmwares and while tweaking around in the recovery i somehow deleted the stock rom. This is my 1st time...

DroneDoom said:
This is not really a problem with the phone per se but the rom you chose to flash. The reboot issue can be checked by setting a command at bootloader using "fastboot oem fb_mode_clear".
Click to expand...
Click to collapse
Thanks... I tried the above command (it does recognize my device) bur this is what i get :
{bootloader} slot-count: not found
{bootloader} slot-suffixes: not found.

Pal Guite said:
Thanks... I tried the above command (it does recognize my device) bur this is what i get :
{bootloader} slot-count: not found
{bootloader} slot-suffixes: not found.
Click to expand...
Click to collapse
Is there an option for the bootloader in developer settings in your rom similar to the screenshot I attached? Make sure it's enabled.

DroneDoom said:
Is there an option for the bootloader in developer settings in your rom similar to the screenshot I attached? Make sure it's enabled.
Click to expand...
Click to collapse
Thanks for your concern. Developer option is 'on' and Multiprocess webView renderers seperately - 'on'. But i get the same problem. (and how do you attach screenshots ? I don't see any option for attaching files) In anycase, like you said, i think the problem has more to do with the rom. Can you please suggest me another rom or if possible link from where i can download stock rom for my phone.

Pal Guite said:
Thanks for your concern. Developer option is 'on' and Multiprocess webView renderers seperately - 'on'. But i get the same problem. (and how do you attach screenshots ? I don't see any option for attaching files) In anycase, like you said, i think the problem has more to do with the rom. Can you please suggest me another rom or if possible link from where i can download stock rom for my phone.
Click to expand...
Click to collapse
If your on xda with your browser, it's the paperclip icon to attach files. If you are using a 3rd party app that wraps xda into it then I can't help you there. As for going back to stock, Motorola made things a little critical when they released Nougat. Depending on how far you were on keeping the device up to date through stock, flashing the available stock images (which aren't signed) could brick the device if you aren't careful. There use to be an account on androidfilehost that uploaded current stock packages but it seems they're all gone now. If you remember the build number of the device before you rooted, that will help in picking the right stock files. I've taken a break in keeping my device rooted so I haven't kept track of the resources used to help go back to stock but they're in the MZP guide threads.
EDIT: a word of caution when reverting to stock:
-Don't use flash tools that don't let you see/edit the fastboot commands
-Do not use commands that touch modem/radio or gpt partitions
Found an upload of the latest build release keep it around when you figure out what you need to flash. It's best to clear system, data, and cache before flashing. Also have a rom (and twrp) at hand to adb sideload in case stock doesn't boot.
https://androidfilehost.com/?a=show&w=files&flid=215703
This Android version 7.1.1
Security patch: Sept 2017
Build number: NPN26.118-22-2

Thanks alot... ?

HELP!!!! no wifi after going from slim remix to omni rom then back to stock

so today i was testing the roms availble outside of oxygen os (forgot to make a back-up of oxygen was on the oreo beta wich seems to have been pulled now )when i flashed liquid remix and saw everything worked well, so i went back to twrp to adb sideload the open beta build i ha saved from when it was released, adb sideload fails cant read the zip figured oh ill redownload it, see that oneplus has deleted the download link son i decided to test crdroid and that worked as well as the other so i flashed omni and loved it except that it couldnt get wifi working so i downloaded the stock zip for 4.74 adb sideload from the stock recovery and boot up, still not able to connect to wifi it allows me to enter the password and it starts connecting then fails for no reason after 3 tries to connect the ssid shows that it is disabled

Learn a bit before flashing

Do you still have a MAC address for the WIFI on your phone?

Flash stock including radios from the factory image via fastboot

i dont have the ip address on that phone but i can get it off my friends. where would i find the fastboot images for the oneplus 5T?

I had/have the same problem with my 5T. I flashed the Oreo beta and now I can't use any of the Nougat versions of Oxygen. I flashed the Oreo back on and the WiFi works fine.

RLD831 said:
I had/have the same problem with my 5T. I flashed the Oreo beta and now I can't use any of the Nougat versions of Oxygen. I flashed the Oreo back on and the WiFi works fine.
Click to expand...
Click to collapse
i cant find a version of the oreo beta that boots through could you link me to it

No problem. Let me upload it to my Google Drive and I'll post a link.

thanks ill report back

ummm its right in front of u... if it was a snake it would have bit u
https://forum.xda-developers.com/oneplus-5t/how-to/soon-oxygenos-beta-1-android-o-oneplus-t3726074

Bradl79 said:
ummm its right in front of u... if it was a snake it would have bit u
https://forum.xda-developers.com/oneplus-5t/how-to/soon-oxygenos-beta-1-android-o-oneplus-t3726074
Click to expand...
Click to collapse
already tried that build adb sideload cant read it and the stock oneplus recovery cant seem to see my internal storage whereas twrp can twrp flash fails

kanaan360 said:
already tried that build adb sideload cant read it and the stock oneplus recovery cant seem to see my internal storage whereas twrp can twrp flash fails
Click to expand...
Click to collapse
that is a full zip whether its stock or twrp... what error does it give u in twrp
or r u having an error flashing TWRP recovery via fastboot?

it doesnt give an error in twrp it just fails to boot after the flash also i know that it doesnt matter sice its a full zip im getting more at adb fails on both

kanaan360 said:
it doesnt give an error in twrp it just fails to boot after the flash also i know that it doesnt matter sice its a full zip im getting more at adb fails on both
Click to expand...
Click to collapse
sorry to hear the issues u are having, but this device is a Pain the Ass to try different things and flashing different things, unlike older devices which u could flash anything and everything back and fourth. I am not even going to try Open Betas on this device, I may even stay away from Oero and custom roms for awhile until we can find an unbricking tool
have u tried to the rollback and/or nougat full zip

Bradl79 said:
sorry to hear the issues u are having, but this device is a Pain the Ass to try different things and flashing different things, unlike older devices which u could flash anything and everything back and fourth. I am not even going to try Open Betas on this device, I may even stay away from Oero and custom roms for awhile until we can find an unbricking tool
have u tried to the rollback and/or nougat full zip
Click to expand...
Click to collapse
yea i think ill just fix my onplus 3 screen because damn only had one issue with that and it was an easy fix. ive gone back to 4.7.4 and im about to try the rollback

kanaan360 said:
yea i think ill just fix my onplus 3 screen because damn only had one issue with that and it was an easy fix. ive gone back to 4.7.4 and im about to try the rollback
Click to expand...
Click to collapse
good luck man... let me know how it goes

no luck, btw the roll back build puts you on 4.7.5

kanaan360 said:
so today i was testing the roms availble outside of oxygen os (forgot to make a back-up of oxygen was on the oreo beta wich seems to have been pulled now )when i flashed liquid remix and saw everything worked well, so i went back to twrp to adb sideload the open beta build i ha saved from when it was released, adb sideload fails cant read the zip figured oh ill redownload it, see that oneplus has deleted the download link son i decided to test crdroid and that worked as well as the other so i flashed omni and loved it except that it couldnt get wifi working so i downloaded the stock zip for 4.74 adb sideload from the stock recovery and boot up, still not able to connect to wifi it allows me to enter the password and it starts connecting then fails for no reason after 3 tries to connect the ssid shows that it is disabled
Click to expand...
Click to collapse
have you tried to remove the wifi Networks from the Network list and reconnect it? i had a similar issue where it showed my wifi Networks as saved by Default as it was synched trough Google. and i had to remove and reconnect in order to get it working.

nadejo said:
have you tried to remove the wifi Networks from the Network list and reconnect it? i had a similar issue where it showed my wifi Networks as saved by Default as it was synched trough Google. and i had to remove and reconnect in order to get it working.
Click to expand...
Click to collapse
yes i even have this issue without gapps

I had similar issue yesterday after flashing the liquid ROM - when i try to connect to Wifi it says "Disabled" after many struggle i flashed the OOS Open Beta 1 now it works fine.

[UNOFFICIAL][ROM] LineageOS 14.1 for Galaxy Tab E [SM-T561/SM-T560]

Code:
[B][U]Disclaimer:[/U][/B]
I am not responsible for any damage to you your device. Everything you do, you do on your own risk!
Last year I got a Galaxy Tab E (SM-T560) from Samsung for free as gift to my new mobile phone.
Unfortunately the ROMs for SM-T560NU tabs are not working on that device, but I found a working ROM of LineageOS 14.1 (Android Nougat 7.1.2) on the following page:
How to install Android Nougat on the Galaxy Tab E (SM-T561)
Click to expand...
Click to collapse
Original source (Russian language)
Click to expand...
Click to collapse
LineageOS 14.1 (formerly known as CyanogenMod) ROM is based on the Android stock ROM released by Google, which the LineageOS team modifies.
Credits go to the LineageOS team for making this ROM available to many devices and to independent developers like Ma3a_XaTa for porting this ROM to the Tab E SM-T561.
Click to expand...
Click to collapse
Just installed it to my tab and it seems working well!
I used the instructions from a comment at the bottom of the page:
Downloads:
ROM: LineageOS 14.1
Gapps: The Open GApps Project
Boot Image: boot.img
SoftKeyFix: KeyFix
Recovery: TWRP Recovery for Tab E
Root: SuperSU
Click to expand...
Click to collapse
Prerequisites:
1. Make sure you have TWRP 3 installed (HowTo)
2. Move the downloaded files to your Micro SD Card (>4GB recommended)
3. >50% battery charge
4. Some patience.
Click to expand...
Click to collapse
Installation:
1. Boot to TWRP 3 (Power + Home + Volume Up) and Swipe to allow modifications
Note: Make sure to Backup EFS and Modem to Micro SD Card in TWRP.
2. Wipe > Advanced Wipe > (Select Dalvik Cache, System, Data, Internal Storage, Cache ONLY) > Swipe to WIPE
3. Install > Select Storage > Micro SD Card > Select lineage-14.1-20180419-UNOFFICIAL-gtel3g.zip
4. Add More Zips > open_gapps-arm-7.1-pico-2018xxxx.zip
5. Add More Zips > keys.zip
6. Swipe to confirm flash and wait for 5-10 mins
7. After the Flash process DO NOT restart system.
8. Go back to Install > Install Image > boot.img > Select Boot Partition > Swipe to confirm flash
9. After the boot.img has been flashed DO NOT restart system IF you want Root.
10. Go back to Install > Install Zip > SR3-SuperSU-v2.82-SR3-20170813133244.zip > Swipe to confirm flash
11. Now Restart System.
12. Wait 10-15 mins, it will take some time.
13. Enjoy Lineage OS!
Click to expand...
Click to collapse
Known bugs:
- Charging while the device is off works, but does not show battery charge indicator animation.
Click to expand...
Click to collapse
Good luck and enjoy!
Code:
[B][U]Miscellaneous:[/U][/B]
[URL="https://www.hardreset.info/devices/samsung/samsung-t560-galaxy-tab-e-96-wifi/download-mode/"]HowTo bring the Tab to DownloadMode[/URL]

Hints & Tips:
1. To improve the speed of the tablet, turn of animations inside Developer Options.
2. You can also install an app freezer called "Icebox" to temporarily disable RAM hungry apps like Facebook, Chrome etc.
3. To ensure longer battery life, disable “double tap to wake” hidden somewhere in the settings (use the app called "Kernel Adiutor" from the Playstore).
4. If you don’t plan to put a SIM on this thing or if you are having a SM-T560 only, put it in airplane mode and then turn on your WiFI when needed. Turn of GPS/location or even sync when not necessary.
5. Disable "Adaptive Display" in the settings. It seems to make the tablet slower.
6. Improve the battery life of the tab by using an app called “L Speed“ (available in Playstore).

Hello, great post. I used this ROM before, but after some time it just stops working. You can't boot it anymore.
How long do you use it already?

mimuta said:
Hello, great post. I used this ROM before, but after some time it just stops working. You can't boot it anymore.
How long do you use it already?
Click to expand...
Click to collapse
I'm using it now for approx. 3 weekswithout any problems. How long did you use it?
BR, See

SeeDoubleYous said:
I'm using it now for approx. 3 weekswithout any problems. How long did you use it?
BR, See
Click to expand...
Click to collapse
I was wondering what version are you running? Everytime j download one it fails to flash through TWRP? You got a link to a download ??

V3rdeV1ntage said:
I was wondering what version are you running? Everytime j download one it fails to flash through TWRP? You got a link to a download ??
Click to expand...
Click to collapse
What version of TWRP are you using & what error do you get?

Have someone passed safetynet check ? Can you help me with pass?

The ROM is running ok so far on my T560, but I noticed some problems:
* If the tablet runs out of battery with Wifi activated, charging and booting it up causes a boot loop until Wifi is turned off. Something like that... it sometimes gives you the time to open the settings and turn off Wifi before it reboots.
* The Tablet's battery is drained by "Mobile Standby" in approx. two days, regardless of power save, battery saver and/or flight mode. When the Tab is idle all the time, the battery graph runs down in a straight diagonal line until the battery is empty, approx. 2 % per hour. Did not find a way to disable Mobile Standby on my T560 which doesn't even have a modem (maybe that's the problem).
* The system is a bit laggy given that it's a quad core, but turning off Animations helped. I suspect hardware acceleration does not work.
I'd switch to a better rom if I find one. But thanks anyways for the information and work! Better than nothing, I guess

Problems of ignition and charge of battery
Hello friends, I need a help I have a Samsung Tab E 9.6 = SM.T561, I installed Roon Custom Lineage 14.1 with TWRP, but the Tablet was downloaded and I can not charge it or turn it on, I searched everywhere and nobody gives me answers . I appreciate the help given. Thank you

Hi, I hope someone who has tried this rom can give me some feedback on it. My main concern its if this is stable and faster than ron. Any idea?

s5minimalist said:
The ROM is running ok so far on my T560, but I noticed some problems:
* If the tablet runs out of battery with Wifi activated, charging and booting it up causes a boot loop until Wifi is turned off. Something like that... it sometimes gives you the time to open the settings and turn off Wifi before it reboots.
* The Tablet's battery is drained by "Mobile Standby" in approx. two days, regardless of power save, battery saver and/or flight mode. When the Tab is idle all the time, the battery graph runs down in a straight diagonal line until the battery is empty, approx. 2 % per hour. Did not find a way to disable Mobile Standby on my T560 which doesn't even have a modem (maybe that's the problem).
* The system is a bit laggy given that it's a quad core, but turning off Animations helped. I suspect hardware acceleration does not work.
I'd switch to a better rom if I find one. But thanks anyways for the information and work! Better than nothing, I guess
Click to expand...
Click to collapse
I have my T560 all the time in airplane mode with Wifi on. Battery drain is no problem at all.
It is also written in my second post:
HTML:
https://forum.xda-developers.com/showpost.php?p=78977223&postcount=2
aribetty said:
Hello friends, I need a help I have a Samsung Tab E 9.6 = SM.T561, I installed Roon Custom Lineage 14.1 with TWRP, but the Tablet was downloaded and I can not charge it or turn it on, I searched everywhere and nobody gives me answers . I appreciate the help given. Thank you
Click to expand...
Click to collapse
I had a similar problem in the beginning. Seemed as the tab was in a bootlooporsomething similar with black screen.
The only solution I found was to wait some days until the battery was empty, charge the tab and directly started to download/recovery mode and flash it again.
Now it is working fine with this ROM.
Rittachi said:
Hi, I hope someone who has tried this rom can give me some feedback on it. My main concern its if this is stable and faster than ron. Any idea?
Click to expand...
Click to collapse
I am using it now for ~2.5 months and I am quite happy with it.
It is much better then the stock ROM.

Hi @SeeDoubleYous and guys. I was reading the Forum and decided to share with you my experience with this ROM. Well, I'm owner of a SM-T560 (in US and Canada this model is T560NU I don't know why it's different just in these two countries ). Anyway....
I made all the steps described on the step-by-step Instructions. (TWRP Recovery via ODIN, Root, ROM, GAPPS, etc etc etc).
I'll be honest with you. My t560 turned in a piece of sh... Very Slow, Apps Stucking all the time, sometimes bootlooping too... i used the Tab for almost 3 weeks. After that I decided to reset the device and I did all steps again using the same ROM (I reinstalled the TWRP RECOV via ODIN, proceeded a Factory + Internal Memory Wipe, Installed the LINEAGE 14.1 OS, etc, etc, etc) But this time I choose the "Micro" GAPPS option instead "PICO". Installed Root SU, etc, etc exactly as the directions wrote in the top page.
For my surprise, It's perfect Now!!!! ROM is great.... No problems of RAM, Bootlooping, Stucking, APP crashing... Absolutelly Nothing!
I don't know why, but it seems that the secret is install for first time and use for some weeks even its is not working fine. And After that, proceed All the step-by-step again from the very beggining. (Reinstall TWRP, ROM, GAPPS, Keys, "Boot Image" and ROOT SU). It will work fine on SM-T560 just from the second Install on.....
All Best guys

I need help. My screen is stuck on boot again
Am I bricked?

Hi guys, I've got a T560 tablet with the official ROM and I'm researching to upgrade it's software.
Currently I'm away off-shore for work but as soon as I get home I'll try this ROM.
I've been a fan of CyanogenMod since the early days and I'm eager to try it so I can bring some new life into my old tablet.
Since this ROM is for the SIM card variant T561 I was searching for a way to disable the Radio altogether and I found this:
https://android.stackexchange.com/q...le-radio-signal-in-a-phone-without-a-sim-card
Basically it disables the RIL with a simple Terminal Command:
Code:
su -c "setprop persist.radio.noril 1"
Can someone try this and see if its working properly? (OFC after a Back-up is done) Its persistent through reboots so you don't need to use Airplane Mode anymore and maybe it will help with the battery draining problem.
Also one question for the guys who are currently using this ROM:
Is Magisk working? After everything is set-up can we uninstall SuperSU and install Magisk for root?
Thank you,
Have a nice day!

SpawNyK said:
Code:
su -c "setprop persist.radio.noril 1"
Click to expand...
Click to collapse
I've tried the command and it worked, no reboots even if the airplane mode is off and no problem so far.
I don't know if the battery life is better now because I've just done it.
For the other question, I haven't tried because I like SuperSu, but I think there's no problem.

gucio1976 said:
And what do you think about it.
https://mega.nz/#!49QXRIAb!7FtqWknBNzIe5-Ak-Jgmq7N71JB4TcGEi-MjuQCuvhw
Click to expand...
Click to collapse
Can you please provide a guide for flashing this?
Like which GApps version should I use, etc...

I get in red, does something affect ROM? e: unknown command [log]

Hey,
does this rom works with SM-T562??? (3G)

Is there any updated ROMs like LOS 15 or 16 for SM-T561 (gtel3g), I tried to Port LOS 16 but I get error 7 while flashing in TWRP(V3).

gucio1976 said:
And what do you think about it.
https://mega.nz/#!49QXRIAb!7FtqWknBNzIe5-Ak-Jgmq7N71JB4TcGEi-MjuQCuvhw
Click to expand...
Click to collapse
gucio1976 said:
I found it here .
https://www.youtube.com/watch?v=-4h_3qDRiv8
Click to expand...
Click to collapse
Why should you use the old version, if this thread offers a newer one?
gucio1976 said:
---------- Post added at 11:33 ---------- Previous post was at 11:13 ----------
Something else. Maybe it will be useful to someone.
https://www.youtube.com/watch?v=7JpUomQs2ok
Click to expand...
Click to collapse
I think that's the same version as offered here...
shreejalm said:
Is there any updated ROMs like LOS 15 or 16 for SM-T561 (gtel3g), I tried to Port LOS 16 but I get error 7 while flashing in TWRP(V3).
Click to expand...
Click to collapse
I did not find any new version. The ones available are only working with the SM-T560NU....
Sorry!

"Phone is starting" Magisk bug on most custom ROMs

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?

Question Touchscreen not working

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.