Related
Hello Friend Recently I update my grand 2 to official android 4.4.2 Firmware , And The problem is that Sometimes It restarts automatically after showing BLUE SCREEN . Can anyone facing this problem ...?? Can anyone please Help me to Solve this Problem ..???
hey, let me help you.
what was the situation when this wierd thing happened?
eg. were you playing game?
or surfing internet. or any other..
was your phone rooted?
did you installed xposed framework?
(i've seen most blue screens in Xposed)
if you have installed xposed framework then either remove recently installed modules or completely remove xopsed framework.
and if your phone hasnt been rooted, and you are facing blue screen problems, i think you havent factory reseted your phone, so perform factory reset and wipe cache frome recovery..
hope this helps.
Hey Vrushabh thanls a lot for your time , This happens only sometimes like once in a week.
I had rooted my phone earlier but after this crash i formally uprooted my phone and from last 4 days it has no problem .... THANKS AGAIN BRO.
Now my question is that , what was the reason behind this type of blue screen error...?
I have the same problem with my Grand 2. It automatically got an official update 4.4.2 and since then whenever I use it for a while specially on facebook, the cell gets restarted after giving a blue screen. I have made the factory data reset and since then its a bit improved but the problem still not gone altogether. Please if you can give any solution?
DEEP1994 said:
Hello Friend Recently I update my grand 2 to official android 4.4.2 Firmware , And The problem is that Sometimes It restarts automatically after showing BLUE SCREEN . Can anyone facing this problem ...?? Can anyone please Help me to Solve this Problem ..???
Click to expand...
Click to collapse
i try to boot into the safemode but no use the blue screesn restart problem still happend
what about the new rom NI2 , saying it fix the problem , did any1 try it ?
Grand 2 Duos Bluescreen
Hi all,
I also encountered the blue screen and restart error. This happens randomly like using Whatsapp, 9gag or Facebook. It also restarts for no reason at all.
The phone is not rooted by the way. I tried running it on safe mode and nothing happened. After normally booting it, it crashed twice. First with a blue screen and the second was an automatic restart.
Thanks
I tried ni2 but no luck . blue screen and restart again
2Hourse ago i Downgrade to 4.3 and now i have not any problem.byby **** kitkat by damet samsung:
Reason of Blue Screen Death
gn_hanna said:
i try to boot into the safemode but no use the blue screesn restart problem still happend
what about the new rom NI2 , saying it fix the problem , did any1 try it ?
Click to expand...
Click to collapse
I think this happens because some times Apps are trying to write something on prohibited areas of system , and that's why OS restarts Itself to prevent data looses .
Are the people having this problem on SM-7102 and perhaps the phone bought/CSC from India?
peman2010 said:
2Hourse ago i Downgrade to 4.3 and now i have not any problem.byby **** kitkat by damet samsung:
Click to expand...
Click to collapse
Bro @peman2010, pls tell the detailed process of Downgrading from KK to JB...............
Sent from my SM-G800H using Tapatalk
SD card access permission denied
DEEP1994 said:
I think this happens because some times Apps are trying to write something on prohibited areas of system , and that's why OS restarts Itself to prevent data looses .
Click to expand...
Click to collapse
yes you are right ,
I realties that the system can't write to my SD card access permission denied
Is there any solution for this issue?
How to fix permission for both system area as you mentioned above and the SD card access
gn_hanna said:
yes you are right ,
I realties that the system can't write to my SD card access permission denied
Is there any solution for this issue?
How to fix permission for both system area as you mentioned above and the SD card access
Click to expand...
Click to collapse
no its not bcuz it cant read Sd card or something like that
it happens due to system error
and ya u can get access to sd using the xposed module
Sanjuujosephh said:
no its not bcuz it cant read Sd card or something like that
it happens due to system error
and ya u can get access to sd using the xposed module
Click to expand...
Click to collapse
On 4.4, Google bolted down write access to the external SD except the folder named Android.
SDCard Fix App
WaseemAlkurdi said:
On 4.4, Google bolted down write access to the external SD except the folder named Android.
Click to expand...
Click to collapse
did you check the SDCard Fix App
http://forum.xda-developers.com/showthread.php?t=2684188
Update:
After testing SDFix: KitKat Writable MicroSD
It is still the restart problem remains as it is although I can write to the SD card and move apps to
My device is rooted now
Is there any other solution !!??
DEEP1994 said:
Hello Friend Recently I update my grand 2 to official android 4.4.2 Firmware , And The problem is that Sometimes It restarts automatically after showing BLUE SCREEN . Can anyone facing this problem ...?? Can anyone please Help me to Solve this Problem ..???
Click to expand...
Click to collapse
I have the same error . i already flash official 4.4.2 firmware & clear all data & factory reset . but i still have the same problem .
plz let me know if anyone can solve this .
what is the best rom for the device without any issue (restart,blue screan,sdcard write access,.....)
gn_hanna said:
what is the best rom for the device without any issue (restart,blue screan,sdcard write access,.....)
Click to expand...
Click to collapse
None
My grand 2 got same problem
I have random reboots/blue screen during fb/viber/ etc..
while also watching vids via MXplayer pro
i hate it so much..
can some1 give me a detailed tutorial for downgrading to 4.3 JB? i have this prob since upgraded to kitkat
juck401 said:
I have random reboots/blue screen during fb/viber/ etc..
while also watching vids via MXplayer pro
i hate it so much..
can some1 give me a detailed tutorial for downgrading to 4.3 JB? i have this prob since upgraded to kitkat
Click to expand...
Click to collapse
You can download official FirmwareVersion from sam mobile, just google it. And flash it through Odin 3.7, i hope it will help you .
This is a Dedicated Q&A thread for Resurrection Remix Rom by quanganh2627. Please post all your Questions & all issues related with RR Rom. Any Dev or other Friends here will try to solve your issues.
Please don't tag quanganh2627 for every small issue or bug. He has lots of work to do. Don't ask for any ETA's or Update's because when ever there is one, quanganh2627 will will let us know. Kindly post all your issues here without tagging dev's.
ROM & INSTALLATION : forum.xda-developers.com/zenfone-5/development/resurrection-remix-zenfone-5-t3185403
you can use Unlocking Tool from above
Or
Unlocking Bootloader & install TWRP (Auto-installer): Install-twrp-stable-on-zenfone-5 " NOT PROMOTING ANYTHING " I found it working Efficiently
--RESERVED---
Issues :
1. Random lock when use mobile radio except 3G (sometimes i have to travel to poor signal and just got Edge)
2. After reboot the network type is WCDMA prefered, i have to set to everytime i restrart the phone on *#*#4636#*#* to lock on 3G signal
3.How to save photo on External Memory on Asus Pixel Master Camera
4.How to update Asus Keyboard ? ( on google play say asus keyboard not compatible wth the phone
5,network activity on status bar is default to NO everytime restrart the phone
BTW this is some issues i found,im using kernel beta 7.0 7.2 and Exposed V75
thanks Before
kuranzi said:
Issues :
1. Random lock when use mobile radio except 3G (sometimes i have to travel to poor signal and just got Edge)
2. After reboot the network type is WCDMA prefered, i have to set to everytime i restrart the phone on *#*#4636#*#* to lock on 3G signal
3.How to save photo on External Memory on Asus Pixel Master Camera
4.How to update Asus Keyboard ? ( on google play say asus keyboard not compatible wth the phone
5,network activity on status bar is default to NO everytime restrart the phone
BTW this is some issues i found,im using kernel beta 7.0 7.2 and Exposed V75
thanks Before
Click to expand...
Click to collapse
1. I Face random screen lock very rarely.
2. Select 3g from sim cards > sim settings.
3. Photo can't be saved to extcard as of now.
4. Place the updated apk in /system/priv-app/asuskeyboard folder, set permission to rw r r or 06 4 4 & reboot device.
5. Clear cache & dalvik cache or upgrade to 7.1.
Hey, is there anybody facing phone waking up in your pocket?
Unlocking Bootloader & install TWRP (Auto-installer): Install-twrp-stable-on-zenfone-5 " NOT PROMOTING ANYTHING " I found it working Efficiently[/QUOTE]
Open gapps works with above twrp?
FaizK said:
Unlocking Bootloader & install TWRP (Auto-installer): Install-twrp-stable-on-zenfone-5 " NOT PROMOTING ANYTHING " I found it working Efficiently
Click to expand...
Click to collapse
Open gapps works with above twrp?[/QUOTE]
Haven't tested with this twrp.....i flashed it from quang's twrp.
Just try it out..! If it fails nothing happens......if its success then you can enjoy your open gapps....
[email protected]!$h said:
Open gapps works with above twrp?
Click to expand...
Click to collapse
Haven't tested with this twrp.....i flashed it from quang's twrp.
Just try it out..! If it fails nothing happens......if its success then you can enjoy your open gapps....[/QUOTE]
As you said it is efficient ,so I thought you might have flashed the ROM and opengapps via above recovery.
I also flashed it via quann's recovery
[email protected]!$h said:
1. I Face random screen lock very rarely.
2. Select 3g from sim cards > sim settings.
3. Photo can't be saved to extcard as of now.
4. Place the updated apk in /system/priv-app/asuskeyboard folder, set permission to rw r r or 06 4 4 & reboot device.
5. Clear cache & dalvik cache or upgrade to 7.1.
Click to expand...
Click to collapse
thks before...
random lock is appear when i have poor signal, and 3g is default change to wcdma prefered after restart
FaizK said:
Haven't tested with this twrp.....i flashed it from quang's twrp.
Just try it out..! If it fails nothing happens......if its success then you can enjoy your open gapps....
As you said it is efficient ,so I thought you might have flashed the ROM and opengapps via above recovery.
I also flashed it via quann's recovery
Click to expand...
Click to collapse
I said i found it working Efficiently for unlocking bootloader..........it unlocks bootloader & installs twrp...
When I try to change music by earphone controls with the screen off, the screen lights up instead of exchanging music. Does anyone know how to fix?
This bug is present in versions 6.7, 6.9, 7.0, 7.1 and 7.2 of the RR
hey guys, i got problem when i've install l_speed_v2.3_revolution also with super su and got bootloop. i've tried to wipe the dalvik and cache, it work for an hour and reboot again by it self.
what can i do to solve this problem.? thanks.
No UI after dirty flashing Beta 7.2 with Kernel Auditor ! The Boot animation and "Upgrade in Progress" dialog did show but Android UI didn't !
I have data in internal storage so I can't wipe it ! Any tips guys ?
I flashed the zips in this order : RR ROM, OLD GAPPS, Xposed v78 and then Wipe Cache.
EDIT : When I press the power button for a few seconds for force shutdown, the power menu pops up for a few milliseconds before the device goes off
adnaanbheda said:
No UI after dirty flashing Beta 7.2 with Kernel Auditor ! The Boot animation and "Upgrade in Progress" dialog did show but Android UI didn't !
I have data in internal storage so I can't wipe it ! Any tips guys ?
I flashed the zips in this order : RR ROM, OLD GAPPS, Xposed v78 and then Wipe Cache.
EDIT : When I press the power button for a few seconds for force shutdown, the power menu pops up for a few milliseconds before the device goes off
Click to expand...
Click to collapse
Try to Connect your device to PC & copy your data......
Fernando0258 said:
When I try to change music by earphone controls with the screen off, the screen lights up instead of exchanging music. Does anyone know how to fix?
This bug is present in versions 6.7, 6.9, 7.0, 7.1 and 7.2 of the RR
Click to expand...
Click to collapse
@tank0412 bro.....do you know how to Fix it?
sorry, now i've back to my kitkat stock rom due my device usually reboot after several minutes in RR 7.2 and want to go to RR again. Do i have to install lollypop first or just straight install RR.? thx
ekinodermata said:
sorry, now i've back to my kitkat stock rom due my device usually reboot after several minutes in RR 7.2 and want to go to RR again. Do i have to install lollypop first or just straight install RR.? thx
Click to expand...
Click to collapse
If u r not facing any screen freeze due to unlocking boot loader........ U can directly upgrade to RR......
[email protected]!$h said:
If u r not facing any screen freeze due to unlocking boot loader........ U can directly upgrade to RR......
Click to expand...
Click to collapse
yeah thx, it works.
adnaanbheda said:
No UI after dirty flashing Beta 7.2 with Kernel Auditor ! The Boot animation and "Upgrade in Progress" dialog did show but Android UI didn't !
I have data in internal storage so I can't wipe it ! Any tips guys ?
I flashed the zips in this order : RR ROM, OLD GAPPS, Xposed v78 and then Wipe Cache.
EDIT : When I press the power button for a few seconds for force shutdown, the power menu pops up for a few milliseconds before the device goes off
Click to expand...
Click to collapse
Maybe it has something todo with Auto Brightness and you set it so Low before you upgrade it to 7.2 because i noticed there's that bug in that version , i suggest to flash Multifunctional Kernel by X AnwarMov but if you want the Stock RR ROM kernel then flash it , fix the auto brightness ( by set the brightness slider to middle or really high and turning the auto off ) and then reflash the RR ROM stock kernel
[email protected]!$h said:
Try to Connect your device to PC & copy your data......
Click to expand...
Click to collapse
You Know , you still able to connect via USB to computer from TWRP Recovery ( Dec Build ) By Quanganh just look for the option ( this will make the proses easier ) , but so far as i remember if you want to backup the internal memory you have to boot normal and plug the USB ( Depend if your device if locked )
Sorry for Late Answering
and as you know this is according to my logic so correct me if i'm wrong
RevanEphys said:
Maybe it has something todo with Auto Brightness and you set it so Low before you upgrade it to 7.2 because i noticed there's that bug in that version , i suggest to flash Multifunctional Kernel by X AnwarMov but if you want the Stock RR ROM kernel then flash it , fix the auto brightness ( by set the brightness slider to middle or really high and turning the auto off ) and then reflash the RR ROM stock kernel
You Know , you still able to connect via USB to computer from TWRP Recovery ( Dec Build ) By Quanganh just look for the option ( this will make the proses easier ) , but so far as i remember if you want to backup the internal memory you have to boot normal and plug the USB ( Depend if your device if locked )
Sorry for Late Answering
and as you know this is according to my logic so correct me if i'm wrong
Click to expand...
Click to collapse
You're right It was due to the auto brightness setting ! I turned it off and everything turned out fine. Anyway, I've switched to a stock based custom ROM for the time being, I'll definitely come back for RR 5.6 !
Plz help me!!!!
Im installing custom rom in sm core prime 360H via twrp but its shows error number7
How to fix it..???
Any one help me plz i need it
Probably your internal storage if full or something. Which ROM were you installing anyway?
rms112 said:
Probably your internal storage if full or something. Which ROM were you installing anyway?
Click to expand...
Click to collapse
I tried every custom rom but same issue
Error code 7
My phone storage is almost 70%free
Plz help me to solv this
Are you sure you're using ROM built ONLY for G360H? None of us faced that error. Also remember Roms made for other device won't work and you may hard brick your device.
See here for more.
https://forum.xda-developers.com/showthread.php?t=2522762
rms112 said:
Are you sure you're using ROM built ONLY for G360H? None of us faced that error. Also remember Roms made for other device won't work and you may hard brick your device.
See here for more.
https://forum.xda-developers.com/showthread.php?t=2522762
Click to expand...
Click to collapse
Yes in 100% sure its 360H stock rom
I also try ins and inu both stock rom but issue is same
Can u tell me which stock are you use
Bdw are you indian....? Because my English is lil bit week?
rms112 said:
Are you sure you're using ROM built ONLY for G360H? None of us faced that error. Also remember Roms made for other device won't work and you may hard brick your device.
See here for more.
https://forum.xda-developers.com/showthread.php?t=2522762
Click to expand...
Click to collapse
I use this method also which is given in link but same issue ?
Idk man. You should probably try flashing official stock firmware using Odin. Its really easy. Then flash twrp by dreamstar. And start flashing custom ROMs.
I was on stock of Saudi Arabia. But I never used it after we got various CM builds..
I am on RR 5.8.3 by hash now.
Thnx for ideas
my problem solved
Now Installed lineage 7.1
Bdw how to close this Thread ?
rms112 said:
Idk man. You should probably try flashing official stock firmware using Odin. Its really easy. Then flash twrp by dreamstar. And start flashing custom ROMs.
I was on stock of Saudi Arabia. But I never used it after we got various CM builds..
I am on RR 5.8.3 by hash now.
Click to expand...
Click to collapse
RR 5.8.3 working fine
I trywd this but home button and resent apps cnt shows
Any idea about it...
rms112 said:
Idk man. You should probably try flashing official stock firmware using Odin. Its really easy. Then flash twrp by dreamstar. And start flashing custom ROMs.
I was on stock of Saudi Arabia. But I never used it after we got various CM builds..
I am on RR 5.8.3 by hash now.
Click to expand...
Click to collapse
RR 5.8.3 working fine ??
I trywd this but home button and resent apps cnt shows
Any idea about it...
Works fine with me. RR beta 1 based on 7.1.2.
You should ask on that thread of ROM. Maybe hash can help you!
Good luck.
Help i'm not sure but i think i might have bricked my sm-g360h.
HELP I'M NOT SURE BUT I THINK I MIGHT HAVE BRICKED MY SM-G360H. When i had some issues with my phone, I used twrp to flash cyanogenmod 12 custom rom on my phone some two weeks ago and it flashed properly. After a number of issues, i decided i wanted to go back to the stock rom. so i downloaded the firmware from sammobile, installed odin and flashed it with odin. when the flashing was done successfully, my phone rebooted instead of giving me the screen of a newly launched phone it went to the home screen, and had a pattern lock screen and tried my pattern lock from when i was on cyanogenmod 12 and it unlocked it. and gave me the screen of a newly lauched phone but before i could continue with startup, it rebooted immediately and each time it get to the lock screen, it goes to the screen with the samsung logo after some few seconds and then come back to the lock screen please help what do i do?
PS: one of the issues i had that made me want to return to the stock rom was the fact that i couldn't change my screen lock to none or swipe after i decided to use pattern on the cyanogenmod
yemialabipurpose said:
HELP I'M NOT SURE BUT I THINK I MIGHT HAVE BRICKED MY SM-G360H. When i had some issues with my phone, I used twrp to flash cyanogenmod 12 custom rom on my phone some two weeks ago and it flashed properly. After a number of issues, i decided i wanted to go back to the stock rom. so i downloaded the firmware from sammobile, installed odin and flashed it with odin. when the flashing was done successfully, my phone rebooted instead of giving me the screen of a newly launched phone it went to the home screen, and had a pattern lock screen and tried my pattern lock from when i was on cyanogenmod 12 and it unlocked it. and gave me the screen of a newly lauched phone but before i could continue with startup, it rebooted immediately and each time it get to the lock screen, it goes to the screen with the samsung logo after some few seconds and then come back to the lock screen please help what do i do?
PS: one of the issues i had that made me want to return to the stock rom was the fact that i couldn't change my screen lock to none or swipe after i decided to use pattern on the cyanogenmod
Click to expand...
Click to collapse
Sounds like problem of dirty flash not hard brick.
Here's what you should do.
1) go to twrp recovery using power + vol up
2) wipe everything except storage
3) Flash cm 13 beta 5 or 6 ( the latest beta) or lineage OS or RR
4) if the problem still exists, then used Odin to flash stock ROM and repeat steps 1 to 3
Also don't use cm 12. Its EOF and you won't get any bug fixes and updates.
Hello Guys.
Im in dire need of help actually. Ive recently rooted my galaxy grand 2 running 4.4.2 KK and set it up with twrp v3.1.
yet im having the issue when i install a custom rom.
1.) Cyanogenmod - MM
When i install the rom, it installs and and on 1st reboot it optimizes all the apps yet gets stuck on "starting apps". when i force restarted it, it boots till the welcome screen to select the language but then the touch screen stops responding but its not stuck as pressing the power button turns off the screen and back on and also on long press reboot options appear , which on the other hand responds to touch. so im guessing its not the touch screen issue? but then ive noticed that apps also crash while im on the welcome screen.
2. Resurrection remix - MM
Same issue yet this passes the starting apps screen and goes to the home screen directly but only to be found that the screen isnt responding.
this is very weird because of all the phones ive installed custom rom on, this is the first case im having such trouble.
could it be because knox is installed? i tried getting rid of it from the stock rom but everytime i try that i cant boot back up because it gets stuck at the samsung logo.
can some one help me quick because this is really irritating.
Thanks.
Maybe its realy screen problem... did the touch screen works on twrp
fire_onCA said:
Maybe its realy screen problem... did the touch screen works on twrp
Click to expand...
Click to collapse
Yes It Does. Its not the screen issue because on stock rom everything works properly.
Im guessing somethings interrupting with the OS, causing the apps to crash.
aymanabdulla said:
Hello Guys.
Im in dire need of help actually. Ive recently rooted my galaxy grand 2 running 4.4.2 KK and set it up with twrp v3.1.
yet im having the issue when i install a custom rom.
1.) Cyanogenmod - MM
When i install the rom, it installs and and on 1st reboot it optimizes all the apps yet gets stuck on "starting apps". when i force restarted it, it boots till the welcome screen to select the language but then the touch screen stops responding but its not stuck as pressing the power button turns off the screen and back on and also on long press reboot options appear , which on the other hand responds to touch. so im guessing its not the touch screen issue? but then ive noticed that apps also crash while im on the welcome screen.
2. Resurrection remix - MM
Same issue yet this passes the starting apps screen and goes to the home screen directly but only to be found that the screen isnt responding.
this is very weird because of all the phones ive installed custom rom on, this is the first case im having such trouble.
could it be because knox is installed? i tried getting rid of it from the stock rom but everytime i try that i cant boot back up because it gets stuck at the samsung logo.
can some one help me quick because this is really irritating.
Thanks.
Click to expand...
Click to collapse
Flash twrp 3.0.0 (over your existing twrp 3.1). Just copy the twrp.zip to your root directory of internal storage and flash using twrp 3.1. Maybe that will help because it helped me.
mfaisal98 said:
Flash twrp 3.0.0 (over your existing twrp 3.1). Just copy the twrp.zip to your root directory of internal storage and flash using twrp 3.1. Maybe that will help because it helped me.
Click to expand...
Click to collapse
but I've already tried that! I started off with 3.0 and when that didn't work I moved to 3.1!
I also noticed I get a small message on top when. I start the phone with the Samsung logo saying that something isn't seandroid when I install a custom room but it isn't like an error or something.
Could the issue be with the kernal?
Or should I try cwm recovery now?
aymanabdulla said:
but I've already tried that! I started off with 3.0 and when that didn't work I moved to 3.1!
I also noticed I get a small message on top when. I start the phone with the Samsung logo saying that something isn't seandroid when I install a custom room but it isn't like an error or something.
Could the issue be with the kernal?
Or should I try cwm recovery now?
Click to expand...
Click to collapse
If you get some error message on boot while there is the Samsung logo then there is something wrong! Now you should:
1. Flash the stock rom (to correct that error message on boot)
2. Flash recovery
3. Root (SuperSU 2.82)
4. Continue with the installation (thru twrp 3.0.0) of 6.0.1 but before that:
(a) Factory reset
(b) Wipe data
(c) Wipe cache
(d) Wipe dalvik cache)
(e) DO NOT WIPE THE SYSTEM!
Goog luck
I suggest flashing the stock 4.4.2 ROM via Odin and then start everything from scratch. Currently facing the same problem after flashing the Ressurection Remix M 5.7.4.
mfaisal98 said:
If you get some error message on boot while there is the Samsung logo then there is something wrong! Now you should:
1. Flash the stock rom (to correct that error message on boot)
2. Flash recovery
3. Root (SuperSU 2.82)
4. Continue with the installation (thru twrp 3.0.0) of 6.0.1 but before that:
(a) Factory reset
(b) Wipe data
(c) Wipe cache
(d) Wipe dalvik cache)
(e) DO NOT WIPE THE SYSTEM!
Goog luck
Click to expand...
Click to collapse
Its not actually an error message but a small notice on the top left corner.
When I restore my official rom back the message is normally gone.
But I will try again with ur advice again because I always wipe system before flashing the rom so it could be causing the issue.
Thanks I'll let u know what happens
kaiserfakinaway said:
I suggest flashing the stock 4.4.2 ROM via Odin and then start everything from scratch. Currently facing the same problem after flashing the Ressurection Remix M 5.7.4.
Click to expand...
Click to collapse
I did do that. I have the official stock rom running now since RR and cyanogenmod isn't responding.
aymanabdulla said:
I did do that. I have the official stock ROM running now since RR and CyanogenMod isn't responding.
Click to expand...
Click to collapse
Have you tried flashing RR or CM13 after flashing the stock ROM?
and could you give me the full name of the stock ROM?
aymanabdulla said:
Hello Guys.
Im in dire need of help actually. Ive recently rooted my galaxy grand 2 running 4.4.2 KK and set it up with twrp v3.1.
yet im having the issue when i install a custom rom.
1.) Cyanogenmod - MM
When i install the rom, it installs and and on 1st reboot it optimizes all the apps yet gets stuck on "starting apps". when i force restarted it, it boots till the welcome screen to select the language but then the touch screen stops responding but its not stuck as pressing the power button turns off the screen and back on and also on long press reboot options appear , which on the other hand responds to touch. so im guessing its not the touch screen issue? but then ive noticed that apps also crash while im on the welcome screen.
2. Resurrection remix - MM
Same issue yet this passes the starting apps screen and goes to the home screen directly but only to be found that the screen isnt responding.
this is very weird because of all the phones ive installed custom rom on, this is the first case im having such trouble.
could it be because knox is installed? i tried getting rid of it from the stock rom but everytime i try that i cant boot back up because it gets stuck at the samsung logo.
can some one help me quick because this is really irritating.
Thanks.
Click to expand...
Click to collapse
Did you flashed the vendor.zip provided after flashing the rom?If not,then it is the cause of that problem
kaiserfakinaway said:
Have you tried flashing RR or CM13 after flashing the stock ROM?
and could you give me the full name of the stock ROM?
Click to expand...
Click to collapse
Yes, thats what i did.
G7102DDUBNK1_G7102ODDBNK1_G7102DDUBNK1_HOME.tar.md5 this was the file name. it works fine i guess, had some issues with the sim as the phone keeps on asking to reboot but no other issues.
Subhashis said:
Did you flashed the vendor.zip provided after flashing the rom?If not,then it is the cause of that problem
Click to expand...
Click to collapse
Yes i did. as well as the front cam + patch fix. i flashed both yet still the same issue.
mfaisal98 said:
If you get some error message on boot while there is the Samsung logo then there is something wrong! Now you should:
1. Flash the stock rom (to correct that error message on boot)
2. Flash recovery
3. Root (SuperSU 2.82)
4. Continue with the installation (thru twrp 3.0.0) of 6.0.1 but before that:
(a) Factory reset
(b) Wipe data
(c) Wipe cache
(d) Wipe dalvik cache)
(e) DO NOT WIPE THE SYSTEM!
Goog luck
Click to expand...
Click to collapse
Ok i tried this with the steps u have told me. still no luck
i went to twrp opened wipe, wiped dalvik cache, cache, internal storage and data. but not the system.
same issue. also the small message which comes in the top left corner is
"Kernal is not seandroid enforcing" red colour font
"set warranty bit : kernal" yellow colour font
why is this shown?
should i try cwm?
So I have been trying various ROMs and found out that this problem only exists on MM ROMs. RR-M and CM13 both starts but system stops responding completely. But RR-N and CM14.1/12.1/12 are working flawlessly.
---------- Post added at 08:05 AM ---------- Previous post was at 08:03 AM ----------
aymanabdulla said:
Ok i tried this with the steps u have told me. still no luck
i went to twrp opened wipe, wiped dalvik cache, cache, internal storage and data. but not the system.
same issue. also the small message which comes in the top left corner is
"Kernal is not seandroid enforcing" red colour font
"set warranty bit : kernal" yellow colour font
why is this shown?
should i try cwm?
Click to expand...
Click to collapse
That small message is not a problem. It is showing because the kernel is not selinux enforcing.
kaiserfakinaway said:
So I have been trying various ROMs and found out that this problem only exists on MM ROMs. RR-M and CM13 both starts but system stops responding completely. But RR-N and CM14.1/12.1/12 are working flawlessly.
---------- Post added at 08:05 AM ---------- Previous post was at 08:03 AM ----------
That small message is not a problem. It is showing because the kernel is not selinux enforcing.
Click to expand...
Click to collapse
Why Doesnt any one else have this problem?
oh is it? what about lineage os 13.1 running MM?
Fine i have put cm12.1 for download, will flash it and let u know what happened.
Fingers Crossed
kaiserfakinaway said:
So I have been trying various ROMs and found out that this problem only exists on MM ROMs. RR-M and CM13 both starts but system stops responding completely. But RR-N and CM14.1/12.1/12 are working flawlessly.
---------- Post added at 08:05 AM ---------- Previous post was at 08:03 AM ----------
That small message is not a problem. It is showing because the kernel is not selinux enforcing.
Click to expand...
Click to collapse
Thank You So MUCH.....
The issue was with the MM roms, because cm12.1 seems to be working perfectly, although not the camera. could someone tell me what about that now?
what now should we close this thread or figure out why MM isnt working on this device? Kernal Issue?
Could someone also check if the Lineage os with MM works or not?
Thanks again.
aymanabdulla said:
Thank You So MUCH.....
The issue was with the MM roms, because cm12.1 seems to be working perfectly, although not the camera. could someone tell me what about that now?
what now should we close this thread or figure out why MM isnt working on this device? Kernal Issue?
Could someone also check if the Lineage os with MM works or not?
Thanks again.
Click to expand...
Click to collapse
Have you tried any TW MM ports like J7 Hybrid MM Heavily Debloated Port or [ROM][6.0.1][TW][Electron Rom][Version 1] or [ROM][6.0.1][TW] JSERROM Version 3.1 [BETA][ms013g]?
kaiserfakinaway said:
Have you tried any TW MM ports like J7 Hybrid MM Heavily Debloated Port or [ROM][6.0.1][TW][Electron Rom][Version 1] or [ROM][6.0.1][TW] JSERROM Version 3.1 [BETA][ms013g]?
Click to expand...
Click to collapse
Nope, all of them have camera issues too.
but im sure there will be a fix for this, since its running LOLLIPOP.
I'll let u know.
aymanabdulla said:
Thank You So MUCH.....
The issue was with the MM roms, because cm12.1 seems to be working perfectly, although not the camera. could someone tell me what about that now?
what now should we close this thread or figure out why MM isnt working on this device? Kernal Issue?
Could someone also check if the Lineage os with MM works or not?
Thanks again.
Click to expand...
Click to collapse
Might not be a kernel issue because I have also tried with this custom kernel [KERNEL][5.x/TW/6.x]Infected Kernel R4[15-05-2016] and still the same.
Last few days I tried to use custom ROM. Volte doesn't work. I've given up on that issue now. Now problem is Miui pro.
After flashing it keeps showing boot logo ( I waited for more than 30 minutes) but the older version (7... Something) flashes without any problem.
How long should I wait to complete it's booting process( more than an hour??!!!!!)
P.s- device encryption is enabled [ but I don't think it's causing the problem cuz older version is doing fine]
http://miuiid.blogspot.in/p/rom.html?m=1
Download this and flash like normal rom.
First clear data, dv-cache, system,
Then flash this along with magisk
After flash don't clear dv-cache, not even after flashing magisk and dont change anythink in the system partition untill first boot u can also flash the magisk modules straight ahead.
This is miui id best, u get paid themes free, also volte working and it does have split screen.
Note:- don't forget to flash magisk, don't clear cache after flashing the rom and i mean anytime don't do it it will take a lot of time then.
First boot will take 15 min, dont wait for it once it gets past the boot logo and enters the bootanimation wait for 2 min then again do force reboot by long pressing the power button, do it one more time this time wait for 5 min if it opens then good or again reboot. This time it will happen.
The rom is stable and totally worth the trouble.
This process is just to reduce the first booting time.
Thanks ?
Also check this post for more information.
Link:- https://forum.xda-developers.com/xi...t/arvanasoft-miui-9-7-10-20-redmi-3s-t3694036
Thanks.
Im running Miui 9.2 global stable 9.2.2.0
Can i do dirty install? I dont wanna lose apps data
Im using stock miui global stable 9.2.2. Android 6.0
If i wanna install miui id, do i need to wipe all , as in format my handset. Or is it ok to just wipe system, cache dv? I dont wanna lose my apps data
@Trovies hi,
Just do titanium or swiftbackup search the apk in google, and u can do dirty flash but i will not recommend it.
Note :- download the premium version of the swiftbackup from the internet.
Thanks
Flash lazyflasher.zip
Sagar_zac said:
http://miuiid.blogspot.in/p/rom.html?m=1
Download this and flash like normal rom.
First clear data, dv-cache, system,
Then flash this along with magisk
After flash don't clear dv-cache, not even after flashing magisk and dont change anythink in the system partition untill first boot u can also flash the magisk modules straight ahead.
This is miui id best, u get paid themes free, also volte working and it does have split screen.
Note:- don't forget to flash magisk, don't clear cache after flashing the rom and i mean anytime don't do it it will take a lot of time then.
First boot will take 15 min, dont wait for it once it gets past the boot logo and enters the bootanimation wait for 2 min then again do force reboot by long pressing the power button, do it one more time this time wait for 5 min if it opens then good or again reboot. This time it will happen.
The rom is stable and totally worth the trouble.
This process is just to reduce the first booting time.
Thanks
Click to expand...
Click to collapse
very well explained. As per habit I was clearing both dv cache and cache and due to this rom was taking too much time to boot. But after reading your post I have made clear pretty much everything. This is the best MIUI rom I have ever used. Performance, battery life, smoothness everything is spot on. I just wish it would had double tap to wake feature and recent apps menu would had icon mode option. Audio through earphones is also low. other than that its fantastic rom.
https://forum.xda-developers.com/xi...t/arvanasoft-miui-9-7-10-20-redmi-3s-t3694036
Vinayakn73 said:
very well explained. As per habit I was clearing both dv cache and cache and due to this rom was taking too much time to boot. But after reading your post I have made clear pretty much everything. This is the best MIUI rom I have ever used. Performance, battery life, smoothness everything is spot on. I just wish it would had double tap to wake feature and recent apps menu would had icon mode option. Audio through earphones is also low. other than that its fantastic rom.
https://forum.xda-developers.com/xi...t/arvanasoft-miui-9-7-10-20-redmi-3s-t3694036
Click to expand...
Click to collapse
Well u don't get everything but the things you mentioned i don't use it. So... Good for me right. ?For the audio problem use Dolby from the magisk repo the lenovo A7000 one the others don't work. Just flash the settings zip after flashing the rom and don't clear cache
Sagar_zac said:
Well u don't get everything but the things you mentioned i don't use it. So... Good for me right. For the audio problem use Dolby from the magisk repo the lenovo A7000 one the others don't work. Just flash the settings zip after flashing the rom and don't clear cache
Click to expand...
Click to collapse
well I'm using viper4android but with it audio quality increased but volume decreased further, I think I can live up with it. After flashing settings zip I did everything as you mentioned (did not clear dvk cache or cache) but now rom is stuck on mi logo (almost 20 to 25 minutes) can I dirty flash rom again???? Or do I need to do clean install??
Vinayakn73 said:
well I'm using viper4android but with it audio quality increased but volume decreased further, I think I can live up with it. After flashing settings zip I did everything as you mentioned (did not clear dvk cache or cache) but now rom is stuck on mi logo (almost 20 to 25 minutes) can I dirty flash rom again???? Or do I need to do clean install??
Click to expand...
Click to collapse
Just do a clean flash, rom + settings zip, together like do a batch. Then no clear cache boot and do the process
Sagar_zac said:
Just do a clean flash, rom + settings zip, together like do a batch. Then no clear cache boot and do the process
Click to expand...
Click to collapse
yup I'm not noob and doing exactly as you are saying but still I'm struggling with this rom
1st attempt wipe dalvik, system, data cache - flashed rom - flashed settings zip - flashed magisk - tried to flash magisk modules (failed) - reboot without any wipe - rom didn't boot
2nd attempt - clean installed with only rom and settings zip - booted normally - went to bootloader again installed magisk - reboot system - went in bootloader again - flashed app systemizer module- rebooted successfully - went to magisk manager and added module youtube advanced - reboot stuck on mi logo
3rd attempt - reinstalled clean as described in 2nd attempt till the setup of app sytemizer on reboot - went to app systemizer module and ticked gps app- module asked to reboot boooooom stuck on mi logo
Everything I wrote above is my common practice with every miui rom but I don't know why It is not working with this rom. anyways thanks for your help I am moving to global stable as I can't live without these modules. n sorry for bad english
Vinayakn73 said:
yup I'm not noob and doing exactly as you are saying but still I'm struggling with this rom
1st attempt wipe dalvik, system, data cache - flashed rom - flashed settings zip - flashed magisk - tried to flash magisk modules (failed) - reboot without any wipe - rom didn't boot
2nd attempt - clean installed with only rom and settings zip - booted normally - went to bootloader again installed magisk - reboot system - went in bootloader again - flashed app systemizer module- rebooted successfully - went to magisk manager and added module youtube advanced - reboot stuck on mi logo
3rd attempt - reinstalled clean as described in 2nd attempt till the setup of app sytemizer on reboot - went to app systemizer module and ticked gps app- module asked to reboot boooooom stuck on mi logo
Everything I wrote above is my common practice with every miui rom but I don't know why It is not working with this rom. anyways thanks for your help I am moving to global stable as I can't live without these modules. n sorry for bad english
Click to expand...
Click to collapse
Ya i know modules can be a pain in the ass only one suggestion when ever after flashing a module if its stuck in the bootloop then just use magisk Uninstaller then again install Magisk or use magisk for recovery to remove the particular module which is causing boot loop also use root youtube valence and use universal installer it will not cause bootloop. Also use minimal module only what you need. Ok then. Also do as u discreet i am fine in this rom. And its great. ?
See my modules
I too use YouTube vanced.
Man u got to find solutions not give up and change only after a few attempts. U know how many times i got bootloop because of this rom and it's compatibility issues with the modules. After many attempts i got it. Now its the best custom miui rom ever also the dev is constant and hops to bring miui 10. Also if u have used this rom only for a few hours u can realize the difference.
Sagar_zac said:
I too use YouTube vanced.
Man u got to find solutions not give up and change only after a few attempts. U know how many times i got bootloop because of this rom and it's compatibility issues with the modules. After many attempts i got it. Now its the best custom miui rom ever also the dev is constant and hops to bring miui 10. Also if u have used this rom only for a few hours u can realize the difference.
Click to expand...
Click to collapse
yup there is no doubt this is best custom miui rom out there. But this bootloop and boot time driving me nuts. I wonder why all this problems are popping up though the rom is based on official firmware and I've never faced such problem with official roms. I will give it a try again after two days. I just hope that time it will go smooth.