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? :/
Related
Hey there ...
I'm asking because I don't know what's wrong.?
Battery went flat on me, so I charged it up as normal,
when I pressed the power button to boot up, that's as far as it went.?
I can get into Recovery ( TWRP, v2.3.2.3 ) fine, access to KB SD Card = Nill tho.?
Currently using a " Team EOS " ROM, happy to change to another ROM to fix this !!
Can anyone help or suggest anything.? What have I done wrong.?
{
"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"
}
Tab boots now, but old apps still there after fresh Rom install.?
Wow, I must say ...
I am " very disappointed " that I did not get a reply sooner than now ...
With over 45 views & no replies.? Has no-one been in my situation, stuck on the boot screen.?
I do realize not "everyone" knows how to fix things, but still, I was surprised that I got no replies, very surprised!?
Only thru " guessing " what to do, I chose to try & flash another ROM on to fix it ...
Apart from having initial "memory-card" issues, I successfully copied over a rom of my choice!
I had to take the microSD out of the TF101, into a card reader, to copy over the Rom & Gapps!
With the Rom on the memory card, I pressed the power + down volume, waited for the text to appear, then pressed the up volume!
Once inside my TWRP Recovery, (backup already done) I chose "Wipe" from the choices expecting to wipe "everything! Hmmm...
I installed the Rom of my choice ( KatKiss ), wiped cache, wiped dalvik, pressed reboot & waited ... Success, it's now booting up!
Question : What happens IF I keep the install the way it is.? - Even tho thru rebooting, it did say "Android is updating... 56 or 121" etc ...
*** After it all settled down, I noticed that ALL my apps etc, were ALL still there.? - What have I done wrong.? Why are all my apps still there.?
Am I safe to keep this install ... OR ... Do I do a fresh install (which I prefer & was expecting)!! What step did I miss, please tell me, I need to know!
Still NOT Booting Up! → Still Stuck On Boot-Screen.??
Can someone PLEASE help me.?
... I'm still stuck on this Boot Screen ...
Battery did go flat again, charged it up,
& when I rebooted it back up, I got the original boot screen & went no further.? WHY.?
I still need help on getting my Tablet setup "correctly", as obviously I'm doing something wrong.?
All ROM's install, but NEVER gets past the boot screen.? WHY.? Is there a step I'm missing.? Please tell me !!
I did do yet another complete "factory reset" ...
I then proceeded to do ALL WIPES - IE; Dalvik Cache , System , Cache , Data - Installed ROM (KatKiss-KitKat #036), install Gapps, wipe Dalvik & Cache, reboot ..
Apon rebooting, I get THE SAME SCREEN.? - Again, WHY.? - What the hell am I doing wrong.? - The message says "Install Successfull" .. Why doesn't it boot up.?
Hello there,
well, I had some Problems with my TF101 too. So.. maybe I am able to help you.
First of all: Are you able to connect your Device with your PC?
APX working?
ADB working?
Dont know if I am able to response very soon, so please feel free to look at my "Problem" Thread and what I have done or how I solved it:
http://forum.xda-developers.com/eee...tf101-boot-loop-stuck-fastboot-shell-t3147235
Regards
Bava
Bought a new miix 3-1030 running win 10for my son few weeks ago, it worked fine up untill about 2 days ago, when he started receiving only a blank black screen after login. I have tried reinstalling. Net framework and updating all video drivers, nothing changed, ive also tried hard reset. From the black screen i can still open task manager and run a few of his games for him with the run new task command, but cant windows to open start or show up in any way, touchscreen seems to have no problems. I have also brought up the novo menu with the power vol up buttons. Gives options of normal startup, bios setup, boot menu, and system recovery. Tried all 4. Normal startup and system recovery both simply restart the device with no further options and nothing has changed. Selecting Boot menu takes me one screen further but only 1 option here...win boot manager, selecting this simply restarts the device yet again with nothing changed and no other options. Ive been in bios setup as well and have tried both secure boot enabled and disabled, no change, i havn't noticed anything else changable in this section. I don't know what else to try, hate to chuck his new toy out my 28th floor window, please help!!
{
"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"
}
[QRCODE]
[/QRCODE]
Click to expand...
Click to collapse
Peteang87 said:
Bought a new miix 3-1030 running win 10for my son few weeks ago, it worked fine up untill about 2 days ago, when he started receiving only a blank black screen after login. I have tried reinstalling. Net framework and updating all video drivers, nothing changed, ive also tried hard reset. From the black screen i can still open task manager and run a few of his games for him with the run new task command, but cant windows to open start or show up in any way, touchscreen seems to have no problems. I have also brought up the novo menu with the power vol up buttons. Gives options of normal startup, bios setup, boot menu, and system recovery. Tried all 4. Normal startup and system recovery both simply restart the device with no further options and nothing has changed. Selecting Boot menu takes me one screen further but only 1 option here...win boot manager, selecting this simply restarts the device yet again with nothing changed and no other options. Ive been in bios setup as well and have tried both secure boot enabled and disabled, no change, i havn't noticed anything else changable in this section. I don't know what else to try, hate to chuck his new toy out my 28th floor window, please help!!
Click to expand...
Click to collapse
Hi,
I couldn't find much information about your device here. Try posting your query in
Android Q&A,Help and Troubleshooting
or in the Q&A thread here->[Ask Any Question][Newbie Friendly].
Experts there may be able to assist you.
Good luck
Art Vanderlay
XDA Assist
Thank you I will definitely report this there and cross my fingers
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 !
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
Hey everyone,
A few days ago I was taking the battery out of my phone, to get to the SD card, without shutting it down properly first, which presumably broke some component in my system. When I booted the phone back up again, I was noticing some weird behavior: I am able to use the phone normally, but after about a minute, the whole phone freezes and I am not able to interact (touch or power / volume buttons) with it in any way anymore. After the phone has been frozen for about a minute, it will crash and restart and I will be thrown back into the boot sequence.
Luckily I discovered, that the Safe Mode worked fine and none of these problems ever occurred there. I am able to make phone calls and access the internet via the default browser just fine there.
When using adb to get the log below, I noticed I was still able to use the shell (cd, ls, etc.) after the display froze, so I assume only some of the system is having problems.
Phone: Fairphone 3
OS: Lineage 20.0 with MindTheGapps. I updated to 20.0 a few weeks ago and already tried OTA updating to the newest version after the phone started misbehaving, without any luck.
My phone is/was rooted using magisk, but I already uninstalled it trying to prevent the crash.
Below I added the output of adb logcat, which I ran as soon as the connection to the PC was established and until I saw the bool logo again.
One thing I noticed was the message
[ 06-20 00:07:09.165 1179: 9685 E/qdmetadata ]
Unknown paramType 4096
which was issued 4000+ times during the duration the log was taken. I don't know about the fatality of this error, but digging in the lineage Source-Code I think it relates to the display.
I already thought about resetting the phone to factory default, but I have a lot of stuff on there and would prefer to not do so, ignoring the fact that this might not even solve the problem, depending on how deep it lies.
Thanks in advance,
~Okaghana
That's what ChatGPT says:
{
"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"
}
I already uninstalled all apps that I recently installed and even some older ones I didn't need.
One more thing I noticed: When my phone has low battery power (below 10%) it takes longer to freeze. I suspect a background activity is the culprit and when the phone is low on battery the power saver increases the time until it is executed
Okaghana said:
I already uninstalled all apps that I recently installed and even some older ones I didn't need.
One more thing I noticed: When my phone has low battery power (below 10%) it takes longer to freeze. I suspect a background activity is the culprit and when the phone is low on battery the power saver increases the time until it is executed
Click to expand...
Click to collapse
Do you have custom recovery ? To reflash the system, I think the update crashed the system.
Originally I had the Recovery that came with LineageOS, but I patched it for Magisk. I flashed the original, unmodified LineageOS Recovery, but that did not fix it :/
Okaghana said:
Originally I had the Recovery that came with LineageOS, but I patched it for Magisk. I flashed the original, unmodified LineageOS Recovery, but that did not fix it :/
Click to expand...
Click to collapse
What was your original os of the phone
The original OS is Fairphone OS
Okaghana said:
The original OS is Fairphone OS
Click to expand...
Click to collapse
Well my friend it's time for you try to trick your phone with firmware upgrade and return to the original os I suppose, but you said you have files one the phone am not sure about that but you can still flash twrp to backup, tell me what you think