• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
Search This thread

immortalneo

Senior Member
Jan 25, 2011
4,423
1,951
Malappuram, Kerala
There are a lot of people joining XDA on a daily basis, and there are a lot of repetitive questions being asked
which clutter up the Development and 'Q & A' threads. Point them here. Feel free to ask or answer questions.

The idea of this thread is to get users to help other users with their problems/questions. People are usually
ridiculed for asking questions that other people deem stupid even though it may be a legitimate question. This
leads to new users being afraid to ask questions!

Only provide well mannered help towards users in this thread. Please do not spoon feed, but rather point in
the direction where that user can find an answer
and educate himself. If you don't want to answer, at least
point out where to find the answer.



Before posting anything, I strongly advise you to read THIS thread.

Then, have a quick look at the names of threads in Post No. 2, you might find what you need right away.

Third. Even if you do get your question answered, please do come back and read threads in Post No. 2
(coming later as soon as we start getting the guides) to educate yourself. You'll be surprised how much time
and frustration it will save you in the future!



No abuse towards noobs tolerated here! That means:
NO TROLLING
NO NAME CALLING
NO RIDICULING
NO FLAMING


ASK ANY QUESTION HERE! No question is stupid or irrelevant in this thread. You will either get an answer or will get pointed in the right direction.


*A Special Thanks to mark manning for his help in creating this thread*


HALL OF FAME

People who contributed most to this thread and helped countless number of people with their
problems/questions. In no particular order.

Bruce Wayne
post-mortem
SilentStrider
Ghostfreak NB
mayank9856
sgs22012
Zatta
ADDICT.ANK



These people also have the right to use the banner below:
Newbie%20Thread%20Sign.gif


Just add this code to your signature:
HTML:
[URL="http://forum.xda-developers.com/showthread.php?t=2257421"][IMG]https://dl.dropboxusercontent.com/u/41066660/Newbie%20Thread%20Sign.gif[/IMG][/URL]
 
Last edited:

tchl

Senior Member
Nov 15, 2021
65
6
Yes, it's normal, as an update always replace the boot image and sometimes the recovery if this partition is where Magisk-su lies then this occurs. If your device has a TWRP then it can prevent it from happening, otherwise will do. For auto updates, most devices have the option to allow or not, check in the /settings/about phone or /settings/software update or Developer options/Auto update system.
FLASHED each partition individually and it worked for some reason. Have no idea why it worked but I'd like to know.
 
Last edited:

fmlfr

New member
Nov 29, 2021
2
0
Did you follow the other steps to flash a GSI, maybe the vbmeta image or factory resetting before to try to boot?. To power off device to can flash the stock ROM you simply have to press the three buttons at same time for about 12 seconds, prepare the SP Flash tool, prepare the stock ROM and connect your device depending on if your OEM allow flashing through preloader the buttons' combination may vary.
Hi look can we contact on any platform if there here dms we can talk there i really need help fixing this phone. or like try to help me to flash a gsi so i can flash a stock rom.
 

tchl

Senior Member
Nov 15, 2021
65
6
What do you mean with "it worked"? Maybe you flashed also the boot and/or stock recovery, and Magisk is still there?
Yesterday, I found a flash file xml for the original firmware and so I flashed each and every step as it was laid out in the xml document. It worked but then that security update wiped out my root with Magisk. Today, I tried to flash again but I did all of the fastboot flash commands in one paste from the notepad app. For whatever reason it didn't take and I was back to a boot loop. I wiped it all clean with TWRP and then reflashed each step individually. Somehow that worked.

As soon as I get this device rooted and set up to my proxy, I am going to back it up to TWRP. :) I'm also disabling automatic updates in USB debugging and rechecking it before each reboot.
 

usrx69

New member
Nov 30, 2021
1
0
I've been trying to change pixel experience custom recovery but I got no permission error.
Then I configured udev rules and no permission error is gone but while flashing custom recovery or booting through that its progress bar gets stuck.
In short I can't able to flash custom recovery.
HELP!
 

Attachments

  • Screenshot from 2021-11-30 17-32-08.png
    Screenshot from 2021-11-30 17-32-08.png
    54.6 KB · Views: 7

SubwayChamp

Senior Member
Aug 6, 2016
3,403
3
1,443
Hi look can we contact on any platform if there here dms we can talk there i really need help fixing this phone. or like try to help me to flash a gsi so i can flash a stock rom.
You have to find exactly which processor uses this device, either Qualcomm, MediaTek. Spreadtrum (if it has Android Go probably this), or other.

Then based on that, find the right tool and the right stock ROM to flash it in order to return to its original state.

Only from a Fixed device you could think to flash some GSI, if your device has Android Go as it is read here https://www.gsmarena.com/infinix_hot_6-9426.php the method would be tricky, read on here to have some idea https://forum.xda-developers.com/t/aosp-8-1-2019-03-06-phh-treble.3709659/
 

Andy243

Member
Nov 24, 2017
5
0
I really need someone's help! My grandma forgot her google account password and I need it in order to get her covid certificate(green pass or whatever). She didn't put any phone number or any recovery emails so that's a no go. Can I somehow use adb and find her password somewhere? I am really noob at adb stuff and I need help. The phone runs android 5.1 and is not rooted. I enabled usb debugging and I downloaded the adb files so I am good there. Can someone help me find my grandma's google password? Then I'll put my email as recovery and add her phone number.
 

kos25k

Senior Member
Nov 15, 2012
3,106
428
Hello.I wonder if there is any module that is able to lockor hide quick settings icons on secure lockscreen on android 11 lineage os!
 

tchl

Senior Member
Nov 15, 2021
65
6
I currently have an app that refuses to run because it thinks I have Developers Mode activated but I do not. I have rebooted, uninstalled the app and reinstalled the app but I keep getting the error message.

Why does this app think I am in Developers Mode? Could it possibly have something to do with the bloatware and a few system packages that I uninstalled? Device is a Moto G6 and is rooted. SafetyCheck is red. Trying to solve that riddle as well. Maybe the two are connected?
 

xAxB

Member
Mar 9, 2017
45
9
Is it better to update phone from major version to major version (e.g. Android 7 -> 8 -> 9 -> 10) or make that leap of faith?

On one hand, I think that going version by version would enable me to make sure will make it easier to find out the case of something breaking, but I am also wondering if each update will leave and accumulate garbage on my phone that doesn't get cleaned up properly.

Thanks.

(Not sure if relevant but I am updating a rooted Pixel phone)
 

Toasty1Too

Member
May 13, 2019
10
1
OnePlus 6
LG G8X ThinQ
Thanks so much for this thread!

I have a brand new Moto G100, purchased direct from Motorola. I have unlocked my bootloader, but I'd like to pull a full copy of all of my device's files prior to continuing down the road to add root, custom roms, etc.

What is the best way to do this *before* I root my device?

For reference, I attempted to use this(quite old) guide, and though I am able to access adb shell on my device, none of the other commands seem to work. https://forum.xda-developers.com/t/guide-making-dump-files-out-of-android-device-partitions.2450045/

Edit: By device files, I mean boot.img, system.img, etc.
 

Relected

Member
Nov 30, 2021
28
0
hello everyone, this is my very first post ever on XDA (and you guessed it, ROOT!)

so i have this phone which is really tough that i apparently cannot unlock its bootloader

Huawei Y9 2018 Android 9 HWFLA-H FLA-LX1 Kirin 659A with EMUI 9.1.0

9.1.0.186(C185E12R1P5) specifically

i have tried multiple times to find a working method to unlock the bootloader but alas nothing worked, also i cant find a supported TWRP "thing" (idk what to call it), and the closest thing i could find for the firmware of the device was this and this which i still dont really trust

is there an free or easy/safe way to get an unlock code for this device, because i really want to root it and maybe find a good custom ROM for it :)
also would PotatoNV or this work on my phone? since i am too scared to open it, its my only phone

ps: i am currently using voidlinux and i have adb/fastboot already installed and working on my laptop, and i hope to god that this wouldn't make stuff more difficult.

edit: i will be making my own new thread for this, how do i delete this post
 
Last edited:

Vitale87

Member
Aug 18, 2013
11
0
I have a note 9 running Android 10 on One UI 2.5

I debloated a lot of stuff on the phone everything works fine except 1 thing which is Files app or documentsui i get file app crashed when trying to gain permissions to my sd card this can be reproduced by for example using a gallery app and trying to delete a file on the sd card or moving a file from the sd car as well

It can also be reproduced in foxit pdf reader when i try to move a pdf file it asks for SD card permissions when i press okay it seems to open the files app very briefly and then crashes with files app crashed

I am trying to figure out which service i have removed that may be responsible for this file app crashing when i use file manager / my files etc they all open and run no issue it just seems to be an issue when an app requests permissions to access to sd card and asks me to locate the sd folder (triggering the file app to open then crash instantly)

