Database Users

[Q] Reboot Button problem

OK, I'd appreciate some help here. I Just downloaded Zenmaster's Reboot button app. I probably made a mistake by going to ROM manager and its install from SD card option.
The install started out fine, but just stalled at installing update. Left it there for 30 minutes.
I did a battery pull and the phone went into recovery except it says at the bottom of the screen:
E: Can't mount /dev/block/mmcblk01p1
(Invalid Arguement)
#MANUAL MODE#
The upper screen has the typical
reboot system now
Apply sdcard...
wipe data/factory reset
wipe cache partition
Nothing happens with either reboot system now or apply from sdcard
So I really would appreciate...what now.

Are you rooted? Do you have Clockwork Recovery installed?
Are you hitting the "Home" soft button key on the Reboot option? That's the "Enter" key for the stock recovery screen, not the Power button like it is for Clockwork.
-Div

Diversion said:
Are you rooted? Do you have Clockwork Recovery installed?
Are you hitting the "Home" soft button key on the Reboot option? That's the "Enter" key for the stock recovery screen, not the Power button like it is for Clockwork.
-Div
Click to expand...
Click to collapse
Thanks for your response.
Yes I'm rooted and yes I have CWM.
This is embarrassing now, because I WAS NOT hitting the home button, which I should have known to do, but obviously forgot. Did that and I'm back up. Old Droid habits die hard I guess.
My apologies for using up bandwidth and thank you again.

SteveC485 said:
Thanks for your response.
Yes I'm rooted and yes I have CWM.
This is embarrassing now, because I WAS NOT hitting the home button, which I should have known to do, but obviously forgot. Did that and I'm back up.
My apologizes for using up bandwidth and thank you again.
Click to expand...
Click to collapse
That's okay, I believe I freaked out the first time I was in stock recovery as well not getting any response from the power button

SteveC485 said:
OK, I'd appreciate some help here. I Just downloaded Zenmaster's Reboot button app. I probably made a mistake by going to ROM manager and its install from SD card option.
Click to expand...
Click to collapse
Yeah, that's not gonna work. The app is a .apk file, which gets installed via adb or Root Manager/Astro. It's not a flashable zip.
It's also now available on the market .

Zennmaster said:
It's also now available on the market .
Click to expand...
Click to collapse
Bonus. That is fantastic news.

Well naming the .zip to .apk worked and Reboot Button worked. Sort of. I think what happened here was no fault of the app, but something related to the relationship between my phone and voodoo. I had never seen any particular problem on my phone, but I just wanted a way to disable the thing as I was contemplating flashing jt's ROM.
Well the disabling of voodo lost root on my phone. I use Launcher Pro and that was gone too. So I tried reinstalling that and entered a force close loop from hell. After installing the LP, the phone regressed to the same opening screen it had when out of the box, different from the static wallpaper I had.
There is a thread on this here:
http://forum.androidcentral.com/fascinate-roms-hacks/38029-how-escape-force-close-loop-hell.html
I followed that and got back to the out of the box Fascinate state. Only part of my apps, and not all of the paid ones showed up in Market, even after an overnight wait. The significant missing one is Documents to Go.
There was 0.00 space left on internal memory, so I did a factory reset.
This would not be a big deal, BUT the phone will not root, so I can't use Titanium Backup to restore stuff. The Samsung Drivers are installed, the USB cable is the one that came with the phone, and the computer recognizes the device. However, Odin seems to think the device is not connected.
So, I'm not sure what is going on with this phone of mine. Again, I don't think it is the app.
Edit; All is back to normal

Titanium pro no menu or settings?

I flashed a new rom and after that i installed Titanium pro, busybox and supersu is alredy there. My issue is that i cannot access the settings or menu from Titanium anymore. The icon at the top right corner is grey and when i click on it goes straight into batch....? the rom is 6.0.1 could it be a compatibility issue?

