Random Freezes and Reboots with 4.1.2 - RAZR HD Q&A, Help & Troubleshooting

I reluctantly took the OTA to 4.1.2 on my Verizon Droid RAZR MAXX HD. The phone runs fine. I haven't had any noticeable issues with signal strength, battery life or anything that other people have been mentioning. What has been happening though, is it will randomly freeze then after a few seconds reboot.
My first thought was to do a factory reset which I did twice. Little to no improvement.
After I unlocked my bootloader, I installed the TWRP recovery. None of the modified 4.1.2 ROMs meant for Safestrap would properly flash.
I then used AD Fastboot to completely a Flash a new image of the firmware, back to stock recovery and everything. I couldn't go back to 4.1.1 so I flashed 4.1.2 hoping that the problem was in a corrupt file. Still rebooting.
Finally I flashed an Image of a mdofified firmware with the DST ROM, TWRP and a few other improvements baked into the firmware. It's rebooting less often now, but it's still rebooting. The reboots don't seem to be linked to a specific application, which makes me think it's some sort of background process, but every process I recognize as unneeded hasn't stopped the rebooting even when force stopped.
As anyone else having any problems like this? I don't feel that it's a hardware issue as the phone worked flawlessly on 4.0 and 4.1.1. Any suggestions?

So my situation is similar... sorta.
Stock non-rooted phone. Its my wife's phone.. Every since the 4.1.2 Update her phone constantly randomly reboots.
In safe Mode it seems to work fine so that led me to believe it was an application.
So Out of safe mode I removed EVERYTHING it'd let me remove.. Still Rebooted.
Factory Reset... Still reboots.
Then I Used RSD lite and Loaded the Firmware back onto it Manually. STILL reboots.
Any Ideas would be appreciated..

sammyboy405 said:
So my situation is similar... sorta.
Stock non-rooted phone. Its my wife's phone.. Every since the 4.1.2 Update her phone constantly randomly reboots.
In safe Mode it seems to work fine so that led me to believe it was an application.
So Out of safe mode I removed EVERYTHING it'd let me remove.. Still Rebooted.
Factory Reset... Still reboots.
Then I Used RSD lite and Loaded the Firmware back onto it Manually. STILL reboots.
Any Ideas would be appreciated..
Click to expand...
Click to collapse
I hadn't tried safe mode. If that is the case, then maybe it's an issue with a system service and the kernel? I feel that if that were the case there'd be more people having the problem though. The only other thing I could think of is maybe an issue with the new radio firmware? Do you know if safe-mode disables the radios?

just got my brand new HD today and after a few hours let it OTA to 4.1.2, and have experienced the random freezes and reboots since upgrading... like the OP I've tried freezing/disabling everything in turn trying to figure out the culprit and found none... however I've noticed it does not happen that much, if at all, if the phone is sitting idle, however happens much more frequently only when I'm listening to music through Poweramp if that helps at all
sent from my RAZR HD

I had the exact same problem as you guys, and the issue was that somehow, I had accidentally gotten the stock 4.0.4 sbl1, sbl2, sbl3, and rpm partitions mixed in with my 4.1.2 installation. After fastbooting stock 4.1.2 everything, my phone worked without a hitch. And like you said anoninja118, it rebooted more often when I was listening to music. I would suggest trying to fastboot stock 4.1.2 again, and put nothing on it, make sure it works, and then experiment with putting on applications. sammyboy405 and AtrusNex, when you fastbooted, was it working fine until you started loading applications onto it?

Mr.Parkinson said:
I had the exact same problem as you guys, and the issue was that somehow, I had accidentally gotten the stock 4.0.4 sbl1, sbl2, sbl3, and rpm partitions mixed in with my 4.1.2 installation. After fastbooting stock 4.1.2 everything, my phone worked without a hitch. And like you said anoninja118, it rebooted more often when I was listening to music. I would suggest trying to fastboot stock 4.1.2 again, and put nothing on it, make sure it works, and then experiment with putting on applications. sammyboy405 and AtrusNex, when you fastbooted, was it working fine until you started loading applications onto it?
Click to expand...
Click to collapse
Not really any difference between no installed programs, so I'm guessing it's something in the Motorola or system applications. I've been noticing that it seems more likely to reboot during media streaming. Currently testing the phone in my free time to see if I can trace the issue.

Got fet up with it enough I just called Verizon and did a warranty replacement. They shipped one overnight. And wife hasn't had a reboot/freeze yet. So I suspect there was a hardware issue causing the issues.
All seems well so far.