Someone mentioned some galaxy services may be involved is there any way to find out without having to do a factory reset ?

----- SYSTEM LOG (logcat -v threadtime -v printable -v uid -d *:v) ------
--------- beginning of crash
11-30 19:23:15.348 10067 22299 22299 E AndroidRuntime: FATAL EXCEPTION: main
11-30 19:23:15.348 10067 22299 22299 E AndroidRuntime: Process: com.android.documentsui, PID: 22299
11-30 19:23:15.348 10067 22299 22299 E AndroidRuntime: java.lang.RuntimeException: Default Root URI is not a valid root URI.
11-30 19:23:15.348 10067 22299 22299 E AndroidRuntime: at com.android.documentsui.base.Shared.getDefaultRootUri(Shared.java:240)
11-30 19:23:15.348 10067 22299 22299 E AndroidRuntime: at com.android.documentsui.AbstractActionHandler.loadHomeDir(AbstractActionHandler.java:551)
11-30 19:23:15.348 10067 22299 22299 E AndroidRuntime: at com.android.documentsui.picker.ActionHandler.loadDefaultLocation(ActionHandler.java:228)
11-30 19:23:15.348 10067 22299 22299 E AndroidRuntime: at com.android.documentsui.picker.ActionHandler.onLastAccessedStackLoaded(ActionHandler.java:188)
11-30 19:23:15.348 10067 22299 22299 E AndroidRuntime: at com.android.documentsui.picker.ActionHandler.lambda$x4xchQbIp2JBw1iYgZ_QB_1wH30(Unknown Source:0)
11-30 19:23:15.348 10067 22299 22299 E AndroidRuntime: at com.android.documentsui.picker.-$$Lambda$ActionHandler$x4xchQbIp2JBw1iYgZ_QB_1wH30.accept(Unknown Source:4)
11-30 19:23:15.348 10067 22299 22299 E AndroidRuntime: at com.android.documentsui.picker.LoadLastAccessedStackTask.finish(LoadLastAccessedStackTask.java:65)
11-30 19:23:15.348 10067 22299 22299 E AndroidRuntime: at com.android.documentsui.picker.LoadLastAccessedStackTask.finish(LoadLastAccessedStackTask.java:37)
11-30 19:23:15.348 10067 22299 22299 E AndroidRuntime: at com.android.documentsui.base.CheckedTask.onPostExecute(CheckedTask.java:73)
11-30 19:23:15.348 10067 22299 22299 E AndroidRuntime: at android.os.AsyncTask.finish(AsyncTask.java:755)
11-30 19:23:15.348 10067 22299 22299 E AndroidRuntime: at android.os.AsyncTask.access$900(AsyncTask.java:192)
11-30 19:23:15.348 10067 22299 22299 E AndroidRuntime: at android.os.AsyncTask$InternalHandler.handleMessage(AsyncTask.java:772)
11-30 19:23:15.348 10067 22299 22299 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:107)
11-30 19:23:15.348 10067 22299 22299 E AndroidRuntime: at android.os.Looper.loop(Looper.java:237)
11-30 19:23:15.348 10067 22299 22299 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:8167)
11-30 19:23:15.348 10067 22299 22299 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
11-30 19:23:15.348 10067 22299 22299 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:496)
11-30 19:23:15.348 10067 22299 22299 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1100)
12-01 03:48:10.526 1000 955 1041 E AndroidRuntime: [email protected]*** FATAL EXCEPTION IN SYSTEM PROCESS: android.ui
12-01 03:48:10.526 1000 955 1041 E AndroidRuntime: java.lang.NullPointerException: NPE by silent reset
12-01 03:48:10.526 1000 955 1041 E AndroidRuntime: at com.android.server.power.PowerManagerService$11.run(PowerManagerService.java:5704)
12-01 03:48:10.526 1000 955 1041 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:883)
12-01 03:48:10.526 1000 955 1041 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:100)
12-01 03:48:10.526 1000 955 1041 E AndroidRuntime: at android.os.Looper.loop(Looper.java:237)
12-01 03:48:10.526 1000 955 1041 E AndroidRuntime: at android.os.HandlerThread.run(HandlerThread.java:67)
12-01 03:48:10.526 1000 955 1041 E AndroidRuntime: at com.android.server.ServiceThread.run(ServiceThread.java:44)
12-01 03:48:10.526 1000 955 1041 E AndroidRuntime: at com.android.server.UiThread.run(UiThread.java:43)
12-01 03:48:15.003 10089 1538 32047 E AndroidRuntime: FATAL EXCEPTION: [com.google.android.gms.chimera.PersistentIntentOperationService$ChimeraService-Executor] idle
12-01 03:48:15.003 10089 1538 32047 E AndroidRuntime: Process: com.google.android.gms.persistent, PID: 1538
12-01 03:48:15.003 10089 1538 32047 E AndroidRuntime: DeadSystemException: The system died; earlier logs will point to the root cause
12-01 03:48:15.006 1000 29906 29906 E AndroidRuntime: FATAL EXCEPTION: main
12-01 03:48:15.006 1000 29906 29906 E AndroidRuntime: Process: com.samsung.android.lool, PID: 29906
12-01 03:48:15.006 1000 29906 29906 E AndroidRuntime: DeadSystemException: The system died; earlier logs will point to the root cause
12-01 11:47:52.623 10067 24336 24336 E AndroidRuntime: FATAL EXCEPTION: main
12-01 11:47:52.623 10067 24336 24336 E AndroidRuntime: Process: com.android.documentsui, PID: 24336
12-01 11:47:52.623 10067 24336 24336 E AndroidRuntime: java.lang.RuntimeException: Default Root URI is not a valid root URI.
12-01 11:47:52.623 10067 24336 24336 E AndroidRuntime: at com.android.documentsui.base.Shared.getDefaultRootUri(Shared.java:240)
12-01 11:47:52.623 10067 24336 24336 E AndroidRuntime: at com.android.documentsui.AbstractActionHandler.loadHomeDir(AbstractActionHandler.java:551)
12-01 11:47:52.623 10067 24336 24336 E AndroidRuntime: at com.android.documentsui.picker.ActionHandler.loadDefaultLocation(ActionHandler.java:228)
12-01 11:47:52.623 10067 24336 24336 E AndroidRuntime: at com.android.documentsui.picker.ActionHandler.onLastAccessedStackLoaded(ActionHandler.java:188)
12-01 11:47:52.623 10067 24336 24336 E AndroidRuntime: at com.android.documentsui.picker.ActionHandler.lambda$x4xchQbIp2JBw1iYgZ_QB_1wH30(Unknown Source:0)
12-01 11:47:52.623 10067 24336 24336 E AndroidRuntime: at com.android.documentsui.picker.-$$Lambda$ActionHandler$x4xchQbIp2JBw1iYgZ_QB_1wH30.accept(Unknown Source:4)
12-01 11:47:52.623 10067 24336 24336 E AndroidRuntime: at com.android.documentsui.picker.LoadLastAccessedStackTask.finish(LoadLastAccessedStackTask.java:65)
12-01 11:47:52.623 10067 24336 24336 E AndroidRuntime: at com.android.documentsui.picker.LoadLastAccessedStackTask.finish(LoadLastAccessedStackTask.java:37)
12-01 11:47:52.623 10067 24336 24336 E AndroidRuntime: at com.android.documentsui.base.CheckedTask.onPostExecute(CheckedTask.java:73)
12-01 11:47:52.623 10067 24336 24336 E AndroidRuntime: at android.os.AsyncTask.finish(AsyncTask.java:755)
12-01 11:47:52.623 10067 24336 24336 E AndroidRuntime: at android.os.AsyncTask.access$900(AsyncTask.java:192)
12-01 11:47:52.623 10067 24336 24336 E AndroidRuntime: at android.os.AsyncTask$InternalHandler.handleMessage(AsyncTask.java:772)
12-01 11:47:52.623 10067 24336 24336 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:107)
12-01 11:47:52.623 10067 24336 24336 E AndroidRuntime: at android.os.Looper.loop(Looper.java:237)
12-01 11:47:52.623 10067 24336 24336 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:8167)
12-01 11:47:52.623 10067 24336 24336 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
12-01 11:47:52.623 10067 24336 24336 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:496)
12-01 11:47:52.623 10067 24336 24336 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1100)
12-01 11:48:09.303 10067 25206 25206 E AndroidRuntime: FATAL EXCEPTION: main
12-01 11:48:09.303 10067 25206 25206 E AndroidRuntime: Process: com.android.documentsui, PID: 25206
12-01 11:48:09.303 10067 25206 25206 E AndroidRuntime: java.lang.RuntimeException: Default Root URI is not a valid root URI.
12-01 11:48:09.303 10067 25206 25206 E AndroidRuntime: at com.android.documentsui.base.Shared.getDefaultRootUri(Shared.java:240)
12-01 11:48:09.303 10067 25206 25206 E AndroidRuntime: at com.android.documentsui.AbstractActionHandler.loadHomeDir(AbstractActionHandler.java:551)
12-01 11:48:09.303 10067 25206 25206 E AndroidRuntime: at com.android.documentsui.picker.ActionHandler.loadDefaultLocation(ActionHandler.java:228)
12-01 11:48:09.303 10067 25206 25206 E AndroidRuntime: at com.android.documentsui.picker.ActionHandler.onLastAccessedStackLoaded(ActionHandler.java:188)
12-01 11:48:09.303 10067 25206 25206 E AndroidRuntime: at com.android.documentsui.picker.ActionHandler.lambda$x4xchQbIp2JBw1iYgZ_QB_1wH30(Unknown Source:0)
12-01 11:48:09.303 10067 25206 25206 E AndroidRuntime: at com.android.documentsui.picker.-$$Lambda$ActionHandler$x4xchQbIp2JBw1iYgZ_QB_1wH30.accept(Unknown Source:4)
12-01 11:48:09.303 10067 25206 25206 E AndroidRuntime: at com.android.documentsui.picker.LoadLastAccessedStackTask.finish(LoadLastAccessedStackTask.java:65)
12-01 11:48:09.303 10067 25206 25206 E AndroidRuntime: at com.android.documentsui.picker.LoadLastAccessedStackTask.finish(LoadLastAccessedStackTask.java:37)
12-01 11:48:09.303 10067 25206 25206 E AndroidRuntime: at com.android.documentsui.base.CheckedTask.onPostExecute(CheckedTask.java:73)
12-01 11:48:09.303 10067 25206 25206 E AndroidRuntime: at android.os.AsyncTask.finish(AsyncTask.java:755)
12-01 11:48:09.303 10067 25206 25206 E AndroidRuntime: at android.os.AsyncTask.access$900(AsyncTask.java:192)
12-01 11:48:09.303 10067 25206 25206 E AndroidRuntime: at android.os.AsyncTask$InternalHandler.handleMessage(AsyncTask.java:772)
12-01 11:48:09.303 10067 25206 25206 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:107)
12-01 11:48:09.303 10067 25206 25206 E AndroidRuntime: at android.os.Looper.loop(Looper.java:237)
12-01 11:48:09.303 10067 25206 25206 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:8167)
12-01 11:48:09.303 10067 25206 25206 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
12-01 11:48:09.303 10067 25206 25206 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:496)
12-01 11:48:09.303 10067 25206 25206 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1100)
12-01 11:48:29.971 10067 25427 25427 E AndroidRuntime: FATAL EXCEPTION: main
12-01 11:48:29.971 10067 25427 25427 E AndroidRuntime: Process: com.android.documentsui, PID: 25427
12-01 11:48:29.971 10067 25427 25427 E AndroidRuntime: java.lang.RuntimeException: Default Root URI is not a valid root URI.
12-01 11:48:29.971 10067 25427 25427 E AndroidRuntime: at com.android.documentsui.base.Shared.getDefaultRootUri(Shared.java:240)
12-01 11:48:29.971 10067 25427 25427 E AndroidRuntime: at com.android.documentsui.AbstractActionHandler.loadHomeDir(AbstractActionHandler.java:551)
12-01 11:48:29.971 10067 25427 25427 E AndroidRuntime: at com.android.documentsui.picker.ActionHandler.loadDefaultLocation(ActionHandler.java:228)
12-01 11:48:29.971 10067 25427 25427 E AndroidRuntime: at com.android.documentsui.picker.ActionHandler.onLastAccessedStackLoaded(ActionHandler.java:188)
12-01 11:48:29.971 10067 25427 25427 E AndroidRuntime: at com.android.documentsui.picker.ActionHandler.lambda$x4xchQbIp2JBw1iYgZ_QB_1wH30(Unknown Source:0)
12-01 11:48:29.971 10067 25427 25427 E AndroidRuntime: at com.android.documentsui.picker.-$$Lambda$ActionHandler$x4xchQbIp2JBw1iYgZ_QB_1wH30.accept(Unknown Source:4)
12-01 11:48:29.971 10067 25427 25427 E AndroidRuntime: at com.android.documentsui.picker.LoadLastAccessedStackTask.finish(LoadLastAccessedStackTask.java:65)
12-01 11:48:29.971 10067 25427 25427 E AndroidRuntime: at com.android.documentsui.picker.LoadLastAccessedStackTask.finish(LoadLastAccessedStackTask.java:37)
12-01 11:48:29.971 10067 25427 25427 E AndroidRuntime: at com.android.documentsui.base.CheckedTask.onPostExecute(CheckedTask.java:73)
12-01 11:48:29.971 10067 25427 25427 E AndroidRuntime: at android.os.AsyncTask.finish(AsyncTask.java:755)
12-01 11:48:29.971 10067 25427 25427 E AndroidRuntime: at android.os.AsyncTask.access$900(AsyncTask.java:192)
12-01 11:48:29.971 10067 25427 25427 E AndroidRuntime: at android.os.AsyncTask$InternalHandler.handleMessage(AsyncTask.java:772)
12-01 11:48:29.971 10067 25427 25427 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:107)
12-01 11:48:29.971 10067 25427 25427 E AndroidRuntime: at android.os.Looper.loop(Looper.java:237)
12-01 11:48:29.971 10067 25427 25427 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:8167)
12-01 11:48:29.971 10067 25427 25427 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
12-01 11:48:29.971 10067 25427 25427 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:496)
12-01 11:48:29.971 10067 25427 25427 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1100)