angeluszero said:
I flashed a new rom and after that i installed Titanium pro, busybox and supersu is alredy there. My issue is that i cannot access the settings or menu from Titanium anymore. The icon at the top right corner is grey and when i click on it goes straight into batch....? the rom is 6.0.1 could it be a compatibility issue?
Click to expand...
Click to collapse
This happened to me too, I don't know why does it happen but you can access the menu holding Home button.

pmzerdan said:
This happened to me too, I don't know why does it happen but you can access the menu holding Home button.
Click to expand...
Click to collapse
try this:
[email protected]

angeluszero said:
I flashed a new rom and after that i installed Titanium pro, busybox and supersu is alredy there. My issue is that i cannot access the settings or menu from Titanium anymore. The icon at the top right corner is grey and when i click on it goes straight into batch....? the rom is 6.0.1 could it be a compatibility issue?
Click to expand...
Click to collapse
Yes, this happens sometimes with non-TW roms. I believe I did a button assignment change in CM and I was able to access it, but by default as stated previously holding the home button will give you the menu.

New N935F 8.0 Update - Best Way to Install w/o Getting Lock

Hi All,
What is the best way to install the new N935F update without having to wait another 7 days?
(Update: N935FXXU2BRF1_N935FOLB2BRF1_THL.zip)
Already on 8.0...this is a new security patch update.
Note: I am rooted and using TWRP

