Hello I am having an issue with my Samsung Galaxy S6 Edge and wanted to find out if anyone had any advice. Every time I restart the phone I am met with this 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"
}
It always boots up without further issues but it takes about 15 to 20 minutes for my phone to get passed this screen, which is quite frustrating. Is there any way that I can fix this issue without having to boot into the bootloader and wiping all the data from the phone or is this the only way that I can get rid of this issue.
Thank you in advance
James.
James10101 said:
Is there any way that I can fix this issue without having to boot into the bootloader and wiping all the data from the phone or is this the only way that I can get rid of this issue.
Click to expand...
Click to collapse
You keep getting that persistent message because the amount of cache files that is present in your phone. Including cache files are unwanted remnants after deleting multiple apps.
Download an app called SD Maid and:
1) Clean your junk files/cache and any other files you consider unwanted
2) Optimize your databases
3) Delete bloatware (If rooted)
4) And plenty of other things the app has to offer.
If that does not work, try doing this https://www.unlockunit.com/blog/how-to-get-rid-of-android-optimizing-apps/
Hope that helps.
Tiqqy said:
You keep getting that persistent message because the amount of cache files that is present in your phone. Including cache files are unwanted remnants after deleting multiple apps.
Download an app called SD Maid and:
1) Clean your junk files/cache and any other files you consider unwanted
2) Optimize your databases
3) Delete bloatware (If rooted)
4) And plenty of other things the app has to offer.
If that does not work, try doing this (had to remove the link because i'm a new member and can't post outside links)
Hope that helps.
Click to expand...
Click to collapse
Thanks for the help, I have used SD Maid and it still brings me to the android is starting screen. I don't know if it could have something to do with the fact that I tried and failed at rooting the device which caused some kind of error, I cant remember what it said now. I'll take a look at the link to see if that helps. Thank you.
James10101 said:
Thanks for the help, I have used SD Maid and it still brings me to the android is starting screen. I don't know if it could have something to do with the fact that I tried and failed at rooting the device which caused some kind of error, I cant remember what it said now. I'll take a look at the link to see if that helps. Thank you.
Click to expand...
Click to collapse
Boot to recovery and wipe the cache partition.
If that doesn't work, boot to recovery and factory reset(do not use factory reset in system settings, do it in recovery).
Sent from my LGL84VL using Tapatalk
This is a bug in dexopt. Sometimes it crashes, not being able to produce the optimized oat file. This causes PackageManager to invoke it again and again on each boot.
For me it happened with the Google Photos app.
To find out for sure, follow these steps:
1. Enable Developer options. Enable USB debugging in Developer options.
2. Install ADB and phone USB drivers.
3. Connect phone to PC, run adb logcat, permanently authorize the PC on the phone. Make sure "adb logcat" succeeds and you can see the logs.
4. Restart the phone.
5. Run adb logcat > log.txt while the phone is booting, wait for the boot to finish.
6. Open log.txt and look for lines containing PackageManager.DexOptimizer. For example:
Code:
03-18 11:24:40.685 4448 4448 I PackageManager.DexOptimizer: Running dexopt (dex2oat) on: /data/app/com.google.android.apps.photos-1/base.apk pkg=com.google.android.apps.photos isa=arm vmSafeMode=false debuggable=false oatDir = /data/app/com.google.android.apps.photos-1/oat bootComplete=false
03-18 11:24:54.555 4921 4928 W dex2oat : No verified method for method calling String.<init>: java.lang.String android.text.TextUtils.substring(java.lang.CharSequence, int, int)
03-18 11:24:55.410 4921 4927 F libc : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x0 in tid 4927 (Compiler driver)
03-18 11:24:55.470 3298 3298 F DEBUG : pid: 4921, tid: 4927, name: Compiler driver >>> /system/bin/dex2oat <<<
03-18 11:24:55.490 3298 3298 F DEBUG : #00 pc 0020f4be /system/lib/libart-compiler.so (_ZN3art8MIRGraph27ComputeTopologicalSortOrderEv+717)
03-18 11:24:55.635 3320 4920 E sdp.engine_list: DexInv: --- END '/data/app/com.google.android.apps.photos-1/base.apk' --- status=0x000b, process failed
7. Delete/disable the mentioned app(s) in Settings > Apps (reinstalling the app won't help, it's a bug in the ROM).
If your log.txt does not start with "---- beginning of main", increase Buffer size for logging in Developer options from 256KB to 1MB and repeat.
Related
[Q]Tried possible fixes still "Error dwnloding app frm mrket.Insufficient space..."
Fixed the problem by reflashing the Stock Firmware.No idea what was causing the problem.
If you are facing the same problem,read it (what "Dark3n" suggested ) before proceeding for a reflash.
Hi guys,the Infamous "Error downloading app from market.There is insufficient space on the device."problem is back to haunt.I am unable to find a solution even after an intensive research and troubleshooting
When I am trying to install the applications from the Google Play Store, I am getting this error.
"Error while downloading <application_name>. There is insufficient space on the device"
Click to expand...
Click to collapse
{
"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"
}
While I have sufficient space (500 MB) in the internal memory.I can’t even install the small apps like Root Checker.ASUS apps are also not getting installed.
I have faced the same error in the past on my previous devices but that got resolved after wiping the cache partiton via CWM Recovery.But this time the problem is so persistent.
Things I have tried :
>Cleared cache using Clean Master and CacheMate.
1.Checked and if there's any “ .odex file” in “/data/app”.NO .odex file there.
2.Wiped cache partition via recovery.
3.Force Stopped “Google Play Store” and “Google Services”.Cleared “Data” and “Cache”
4.Force Stopped “Google Play Store” and “Google Services”.Cleared “Data” and “Cache” and uninstalled “Updates”.
5.Stop the market app.Then clear the cache from inside the task manager according to this post.
This error is annoying the crap outta me and I am at my wits end on this one.
P.S. Yes,I know,I can use "FolderMount" OR use "Link2SD" to link the apps to SDCard,I just don’t understand the point of wasting 500 MB space.That’s beyond comprehension.
[Asus Zenfone5 A501CG] [Rooted] [Android : 4.4.2] [Build :ASUS_T00J_WW_user_2.21.40.44] [Stock Recovery]
(Updated to 2.21.40.44 via OTA.Do I need to "Factory Reset" my device ?)
Ever faced the same issue ? Any clues ?
Any help on this problem would be greatly appreciated!!!
Thank you!!
Could be a permission issue, or preexisting files that fail to be overwritten.
Try SD Maids CorpseFinder and enable all extra filters in the settings, that should find issues with preexisting files.
Make sure that you have enough space specifically on /data/data.
If you can record the failed install in a logcat there might be more specific information.
Dark3n said:
Could be a permission issue, or preexisting files that fail to be overwritten.Try SD Maids CorpseFinder and enable all extra filters in the settings, that should find issues with preexisting files.
Make sure that you have enough space specifically on /data/data.
If you can record the failed install in a logcat there might be more specific information.
Click to expand...
Click to collapse
Thanks for the response buddy.I had already fixed the problem by flashing latest firmware by the time I checked your post.
You are right,that could be a permission.I have been using SD Maid for a long time and no doubt it's such a wonderful must have utility,unfortunately I didn't think about the preexisting files Anyway,it might be useful for othere users.
Thanks again for your support and developing such a wonderful app
Really appreciate that.
Regards
(request to admins and moderators i have found some newer methods so please dont close this thread)
here is a list of how to fix a lot of play store problems
note currently i am busy ill write them later i ve written some of them
please click the thanks button
(request to admins and moderators i have found some newer methods so please dont close this thread)
error 492 wipe dalvik cache cache remove and add your google account if youre using greenifys beta version please degreenify google account manager downloads download manager media storage play services and play store and clear cache
if you used internet speed master by nez droid, you will need to reflash the system
error 923 check your connection delete the file system/etc/hosts and , if present, delete /data/hosts. this error happens when a reliable connection to google cant be established due to network problems. try deleting system/etc/hosts and data/hosts (if present)
error 429 try on wifi instead of mobile network try using a different apn remove rooted xxxxxxx task killers
error 29 (4.4 only) looks like some phone using art runtime are affected try switching to dalvik
rpc 5 aec 0 error this sometimes can happen when you restore accounts.db remove and re-add your google account
cant establish secure connection - factory data reset. if factory reset didnt work, reflash the /system partition / rom
combination of 492 429 and 923 this means your dalvik cache is corrupted, your internet is bad, amplify is blocking some wakelock, greenify has cut off important wake up paths you used freedom or used lucky patchers odex all system apps in lucky patcher
firstly if you have lucky patcher, go into toolbox and select remove all odex files then delete system/etc/hosts and /data/hosts (only if present) flush the dalvik cache then wipe /cache. if youre thinking that an xposed mod is doing this, deactivate all mods and reactivate one by one to see which one causes the issue. try on a different internet connection. if everything fails wipe /data /cache and /system and reflash your rom. this error is known to be caused by notorius apps, battery saver apps, task killers that rely on root+xposed etc. Also, try keeping the screen on. maybe it will succeed
(request to admins and moderators i have found some newer methods so please dont close this thread)
heh heh
{
"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've used <Mod snip> and now my playstore isn't sorking showing connection error even after a factory reset
waheedzaman1998 said:
I've used <Mod snip> and now my playstore isn't sorking showing connection error even after a factory reset
Click to expand...
Click to collapse
We don't discuss warez on XDA, which is what that app is. It steals from developers by hacking paid features. You will need to find help with that elsewhere.
Darth
Forum Moderator
Yup!! I know all you have to do is use root explorer and delete the file named hosts and uninstall playstore and reinstall again and use link2Sd app and make it a system app. Clear data of playstore and u r done
digitalworld2028 said:
thanks a lot
Click to expand...
Click to collapse
I wrote this guide a long time ago. Back then I had no knowledge really and uselessly associated error codes with what could be happening
In reality, an error code is just a condition in the code that evaluated to true and says nothing about the actual error
Maybe the information in this guide will work for 90% of all users but the information in this thread should just be considered wrong now, considering it's age and what I was trying to do with it anyway
thread closed as per OP request
Hello
so after filming for 5 seconds underwater my z3's screen turned black and turned off permanently. though it seems to still turn on normally
after unsuccessful replacements and search on the internet the logical explanation was that the gpu is dead
so now i want to recover the data (photos, videos, music) i have on the internal memory
the device is locked by pattern lock so i can't access it when i plug it (it just detects the device)
i want to know if flashing will remove the lock without clearing my data
and if so how can i do it with a dead screen
best regards
I can think some ways of doing data recovery...
1: Safe method if you have recovery!
you can do a soft reset by pressing the button on the side of the sd card/sim tray.
{
"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"
}
Press it till it vibrates for a second time, this time it will shut down.
After this, you can turn on your phone and enter recovery (if you have a custom rom or kernel), in this mode you can fetch your files from the internal storage by connecting it via usb to your computer.
2: Use as last resort and confirm the internal storage wiping before doing anything...
Unlock bootloader (I cant remember if it does erase the internal storage partition or not) to install a custom kernel that has recovery.
3: Probably the second safest but it's needs searching the tools if you don't know how to use adb.
If you do have USB Debugging enabled in the phone, you can try to fetch files by using adb in your computer.
Open a CMD in the directory where adb.exe is located and write this code
adb.exe pull /sdcard/ c:/sdcardbackup/
Click to expand...
Click to collapse
It will fetch your files from internal storage to a folder called sdcardbackup on your C:/ drive
Hope this can help you!
If you're going with flashtool, you need to wipe the data partition called userdata since there is where the config is stored but it also wipes the internal storage
hello thanks for the reply
1. tried no luck
2. bootloader is already unlocked and phone is rooted
3. i remember unlocking usb debugging (always do on android) so i will try this, i'll keep you updated on the results
best regards
update :
for whatever reason the phone isn't authorized anymore and i can't access it. anything i can do about it
mm.salem said:
hello thanks for the reply
1. tried no luck
2. bootloader is already unlocked and phone is rooted
3. i remember unlocking usb debugging (always do on android) so i will try this, i'll keep you updated on the results
best regards
update :
for whatever reason the phone isn't authorized anymore and i can't access it. anything i can do about it
Click to expand...
Click to collapse
Hi, as your bootloader is already unlocked try to continue with 2.
If you haven't installed a custom kernel try to install a kernel like EliteKernel, you can find it here in the forums.
Use flashtools and flash boot.img via fastboot mode on your phone, that way you will have a recovery working.
update
flashed Z3FotaTWRPV5.img into it and got it to boot to recovery
i just got my pictures including the picture that killed my gpu (ironic)
anyway thanks for the help... can i edit this to solved?
in brief:
the data should be there on the phone, so there's hope it should be easier to recover than deleted data but i run out of ideas how to get adb to find and pull it... maybe a more advanced user has better knowledge (better commands or tools)
adb devices and fastboot devices communicate with phone, so i have all drivers installed, i can only tackle with it via usb from windows 7 based computer
the detailed story:
i have a huawei g620s-L01, stuck in bootloop (just loading huawei logo forever or until battery empty but does not restart) and also "volume down" button does nothing... the bootloader is locked and huawei seems to have stopped providing unlock codes...the touch works but is shattered so i was told repair the button is not an option...
i can boot it into recovery mode using "volume up + power" but i can't use the recovery menu due to the dead "volume down"
from recovery menu i can only "reboot system now" but that re-enters the bootloop,
also i get bootloop if i try to boot into download mode via adb command
i can use some adb commands (i say some because some return errors, others say i don't have permissions)
i can boot into fastboot via adb command too...i can not find my dcim folder or any data folder to use the pull commnad, i tried the generic commands to pull sdcrd or dcim or all files with *.jpg
the user data is not accesible, i could browse some system directories but they did not contain my files via cd commands
i found some threads saying maybe i need mount or root commands
but trying to mount partitions or access su via adb also gives errors
su is not found, i do remember there was a su when android was working on the devices but is useless if i can't find/access it
i found the factory rom and some tools to try to restore rom to the phone due to claims that same rom might find my data, but the tools failed to start due to locked bootloader
i also tried several versions of full android sdk (old and new) trying to find "monitor or file browser" tools but the menu is not there...perhaps it will not activate those tools when device is in fastboot/recovery modes
{
"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 also found a 3rd party full android browser but can't connect with it either
also recovery softs are useless, they need a working android to try to recover anything...some recovery softs claimed they can fix bootloop but don't support my device
free tools that try to unlock bootloader also failed
so at this point i am running out of things to try
this is what i figured so far: i can see my data but can't touch it
i seem to have 4 partitions on the device:
1 is called sdcard but has nothing accesible on it, could be the feature for external card
2 is called ext , total size is 711,49mb , used 124,98 and available 586,5
3 is called system , total size 1,64 gb, used 1,23gb, available 418,1mb
4 is called data, total size 3,96gb, used 3,75gb, available 218,16mb
clearly the data partition is still keeping my data
i can not see my installed apps, so i guess they are also on that partition
i can see some system apps, namely 49 out of 146
so i'm guessing the issue is with one application, likely system app since i can't see them all
the phone may be partly rooted, the android may have some rooted features but the adb on it is not rooted
so i can not use the adb root command to get to my data
and i can not try to flash recovery or rom or custom boot img from adb due to bootloader locked and asking for unknown code
Hello, I installed Pixel Experience Android 13 Custom ROM. But it had IMEI issues, So I decided to roll back. When I opened SP Flash Tool, It said Select the Format All + Dowload Tool. I did the exact, But then it said, Disable verified boot or unselect the "Preloeader, Tkv, Dtbo, Trnsfs" I did what they said, Then, I flashed it completely, It said OK, I tried to boot in my device, But it wont budge. I guess it's bricked? I tried downloading an older firmware like previous version of the firmware for the same model, Then I opened the MTK Auth Bypass tool, I opened it, It used to work, But now, It gives an error:
► Installing driver... [OKAY]
► Waiting for brom... [FOUND]
● DETECT AS MTK USB Port (COM5)
► Configuration port... [OKAY]
► Handshaking... [ERROR] UNEXPECTED RESPONSE: 0x78
How to fix this error, and what could the reason be behind the bricking of the phone over no REASON?
Please guide, as I dont want to spend more on this phone as I alr went to Tech Support and spent my money there.
Thanks
[Update]: Found the Solution after 6 months, All I needed to do is to disconnect the Battery and reconnect it. Full detail on the last point in this thread I created: Infinix Fix
Re-flash Stock ROM.
jwoegerbauer said:
Re-flash Stock ROM.
Click to expand...
Click to collapse
Dear Brother, I cant flash stock rom, unless I get the DA File, and I bypass the DA file, And the Bypass tool gives an error:
Handshaking... [ERROR] UNEXPECTED RESPONSE: 0x78
Is there anyway you could help me?
If phone can get connected by ADB then you connect computer and phone via USB-cable and run
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM-ZIP-FILE>
adb reboot
jwoegerbauer said:
If phone can get connected by ADB then you connect computer and phone via USB-cable and run
Code:
adb devices
adb reboot sideload
adb sideload <STOCK-ROM-ZIP-FILE>
adb reboot
Click to expand...
Click to collapse
ummm, i dont have custom recovery.....
if it could work without custom recovery plzz reply.
{
"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"
}
Carefully read posts.
can you flash via fastboot?
i may be saying something stupid, but I do not hwo ur device works lmao.
Arealhooman said:
can you flash via fastboot?
i may be saying something stupid, but I do not hwo ur device works lmao.
Click to expand...
Click to collapse
Ur Bio is relatable, lol, Btw, Yes, my android is fixed now, But its IMEI is unknown, Idk what to do now.
how did you fix it . i am stuck in the same thing
hello 00101 said:
how did you fix it . i am stuck in the same thing
Click to expand...
Click to collapse
I went to the tech support, I just saw him opening my mobile, maybe he disconnected the battery and reattached it, as disconnecting and reattaching battery resets usb connections.