12-01 12:11:21.465 10131 28963 29008 I DIAGMON_SDK[605026]: SetConfiguration
12-01 12:11:21.474 10131 28963 29008 I DIAGMON_SDK[605026]: generated SR object
12-01 12:11:21.474 10131 28963 29008 D DIAGMON_SDK[605026]: Status is chaged to CustomLogging
12-01 12:11:21.477 10131 28963 29008 D DIAGMON_SDK[605026]: Diagmon Logger Init
12-01 12:11:21.477 10131 28963 29008 D DIAGMON_SDK[605026]: MAIN_LOG_PATH : /data/user/0/com.sec.android.app.myfiles/exception/diagmon_main.log
12-01 12:11:21.477 10131 28963 29008 D DIAGMON_SDK[605026]: CRASH_LOG_PATH : /data/user/0/com.sec.android.app.myfiles/exception/diagmon.log
12-01 12:11:21.477 10131 28963 29008 D DIAGMON_SDK[605026]: EVENT_LOG_PATH : /data/user/0/com.sec.android.app.myfiles/exception/diagmon_event.log
12-01 12:11:21.478 10131 28963 29008 D DIAGMON_SDK[605026]: THREAD_STACK_LOG_PATH : /data/user/0/com.sec.android.app.myfiles/exception/diagmon_thread.log
12-01 12:11:21.478 10131 28963 29008 D DIAGMON_SDK[605026]: MEMORY_LOG_PATH : /data/user/0/com.sec.android.app.myfiles/exception/diagmon_memory.log
12-01 12:11:21.478 10131 28963 29008 D DIAGMON_SDK[605026]: STORAGE_LOG_PATH : /data/user/0/com.sec.android.app.myfiles/exception/diagmon_storage.log
12-01 12:11:21.492 10131 28963 28963 I MyFiles : [0004/PreferenceUtils ] set - avail_app_update false
12-01 12:11:21.494 10131 28963 29010 D DIAGMON_SDK[605026]: Status is chaged to CustomLogging
12-01 12:11:21.495 10131 28963 28988 I MyFiles : [0005/AccountDatabase ] onCreate() ] Start AccountDatabase initialization
12-01 12:11:21.496 10131 28963 28988 W SQLiteLog: (28) failed to open "/data/user/0/com.sec.android.app.myfiles/databases/MyFilesSEP10.db" with flag (131072) and mode_t (0) due to error (2)
12-01 12:11:21.496 10131 28963 28988 E SQLiteLog: (14) cannot open file at line 37769 of [68b898381a]
12-01 12:11:21.496 10131 28963 28988 E SQLiteLog: (14) os_unix.c:37769: (2) open(/data/user/0/com.sec.android.app.myfiles/databases/MyFilesSEP10.db) -
12-01 12:11:21.496 10131 28963 28988 E SQLiteLog: (1) Process oid.app.myfiles : Pid (28963) Uid (10131) Euid (10131) Gid (10131) Egid (10131)
12-01 12:11:21.496 10131 28963 28988 E SQLiteLog: (1) osStat failed "/data/user/0/com.sec.android.app.myfiles/databases/MyFilesSEP10.db" due to error (2)
12-01 12:11:21.496 10131 28963 28988 E SQLiteLog: (1) Stat of /data/user/0/com.sec.android.app.myfiles/databases : st_mode(40771) st_uid(10131) st_gid(10131) st_ino(2031708)
12-01 12:11:21.496 10131 28963 28988 E SQLiteLog: (1) Stat of /data/user/0/com.sec.android.app.myfiles : st_mode(40700) st_uid(10131) st_gid(10131) st_ino(1966595)
12-01 12:11:21.496 10131 28963 28988 E SQLiteLog: (1) Stat of /data/user/0 : st_mode(40771) st_uid(1000) st_gid(1000) st_ino(1966081)
12-01 12:11:21.496 10131 28963 28988 E SQLiteLog: (1) Stat of /data/user : st_mode(40711) st_uid(1000) st_gid(1000) st_ino(851969)
12-01 12:11:21.496 10131 28963 28988 E SQLiteLog: (1) Stat of /data : st_mode(40771) st_uid(1000) st_gid(1000) st_ino(2)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: Failed to open database '/data/user/0/com.sec.android.app.myfiles/databases/MyFilesSEP10.db'.
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: android.database.sqlite.SQLiteCantOpenDatabaseException: unknown error (code 1294 SQLITE_CANTOPEN_ENOENT[1294]): Could not open database
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at android.database.sqlite.SQLiteConnection.nativeOpen(Native Method)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java:300)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java:218)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at android.database.sqlite.SQLiteConnectionPool.openConnectionLocked(SQLiteConnectionPool.java:737)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at android.database.sqlite.SQLiteConnectionPool.open(SQLiteConnectionPool.java:284)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at android.database.sqlite.SQLiteConnectionPool.open(SQLiteConnectionPool.java:251)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at android.database.sqlite.SQLiteDatabase.openInner(SQLiteDatabase.java:1394)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at android.database.sqlite.SQLiteDatabase.open(SQLiteDatabase.java:1339)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:1001)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:940)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at com.sec.android.app.myfiles.external.database.AccountDatabase$1.onCreate(AccountDatabase.java:73)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at com.sec.android.app.myfiles.external.database.AccountDatabase_Impl$1.onCreate(AccountDatabase_Impl.java:47)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at androidx.room.RoomOpenHelper.onCreate(RoomOpenHelper.java:75)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at androidx.sqlite.db.framework.FrameworkSQLiteOpenHelper$OpenHelper.onCreate(FrameworkSQLiteOpenHelper.java:127)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at android.database.sqlite.SQLiteOpenHelper.getDatabaseLocked(SQLiteOpenHelper.java:486)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at android.database.sqlite.SQLiteOpenHelper.getWritableDatabase(SQLiteOpenHelper.java:391)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at androidx.sqlite.db.framework.FrameworkSQLiteOpenHelper$OpenHelper.getWritableSupportDatabase(FrameworkSQLiteOpenHelper.java:96)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at androidx.sqlite.db.framework.FrameworkSQLiteOpenHelper.getWritableDatabase(FrameworkSQLiteOpenHelper.java:54)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at androidx.room.RoomDatabase.query(RoomDatabase.java:238)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at com.sec.android.app.myfiles.external.database.dao.CloudAccountDao_Impl.getAccountInfo(CloudAccountDao_Impl.java:137)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at com.sec.android.app.myfiles.external.database.repository.CloudAccountRepository.get(CloudAccountRepository.java:98)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at com.sec.android.app.myfiles.presenter.account.CloudAccountManager.retrieveAccountInfo(CloudAccountManager.java:498)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at com.sec.android.app.myfiles.presenter.account.CloudAccountManager.updateLoginStatus(CloudAccountManager.java:531)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at com.sec.android.app.myfiles.presenter.account.CloudAccountManager.<init>(CloudAccountManager.java:65)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at com.sec.android.app.myfiles.presenter.account.CloudAccountManager.<init>(CloudAccountManager.java:42)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at com.sec.android.app.myfiles.presenter.account.CloudAccountManager$CloudAccountManagerHolder.<clinit>(CloudAccountManager.java:46)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at com.sec.android.app.myfiles.presenter.account.CloudAccountManager$CloudAccountManagerHolder.access$100(CloudAccountManager.java:45)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at com.sec.android.app.myfiles.presenter.account.CloudAccountManager.getInstance(CloudAccountManager.java:94)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at com.sec.android.app.myfiles.external.database.repository.AbsCloudRepository.addAccountRemovedListener(AbsCloudRepository.java:162)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at com.sec.android.app.myfiles.external.database.repository.SamsungDriveFileInfoRepository.<init>(SamsungDriveFileInfoRepository.java:64)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at com.sec.android.app.myfiles.external.database.repository.SamsungDriveFileInfoRepository.getInstance(SamsungDriveFileInfoRepository.java:50)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at com.sec.android.app.myfiles.external.injection.RepositoryFactory.getCloudRepositorySparseArray(RepositoryFactory.java:173)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at com.sec.android.app.myfiles.external.injection.RepositoryFactory.provideRepositoryAsToPageType(RepositoryFactory.java:138)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at com.sec.android.app.myfiles.external.feature.devicesearch.MyFilesIndexModule$MyFilesIndexModuleSearchable.<init>(MyFilesIndexModule.java:82)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at com.sec.android.app.myfiles.external.feature.devicesearch.MyFilesIndexModule.<init>(MyFilesIndexModule.java:56)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at com.sec.android.app.myfiles.external.providers.DeviceSearchIndexProvider.getIndexModule(DeviceSearchIndexProvider.java:33)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at com.sec.android.app.myfiles.external.providers.DeviceSearchIndexProvider.call(DeviceSearchIndexProvider.java:76)
 
