Related
Hellybean is by far the best ROM I've used yet on my Note. It runs almost perfectly. I did have to reboot because my bluetooth wouldn't come on (reboot always fixes that). However, when I rebooted it, the phone tried to restart, I saw the Samsung SGH-I717 screen, and then it went black. It never brings up the Hellybean ring of fire. If I pull the battery I see the ring of fire for about 5 seconds, then it reboots, then black screen.
At this point, the only thing I can do is force the phone into TWRP and restore a previous backup. Does anyone have any idea what could cause the phone to not want to reboot back into the system?
I was on the latest Hellybean build and TWRP is up-to-date as well. I had to revert back to the October 10 build though. I just tried rebooting it after a restore and the same thing happens (so it's not specific to a certain date of ROM). As long as I don't reboot I don't have a problem.
Thanks
Chris
MI_SS_IL said:
Hellybean is by far the best ROM I've used yet on my Note. It runs almost perfectly. I did have to reboot because my bluetooth wouldn't come on (reboot always fixes that). However, when I rebooted it, the phone tried to restart, I saw the Samsung SGH-I717 screen, and then it went black. It never brings up the Hellybean ring of fire. If I pull the battery I see the ring of fire for about 5 seconds, then it reboots, then black screen.
At this point, the only thing I can do is force the phone into TWRP and restore a previous backup. Does anyone have any idea what could cause the phone to not want to reboot back into the system?
I was on the latest Hellybean build and TWRP is up-to-date as well. I had to revert back to the October 10 build though. I just tried rebooting it after a restore and the same thing happens (so it's not specific to a certain date of ROM). As long as I don't reboot I don't have a problem.
Thanks
Chris
Click to expand...
Click to collapse
have you tried any other roms?
I have ran every update of Hellybean since its arrival here. I had made a backup and flashed another rom, didn't like so I went to install back up.
it would not install, just kept looping in the boot screen. had to fresh flash the rom. didn't matter which, just had to reflash. screen never went black though. you issue sounds more similar to a stuck power button, which is why I ask if you have had same problem with another rom.
I find it hard to believe this rom wont restore a back up. others have not chimed in with that specific issue. but you and I may just be 2 that have voiced the issue. wasn't that big of issue for me as I thought it more an oddity. my back up wouldn't install at all in 3 attempts, so again, whyi question your power button.
try another rom real quick if you can. don't have to like or want it, but this is a test right?
let us know what happens
captemo said:
have you tried any other roms?
I have ran every update of Hellybean since its arrival here. I had made a backup and flashed another rom, didn't like so I went to install back up.
it would not install, just kept looping in the boot screen. had to fresh flash the rom. didn't matter which, just had to reflash. screen never went black though. you issue sounds more similar to a stuck power button, which is why I ask if you have had same problem with another rom.
I find it hard to believe this rom wont restore a back up. others have not chimed in with that specific issue. but you and I may just be 2 that have voiced the issue. wasn't that big of issue for me as I thought it more an oddity. my back up wouldn't install at all in 3 attempts, so again, whyi question your power button.
try another rom real quick if you can. don't have to like or want it, but this is a test right?
let us know what happens
Click to expand...
Click to collapse
Let me clarify ... I'm not having a problem restoring or installing Hellybean or any other ROM. It's after I install or restore and the ROM is running fine (for days even) ... at some point I have to reboot for some reason and it's then that it won't boot back into the ROM. In other words I can't reboot my system because it never comes back to the ROM. I have to then boot to TWRP, restore something else and then that will boot to the ROM. If I reboot again after the ROM is up and running, I get the same thing, it won't boot back into the ROM, I have to restore again. That rules out a power button ... if it was stuck I would never get back in.
I've tried most of the ROMs out there, but since Hellybean I haven't tried any others (because this is the best one). You think there's any possibility dirty flashing all of the Hellybean builds over top of each other could cause it? Maybe I'll try installing the latest one from a full wipe.
Thanks
Chris
MI_SS_IL said:
Let me clarify ... I'm not having a problem restoring or installing Hellybean or any other ROM. It's after I install or restore and the ROM is running fine (for days even) ... at some point I have to reboot for some reason and it's then that it won't boot back into the ROM. In other words I can't reboot my system because it never comes back to the ROM. I have to then boot to TWRP, restore something else and then that will boot to the ROM. If I reboot again after the ROM is up and running, I get the same thing, it won't boot back into the ROM, I have to restore again. That rules out a power button ... if it was stuck I would never get back in.
I've tried most of the ROMs out there, but since Hellybean I haven't tried any others (because this is the best one). You think there's any possibility dirty flashing all of the Hellybean builds over top of each other could cause it? Maybe I'll try installing the latest one from a full wipe.
Thanks
Chris
Click to expand...
Click to collapse
I have dirty flashed every one. the only thing I try to do when gong dirty is to still give it that 10 settle time. no particular reason other than my OCD
Okay, thanks for the replies. I'll play around with it some more, maybe try a fresh install and see if that changes anything. I'll let you know if I figure it out.
Chris
I figured it out. Not Hellybean at all. It was TWRP. I reverted back to an early build and then reinstalled 2.6.3.0 and now it reboots fine.
Chris
I guess I can't edit the title to reflect the correct issue? Thread can be deleted if the moderators want. Hellybean is running strong ... it's the first ROM I get 0 random reboots.
Thanks for the help captemo and to the makers of Hellybean.
Chris
beanstalk
I got exactly same problem with beanstalk 4.3.
I tried reinstall recovery but no luck. Every time powering off or rebooting need a fully wipe and restore.
Do you think other or older recovery will work?
hotgly said:
I got exactly same problem with beanstalk 4.3.
I tried reinstall recovery but no luck. Every time powering off or rebooting need a fully wipe and restore.
Do you think other or older recovery will work?
Click to expand...
Click to collapse
Same issue. Any of the 4.3 ROMS.
MI_SS_IL said:
I figured it out. Not Hellybean at all. It was TWRP. I reverted back to an early build and then reinstalled 2.6.3.0 and now it reboots fine.
Chris
Click to expand...
Click to collapse
So did you:
1- restore a stable backup
2- boot to recovery and flash TWRP (which version?)
3- Boot back into recovery
3- wipe and flash HellyBean
Is this correct?
edit - problem solved......
biggary said:
Hello there, long time member of XDA, but a new user of Honor 5x - Nice to see some devs create some nice roms....but I have a problem.....
I unlocked bootloader via the proper way, and its flashed, rooted etc, and its happily running the newest resurrection remix rom.....but.....
I went to download the great modaco roms by @paulobrien , done what was said, but the phone reboots, and it does the splash screen thing....and thats it....as far as it goes, I try leaving for half a hour, but still nothing......
sometimes i get the error in TWRP that /system cant be mounted, and although it flashes, when rebooting, it says NO OS installed, so i flash it again, and no error but, reboots and sticks at the 'HONOR' logo....
My model is L21, when i clean for a new rom, I advance wipe all sections except internal and external memory, and i also do a factory reset, as I have done with many many other phones
is there a step i am missing? i have read about swap - what is that?
All I want is a nice stock rom which i can debloat, install the htc home launcher, and a few useful apps.....
Who can help me???
Click to expand...
Click to collapse
If you wipe system before flashing the rom you get that error
don't wipe system the rom does it for you
to flash the rom after wiping the system choose reboot / recovery now the rom will flash
Arobase40 said:
"Honor 5x running Resurrection Remix Marshmallow"... ^^
Click to expand...
Click to collapse
@Arobase40 I know my Sig says runing RRemix, but what im asking for, is going back to a stock rom, i can flash any of the CM based roms, but have problems when returning to stock.
Im having some trouble with my OPX. I was running CM13 nightly of sept 20th. Today i wanted to update my OPX to the latest nightly, and make a fresh start, so i took some backups of apps, downloaded the latest nightly (not OTA), went into TWRP, did a full wipe, and flashed the 10/15 nightly and opengapps pico package.... Thats when the fun began.
All my phone shows is the Oneplus X logo. (without powered by android). I am able to turn it off, and reboot into recovery, and flash another zip, but so far ive tried flashing 6 different CM13 nightlies, and all give the same result.
I was a pokemon player with root and xposed, so my guess was that systemless xposed, magisk and superSU were causing trouble. So ive tried running all the uninstaller packages, to no avail.
i CAN run a nandroid restore from 1 week ago. i can boot to that nightly version. it works.... but as soon as i try to update it again, or even wipe all data, it doesnt want to boot anymore. i thought that as long as i had TWRP things should be easy to fix, but im running out of ideas. Uninstalling xposed, magisk and superSU in this backup, and rebooting, still works, but the same problem arises after updating.
Im pretty sure the answer is simple as hell, but i must be overlooking something. any sugestions?
I just found out you need a new bootloader... should have looked harder before starting this thread (was searching for over an hour, but in the wrong places). I'll try the guide in the CM thread.
same exact thing happened to me, wasn't aware you needed new bootloader, think you could share the link?
rx15901 said:
same exact thing happened to me, wasn't aware you needed new bootloader, think you could share the link?
Click to expand...
Click to collapse
Here.you should always keep an eye on general section,thats where all the guides are,also should read the thread before flashing a rom.
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
Hi,
Hello to everybody, I am new on this forum.
I have a Leeco Max 2.
2 weeks ago I installed Twrp with success and I installed a first rom installed. Everything was working fine.
After few days, I got a loop restart and the first welcome picture of leeco change from english to chineese.. a virus ???
Now, If don't use it after 1 or 2 minutes, it restarts. If i put it in charge, it's work without loop !
I flashed 2 different rom, to see if i's solve the problem, but no. Before each flash I formated with twrp : the cache dalvik, system, cache, data.
But still the loop.
Did any one face the same symptoms ? Any ideas how to solve the problem ?
Thanks in advance for your proposals.
Heyyo, the change in boot screen logo from English to Chinese could be if you flashes any EUI ROM be if custom or not that is based on the Chinese versions and have a Chinese boot logo in the files. If you flash an English EUI ROM splash screen or EUI ROM it will return to English.
As for the boot looping? Hmm that's unfortunate. Can you please specify which ROMs you have tried?
ThE_MarD said:
Heyyo, the change in boot screen logo from English to Chinese could be if you flashes any EUI ROM be if custom or not that is based on the Chinese versions and have a Chinese boot logo in the files. If you flash an English EUI ROM splash screen or EUI ROM it will return to English.
As for the boo,t looping? Hmm that's unfortunate. Can you please specify which ROMs you have tried?
Click to expand...
Click to collapse
--
Hi The Mard,
Regarding the boot screen logo. it doens't change any more to english .. After 2 or 3 rom flashed. does it mean something ? may be not ..
The last rom I flashed is the PixelExperience_x2-8.1.0-20180218-1114-OFFICIAL.
rodolphediet said:
--
Hi The Mard,
Regarding the boot screen logo. it doens't change any more to english .. After 2 or 3 rom flashed. does it mean something ? may be not ..
The last rom I flashed is the PixelExperience_x2-8.1.0-20180218-1114-OFFICIAL.
Click to expand...
Click to collapse
---
Nobody to help me .. please I am really bad. Thank you
rodolphediet said:
---
Nobody to help me .. please I am really bad. Thank you
Click to expand...
Click to collapse
Have you flashed a modern firmware version on your device ?
Try going on TWRP and flash 26S or 466D modem (try one first and if that doesn't work try the other):
466D Modem
26S Modem
I've had a similar problem, a few days ago I woke up and noticed my phone was boot looping.
Ive since wiped the phone, with inbuilt recovery. I then flashed twrp via adb cmd, made a back up. Was working for two days, then today constantly crashing, so I flashed my recovery via twrp, now back to bootloop.
Mine started doing this a few days ago. I've used https://forum.xda-developers.com/showthread.php?t=3492949 to try to fix mine. It didn't help initially. After doing it a few times over the last few days I'm running fine. I don't know how long it will last. So far about six hours without a reboot. I did the above process, then flashed a stock 20s US rom via TWRP and then a Lineage rom. I did this whole process a few times. The last time, I ran the unbrick process two times in a row. Not sure if that's what did the trick or not. Good luck.
Sent from my LEX829 using Tapatalk
first flash cbg or cuoco rom to overwrite chinese bootloader (maybe better fastboot version). After, flash one of the lastest modem, maybe improve stability, than try to flash another custom rom (pixel revenge, official lineage, aosip, du...the best atm). If that does not solve the reboot issue, buy another battery.
My phone has an up time of 20 hours so far after the "process" I did. That's after having an up time of an hour or so for each step I took. So, almost a day in total without a random reboot.
Sent from my LEX829 using Tapatalk
4ish days later and it's doing it again. Tine to sell it for parts.
Sent from my Ascend Mate 2 using Tapatalk