I just got a recertified device and am having the same issues. Seems connected to music. It only happens when I'm using Spotify or Pandora. Also appears others are having a similar reaction with music apps.
Sent from my DROID RAZR HD using xda app-developers app

I'm confounded as to finding hte source of the problem. Every application I've checked, that isn't a main Android service seems to be working fine and doesn't stop the reboots when disabled. I guess I can only hope the problem is remedied with a newer issued kernel or the Cyanogenmod kernel.

its definitely music related, only happens during playback through headphones or phone speaker while playing music... doesn't matter if its streamed or local from SD card... strangely enough it plays fine through bluetooth but I'm rooting and putting CM on this thing as soon as it charges before I throw it at the wall, its sooooooo freaking annoying
sent from my RAZR HD

Installing Cyanogenmod 10.1 seemed to fix my problem. I'm guessing the AOSP based kernel fixed whatever issue existed within the Verizon 4.1.2 kernel. You might try the same and see how it works out.

sammyboy405 said:
So my situation is similar... sorta.
Stock non-rooted phone. Its my wife's phone.. Every since the 4.1.2 Update her phone constantly randomly reboots.
In safe Mode it seems to work fine so that led me to believe it was an application.
So Out of safe mode I removed EVERYTHING it'd let me remove.. Still Rebooted.
Factory Reset... Still reboots.
Then I Used RSD lite and Loaded the Firmware back onto it Manually. STILL reboots.
Any Ideas would be appreciated..
Click to expand...
Click to collapse
Hi, I'm having the same issues. Now my phone is stuck in a factory reset. It goes to the Android Robot with the spinning symbol in his chest, and stays there. I can get into Fastboot mode, and did try flashing what I thought was the correct file. But I keep getting a "Failed flashing process. Unknown fastboot command. (getvar)" Where did you get the file that you flashed in RSDLite?

evltwn72 said:
Hi, I'm having the same issues. Now my phone is stuck in a factory reset. It goes to the Android Robot with the spinning symbol in his chest, and stays there. I can get into Fastboot mode, and did try flashing what I thought was the correct file. But I keep getting a "Failed flashing process. Unknown fastboot command. (getvar)" Where did you get the file that you flashed in RSDLite?
Click to expand...
Click to collapse
You have the right file.. but you need to edit the XML file in it.. inside it there are 2 or 3 lines with the getvar command.. delete those lines.. save it and bam.. should work fine.

sammyboy405 said:
You have the right file.. but you need to edit the XML file in it.. inside it there are 2 or 3 lines with the getvar command.. delete those lines.. save it and bam.. should work fine.
Click to expand...
Click to collapse
Okay, so here's my question. Do I delete the whole line or just getvar? Do I delete this whole line? I believe it's in there twice.
"<step operation="getvar" var="max-download-size" />"
---------- Post added at 07:30 AM ---------- Previous post was at 06:53 AM ----------
Ok, so I went ahead and deleted the whole line and moved it up so there wasn't any space between lines. I tried flashing the file, and now I'm getting another fail. It says "Failed flashing process. 1/27 flash sbl1 "sbl1.mbn" -> USB error occurred while reading/writing" What do I do next?

Related

[Q] Anyone having freezes, reboots, ALSO in CWM recovery?