Last edited:

not.not

New member
Dec 1, 2021
1
0
Hello! Can I enable OTA on my redmagic 6r? Since I unpacked my phone it doesn't work. Thank you
 

Attachments

  • Screenshot_20211201-083539.png
    Screenshot_20211201-083539.png
    117.4 KB · Views: 7

SubwayChamp

Senior Member
Aug 6, 2016
3,403
3
1,443
I have a note 9 running Android 10 on One UI 2.5

I debloated a lot of stuff on the phone everything works fine except 1 thing which is Files app or documentsui i get file app crashed when trying to gain permissions to my sd card this can be reproduced by for example using a gallery app and trying to delete a file on the sd card or moving a file from the sd car as well

It can also be reproduced in foxit pdf reader when i try to move a pdf file it asks for SD card permissions when i press okay it seems to open the files app very briefly and then crashes with files app crashed

I am trying to figure out which service i have removed that may be responsible for this file app crashing when i use file manager / my files etc they all open and run no issue it just seems to be an issue when an app requests permissions to access to sd card and asks me to locate the sd folder (triggering the file app to open then crash instantly)

Someone mentioned some galaxy services may be involved is there any way to find out without having to do a factory reset ?

----- SYSTEM LOG (logcat -v threadtime -v printable -v uid -d *:v) ------
--------- beginning of crash
11-30 19:23:15.348 10067 22299 22299 E AndroidRuntime: FATAL EXCEPTION: main
11-30 19:23:15.348 10067 22299 22299 E AndroidRuntime: Process: com.android.documentsui, PID: 22299
11-30 19:23:15.348 10067 22299 22299 E AndroidRuntime: java.lang.RuntimeException: Default Root URI is not a valid root URI.
11-30 19:23:15.348 10067 22299 22299 E AndroidRuntime: at com.android.documentsui.base.Shared.getDefaultRootUri(Shared.java:240)
11-30 19:23:15.348 10067 22299 22299 E AndroidRuntime: at com.android.documentsui.AbstractActionHandler.loadHomeDir(AbstractActionHandler.java:551)
11-30 19:23:15.348 10067 22299 22299 E AndroidRuntime: at com.android.documentsui.picker.ActionHandler.loadDefaultLocation(ActionHandler.java:228)
11-30 19:23:15.348 10067 22299 22299 E AndroidRuntime: at com.android.documentsui.picker.ActionHandler.onLastAccessedStackLoaded(ActionHandler.java:188)
11-30 19:23:15.348 10067 22299 22299 E AndroidRuntime: at com.android.documentsui.picker.ActionHandler.lambda$x4xchQbIp2JBw1iYgZ_QB_1wH30(Unknown Source:0)
11-30 19:23:15.348 10067 22299 22299 E AndroidRuntime: at com.android.documentsui.picker.-$$Lambda$ActionHandler$x4xchQbIp2JBw1iYgZ_QB_1wH30.accept(Unknown Source:4)
11-30 19:23:15.348 10067 22299 22299 E AndroidRuntime: at com.android.documentsui.picker.LoadLastAccessedStackTask.finish(LoadLastAccessedStackTask.java:65)
11-30 19:23:15.348 10067 22299 22299 E AndroidRuntime: at com.android.documentsui.picker.LoadLastAccessedStackTask.finish(LoadLastAccessedStackTask.java:37)
11-30 19:23:15.348 10067 22299 22299 E AndroidRuntime: at com.android.documentsui.base.CheckedTask.onPostExecute(CheckedTask.java:73)
11-30 19:23:15.348 10067 22299 22299 E AndroidRuntime: at android.os.AsyncTask.finish(AsyncTask.java:755)
11-30 19:23:15.348 10067 22299 22299 E AndroidRuntime: at android.os.AsyncTask.access$900(AsyncTask.java:192)
11-30 19:23:15.348 10067 22299 22299 E AndroidRuntime: at android.os.AsyncTask$InternalHandler.handleMessage(AsyncTask.java:772)
11-30 19:23:15.348 10067 22299 22299 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:107)
11-30 19:23:15.348 10067 22299 22299 E AndroidRuntime: at android.os.Looper.loop(Looper.java:237)
11-30 19:23:15.348 10067 22299 22299 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:8167)
11-30 19:23:15.348 10067 22299 22299 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
11-30 19:23:15.348 10067 22299 22299 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:496)
11-30 19:23:15.348 10067 22299 22299 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1100)
12-01 03:48:10.526 1000 955 1041 E AndroidRuntime: [email protected]*** FATAL EXCEPTION IN SYSTEM PROCESS: android.ui
12-01 03:48:10.526 1000 955 1041 E AndroidRuntime: java.lang.NullPointerException: NPE by silent reset
12-01 03:48:10.526 1000 955 1041 E AndroidRuntime: at com.android.server.power.PowerManagerService$11.run(PowerManagerService.java:5704)
12-01 03:48:10.526 1000 955 1041 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:883)
12-01 03:48:10.526 1000 955 1041 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:100)
12-01 03:48:10.526 1000 955 1041 E AndroidRuntime: at android.os.Looper.loop(Looper.java:237)
12-01 03:48:10.526 1000 955 1041 E AndroidRuntime: at android.os.HandlerThread.run(HandlerThread.java:67)
12-01 03:48:10.526 1000 955 1041 E AndroidRuntime: at com.android.server.ServiceThread.run(ServiceThread.java:44)
12-01 03:48:10.526 1000 955 1041 E AndroidRuntime: at com.android.server.UiThread.run(UiThread.java:43)
12-01 03:48:15.003 10089 1538 32047 E AndroidRuntime: FATAL EXCEPTION: [com.google.android.gms.chimera.PersistentIntentOperationService$ChimeraService-Executor] idle
12-01 03:48:15.003 10089 1538 32047 E AndroidRuntime: Process: com.google.android.gms.persistent, PID: 1538
12-01 03:48:15.003 10089 1538 32047 E AndroidRuntime: DeadSystemException: The system died; earlier logs will point to the root cause
12-01 03:48:15.006 1000 29906 29906 E AndroidRuntime: FATAL EXCEPTION: main
12-01 03:48:15.006 1000 29906 29906 E AndroidRuntime: Process: com.samsung.android.lool, PID: 29906
12-01 03:48:15.006 1000 29906 29906 E AndroidRuntime: DeadSystemException: The system died; earlier logs will point to the root cause
12-01 11:47:52.623 10067 24336 24336 E AndroidRuntime: FATAL EXCEPTION: main
12-01 11:47:52.623 10067 24336 24336 E AndroidRuntime: Process: com.android.documentsui, PID: 24336
12-01 11:47:52.623 10067 24336 24336 E AndroidRuntime: java.lang.RuntimeException: Default Root URI is not a valid root URI.
12-01 11:47:52.623 10067 24336 24336 E AndroidRuntime: at com.android.documentsui.base.Shared.getDefaultRootUri(Shared.java:240)
12-01 11:47:52.623 10067 24336 24336 E AndroidRuntime: at com.android.documentsui.AbstractActionHandler.loadHomeDir(AbstractActionHandler.java:551)
12-01 11:47:52.623 10067 24336 24336 E AndroidRuntime: at com.android.documentsui.picker.ActionHandler.loadDefaultLocation(ActionHandler.java:228)
12-01 11:47:52.623 10067 24336 24336 E AndroidRuntime: at com.android.documentsui.picker.ActionHandler.onLastAccessedStackLoaded(ActionHandler.java:188)
12-01 11:47:52.623 10067 24336 24336 E AndroidRuntime: at com.android.documentsui.picker.ActionHandler.lambda$x4xchQbIp2JBw1iYgZ_QB_1wH30(Unknown Source:0)
12-01 11:47:52.623 10067 24336 24336 E AndroidRuntime: at com.android.documentsui.picker.-$$Lambda$ActionHandler$x4xchQbIp2JBw1iYgZ_QB_1wH30.accept(Unknown Source:4)
12-01 11:47:52.623 10067 24336 24336 E AndroidRuntime: at com.android.documentsui.picker.LoadLastAccessedStackTask.finish(LoadLastAccessedStackTask.java:65)
12-01 11:47:52.623 10067 24336 24336 E AndroidRuntime: at com.android.documentsui.picker.LoadLastAccessedStackTask.finish(LoadLastAccessedStackTask.java:37)
12-01 11:47:52.623 10067 24336 24336 E AndroidRuntime: at com.android.documentsui.base.CheckedTask.onPostExecute(CheckedTask.java:73)
12-01 11:47:52.623 10067 24336 24336 E AndroidRuntime: at android.os.AsyncTask.finish(AsyncTask.java:755)
12-01 11:47:52.623 10067 24336 24336 E AndroidRuntime: at android.os.AsyncTask.access$900(AsyncTask.java:192)
12-01 11:47:52.623 10067 24336 24336 E AndroidRuntime: at android.os.AsyncTask$InternalHandler.handleMessage(AsyncTask.java:772)
12-01 11:47:52.623 10067 24336 24336 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:107)
12-01 11:47:52.623 10067 24336 24336 E AndroidRuntime: at android.os.Looper.loop(Looper.java:237)
12-01 11:47:52.623 10067 24336 24336 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:8167)
12-01 11:47:52.623 10067 24336 24336 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
12-01 11:47:52.623 10067 24336 24336 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:496)
12-01 11:47:52.623 10067 24336 24336 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1100)
12-01 11:48:09.303 10067 25206 25206 E AndroidRuntime: FATAL EXCEPTION: main
12-01 11:48:09.303 10067 25206 25206 E AndroidRuntime: Process: com.android.documentsui, PID: 25206
12-01 11:48:09.303 10067 25206 25206 E AndroidRuntime: java.lang.RuntimeException: Default Root URI is not a valid root URI.
12-01 11:48:09.303 10067 25206 25206 E AndroidRuntime: at com.android.documentsui.base.Shared.getDefaultRootUri(Shared.java:240)
12-01 11:48:09.303 10067 25206 25206 E AndroidRuntime: at com.android.documentsui.AbstractActionHandler.loadHomeDir(AbstractActionHandler.java:551)
12-01 11:48:09.303 10067 25206 25206 E AndroidRuntime: at com.android.documentsui.picker.ActionHandler.loadDefaultLocation(ActionHandler.java:228)
12-01 11:48:09.303 10067 25206 25206 E AndroidRuntime: at com.android.documentsui.picker.ActionHandler.onLastAccessedStackLoaded(ActionHandler.java:188)
12-01 11:48:09.303 10067 25206 25206 E AndroidRuntime: at com.android.documentsui.picker.ActionHandler.lambda$x4xchQbIp2JBw1iYgZ_QB_1wH30(Unknown Source:0)
12-01 11:48:09.303 10067 25206 25206 E AndroidRuntime: at com.android.documentsui.picker.-$$Lambda$ActionHandler$x4xchQbIp2JBw1iYgZ_QB_1wH30.accept(Unknown Source:4)
12-01 11:48:09.303 10067 25206 25206 E AndroidRuntime: at com.android.documentsui.picker.LoadLastAccessedStackTask.finish(LoadLastAccessedStackTask.java:65)
12-01 11:48:09.303 10067 25206 25206 E AndroidRuntime: at com.android.documentsui.picker.LoadLastAccessedStackTask.finish(LoadLastAccessedStackTask.java:37)
12-01 11:48:09.303 10067 25206 25206 E AndroidRuntime: at com.android.documentsui.base.CheckedTask.onPostExecute(CheckedTask.java:73)
12-01 11:48:09.303 10067 25206 25206 E AndroidRuntime: at android.os.AsyncTask.finish(AsyncTask.java:755)
12-01 11:48:09.303 10067 25206 25206 E AndroidRuntime: at android.os.AsyncTask.access$900(AsyncTask.java:192)
12-01 11:48:09.303 10067 25206 25206 E AndroidRuntime: at android.os.AsyncTask$InternalHandler.handleMessage(AsyncTask.java:772)
12-01 11:48:09.303 10067 25206 25206 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:107)
12-01 11:48:09.303 10067 25206 25206 E AndroidRuntime: at android.os.Looper.loop(Looper.java:237)
12-01 11:48:09.303 10067 25206 25206 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:8167)
12-01 11:48:09.303 10067 25206 25206 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
12-01 11:48:09.303 10067 25206 25206 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:496)
12-01 11:48:09.303 10067 25206 25206 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1100)
12-01 11:48:29.971 10067 25427 25427 E AndroidRuntime: FATAL EXCEPTION: main
12-01 11:48:29.971 10067 25427 25427 E AndroidRuntime: Process: com.android.documentsui, PID: 25427
12-01 11:48:29.971 10067 25427 25427 E AndroidRuntime: java.lang.RuntimeException: Default Root URI is not a valid root URI.
12-01 11:48:29.971 10067 25427 25427 E AndroidRuntime: at com.android.documentsui.base.Shared.getDefaultRootUri(Shared.java:240)
12-01 11:48:29.971 10067 25427 25427 E AndroidRuntime: at com.android.documentsui.AbstractActionHandler.loadHomeDir(AbstractActionHandler.java:551)
12-01 11:48:29.971 10067 25427 25427 E AndroidRuntime: at com.android.documentsui.picker.ActionHandler.loadDefaultLocation(ActionHandler.java:228)
12-01 11:48:29.971 10067 25427 25427 E AndroidRuntime: at com.android.documentsui.picker.ActionHandler.onLastAccessedStackLoaded(ActionHandler.java:188)
12-01 11:48:29.971 10067 25427 25427 E AndroidRuntime: at com.android.documentsui.picker.ActionHandler.lambda$x4xchQbIp2JBw1iYgZ_QB_1wH30(Unknown Source:0)
12-01 11:48:29.971 10067 25427 25427 E AndroidRuntime: at com.android.documentsui.picker.-$$Lambda$ActionHandler$x4xchQbIp2JBw1iYgZ_QB_1wH30.accept(Unknown Source:4)
12-01 11:48:29.971 10067 25427 25427 E AndroidRuntime: at com.android.documentsui.picker.LoadLastAccessedStackTask.finish(LoadLastAccessedStackTask.java:65)
12-01 11:48:29.971 10067 25427 25427 E AndroidRuntime: at com.android.documentsui.picker.LoadLastAccessedStackTask.finish(LoadLastAccessedStackTask.java:37)
12-01 11:48:29.971 10067 25427 25427 E AndroidRuntime: at com.android.documentsui.base.CheckedTask.onPostExecute(CheckedTask.java:73)
12-01 11:48:29.971 10067 25427 25427 E AndroidRuntime: at android.os.AsyncTask.finish(AsyncTask.java:755)
12-01 11:48:29.971 10067 25427 25427 E AndroidRuntime: at android.os.AsyncTask.access$900(AsyncTask.java:192)
12-01 11:48:29.971 10067 25427 25427 E AndroidRuntime: at android.os.AsyncTask$InternalHandler.handleMessage(AsyncTask.java:772)
12-01 11:48:29.971 10067 25427 25427 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:107)
12-01 11:48:29.971 10067 25427 25427 E AndroidRuntime: at android.os.Looper.loop(Looper.java:237)
12-01 11:48:29.971 10067 25427 25427 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:8167)
12-01 11:48:29.971 10067 25427 25427 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
12-01 11:48:29.971 10067 25427 25427 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:496)
12-01 11:48:29.971 10067 25427 25427 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1100)




