Develop Bugs

HELP! I rooted my phone and not touchwiz is gone

Hello,
Last night I rooted my device using this (http://forum.xda-developers.com/showthread.php?t=1265429) method and file from zedomax and everything worked great except when I booted my device there was a yellow triangle with a black “!” in it. I figured that just indicated the device was rooted or running a 3rd party kernel so I didn’t worry about it.
Today I launched my camera app and it failed to load the interface but showed the image from the camera momentary then crashed back to the home screen. I restarted my device and when the device restarted it was very slow and unresponsive and after unlocking it my live wallpaper was gone replaced with the last background I used before selecting a live background a couple weeks back. No icons or widgets loaded and I am unable to open the settings tray. The only things I am able to do with the phone is pull down the notification bar, respond to text messages, adjust the volume and hold power to restart the phone. All of which are very slow and delayed.
When I connect the device to my computer windows is no longer able to load the drivers and Kies is unable to connect with the device. I am not sure what caused this or how to resolve this issue so any advice or known fixes would be fantastic! I am unable to get to clockwork mod to restore my backup and I am unable to get to Kies or the phone settings to do a factory reset so I really don’t know what to do they were supposed to be a last resort and now I don’t even think I can do them. I am an experienced techie but I am new to android and this is the first device I have rooted so any advice would be great no matter how basic it may be.
UPDATE: I just connected the phone via USB to my laptop at work and it was able to discover and install everything it needed to connect with the phone. I am installing Kies now so at least there is hope of a factory restore, although I really hope it doesn't come to that!

Boot into download mode and flash the stock eg30 tar file from crawrj.
Sent From My Evo Killer!!!

Thanks Already started doing that waiting for it to download now

Still no touchwiz... great!

Try flashing a stock rom via clockworkmod.

efarley said:
Still no touchwiz... great!
Click to expand...
Click to collapse
You can root again and restore your backup, or go to this website www.lostandtired.com (midnight roms blog) click on android development and download and flash the sprint bloat and TW restore zip. Hope that helps.

I flashed the stock rom which didn't change anything so then I used clockworkMod to do a factory reset which ended up trapping me into a boot loop. I could use Odin to flash new roms but the device would never go past the 4G logo
I ended up taking the device back to Best Buy and since the loading screen showed the stock rom and they couldn't get past the 4G logo I just had to say it wasn't rooted and they gave me a new one.
I would love to know if anyone has any idea of what went wrong here so that I can feel comfortable rooting again. Also if anyone has some basic articles handy that teach basics of rooting that would be great, I didn't even know about clockwork mod until after I had this problem so knowing things like that earlier would have helped a lot I think. I'll be spending the weekend looking up everything I can find on the subject so any reading you guys can suggest would be fantastic.

efarley said:
I flashed the stock rom which didn't change anything so then I used clockworkMod to do a factory reset which ended up trapping me into a boot loop. I could use Odin to flash new roms but the device would never go past the 4G logo
I ended up taking the device back to Best Buy and since the loading screen showed the stock rom and they couldn't get past the 4G logo I just had to say it wasn't rooted and they gave me a new one.
I would love to know if anyone has any idea of what went wrong here so that I can feel comfortable rooting again. Also if anyone has some basic articles handy that teach basics of rooting that would be great, I didn't even know about clockwork mod until after I had this problem so knowing things like that earlier would have helped a lot I think. I'll be spending the weekend looking up everything I can find on the subject so any reading you guys can suggest would be fantastic.
Click to expand...
Click to collapse
If you a clockwork and "stock rom" you were still rooted...Doing a factory reset will send you into bootloop when rooted. Trying to flash other roms on a bootloop is not going to work. You need to have grabbed a backup such as Zedo has on his post and put the backup in clockwork folder on your phone. Then flash that in CWM. Would of brought you out of bootloop to a stock rom with his kernal. Now you can flash Roms and kernals or could of flashed crawf or anyone else FULL stock rom and been back to stock kernel and rom and not rooted.

dallastx said:
If you a clockwork and "stock rom" you were still rooted...Doing a factory reset will send you into bootloop when rooted. Trying to flash other roms on a bootloop is not going to work. You need to have grabbed a backup such as Zedo has on his post and put the backup in clockwork folder on your phone. Then flash that in CWM. Would of brought you out of bootloop to a stock rom with his kernal. Now you can flash Roms and kernals or could of flashed crawf or anyone else FULL stock rom and been back to stock kernel and rom and not rooted.
Click to expand...
Click to collapse
Ohhhh that's what happened! Awesome thanks. I will be much better prepared with backups out the wazoo this time haha.
Now if only I could figure out why Touchwiz died in the first place hmmm....

I hope you can figure it out, just postin here to say that when I saw this thread, it reminded me of the thread over in the EVO forums about the guy who claimed that sprint removed his Sense from his phone.

Khilbron said:
I hope you can figure it out, just postin here to say that when I saw this thread, it reminded me of the thread over in the EVO forums about the guy who claimed that sprint removed his Sense from his phone.
Click to expand...
Click to collapse
haha SPRINT removed it?! So that person thinks sprint monitors every device and has a team of techies on staff to hack your phone and brick it if you break their rules?... yeah that totally makes more sense than a file got corrupted when you were messing with the kernel.. some people maybe shouldn't be rooting their devices in the first place haha

[Q] Need Advice...Blank Screen after loading LK 1.6

Hello everyone,
been creeping the forums for the past week...new to the android world but i find the idea of customizing your phone in your own unique way was a good enough reason to leave blackberry after using it for 7years. Anyways....onto my real problem here.
(I appolgize in advance if i mess up the terminology. hopefully you can understand me)
I use a phone on wind mobile (SGH-T999V) and from what i know it's been a safe assumption that if the T999 works then the t999v will most likely work.
I was on AOKP build 5 prior to flashing to the CM M2 ROM...used odin to install CWM_Touch 6.0.1.2.tar then did the steps in
http://forum.xda-developers.com/showthread.php?t=1946701
Edit : I forgot to mention...I can get the screen to go into recovery mode...however, when i press up on the volume key my phone will turn itself off.
and i plugged the phone in again and it decided to be read by my computer.
to install the ROM which worked successfully... however this is where I think i messed up or maybe it has nothing to do with it at all... But my MMS messages did not work so i tried to just play around with some settings and i searched the forums and tried the things that were posted but to no avail. One of the things i did try was to uncheck the privilege unknown applications button and to turn off developers option so USB debugging should be off...or it may have been on...not too sure.
Anyways, so i remembered that I haven't finished the last 2 steps from the "how to flash a rom" in the midst of reinstalling my programs using titanium backup. So i reboot into recovery mode(and this is where i messed up i think) and i wiped my factory data again so after noticing that i did that i went back and restarted the phone and filled in all the information on the welcome screen again. and went back into recovery.
did "wipe cache partition" 3 times AND dalvik cache once then proceeded to install from my sd card the "lk_aosp_jb_tmo-v1.6". After installing i rebooted the device again and i get to see the Samsung Galaxy S3 screen and my screen will go completely black. However, I know it's still on as the battery charging indicator is on and my two buttons around the home button are lit up constantly....out of curiosity i decided to call myself using a land line and the phone is still working (I hope this is good news and that i'm not bricked but teased in a sense i can't fix the screen).
I tried to plug my phone in and it didn't detect it so i reinstalled the drivers and it did detect the phone. I laoded the Samsung Galaxy S3 Toolkit V.2.3.0 in hopes of trying to recover via option 6 "backup and restore your phone" and was hoping to revive it by restoring the nandroid backup however when i typed in my folder the toolkit crashed on me...and now it can't detect my phone as when i try to install the drivers again - the MDA driver seems to fail everytime.
Sorry for the long message...I wanted to be detailed in a sense I don't have to keep giving people more details... your help would be appreciated...Thanks everyone!!

Where'd you get the lk_aosp_jb_tmo_1.6 file from? Never read about it. All you need to do is wipe completely from recovery (data, system, cache...) and install cyanogen and then gapps, reboot.
Sent from my SGH-T999 using xda premium

You can also just odin back to stock and start over from fresh. If you can still get into cwm then just do what he just stated above.
Sent from my SGH-T999 using xda app-developers app

Where'd you get the lk_aosp_jb_tmo_1.6 file from? Never read about it. All you need to do is wipe completely from recovery (data, system, cache...) and install cyanogen and then gapps, reboot.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1845836
It was 1.6 as of yesterday when i downloaded it but it looks like it's 1.7 now. That was my original plan however when i boot into recovery i literally have roughly 1second to pick an option before my screen goes blank again. I tried to boot it a few times into recovery trying to "beat" the blank screen but that hasn't worked.
You can also just odin back to stock and start over from fresh. If you can still get into cwm then just do what he just stated above.
Click to expand...
Click to collapse
Yeah the problem is I can't get back into the cwm as my screen goes blank
I tried to find a link for the stock kernel but the 2-3 that i found all have 404.
Something tells me i just ran into bad luck with the kernel flash. or does it have to do with me doing a wipe/data reset again and perhaps not selecting the debugging options/trusting unknown apps checkbox before running it through again? I'm not sure...just grasping at straws here to why my phone is doing that.
Anyone else have more ideas?? Anything will help...Thanks again!!

Looking like an Odin is your option here. To flash a ROM/kernel, wipe data,system,cache... flash ROM then gapps(optional for which ever ROM you are on) and then kernel. Make sure you're flashing the proper kernel.
Sent from my SGH-T999 using xda premium

mt3g said:
Looking like an Odin is your option here. To flash a ROM/kernel, wipe data,system,cache... flash ROM then gapps(optional for which ever ROM you are on) and then kernel. Make sure you're flashing the proper kernel.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Okay - I'll try it tonight when i get home from work. Here's where my lack of knowledge/noob status comes into play. Thanks for the help.
Do i get into Odin via trying to start my phone in download mode? (I tried to hold the power button/down/home) but that's when i get that glimmer of hope before my screen turns blank again when it asks if i want to continue or reboot my phone.
Or do i try to get it running through Samsung Galaxy S3 Toolkit V.2.3 ?? (If that's the case can you tell me which option i should use to get to the appropriate screen? or should i just launch the odin executable file? (however I'm not sure how that would get anything accomplished if my phone doesn't enter download mode...or maybe it's in download mode when i press up on the volume key but the screen is actually blank? Or maybe i don't understand the process 100%)
But lets say hypothetically speaking I manage to get Odin working. Which proper kernel should i be using? I tried looking for the stock kernel but all the links i found 404'ed. Does anyone have one that works? I'm just kind of trying to get my phone working in general...even if it means going back to stock everything. Pointers Anyone?
Thanks!!
Edit: Forgot to mention the fact that I may not be in debugging mode as i tried to turn that off to see if that had anything to do with my inability to send out MMS msg's as i mentioned in my first post... so that might stop me from using Odin no?

Update
Ok well just an update in case it happens to someone else - I pretty much left the phone alone and didn't touch it for 16hrs. Came home from work and it decided to boot up recovery mode so i just wiped data/cache quicker than a little kid wanting to open Christmas presents on Christmas day when they wake up... Needless to say I didn't bother testing the lk 1.6 kernel so i'm not sure if it works with CM10 running a SGH-T999V (Wind Mobile) phone. I'm trying to think of what may have happened and I'm thinking MAYBE it's because i was charging my phone from 20% all the way to about 95 then decided to plug it into my computer ...so maybe an overheat issue?
Anyways. Thanks for everyone's attempt to help. Much appreciated!

[Q] Various problems with phone. Completely restore phone?

As of recent, I've been having a ton of stability problems on my S2 across all ROMs. It will often get sluggish and randomly shut down, the WiFi will completely drop and I won't be able to connect unless I restart my entire phone, and various other problems. I've done a full wipe when installing any ROM and problems only came up when I installed cwm 6.0.4.3 and I was wondering if that may have been the issue. Either way, I was wondering if there was a way to completely wipe my phone and bring it all the way back to factory and how it came in the box so I can completely start over to try to fix these problems. Any other suggests would be greatly appreciated, too.
Currently running BeanStalk 4.4+, last "stable" build was with Cyanogenmod 10.1 nightly.
Thank you to everyone in the XDA Developer community, you certainly are amazing and thank you to the developers of the search function, I may not know how to use it to it's greatest potential but it's certainly helped me a TON. This is the first time I've felt I've actually need to make a post for something going wrong, sorry if the problem has happened in the past and I missed a post.

Dude i had a similar problem a while back switching from TWRP to CWM. Somehow I corrupted my Dalvik partition. I couldn't even get back to recovery.
So I went here. Followed the instructions and completely went back to stock.
Quick Note that I don't see mentioned enough, YOU WILL LOSE YOUR APPS AND SETTINGS, (hopefully thy're all backed up with Titanium), BUT YOU WILL NOT LOSE YOUR STUFF ON YOUR INTERNAL OR EXTERNAL SD CARDS. The first time I went back to Stock I was scared s***less because I thought I was losing all my pics.
When I booted up the first time, I got the "repairing" Android Icon, it rebooted and I was back in business.
Then I had previously grabbed the TWRP odin flashable 2.5.0.0. tar file from over here. I got 2.5.0.0 because I planned to flash a 4.2.2 ROM after all is said and done. I flashed that with Odin from Download Mode.
I didn't even bother logging into Google on the stock 4.1.2 ( I just can't go back TouchWiz after Cyanogenmod). I just rebooted right into TWRP 2.5.0.0 manually with Volume up and Power button.
From there I factory wiped everything, then superwiped and cachewiped ( both can be found http://forum.xda-developers.com/showthread.php?t=2235141), just to be on the paranoid side.
And finally I flashed Cl3Kener's latest 4.2.2 version of his BlackLiquid and his latest 4.2.2 stable Uber Kernel. I personally think this is the most stable, and as close to perfect ROM thats going to come out for this phone. Of course that is just my opinion after my own experiences with 4.3, 4.3.1, and 4.4.
This is a completely streamlined version of the complete cluster f** I did researching, trial and error, and starting over, while I was in the middle of actually doing it. One last tip I can give, is to get all the files you think you might possibly need and put then on your external SD if you got it, or internal SD. Its a real pain stopping and starting cause your missing a zip you forgot.
Hope this helps
Huge thanks to the Developers threads I Linked to.

A N00b's First Foray Into Modding Their Phone [Root, DN4]

I've always been interested in installing ROMs, rooting, and all the cool stuff that comes with it, since my first android phone. Unfortunately, my first two android phones ended up having a lot of issues with just working stock, so when I finally ended up getting a Samsung Galaxy Note II (I317M - Rogers/Canadian) and it worked... I held off on the modding. Well, my cell contract is up, the warranty has expired, sounds like the perfect time to start.
Of course, this is post KNOX, so after reading around and watching some videos, it was unclear as to whether I could actually install ROMs at all. I wasn't worried about the warranty, just if I could do it, and it would work. So I decided to just jump in anyway.
First task is to root. I tried flashing a CWM+Root with Odin 1.85. No go. Just wouldn't work. So I ended up using chainfire's CF-Auto-root. It would give me the root I wanted, and the stock recovery. The package came with Odin 3.07, and everything worked. It flashed, I downloaded Titanium Backup and launched it, and SuperSU did prompt for root access, and everything went fine. Excellent! Two years after getting the phone and 3 years since I've wanted to do this, everything is going well.
Next task is a custom recovery. I picked TWRP, mostly because I wanted to try the Ditto Note ROM, and they suggested using that. Flashed the recovery in Odin 3.07 and reboot into Recovery with the three finger salute of volume up, home, and power. TWRP launches. Excellent. First order of business is to click the backup button and check all the boxes. Takes 1400-1500 seconds to backup the 6.5GB.
Time to get the ROM and jump in. Downloaded Ditto Note 4 v 2.2 from the team Electron site, and transfer it to my phone. So far things are looking good. Still don't know for SURE if my bootloader is locked or if KNOX will not let me do things, but I have a couple of backups, so I'm going to take the plunge. I reboot into TWRP, wipe the dalvik cache, cache, data, and system, then I install the ROM. Didn't take long at all. Time to see if it works.
At this point I should mention that the reboot function on TWRP(v2.8.6.0) seems to just loop me back into TWRP, no matter which option I choose. So I hold the power button to actually reboot... and...
TA DA! Ditto Note 4 is going through it's first start. I come across a black and white gradient fill background with some sort of animated tesseract sphere in the middle. I'm cool with that, but that also means I can add in my own animation at some point which is even more cool. Go through the start up prompts and...
The first problem. Wifi won't turn on. The other Canadians here will know the pain of not having wifi for your cell with our data prices up here. This is something that needs to be solved. Back on to the forums to see if anyone else has had the same issue, and someone did, the solution? Flash the latest AGNi kernel. Hey, I'm down, now do I flash a kernal with odin or TWRP? After spending way too much time on google, I went to the actual AGNi thread and after a few pages found out that people were installing it with CWM. TWRP it is then. I tried installing it through TWRP, all seemed to go well, though I did note that in the terminal window I did say that it failed to set permissions. That can't be good, but it did say that it installed successfully. Let's give it a go.
The phone started... but nothing had changed. I noticed the OTA Updater app, so I tried using that. Once it was done downloading I clicked the install/flash button. That wasn't a good idea. I flashed it, but ended up in a loop that would only show me TWRP. Even after removing the battery it would only go to TWRP.
What else could I do? I restored the backup in TWRP. Let's start over.
Rooted with the same method, Installed TWRP again, installed DN4 again, tried to run the AGNi settings app and found out that root wasn't working. So after some searching I came across the 2.14 SuperSU update and installed it with TWRP. Root is back. Awesome. Time to get my wifi back, installed the 4.4.5 AGNi kernel, and this time, no permission sets failed. This too, is a great sign. Got the OTA Updater download and this time, decided not to have the program reboot to install it, and just rebooted into TWRP myself to do it manually. Installed fine, rebooted and... my wifi is working.
Mission accomplished. I haven't fully tested everything yet, but I did check to make sure that the s-pen was working, the camera, and after messing with the APN settings a bit, had LTE as well.
All things considered, for a first time, not too bad. So glad I had made that backup before hand. Glad I had remembered to do that, and also to write down the APN stuff before hand. It was mostly correct to what I had, but there were 2 fields that were different, changed them and had full LTE.
So far things seem great! More testing is needed, but I can call and recieve calls, wifi/cellular data works, camera and s-pen works.
Still a noob in this department, but due to the xda-devs making good products, nothing killed the phone, and things are working great.
Thanks to Chainfire, Team Win, Team Electron, psndna88, and anyone else that has worked on any of these projects. So far things work well, and those of us with older phones really appreciate your effort and work on breathing new life into these devices. Cheers mates!

Nice first post for your first one my friend excellent ?! If you need any help with Dn4 you can post in the q&a section since your so new to Xda.
And welcome to the world of Android and Xda enjoy your stay here.. Ttys
Bajan

Need S4 Rom advice!

Hello! Pretty new in XDA forum and I have a couple of questions and concerns. I was browsing through some threads and I was wondering if I could get some opinion/help from other members.
I have a second phone that I want to mod and I need some help.
Device: Samsung Galaxy S4 (ROOTED)
Model#: SGH-M919
Android Version: 4.4.4
Baseband: M919UVUFNK2
It's an old phone and lately, it's been running really slow and if possible, I'd like to make it run as if it was brand new or at least somewhat close. So the question is, are there any recommended stable roms/mods I could use and if there are/is, will I be able to use it with my rooted phone or do I have to completely factory reset it before I apply the mods/roms?
Thank you!

Hi @Mr.LinK,
Just yesterday I finally got sick of my M919 slow/battery drain/old stuff and decided it was time for a reset. I was running SlimKat from over a year ago and while it was a great ROM, I had accumulated so much crap that it was getting really bogged down. This just happens over time no matter what OS, no fault to Slim. But I was also looking to move to Lollipop. Here's what I did:
1. Backed up using several methodologies (full backup with TWRP just in case, then from Android I backed stuff up with Helium, and used Backup My Mobile for SMS/MMS etc., an EFS backup just in case, etc..)
2. From within Android, did a factory reset. This sent the phone into recovery, and it formatted the data partition.
3. Rebooted to recovery again, and used TWRP to manually format the media section, just in case something was left there. Then wiped everything except the external SD.
4. Used ODIN to flash the OH3 firmware onto my MDL M919, without letting reboot after (unchecked the reboot checkbox). Pulled battery, rebooted back into download mode again, and flashed OH3 a second time... this gets around some instance people have reported about incomplete upgrades of firmware and all sorts of issues... better safe than sorry.
5. Let phone boot into now 100 % stock OH3 Android 4.4.4. YEEEUKKK. Some part of me thought I would just root the thing and get rid of Samsung crapware, but just the sheer annoyance of the T-Mobile boot animation was enough to remind me why I left stock long ago. Anyway, I let it boot, and set it up minimally with just 1 Google account, not restoring from backup. To my surprise it found the ATT network (I'm an ATT user, not T-Mobile... I just prefer T-Mo phones because they have unlocked bootloaders) and APN no problem no effort from me. Usually I have to enter an APN.
6. I tested the phone out to make sure all systems were working. GPS, WIFI, Bluetooth, etc.. To my surprise, first time I ran the camera app, it applied a firmware patch. Sweet. I'm glad I went through this step. Coming from ancient MDL, I figured there might be some kinks like this. I let it sit on stock for a few hours while I did stuff with my kids.
7. Back home, I did a factory reset from within Android. Then I flashed the latest TWRP tar file (2.8.7.0) using ODIN, and in TWRP did a full wipe of everything again.
8. At this point I flashed Danvdh's GPE edition of Lollipop from here.
http://forum.xda-developers.com/showthread.php?t=2539361
Installation went smoothly. It's a very basic set of apps that it comes with (Google play is there, but you have to download email/messaging apps from the store such as Gmail and Messaging, Maps, etc). I like this approach!
I've been gradually setting things back up, and am very happy with things so far. Haven't run into any problems yet. The nice pure GPE android experience is refreshing.

@Frankenscript Thanks for the information. I was reading the linked thread and it looks really good so I'll give it a try

Mr.LinK said:
@Frankenscript Thanks for the information. I was reading the linked thread and it looks really good so I'll give it a try
Click to expand...
Click to collapse
Good luck and let us know how it goes!

Frankenscript said:
Good luck and let us know how it goes!
Click to expand...
Click to collapse
I just completely flashed my phone with the ROM and I'm pretty happy with the outcome. No bloatware feels so nice. I've been tinkering with it for a while now and I haven't encountered any problems so far but I did notice that model number changed to GT-I9505G. I'm assuming that's normal since the rom is based off of another variant which makes sense, correct me if I'm wrong. Will this complicate future updates or other rom installation? If so, are there any ways of reverting back to the original model number?

Mr.LinK said:
I just completely flashed my phone with the ROM and I'm pretty happy with the outcome. No bloatware feels so nice. I've been tinkering with it for a while now and I haven't encountered any problems so far but I did notice that model number changed to GT-I9505G. I'm assuming that's normal since the rom is based off of another variant which makes sense, correct me if I'm wrong. Will this complicate future updates or other rom installation? If so, are there any ways of reverting back to the original model number?
Click to expand...
Click to collapse
I'm pretty sure we can change the reported model number by modifying the build.prop file. I just haven't poked around with it yet... I did ask the question in the thread and am waiting for a reply. I haven't had to do this kind of thing for over a year, and I forget the build.prop key that does it. But I had some concern that it might bork something else down the road so I decided to wait a bit. IT's just a cosmetic thing and I'm SOOO enjoying the experience right now.
Two little things I'm still fishing around for answers to:
-In the drop down quick access menu, I wish there was a sound/vibrate/mute toggle. I can make one with PowerToggles but maybe there's a way to adjust what's in the native one.
-Really silly, but the power off button when pressed just seems to ... power off the phone!? No option for restart / recovery. Maybe there's an option to set this somewhere; haven't checked.
Still, these are all minor things to sort out. Really, I think I'm very sold on GPE editions now thanks to Danvdh's work.
Marc

Just an update, my phone just rebooted twice in the last 5 mins or so. Was watching on my netflix and it randomly rebooted. Any idea what's causing it and how to prevent it from happening?

Mr.LinK said:
Just an update, my phone just rebooted twice in the last 5 mins or so. Was watching on my netflix and it randomly rebooted. Any idea what's causing it and how to prevent it from happening?
Click to expand...
Click to collapse
Haven't seen random reboots. I think I got maybe one reboot since installing the ROM. Then again, I haven't put NF on the phone. I do know that Netflix app had some issues on my Shield tablet, and the manufacturer (Nvidia) came out with a patch... maybe it's something general in Lollipop?

Frankenscript said:
Two little things I'm still fishing around for answers to:
-In the drop down quick access menu, I wish there was a sound/vibrate/mute toggle. I can make one with PowerToggles but maybe there's a way to adjust what's in the native one.
-Really silly, but the power off button when pressed just seems to ... power off the phone!? No option for restart / recovery. Maybe there's an option to set this somewhere; haven't checked.
Click to expand...
Click to collapse
Both if those can be fixed with Xposed modules.
Sent from my SGH-M919 using XDA Free mobile app

Will look into doing this in a week or so. Thanks
Sent back in time via Android 9.0 TimeText feature.