I just flashed the Krypton rom and the security settings always crashes whenever I click on it. I have tried wiping cache/dalvik and factory resetting but still no luck. I searched this up and there isn't a clear solution.
Reflash system.img in fastboot
Projectno6 said:
I just flashed the Krypton rom and the security settings always crashes whenever I click on it. I have tried wiping cache/dalvik and factory resetting but still no luck. I searched this up and there isn't a clear solution.
Click to expand...
Click to collapse
What stock rom was on your phone before you tried Krypton?
And What Rom is Krypton based on?
Why do I ask? Well, when Stock Moto 4.4.2 came out, we saw some people try and downgrade by flashing only an older system (since GPT.BIN and Motoboot.img can't be downgraded) and they encountered the same issue... Settings -> Security kicked them back out. So I'm thinking you might be running into something similar. i.e. Krypton you are flashing is based on an older stock ROm than you had flashed on your phone. And since 3rd party roms generally only flash SYSTEM.IMG, its likely you have mismatched parts on the phone which has been shown to cause quirks and issues.
Related
About a week ago, I received an update to 22.121.1.victara_retgb.retgball.en.GB retgb. Since then, I've been having multiple random reboots every day. ..
I've tried formatting cache, still reboots. Tried running in safe mode to see if it were external apps, still reboots. Tried a factory reset yesterday and downloaded my apps again, still reboots.
Are there more people experiencing these reboots? Is there a way I can rollback the ota (I don't have a backup)?
And another small thing. I noticed how it says GB all over my FW version name. However, I'm Dutch, bought my phone retail in The Netherlands, shouldn't the version be something like nl.NL, or eu.EU ?
Try doing a factory reset, but don't install your apps. If it does not reboot when your apps are not there, it means that one of your apps is causing the reboot. To figure out which app install apps 1 by 1 to see if it reboots. Repeat until you find the app that causes the reboot.
As far as the version GB. Have you flashed any firmware? If not, then GB is fine, it does not change by itself which means you are on the correct firmware.
Sent from my XT1095 using Tapatalk
AGISCI said:
Try doing a factory reset, but don't install your apps. If it does not reboot when your apps are not there, it means that one of your apps is causing the reboot. To figure out which app install apps 1 by 1 to see if it reboots. Repeat until you find the app that causes the reboot.
As far as the version GB. Have you flashed any firmware? If not, then GB is fine, it does not change by itself which means you are on the correct firmware.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
I was hoping there would be an easier solution, but I'll do another factory reset this evening and install 1 app per day (if i'm still without crashes). I did sideload the OTA to 5.0 when it became available a couple of months back, but I think that was a link to a french OTA.
I will update this thread when I know more...
So, I've tried several things now...
- Factory Reset with backup restore
- Factory Reset without backup restore and only install Whatsapp
- Factory Reset without backup restore and no apps installed except for pre-installed apps.
In between all resets I also cleared the cache, just to be sure...
But none of all the options have any effect. I had contact with Motorola support and they told me there is absolutely nothing wrong with the update and they've never heard of this before and I should wait for the 5.1 through the official notification and not attempt to flash any other firmware or sideload any other OTA.
The GB firmware is because I returned my device due to a broken headphone input and they probably just switched the phone out with another one which so happened to have GB firmware...
I really hope I can update to 5.1 soon and the issues will be gone as this is not something desirable for retail firmware...
Hi, I tried searching for this here (I remember reading something about the bootloop problem) but can't seem to find the thread, so any help will be greatly appreciated.
I have successfully rooted my Z3c using this guide all the way to the very end, however I noticed that the wifi wasn't working. I figured it was simply because I hadn't flashed the 23.1.A.0.690 firmware yet, but once I did, my phone is stuck in a bootloop; the sony logo appears and the phone resets over and over. I'm still able to go into fastboot but my question is, how can I put a stop to the boot loop? should I flash the newest FW (D5803_23.1.A.1.28_Customized_US.ftf), go back to the one the phone was shipped with (D5803_23.1.A.0.726_Customized_US.ftf), or reflash the root exploit one (D5803_23.0.1.A.5.77_US.ftf)>
UPDATE: I flashed D5803_23.0.1.A.5.77_US.ftf and the phone booted up without a hitch and kept rooted.
cowboyv said:
Hi, I tried searching for this here (I remember reading something about the bootloop problem) but can't seem to find the thread, so any help will be greatly appreciated.
I have successfully rooted my Z3c using this guide all the way to the very end, however I noticed that the wifi wasn't working. I figured it was simply because I hadn't flashed the 23.1.A.0.690 firmware yet, but once I did, my phone is stuck in a bootloop; the sony logo appears and the phone resets over and over. I'm still able to go into fastboot but my question is, how can I put a stop to the boot loop? should I flash the newest FW (D5803_23.1.A.1.28_Customized_US.ftf), go back to the one the phone was shipped with (D5803_23.1.A.0.726_Customized_US.ftf), or reflash the root exploit one (D5803_23.0.1.A.5.77_US.ftf)>
UPDATE: I flashed D5803_23.0.1.A.5.77_US.ftf and the phone booted up without a hitch and kept rooted.
Click to expand...
Click to collapse
Bootloops on Android devices can be caused by multiple factors. I suggest Flashing the .93 Kitkat firmware from there Root and if I am not mistaken there are flashable ( .zip) Pre-Rooted Roms which are Lollipop found in the Android Development Section of this Area.
Just make sure to flash the FW corresponding to your Model Number either D5803/833
If you prefer the harder way you can always use Flashtool to flash the Stock 4.4 FTF it came with and upgrade from there.
Revontheus said:
Bootloops on Android devices can be caused by multiple factors. I suggest Flashing the .93 Kitkat firmware from there Root and if I am not mistaken there are flashable ( .zip) Pre-Rooted Roms which are Lollipop found in the Android Development Section of this Area.
Just make sure to flash the FW corresponding to your Model Number either D5803/833
If you prefer the harder way you can always use Flashtool to flash the Stock 4.4 FTF it came with and upgrade from there.
Click to expand...
Click to collapse
Yeah, what I did was reflash the .77 FW without wiping system, and then, from there I flashed this 5.02 image, however now I am encountering a different problem: a persisting notification stating that I need to update google play services, even when I'm using the 7.5.73 version for 036. Has any one else encountered this problem? Is there a solution to this?
cowboyv said:
Yeah, what I did was reflash the .77 FW without wiping system, and then, from there I flashed this 5.02 image, however now I am encountering a different problem: a persisting notification stating that I need to update google play services, even when I'm using the 7.5.73 version for 036. Has any one else encountered this problem? Is there a solution to this?
Click to expand...
Click to collapse
You can always download GAPPS manually, and flash it via Recovery if you think the Google Play Services that comes with your FW is bugged
What are my options for root?
DELETE
Can my device be rooted with the super tool?
AntDeek said:
Can my device be rooted with the super tool?
Click to expand...
Click to collapse
Yes. I rooted my 5.1.1 and installed SlimLP 5.1.1 following the last two videos in this post. Very easy
Giorgi-geo said:
Yes. I rooted my 5.1.1 and installed SlimLP 5.1.1 following the last two videos in this post. Very easy
Click to expand...
Click to collapse
the tutorial does work to root device and install SlimLP rom... but I will say that the UI keeps crashing and make the device unusable for me at the moment. I've read that SlimLP is stable, so i guess i'm a little unlucky that I've encountered this problem. I'm going to restore the device to stock and do it all over again. Anyway, just a word of warning!
DrewFerg11 said:
the tutorial does work to root device and install SlimLP rom... but I will say that the UI keeps crashing and make the device unusable for me at the moment. I've read that SlimLP is stable, so i guess i'm a little unlucky that I've encountered this problem. I'm going to restore the device to stock and do it all over again. Anyway, just a word of warning!
Click to expand...
Click to collapse
You did a clean flash, right? Wipe dalvik cache, cache, data and system.
Are you using Layers? They don't play well with Fire's screen. In fact the dev mentioned discontinuing Layers support. Anyone on 5.1.1 should definitely never use Layers.
I've been on SlimLP since it was released (I upgrade to each new version as it comes out). No crashes at all.
blueberry.sky said:
You did a clean flash, right? Wipe dalvik cache, cache, data and system.
Are you using Layers? They don't play well with Fire's screen. In fact the dev mentioned discontinuing Layers support. Anyone on 5.1.1 should definitely never use Layers.
I've been on SlimLP since it was released (I upgrade to each new version as it comes out). No crashes at all.
Click to expand...
Click to collapse
Yep, I did a clean install, wiped, and stayed away from layers (never used it before anyways). The 'System UI' constantly crashed and therefore made it impossible to do anything, besides restart the device. I was changing the Date/Date Style configurations in Settings.
Settings -> Interface -> Status Bar -> Clock and Date
Messing with the Date Style and Position, and then an alert appeared saying the UI crashed. I was able to restore my device to stock 5.1.1, re-root, and re-flash SlimLP. So far so good.... Whats weird is after the fresh re-flash I did mess with those same settings again, and the UI did crash again. Unlike last time where it would then crash constantly making it unusable, it crashed to the lock screen and then has been fine since (knock on wood). I've been using my device for about an hour now, haven't touched those settings, and everything seems to be fine for the moment :fingers-crossed:.
Can anyone tell me what´s the difference if i get a device with 5.0.1 or with 5.1.1 from amazon? Will the root or flashing of custom rom be somehow more difficult or unable?
If i get a 5.1.1 device, will i have something not working, while it would be working if i would get a 5.0.1 device?
With 5.1.1 you can't load twrp recovery to flash custom roms. Only way to currently flash roms in 5.1.1 is via FlashFire. This is far from ideal. SlimLP seems to work ok via FlashFire but there are reports that you can't flash RR or CM12.1 at the moment. And if your rom gets into a bootloop, you need to start over. Reinstall stock OS > root > install FlashFire > wipe & flash rom.
Currently 5.1.1 devices aren't as capable at flashing custom roms, rooting is simple to the end user on either now.
5.1.1 can't use the tethered twrp and thus far can't use Flashfire to install CM, though has had some success at going to SlimLp and RR roms.
Pond-life said:
Currently 5.1.1 devices aren't as capable at flashing custom roms, rooting is simple to the end user on either now.
5.1.1 can't use the tethered twrp and thus far can't use Flashfire to install CM, though has had some success at going to SlimLp and RR roms.
Click to expand...
Click to collapse
You can now flash CM on 5.1.1 devices. See this post: http://forum.xda-developers.com/showpost.php?p=64456287&postcount=969
I am being plagued by wifi issues ever since i went to a new version of Purenexus. It seems to have something to do with going to 7.1.1
I've tried the older version of the rom that was working fine before, but i still seem to have wifi issues even in these older versions now.
i tried resurection remix, but still have the same issue.
after a while the wifi wont be connected and it says authentication problem, or sometimes shows it as simply discconected.
i can manually forget the network and re add it and it seems to work fine for a while.
Durring troubleshooting today, i have tried to resey my router, even upgraded the firmware,
anyways, i'd like to flash the factory image to test to see if i still have issues. but i want to make sure that if i install 7.1.1 factory image, or 7.0 that i can still re-flash twrp from adb or am i going to have to find a root exploit?
if i flash a factory image does it "relock" my bootloader? i guess that is the more important question
thanks.
citrusfizz said:
I am being plagued by wifi issues ever since i went to a new version of Purenexus. It seems to have something to do with going to 7.1.1
I've tried the older version of the rom that was working fine before, but i still seem to have wifi issues even in these older versions now.
i tried resurection remix, but still have the same issue.
after a while the wifi wont be connected and it says authentication problem, or sometimes shows it as simply discconected.
i can manually forget the network and re add it and it seems to work fine for a while.
Durring troubleshooting today, i have tried to resey my router, even upgraded the firmware,
anyways, i'd like to flash the factory image to test to see if i still have issues. but i want to make sure that if i install 7.1.1 factory image, or 7.0 that i can still re-flash twrp from adb or am i going to have to find a root exploit?
if i flash a factory image does it "relock" my bootloader? i guess that is the more important question
thanks.
Click to expand...
Click to collapse
There will be no locking of the bootloader unless you issue the command. No exploits needed. Just flash away...
Here's an attempted TLR of what has happened
Tried installing LineageOS. Got Error 7. Tried a bunch of things to make it work like editing the updater-script and things like that but it didn't work.
Then I simply wanted my phone to work again. Installed Clean Stock ROM + Stock Recovery straight out of OnePlus webpage. Now I have permanent dm-verity error (tried going back to 4.0.2, disabling dm-verity via fastboot commands and restoring 4.0.3) and still appears.
So yeah, basically that.
I messed up like a month ago too, bricked the OP3T and managed to revive it with a chinese program.
Any ideas on why I can never manage to install LineageOS?
EDIT: After the last factory reset, the phone wouldn't find any wifi network. After an hour or so, it found my wifi and got a 92mb update that fixed the dm-verity error
What firmware are you running and what's your Android version? If you're running 7.1.1 on 4.1.0 you should be good to go just by flashing all the latest LOS files
sakumaxp said:
What firmware are you running and what's your Android version? If you're running 7.1.1 on 4.1.0 you should be good to go just by flashing all the latest LOS files
Click to expand...
Click to collapse
I just received the 4.1.0, going to try again tonight. Hope it works