12-01 12:11:21.465 10131 28963 29008 I DIAGMON_SDK[605026]: SetConfiguration
12-01 12:11:21.474 10131 28963 29008 I DIAGMON_SDK[605026]: generated SR object
12-01 12:11:21.474 10131 28963 29008 D DIAGMON_SDK[605026]: Status is chaged to CustomLogging
12-01 12:11:21.477 10131 28963 29008 D DIAGMON_SDK[605026]: Diagmon Logger Init
12-01 12:11:21.477 10131 28963 29008 D DIAGMON_SDK[605026]: MAIN_LOG_PATH : /data/user/0/com.sec.android.app.myfiles/exception/diagmon_main.log
12-01 12:11:21.477 10131 28963 29008 D DIAGMON_SDK[605026]: CRASH_LOG_PATH : /data/user/0/com.sec.android.app.myfiles/exception/diagmon.log
12-01 12:11:21.477 10131 28963 29008 D DIAGMON_SDK[605026]: EVENT_LOG_PATH : /data/user/0/com.sec.android.app.myfiles/exception/diagmon_event.log
12-01 12:11:21.478 10131 28963 29008 D DIAGMON_SDK[605026]: THREAD_STACK_LOG_PATH : /data/user/0/com.sec.android.app.myfiles/exception/diagmon_thread.log
12-01 12:11:21.478 10131 28963 29008 D DIAGMON_SDK[605026]: MEMORY_LOG_PATH : /data/user/0/com.sec.android.app.myfiles/exception/diagmon_memory.log
12-01 12:11:21.478 10131 28963 29008 D DIAGMON_SDK[605026]: STORAGE_LOG_PATH : /data/user/0/com.sec.android.app.myfiles/exception/diagmon_storage.log
12-01 12:11:21.492 10131 28963 28963 I MyFiles : [0004/PreferenceUtils ] set - avail_app_update false
12-01 12:11:21.494 10131 28963 29010 D DIAGMON_SDK[605026]: Status is chaged to CustomLogging
12-01 12:11:21.495 10131 28963 28988 I MyFiles : [0005/AccountDatabase ] onCreate() ] Start AccountDatabase initialization
12-01 12:11:21.496 10131 28963 28988 W SQLiteLog: (28) failed to open "/data/user/0/com.sec.android.app.myfiles/databases/MyFilesSEP10.db" with flag (131072) and mode_t (0) due to error (2)
12-01 12:11:21.496 10131 28963 28988 E SQLiteLog: (14) cannot open file at line 37769 of [68b898381a]
12-01 12:11:21.496 10131 28963 28988 E SQLiteLog: (14) os_unix.c:37769: (2) open(/data/user/0/com.sec.android.app.myfiles/databases/MyFilesSEP10.db) -
12-01 12:11:21.496 10131 28963 28988 E SQLiteLog: (1) Process oid.app.myfiles : Pid (28963) Uid (10131) Euid (10131) Gid (10131) Egid (10131)
12-01 12:11:21.496 10131 28963 28988 E SQLiteLog: (1) osStat failed "/data/user/0/com.sec.android.app.myfiles/databases/MyFilesSEP10.db" due to error (2)
12-01 12:11:21.496 10131 28963 28988 E SQLiteLog: (1) Stat of /data/user/0/com.sec.android.app.myfiles/databases : st_mode(40771) st_uid(10131) st_gid(10131) st_ino(2031708)
12-01 12:11:21.496 10131 28963 28988 E SQLiteLog: (1) Stat of /data/user/0/com.sec.android.app.myfiles : st_mode(40700) st_uid(10131) st_gid(10131) st_ino(1966595)
12-01 12:11:21.496 10131 28963 28988 E SQLiteLog: (1) Stat of /data/user/0 : st_mode(40771) st_uid(1000) st_gid(1000) st_ino(1966081)
12-01 12:11:21.496 10131 28963 28988 E SQLiteLog: (1) Stat of /data/user : st_mode(40711) st_uid(1000) st_gid(1000) st_ino(851969)
12-01 12:11:21.496 10131 28963 28988 E SQLiteLog: (1) Stat of /data : st_mode(40771) st_uid(1000) st_gid(1000) st_ino(2)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: Failed to open database '/data/user/0/com.sec.android.app.myfiles/databases/MyFilesSEP10.db'.
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: android.database.sqlite.SQLiteCantOpenDatabaseException: unknown error (code 1294 SQLITE_CANTOPEN_ENOENT[1294]): Could not open database
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at android.database.sqlite.SQLiteConnection.nativeOpen(Native Method)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java:300)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java:218)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at android.database.sqlite.SQLiteConnectionPool.openConnectionLocked(SQLiteConnectionPool.java:737)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at android.database.sqlite.SQLiteConnectionPool.open(SQLiteConnectionPool.java:284)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at android.database.sqlite.SQLiteConnectionPool.open(SQLiteConnectionPool.java:251)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at android.database.sqlite.SQLiteDatabase.openInner(SQLiteDatabase.java:1394)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at android.database.sqlite.SQLiteDatabase.open(SQLiteDatabase.java:1339)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:1001)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:940)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at com.sec.android.app.myfiles.external.database.AccountDatabase$1.onCreate(AccountDatabase.java:73)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at com.sec.android.app.myfiles.external.database.AccountDatabase_Impl$1.onCreate(AccountDatabase_Impl.java:47)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at androidx.room.RoomOpenHelper.onCreate(RoomOpenHelper.java:75)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at androidx.sqlite.db.framework.FrameworkSQLiteOpenHelper$OpenHelper.onCreate(FrameworkSQLiteOpenHelper.java:127)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at android.database.sqlite.SQLiteOpenHelper.getDatabaseLocked(SQLiteOpenHelper.java:486)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at android.database.sqlite.SQLiteOpenHelper.getWritableDatabase(SQLiteOpenHelper.java:391)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at androidx.sqlite.db.framework.FrameworkSQLiteOpenHelper$OpenHelper.getWritableSupportDatabase(FrameworkSQLiteOpenHelper.java:96)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at androidx.sqlite.db.framework.FrameworkSQLiteOpenHelper.getWritableDatabase(FrameworkSQLiteOpenHelper.java:54)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at androidx.room.RoomDatabase.query(RoomDatabase.java:238)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at com.sec.android.app.myfiles.external.database.dao.CloudAccountDao_Impl.getAccountInfo(CloudAccountDao_Impl.java:137)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at com.sec.android.app.myfiles.external.database.repository.CloudAccountRepository.get(CloudAccountRepository.java:98)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at com.sec.android.app.myfiles.presenter.account.CloudAccountManager.retrieveAccountInfo(CloudAccountManager.java:498)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at com.sec.android.app.myfiles.presenter.account.CloudAccountManager.updateLoginStatus(CloudAccountManager.java:531)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at com.sec.android.app.myfiles.presenter.account.CloudAccountManager.<init>(CloudAccountManager.java:65)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at com.sec.android.app.myfiles.presenter.account.CloudAccountManager.<init>(CloudAccountManager.java:42)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at com.sec.android.app.myfiles.presenter.account.CloudAccountManager$CloudAccountManagerHolder.<clinit>(CloudAccountManager.java:46)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at com.sec.android.app.myfiles.presenter.account.CloudAccountManager$CloudAccountManagerHolder.access$100(CloudAccountManager.java:45)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at com.sec.android.app.myfiles.presenter.account.CloudAccountManager.getInstance(CloudAccountManager.java:94)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at com.sec.android.app.myfiles.external.database.repository.AbsCloudRepository.addAccountRemovedListener(AbsCloudRepository.java:162)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at com.sec.android.app.myfiles.external.database.repository.SamsungDriveFileInfoRepository.<init>(SamsungDriveFileInfoRepository.java:64)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at com.sec.android.app.myfiles.external.database.repository.SamsungDriveFileInfoRepository.getInstance(SamsungDriveFileInfoRepository.java:50)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at com.sec.android.app.myfiles.external.injection.RepositoryFactory.getCloudRepositorySparseArray(RepositoryFactory.java:173)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at com.sec.android.app.myfiles.external.injection.RepositoryFactory.provideRepositoryAsToPageType(RepositoryFactory.java:138)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at com.sec.android.app.myfiles.external.feature.devicesearch.MyFilesIndexModule$MyFilesIndexModuleSearchable.<init>(MyFilesIndexModule.java:82)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at com.sec.android.app.myfiles.external.feature.devicesearch.MyFilesIndexModule.<init>(MyFilesIndexModule.java:56)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at com.sec.android.app.myfiles.external.providers.DeviceSearchIndexProvider.getIndexModule(DeviceSearchIndexProvider.java:33)
12-01 12:11:21.514 10131 28963 28988 E SQLiteDatabase: at com.sec.android.app.myfiles.external.providers.DeviceSearchIndexProvider.call(DeviceSearchIndexProvider.java:76)
The issue seems to be related to Files (DocumentsUI) from Google, this is the app that manage the permissions to RW to external media. Clear all from the settings of the app and also clear from the settings of My Files, Samsung. As an alternative way, you can perform at least an operation like this directly through Files from Google, tap on allow to write over external SD card once, and then will stick this way for any file explorer app.
 
  • Like
