Related
Hi guys,
I have a problem with my Magic 32B and hope one of you guys could figure out where this all come from.
Since a couple of weeks my magic has become very unstable and I would say I have about 20 to 30 freezes or reboots a day. It suddenly started when I switched from a nightly froyo to another and since then regardless on the ROM I flash I always have the same behaviour (I'm currently on the CM6 RC1).
I tried the following:
- full wipe via AmonRa + format of SD (128 SWAP + 512 EXT + FAT) clean reinstall of a presumably stable rom --> failed keeps rebooting or freezing
- I did a fastboot erase system -w + flash of a clean ROM --> failed
The bizarre thing is it never crashes when the phone is USB plugged on my laptop, therefore I've never seen a logcat showing anything bad ...
Also I can't identify any pattern or scenario which would systematically frag my magic... Even when I install a fresh new ROM, it can work pretty well for as long as an hour but then start being screwed up.
I've spent quite some time on this forum desperately looking for someone experiencing the same troubles but so far unsuccessfully ...
Would you guys have any idea ?
cheers
ZeRoT
zerot said:
Hi guys,
I have a problem with my Magic 32B and hope one of you guys could figure out where this all come from.
Since a couple of weeks my magic has become very unstable and I would say I have about 20 to 30 freezes or reboots a day. It suddenly started when I switched from a nightly froyo to another and since then regardless on the ROM I flash I always have the same behaviour (I'm currently on the CM6 RC1).
I tried the following:
- full wipe via AmonRa + format of SD (128 SWAP + 512 EXT + FAT) clean reinstall of a presumably stable rom --> failed keeps rebooting or freezing
- I did a fastboot erase system -w + flash of a clean ROM --> failed
The bizarre thing is it never crashes when the phone is USB plugged on my laptop, therefore I've never seen a logcat showing anything bad ...
Also I can't identify any pattern or scenario which would systematically frag my magic... Even when I install a fresh new ROM, it can work pretty well for as long as an hour but then start being screwed up.
I've spent quite some time on this forum desperately looking for someone experiencing the same troubles but so far unsuccessfully ...
Would you guys have any idea ?
cheers
ZeRoT
Click to expand...
Click to collapse
Probably other people will say it, but wrong forum.
Also, what ROMs have you flashed after the nightly froyo? Nightly froyos are cautioned, which I'm sure you knew.
yep, I used a couple of FroYo SP French Connection nightlies and then switched to CM V6.0.0-RC1.
(sorry if it's the wrong forum, @admins, please feel free to move it to wherever make sense)
zerot said:
Hi guys,
I have a problem with my Magic 32B and hope one of you guys could figure out where this all come from.
Since a couple of weeks my magic has become very unstable and I would say I have about 20 to 30 freezes or reboots a day. It suddenly started when I switched from a nightly froyo to another and since then regardless on the ROM I flash I always have the same behaviour (I'm currently on the CM6 RC1).
I tried the following:
- full wipe via AmonRa + format of SD (128 SWAP + 512 EXT + FAT) clean reinstall of a presumably stable rom --> failed keeps rebooting or freezing
- I did a fastboot erase system -w + flash of a clean ROM --> failed
The bizarre thing is it never crashes when the phone is USB plugged on my laptop, therefore I've never seen a logcat showing anything bad ...
Also I can't identify any pattern or scenario which would systematically frag my magic... Even when I install a fresh new ROM, it can work pretty well for as long as an hour but then start being screwed up.
I've spent quite some time on this forum desperately looking for someone experiencing the same troubles but so far unsuccessfully ...
Would you guys have any idea ?
cheers
ZeRoT
Click to expand...
Click to collapse
This may not be your problem, but I found personaly that as soon as I enabled swap, my phone became a bit unstable. It was not rebooting itself when I had compcache on. Then I turned that off and switched to swap and now my phone rebooted itself sometimes. For me compcache was noticeably faster but swap multitasks better. So I've kept swap in spite of reboots. I have also found that switching between them either way my phone becomes unstable and rebooted itself multiple times before becoming stable on compcache or at least not rebooting as much on swap.
Sent from my HTC Magic using XDA App
well i had the same issue. nothing helped, i reinstalled the spl, radio, rom, recovery, everything.
the only thing that helped is :
REROOTING YOUR PHONE
there´s no other way.
have a good day.
zerot said:
Hi guys,
I have a problem with my Magic 32B and hope one of you guys could figure out where this all come from.
Since a couple of weeks my magic has become very unstable and I would say I have about 20 to 30 freezes or reboots a day. It suddenly started when I switched from a nightly froyo to another and since then regardless on the ROM I flash I always have the same behaviour (I'm currently on the CM6 RC1).
<snip>
Click to expand...
Click to collapse
I would expect a Donut based ROM to be fine. Which ROMs have you tried since the freezing/rebooting problem started?
The next time it reboots you should take a copy of /proc/last_kmsg and post it here. You can do so with:
Code:
adb shell cat /proc/last_kmsg > last_kmsg.log
Reboot cycle
I'm sorry if I'm in the wrong area, but I also have the same problem. I have a mytouch 3g (32B). I recently flashed it with "Froyo SPF Connection" and that made it reboot just about every 30 seconds. I restored it to the 1.6 Donut rom and it kept rebooting but repeated the process and now it seems fine. The problem is I don't want the 1.6 rom but that's all can have right now since everything else slows it down and freezes it. Please help me solve this problem. I'm opened to any useful recommendations and every help is appreciated.
benjaminb007 said:
I'm sorry if I'm in the wrong area, but I also have the same problem. I have a mytouch 3g (32B). I recently flashed it with "Froyo SPF Connection" and that made it reboot just about every 30 seconds. I restored it to the 1.6 Donut rom and it kept rebooting but repeated the process and now it seems fine. The problem is I don't want the 1.6 rom but that's all can have right now since everything else slows it down and freezes it. Please help me solve this problem. I'm opened to any useful recommendations and every help is appreciated.
Click to expand...
Click to collapse
Eclair ROMs are just as stable as donut ROMs and as fast as donut. Just don't use Froyo till it's stable. Use CM5.0.8 or any CM variant and you should be fine.
I'm having the same problem after flashing the new radio the phone will boot and as soon as its done loading the home screen it will reboot then load the home scree and turn off
Flashed French Connection ROM few days back and have had same problems as above ever sense.. Flash other ROM's and they constantly Reboot. cy 6.0 Working for me now, But only my Nandroid back up of it. Re flashed it fresh and it reboots...
why dont you reroot ur phones like i told you?
This freezing and rebooting problem is weird - it doesn't make sense a lot of the time.
I've developed a ROM based on AOSP 2.2 for the G1 and it also seemingly randomly freezes or reboots.
When it reboots it's usually the result of an ARM9 crash and so far I have tracked it down to a call to a proprietary library function which doesn't return to the correct return address. It seemingly returns to a random address and the consequences of doing so is random. Sometimes it causes a freeze or a reboot and other times it doesn't.
I'm starting to suspect something in the JNI code is causing the problem but it's difficult to track it down.
FroYo SP French Connection is overclocked to 614 by default. My Mytouch (32B) reboots and freezes constantly if i don't turn it down to 576. Try turning the overclock down in set cpu to 528 first then if its stable you can try turning it up a little.
Urgh, I hadn't considered clock speed as a potential problem.
What if some of our phones are unstable at the default Froyo maximum of 528 MHz?
I am (was) in the same situation (Magic 32B). It started with CM6 RC1 first and after it, my nandroid backups got weird too! I always wiped everything and rebooted by myself several times. I never played with overclocking, compcache or ext partition - but after trying other FROYO ROMs as well, even a clean install of CM5.0.8 final was unstable got fc's and rebooted...
So, after one year of trying nearly every ROM out there, i finally made a decision: i went back to my stock rooted 1.5 cupcake!! Yes, 1.5! I never tried this ROM before - even in my first days i immediately switched to sense...
And what should i say? I'm blown away by the speed and stability of this ROM! Unbelievable! ... sad day ... really sad ....
And my decision after that: i will wait for an official FROYO for Magic, which was at least officially announced...
sad, sad, sad...
alutastisch said:
why dont you reroot ur phones like i told you?
Click to expand...
Click to collapse
Well, i think - like my approach - rerooting will not bug down the fault in FROYO ROMs. I hope it will be sorted out, but for me the daily flashing is over for now. I really appreciate the hard work of all the devs and i also donated to some, but at the end of the day i just want my phone and don't want to wait for going to homescreen or missing a call because of the lags...
sad, sad, sad...
akivlin said:
Urgh, I hadn't considered clock speed as a potential problem.
What if some of our phones are unstable at the default Froyo maximum of 528 MHz?
Click to expand...
Click to collapse
Well, I think default for stock unrooted phones is like three hundred something you could try that but it would be really slow.
hudl said:
I am (was) in the same situation (Magic 32B). It started with CM6 RC1 first and after it, my nandroid backups got weird too! I always wiped everything and rebooted by myself several times. I never played with overclocking, compcache or ext partition - but after trying other FROYO ROMs as well, even a clean install of CM5.0.8 final was unstable got fc's and rebooted...
So, after one year of trying nearly every ROM out there, i finally made a decision: i went back to my stock rooted 1.5 cupcake!! Yes, 1.5! I never tried this ROM before - even in my first days i immediately switched to sense...
And what should i say? I'm blown away by the speed and stability of this ROM! Unbelievable! ... sad day ... really sad ....
And my decision after that: i will wait for an official FROYO for Magic, which was at least officially announced...
sad, sad, sad...
Well, i think - like my approach - rerooting will not bug down the fault in FROYO ROMs. I hope it will be sorted out, but for me the daily flashing is over for now. I really appreciate the hard work of all the devs and i also donated to some, but at the end of the day i just want my phone and don't want to wait for going to homescreen or missing a call because of the lags...
sad, sad, sad...
Click to expand...
Click to collapse
I totally agree. I know waiting for the official Froyo for the Magic may take years before it's finally released, but I'm tired of flashing and testing new roms every day without getting the results I want. As a result of this frustration, I will go back to Donut 1.6 for now and wait for the official update. Hopefully 5.1 won't be out before we finally get the update
TJ Gonz said:
Well, I think default for stock unrooted phones is like three hundred something you could try that but it would be really slow.
Click to expand...
Click to collapse
Yes, I will find out the maximum Donut clock speed and test at that speed.
TJ Gonz said:
Well, I think default for stock unrooted phones is like three hundred something you could try that but it would be really slow.
Click to expand...
Click to collapse
I modified the kernel to allow only the following frequencies:
09-12 01:41:12.579 D/setcpu ( 281): Autodetecting Frequencies
09-12 01:41:12.599 D/setcpu ( 281): Frequencies autodetected: 122880 128000 245760
Click to expand...
Click to collapse
Unfortunately the phone still rebooted due to an ARM9 crash.
I've attached a small CM6 RC1 update as a test fix for the ARM9 crashing.
Anyone experiencing random freezing or reboots should give it a try by copying it to your SD card and boot to recovery to flash it.
If you install the test fix but still experience random reboots I'd appreciate if you could upload a copy of /proc/last_kmsg to http://android.pastebin.com and post the link to it in here. A logcat up to the point of the reboot would be very helpful too.
I was running the new version of cyanogen Froyo rom (RC3) and it worked fine for about a day or two but then I started having random restarts. At first it was just once in a while but then last night it got really bad. It was restarting every 2-3 minutes.
I thought the rom was the problem so I decided to try out zachattack052 & xillius200's 2.1&1.5HERO rom but I could not get the gapps to work.
At this point I was getting frustrated so I decided to just get the newest stable cyanogen rom (v5.0.8) thinking that at least this one is known to be pretty stable. Unfortunately, I am having random restart problems again (less than 30 minutes after flashing this rom). I think it most frequently restarts when I am sliding the screen back after using the keyboard. Not only that but it's noticeably slower than the other two roms.
I am getting a bit annoyed. Is it the roms that are the problem? Is it me, am I doing something wrong? Or is it a hardware problem with my phone?
Firmware version: 2.1-update1
Kernel version: 2.6.34-cyanogenmod
Mod version: CyanogenMod-5.0.8-DS
Recovery: RA-dream-v1.7.0
Programs running: Advanced Task Killer, Power Manager, Google Voice, Fancy Widget.
i have that Problem Too but then mine usually happens when its low on battery
it restarts once I take out the battery put it back in and it works fine for a while just keep it charging b4 it goes low thats what i did with mine
you just need to clean your system, run fastboot erase system -w and then try any rom you want. that should do the trick. I cant help you if you dont know how to use fastboot, in that case search for it in the forum n_n
etu_aty said:
you just need to clean your system, run fastboot erase system -w and then try any rom you want. that should do the trick. I cant help you if you dont know how to use fastboot, in that case search for it in the forum n_n
Click to expand...
Click to collapse
I've never used fastboot but I am sure I can figure it out. Does doing a wipe from fastboot clean more than doing a wipe from recovery? If so I will definitely try it.
I am running KiNgxKxROM Sapphire Sense to G1 Port v1.4 right now. I like it but I am still getting a couple random restarts a day. Two so far today, both of which were while the phone was sitting unused in my pocket.
same problem
I was having the same problem, except that my G1 was with CM 6 RC2 and it does restart only when i was trying to connect to internet through wifi or 3G. If I didnt connect to internet the phone was working OK. After I made upgrate to RC3 the problem disapiered.
Sorry for my english
You can either fastboot(you SHOULD know how to do this if you are rooted) or something that worked for me was that I switched to clockwork(using rom manager app) and flashed a new rom. BTW this should be in Q&A bud.
etu_aty said:
you just need to clean your system, run fastboot erase system -w and then try any rom you want. that should do the trick. I cant help you if you dont know how to use fastboot, in that case search for it in the forum n_n
Click to expand...
Click to collapse
fastboot -w bricked my phone.
after I erased everything it randomly restarted. went to the G1 screen then turned off. I have tried removing the battery but it still will not turn on. I have tried Home + Power, Camer + Power, Call + Menu + Power, and the power button by itself with no luck.
T-Mobile is sending me a new phone now.
Have you checked your battery lately? How old is it? What does it look like? Any bloating?
sent from superfroyo dream
Xx12thANG3LxX said:
Have you checked your battery lately? How old is it? What does it look like? Any bloating?
sent from superfroyo dream
Click to expand...
Click to collapse
I have two batteries and I tried it with both. One battery is brand new and the other is the original. When I plug it in the orange "charging" light doesn't even come on.
Hi,
I managed to brick my Milestone, terminally I'm afraid, but the symptoms are different than what I see around the forum so they might interest someone else.
So, I first backed up everything with GOT Nandroid and Titanium Backup then modded CyanogenMod 7 RC4 0.08-11.04.05 (Android 2.3.3) successfully, except that the SIM was locked and would not unlock, although it works in another phone. This was a bug supposedly fixed in version 6 of Cyanogen...
Browsing the forums, the only thing that made a bit of sense was that maybe the GSM frequency was set to the wrong value. There is a Nandroid mod (but not GOT) that allows you to change that so I entered GOT Nandroid again. Since it had no such option, I Rebooted. Then, the fun begun.
The phone got stuck on the Motorola logo and no button, not even Power, worked anymore. After waiting for many minutes with no progress, I took out the battery - that made a change , the phone shut down. I then put it back - the phone immediatelly, no, instantly, cause there's no delay as when you were powering it up, lights up with the same Motorola logo. Tried several times, always the same behavior.
I left it booting (but also connected to the charger) for a whole night, no change.
The phone is not seen by the PC when connected to USB. It won't reboot, normally or to recovery. Buttons won't work at all. Yeah, tried with or without the SIM and the sdcard, no change. Tried to start without battery, just the charger, doesn't work.
Useless to say, I am getting bored of that Motorola logo
I suspect that the bootloader in the internal memory got corrupted. Can this be flashed even if the device is not seen by the PC (I mean by the RDSLite installed on it)?
Cheers
When the charger is connected to the phone try at the same timeull out and pull in the battery while holding the buttons who will get you in the OR
Yup, it worked. So first I got the battery with a question mark. Then I put in the battery and I got a battery at 60%. Since I was holding Power+Camera, it continued to the Recovery mode and now I have a working Milestone with Cyanogen mod!!
Thank you a lot, Mikicishte.
I still have to see about the initial locked SIM problem... but that will be mostly fun.
florinadrian said:
I still have to see about the initial locked SIM problem... but that will be mostly fun.
Click to expand...
Click to collapse
Have you tried to factory reset the Milestone, to see if after that the SIM is accessible again ?
http://forum.cyanogenmod.com/topic/14099-sim-card-not-detected-after-factory-reset/
You could try also to install a logger application catlog for example (https://market.android.com/details?id=com.nolanlawson.logcat&feature=search_result ) to see in the logs if you can find out more details to help you with the investigations...
I did the factory reset as part of installing the mod.
Even if the post quoted reports the wipe as the source of the problem and not as a solution, I just wiped again with no good result.
Will try catlog.
florinadrian said:
I did the factory reset as part of installing the mod.
Even if the post quoted reports the wipe as the source of the problem and not as a solution, I just wiped again with no good result.
Will try catlog.
Click to expand...
Click to collapse
or maybe you could try to use an unlock tool to see what error is reporting
https://market.android.com/details?id=com.droidgram.bladeunlock&feature=search_result
I got a Sprint HTC One last week, rooted it, s-offed it and flashed several ROMs on it.
My problem is that in every ROM I've tested, the phone reboots after a couple of minutes.
Here are the ROMs I've tried so far:
- CLEAN ROM SPR 2.5
- CM-10.1-20130714-NIGHTLY-m7spr
- MIUI_m7wls_signed_07042013
- Slim-m7spr-4.2.2.build.7-OFFICIAL
- Sprint_HTC_One_1.29.651.10_Stock_Deodexed
- Sprint_HTC_One_1.29.651.10_Stock_Odexed_05.17.13
- Stock_w_Goodies_One_1.06
- viperROM_One_v1.1.0
I'm using TWRP 2.5, advanced wiping: dalvik, cache, data, system before flashing the ROM.
Does anyone have sugestions?
Hi bro...
There's another thread talking about that:
http://forum.xda-developers.com/showthread.php?t=2344478
alexyomar said:
Hi bro...
There's another thread talking about that:
http://forum.xda-developers.com/showthread.php?t=2344478
Click to expand...
Click to collapse
I guess that's a slightly different problem then mine.
My phone is S-OFF already and I've wiped and flashed almost every single ROM out there and the phone reboots (doesn't shutdown) every 2 minutes...
After I read some other similar issues, I'm guessing I'll have to use a RUU tool to fix the problem. The other problem is that I only have Mac and Linux...
I've read a post advising to copy the ROM file to the root of the phone's internal storage in order to do a proper flash.
Since I was always flashing the roms directly from an external usb thumb drive, I thougt it was a good idea.
I copied Android Revolution 2.5 to the phone's memory, wiped everything and flashed it. Installation whas OK so I rebooted. When selecting the wi-fi network on the initial setup I received a message saying "avoiding poor signal network" even thoug my router was about 10ft from me. After finishing the initial setup I rebooted the phone and then it got stuck hard.
Even when pressing the power button for over 20 second it didn't shut down. Now I'm waiting for the battery to die so I can see what happens on the next boot.
Again, if someone can help me on this situation, I'll appreciate it...
1alemao said:
I've read a post advising to copy the ROM file to the root of the phone's internal storage in order to do a proper flash.
Since I was always flashing the roms directly from an external usb thumb drive, I thougt it was a good idea.
I copied Android Revolution 2.5 to the phone's memory, wiped everything and flashed it. Installation whas OK so I rebooted. When selecting the wi-fi network on the initial setup I received a message saying "avoiding poor signal network" even thoug my router was about 10ft from me. After finishing the initial setup I rebooted the phone and then it got stuck hard.
Even when pressing the power button for over 20 second it didn't shut down. Now I'm waiting for the battery to die so I can see what happens on the next boot.
Again, if someone can help me on this situation, I'll appreciate it...
Click to expand...
Click to collapse
press the buttons while holding phone under a bright light and it will reboot, if that rom was a 4.2.2 rom from the intl. forum you're going to have to ruu it.
Aldo101t said:
press the buttons while holding phone under a bright light and it will reboot, if that rom was a 4.2.2 rom from the intl. forum you're going to have to ruu it.
Click to expand...
Click to collapse
This!
Sent from my HTCONE using xda app-developers app
I've only used Sprint ROMs but still got those freaking reboots. Only by using RUU (provided by viperboy) I managed to solve the reboot issue.
Now I'm waiting for a software SIM Unlock solution, since I'm in Brazil an cannot unlock it OTA.
I'll post an update here as soon as I have a solution...
So lately I'm getting this weird error wherein after the battery drops below 30% and if I try to call or if I receive a call, the phone restarts itself. And after restarting, it completes boot animation, loads "Starting Apps" screen and after that screen just goes blank(ie. Pressing any button is futile at this point of time). This keeps on repeating itself. The only workaround I have found to it is to connect a charger while restarting. After connecting charger the phone boots itself (instead of screen going blank) and works normally.
I'm currently on Cataclysm 6.0.1
Kernel : Elite Kernel
Multi ROM : Installed.
Xposed : Installed
I've tried various kernels and various ROMS combinations (except the stock ones) but the error keeps on repeating itself.
Any help appreciated.
x0nar said:
So lately I'm getting this weird error wherein after the battery drops below 30% and if I try to call or if I receive a call, the phone restarts itself. And after restarting, it completes boot animation, loads "Starting Apps" screen and after that screen just goes blank(ie. Pressing any button is futile at this point of time). This keeps on repeating itself. The only workaround I have found to it is to connect a charger while restarting. After connecting charger the phone boots itself (instead of screen going blank) and works normally.
I'm currently on Cataclysm 6.0.1
Kernel : Elite Kernel
Multi ROM : Installed.
Xposed : Installed
I've tried various kernels and various ROMS combinations (except the stock ones) but the error keeps on repeating itself.
Any help appreciated.
Click to expand...
Click to collapse
an error is when an error screen appears, you arent having an error. first thing first though, completely get xposed off your phone, completely, reflash if need be. i bet this will fix your issue. whenever weird issues appear, and xposed is installed, most likely its xposed.
simms22 said:
an error is when an error screen appears, you arent having an error. first thing first though, completely get xposed off your phone, completely, reflash if need be. i bet this will fix your issue. whenever weird issues appear, and xposed is installed, most likely its xposed.
Click to expand...
Click to collapse
Hi thanks for replying. I've followed your instructions, however the issue still persists.
So this is my current combination
Benzo ROM : 6.0.1
Kernel : Default
Multi ROM : Uninstalled
Xposed : Uninstalled.
The only change that is left to make is to change the recovery from Multi ROM to TWRP.
The most weird part of this problem is that as soon as I make a call or receive a call it restarts and enters into a black screen. However as soon as I connect charger it works normally. That is what bugs me the most. Also my bootloader and Radio are the updated ones. And I checked if there was a log in /sys/fs/pstore but there isn't any.
Please suggest.
x0nar said:
Hi thanks for replying. I've followed your instructions, however the issue still persists.
So this is my current combination
Benzo ROM : 6.0.1
Kernel : Default
Multi ROM : Uninstalled
Xposed : Uninstalled.
The only change that is left to make is to change the recovery from Multi ROM to TWRP.
The most weird part of this problem is that as soon as I make a call or receive a call it restarts and enters into a black screen. However as soon as I connect charger it works normally. That is what bugs me the most. Also my bootloader and Radio are the updated ones. And I checked if there was a log in /sys/fs/pstore but there isn't any.
Please suggest.
Click to expand...
Click to collapse
You're probably not going to like this suggestion, but here goes. In order to confirm or deny a potential hardware defect, you probably should go back to 100% stock. Fastboot flash the factory image for MMB29K. IMHO
Your issue is most likely multi. It has been known to cause random issues.
Your best bet is to make it do it again and grab a logcat or kmsg
zelendel said:
Your issue is most likely multi. It has been known to cause random issues.
Your best bet is to make it do it again and grab a logcat or kmsg
Click to expand...
Click to collapse
I'm willing to do that, but the problem is as soon as I connect it to the charger or USB on my laptop to take out log via ADB it acts normally. So, I believe the log will come out normal. Now the only option left here for me is to Factory Reset, and see how it goes.
To be honest, I never faced this issue while on 5.1.1. This just started out recently. Anyways, thank you.
cam30era said:
You're probably not going to like this suggestion, but here goes. In order to confirm or deny a potential hardware defect, you probably should go back to 100% stock. Fastboot flash the factory image for MMB29K. IMHO
Click to expand...
Click to collapse
Unfortunately that is what I believe I'll have to do.
x0nar said:
I'm willing to do that, but the problem is as soon as I connect it to the charger or USB on my laptop to take out log via ADB it acts normally. So, I believe the log will come out normal. Now the only option left here for me is to Factory Reset, and see how it goes.
To be honest, I never faced this issue while on 5.1.1. This just started out recently. Anyways, thank you.
Click to expand...
Click to collapse
There are apps out there that will do it without being connected to the pc. Try one of those. If it was me I would just drop multi rom all together. It has never been completely stable and most likely never will be.
zelendel said:
There are apps out there that will do it without being connected to the pc. Try one of those. If it was me I would just drop multi rom all together. It has never been completely stable and most likely never will be.
Click to expand...
Click to collapse
I've dropped Multi ROM completely. The issue sad-fully still persists. I have even deleted Kernel Control Apps and any apps that revolve around Root. I really am not aware of what I should be doing next other than formatting and just hoping nothing worse happens. Also could you name a few apps that could take out logcat even while booting. In a surprising twist of events, now as soon as I hit reboot on the phone, it enters into bootloop and does not return back to normalcy, until connected to a charger or PC via USB. So I guess, I could take a logcat. Thank You again.