Hi all, a week or so ago I took my old D855 out of a drawer to give it to my niece. At that moment it had CandySix ROM on it and after a wipe all worked fine.
So the other day I got the phone back because it was bootlooping. Since then I tried the following:
- wipe
- format all
- flash LineageOS
- flash Fulmics
- flash Candy7
- use LGUP to flash the proper KDZ.
All of the roms get installed correctly, but I can't enabled wifi. When setting up the phone I can't use the wifi toggle and also after a restart I can't get it o find any AP's.
Then it starts to reboot and remains in a bootloop.
This sounds bad doesn't it?
Related
Hi,
I was on the paranoid 4.4.4 rom on my I9300, everything worked fine.
I did the last update with paranoid 5.1.1 but it didn't worked well, i have multiple error and Google service won't work anymore.
The thing is, i can't do anything at all, like restore my last backup because i lost the root access with the update.
I can't load in recovery mode, i tried the HOME+VOLUME DOWN (or up) + POWER, it won't work.
I can't fine the debug mode on this version, so i really don't know how i can at least restore my last backup to go back to the 4.4.4 version.
Any help is appreciated, thaks for your time.
Root doesn't ship with any 5.x build of paranoid android. To reset you need to boot into recovery and restore your backup or flash a different ROM.
You don't need root access for that.
It sounds like you installed an incompatible gapps....
Thanks for your reply,
I managed to boot in recovery, using a method i found on the web, i pull the battery then hold the combination keys when i put it back, and it load in recovery just fine.
I think i couldn't install the proper gapps because i was in clockwork recovery, i installed the latest TWRP, but i still can't manage to install the latest paranoid rom prpoperly.
here's what i did so far:
- wipe all/ factory reset , install Paranoid5.1.1 + Gapps 5.1 mini => paranoid load but Black screen once it's loaded with the message "Android.phone interrupted" (gross traduction) popping every 2 sec, it disapear if i put the phone on airplane mode => make me think the Google service can't connect.
- Restore my last 4.4.4 backup then => wipe cache/dalvik=>install Paranoid 5.1.1 + gapps => same as the previous problem, but this time i have my old app and i can call and receive sms.
My guess so far is a problem with the Google service who can't synchronize, the Gapps i try to use are the pa_gapps-modular-pico-5.1-20150315-signed.zip
Any guess ?
Yeah. The problem is you are using old gapps. Use banks gapps
I had trouble with a clean install of PA 5.1 + Gapps on my S3 (i9300) and similar issues to yours, not sure why but I found that if I used th full fat "Stock" 5.1 Gapps the phone was fine and has been for a day or 2 now, the pico/mini/full seemed to be problematic (at least for me). Also moved to Philz Recovery using the "Rashr" app as my old CWM kept throwing an error of status 6 on any Gapps I downloaded... Must admit though that once stable PA Lollipop runs well on the S3 and battery seems better over the past couple of days too...
I have been running CM13 for few months now. Yesterday the phone turned off and when I tried to turn it back on, it always kept on turning off once it gets to CM boot logo. Sometimes there might be few background flashes (the white circle that keeps on coming up behind sid, like normal boot) and then it would die.
I have since did a clean install with latest CM13 nightly with opengapps pico without xposed framework just to rule it being the cause of the issue. I am able to boot the first time after clean flash but if I reboot, the issue happens.
Installed fulmics 5.0 ROM for testing and it worked fine If I flash CM13 back again, the issue happens.
Tried to capture logcat by running adb logcat and turn on the phone. It still is stuck at waiting for device.
Does anyone else have issues with latest CM13?
Did you try older builds?
Just ask - Did you made full wipe?
halekhonza said:
Did you try older builds?
Just ask - Did you made full wipe?
Click to expand...
Click to collapse
The oldest build I could find is cm-13.0-20160422-NIGHTLY which I tried and same result.
Yes. wiped system, data, cache, Dalvik Cache & Internal storage partitions.
New to the world of Custom ROMs. A week ago I installed CM 13 which took great courage on my part and wanted to share my experience, issues and discuss possible solutions.
My phone had the latest lollipop on it. And McCafee locked. The steps that worked for me where
1) Did a factory reset and bumped into mccafee.
2) Tried download mode but kill switch was enabled.
3) Rebooted the phone to face mccafee, tried 123465 pin which worked.
4) Disengaged McCafee but not before transferring ownership to my email.
5) Tried rooting didnt work with any method.
6) Rolled back to d software version stock lollipop.
7) Rooted with PurpleDrake
8) Replaced with CM recovery didnt work.
9) Replaced with TWRP and rebooted directly to recovery
10) Installed CM and gapps mini. Worked fine. Voila!
Issues:
1) No Custom recovery sticks, whenever I flash with a custom recovery like TWRP or Clockwork. I have to reboot into recovery immediately or the custom recovery is replaced by stock. It happens on every second reboot.
My concern is here if I get stuck into bootloop and dont have a custom recovery I might not have any other option than the stock ROM which does a full reset. How can make TWRP stick forever?
2) After installation of Custom ROM there have been random reboots, I suspect there is something here with phone app or voice. So far the reboots have been when I try to call using fb messenger, appear.in and phone app itself.
Is there a guide that tells me how to track this down?
Can I install a newer Nightly and hope this get fixed?
How can I retain my apps and data when installing a newer nightly? since all guides ask to wipe everything :S
I have a backup of system and data partitions, can I use that with other ROMs.
What ROMs have a better chance of fixing this issue?
Coudnt find Stock M for D850. Why arent those available?
Should an Official ROM be more reliable than CM for this?
3) Bad signal reception so far. It may be a generic g3 issue.
Can I hope that this issue be fixed with a different ROM or updates from Cynogen?
Someone said you may have to flash the radio partition. My question is where can I get a brief understanding of what partitions there are in android and which are risky. Which ones can be replaced, backedup and replaced back.
4) Whenever the phone reboots, it gets stuck into bootloop unless I remove the SIM card. Then I power off and install SIM Card and reboot and it boots fine.
I am already tracking CM changelog for something important. Cant post urls as of now :S
Hello, I think I have a really strange problem. I'm running Exodus 6.0 (and I made a full and fully functional backup that worked without issues) and yesterday I wanted to install AICP 12.0 (Android 7.0).
So I did a clean flash, but the SIM card detection didn't work and baseband showed up as "unknown" (according to the AICP members, I am the only one with such an issue).
So I tried several times but no success. They told me that it could be a problem of the 20G modem and bootloader. So I decided to revert back and since then I only have problems.
This is what I've done: Firstly, I flashed the 20D kdz. The phone booted fine. So I tried to install TWRP through ADB. (The phone was recognized and I was able to perform ADB commands). So I booted to bootloader, typed in the commands, but....nothing. TWRP didn't boot and I couldn't install it, no matter what I've tried. No I was on stock Rom without root and custom recovery, so I decided to revert back to Lollipop. I flashed the 10c kdz, flashed the rooted system image, wanted to flash TWRP (3.0.2-1) via Flashify, no success. Not until I tried TWRP 3.0.2-0, I had success and TWRP has been flashed. So ok, all fine now I thought, so I flashed the complete 20D stock Rom via TWRP, booted it up, worked. Now I wanted to give AICP a try again. So again installed, again no SIM card detection. With the CM 14 nightly 10/21 flashed afterwards (always clean flashed), success! SIM card was detected fine. So, again AICP tried and surprise, SIM card was detected as well. But now I had new problems: When I flashed SuperSU, SIM card wasnt't detected again.
Without SuperSU and stock AICP kernel, I suffered random reboots while setting up the WiFi connection in setup wizzard. Without SuperSU and Llama Sweet R7 kernel, I suffered a system crash and got a green screen saying something like "App F1Q: XPU Error!". So after some time I gave up and wanted to clean flash Exodus again, again no success, because the setup wizzard stopped (unfortunately:laugh:).
So ok, last rescue: My full backup. So I restored it (Exodus 6.0 10/22 nightly, opengapps pico 10/23, SuperSU SR1 2.78 in systemless mode, systemless xposed v86.2) and seemed to work fine. Today, I wanted to run SafetyNet Helper, and the phone suddenly rebooted. I wanted to run Pokémon Go, the phone suddenly rebooted. Nova Launcher can't get permissions for showing up unread labels correctly (though I have Nova Prime and all permissions are granted for sure!), other apps seem to work correctly. But all in all it's very strange because I have the feeling that somethink went completly wrong. So I don't know what I've done wrong, what do you think about this?
Hi All!
LG G3 with LOS 7.1.2: works fine for long time, but suddenly it crashed and goes into Boot-Loop.
Re-flashed LOS 7.1.2 -> success, but it crashed again and fall into Boot-Loop again.
Restore a pre-saved Image using TWRP: crashes while restoring now.
Try Clean Install LOS 7.1.2 -> crashes while flashing now.
Ok, going back to Stock via Download-Mode: success. But after Start-Up (asking for Lanuage ...): re-boot again
Once again installed Stock using LG Mobile Support Tool: success, but after Start-Up (asking for Lanuage ...): switch off
The battery usually lasts two to three days.
Connected it to a 2 A power supply: No improvement.
I think this should be a HW problem. Does anyone have a hint for me except cannibalize ?
Kind regards!
Had a problem the last few weeks of random restarts alot. Started by flashing stock etc. Still rebooting, thought wtf ? Bought a new battery and been all good ever since.
Try another battery.
If that doesn't work its bad internal HW.