Reactions: Vitale87

harsha7sai

Senior Member
Feb 10, 2016
318
35
Guntur
I am trying to reduce my smartphone addiction
is there any possible way I can my setup so that i can use only specific apps .
i tried stay focused app but even on strict mode i some how able to uninstall the app and use social apps
my question is if i install just the from without gapps can have only phone calls?
 

SubwayChamp

Senior Member
Aug 6, 2016
3,403
3
1,443
I am trying to reduce my smartphone addiction
is there any possible way I can my setup so that i can use only specific apps .
i tried stay focused app but even on strict mode i some how able to uninstall the app and use social apps
my question is if i install just the from without gapps can have only phone calls?
You can get rid of the apps as far from you want.
 

The Invizible

Member
Feb 28, 2017
29
2
Hello
I have the Samsung galaxy tab 8.9 sch-739 this is the china model and I don't think it was sold anywhere else in the world because I didn't find any mention of this model in xda. this tablet is as good as dead because Samsung didn't update it to android ice cream sandwich. the last available update for this model is android 3.2.
I've tried to revive it by flashing multiples gt-pt7300 custom ROMs such as cm 11 and asop nougat " same tablet but from different region". these ROMs worked perfectly for the china model except for the sound. I can't for the life of me understand why the sound didn't work. I've looked everywhere from xda to Chinese forums and did a ton of research but to no avail.
it would be such a waste to let this tablet die off especially since there's a decent chance that this sound problem can be fixed if someone knowledgeable enough looks into it
 