I have had my TF for a week or so, and have had no issues whatsover. I have am rooted, running a custom kernel.
All of the sudden I am having the TF reboot at random places, and now it is freezing even in CWM recovery. I wiped everything and went back to stock and still having the problem (on 3.1). Anyone else with this issue, and does it sound like hardware at this point? I think I may return it today, but I am nervous since the screen on this one is perfect.. don't want to get one with light bleed like my last.
Thanks guys.
yes. A quick search will show you the multitudes of threads regarding this issue.
skydirt said:
yes. A quick search will show you the multitudes of threads regarding this issue.
Click to expand...
Click to collapse
Yeah.. I get that.. I have been on XDA for 4 years.
I understand the freezes and reboots happen and are happening and other people are having them happen, however per my subject line I was looking for people who are having it happen while they are in their recovery mode. I have had the tab freeze after booting into recovery, as well as during a restore and backup. I wasn't having any issues for an entire week and without any kernal or rom mods this just started. (SPECIFICALLY IN RECOVERY MODE AS WELL AS NORMAL MODE)
If it freezes + reboots in recovery, see if a Ramdump file is placed in the root of your /sdcard/ folder. If so, paste it up here so we can look at it.
sassafras
sassafras_ said:
If it freezes + reboots in recovery, see if a Ramdump file is placed in the root of your /sdcard/ folder. If so, paste it up here so we can look at it.
sassafras
Click to expand...
Click to collapse
I actually have a bunch of those files. I attached them here. Oddly, today I am trying to dup the issue after the tablet has sat on but unused, it is working fine. I went into CWM, moved around the menus and waited for it to freeze but it didn't. I restored my backup and am currently testing different things to repeat the freezes. I know there was an issue so if possible I would love to be able to find out what it was/is, and make sure it will or won't happen again so I can get a replacement if needed while I can.
I post if I have the issue again..
EDIT: yup rebooted 3 times again after barely using the tablet. Also completely locked up on one boot before I even put in my pass pattern.
I then went into recovery mode, moved around the menu system and it froze again in CWM.
superevilllama said:
I actually have a bunch of those files. I attached them here. Oddly, today I am trying to dup the issue after the tablet has sat on but unused, it is working fine. I went into CWM, moved around the menus and waited for it to freeze but it didn't. I restored my backup and am currently testing different things to repeat the freezes. I know there was an issue so if possible I would love to be able to find out what it was/is, and make sure it will or won't happen again so I can get a replacement if needed while I can.
I post if I have the issue again..
EDIT: yup rebooted 3 times again after barely using the tablet. Also completely locked up on one boot before I even put in my pass pattern.
I then went into recovery mode, moved around the menu system and it froze again in CWM.
Click to expand...
Click to collapse
Hey there superevilllama, glad to see you back on XDA. Question, are you running custom firmware, ie. custom kernel, ROM, etc? If so, I would suggest downloading the stock firmware from ASUS and flashing back completely to stock and see if that alleviates any issues. If this continues to happen on a completely stock system, you might have faulty hardware.
It was the kernel...
Alright guys.. It was the kernel. I wiped and reset to stock, thinking I had already went back to stock kernel but apparently flashed the same kernel instead of stock.
I checked Clemsyn's kernel thread and # 17 of his had other people getting lockups and reboots too, OC or not. Gave me a scare because I did a bunch of things at one time.. updated kernel, got a new keyboard dock, updated setcpu.
I kept freezing all over the place and rebooting, OC or not. Thought I restored back to stock kernel but I didn't. Thought it was wierd as I had no issues before. Back to 16 of Clemsyn's kernel and all is well, both when not overclocked and OC to 1.5ghz.
I appreciate your help guys. Glad to know my TF is still in good shape. Good thing because the replacement I got had bbaaadd light leakage. Now I can just take it back.
Yes, it was the kernel.
More importantly, it looks like it was the clock speed.
sassafras
It is wierd that it froze in recovery mode tho. I thought recovery had its own kernel, I didn't think it used whatever kernel I had flashed. Eh either way I am glad it is working.

Need help - soft-bricked phone and can't recover

