Can somebody help me? I used the CM for a long time, but less than a month when I was with the CyanogenMod, the phone restarted and did not turn on anyway (something like a bootloop, but the darkened screen as if you were about to turn on, then lit again).
I tried to reinstall CM, but always after a short time of use, it restarts, and bootloop again.
I reinstalled the stock, but the frustration and willingness to use CM was so big that I tried to install again. Result: bootloop.
Anyway, I'm using the stock rom for a while, but still want to use CM.
Does anyone have any idea what could have happened? (All Xposed modules and mods that put into CM are the same I'm using now, but the stock has no problems)
This happened with RR rom too.
Sorry for this long text and my bad english
I want suggest you to wipe all thing system and data , cash/dalvik, (after backup) and then try to flash the ROM and just try another ROM instead CM and RR
Sent from my GT-I8190 using Tapatalk
But I've never had this problem before!
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?
Before continuing reading, please keep in mind that the problem I am asking support for was already solved for my own. What I want to know is how did it happen. For prevention, you know.
It all started when I flashed the Black Box ROM 2.0.2 (http://forum.xda-developers.com/showthread.php?t=1834915) It flashed normally, without any problem. But, since it lacked the Xposed Framework, I installed it manually, downloading from its thread, and choosing a full install. Using the Framework I downloaded Gravity Box and the Youtube Adaway, before downloading Youtube. Since the modules needed a reboot to work, I rebooted. And this is when the bad things started to happen.
The ROM did not start. It went through the BlackBox logo, but when it appeared that the SIM unlock was going to pop up, then the phone turned off. This happened many times. So I decided to do a full wipe and install another ROM. The problem was that the phone didn´t allowed me to access the recovery.
I was using the PhilZ Touch 6, but when I pressed Volume up+Menu+Power it did not work. The only thing that worked was the Odin Menu, and I got stuck at it, I couldn´t get out the Odin Menu. So, seeing that the phone wasnt going to work anyways, I flashed a 4.3 stock ROM through Odin.
As I suspected, the ROM got stuck at boot, and got a bootloop. So then I flashed another recovery, and flashed good ol´ CWM. And It worked..for a while. The phone would shut down after some seconds. So then I tried to flash TWRP, but it lasted about one second and then the phone shut down again.
Since I was using Odin 3.03, I downloaded Odin 3-04 Moded Edition, from the Modem thread, and then reflashed CWM. In this time, it worked without failing, and I could do a full wipe and flashing an old Cyanogenmod 4.2.2 ROM, finally solving the problem. The day after I flashed Ultima ROM and at the moment it goes fine, without any problem. Which is weird, because it too uses Gravity Box and Xposed Modules. I even installed new modules, rebooted the phone and it works fine, without any problem.
What I want for the people here is that someone explains to me what happened, because the BlackBox ROM looked gorgeous and I wanted to give it a long try. And because I spent an entire night solving that problem, and well, I wont sleep in peace until I get to know what happened to that bastard
r1k1v1 said:
Before continuing reading, please keep in mind that the problem I am asking support for was already solved for my own. What I want to know is how did it happen. For prevention, you know.
It all started when I flashed the Black Box ROM 2.0.2 (http://forum.xda-developers.com/showthread.php?t=1834915) It flashed normally, without any problem. But, since it lacked the Xposed Framework, I installed it manually, downloading from its thread, and choosing a full install. Using the Framework I downloaded Gravity Box and the Youtube Adaway, before downloading Youtube. Since the modules needed a reboot to work, I rebooted. And this is when the bad things started to happen.
The ROM did not start. It went through the BlackBox logo, but when it appeared that the SIM unlock was going to pop up, then the phone turned off. This happened many times. So I decided to do a full wipe and install another ROM. The problem was that the phone didn´t allowed me to access the recovery.
I was using the PhilZ Touch 6, but when I pressed Volume up+Menu+Power it did not work. The only thing that worked was the Odin Menu, and I got stuck at it, I couldn´t get out the Odin Menu. So, seeing that the phone wasnt going to work anyways, I flashed a 4.3 stock ROM through Odin.
As I suspected, the ROM got stuck at boot, and got a bootloop. So then I flashed another recovery, and flashed good ol´ CWM. And It worked..for a while. The phone would shut down after some seconds. So then I tried to flash TWRP, but it lasted about one second and then the phone shut down again.
Since I was using Odin 3.03, I downloaded Odin 3-04 Moded Edition, from the Modem thread, and then reflashed CWM. In this time, it worked without failing, and I could do a full wipe and flashing an old Cyanogenmod 4.2.2 ROM, finally solving the problem. The day after I flashed Ultima ROM and at the moment it goes fine, without any problem. Which is weird, because it too uses Gravity Box and Xposed Modules. I even installed new modules, rebooted the phone and it works fine, without any problem.
What I want for the people here is that someone explains to me what happened, because the BlackBox ROM looked gorgeous and I wanted to give it a long try. And because I spent an entire night solving that problem, and well, I wont sleep in peace until I get to know what happened to that bastard
Click to expand...
Click to collapse
OK first black box already has xposed in ROM control settings.. so maybe because you manually installed it it may have caused conflicts... Don't know why you got a recovery bootloop... but maybe due to same problems... And I am also using blackbox 2.1 and so far it is fantastic...
Sent from my GT-I9300 using xda app-developers app
Partition structure on these phones is very fragile, one bad shutdown can corrupt one or more partitions at the same time. I'd suggest the combination of mods applied caused the kernel panic, while data was being written.
Subsequent events read like normal solution to corruption, it shouldn't happen again but best to apply framework mods one at a time.
Sent from my GT-I9300 using Tapatalk
kunal1540 said:
OK first black box already has xposed in ROM control settings.. so maybe because you manually installed it it may have caused conflicts... Don't know why you got a recovery bootloop... but maybe due to same problems... And I am also using blackbox 2.1 and so far it is fantastic...
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Hmm, I don´t remember that the BlackBox 2.0.2 had any Framework...thats why I did a manual installation. But I will try the new version 2.1. Hopefully the problems may have been solved.
boomboomer said:
Partition structure on these phones is very fragile, one bad shutdown can corrupt one or more partitions at the same time. I'd suggest the combination of mods applied caused the kernel panic, while data was being written.
Subsequent events read like normal solution to corruption, it shouldn't happen again but best to apply framework mods one at a time.
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Interesting. So I have to apply mods one by one? Or can I add multiple mods because corruption has already been solved?
On a side note, when I boot the phone the red exclamation mark that used to appear has disappeared. Does that means that I somewhat reseted the flash counter to 0?
HI guys,
My tablet is giving me issues with my wifi all of the sudden.
It was working fine and now it just says Turning on Wi-Fi... this never stops.
I have a Huawei Mediaoad S7-301u
Any ideas how I can get my wifi back up and running?
A restart should do. If you don't have to do this too often. All custom roms for the Mediapad should exhibit this fom time to time, stock rom is too long gone to remember, but if you're still using it you found the answer for that.
Usually it should happen after wakeup from standby, and if it occurs several times a day, another rom may perform better, also increasing screen timeout should help.
If wifi is completely gone, restore a nandroid backup or recover the stock rom via dload method, if there's no custom recovery, which would prevent that. Custom rom and no backup means doing a clean flash.
lecorbusier said:
A restart should do. If you don't have to do this too often. All custom roms for the Mediapad should exhibit this fom time to time, stock rom is too long gone to remember, but if you're still using it you found the answer for that.
Usually it should happen after wakeup from standby, and if it occurs several times a day, another rom may perform better, also increasing screen timeout should help.
If wifi is completely gone, restore a nandroid backup or recover the stock rom via dload method, if there's no custom recovery, which would prevent that. Custom rom and no backup means doing a clean flash.
Click to expand...
Click to collapse
I have done a few restarts and I have also reinstalled the same rom. I am starting to think it is the rom, it seemed buggy from the start.
Which rom would you suggest?
Stability-wise it's the older the better. Stock rom and After Silence's CM10(probably gone forever) . He developed the kernel Zyr3x was also using, whose roms got buggier and buggier. Zyr3xs AOKP, maybe, that was my first custom rom on the Mediapad, but I don't remember the bugs there were. Some, but not many.
My just about 3-4y phone.
It just randomly started rebooting like a week ago, like twice a day. Then it went progressively worse over time like it failed to boot on the first try it was rebooting 30 minutes until it actually succeeded booting to android. So then I decided to factory reset my phone but that didn't help either.
after that, I just tried to flash a new ROM AOSP extended 4.6 still based on kernel 3.1. I'm not really sure if using ROM with newer kernel will fix the issue because I don't think TWRP uses kernel and it doesn't reboot when using it
can it be because of that kernel or can it be something different?
PLZ help if anyone knows.
As tittle says, I have been in XDA for a while, never created an account cause I have always encountered responses to all my problems there. But not this time. I have created an account just to ask you people if someone knows (or had) this problem.
I have been getting touchscreen problems since a while (I dont know if it was caused by a custom kernel I changed months ago, or by touchscreen needing a replacement). Then the problem with WebView happend, but after trying to fix it by OTA, reinstalling WebView, clearing cache of google apps and few other things, apps kept closing randomly, and with the touchscreen failing, it was a real pain, so I downloaded a few roms and saved all my data, then went to TWRP. I updated it to 3.5.2_10-0-beryllium before anything, and flashed vendor, firmware and ROM GLOBAL_V12.0.3.0.QEJMIXM_cf3fccffce_10.0. Here begins the brick. I cannot pass the first boot, in any of the roms I tried. In MIUI, the logo of starting stay indefinitly (not the poco one, the MIUI one). I tried pa-quartz-5-beryllium-20200924, also stays infinitly in the green ball logo moving. After that, I tried lineage-18.1-20210410-nightly-beryllium-signed, with the same result, Infinite starting moving blue logo (more than 8h and still didnt boot). I tried clean installs and dirty installs. The worst part is that my PC only recognizes my F1 on recovery, Fastboot don't seems to be working (I was going to try flashing via fastboot). And here I am, after 6h of trying different installs, flashing the Disable Force Encryptation, flashing stock firmware and stock rom, stock firmware and custom roms, flashing vendor, not flashing vendor, etc... Im sick.
Thanks in advance to anyone who try to help me.
EDIT: I missed that i was having random reboots too, not only touchscreen fails.
iJaviXR said:
As tittle says, I have been in XDA for a while, never created an account cause I have always encountered responses to all my problems there. But not this time. I have created an account just to ask you people if someone knows (or had) this problem.
I have been getting touchscreen problems since a while (I dont know if it was caused by a custom kernel I changed months ago, or by touchscreen needing a replacement). Then the problem with WebView happend, but after trying to fix it by OTA, reinstalling WebView, clearing cache of google apps and few other things, apps kept closing randomly, and with the touchscreen failing, it was a real pain, so I downloaded a few roms and saved all my data, then went to TWRP. I updated it to 3.5.2_10-0-beryllium before anything, and flashed vendor, firmware and ROM GLOBAL_V12.0.3.0.QEJMIXM_cf3fccffce_10.0. Here begins the brick. I cannot pass the first boot, in any of the roms I tried. In MIUI, the logo of starting stay indefinitly (not the poco one, the MIUI one). I tried pa-quartz-5-beryllium-20200924, also stays infinitly in the green ball logo moving. After that, I tried lineage-18.1-20210410-nightly-beryllium-signed, with the same result, Infinite starting moving blue logo (more than 8h and still didnt boot). I tried clean installs and dirty installs. The worst part is that my PC only recognizes my F1 on recovery, Fastboot don't seems to be working (I was going to try flashing via fastboot). And here I am, after 6h of trying different installs, flashing the Disable Force Encryptation, flashing stock firmware and stock rom, stock firmware and custom roms, flashing vendor, not flashing vendor, etc... Im sick.
Thanks in advance to anyone who try to help me.
EDIT: I missed that i was having random reboots too, not only touchscreen fails.
Click to expand...
Click to collapse
Check my POCO F1 Ultimate Collection & Guides. Try to Clean Install Pixel Experience for example, according my guide (u need to format data also). Let me know how it goes.
Tried Android 10 and 11 Pixel Experience, tried with stock and NG Kernels. Still stays forever in the first load of the SO.
Just got the properties file from XiaomiADBFastbootTools. Maybe someone can see something wrong on it.