DiamondJohn

Recognized Contributor
Aug 31, 2013
5,859
5,699
Sydney
Hello
I have the Samsung galaxy tab 8.9 sch-739 this is the china model and I don't think it was sold anywhere else in the world because I didn't find any mention of this model in xda. this tablet is as good as dead because Samsung didn't update it to android ice cream sandwich. the last available update for this model is android 3.2.
I've tried to revive it by flashing multiples gt-pt7300 custom ROMs such as cm 11 and asop nougat " same tablet but from different region". these ROMs worked perfectly for the china model except for the sound. I can't for the life of me understand why the sound didn't work. I've looked everywhere from xda to Chinese forums and did a ton of research but to no avail.
it would be such a waste to let this tablet die off especially since there's a decent chance that this sound problem can be fixed if someone knowledgeable enough looks into it
I do not like your chances, but have you searched github for a device tree for your specific Chinese model?

I once had a phone that was no longer supported by custom ROMs, but, a very similar phone was still being built by LOS. ROMs for the other phone worked on my phone except that the screen was upside down. I found (well someone else did) that this could be corrected by replacing two files with ones sourced from my device, and then the LOS ROM worked. On finding this out, I started building numerous newer custom ROMs from source, for my no longer supported phone.

Your sound issue may be caused by a difference in the default device blobs. There are also methods to build device trees from a running phone. They basically pull all the required proprietary blobs specific to your working device.
 

tchl

Senior Member
Nov 15, 2021
65
6
Strange question, does anyone know how to boot into Manufacturer mode on a Huawei Mate 9 without the keypad dialer?
 