Ok, I'm having some major issues here and hope someone can help. I seem to be "soft-bricked." My Maxx will boot up, gets to the droid graphic (right before it normally gets to the unlock screen), screen dims and capacitive buttons light up, then it just pulses brighter every 10 seconds or so. Once, after sitting for a while, a voice said "Loss of service."
History:
1. Was rooted, unrooted to get the OTA, re-rooted. Everything was fine.
2. Got tired of the wireless charging sound, so I applied the fix noted here - http://forum.xda-developers.com/showthread.php?t=2450085&page=3
3. Also had Xposed installed with NFCUnlock and GravityBox.
4. Was running into issues with apps randomly losing root access, and the wireless charging sound would come back, so I downgraded Xposed to the previous version as recommended in another thread.
5. Also was using DelayedUnlock app, so I disabled USB Debugging as recommended.
6. Still faced issues with apps losing root access, so I decided to restore the apk I replaced in #2 with the backup I made. Rebooted phone and am soft-bricked (I guess).
7. Downloaded the latest FXZ (http://sbf.droid-developers.org/obake/list.php) and used HouseofMoto (http://forum.xda-developers.com/showthread.php?t=2450702) to flash it, no help. Deleted the <step operation="getvar" var="max-download-size" /> line as recommended in another thread (http://forum.xda-developers.com/showthread.php?t=2416478&page=6) and flashed again, still doesn't work.
I posted this in another thread in General, but was afraid it would get lost in the thread and wasn't sure that thread was appropriate for my request for help. Any help would be greatly appreciated!
Nevermind, impatience got the best of me and I factory reset my phone, so I'm back up and running again. Hated to do it as I didn't want to lose all my stuff, but hopefully I can get it re-rooted and restore my TB backups. A little worried about re-rooting, though.
osucowboy96 said:
Nevermind, impatience got the best of me and I factory reset my phone, so I'm back up and running again. Hated to do it as I didn't want to lose all my stuff, but hopefully I can get it re-rooted and restore my TB backups. A little worried about re-rooting, though.
Click to expand...
Click to collapse
Just in case anyone else has similar issues and reads this, I believe after trial and error I found the culprit. The DelayedLock app seems to be the issue causing my brick. Will be avoiding this paid app, sure wish I could get a refund on it.

[Q] Flashing no longer possible: Flash successful but system does not change

Hello!
I can no longer flash anything to my GT-P5110, even factory reset has no effect. The internal storage seems to be read-only.
I think this is a longer story: About one year ago the stock firmware became incredibly slow, to the point that processes started to force close, then my user data was lost, and after factory reset the tablet went into endless boot loop.
So I decided to give CM10 a try and it worked flawlessly. The tablet was fast again. I even could upgrade to CM11 later. But around 2 month ago, only sometimes processes started to force-close or the tablet randomly rebooted itself - mostly during charging. I left it that way in the charger for some days because I had no time to bother with that issue. Then, I tried to factory reset my device only to find out that this has absolutely no effect. Installing app updates: No effect. Changing system settings: No effect. And apps start to force-close at an insane rate short after boot. The device is unusable. My could only shut down and reboot into recovery. I left the tablet lying around, turned off, out of charger, for 2 months. Now I tried to investigate:
When I "adb shell" into recovery and call dmesg, I see lots of these lines:
Code:
mmcblk0: timed out sending SET_BLOCK_COUNT command, card status 0x400d00
I think something is really broken with the internal storage. I tried to flash a newer recovery but it has no effect, even when done from download mode.
Factory reset sometimes fails with an error. Reinstalling CM fails with an error. Wiping cache seemingly succeeds but I'm sure it has no effect. I tried installing SlimRom instead which seemingly succeeds, too - but after reboot I'm greeted with the CM boot logo again.
I tried to flash stock firmware with Odin. It is very very slow, runs for about 15 minutes, then fails at around 50%. Of course: That "half flashed firmware" does in no way affect the device: It still boots CM11 "without problems", then a few seconds after finishing boot (showing home screen), force-closes start to pop-up.
What should I do? I suppose the device is out of warranty for a few weeks or months, now. And even when not: It has been flashed with CM, the triangle counter is not zero. I suppose that combination of problems (read-only/failing storage, non-stock firmware) voids warranty in a way that Samsung will deny any repair. If at least I could return the device to stock firmware things would be different maybe.
Any ideas what I could try? Is it possible that the internal storage is simply fried? fsck'ing the partitions shows no errors, just the data partition is unclean with unwritten journal data but all data is readable. So the internal storage has probably not died. It just sticks to read-only mode for whatever reason.
I've found some posts with similar problems but those seem to be about older Galaxy Tab 1 devices built 2011 or before.
Just reading over this and it sounds very similar to what I'm currently facing, which is doubly annoying as no one else has chipped in a solution
I had reboot issues with my Tab2 10.1 (GT-P5110) on stock so after realizing I'd need to factory reset bite the bullet and rooted so I could use CM10.
Had occasional reboots but nothing I couldn't live with however from yesterday evening the tablet is seemingly stuck in a boot loop. It comes on, some apps fire up and an update starts. Sometimes apps force close then BOOM I get the boot splash screen.
I've tried factory reset in recovery (CWM 6.0.2.7) to no avail and wiping just about everything which also had no noticeable effect as all my settings and the rom are still the same when I get back in (albeit briefly!).
I've tried flashing new recovery via ODIN which reported a success however that also didn't appear to take. I'm beginning to think it some serious file system or storage corruption ;(
Same problem here...
Hopefully someone can come up with a solution or at least a cause. I've tried to Odin every recovery available for my 5113 and nothing has taken. I'm currently on Omni with cwm and tried to update to the latest cwm and twrp and aroma installer yet nothing takes. I too rooted because of the incessant bootloops about 3 months ago.
bigg fella said:
Hopefully someone can come up with a solution or at least a cause. I've tried to Odin every recovery available for my 5113 and nothing has taken. I'm currently on Omni with cwm and tried to update to the latest cwm and twrp and aroma installer yet nothing takes. I too rooted because of the incessant bootloops about 3 months ago.
Click to expand...
Click to collapse
For what I can tell, my device is effectively read-only. Even in download mode (Odin) I cannot even flash a different recovery (tried to flash TWRP, still boots CWM).
hurikhan77 said:
For what I can tell, my device is effectively read-only. Even in download mode (Odin) I cannot even flash a different recovery (tried to flash TWRP, still boots CWM).
Click to expand...
Click to collapse
exactly, can't even uninstall an app. It's as if it boots from a permanent back up because even deleting pictures or files isn't permanently successful. You can uninstall and delete to your hearts content, get false hope, and get crushed after it reboots and everything is unchanged
Not looking very optimistic for this I was getting a similar inkling that it's gone into a permanent RO mode as not even the wipes from recovery have an effect. I'd also tried un-installing apps as I noticed one updating and thought it was crashing it however even when it did fire up and I disabled WLAN to stop Play Store auto-updating and removed the app on the next reboot cycle the app was back:crying::crying:
I fear I may have a big white paperweight....
Sounds like the internal partitions might need to be completely reformatted. This CAN be done through recovery, but is tricky... However without actually having your device in my hand I'm not sure 100 what the best course of action would be. Try searching for the commands to format (or maybe someone else will post them) or maybe PM me for them but no promises. I won't post them publicly on XDA because honestly there are too many users who do stuff like one-click root and don't actually know what they're doing and I don't want to be in some way responsible for someone following the command wrong and bricking their device for good. I don't need that on my conscience. Personal choice.
Sent from my Nexus 4 using XDA Premium HD app
shakatu said:
Sounds like the internal partitions might need to be completely reformatted. This CAN be done through recovery, but is tricky... However without actually having your device in my hand I'm not sure 100 what the best course of action would be. Try searching for the commands to format (or maybe someone else will post them) or maybe PM me for them but no promises. I won't post them publicly on XDA because honestly there are too many users who do stuff like one-click root and don't actually know what they're doing and I don't want to be in some way responsible for someone following the command wrong and bricking their device for good. I don't need that on my conscience. Personal choice.
Sent from my Nexus 4 using XDA Premium HD app
Click to expand...
Click to collapse
Would this method be any different to the way it attempts to reformat the internal partitions when you select to format the various mounts from CWM? If so I'm more then willing to give it a go as I really have nothing to lose as the damn thing is useless atm!
shakatu said:
Sounds like the internal partitions might need to be completely reformatted. This CAN be done through recovery, but is tricky... However without actually having your device in my hand I'm not sure 100 what the best course of action would be. Try searching for the commands to format (or maybe someone else will post them) or maybe PM me for them but no promises. I won't post them publicly on XDA because honestly there are too many users who do stuff like one-click root and don't actually know what they're doing and I don't want to be in some way responsible for someone following the command wrong and bricking their device for good. I don't need that on my conscience. Personal choice.
Sent from my Nexus 4 using XDA Premium HD app
Click to expand...
Click to collapse
Good call......Smart move?
help!!
same issue here , sort of .. i have stock rom and stock recovery and i cannot flash CWM .. no matter how many times i try through ODIN or hemidal nothing changes.. any idea what is going on here?
PMs have been sent. Hopefully it works.
Sent from my Nexus 4 using XDA Premium HD app
im also having this issue with my galaxy tab2 7".. help is badly needed
Well, the proposed fix I had didn't help. Was worth a shot...
Sent from my Nexus 4 using XDA Premium HD app
hope someone finds a solution for this.
No Access to ADB
shakatu said:
PMs have been sent. Hopefully it works.
Sent from my Nexus 4 using XDA Premium HD app
Click to expand...
Click to collapse
Hi Shakatu,thanks for the PM, however, my device in ADB is unauthorised, so wont let me get into shell. Is there a way around this please?
sunnytimes said:
same issue here , sort of .. i have stock rom and stock recovery and i cannot flash CWM .. no matter how many times i try through ODIN or hemidal nothing changes.. any idea what is going on here?
Click to expand...
Click to collapse
Unmark "Auto Reboot" in Odin when CWM is flashed... Stock room overwrites it during start.
After flashed CWM start in Recovery mode and flash new ROM.
this is offtopic in this tread
same problem please help me... :crying:
seagman said:
Unmark "Auto Reboot" in Odin when CWM is flashed... Stock room overwrites it during start.
After flashed CWM start in Recovery mode and flash new ROM.
this is offtopic in this tread
Click to expand...
Click to collapse
i have tried that 100 times .. its also exactlly what this thread is about , not being able to flash because nothing changes..
sunnytimes said:
i have tried that 100 times .. its also exactlly what this thread is about , not being able to flash because nothing changes..
Click to expand...
Click to collapse
same here too, i have same issue.. unable to flash or do anything to my phone....
Probably this is the end for our tab. As off now the tab is useless.
Sent from my GT-N7000 using XDA Free mobile app

[Q] Bricked xt925 - read-only eMMC ?

Hello,
Since yesterday my phone is crashing about 20-30 seconds after properly booting. I can unlock the phone with my lockscreen pattern, I land on my homescreen but process like Google Play Services goes like "x has stopped working".
On CWM I've erased /system and /data and then reflash a rom (Slimkat or CM), Erasing and flashing process on CWM seems to work as planned but when the phone reboot it's still on Slimkat with all my datas, like if nothing have been done in CWM.
So I've rebooted on the bootloader and tried a "fastboot -w", again the process seems to be ok on my pc but when the phone reboot it is still on this f**ked rom with all my datas, like if fastboot have done nothing.
I've tried to flash an up-to-date CWM, same thing again.
I think the eMMC chip are deeply corrupted, they say any writing on it is ok but in fact they are read-only, which may explain why all the process are crashing after the boot and why flashing seams ok but are useless.
What do you think XDA, andy idea about my problem ? Do you think it's an Hardware issue or what can I do to solve it ?
Why not flashing a stock firmware to go back to STOCK?
joel_sinbad said:
Why not flashing a stock firmware to go back to STOCK?
Click to expand...
Click to collapse
I've tried it with RSDLite but same thing again, everyhing seams ok in RSDLite, the 22 blocks are writed but at the reboot it's still the same Slimkat with my datas.
Ezekiel3 said:
I've tried it with RSDLite but same thing again, everyhing seams ok in RSDLite, the 22 blocks are writed but at the reboot it's still the same Slimkat with my datas.
Click to expand...
Click to collapse
if infact it has gone read only as has happened to some other users, there is no known fix. all known angles have been explored, even with input from a developer.
if you find a fix, post it, it may help others.
most likely, you will need a new phone.
I agree with bwen diord...aint never see anyone recover from that, least not yet.
cmh714 said:
I agree with bwen diord...aint never see anyone recover from that, least not yet.
Click to expand...
Click to collapse
I've just see it's possible to boot from the SD card in that case but I'm to lazy to try it.
Goodbye little RAZR HD, we have covered a lot of mileage together, it's time to leave. :angel:
Anyway thanks for the help XDA

Stuck in Optimizing App xxx of xxx

I recently upgraded my phone from 4.4.4 to the latest OTA. It was working fine for a while but it crashed, rebooted and keeps (re)optimizing the apps. It'll get stuck on some of them for a long time and might make it through, or I hard reboot it and it does it all over. Whenever it does make it through, it says "starting apps" and then reboots and does it all over again.
I've cleared the cache multiple times and restored the stock recovery, but still not working. Does anyone else have any other suggestions that I could try??
Also I read somewhere that there was a zip I could possibly flash to use all the cores, as lollipop only uses one during this process? Does anyone know where that is?
Thanks.
natboy said:
I recently upgraded my phone from 4.4.4 to the latest OTA. It was working fine for a while but it crashed, rebooted and keeps (re)optimizing the apps. It'll get stuck on some of them for a long time and might make it through, or I hard reboot it and it does it all over. Whenever it does make it through, it says "starting apps" and then reboots and does it all over again.
I've cleared the cache multiple times and restored the stock recovery, but still not working. Does anyone else have any other suggestions that I could try??
Also I read somewhere that there was a zip I could possibly flash to use all the cores, as lollipop only uses one during this process? Does anyone know where that is?
Thanks.
Click to expand...
Click to collapse
To make things clearer. Previous what ROM were you on? After your proclaimed (OTA), what was the ROM suppose to be?
I went from the Oneplus One CM 4.4.4 to the CM 5.1 OTA. Not sure why you're don't believe me..
I think I might have bad memory or flash or something at this point..
So since yesterday I've tried using the tutorials here to flash stock Kitkat with the same errors happening. When it boots up, I get a done of crashes on things like gapps and process.acore. I also tried flashing the stock Lollipop; both using the non fastboot and fastboot way. Every time wiping everything with all the same results. The only rom I've had some slight uptime with has been slimrom without gapps as there's not much running there. Once I add the gapps package to it, processes start crashing again.
Does anyone know of a memory/cpu/flash test I could try, or any other suggestions? Thank you.

Categories

Resources