well i tried multiple roms and kernels but every time and in every rom i face only problem even its not its bug but still i face whatever rom i install it reboots automatically after some time but not proper reboot its like eg -> in RR 5.7.4 its intro is "ressurction remix" then 'R' sign this comes every time not the samsung galaxy grand duos i9082 so its diff. kind of reboot and it is with every rom . i thought kernel may be a fix of it so shifted to evolution kernel 1.8.1 by k2wl and still problem persists and with stock kernel also same problem i tried every thing wiping ,flashing, etc
so if anyone know how to fix this pls reply and thnxs in advance
Related
i'm using paranoid anroid 3+ but i have some problem with my dialer , have some one got this bug like me ???
after flash this rom , i reboot my HOV but it stuck at the red text screen , i have tried to shut down my device then reboot again and again , 2 or 3 times , and it start up @@ , some time i need to reboot my device but when i do , it alway stuck at the red text screen then i do the same thing and it stat up agian @@ , have some body got this problem , or some body know how to fix it , please help me , i was search for this issue but i got nothing (sr poor english )
i'm using boot-HELLBOY-42-201302150110.img kernel
its a initial built there are many issue with this rom better to switch to other rom
gulsher said:
its a initial built there are many issue with this rom better to switch to other rom
Click to expand...
Click to collapse
thank you very much bro
Hi Xperia S users
been using XS for over 2 years with custom roms(since carbon 4.4) ... i am a regular rom flasher and i know all the flashing procedures .. i just need help with the FC's that happens when i freshly install a new Lollipop roms mainly... no matter what ... weather its a nAosp, ucyan, or Oneofakind..
i follow all procedures
The FC's happens every-time on my 1st boot itself after 5 mins or so.
if i boot rom alone without gapps then it works flawless .. no FC's whatsoever
But with gapps, it is not working for me at all .. ( i mean any gapps, Opengapps, slimgapps delta gapps .. mini,micro,pico )
have been having this issue for the last 5-6months ..i moved on to xperia z3c... but i broke the screen twice and got no money to repair it again ( wish it had the strength of the XS)
i am using the latest fota, twrp, have re-partitioned the sdcard, f2fs(cache,date) tried the sdcard but no joy with the fc's
Don't know how to get it up and running and i need a daily driver
Please help anyone
ibtihaaz said:
Hi Xperia S users
been using XS for over 2 years with custom roms(since carbon 4.4) ... i am a regular rom flasher and i know all the flashing procedures .. i just need help with the FC's that happens when i freshly install a new Lollipop roms mainly... no matter what ... weather its a nAosp, ucyan, or Oneofakind..
i follow all procedures
The FC's happens every-time on my 1st boot itself after 5 mins or so.
if i boot rom alone without gapps then it works flawless .. no FC's whatsoever
But with gapps, it is not working for me at all .. ( i mean any gapps, Opengapps, slimgapps delta gapps .. mini,micro,pico )
have been having this issue for the last 5-6months ..i moved on to xperia z3c... but i broke the screen twice and got no money to repair it again ( wish it had the strength of the XS)
i am using the latest fota, twrp, have re-partitioned the sdcard, f2fs(cache,date) tried the sdcard but no joy with the fc's
Don't know how to get it up and running and i need a daily driver
Please help anyone
Click to expand...
Click to collapse
Do try the 5.0 gapps from here. They always worked for Me, no matter which Lollipop ROM.
Or tk-gapps and remember to use twrp that came with nAOSP
Sorted for now
Mirhawk said:
Do try the 5.0 gapps from here. They always worked for Me, no matter which Lollipop ROM.
Click to expand...
Click to collapse
Tried it with the 5.0 gapps .. and i Was Amazed ... But why it does this with 5.1.1 gapps ???? ... i am so glad .. Its Alive and running with No Fc's so far ... :good:
darknessmc said:
Or tk-gapps and remember to use twrp that came with nAOSP
Click to expand...
Click to collapse
I tried the tk 5.1 a while ago and it was the same thing .. but i will try the 5.0 if they have it .... some other time
hi guys. i cannot install any custom rom like accent os lineage os and many more . if some rom boots then in that rom finger print sensor does not works like rr n xosp and back in jan and feb it was working in some roms like xosp and now it isnt . the phone just stucts at boot logo . like now now i m using miui 8 based on m .whenever i install cm 13 it shows error 7 even on cm 14 also . and when i install freedom os and accent os it shows (this package is for oneplus 3 this is a "'.. any fix u guys might know . i dont like oos the main reason is
First of all, you should read, read and search. Every thread has a search option. Second please don't start flashing crap on your phone if you littery have 0 knowledge. It's okay to be noob but at least do a little research. Now I'm trying to learn you something:
1. Go to the thread of the rom you want to flash
2. Read the entire post, double read the instructions.
3. If you still encounter any issues while you exactly did what the instructions said, then use the search option that every thread has.
4. If you still can't fix it yourself and have tried multiple times feel free to ask for help.
If you follow those steps you should fix your problem, if not READ it again... If you feel like you have tried enough I will be right here to help you
krishna:) said:
hi guys. i cannot install any custom rom like accent os lineage os and many more . if some rom boots then in that rom finger print sensor does not works like rr n xosp and back in jan and feb it was working in some roms like xosp and now it isnt . the phone just stucts at boot logo . like now now i m using miui 8 based on m .whenever i install cm 13 it shows error 7 even on cm 14 also . and when i install freedom os and accent os it shows (this package is for oneplus 3 this is a "'.. any fix u guys might know . i dont like oos the main reason is
Click to expand...
Click to collapse
Download the correct ROM for your device. A ROM meant for OP3T will not work on OP3.
Check the firmware you have currently on the device and the required firmware version for the ROM you are flashing. Fingerprint sensor not working usually means a firmware mismatch.
Keep the twrp updated.
Clean flash as much as possible.
Follow the first reply to your question - read and understand before you do anything.
Hello , everyone
First i wanna thank this guy for posting this ROM
The ROM was installed correctly and worked fine a long time even though , there're some mini issues showen like (system has been stopped / Mail has been stopped) I've made some settings to get ride of Mail has been stopped (Disable it and Delete it after )
But when i've kept my phone on charging in the night and woke up for checking it , it's only some secondes before the system shutdown without reason without even showing something else and this reboot loop continue and i can't use my phone anymore Please help me out ..
did you manage to solve it?
tberma said:
Hello , everyone
First i wanna thank this guy for posting this ROM
The ROM was installed correctly and worked fine a long time even though , there're some mini issues showen like (system has been stopped / Mail has been stopped) I've made some settings to get ride of Mail has been stopped (Disable it and Delete it after )
But when i've kept my phone on charging in the night and woke up for checking it , it's only some secondes before the system shutdown without reason without even showing something else and this reboot loop continue and i can't use my phone anymore Please help me out ..
Click to expand...
Click to collapse
I'm facing the same issue and I dont know what to do! I tried several ROMs, and problem persists!
ggonmar said:
I'm facing the same issue and I dont know what to do! I tried several ROMs, and problem persists!
Click to expand...
Click to collapse
The problem is because of a bug between the upgraded android app and CM based ROMs.
Since the problem hasn't been solved on either part. people are experiencing this on many other devices that are running CM based ROMs. Use any other ROM and you should be fine.
I too faced this problem, when I had marshmallow. Then I switched to Android KitKat ( This one https://forum.xda-developers.com/showthread.php?t=2627818 to be specific )and my phone is perfect now. Maybe galaxy grand cant handle ROMs above KitKat. I think any KitKat variant will be fine.
kundank191 said:
I too faced this problem, when I had marshmallow. Then I switched to Android KitKat ( This one https://forum.xda-developers.com/showthread.php?t=2627818 to be specific )and my phone is perfect now. Maybe galaxy grand cant handle ROMs above KitKat. I think any KitKat variant will be fine.
Click to expand...
Click to collapse
Aosp 6.0 Works fine, No bootloop like on other CM based ROMs, it's CM compatibility issue here is the link for others who want to stick to Marshmallow, this one is very stable for daily driver.
I think I have an answer. The culprit is your battery. Try a new battery and see if the problem exists. With the passage of time, the battery degrades and is no longer able to support demanding ROMs and thus the mobile shuts down.
Members please help me!!!!!!!!!......I have Samsung Grand Dous GT-I9082 ,I tried many roms ressurection remix,glade viper every time i installed whatsapp causing reboot again again any solution??????
faiz12 said:
Members please help me!!!!!!!!!......I have Samsung Grand Dous GT-I9082 ,I tried many roms ressurection remix,glade viper every time i installed whatsapp causing reboot again again any solution??????
Click to expand...
Click to collapse
the error occurs because of a cyanogenmod patch that has not yet been fixed in ROMs with Android 6.0, whenever an application is installed it goes into bootloping, wait until the rom developer fixes the patch or migrates to a more upgraded Android, or use a rom 6.0 that is not based on cyanagenmod.
Leonardoliveira said:
the error occurs because of a cyanogenmod patch that has not yet been fixed in ROMs with Android 6.0, whenever an application is installed it goes into bootloping, wait until the rom developer fixes the patch or migrates to a more upgraded Android, or use a rom 6.0 that is not based on cyanagenmod.
Click to expand...
Click to collapse
(Fortaleza, CE) Thanks friend ...i want explain some points that i installed RR 6.0.1 and open pico Gapps , Viper os 7.1 and open Gapps and Glade rom like that. Before i am using Ressurection marshmallow 6.0 the problem not occur but now i am facing this issue in Ressurection and every rom. I appreciate your help again thanks.
faiz12 said:
(Fortaleza, CE) Thanks friend ...i want explain some points that i installed RR 6.0.1 and open pico Gapps , Viper os 7.1 and open Gapps and Glade rom like that. Before i am using Ressurection marshmallow 6.0 the problem not occur but now i am facing this issue in Ressurection and every rom. I appreciate your help again thanks.
Click to expand...
Click to collapse
Buddy lets start from starting
First flash stock rom through odin
Then recovery CWM then Philz recovery
Then flash VIPER OS 7.1.2 LOOK IN DEV AREA OF THIS THREAD ITS A POST BY ME AND ITS VERY STABLE
and also respective gapps (pico)
Then step your rom like wise and must install (drive and gmail) from playstore
Install whatsapp and if u can restore backup of chats (some times due to any custom rom whatsapp backup shows its restoring but dosent restore in that case close the app from recent (make sure there is no notification of whatsaap) and again open it
It will restore
AND ALSO USE DIFF. BOOTANIMATION WATCH DOG ITS AWSOME LOOK IN THEME THREAD