How is Root working for you and how did you do it? What are the drawbacks (what doesn't work)?

ymmp said:
How is Root working for you and how did you do it? What are the drawbacks (what doesn't work)?
Click to expand...
Click to collapse
Root is working okay. No problems.
Here are the steps I followed:
1. turn off device
2. home+Vol. Down+Power -- get into download mode
3. start Odin 3.12
4. untick Auto-reboot
5. Install Twrp
6. After install => press Home+Vol/ Down+Power
7. At black screen => Home+Vol. Up+Power
8. In Twrp => Wipe -> Format Data -> Yes
9. Reboot into Recovery
10. Install Magisk
11. Wipe Cache & Dalvik
12. Install RMM pkg
13. Wipe Cache & Dalvik
14. Reboot System
15. After setup, check build.prop => ro.security.vaultkeeper.feature=1" change the value to 0.
16. Reboot device
17. Disable SecurityLogAgent pop-up
18. Download "CSC Features Expert for Samsung" on the Play Store (Free)
Launch the app and give it the root rights
In the search bar, type "DisableAntiMalware" (Without commas)
Click on the item and enter the value "TRUE" (Same)
Click on "Save"
Reboot
19. Fix Samsung Health
Download MiXplorer v6.22.1 HERE (Or any file manager of your choice if you're more familiar with it. I recommend MiXplorer because I use it everyday, it's lightweight, really nice to use, free and it's made by a great guy on XDA )
Access root partition and go into the "/system" folder
Open the file "build.prop" with a text editor.
Simply change the line "ro.config.tima=1" to "ro.config.tima=0"
Save the changes, and close the app.
Reboot.

gcrutchr said:
Root is working okay. No problems.
Here are the steps I followed:
1. turn off device
2. home+Vol. Down+Power -- get into download mode
3. start Odin 3.12
4. untick Auto-reboot
5. Install Twrp
6. After install => press Home+Vol/ Down+Power
7. At black screen => Home+Vol. Up+Power
8. In Twrp => Wipe -> Format Data -> Yes
9. Reboot into Recovery
10. Install Magisk
11. Wipe Cache & Dalvik
12. Install RMM pkg
13. Wipe Cache & Dalvik
14. Reboot System
15. After setup, check build.prop => ro.security.vaultkeeper.feature=1" change the value to 0.
16. Reboot device
17. Disable SecurityLogAgent pop-up
18. Download "CSC Features Expert for Samsung" on the Play Store (Free)
Launch the app and give it the root rights
In the search bar, type "DisableAntiMalware" (Without commas)
Click on the item and enter the value "TRUE" (Same)
Click on "Save"
Reboot
19. Fix Samsung Health
Download MiXplorer v6.22.1 HERE (Or any file manager of your choice if you're more familiar with it. I recommend MiXplorer because I use it everyday, it's lightweight, really nice to use, free and it's made by a great guy on XDA )
Access root partition and go into the "/system" folder
Open the file "build.prop" with a text editor.
Simply change the line "ro.config.tima=1" to "ro.config.tima=0"
Save the changes, and close the app.
Reboot.
Click to expand...
Click to collapse
Thanks for taking the time for that!
So everything works fine except for the security stuff?
As for the new update, I installed it through OTA and I can't figure out what it changed. I'm guessing you can't do OTA anymore once you root? If so, are you concerned it could be an issue in the future?

Did you get the update installed successfully? What changed? Is it stable? My current firmware with the April 1 security patch is giving me great battery life and is quite stable so I'm hesitant to upgrade right now...

jkcz said:
Did you get the update installed successfully? What changed? Is it stable? My current firmware with the April 1 security patch is giving me great battery life and is quite stable so I'm hesitant to upgrade right now...
Click to expand...
Click to collapse
I have not upgraded yet. I do not want the RMM lock back (7-day wait). I suppose I can create a TWRP install with the lock app removed and the build.prop edited. I will look into it today.

jkcz said:
Did you get the update installed successfully? What changed? Is it stable? My current firmware with the April 1 security patch is giving me great battery life and is quite stable so I'm hesitant to upgrade right now...
Click to expand...
Click to collapse
Are you also rooted?
I installed the update OTA, and I really don't know what changed even though it was over 200mb.
It is still Oreo 8.0, Samsung Exp. 9.0 and And. Sec. April 1. It does seem that the kernel and Samsung Security were updated.
Probably no connection, but right after the update an update to Good Lock became available.

ymmp said:
Are you also rooted?
I installed the update OTA, and I really don't know what changed even though it was over 200mb.
It is still Oreo 8.0, Samsung Exp. 9.0 and And. Sec. April 1. It does seem that the kernel and Samsung Security were updated.
Probably no connection, but right after the update an update to Good Lock became available.
Click to expand...
Click to collapse
No, I didn't root. Device was great how it was and I didnt have a need to yet so I left it. When did you do the update? Can you comment on device stability and battery life after the update?

jkcz said:
No, I didn't root. Device was great how it was and I didnt have a need to yet so I left it. When did you do the update? Can you comment on device stability and battery life after the update?
Click to expand...
Click to collapse
Updated day and a half ago. I really don't see any difference in performance or features. I only have the phone for less than 3 weeks so maybe I haven't gotten to know it well enough to be able to tell.
Which Carrier are you using it on?

ymmp said:
Updated day and a half ago. I really don't see any difference in performance or features. I only have the phone for less than 3 weeks so maybe I haven't gotten to know it well enough to be able to tell.
Which Carrier are you using it on?
Click to expand...
Click to collapse
Currently using it abroad.

I know this isn't the original topic, but there doesn't seem much feedback on this phone - and there's some activity on this thread ?
The one thing bothering me about the phone (otherwise I absolutely love it) is data drops to "H" during phone call, so I just tested (on T mobile) over 100mb/s download speed goes to .3 during phone call - any fix?

Best way to flash new firmware and not get stuck waiting 7 days is to make sure odin doesn't auto reboot after the flash. Once it done flashing disconnect the phone and go back into download mode (do not reboot) and flash the twrp and root that you are using. Boot into recovery and wipe cache then reboot.
Sent from my [device_name] using XDA-Developers Legacy app

Phone stuck on 'Phone is starting...' screen

I am stuck on the 'Phone is starting...' screen. This is how I landed here
1. Added Finger Print Customizations when the phone was working and they did work as expected.
2. Noticed update from 9.0.10 to 9.0.10
3. Flashed stock 9.0.10 image over Bluespark and Magisk rooted image
4. Flashing stock 9.0.10 caused getting stuck in the 'Phone is starting...' screen
5. I can hear my phone ringing on this screen, but I cannot answer any calls since the phone is stuck forever on this screen
6. I tried flashing bluespark and magisk in the hopes of being able to boot, but that just cases my old boot screen to show up and then going back to restarting in a loop again
I believe OPSystemUI.apk (file that I replaced under /system/priv-app for getting custom finger print animation) is causing the issue. I do not know how to restore the stock version of this file without wiping all my data clean. I am not sure if this is the file causing the issue. Is there any way to get the phone started by flashing some files via adb?
Appreciate the inputs in advance.

pramathesh said:
I am stuck on the 'Phone is starting...' screen. This is how I landed here
1. Added Finger Print Customizations when the phone was working and they did work as expected.
2. Noticed update from 9.0.10 to 9.0.10
3. Flashed stock 9.0.10 image over Bluespark and Magisk rooted image
4. Flashing stock 9.0.10 caused getting stuck in the 'Phone is starting...' screen
5. I can hear my phone ringing on this screen, but I cannot answer any calls since the phone is stuck forever on this screen
6. I tried flashing bluespark and magisk in the hopes of being able to boot, but that just cases my old boot screen to show up and then going back to restarting in a loop again
I believe OPSystemUI.apk (file that I replaced under /system/priv-app for getting custom finger print animation) is causing the issue. I do not know how to restore the stock version of this file without wiping all my data clean. I am not sure if this is the file causing the issue. Is there any way to get the phone started by flashing some files via adb?
Appreciate the inputs in advance.
Click to expand...
Click to collapse
You don't have launcher installed.
Just sideload any launcher apk using advanced and you should be good..

indian84 said:
You don't have launcher installed.
Just sideload any launcher aok using advanced and you should be good..
Click to expand...
Click to collapse
Are you sure? Before messing it up with stock boot image I had nova running for me and had also kept one plus stock installed. Not sure how I can side load a launcher. Any pointers to that, please?

pramathesh said:
Are you sure? Before messing it up with stock boot image I had nova running for me and had also kept one plus stock installed. Not sure how I can side load a launcher. Any pointers to that, please?
Click to expand...
Click to collapse
Not 100% sure it'll help.
But won't hurt to try..

indian84 said:
Not 100% sure it'll help.
But won't hurt to try..
Click to expand...
Click to collapse
True. Any idea on how to side load an apk? I usually side load zip. Apk is new to me.

pramathesh said:
True. Any idea on how to side load an apk? I usually side load zip. Apk is new to me.
Click to expand...
Click to collapse
Well, I shared a screenshot with you.
It's similar to sideloading a zip..

indian84 said:
Well, I shared a screenshot with you.
It's similar to sideloading a zip..
Click to expand...
Click to collapse
I am unable to open the image you have attached

pramathesh said:
I am unable to open the image you have attached
Click to expand...
Click to collapse
Google would help.
Too lazy to type..
Lol

pramathesh said:
True. Any idea on how to side load an apk? I usually side load zip. Apk is new to me.
Click to expand...
Click to collapse
Adb install name.apk
Where name.apk is the app you're installing

indian84 said:
Not 100% sure it'll help.
But won't hurt to try..
Click to expand...
Click to collapse
I am getting this while trying to sideload apk
C:\Program Files (x86)\Minimal ADB and Fastboot>adb install launcher.apk
adb: connect error for write: closed

If you use bluespark TWRP then you're several weeks late, use officially working TWRP check in ROM section
Sideload the whole ROM to go back to normal, with temporary boot TWRP in fastboot mode

Striatum_bdr said:
If you use bluespark TWRP then you're several weeks late, use officially working TWRP check in ROM section
Sideload the whole ROM to go back to normal, with temporary boot TWRP in fastboot mode
Click to expand...
Click to collapse
I have the 9.0.10 downloaded from here:
https://forum.xda-developers.com/oneplus-6t/how-to/official-oxygenos-9-0-4-ota-oneplus-6t-t3860953
I unzipped them found a .bin file. Is there any guide on extracting the binary files and flashing the entire rom via ADB?

pramathesh said:
I have the 9.0.10 downloaded from here:
https://forum.xda-developers.com/oneplus-6t/how-to/official-oxygenos-9-0-4-ota-oneplus-6t-t3860953
I unzipped them found a .bin file. Is there any guide on extracting the binary files and flashing the entire rom via ADB?
Click to expand...
Click to collapse
Use fastboot ROM in that case. See relevant threads

Striatum_bdr said:
Use fastboot ROM in that case. See relevant threads
Click to expand...
Click to collapse
Let me check, is it okay to PM you?

pramathesh said:
Let me check, is it okay to PM you?
Click to expand...
Click to collapse
No, I've never had to use that, and all is explained clearly in the threads giving fastboot ROM
Ultimate tool is msmdownload, there are dedicated threads also

Striatum_bdr said:
No, I've never had to use that, and all is explained clearly in the threads giving fastboot ROM
Ultimate tool is msmdownload, there are dedicated threads also
Click to expand...
Click to collapse
Sorry for being so naive but I couldn't find any ROM that would have fastboot support. There is very less stuff for 6T to comb from.

pramathesh said:
Sorry for being so naive but I couldn't find any ROM that would have fastboot support. There is very less stuff for 6T to comb from.
Click to expand...
Click to collapse
Not very hard to find
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516

Striatum_bdr said:
Not very hard to find
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
Click to expand...
Click to collapse
Silly me, I was looking in the ROM section. I will use this and update the thread again

Hey! It worked. The phone is up and running now. Only thing is I lost all the data on the phone

Solution
Next time you face this issue in any ROM, you can do the following to come out of it. However, you would need to have a customised notification panel, which will allow you to go to settings and security option. Also, ensure you do not have a default launcher, if you have more than 1 launcher in your phone that you use.
Just long press any icon which leads to settings, or click on the settings icon from the notification bar.
It will open a blank settings page. Do a scroll up and down, and it will refresh.
Then go to security and privacy and delete the fingerprints.
You may also need to delete the security pin or swipe or the lock screen settings.
NOTE: Do not delete the locksettings.db from Recovery mode. It will break everything and the above steps might not help.
BTW, I am facing this issue for the last 3 days. Have been doing clean flash everytime. I was searching this issue on internet, but yours came up just now, and I read, FingerPrint, and it stuck me. Now it worked. Rebooting now. But posting the comment here in case I face any issues. Want to help you, as I know what the feeling is like. Frustrated and tired, wanting to kill someone.
Edit: Rebooted without any lock pin or FP. Shows phoe is starting, and starts in 2 seconds and allows access.
Will set a pin and check now.
Then will set one FP and check.
Edit2: Set pin lock and rebooted. Works okay..

no gestures after update

I have IN2023 latest OTA oxygen OS 11.0.1.1.INI11BA.
After rooting on magisk canary (as well as beta) I can neither enable gestures nor hide the Navbar (in system buttons and gestures). (see picture)
Hold powerbutton to open the menu also doesn't work (it simple turns the power off, changing to google assistant does work)
How to solve this, did I do something wrong or is it a bug?

henk-jan said:
I have IN2023 latest OTA oxygen OS 11.0.1.1.INI11BA.
After rooting on magisk canary (as well as beta) I can neither enable gestures nor hide the Navbar (in system buttons and gestures). (see picture)
Hold powerbutton to open the menu also doesn't work (it simple turns the power off, changing to google assistant does work)
How to solve this, did I do something wrong or is it a bug?
Click to expand...
Click to collapse
What modules have you got installed??
I noticed my center clock mod broke gestures too.
Also if you have frozen or uninstalled the OnePlus launcher this too breaks gestures.
Chances are it's a mod that broke it or freezing the OOS launcher..
But then again it's only just came out so who knows what's going on at the moment

dladz said:
What modules have you got installed??
I noticed my center clock mod broke gestures too.
Also if you have frozen or uninstalled the OnePlus launcher this too breaks gestures.
Chances are it's a mod that broke it or freezing the OOS launcher..
But then again it's only just came out so who knows what's going on at the moment
Click to expand...
Click to collapse
Thanks for the reply. The centre clock mod works fine. I use nova launcher and indeed freezing the OOS launcher when switching to it
It all happens before any mod is installed.
Your answer sugests there's a bug in Magisk comparing to the latest OTA

henk-jan said:
Thanks for the reply. The centre clock mod works fine. I use nova launcher and indeed freezing the OOS launcher when switching to it
It all happens before any mod is installed.
Your answer sugests there's a bug in Magisk comparing to the latest OTA
Click to expand...
Click to collapse
In regards to the centre clock mod no it's due to the apks used not being the most up to date.
In regards to your issue, the only way to find out what it is is to remove modules then try again. If it goes away then install one at a time, obviously unfreeze the OOS launcher too

dladz said:
In regards to the centre clock mod no it's due to the apks used not being the most up to date.
In regards to your issue, the only way to find out what it is is to remove modules then try again. If it goes away then install one at a time, obviously unfreeze the OOS launcher too
Click to expand...
Click to collapse
Maybe you've been to quick: I wrote it happens before any mod is set. It doesn't happen without root. (and everything else is the same)
As long as I'm the only one I have to start from scratch, otherwise I'll wait till a solution is found. (I guess from John Wu)
Regards, Henk-Jan

henk-jan said:
Maybe you've been to quick: I wrote it happens before any mod is set. It doesn't happen without root. (and everything else is the same)
As long as I'm the only one I have to start from scratch, otherwise I'll wait till a solution is found. (I guess from John Wu)
Regards, Henk-Jan
Click to expand...
Click to collapse
Oh really??
So you're not running any modules, and no other mods or changes?
Then youre alone with this problem..
It's possible that some modules were left behind before the update. Beyond that I'm not sure buddy, mines working fine unless I make the aforementioned changes.

dladz said:
Oh really??
So you're not running any modules, and no other mods or changes?
Then youre alone with this problem..
It's possible that some modules were left behind before the update. Beyond that I'm not sure buddy, mines working fine unless I make the aforementioned changes.
Click to expand...
Click to collapse
Thanks, then I'll start from scratch

henk-jan said:
Thanks, then I'll start from scratch
Click to expand...
Click to collapse
Bit of a long shot but try this
1. Connect your phone to your computer.
2. Reboot the phone, then during the boot animation have this command ready and run via ADB.
adb wait-for-device shell magisk --remove-modules
3. Reboot, cycle the gestures to nav bar and see if it works.
That'll eliminate any left over modules, just incase, even if they're disabled from magisk they can still be left behind, have seen this a few times.

solved
dladz said:
Bit of a long shot but try this
1. Connect your phone to your computer.
2. Reboot the phone, then during the boot animation have this command ready and run via ADB.
adb wait-for-device shell magisk --remove-modules
3. Reboot, cycle the gestures to nav bar and see if it works.
That'll eliminate any left over modules, just incase, even if they're disabled from magisk they can still be left behind, have seen this a few times.
Click to expand...
Click to collapse
I feel so stupid
Going to bed I just realised I completely forgot the CC mod. I removed all mods except this one
Now I did the problem is solved.
Thanks for all the help and pointing to the right direction!

henk-jan said:
I feel so stupid
Going to bed I just realised I completely forgot the CC mod. I removed all mods except this one
Now I did the problem is solved.
Thanks for all the help and pointing to the right direction!
Click to expand...
Click to collapse
No worries man. Hit the thanks button.:good:
Glad you're sorted