hey guys so i couldnt think of a title which accurately describe my problem so there it is
For the past 2 months i have been on AOKP Nougat for my sm-g800f (UK) (EE) and it has been running perfectly fine except the odd random restarts but nothing more. Just 2 days ago it started freezing a lot, unresponsive screen, restarting more often keep in mind i did not install anything new or tweak anything. So i decided to do a fresh install and also try a new rom.
I have tried 3 custom roms:
1. First i tried beanstalk the nougat version and i managed to install it but 30 minutes into use i got constant reboots:crying:
2. Resurrection Remix was next this rom took many many tries to install as the phone kept constantly rebooting through the setup process and i ran into other problems such as 'setting has stopped' and 'setup wizard has stopped'. finally after many attempts and with perseverance which manifested from i dont know where i installed it:victory: along with Gapps but just like beanstalk after 30min the same problem, constant reboots
3. the third is what i just tried aokp nougat which is right now constantly rebooting not even allowing me to set it up.
(btw between each install i did factory resets and data wipes and even wiped internal and external storage)
i have twrp 3.1.1.0-0 installed which works perfectly fine but the latest version caused problems whcih is why i am not using it.
the kernel is default.
There was one fix.... after the millionth factory reset before installing kernel 3 but after trying kernel 2 i odin flashed a clean stock 6.0.1 which worked perfectly, no restarts or freezing or anything.
However i do not want that so i flashed twrp and installed AOKP along with Gapps and here i am in a bootloop.
(note i can still access recovery even now)
my preffered setup rn is resurrection remix nougat with spookcity 1.5ghz kernel if that can be done idk
thank you and i hope u can help me
edit: atm when im in twrp on my pc the phone is shown as SM-G800 (no f )
Hi, had the same problem for months.
Succeeded yesterday for G800F with :
- complete wipe except MicroSD
- Lineage OS 14.1 August build
- AddonSu from LOS extra
- OpenGApps Nano ARM 7.1
- Spookcity Kernel 1,5 GHz.
Keep in touch.
I'll update my tutorial once I'm back home.
Related
Hello guys! How are you?
I'm having some bugs with CyanogenMod 12.1 in my MotoG and haven't found nothing that could help me with my problem.
Well, here's the story:
My device had Android KitKat 4.4 as the stock rom and I updated it to Lollipop 5.0 before rooting.
Well, I unlocked the bootloader and used TWRP as a custom recovery and installed SuperSU.
I've been using the phone about almost 8 months after rooting and then, Motorola released an update, I tried to update it via OTA and, of course, it didn't worked since TWRP can't OTA. Nothing changed in my phone, I simply rebooted it and it worked but since a few days some apps started to suddenly close and/or stop.
I decided to install CyanogenMod 12.1, downloaded the latest nightly and a stock package of GApps and flashed them via TWRP.
Wiped Dalvik Cache, Data, Cache and System
At the first attempt, TWRP rebooted after flashing CM12.1 and I wiped the caches via WIPE menu before flashing GApps wich couldn't be installed because there was "no space in storage". Well, I booted my phone normally (running cm12) and downloaded a Micro GApps package and flashed it sucessfully.
Problem is: Clock stops working (it has stopped for now), I can't install some apps from PlayStore such as Facebook, etc and my phone appears to be unrooted.
I think my TWRP is bugged or something cause it does not works as tutorials, etc tells...It shows some errors and sometimes reboots itself after flashing some file.
Do you guys think I should reset everything and then redo all the steps to use CyanogenMod properly? I really liked this custom rom but I'm afraid there will be more bugs in the future....
Anyone?
my solution..
1. (JUST SAYING)You can install ota through fastboot. Use the ota file found in root.( There is a thread for this)
2. Try installing Lucas 2.8.7.0 build. Find it in his thread. Its posted there. It's somewhere in the sea of posts just find it.
3. Then try to clean flash cm 11 build. Then install cm 12.1 build.
4. See if it works.
I don't understand why you face this problem cause well TWRP is very stable.
Well see if it works and get back to me.
Edit :
Saved you some trouble here's the link for TWRP
Link : https://drive.google.com/file/d/0B0WGdtNWubBJVlctNE5PZ1oyQ00/view?pli=1
Its labelled as 2.8.7.0 but its actually 6.0 features of 7.0.
sagar846 said:
1. (JUST SAYING)You can install ota through fastboot. Use the ota file found in root.( There is a thread for this)
2. Try installing Lucas 2.8.7.0 build. Find it in his thread. Its posted there. It's somewhere in the sea of posts just find it.
3. Then try to clean flash cm 11 build. Then install cm 12.1 build.
4. See if it works.
I don't understand why you face this problem cause well TWRP is very stable.
Well see if it works and get back to me.
Edit :
Saved you some trouble here's the link for TWRP
Link : https://drive.google.com/file/d/0B0WGdtNWubBJVlctNE5PZ1oyQ00/view?pli=1
Its labelled as 2.8.7.0 but its actually 6.0 features of 7.0.
Click to expand...
Click to collapse
This is exactly what you should do.
There are several things that don't work as they supposed to do, so follow the steps @sagar846 mentioned.
Sent from somewhere
Oniganon said:
Anyone?
Click to expand...
Click to collapse
cm 12 and 12.1 have some little bugs still but it is useable for daily use
Hi guys!
my phone seems to have issues with dirty flashes.
A few days ago i successfully clean installed cm 13 from stock. so far, so good.
I decided to use the nightly updates so i downloaded the latest build from the built in updater(i also tried to install the nightlies manually but still no success)
The installation by itself did not show any errors but when i reboot the phone from the recovery(TWRP) it gets stuck in a bootloop. this happened with every nightly so far but when i clean installed them they worked fine.
Am i doing something wrong and does anybody experience the same issue?
i appriciate every tip on how to solve this problem because i am not going to clean install the nightlies and set up the phone over and over again
thanks in advance
Jurac aka. mynameisnotraphael
Have you tried wiping cache and dalvik?
Sent from my Moto G 2014 using Tapatalk
*First a little background on what happened...
So due to an sight oversight on my side, and what I feel was a mistake on CMs part, I installed CM 13 over 12.1 one day on my droid turbo. I did not realize what was going on until after I had done it, it was just me keeping up with my normal updates. So I realized what had happened and used an older version of CM 12.1 that I had already downloaded and installed it. This rendered my phone unable to boot into an OS. No problem, I still had TWRP. I downloaded the flash able 5.0 stock ROM here
http://forum.xda-developers.com/droid-turbo/development/rom-su4tl-44-100-stock-t3320815
I then flashed myself back to stock, did a full wipe, then booted into stock to make sure everything worked correctly and it did. I then downloaded CM 13 and flashed it, and booted into it no problem.
*Now the issue at hand...
I then downloaded the GApps for my system, ARM/6.0/Stock and installed. Now my phone boots but when I unlock it, I get "Unfortunately, Setup Wizard has stopped" and "Unfortunately, Google Play Services has stopped". They keep popping up no matter how many times I press "ok" and prevents the use of the phone completely. I'm not sure where where to go from here. Any idea on getting over this? Wrong GApps perhaps?
BEDickey said:
*First a little background on what happened...
So due to an sight oversight on my side, and what I feel was a mistake on CMs part, I installed CM 13 over 12.1 one day on my droid turbo. I did not realize what was going on until after I had done it, it was just me keeping up with my normal updates. So I realized what had happened and used an older version of CM 12.1 that I had already downloaded and installed it. This rendered my phone unable to boot into an OS. No problem, I still had TWRP. I downloaded the flash able 5.0 stock ROM here
http://forum.xda-developers.com/droid-turbo/development/rom-su4tl-44-100-stock-t3320815
I then flashed myself back to stock, did a full wipe, then booted into stock to make sure everything worked correctly and it did. I then downloaded CM 13 and flashed it, and booted into it no problem.
*Now the issue at hand...
I then downloaded the GApps for my system, ARM/6.0/Stock and installed. Now my phone boots but when I unlock it, I get "Unfortunately, Setup Wizard has stopped" and "Unfortunately, Google Play Services has stopped". They keep popping up no matter how many times I press "ok" and prevents the use of the phone completely. I'm not sure where where to go from here. Any idea on getting over this? Wrong GApps perhaps?
Click to expand...
Click to collapse
I haven't flashed this rom for my turbo yet and this may not be the issue but in the past, dealing with other phones on CM, when you would 1st flash the rom, (& before rebooting the 1st time) you would then need to flash the gapps immediately after for everything to work properly. Try flashing the rom and gapps before rebooting.
I didn't see if the CM op instructions recommended this, just personal experiences from previous rom flashing.
I have had this happen twice after installing any CM13 on top of the March 31 nightly. I have not found a way around it yet besides doing a factory wipe after installing CM13, Open GApps and the latest radio code in this thread.
I've had plenty of experience flashing ROMs on various devices.
I've had this Kindle for a couple years now, and had an old 4.x CM ROM on it for the longest time. I recently upgraded it to a Resurrection Remix ROM and had no issues during the flashing process. I found a different ROM I want to try, and did the usual wiping routine, and I even did the format option. When I went to flash the new zip the process went faster than usual, and after reboot the RR ROM was still there. I thought that was weird, and wiped everything except internal storage and reflashed, but the old ROM is still there. When I did the factory wipe after the 4.x ROM before the RR ROM, it gave me a warning about rebooting without an OS. I can't get that to happen again (only doing this to confirm the RR ROM is gone.) What am I missing? I'm on TWRP 2.8.7.0
Whichever flashing method I use (TWRP, fastboot) Whichever rom I use (I tried clean stock, pre rooted, MM, LP, backups), I can't get past the animation screen. Even restoring a backup through TWRP gets stuck at the same spot. The only ROM that works is LineageOS (based on Android 7.1). I tried wiping various combinations of dalvik cache, data, cache, system, internal storage - still always stuck on boot animation. I tried leaving it for a long time always, the longest was over 2 hours. I feel like I'm missing wiping something since it seems like the issue is going from a 7.1 rom down maybe?
More info: I was using SLiM ROM (MM 6.0.1) for a while but it got extremely slow and poor battery life after a while. I flashed LineageOS for Z3C and it worked fine, but wasn't my cup of tea, so I wanted to go back to stock-based. I figured I'd try eXistenZ (MM 6.0.1). The instructions said to be on 23.5.A.1.291 first, then root it, and then flash the existenz zip. I didn't downgrade to .291 the first time and it didn't work. Second time I flashed a stock D5803_23.5.A.1.291 (which booted up normally). Went through the rooting process (as seen here), and that worked fine. But the next step of flashing eXistenz didn't work. I tried again from the start, but this time I couldn't boot into after flashing 23.5.A.1.291 again. This is where the problem started. I tried Slim and various roms using fastboot, various versions of twrp, and even a 6.0.1 backup through twrp. Always regardless of ROM, it gets stuck on boot animation. Except for LineageOS.
Hi, I'm in the exact same situation, I have Lineage OS 7.1 installed and I can't go back to any custom ROM based on Android 6.0 stock, all I get is always a bootloop. The only other ROM I can install is Sony stock via Flashtool. I really don't know what the problem is, please let me know if you manage to solve this weird problem.
Install old twrp, wipe /apps_log.
Or use emma to get a clean device again.
I solved the issue installing stock Android 6.0 with Flashtool, twrp 3.0.2 and then flashing ROM. :good: