Database Info

[Completed] [OP3] After couple ROM change test my phone is unusable, HELP PLEASE !

Hello everyone,
I currently have a Oneplus 3 which is completly unusable and I'm asking for your help to make it working again.
Until yesterday I used OxygenOs 4.0.2 ROM and it was about a moment I was thinking about changing my OS for the LineageOS ROM on Android 7.1.1 .I already did in the past this kind of changement on my nexus 5 for CM 13.0 .
So, I prepared all the files I needed (TWRP, ROM, Gapps etc...) and compared a lot of similar tutorial for being able to do it perfectly and being sure everything will work fine.
Firstly, I unlocked my bootloader though my PC and installed TWRP whithout any problems.
After that, I started the flash of the ROM and the Gapps zip packs. Everything worked and I launched the OS for checking if everything work.
I also wanted to ROOT my phone so I rebooted it and went to recovery again for flashing the ROOT zip from the LineageOS website and I picked the ARM64 one because I saw on internet it was the one needed.
After that, when I reboot the phone onto the system I have to make a "reconfiguration process" on this kind of way : Choose language --> Restore from zero --> Choose network --> Google account.
But, after filed my google account information I was normally able to receive a text for the double checked of my account but never it never came and the configuration is finally unsuccessfull because IMPOSSIBLE to skip the "network" or "google account" step.
I also tried to connect my phone on an other google account without the double checked option and it doesn't work too with this king of alert : " The process doesn't work due to an unknow error. Try again in 24 hours " .
I concluded that the problem come from the ROOT ZIP file, so I put my phone again in recovery and I do a " wipe / factory reset " for doing the exact same process from the begining (installing ROM) until root with this time the ARM ROOT ZIP.
Finally, I got the exact same result with the Google Account problem.
I choosed to do the complete process a third time with this time the SuperSu v2.79 ZIP file .... Result still the same.
Finally, I stoped trying to root my phone and I did again a "Wipe / factory reset" for just installing LineageOS and the Gapps pack. And I was suprised to see that the same problem continue to happen ! I wipe the phone and did again and again and again.
But, after all of that I choosed to do it on an other way. I saw on internet that " format data" through TWRP could be a solution for cleaning everything and start from zero. I did it and the process failed ....
From this point, I am with a phone which can't do anything and which saying that's impossible for it to "mount data" and other but I prefer to show that part on pictures. I think it'll be better for understanding (Excuse me for the pink because my HTC One M7 spare phone) :
Above there are the information that TWRP give me when I start it :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
On an other hand, the phone is recognize by the computer just as a multimedia device and it's impossible to write on its memory or just having access on it :
I hope I was the most clear as I could and hoping as well for an existing solution for my issue (in better case with LineageOS on it with root working ! But I don't want to ask to much !).
Also, I am french and I apologize for my english if it can be weak sometimes.
Thank you in advance. I'll allways available if you need further information.
PS: Since my bootloader is unlocked I have these both pages when the phone boot (Picture 1 and 2) which normally permit me to boot onto the system, recovery, fastboot etc .... (Picture 3) but in reality there is NOTHING happening and I always have to do it on the classic way if I want to boot on recovery or fastboot (hold power button + ..... etc...) :

Up

Daftnap said:
Up
Click to expand...
Click to collapse
Hi !
Please don`t bump up the threads , we will answer according to our availability , thank you
Here the thread you need to follow
https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Good luck !

Bootloops after messing with Substratum. Please help!

Hi,
I am in need of some urgent help. I have an unrooted Lenovo K8 Note (without custom recovery), running on Android 8.0. I was using Substratum, kinda newish to it, and the first theme I installed was Gravija. I disabled it later to try out some other themes and apps to modify the UI. And the last app I guess I tried was this one https://play.google.com/store/apps/details?id=substratum.xperia.lockscreens which was supposed to give me an Xperia style lock screen clock. It gives a drop down menu to choose the Operating system, etc. and I stupidly chose the first option which was for Nougat roms and rebooted the device. After rebooting, as I couldn't see the clock changed, I did the same and rebooted again. After this, I read its FAQs and realized that I was choosing the wrong option and was supposed to choose the one for my device. As there was no option for an Oreo/AOSP device, I chose the option for Oreo/AOSiP and rebooted. Same result, and therefore did the same thing again. I'd also like to mention that every time I chose to "build and enable", substratum was giving me an error through a toast notification, which I don't remember and ignored, stupidly! As it wasn't working, I then simply uninstalled the app for that theme. Later on, disabled other overlays too. My device was working well for about half an hour when suddenly, everything suddenly came to a standstill. Device became unresponsive and after a few seconds, got rebooted. Since then, it's stuck in bootloops.
Most of the times, it just displays a Lenovo splash screen, then reboots after a few seconds. Sometimes, it goes till the boot animation. While the boot animation is playing, it stops all of a sudden and reboots after a few seconds. And sometimes, it boots up completely, and I unlock it. I am able to use it normally. It happens 1/10 times. But it becomes unresponsive in less than a minute, the statusbar clock stops (I have it set to HH:MM:SS format) and then the device reboots. I am struggling with this since 12 hours ago!
It works long enough for me to be able to go to settings and perform a factory reset. But I have about 40GB of data on its internal storage, including my personal photos and memories, which I don't want to lose and need to back it up before trying to reset.
I am able to connect it to my PC, copy the folders but the phone doesn't last long enough! When the copying process is less than a percent, it reboots again! I tried to backup my files for 5 hours but the phone rebooted everytime!
On one successful boot-up, I uninstalled Andromeda and while Substratum was getting uninstalled, the phone again became unresponsive and rebooted. I was later wondering if it's because of any leftovers of a theme in my system partition. The next time it booted up, I quickly went to the apps list and saw substratum was still there. I opened it and I saw a screen like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Reinstalled Andromeda, gave it permissions through the start_andromeda.bat, but Substratum showed the same screen. I tried the restart option, the app restarted and the same screen. Tried the rescue option, it closed the app and a toast notification "rescuing..." appeared. And the phone rebooted before anything else. Tried the last option and managed to save the log, but didn't understand most of it. Here it is:
Code:
Build version: one thousand ten Device: Lenovo K8 Note (manning) [lenovo/manning_retail/manning:8.0.0/OMB27.43-67/73:user/release-keys] ROM: 8.0.0 - Unknown Theme system: OMS (andromeda) Stack trace: java.lang.RuntimeException: Uncaught exception in Firebase Database runloop (3.0.0). Please report to [email protected] at com.google.firebase.database.obfuscated.zzb$1$1.run(com.google.firebase:[email protected]@16.0.3:98) at android.os.Handler.handleCallback(Handler.java:869) at android.os.Handler.dispatchMessage(Handler.java:101) at android.os.Looper.loop(Looper.java:206) at android.app.ActivityThread.main(ActivityThread.java:6784) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:240) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:852) Caused by: android.database.sqlite.SQLiteCantOpenDatabaseException: unknown error (code 14): Could not open database at android.database.sqlite.SQLiteConnection.nativeOpen(Native Method) at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java:214) at android.database.sqlite.SQLiteConnection.open(SQLiteConnection.java:198) at android.database.sqlite.SQLiteConnectionPool.openConnectionLocked(SQLiteConnectionPool.java:463) at android.database.sqlite.SQLiteConnectionPool.open(SQLiteConnectionPool.java:185) at android.database.sqlite.SQLiteConnectionPool.open(SQLiteConnectionPool.java:177) at android.database.sqlite.SQLiteDatabase.openInner(SQLiteDatabase.java:833) at android.database.sqlite.SQLiteDatabase.open(SQLiteDatabase.java:818) at android.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:711) at android.app.ContextImpl.openOrCreateDatabase(ContextImpl.java:726) at android.content.ContextWrapper.openOrCreateDatabase(ContextWrapper.java:299) at android.database.sqlite.SQLiteOpenHelper.getDatabaseLocked(SQLiteOpenHelper.java:254) at android.database.sqlite.SQLiteOpenHelper.getWritableDatabase(SQLiteOpenHelper.java:194) at com.google.firebase.database.obfuscated.zzc.zza(com.google.firebase:[email protected]@16.0.3:805) at com.google.firebase.database.obfuscated.zzc.<init>(com.google.firebase:[email protected]@16.0.3:214) at com.google.firebase.database.obfuscated.zzb.zza(com.google.firebase:[email protected]@16.0.3:171) at com.google.firebase.database.obfuscated.zzu.zzb(com.google.firebase:[email protected]@16.0.3:156) at com.google.firebase.database.obfuscated.zzab.zza(com.google.firebase:[email protected]@16.0.3:14130) at com.google.firebase.database.obfuscated.zzab$1.run(com.google.firebase:[email protected]@16.0.3:94) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:457) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:301) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636) at java.lang.Thread.run(Thread.java:764) User actions: 2018-11-27 12:35:07: LauncherActivity created 2018-11-27 12:35:08: SplashScreenActivity created 2018-11-27 12:35:08: SplashScreenActivity resumed 2018-11-27 12:35:08: LauncherActivity destroyed
I am not even sure yet if it's because of Substratum. But most probably Substratum is the reason as it was the only thing I was messing up with lastly. Not blaming the developers but my stupidity!
Trying to go to the recovery menu also starts the bootloop.
I seriously don't know what to do now! Can't attempt to factory reset it before backing up my files from the internal storage. And even then I am not sure if factory resetting is going to fix it or not! Can anybody please help me out? :/

Samsung GT-I9060 Phone Stuck at Battery Charging Animation

I have a Samsung phone model GT-i9060 with Android 4.4 and suddenly one day phone suddenly switched off and refused to start.
On powering on it would get stuck to this battery animation screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
On holding the Power+VolDwn+HomeKey I get this Warning screen with two options to continue to recovery (VolUp) or reboot
and selecting either of those options leads to these following screens: recover mode boot screen
But nothing happens then, It switches off again after 5-10 seconds on both the screens and I tried
Code:
adb devices
during all those stages but phone is not detected on PC
I need to recover some critical data from this phone which is paramount. Can someone guide me as how should i proceed with data recovery or extraction?

Asvthama said:
I have a Samsung phone model GT-i9060 with Android 4.4 and suddenly one day phone suddenly switched off and refused to start.
On powering on it would get stuck to this battery animation screen:
On holding the Power+VolDwn+HomeKey I get this Warning screen with two options to continue to recovery (VolUp) or reboot
and selecting either of those options leads to these following screens: recover mode boot screen
But nothing happens then, It switches off again after 5-10 seconds on both the screens and I tried
Code:
adb devices
during all those stages but phone is not detected on PC
I need to recover some critical data from this phone which is paramount. Can someone guide me as how should i proceed with data recovery or extraction?
Click to expand...
Click to collapse
Seems to me that your issue is caused one of these 3 reasons.
1) the battery is failing
2) the internal sdcard is failing.
3) the internal storage is completely full and has no more room to cache files when booting or running.
If it caused by the lack of space to cache files, try booting into stock recovery then use the "wipe cache partition" option(do not choose the "factory reset" option) this will clear the cache and allow the device to boot if that was the issue.
If you know the exact firmware build number version that is currently installed on your device, you can download a copy of that specific build number firmware and flash it via Odin. As long as you use the exact version that you have, it should not wipe your data when you flash it. Then, if it works, you should be able to boot the device normally and retrieve your data.
If the issue is caused by a faulty battery or a faulty internal sdcard, it may fail during flashing, if this happens, it may render the device inoperable.
Sent from my SM-S767VL using Tapatalk

Bootloop on Samsung Galaxy S3 with TWRP and Lineage OS 17.1

Hello guys, so basically you are my last hope since I cannot find a solution for my problem (at least with my level of knowledge).
Lets start from the beginning: I (someone with no experience in this topic) decided to try out a new OS on my old Samsung Galaxy S3 since a lot of apps stopped working on Android 4.3. I tried a tutorial on youtube on how to install a new custom ROM. I installed TWRP (3.5.2_9-0-i9300) and later with the help of TWRP Lineage OS 17.1 (an unoffical version for my type of phone) and everything worked perfect.
I started to download all apps I need and to customise my OS. In the end when everything was set up I decided to do a full backup using TWRP and thats where the problem started. In the development section I checked the function, that when you press the power button you can directly boot your phone into recovery mode. So my phone rebooted and ended up in a constant boot loop where at first the Samsung Galaxy logo appears (first picture) and then TWRP appears (second picture) and this process goes on and on...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sadly there is no way to get into recovery mode since this loop just continues. If tried it many times also with taking out the battery and putting it back in. The only thing I have access to is the download mode.
So my question to you: is there anything I could do in the download mode to solve this problem? I saved the important data before so a full wipe wouldnt be a problem. Maybe I can do something with odin?
I really hope you can give me some ideas to try out. Every help is appreciated. Thanks!

Try reflashing a stock ROM first of all.
Then reflash TWRP. Make a TWRP backup (especially the EFS ! That is a "must-do first and foremost" !) of your working system and progress from there.
And in the future, instead of reinstalling all your apps piecemeal I strongly recommend you use Titanium backup (paid version. The free version is very limited), that is a wise invesment for the small sum it'll cost you

@Snakeforhire reflashing stock ROM worked, thank you so much.
I will take a closer look on Titanium backup. Used it in the past but with root access. On the new Lineage OS I dont have root although it shouldnt be hard to get from what I read.

[Help] Why does my phone's boot screen look like this?

I got a pixel4a phone, but the startup screen looks like a factory mode screen. how can i remove this screen, thanks a lot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

that's not a lot of info to go by. what did you do prior to getting this screen? since when has this screen been showing? is it rooted? did you do low level stuff with it, and if so, did you do it through a computer or on the phone directly?
the first thing you would want to do is to check if you can enter recovery mode (stock will do if you don't have an aftermarket) and see if you can do something with that, like, say; factory reset.
the next thing you could try is to first backup your flash, and I mean from sector 0 to EOF, and a second backup per partition, then flash a stock rom you could get online.
I WOULD preffer to just diagnose the problem and fix it non-destructively but phones and their OSes are not built to accomodate repair beyond changing the screen/batery and resetting/flasing the ROM
P.S. throw in the chipset type while you're at it I.E. MTK or QLM

Thank you for your response, bro! This phone is a second-hand phone. When I received it, it only had the factory mode. I flashed Android 11 through the website flash.android.com, but every time I boot up the phone, the screen will display for a few seconds before entering the system. I searched online and it seems that the phone is still in factory mode and needs to be activated to normal mode, but I haven't found a way to switch to normal mode.

1. Enable ADB ( AKA USB Debugging ) on phone
2. Connect computer and phone via USB-cable
3. On computer run ADB command
Code:
adb reboot

oldmaize said:
Thank you for your response, bro! This phone is a second-hand phone. When I received it, it only had the factory mode. I flashed Android 11 through the website flash.android.com, but every time I boot up the phone, the screen will display for a few seconds before entering the system. I searched online and it seems that the phone is still in factory mode and needs to be activated to normal mode, but I haven't found a way to switch to normal mode.
Click to expand...
Click to collapse
well, taht just sounds like the ROM didn't come with a boot animation/logo so I suggest if you want one you can well... there's not much you can do without tripping tamper triggers I.E. install rootkit & modify system partition (can't be done post pie) or unpack system image, insert the animation/logo and repack, but then you have an orange state device and that's not much better than that factory logo, or you lock it without image verification enabled and hope that something doesn't rely on it
android isn't built to be moded, so you have to mod it before building an hoo boy is that a wild ride
P.S. on second read, the ROM might be in eng mode instead of userdebug or user
you could check it by either terminal emulator, issueing the command `getprop` and search for build variant or do so through adb