Top Liked Posts

  • 1
    Hard to tell but i installed the normal acer a501 driver i installed the adb and fastboot drivers and also the google driver. I just followed several instructions on the Internet.
    That doesn't tell me anything, when I asked what have you tried, I needed an actual answer of what steps you've taken in the process of troubleshooting the driver installation. If you followed stuff on the internet, what did those guides tell you to try. I'm trying to help but I need real answers from you so I can try to determine why they aren't installing correctly and to determine what you need to do to get them installed. It will save time and prevent chasing our tails or doing things you've already tried if you can tell me what you've already tried. If you want help, you've work with me, not against me.
  • 2
    Hello, system apps were not uninstalled ,it were only downgraded.And these apps included only launcher,Play store and Google play services.Factory reset will wipe all the user data and I want to preserve it at any cost.Is there any workaround to fix it via fastboot ?I couldn't find any Asus Zenfone 3 specific QPST flash tool or EDL method to restore data.Thank you
    Well, you said this, in the thread linked: "My device is not rooted.Yes,I selected multiple apps to uninstall and Asus launcher,Play Store,Google Play Services and some other system apps also got selected accidenlty and when Uninstall button was clicked, I suppose were downgraded in the process."

    The apps you did choose to "uninstall" although are not uninstalled this way (assuming you did it using ADB pm) are cut from the user control and sight (as if they were frozen), some OEMs require from these apps by running normally to can boot to OS.
    And, not, the apps are not downgraded this way as if you replace them by the original app that came with.

    Unfortunately you won't find a specific QPST built for this specific Asus model device nor any other specific device, QPST was developed for the Qualcomm family, the eMMC programmer (firehose) is the file that allows to use/communicate with this tool if a specific QPST version supports it.
    The eMMC programmer file is expected to be found in your stock firmware, if it doesn't have it then you can't use it by normal means.

    If the stock firmware have the needed files for QPST tool, then you can try with this method:
    2
    Just the boot slot seems to be messed up from what I did, I am just unable to get into fastboot or BROM, the video posted seemed to match up I guess it is cycling through preloader but not properly?
    I saw in your video that you kept the device connected to the PC, and then you are trying to perform the combination buttons, but you have to disconnect it from the PC.

    It might be that your device is using the DA/SLA authentication, if this is the case you have to bypass the preloader stage allowing the device to boot properly to BROM mode, this is done by the mtk-bypass utility or the same by the tools provided in the Galaxy A Forum I linked previously. Or you can use this zip, unzip it in a convenient place.

    Device might be cycling as it is very unstable, just imagine and direct yourself the timing:
    - Connect one end of the USB cable to the PC.
    - Run the bypass.bat command and have the CMD opened.
    - Press the three buttons for about 10 seconds, this will power off the device.
    - Immediately, release the three buttons, and now, rapidly, press the two volume buttons and connect to the PC the other end of the USB cable. This is how it looks with my device connecting it...
    b1.pngb2.png
    This tool also added support for your processor https://androidfilehost.com/?fid=7161016148664809258
    2
    Hello guys,I was uninstalling some apps and accidently Asus launcher,Google Play and Play services etc got selected as well.While apps were getting uninstalled and downgraded,phone restarted somehow and everything is screwed up now.I am stuck on a screen telling “Can’t load Android System.Your data may be corrupt.If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device” with 2 options underneath, 1.Try again and 2.Factory data reset

    When I select “Try again” it shows “ Dead android robot on his back and red triangle” for a split second and then goes to Asus logo screen for 5 seconds and then ask for encryption key, when I enter the key it goes to ASUS logo screen again for 30-40 seconds and again back to Error screen.

    Asus ZenFone 3 ZE552KL
    ROM : Stock Oreo Version WW-15.0410.1807.75
    Bootloader is Locked
    Recovery : Stock Recovery
    USB debugging : Disabled
    Android device encryption is ON


    I don’t wanna to lose my data coz there are some very important documents,projects reports, pictures and backups in it.

    Device is booting in Fastboot Mode and Recovery Mode.

    It even boots to the Sideload Mode via recovery and running "adb devices" command shows it attached with it's serial number and sideload but other commands don't work ( probably coz USB debugging is disabled ? )

    Device is being shown /listed in Fastboot Mode.

    I am unable to use adb as USB debugging is disabled.Running "adb devices " command shows device’s serial number and "recovery" written next to it ,in the command prompt.

    Will flashing Version WW-15.0410.1807.75 again do the job without wiping user data ? Just like “userdata” partition is not normally touched by the OTA update process ?

    How about flashing only boot.img / system.img ?Can we resolve the issue by just flashing just system.img or boot.img instead of flashing complete stock ROM ?

    I don't care about performance of the system or unpredicted issues later on,my entire focus is on preserving my data.

    Any help would be greatly appreciated!
    If you can flash the same firmware version probably won't wipe data, usually it doesn't but no way to tell you for sure.
    Flashing by parts is not an option, your device is locked.
    1
    Hard to tell but i installed the normal acer a501 driver i installed the adb and fastboot drivers and also the google driver. I just followed several instructions on the Internet.
    That doesn't tell me anything, when I asked what have you tried, I needed an actual answer of what steps you've taken in the process of troubleshooting the driver installation. If you followed stuff on the internet, what did those guides tell you to try. I'm trying to help but I need real answers from you so I can try to determine why they aren't installing correctly and to determine what you need to do to get them installed. It will save time and prevent chasing our tails or doing things you've already tried if you can tell me what you've already tried. If you want help, you've work with me, not against me.
    1
    Ahh ok, more headaches lol.

    The manufacturer refuses to help even developers unlock the bootloader or root and brags that they are doing everything they can to prevent people from doing so with 'their' devices like they still own it, they think they are apple.

    I will continue to scour the net to see if i can locate recovery/root options.

    Thanks for your reply.
    You say that they "refuses to help even developers unlock the bootloader" if this step can't be done, you can't further advance on this matter.

    Your first goal has to finding out how to unlock bootloader.

    As per the FRP maybe it is not triggered, you could boot device and set it up for the use not having only the Google Play service, from what I know the FRP protection avoid device to pass the first setup where the logging account is required.
  • 385
    There are a lot of people joining XDA on a daily basis, and there are a lot of repetitive questions being asked
    which clutter up the Development and 'Q & A' threads. Point them here. Feel free to ask or answer questions.

    The idea of this thread is to get users to help other users with their problems/questions. People are usually
    ridiculed for asking questions that other people deem stupid even though it may be a legitimate question. This
    leads to new users being afraid to ask questions!

    Only provide well mannered help towards users in this thread. Please do not spoon feed, but rather point in
    the direction where that user can find an answer
    and educate himself. If you don't want to answer, at least
    point out where to find the answer.



    Before posting anything, I strongly advise you to read THIS thread.

    Then, have a quick look at the names of threads in Post No. 2, you might find what you need right away.

    Third. Even if you do get your question answered, please do come back and read threads in Post No. 2
    (coming later as soon as we start getting the guides) to educate yourself. You'll be surprised how much time
    and frustration it will save you in the future!



    No abuse towards noobs tolerated here! That means:
    NO TROLLING
    NO NAME CALLING
    NO RIDICULING
    NO FLAMING


    ASK ANY QUESTION HERE! No question is stupid or irrelevant in this thread. You will either get an answer or will get pointed in the right direction.


    *A Special Thanks to mark manning for his help in creating this thread*


    HALL OF FAME

    People who contributed most to this thread and helped countless number of people with their
    problems/questions. In no particular order.

    Bruce Wayne
    post-mortem
    SilentStrider
    Ghostfreak NB
    mayank9856
    sgs22012
    Zatta
    ADDICT.ANK



    These people also have the right to use the banner below:
    Newbie%20Thread%20Sign.gif


    Just add this code to your signature:
    HTML:
    [URL="http://forum.xda-developers.com/showthread.php?t=2257421"][IMG]https://dl.dropboxusercontent.com/u/41066660/Newbie%20Thread%20Sign.gif[/IMG][/URL]
    111
    Reserved

    Just a few words of advice on keeping this thread clean of unnecessary clutter:

    1. Before posting a question, it is highly recommended to read this thread.

    2. Click the Thanks button on the posts that helped you, instead of posting "Thanks". This helps other members in finding out the best replies that get buried in the thread.

    3. Do not use this thread to increase your post count! The Off-Topic forum is the place for that.

    4. Do a simple search of this thread before asking to see if your question has been asked previously.

    5. If your question has not received an answer after a few hours, please be patient. Someone will answer you shortly. If you do not get an answer in 24 hours, you may BUMP your post. If you still have no answer after a week, do mention me in your post.

    Thank you for your cooperation!
    26
    Good job mate, hopefully lots of members will find this thread very helpful :cool::good:
    12
    ZTE V970 Brick?

    Hi,

    I've been trying to install Bruno's ROM for this phone (cam with all chinese apps). http://forum.xda-developers.com/showthread.php?t=1856578

    but have a big problem. I tried my best to follow the instructions but, really couldn't work out if I was doing things in the right order.. is there an actual step- by step for this procedure? I know I'm a noob and read this read that I am an idiot etc. etc. but I thought if I used to ROM on that page and the software recommended it would be easy.

    Here's what I did:

    Downloaded all the files as told.

    Tried to 'flash a custom recovery' as here http://bm-smartphone-reviews.blogspot.co.uk/2012/05/mt6575-flashing-tutorial.html

    but it did not mention how to use the ZTE custom recovery file http://d-h.st/Vgt

    I'm also not sure at all that the 'MediaTek drivers' were installed properly. The phone never appeared in the Device manager.

    I opened SP flash tool and followed this: http://bm-smartphone-reviews.blogspot.co.uk/2012/05/mt6575-flashing-tutorial.html

    and selected the 'scatter file' from the unzipped Bruno ROM (took a while to realise had to unzip it to get the file!!!)

    I noticed most of the boxes on the scatter file were unchecked but carried on and ignored a warning message about the phone may not be able to boot (the tutorial said to ignore it).

    I had to click 'download' then plug the phone in and eventually I got the red loading bar. This finished... then nothing else.. no purple bar.. nothing.

    So after waiting a few minutes I unplugged the phone.

    It now appears to be a total brick. What did I do wrong? Why no purple bar? Were the scatter items supposed to be unchecked? What was the 'custom recovery' file for? Because the SP flash prog never asked for it.

    Is there any point in trying it again or is the phone dead?

    Thanks for any help..

    Theo