He all
Love this site all the info and devs are fantastic. Sadly im stumped and need assistance.
Yes this phone is old there is a reason its important. more so the data with in is backed up but not near enough to be ok with the problem.
So how did it happen ? phone was on as usual picked it up and had the emergency screen.
Previous mods Its a stock rom with unlocked bootloader, it was my phone of choice for pokemon at the time, then the Magisk changes forced me to find an alternate headset. so it was reset and used perfectly till now.
Images to understand and answer further questions added.
My request would be to run a fix and kick on... secondly a way to backup the device
and sadly third nuke or reset and rebuild, its not your ever day oh i lost my messages or girlfriends photos, no disrespect to those positions, this is just highly impactful to me.
i do my own android hardware repairs and such so not afraid to dive in
I have No clue the password its requesting ?? how ? why ? for what ? I do have an applock program assigned to 2 apps for security, this to makes no sense.
a few more tidbits dev mode is on but i cant change an option via windows ie transfer files.
Its not rooted, no modules, it appears fastboot is working bootloader loads fine.
recovery its NO COMMAND but i can boot TWRP image if needed.
i am not well off at all but i would be willing to donate a reasonable but fair fee if the data can be retained.
I thank those taking interest in this greatly an hope your weekend was better than mine
{
"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"
}
If you can boot twrp, then you may be able to read your files using adb pull. I say "may" because sometimes twrp can't decrypt the data, and then that won't work.
Another way is described in this thread:
Remove /Bypass Lockscreen With Recovery
Recently when i restored my data using TWRP i faced a problem at lock screen. I was not able to unlock my phone with the pin i set Earlier..So after so many attempts i was able to find a solution for that problem.(works with pattern,pin etc)...
forum.xda-developers.com
but again you need a fully working twrp.
A third way is using the vulnerability described here:
Accidental $70k Google Pixel Lock Screen Bypass
David Schütz's bug bounty writeups
bugs.xdavidhu.me
That does not require twrp.
runekock said:
If you can boot twrp, then you may be able to read your files using adb pull. I say "may" because sometimes twrp can't decrypt the data, and then that won't work.
Another way is described in this thread:
Remove /Bypass Lockscreen With Recovery
Recently when i restored my data using TWRP i faced a problem at lock screen. I was not able to unlock my phone with the pin i set Earlier..So after so many attempts i was able to find a solution for that problem.(works with pattern,pin etc)...
forum.xda-developers.com
but again you need a fully working twrp.
A third way is using the vulnerability described here:
Accidental $70k Google Pixel Lock Screen Bypass
David Schütz's bug bounty writeups
bugs.xdavidhu.me
That does not require twrp.
Click to expand...
Click to collapse
Your TWRP experience with this disk layout has chewed some of your time to i see
i shall, fiddle with your optiond. thank you your sppreciated.
Related
I've had my phone since end of November so its one of the original rev.
Just a few minutes ago I rebooted my phone to recovery and this is what happened.
- Rebooted to Recovery (TWRP)
- Screen turned White
- Didn't do anything and went to take a picture of it.
- Took a Picture (view below)
- Then it loaded TWRP but screen is still flickering
- Didn't touch anything and it went to the bootloader menu and screen was still flickering.
What I mean about flickering, the screen was still viewable just the brightness was going higher and lower.
- Rebooted back to System (still flickering), tried to record it but couldnt really since the quality of the cam couldn't see what was going on.
- Rebooted back to TWRP, loaded it fine but still flickering.
- Rebooted back to System and it went away.
- Rebooted back to TWRP and it looks fine.
Modem: .83
OS: 4.3
ROM: Paranoid Android 4.3 August 16
Kernel: hells-Core b33-ANY
Now someone might say oh its the kernel, probably kernel or ROM. But this happened in both the bootloader menu and TWRP and during that time ROM and kernel wouldn't be running.
Anyone has had this happen, please share your experience
Wanted to know if this is a known thing or my phone is starting to die?
Only dropped once like 6 months back and thats w/ a hard case 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"
}
Happened to me twice till now. I think it's just a bug with gpu and a reboot should fix that. Although, I have no clue why it happens or what triggers it. Also I have noticed that both the times it happened to me, I was rebooting into recovery (TWRP).
sandy-achar said:
Happened to me twice till now. I think it's just a bug with gpu and a reboot should fix that. Although, I have no clue why it happens or what triggers it. Also I have noticed that both the times it happened to me, I was rebooting into recovery (TWRP).
Click to expand...
Click to collapse
Ah alright thanks, good to know I'm not the only one or at least its known.
I practically flash my phone weekly/daily and never had that happen to me before so when I did it today I was like wth lol. Now with my experiences with computers when it something flickers like that or graphic errors we think drivers and if its not loaded up we think its memory dying so I was already trying to diagnose it lol..
But if its a known issue guess I cant do anything about it, at least its back in working condition :good:
The same thing has happened to me, but when I am running Google Maps. The first time it happened the screen became unresponsive and I went to reboot and had the same flashing screen you are describing. I started freaking out and went to reboot again and it was persistent in the boot screen each time. After about 5 minutes it stopped but I still have issues with my phone freezing with Maps and now when I look at flash videos on the stock Browser (I don't use Chrome).
I had a similar issue with my Macbook Pro when I accidentally block the exhaust but my phone is set to very lore frequency's with SetCPU.
I am using AOKP Milestone 2 and Ziddy's kernel for OTG support.
Sept 20
I've been getting a display bug while using the Cyanogen M10 snapshot and I can't figure out the issue.
{
"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 have done a fresh install, no kernels, no messing with stock performance settings, and lately no Xposed. Disabling Xposed seemed to have no resolve with the issue so I've tried a dirty flash this time to see if it could be something that messed up system files.
Anyone know what might be causing this or be suffering from the same issue?
In addition I tried doing a reflash of the ROM after having determined Xposed is not at fault (issue persists), this is me testing to see if some system files are somehow corrupt and have done something to cause this.
Sept 21
I noticed that the issue commonly occurs while I am in the middle of typing with the keyboard, cleared cache & data of Google Keyboard.
I have installed the latest Nightly in an attempt to fix this, if it is an issue with the M10 Snapshot.
Time since boot: About 4 hours. (Trying to find a correlation).
Issue persisting.. kinda?
The screen flashes the glitch this time, rather than freezing with the screen. So think of using some sort of app or interacting and for a split second the above image, or something similar, appears then reverts to proper rendering. My phone froze not too long after this, I didn't sit and wait to figure out if it was lag or full-freeze.
The display stopped responding though the keys still would re-light after touching the home key. I waited only 10 seconds before pulling the battery, since it wasn't worth the time finding out.
P.S. I have also posted this in the CyanogenMod Builder Thread, so if it looks familiar.. there you go.
i
Serotheo said:
Sept 20
I've been getting a display bug while using the Cyanogen M10 snapshot and I can't figure out the issue.
I have done a fresh install, no kernels, no messing with stock performance settings, and lately no Xposed. Disabling Xposed seemed to have no resolve with the issue so I've tried a dirty flash this time to see if it could be something that messed up system files.
Anyone know what might be causing this or be suffering from the same issue?
In addition I tried doing a reflash of the ROM after having determined Xposed is not at fault (issue persists), this is me testing to see if some system files are somehow corrupt and have done something to cause this.
Sept 21
I noticed that the issue commonly occurs while I am in the middle of typing with the keyboard, cleared cache & data of Google Keyboard.
I have installed the latest Nightly in an attempt to fix this, if it is an issue with the M10 Snapshot.
Time since boot: About 4 hours. (Trying to find a correlation).
Issue persisting.. kinda?
The screen flashes the glitch this time, rather than freezing with the screen. So think of using some sort of app or interacting and for a split second the above image, or something similar, appears then reverts to proper rendering. My phone froze not too long after this, I didn't sit and wait to figure out if it was lag or full-freeze.
The display stopped responding though the keys still would re-light after touching the home key. I waited only 10 seconds before pulling the battery, since it wasn't worth the time finding out.
P.S. I have also posted this in the CyanogenMod Builder Thread, so if it looks familiar.. there you go.
Click to expand...
Click to collapse
did you Wipe completely and then install fresh rom?
1. wipe completely through recovery (cache/dalvik/data)
2. install Fresh (latest nightlies) firmware
> if problem remains after few hours (without any extra customization) it might be the hardware problem... so take it to a services.
:good:
I have done those entirely.
Hi All,
Problem: Wifi is not switching on my Galaxy S4 (I9505). It's been grayed out and I'm unable to switch it on.
Actions taken: I've been researching and trying to resolve this problem non stop for nearly 24 hours. I've done the following:
- Upgraded my stock to CyanogenMod 11 since I (naively) thought it would rectify the wifi problem. (cm-11-20141008-SNAPSHOT-M11-jflte)
- Updated my modem to the latest one I could find (I9505XXUGNG2_MODEM)
- Installed the wifi fix (I9505XXUGNG8_WIFI_FIX)
- Tried a bunch of other suggestion (e.g. using sqlite to change some setting values.)
No sure what more I can do, and I'm starting to think it might be a hardware problem?
Are there any more suggestions? Or is there any way to debug it and find out if it's an hardware problem?
Appreciate any help I could get , coz this is driving me crazy!
Images:
{
"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"
}
daylebo5 said:
Wifi is not switching on my Galaxy S4 (I9505). It's been grayed out and I'm unable to switch it on.
Click to expand...
Click to collapse
Try downloading the latest version of your firmware on sammobile.
If it doesn't work, try installing a custom ROM, like "Imperium ROM". It should "repair" the issue.
"Imperium ROM" replaces the kernel (It should also fix this)
Thanks, will give Imperium ROM a try but doesn't Cyanogenmod also replace the kernel?
OK, I tried downloading the latest firmware - No Help
Also tried installing new kernel over the cyanogenmod kernel
- Tried Ktoon but it broke a few more things such as basic connectivity and did not help with the wifi issue (i.e. KT-SGS4-KK4.4-AOSP-INTL-07.12.2014)
- Currently running Alucard but the wifi issue still persist (i.e. Kernel-Alucard-V1.4ocm-[00-22]-[09-11]-AOSPV2-EUR-KK4.4-SGIV-PWR-CORE)
Haven't had a chance to try a Imperium ROM, since I needed my phone and didn't have sufficient time to wipe and reinstall all data and apps. Any other suggestions before flashing a completely new rom?
Revert to stock.
Flash stock rom twice
First time, let odin auto reboot and you configure your phone. Then go to download mode again
Second time flashing, uncheck auto reboot. Keep phone off for 5-10 minutes after flashing and then turn on.
"If someone helps, never forget to hit thanks ? "
I am in dire help with troubleshooting my Axon 7 (US variant).
Here's some quick info on what I have done with the phone.
-Unlocked bootloader
-Tried out the CM ROM, and then flashed a stock based ROM (wiped all the stuff I needed too)
-It's been working fine since then
Fast forward to today. I wanted to try out some more ROMs. I wiped what I was supposed to (Dalvik/Art, cache, data), flashed the ROM, set it up, everything worked fine. Only thing that didn't work was that it wasn't downloading my previous Play Store, so I rebooted a few times, didn't fix it, so I wiped the phone again and reinstalled the ROM. Now here's where things to get messed up.
-Booted into the ROM and no comms are working (ex. SIM data, WiFi)
-Phone kept rebooting roughly every minute
-After a few reboots, the right half of the screen would freeze
Wiped and reflashed a couple different ROMs, same exact things are happening. Okay, this is weird, so I restored my backup (I ticked to back up everything in TWRP), and the same things are happening in my backup now. It doesn't matter what ROM I try, if I wipe the SD card, or even format it, the same things keep happening. I have trying to troubleshoot for the last few hours myself with no success.
Does anybody know what's wrong and any way I can fix this?
Put the lime in the coconut and drink it all up
You put the lime in the coconut and drink it all up
You put the lime in the coconut and drink it all up
{
"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"
}
Have you checked to see if you still have imei number. Sounds like you may have wiped/lost it.
Check about phone>status>imei should have one for each sim slot.
If you do still have both then factory reset, and flash drakken’s b29 update files the bootstack,etc then his stockish rom. Should get you back up and running
I cant update my oneplus 7t pro McLaren 5g edition, i have my Googleplay services up to date, i rebooted my phone multiple time, all it does it is keeps saying downloading and installing update, then it pauses, anyone knows how to fix this issue please it's been 3 days and I can't update my phone
{
"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"
}
Word of warning, me and several other people have taken this update OTA on rooted phones, and its resulted in crashing modems. Its easy enough to fix, just it requires use of the MSM tool which will wipe your data. Although, one guy I've seen so far hasnt even been able to fix it that way, with the issue persisting through multiple wipes. So do be prepared for that possibility, or just wait a while before taking it. It could be a blessing in disguise that you cant take the OTA right now.
But warning aside, I wish I could offer more help on your issue other than suggesting to flash a stock boot image and retry the OTA, as that's worked for me in the past.
If that doesn't work, and you haven't done any other major modifications to the phone, then there might be just something seriously screwed with the update itself because then the OTA would then be working on some rooted devices and not on some unrooted devices which would be exactly the opposite of its normal behavior, and not even consistently across different devices at that.
my phone is losing sim connectivity after going to 11.0.1.2HD61CD ( I am guessing the modem is also crashing) I am not rooted though. Overnight will lose Sim connectivity and then I gotta boot to recovery and wipe cache to bring the sim back online... this is getting very fustrating... whats the best way to address this - MSM TOOL full flash?
UPDATE: MSM flashed - 11.0.1.2 again and alls been well so far - running smooth.