Related
This is my first post here so please excuse any violation of rules.
So, I was running CWM recovery + Siyah kernel + CM10.1 + Touchwiz 4.1.2 (dual boot setup) perfectly fine on my Galaxy s 3 for almost a year. But yesterday I decided to update all of those and updated to latest CWM using ROM manager, then changed the kernel to googy max2 and installed CM11. Everything worked properly except that my phone would freeze or hang up randomly at any time(whether swiping through homescreens or updating apps or even during standby). So I changed my ROM to S4 Revoution ROM (tried with both googy max2 and devil kernel). However, even this ROM gave me same hangup problems. So I moved onto TWRP recovery+ OmniRom but still encountered the same problem multiple times. After getting tired of wasting so much time, I came back to my original setup of CWM+Siyah kernel+CM10.1 thinking I wouldn't face this problem again, but to my aghast, the phone would still freeze randomly. Only a power button reboot would help. Please help, I have no idea what might be causing the problem as I have successfully tried every combination of recovery, kernel and ROM but to no avail. And no, I never manually tinkered with any CPU/GPU frequencies or voltages. Your time and help is greatly appreciated, Thank you.
PS: One more very important thing I forgot to mention, CPU-Z shows most of the time all 4 cores of the CPU stay at 1400MHz even though minimum speed is 200MHz. I have noticed this in S4 revolution ROM with googy max2 kernel and pegasusq governor(currently using this setup on my phone). Also, the "devil kernel" app on this ROM shows CPU either stays in deep sleep mode or 1300-1400MHz frequency.
Can't take screenshot for some reason in this ROM otherwise I would have uploaded those too. Thank you.
newoverhere said:
This is my first post here so please excuse any violation of rules.
So, I was running CWM recovery + Siyah kernel + CM10.1 + Touchwiz 4.1.2 (dual boot setup) perfectly fine on my Galaxy s 3 for almost a year. But yesterday I decided to update all of those and updated to latest CWM using ROM manager, then changed the kernel to googy max2 and installed CM11. Everything worked properly except that my phone would freeze or hang up randomly at any time(whether swiping through homescreens or updating apps or even during standby). So I changed my ROM to S4 Revoution ROM (tried with both googy max2 and devil kernel). However, even this ROM gave me same hangup problems. So I moved onto TWRP recovery+ OmniRom but still encountered the same problem multiple times. After getting tired of wasting so much time, I came back to my original setup of CWM+Siyah kernel+CM10.1 thinking I wouldn't face this problem again, but to my aghast, the phone would still freeze randomly. Only a power button reboot would help. Please help, I have no idea what might be causing the problem as I have successfully tried every combination of recovery, kernel and ROM but to no avail. And no, I never manually tinkered with any CPU/GPU frequencies or voltages. Your time and help is greatly appreciated, Thank you.
Click to expand...
Click to collapse
Did you do a complete wipe before installing all these roms? Wipe Dalvik Cache and Cache partition. I am running WanamLite 7.3 with stock kernel and Wanam Xposed. Here is the link to the rom - http://forum.xda-developers.com/showthread.php?t=1705866
Reboot into custom recovery. Do a full wipe, even though this rom says that it is not necessary but it is always a good idea to do a full wipe before flashing. Try this out and let's try to fix your problem.
Hamza18 said:
Did you do a complete wipe before installing all these roms? Wipe Dalvik Cache and Cache partition. I am running WanamLite 7.3 with stock kernel and Wanam Xposed. Here is the link to the rom - http://forum.xda-developers.com/showthread.php?t=1705866
Reboot into custom recovery. Do a full wipe, even though this rom says that it is not necessary but it is always a good idea to do a full wipe before flashing. Try this out and let's try to fix your problem.
Click to expand...
Click to collapse
Yes, and not just once, but every time I flashed a new ROM. I'm thinking my only option now is to unroot and go back to stock but i am unable to find my country's rom. (found one on sammobile but the download speed refuses to go beyond 2-3kbps).
One more very important thing I forgot to mention, CPU-Z shows most of the time all 4 cores of the CPU stay at 1400MHz even though minimum speed is 200MHz. I have noticed this in S4 revolution ROM with googy max2 kernel and pegasusq governor. Also, the "devil kernel" app on this ROM shows CPU either stays in deep sleep mode or 1300-1400MHz frequency.
Can't take screenshot for some reason in this ROM otherwise I would have uploaded those too. Thank you.
newoverhere said:
One more very important thing I forgot to mention, CPU-Z shows most of the time all 4 cores of the CPU stay at 1400MHz even though minimum speed is 200MHz. I have noticed this in S4 revolution ROM with googy max2 kernel and pegasusq governor. Also, the "devil kernel" app on this ROM shows CPU either stays in deep sleep mode or 1300-1400MHz frequency.
Can't take screenshot for some reason in this ROM otherwise I would have uploaded those too. Thank you.
Click to expand...
Click to collapse
Try WanamLite 7.3. Use the link I gave. And install it after doing a complete wipe. See if that makes a difference.
Hamza18 said:
Try WanamLite 7.3. Use the link I gave. And install it after doing a complete wipe. See if that makes a difference.
Click to expand...
Click to collapse
Thank you for the suggestion but i'm afraid that would not help as i have already tried 4 different roms, one of which i used for a year without any problem, but still facing the hangup only since yesterday. plus, I have gone through enough trouble restoring my accounts/apps/contacts and all (especially whatsapp) again and again for the whole of yesterday every time i flashed a new rom. the problem is not related to the rom. thank you, again.
pertsky makes
newoverhere said:
Thank you for the suggestion but i'm afraid that would not help as i have already tried 4 different roms, one of which i used for a year without any problem, but still facing the hangup only since yesterday. plus, I have gone through enough trouble restoring my accounts/apps/contacts and all (especially whatsapp) again and again for the whole of yesterday every time i flashed a new rom. the problem is not related to the rom. thank you, again.
Click to expand...
Click to collapse
See, most of the things in your phone are software related. It is very very rare that you might have damaged the hardware. I see mismanagement of the resources by the ROM or kernel in your phone. What are the steps you are doing when installing a new ROM and which custom recovery are you using?
Full wipe flash stock rom and test ,
Read the FREEZING sticky and SDS sticky .
JJEgan said:
Full wipe flash stock rom and test ,
Read the FREEZING sticky and SDS sticky .
Click to expand...
Click to collapse
I did a full wipe, flashed everything again, did the emmc check as well as the dummy file generator thing....the hangups have reduced to 2-3 per day from 2-3 per hour but are still there. Should I downgrade my cwm recovery?
If you are rooted try the COMPLETE unrooting procedure mentioned at various places by flashing the latest stock firmware available from sammobile. This is to make sure your device software is like brand new. Test it for at least a day. Do a mega wipe (erasing everything even on internal SD card) before which can fix it in some cases.
When rooting again make sure you have the most bug free version of the recovery. CWM 6.0.4.4 is known to have minor problems here and there but nothing concerning to this topic.
~DemonLord~ said:
If you are rooted try the COMPLETE unrooting procedure mentioned at various places by flashing the latest stock firmware available from sammobile. This is to make sure your device software is like brand new. Test it for at least a day. Do a mega wipe (erasing everything even on internal SD card) before which can fix it in some cases.
When rooting again make sure you have the most bug free version of the recovery. CWM 6.0.4.4 is known to have minor problems here and there but nothing concerning to this topic.
Click to expand...
Click to collapse
Hi guys, I experience the same problems: I'm in any app and I press home to go back to the home menu => my phone's freezing for 5 seconds and then I see all my icons/folders/widgets slowly appearing. I would like to know how to complete format my internal SD card like you said. Thanks in advance.
by pressing the powerkey+homebutton+volume up for about 8-10 seconds you are taken to a recovery menu. You can choose to factory reset over there. That fixed problems in most cases. The only way to wipe the internal partition as well would be to install stock firmware which is a part of unrooting, this will erase everything and put a original rom in your phone.. You can follow the unrooting processes written in many posts in xda
Ok thanks for this quick answer ! So the only way to erase the internal SD card is the unrooting method?
Radder124 said:
Ok thanks for this quick answer ! So the only way to erase the internal SD card is the unrooting method?
Click to expand...
Click to collapse
As far as i know yes. Its not any trouble at all, wont take much time, except the firmware you would have to download. Its not needed in most cases. As i said before you may only need a factory reset so try that before! And just hit the thanks button
Hi, I'm sorry for my bad English, I'm with 1 Moto And first generation that after being looped I was able to unblock and install TWP, and put the Lolipop Rom 5.1, installed without errors, but when I started the android, I set it up and then when I restarted it Device it enters that white screen that appears that the bootloader was unlocked and falls straight into TWRP, does not start Android at all, could they help me? thanks
Nikakz said:
Hi, I'm sorry for my bad English, I'm with 1 Moto And first generation that after being looped I was able to unblock and install TWP, and put the Lolipop Rom 5.1, installed without errors, but when I started the android, I set it up and then when I restarted it Device it enters that white screen that appears that the bootloader was unlocked and falls straight into TWRP, does not start Android at all, could they help me? thanks
Click to expand...
Click to collapse
1. Flash stock lollipop
2. Reboot bootloader
3. Volume up select, Normal powerup
Rajendran Rasa said:
1. Flash stock lollipop
2. Reboot bootloader
3. Volume up select, Normal powerup
Click to expand...
Click to collapse
Guy
Ok, thanks I'll try
Nikakz said:
Guy
Ok, thanks I'll try
Click to expand...
Click to collapse
I tried, accept the installation of Rom, but it is on the screen of the logo starting and it does not leave, I do not know what to do to work.
Nikakz said:
I tried, accept the installation of Rom, but it is on the screen of the logo starting and it does not leave, I do not know what to do to work.
Click to expand...
Click to collapse
Sometimes a new flash takes nearly half an hour to boot. I faced once.. Did u wait for sometime?
vyshak.sk said:
Sometimes a new flash takes nearly half an hour to boot. I faced once.. Did u wait for sometime?
Click to expand...
Click to collapse
Yes, I waited more than 24 hours and nothing and no other flash I tried installs only this one and does not leave the startup logo, very strange this device, I needed a solution.
Nikakz said:
Yes, I waited more than 24 hours and nothing and no other flash I tried installs only this one and does not leave the startup logo, very strange this device, I needed a solution.
Click to expand...
Click to collapse
Flash latest twrp 3.x. You can find it from official lineage os thread under original development section.
Then flash any stable marshmallow custom rom.
_sushan_ said:
Flash latest twrp 3.x. You can find it from official lineage os thread under original development section.
Then flash any stable marshmallow custom rom.
Click to expand...
Click to collapse
Hello everyone, I put a CM13 and she accepted the installation and updated the TWRP also, I put the gaps, I did everything, Android starts, but continues with the problem of falling straight into recovery and going to TWRP and something else when I can do it Start it is not with network signal, recohece the chip, but does not give network signal. I do not know what to do with this device anymore. Could you try to install lolipop on it? Which version could I put? Would it be because of being in 6? I installed this rom cm-13.0-20161022-NIGHTLY-condor only installed it right. thanks
Nikakz said:
Hello everyone, I put a CM13 and she accepted the installation and updated the TWRP also, I put the gaps, I did everything, Android starts, but continues with the problem of falling straight into recovery and going to TWRP and something else when I can do it Start it is not with network signal, recohece the chip, but does not give network signal. I do not know what to do with this device anymore. Could you try to install lolipop on it? Which version could I put? Would it be because of being in 6? I installed this rom cm-13.0-20161022-NIGHTLY-condor only installed it right. thanks
Click to expand...
Click to collapse
Looks like you are using a very old cm 13 build.
Try this one. https://www.androidfilehost.com/?fid=385035244224413102
This is cm 13 snapshot build by @Andersonmends.
Clean install is recommended ie wipe cache data internal and then flash this with pico gapps
Nikakz said:
Hello everyone, I put a CM13 and she accepted the installation and updated the TWRP also, I put the gaps, I did everything, Android starts, but continues with the problem of falling straight into recovery and going to TWRP and something else when I can do it Start it is not with network signal, recohece the chip, but does not give network signal. I do not know what to do with this device anymore. Could you try to install lolipop on it? Which version could I put? Would it be because of being in 6? I installed this rom cm-13.0-20161022-NIGHTLY-condor only installed it right. thanks
Click to expand...
Click to collapse
You flashed latest twrp inside old twrp recovery itself?right?
Rajendran Rasa said:
You flashed latest twrp inside old twrp recovery itself?right?
Click to expand...
Click to collapse
Yes. Out the problem now with the network signal that is not picking up, it recognizes the chip, but it is without signal.
Nikakz said:
Yes. Out the problem now with the network signal that is not picking up, it recognizes the chip, but it is without signal.
Click to expand...
Click to collapse
Flash radio files. Google it for ur device.
_sushan_ said:
Looks like you are using a very old cm 13 build.
Try this one. https://www.androidfilehost.com/?fid=385035244224413102
This is cm 13 snapshot build by @Andersonmends.
Clean install is recommended ie wipe cache data internal and then flash this with pico gapps
Click to expand...
Click to collapse
Hello everyone, I installed Rom CM that the forum colleague indicated and the gapps and installed, everything went well in the installation and initialized Android, was very good in relation to the previous problems, nor know how to thank you. Just when I call it goes to the screen of the fastboot direct and I do not know how to make it not happen, but at least when the motorola logo appears it starts Android. I only notice a certain oscillation in the signal of the network of the operator and I did not find any file to download and to solve this problem of the signal of the network (or radio as you say) if they know where under some that can be installed for that Rom I thank you. I'll leave it for now and see if it's fixing. Thank you very much, ah, I would like to know if I should install the CM updates that appear on the device, it was so good that I'm afraid to accept it and thunder to give it a problem. Another thing he had TV, how to install this Rom? thanks
Hello everyone, I installed Rom CM that the forum colleague indicated and the gapps and installed, everything went well in the installation and initialized Android, was very good in relation to the previous problems, nor know how to thank you. Just when I call it goes to the screen of the fastboot direct and I do not know how to make it not happen, but at least when the motorola logo appears it starts Android. I only notice a certain oscillation in the signal of the network of the operator and I did not find any file to download and to solve this problem of the signal of the network (or radio as you say) if they know where under some that can be installed for that Rom I thank you. I'll leave it for now and see if it's fixing. Thank you very much, ah, I would like to know if I should install the CM updates that appear on the device, it was so good that I'm afraid to accept it and thunder to give it a problem. Another thing he had TV, how to install this Rom? thanks
Nikakz said:
Hello everyone, I installed Rom CM that the forum colleague indicated and the gapps and installed, everything went well in the installation and initialized Android, was very good in relation to the previous problems, nor know how to thank you. Just when I call it goes to the screen of the fastboot direct and I do not know how to make it not happen, but at least when the motorola logo appears it starts Android. I only notice a certain oscillation in the signal of the network of the operator and I did not find any file to download and to solve this problem of the signal of the network (or radio as you say) if they know where under some that can be installed for that Rom I thank you. I'll leave it for now and see if it's fixing. Thank you very much, ah, I would like to know if I should install the CM updates that appear on the device, it was so good that I'm afraid to accept it and thunder to give it a problem. Another thing he had TV, how to install this Rom? thanks
Click to expand...
Click to collapse
You can try flashing radio files.
Find one for your device from this thread : https://forum.xda-developers.com/moto-e/development/rom-stock-motorola-lollipop-rom-t3167111
I m not sure why ur device is rebooting in fastboot. Generally the most common cause for reboot in moto e is faulty lock button. But that jst reboots the phone. You can try using the phone without pressing the lock button. Use volume key wake up option and double tap to status bar to lock.
Also did you wipe cache data internal before flashing ?
And regarding the updates it depends on you. The updates you are for sering are for cm 14 / lineage os. I personally believe that nougat is still not stable enough and features are still missing hence i advised you for mashmallow roms. But if you want to try u can visit the various threads in android development and android development sections and will find nougat roms.
For installing / flashing instructions read guides in general section.
_sushan_ said:
You can try flashing radio files.
Find one for your device from this thread : https://forum.xda-developers.com/moto-e/development/rom-stock-motorola-lollipop-rom-t3167111
I m not sure why ur device is rebooting in fastboot. Generally the most common cause for reboot in moto e is faulty lock button. But that jst reboots the phone. You can try using the phone without pressing the lock button. Use volume key wake up option and double tap to status bar to lock.
Also did you wipe cache data internal before flashing ?
And regarding the updates it depends on you. The updates you are for sering are for cm 14 / lineage os. I personally believe that nougat is still not stable enough and features are still missing hence i advised you for mashmallow roms. But if you want to try u can visit the various threads in android development and android development sections and will find nougat roms.
For installing / flashing instructions read guides in general section.
Click to expand...
Click to collapse
Okay, thank you, it stabilized the signal from the network operator. I will leave as is and will not make updates at the moment. I just want to know how to make the TV function work. Thanks everyone for the help and I do not know how to mark a topic as closed in the forum.
So I have got this Samsung Galaxy Tab 2 3G 10.1" that has been lying in a cupboard for a around a year, mainly because I've been busy Now there's a family member of mine who would really need a tablet so I thought this one would be perfect for her!
From thinking I went on to doing and started with getting rid of the stock software and installing some nice custom ROM.
As I found out i couldn't use USB (probably busted data-cable), I rooted the tab using KingRoot and went on installing CWM recovery. Afterwards long story short: I've tried both CWM and TWRP, different ROM and android versions (Lineage, CM, Slim etc.) and different GApps packages from different developers but the problem still seems to come up :crying:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Hello,
First, have you checked that the ROM you flashed was fully compatible with your device? Yes, this is obvious, but I have to ask.
Second, I'm not a ROM flashing via custom recovery fan... The best way to efficiently flash a ROM in my opinion is Odin-Download mode but whatever (your USB port is screwed, so pfu.)
Redownloading apps doesn't work for you? (updating the apk may fix that!)
Atronid said:
Hello,
First, have you checked that the ROM you flashed was fully compatible with your device? Yes, this is obvious, but I have to ask.
Second, I'm not a ROM flashing via custom recovery fan... The best way to efficiently flash a ROM in my opinion is Odin-Download mode but whatever (your USB port is screwed, so pfu.)
Redownloading apps doesn't work for you? (updating the apk may fix that!)
Click to expand...
Click to collapse
Thanks for your reply!
Yes, I do have used ROMs compatible with my device as they've all are made for espresso3g (which is my device).
I know it's not really the best way but I'll keep on trying with custom recovery for some more time and then perhaps try buying a new cable, and see if that works.
Tried installing Google Play Store from APK both on a clean ROM without GApps and with, but it still doesn't run and keeps on saying that either Google Play Store or "com.google.process.gapps" has stopped.
Alright...
I'm out of idea x/
lordquestionmark said:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Click to expand...
Click to collapse
Hello...!
You could try the following....
1. make absolutely sure you are using the correct version of gapps for the custom rom you are currently using. If your custom rom is on android 6, you need gapps for android 6 for example.
2. after flashing gapps wipe cache/dalvik and make a factory reset BEFORE exiting twrp. You will lose personal data but since you are preparing to give the device to somebody else that should not be much of a concern.
Let me know if it helps, if it does not, I might be able to try and provide additional suggestions.
Good luck!
r&xp said:
Hello...!
You could try the following....
1. make absolutely sure you are using the correct version of gapps for the custom rom you are currently using. If your custom rom is on android 6, you need gapps for android 6 for example.
2. after flashing gapps wipe cache/dalvik and make a factory reset BEFORE exiting twrp. You will lose personal data but since you are preparing to give the device to somebody else that should not be much of a concern.
Let me know if it helps, if it does not, I might be able to try and provide additional suggestions.
Good luck!
Click to expand...
Click to collapse
Hi and thanks for your reply!
1. The ROMs I've been trying to install are all android 6.0.1 and I've been trying with different OpenGApps packages for the 6.0 version which should work (except CM 12 which is android 5.1 with which I've tried OpenGApps and A-Gapps for Android 5.1).
2. Tried that with 3 different ROMs today and the results are following: Slimrom gets stuck in setupwizard which doesn't start, CM 12 starts but the same error as first seems to appear (I get notifications about GApps which stop working) and Lineage bootloops the lineage start screen.
lordquestionmark said:
Hi and thanks for your reply!
1. The ROMs I've been trying to install are all android 6.0.1 and I've been trying with different OpenGApps packages for the 6.0 version which should work (except CM 12 which is android 5.1 with which I've tried OpenGApps and A-Gapps for Android 5.1).
2. Tried that with 3 different ROMs today and the results are following: Slimrom gets stuck in setupwizard which doesn't start, CM 12 starts but the same error as first to appear (I get notifications about GApps which stop working) and Lineage bootloops the lineage start screen.
Click to expand...
Click to collapse
Ok...
This is what I would do if it was my device and I was facing what you are describing. It might take some time and a little patience to do everything described here, but it might also work.
1. Usin Odin, flash latest available official rom for the device. Let it boot and complete setup.
2. Use odin and use CF autoroot to root. Again boot and complete setup.
3. Flash Twrp. Enter Twrp and flash latest flashable supersu.zip. At this time I believe is version 2.82. Again boot and let it reach your welcome screen.
4. Enter Twrp. Enter advanced wipe. Wipe everything except external SD and usb at least 3 times. Do not exit twrp.
5. Install you rom. Do not exit Twrp.
6. After installing your rom, Twrp will ask you if you want to wipe cache/dalvik. "Yes" but DO NOT reboot.
7. Install correct version of gapps for your custom rom (correct both android version and architecture version). Again twrp will ask you to wipe cache/dalvik. "Yes" and this time reboot.
See what happens. If it gets stuck, try entering twrp again and do a factory reset only, only once and reboot again.
If that fails again... I will at a loss here myself too...
I did a quick search here on xda on P5100, I am providing some links that you can take a look at. You probably already searched yourself but you never know...
https://forum.xda-developers.com/ga...-2-unified/rom-cyanogenmod-13-cm13-0-t3303798
https://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-blissmallow-t3312320
https://forum.xda-developers.com/showthread.php?t=1686514
https://forum.xda-developers.com/showthread.php?t=2581782
https://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-candy-5-v2-5-5-t3136904
If nothing else helps, perhaps the best way to go around this would be to find a custom rom with at least some google apps pre-installed, in order to save you the trouble you are currently facing.
lordquestionmark said:
So I have got this Samsung Galaxy Tab 2 3G 10.1" that has been lying in a cupboard for a around a year, mainly because I've been busy Now there's a family member of mine who would really need a tablet so I thought this one would be perfect for her!
From thinking I went on to doing and started with getting rid of the stock software and installing some nice custom ROM.
As I found out i couldn't use USB (probably busted data-cable), I rooted the tab using KingRoot and went on installing CWM recovery. Afterwards long story short: I've tried both CWM and TWRP, different ROM and android versions (Lineage, CM, Slim etc.) and different GApps packages from different developers but the problem still seems to come up :crying:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Click to expand...
Click to collapse
did you find a solution
lordquestionmark said:
So I have got this Samsung Galaxy Tab 2 3G 10.1" that has been lying in a cupboard for a around a year, mainly because I've been busy Now there's a family member of mine who would really need a tablet so I thought this one would be perfect for her!
From thinking I went on to doing and started with getting rid of the stock software and installing some nice custom ROM.
As I found out i couldn't use USB (probably busted data-cable), I rooted the tab using KingRoot and went on installing CWM recovery. Afterwards long story short: I've tried both CWM and TWRP, different ROM and android versions (Lineage, CM, Slim etc.) and different GApps packages from different developers but the problem still seems to come up :crying:
The problem itself is that when I've installed any of the above mentioned ROMs, all the GApps seem to not have been installed correctly (even though the installation process in recovery went smoothly) and basically none of them works (notifications saying that any GApp has stopped keep on coming up and I can't find any Google app in the menu except something things like "com.google.android..." or "com.android.vending...") otherwise everything seems perfectly fine.
Maybe there are others here experiencing the same issue or there's someone who knows how to fix this here, any help will be very appreciated :good:
Click to expand...
Click to collapse
Hey, just try uninstalling Google play services and install them again. I faced the same issue and now it's all working on my Samsung Galaxy Core 2
I have unlocked my bootloader and have TWRP 3.1 installed. I have tried nitrogen, lineage, miui 9 but they are always stuck on booting, after I flash them and opengapps and restart they just have the loading screen for hours on end and will not load.
Any ideas?
same problem with mine, ive booted into AOKP but as i restore apps it just reboots again and again, tried clean install and format data install but is the same
DOESNT make any sense!
If you have unlocked bootloader unofficially LP roms & flashed Nitrogen Lineage etc they won't boot.
follow this tutorial http://en.miui.com/thread-345728-1-1.html unlock & rom will boot fine.
I went back to stock, these custom ones like Lineage etc are garbage.
dupz said:
I went back to stock, these custom ones like Lineage etc are garbage.
Click to expand...
Click to collapse
Lol miui is the worst **** u can use on any phone..los is love.. maybe u are a noob :3
dupz said:
I went back to stock, these custom ones like Lineage etc are garbage.
Click to expand...
Click to collapse
Noobie ****UI good for you
Ok, a bit of backstory:
This is the Canadian Honor 5x, also known as Huawei GR5. After finally unlocking the bootloader, I was able to flash TWRP (3.3.1-0) on it. After flashing AOSIP for it, It was working mostly fine, aside from some basic apps crashing constantly (such as download manager) so I tried to flash gapps afterwards (I know this isn't how it should be done). It started to bootloop.
Then I tried the following without success:
Flashed ROM and Gapps before rebooting; Bootloops
Flashed ROM without Gapps; Works but apps crashes and no googleplay (obviously)
Sideloaded LineageOS with gapps; Same issue as first one.
Wiped Caches and data before flashing ROM (no gapps); Same as first one but crashing apps aren't crashing anymore.
The last thing I tried landed me here: I decided to do the last item on the list but also wiped System. Now I can't install or sideload anything.
Did I shoot myself in the foot here? Is it gone for good?? I need help with this.
thegamerchunk1 said:
Ok, a bit of backstory:
This is the Canadian Honor 5x, also known as Huawei GR5. After finally unlocking the bootloader, I was able to flash TWRP (3.3.1-0) on it. After flashing AOSIP for it, It was working mostly fine, aside from some basic apps crashing constantly (such as download manager) so I tried to flash gapps afterwards (I know this isn't how it should be done). It started to bootloop.
Then I tried the following without success:
Flashed ROM and Gapps before rebooting; Bootloops
Flashed ROM without Gapps; Works but apps crashes and no googleplay (obviously)
Sideloaded LineageOS with gapps; Same issue as first one.
Wiped Caches and data before flashing ROM (no gapps); Same as first one but crashing apps aren't crashing anymore.
The last thing I tried landed me here: I decided to do the last item on the list but also wiped System. Now I can't install or sideload anything.
Did I shoot myself in the foot here? Is it gone for good?? I need help with this.
Click to expand...
Click to collapse
First, you need to be on the latest stock firmware. Before unlocking the bootloader, upgrade to marshmallow to get the marshmallow firmware. You will get issues if you don't have the marshmallow firmware as all custom ROM built on that.
AOSiP was built from LineageOs.
Also note, Important note:
Stock Firmware B360 and B370 are known to cause boot loops!
(Generally: if your stock ROM supports VoLTE it is likely that it is also affected!)
All others might work, please do not ask in here how to up- or downgrade!
---------- Post added at 01:46 PM ---------- Previous post was at 01:43 PM ----------
thegamerchunk1 said:
Ok, a bit of backstory:
This is the Canadian Honor 5x, also known as Huawei GR5. After finally unlocking the bootloader, I was able to flash TWRP (3.3.1-0) on it. After flashing AOSIP for it, It was working mostly fine, aside from some basic apps crashing constantly (such as download manager) so I tried to flash gapps afterwards (I know this isn't how it should be done). It started to bootloop.
Then I tried the following without success:
Flashed ROM and Gapps before rebooting; Bootloops
Flashed ROM without Gapps; Works but apps crashes and no googleplay (obviously)
Sideloaded LineageOS with gapps; Same issue as first one.
Wiped Caches and data before flashing ROM (no gapps); Same as first one but crashing apps aren't crashing anymore.
The last thing I tried landed me here: I decided to do the last item on the list but also wiped System. Now I can't install or sideload anything.
Did I shoot myself in the foot here? Is it gone for good?? I need help with this.
Click to expand...
Click to collapse
Note: In case you want to use any gapps, YOU MUST install the right gapps the first time that you flash a marshmallow ROM. Do not boot with an older gapps or without one and then try to install it later.
50UND2 3NG1N33R said:
Before unlocking the bootloader, upgrade to marshmallow to get the marshmallow firmware. You will get issues if you don't have the marshmallow firmware as all custom ROM built on that.
Click to expand...
Click to collapse
I was on pie I believe so that should of not been an issue.
The first sentence on my post specified that I ALREADY unlocked the boot loader. Please read my post before copy pasting things that were clearly defined.
50UND2 3NG1N33R said:
AOSiP was built from LineageOs.
Click to expand...
Click to collapse
Cool. I cant install neither.
50UND2 3NG1N33R said:
Also note, Important note:
Stock Firmware B360 and B370 are known to cause boot loops!
(Generally: if your stock ROM supports VoLTE it is likely that it is also affected!)
Click to expand...
Click to collapse
I have indeed read this on the AOSiP thread. Although instead of repeating something I was already aware of, you could specify what is VoLTE since no matter how many time I read it I wont know what it means. If its Voice Over LTE I doubt it. I don't have LTE on my carrier.
50UND2 3NG1N33R said:
All others might work, please do not ask in here how to up- or downgrade!
Click to expand...
Click to collapse
Did you read my post? Where does it say that's what I wanna do?? I never, ever, said to either upgrade or downgrade. I want grade, period (by that I mean I want something thats working at all, regardless of version).
thegamerchunk1 said:
I was on pie I believe so that should of not been an issue.
The first sentence on my post specified that I ALREADY unlocked the boot loader. Please read my post before copy pasting things that were clearly defined.
Cool. I cant install neither.
I have indeed read this on the AOSiP thread. Although instead of repeating something I was already aware of, you could specify what is VoLTE since no matter how many time I read it I wont know what it means. If its Voice Over LTE I doubt it. I don't have LTE on my carrier.
Did you read my post? Where does it say that's what I wanna do?? I never, ever, said to either upgrade or downgrade. I want grade, period (by that I mean I want something thats working at all, regardless of version).
Click to expand...
Click to collapse
okay, sorry for not understanding you. You ain't a noob. So I should expect you did a clean install. Wiping Dalvik/ART Cache, Cache, Data, Internal Storage and System. this will give you a clean slate. And be on the latest TWRP which you already are in. If that fails, I can't help beyond that. VOLTE is Voice Over LTE. You are correct.