Ok, I have been searching for a couple of weeks now but I have not found a soulution. I recently recieved a replacement Note 4. I updated it to Lollipop, then rooted and flashed Rapture.
Ever since, I have been experiencing random reboots and the occasional loss of data. This is not a Rapture problem it appears. I have had the issue with both versions of the Rapture Lollipop builds, DarthStalker, and stock Deodexed COD6. I did not have this problem on my last Note 4 which had the first Rapture build on it.
I have factory reset, I have Odined back to stock and repeated the rooting process, following the guides posted here to the letter and I still have the problem. Any help in resolving this issue is greatly appreciated.
KingBeef said:
Ok, I have been searching for a couple of weeks now but I have not found a soulution. I recently recieved a replacement Note 4. I updated it to Lollipop, then rooted and flashed Rapture.
Ever since, I have been experiencing random reboots and the occasional loss of data. This is not a Rapture problem it appears. I have had the issue with both versions of the Rapture Lollipop builds, DarthStalker, and stock Deodexed COD6. I did not have this problem on my last Note 4 which had the first Rapture build on it.
I have factory reset, I have Odined back to stock and repeated the rooting process, following the guides posted here to the letter and I still have the problem. Any help in resolving this issue is greatly appreciated.
Click to expand...
Click to collapse
Seeing that it's happening on so many different Roms; it's something you're installing on your device.
Does it happen on a fresh stock rooted COD6 with nothing installed 3rd party?
I have not tried a stock run without third party apps installed. I will try a fresh install of stock COD6 with root and see how that fairs. It normally happens the first time within an hour of flashing so it won't take long to see if it happens I believe.
I was getting one or two random reboots a day after updating to LP. I noticed most reboots happened after I finish or during use of Google All Access. I have a lot of tracks stored on my SD cards. Once I refreshed the tacks [in all access settings], I haven't has a reboot since.
Jammol said:
Seeing that it's happening on so many different Roms; it's something you're installing on your device.
Does it happen on a fresh stock rooted COD6 with nothing installed 3rd party?
Click to expand...
Click to collapse
So I tried stock rooted without third party apps installed. Got 2 reboots but no loss of data. Seems like it's something with the device itself or should I try just running without root?
dkb218 said:
I was getting one or two random reboots a day after updating to LP. I noticed most reboots happened after I finish or during use of Google All Access. I have a lot of tracks stored on my SD cards. Once I refreshed the tacks [in all access settings], I haven't has a reboot since.
Click to expand...
Click to collapse
I wish it was something that simple. The only consistency I am getting in terms of reproducing it is trying to multitasking and possibly having too many apps running in the background, but sometimes it happens with just 2 or 3 apps running so I am not sure.
What's really annoying about it all is the first unit I had ran flawlessly, even after the 5.0 update.
KingBeef said:
I wish it was something that simple. The only consistency I am getting in terms of reproducing it is trying to multitasking and possibly having too many apps running in the background, but sometimes it happens with just 2 or 3 apps running so I am not sure.
What's really annoying about it all is the first unit I had ran flawlessly, even after the 5.0 update.
Click to expand...
Click to collapse
Does your device get really hot right before it does the random reboots? Could be thermal function of the Note 4. 805SOC is a very hot chip albeit not as bad as the 810 but pretty dang close if you ask me!!! If no heat issues then see below
Give this a try:
This will require you to Odin to COD6 Stock NO ROOT!!!
Shut down and take out your External SDCard.
Boot into TWRP or Flash TWRP if you don't have it on there right now
Do a FULL WIPE: Factory Reset 3x, Advanced Wipe(Everything there) 3x, and finally Format Data(where you have to type yes) 3x
Power off your device and start it up into Download mode and Odin COD6 Stock Firmware(the full one not the partial)
Let it do it's thing and then simply use the device for a few hours on just pure stock.
DO NOT INSERT YOUR SD CARD!!! Why? We want to make sure it isn't something on your card causing Indexing to hang and force reboot.
If you get no reboots then go ahead and shutdown and insert your SDCard and use your device. Still no reboots? Then go ahead and Root. Still no reboots? It's resolved.
This process of elimination is lengthy but it is effective.
Jammol said:
Does your device get really hot right before it does the random reboots? Could be thermal function of the Note 4. 805SOC is a very hot chip albeit not as bad as the 810 but pretty dang close if you ask me!!! If no heat issues then see below
Give this a try:
This will require you to Odin to COD6 Stock NO ROOT!!!
Shut down and take out your External SDCard.
Boot into TWRP or Flash TWRP if you don't have it on there right now
Do a FULL WIPE: Factory Reset 3x, Advanced Wipe(Everything there) 3x, and finally Format Data(where you have to type yes) 3x
Power off your device and start it up into Download mode and Odin COD6 Stock Firmware(the full one not the partial)
Let it do it's thing and then simply use the device for a few hours on just pure stock.
DO NOT INSERT YOUR SD CARD!!! Why? We want to make sure it isn't something on your card causing Indexing to hang and force reboot.
If you get no reboots then go ahead and shutdown and insert your SDCard and use your device. Still no reboots? Then go ahead and Root. Still no reboots? It's resolved.
This process of elimination is lengthy but it is effective.
Click to expand...
Click to collapse
I can't say that I have noticed it in the past, however, it froze up shortly after I read the email notification of your response and was quite warm towards the top half. I pulled the battery expecting it to reboot anyway. Is there anyway to mitigate the thermal affect if it is indeed the culprit?
I will try the second method this evening and see if there's any change in behavior and report back sometime tomorrow. Thank you for your assistance with this.
KingBeef said:
I can't say that I have noticed it in the past, however, it froze up shortly after I read the email notification of your response and was quite warm towards the top half. I pulled the battery expecting it to reboot anyway. Is there anyway to mitigate the thermal affect if it is indeed the culprit?
I will try the second method this evening and see if there's any change in behavior and report back sometime tomorrow. Thank you for your assistance with this.
Click to expand...
Click to collapse
Yes but it is not recommended. Using Synapse from the playstore will do such a thing but it requires a custom Kernel. If it is a thermal issue your device may be defective seeing that it's spiking so much so quickly and just crashing.
Definitely give the process of elimination a try that I suggest in my previous post. If it fails at the first step of being pure stock no SDCard then I'm afraid you need a new device.
Hi KingBeef,
Unfortunately, I have the exact same issues you do. Except I've tried literally everything. Even Odin back to stock KitKat. Seems to reboot or randomly shut off if more than 3-4 apps are running at completely random times. No SD card as well to confirm it's not that. The only difference I see with your situation is my phone will degrade after 3rd day of use. First 2 days are flawless, then almost like a failing hard drive, things start to domino progressively worse. My last attempt was to run it only in wifi mode, no SIM card.
The only thing left is to consider unfortunately is swapping again under warranty. I myself am waiting until I go back to the US (Cad user here) to swap with TMo for another handset.
Good luck!
Sent from my D6503 using Tapatalk
So I was running CF 1.3 base for quite a while with no issues. Two days ago my phone shut down on me and would not boot. I wipe everything multiple times. I wiped cache. I did a factory reset, nothing... I wiped again. Nothing.
It gets past the Motorola logo and then just sits at the boot screen. A couple of times it would say updating android, it would finish, but then it would go right back to the boot screen. After about 8 hours it finally booted and I used it all day yesterday. This morning my issue is back. I've flashed different images to see if it has something to do with 1.3. It's all the same. I think I might try to go back to kit kat. It seems to be a software problem, but I am starting to think that something most be wrong with my hardware.
I found this thread: https://forums.motorola.com/posts/b0021413e7
I think my phone is shot... Any ideas?
When I had my Razr Maxx I had an issue that was similar and nothing I tried would fix it. Factory reset cache wipe flashing different roms nothing. Finally I decided to factory restore it with RSD Lite and after that the problem went away and I was able to do everything again like normal. I don't know why a factory reset wouldn't fix it and that did but it did.
Thanks. That is my next step. Do you know where I can find the RSD image?
Is this what I need? http://forum.xda-developers.com/dro...quark-stock-firmware-moto-maxx-droid-t3063470
Do I need to worry about flashing radios and stuff back to 4.4.4?
Seems to be. Honestly I've used it on many Motorolas in the past but I haven't read much about using RSDlite on the turbo. I would just do some googling around I'm sure you'll find it
my2cents said:
So I was running CF 1.3 base for quite a while with no issues. Two days ago my phone shut down on me and would not boot. I wipe everything multiple times. I wiped cache. I did a factory reset, nothing... I wiped again. Nothing.
It gets past the Motorola logo and then just sits at the boot screen. A couple of times it would say updating android, it would finish, but then it would go right back to the boot screen. After about 8 hours it finally booted and I used it all day yesterday. This morning my issue is back. I've flashed different images to see if it has something to do with 1.3. It's all the same. I think I might try to go back to kit kat. It seems to be a software problem, but I am starting to think that something most be wrong with my hardware.
I found this thread: https://forums.motorola.com/posts/b0021413e7
I think my phone is shot... Any ideas?
Click to expand...
Click to collapse
This just happened to me yesterday. Long story short, I have a strong suspicion that something about the recent Moto Actions update is breaking our phones for reasons that I describe here: http://forum.xda-developers.com/droid-turbo/help/complicated-problem-restore-doesnt-help-t3184251. I managed to fix it, but I re-broke it because I'm an idiot and the method I used before isn't working. If you get it fixed and get your 1.3 CF image back up and running, I would strongly recommend against allowing the Moto Actions update. I have a feeling that we're going to be hearing more about this soon from other people.
TheSt33v said:
This just happened to me yesterday. Long story short, I have a strong suspicion that something about the recent Moto Actions update is breaking our phones for reasons that I describe here: http://forum.xda-developers.com/droid-turbo/help/complicated-problem-restore-doesnt-help-t3184251. I managed to fix it, but I re-broke it because I'm an idiot and the method I used before isn't working. If you get it fixed and get your 1.3 CF image back up and running, I would strongly recommend against allowing the Moto Actions update. I have a feeling that we're going to be hearing more about this soon from other people.
Click to expand...
Click to collapse
That makes sense, after I finally got mine going, I updated Moto Actions and all the other apps it crashed again in about 12 hours. If I can finally get it to boot again, I think I am going to test your theory. If you figure out how to get it booted again, please share!
Edit, which rootjunky image did you flash? SU2-12?
my2cents said:
That makes sense. Like an idiot, after I finally got mine going, I updated Moto Actions and it crashed again. If I can finally get it to boot again, I think I am going to test your theory. If you figure out how to get it booted again, please share!
Click to expand...
Click to collapse
I did get it booted again. I flashed the kitkat update (not the stock, stock update 1, which is what you should be on if you're using mofo) file on the firmware thread that was posted here using the version of RSDlite that was posted there. The key is just to wait a really, really long time. Even if the screen goes black, it could potentially still be booting, especially if the back of the phone gets warm. I left it plugged in, let it get to the boot animation and left the house for several hours, and when I got back it appeared to be functional, but things were slow and choppy at times and my home button didn't work. The settings menu from the pull down menu didn't work either. I had to access settings from the app drawer. I tried a factory reset from the settings menu, and that just re-broke everything. So now I'm back at square one. I re-flashed the same image using RSDlite again, and now I've waited about 10 minutes and I'm still looking at the boot screen, which at this point is normal since the problem occurred.
I got a hold of an old copy of the Motorola Sensor Services apk. As far as I can tell, this is the apk that is replaced by Moto Actions, which according to Google Play is only compatible with 5.0 and above. My plan for tonight is to wait until the thing decides to boot, attempt to start the stock Sensor Services app and get it to do the sensor firmware uninstall that I mentioned in my other post. If that doesn't work, I'm going to try to install the apk that I found and see if I have any more luck with that. I'll report back here when I get a chance to do that. Let me know if you figure out a solution.
---------- Post added at 03:48 PM ---------- Previous post was at 03:33 PM ----------
my2cents said:
That makes sense, after I finally got mine going, I updated Moto Actions and all the other apps it crashed again in about 12 hours. If I can finally get it to boot again, I think I am going to test your theory. If you figure out how to get it booted again, please share!
Edit, which rootjunky image did you flash? SU2-12?
Click to expand...
Click to collapse
Yeah, I used SU2-12.
I followed the procedure outlined here to go back to stock. https://www.youtube.com/watch?v=6avEPGWB8E0 I used the SU2-12 file, but I lost everything... Thanks for the help. I hope there is a fix for this soon! I'll test your idea about MOTO Actions and report.
Edit: Well, I thought my phone was booting when I wrote the above, but it has been 30 minutes and it has not booted...
So, I can get it to boot - although it is not easy and it takes me like 30 minutes and I haven't found a full proof method yet, but after it goes to sleep I have to start the process all over. It has been a frustrating 3 days.
TheSt33v said:
This just happened to me yesterday. Long story short, I have a strong suspicion that something about the recent Moto Actions update is breaking our phones for reasons that I describe here: http://forum.xda-developers.com/droid-turbo/help/complicated-problem-restore-doesnt-help-t3184251. I managed to fix it, but I re-broke it because I'm an idiot and the method I used before isn't working. If you get it fixed and get your 1.3 CF image back up and running, I would strongly recommend against allowing the Moto Actions update. I have a feeling that we're going to be hearing more about this soon from other people.
Click to expand...
Click to collapse
I think you are onto something. I'm currently on 4.4.4 and it is bone stock. When I go into the Play Store it shows that I have Moto Actions installed, but when I click on the app it says that it is not compatible with my device. I've tried wiping the data from the app, force closing it, and clearing the cache. None of that has prompted me to uninstall the sensors. By the way, I found the Moto sensors app and tried doing the same thing, no luck.
So, I think I have the 5.1 Moto Actions installed still, which is causing the 4.4.4 image to freak out. I've thought about trying to go official 5.1 and see if that fixes it, but since I have a replacement on the way, think I might just leave it be - unless someone (like you) figures this thing out.
my2cents said:
I think you are onto something. I'm currently on 4.4.4 and it is bone stock. When I go into the Play Store it shows that I have Moto Actions installed, but when I click on the app it says that it is not compatible with my device. I've tried wiping the data from the app, force closing it, and clearing the cache. None of that has prompted me to uninstall the sensors. By the way, I found the Moto sensors app and tried doing the same thing, no luck.
So, I think I have the 5.1 Moto Actions installed still, which is causing the 4.4.4 image to freak out. I've thought about trying to go official 5.1 and see if that fixes it, but since I have a replacement on the way, think I might just leave it be - unless someone (like you) figures this thing out.
Click to expand...
Click to collapse
I ended up getting a replacement from Motorola too. If it has 5.1 on it, I'll sell it and get one with 4.4.4. Thanks a lot for the tip, by the way. I might still work on it just as a hobby, but I'm out of ideas. Of all the many, many devices I've tinkered with, this is the first one that I ever permanently messed up, so I'd like to fix it as a matter of pride, but I now only have 48 hours to do so. After looking at logcats, the partition table of the phone and the androidmanifest.xml of the motorola sensor services apk, I'm pretty much certain that this app writes those sensor drivers to a partition other than the ones that get flashed when we up/downgrade (ie system, boot, recovery, etc.), which is why these processes don't fix the problem. Theoretically, if I knew which partition that was, I could find someone with a working Turbo who could dump that image, and if I get lucky and it's a partition that isn't sig checked by the bootloader (like the radios, for example), I could flash that and be good to go. I have no idea how to figure out which partition that would be, though. The obvious choice was the "firmware" partition, but that partition has a lot of drivers that seem to relate to lots of different important things, so messing with that seems scary. I also don't know anyone who is knowledgeable enough to generate that image (myself included), so it's a moot point.
TheSt33v said:
I ended up getting a replacement from Motorola too. If it has 5.1 on it, I'll sell it and get one with 4.4.4. Thanks a lot for the tip, by the way. I might still work on it just as a hobby, but I'm out of ideas. Of all the many, many devices I've tinkered with, this is the first one that I ever permanently messed up, so I'd like to fix it as a matter of pride, but I now only have 48 hours to do so. After looking at logcats, the partition table of the phone and the androidmanifest.xml of the motorola sensor services apk, I'm pretty much certain that this app writes those sensor drivers to a partition other than the ones that get flashed when we up/downgrade (ie system, boot, recovery, etc.), which is why these processes don't fix the problem. Theoretically, if I knew which partition that was, I could find someone with a working Turbo who could dump that image, and if I get lucky and it's a partition that isn't sig checked by the bootloader (like the radios, for example), I could flash that and be good to go. I have no idea how to figure out which partition that would be, though. The obvious choice was the "firmware" partition, but that partition has a lot of drivers that seem to relate to lots of different important things, so messing with that seems scary. I also don't know anyone who is knowledgeable enough to generate that image (myself included), so it's a moot point.
Click to expand...
Click to collapse
My question is why hasn't anyone else's device gotten borked since the update? I've had it since the update was distributed with no issues and use Moto Actions continuously. Seems like if it really is a combination of writing drivers to a partition that isn't compatible it would be a universal issue. If only 2 people who have a mofo'd 5.1 IMG (out of probably hundreds) experienced issues my bet is on some weird glitch that occured when you initially flashed the updated firmware to get 5.1 working on the mofo'd device, rather than some general driver incompatibility.
GeoFX said:
My question is why hasn't anyone else's device gotten borked since the update? I've had it since the update was distributed with no issues and use Moto Actions continuously. Seems like if it really is a combination of writing drivers to a partition that isn't compatible it would be a universal issue. If only 2 people who have a mofo'd 5.1 IMG (out of probably hundreds) experienced issues my bet is on some weird glitch that occured when you initially flashed the updated firmware to get 5.1 working on the mofo'd device, rather than some general driver incompatibility.
Click to expand...
Click to collapse
I agree. Either it was a corrupt driver installation that worked just well enough for the app not to realize it, or the firmware update happens silently only when requested (similar to Google play services), and we're all one chop chop flashlight away from a phone apocalypse. Hopefully it's the former.
So, I went ahead and updated my device to official 5.1 and the problem is still there. The moto actions app that is installed still says that it is not compatible with my phone. I have cant figure out how to clear it or delete it or anything. And when I think I have it, I let the phone sleep and I can't bring it back to life again without waiting for a 15 min+ boot. Oh well, at least the bootloader says "official" now rather than "modified." So, Motorola should not complain about it. Thanks for trying to figure it out @TheSt33v
my2cents said:
So, I went ahead and updated my device to official 5.1 and the problem is still there. The moto actions app that is installed still says that it is not compatible with my phone. I have cant figure out how to clear it or delete it or anything. And when I think I have it, I let the phone sleep and I can't bring it back to life again without waiting for a 15 min+ boot. Oh well, at least the bootloader says "official" now rather than "modified." So, Motorola should not complain about it. Thanks for trying to figure it out @TheSt33v
Click to expand...
Click to collapse
Good to know. I picked the $25 option specifically because the free one requires an inspection, but I'll probably update it anyway. I'm not surprised that it didn't solve the problem though. When we flash those upgrade/downgrade images, we're basically just doing manually what RSD lite/Verizon upgrade agent does automatically.
ctopher4
TheSt33v said:
This just happened to me yesterday. Long story short, I have a strong suspicion that something about the recent Moto Actions update is breaking our phones for reasons that I describe here: http://forum.xda-developers.com/droid-turbo/help/complicated-problem-restore-doesnt-help-t3184251. I managed to fix it, but I re-broke it because I'm an idiot and the method I used before isn't working. If you get it fixed and get your 1.3 CF image back up and running, I would strongly recommend against allowing the Moto Actions update. I have a feeling that we're going to be hearing more about this soon from other people.[/QUOTE]
you called it! Just spent 2 hours reflashing 1.3 first repeated V4A, then Base. flashing sick Android upon Recovery attempt, FAIL. reflashed radios and such and with different "vol& pwr" sequence was able to get in to wipe cache. Not hat it would help me but i viewed chche Logs and im wondering if, to the right person, it would help to have copies of them?? It's a bunch of pages tho and and not sure if it would help.
My plan it to, in Recovery, Factory wipe, then reboot to Bootloader and attempt to flash base. W/ all sys.img's, then wipe caches again. ihave read the whole thread early yesterday morning but i fell asleep prob 20 times during. it was like 3 ishi think SO, i'll now go re read probably to find that you've already ruled out "my plan"
Click to expand...
Click to collapse
ctopher4 said:
TheSt33v said:
This just happened to me yesterday. Long story short, I have a strong suspicion that something about the recent Moto Actions update is breaking our phones for reasons that I describe here: http://forum.xda-developers.com/droid-turbo/help/complicated-problem-restore-doesnt-help-t3184251. I managed to fix it, but I re-broke it because I'm an idiot and the method I used before isn't working. If you get it fixed and get your 1.3 CF image back up and running, I would strongly recommend against allowing the Moto Actions update. I have a feeling that we're going to be hearing more about this soon from other people.[/QUOTE]
you called it! Just spent 2 hours reflashing 1.3 first repeated V4A, then Base. flashing sick Android upon Recovery attempt, FAIL. reflashed radios and such and with different "vol& pwr" sequence was able to get in to wipe cache. Not hat it would help me but i viewed chche Logs and im wondering if, to the right person, it would help to have copies of them?? It's a bunch of pages tho and and not sure if it would help.
My plan it to, in Recovery, Factory wipe, then reboot to Bootloader and attempt to flash base. W/ all sys.img's, then wipe caches again. ihave read the whole thread early yesterday morning but i fell asleep prob 20 times during. it was like 3 ishi think SO, i'll now go re read probably to find that you've already ruled out "my plan"
Click to expand...
Click to collapse
Damn. I was hoping I was wrong. Yeah, I did what you suggested many, many times. If you end up reflashing 4.4.4 and you see the message to uninstall the sensor firmware, do it and FLASH NOTHING ELSE until a solution is found. If not, it's really easy to get a new one from Motorola.
Click to expand...
Click to collapse
TheSt33v said:
ctopher4 said:
Damn. I was hoping I was wrong. Yeah, I did what you suggested many, many times. If you end up reflashing 4.4.4 and you see the message to uninstall the sensor firmware, do it and FLASH NOTHING ELSE until a solution is found. If not, it's really easy to get a new one from Motorola.
Click to expand...
Click to collapse
O Jeez, xda gave me a " token timed out message" but only after I hit post reply and, it was a novel! I have to get at least 2.5 hours sleep tonight because that been normal lately. Besides setting up Moto functionality, I'm golden and I do have their updates blocked best I can anyway. Hope all is working.
Click to expand...
Click to collapse
ctopher4 said:
TheSt33v said:
O Jeez, xda gave me a " token timed out message" but only after I hit post reply and, it was a novel! I have to get at least 2.5 hours sleep tonight because that been normal lately. Besides setting up Moto functionality, I'm golden and I do have their updates blocked best I can anyway. Hope all is working.
Click to expand...
Click to collapse
Awesome! Well I managed to fix it too, Moto functionality included!!!! I'll explain on my other thread.
Click to expand...
Click to collapse
What was the solution that found? I'm going through the same problem.
hey guys hope all is well
so i may have somewhat softbricked my g4 dont really know how but i will explain what i did
hopefully someone can point out where i went wrong and how to fix it
Step #1
got root using this guide previously used the guide to get root on my ATT LGG4 worked fine
so got root, was successful everything worked fine
step #2
installed flashify
granted root access; all good
installed TWRP via flashify; all good
step #3 backup via TWRP all good
step #4 flashed G4H811 10N xTreme ROM v2.0 from this via TWRP; All good
step #5 attempt to install xposed framework 64bit from xposed respository via TWRP
supposedly installed fine but thats where the problems started to occur
random crashes of main apps system apps touch screen stops responding android.system crashes etc
step#6 try to flash back to prior TWRP backup
flashed back but same problems still occur
#step 7 flashed back to xtreme rom still same problems
#step 8 flashed to H811 10N stock Restore found herehttp://forum.xda-developers.com/tmobile-g4/development/rom-g4-h811-10n-stock-restore-t3191756
still same problems even though twrp and root are now gone because "clean install of stock rom"
did i **** up during the xposed install? how do i fix this
thanks a ton guys
-ben
armadilloben said:
hey guys hope all is well
so i may have somewhat softbricked my g4 dont really know how but i will explain what i did
hopefully someone can point out where i went wrong and how to fix it
Step #1
got root using this guide previously used the guide to get root on my ATT LGG4 worked fine
so got root, was successful everything worked fine
step #2
installed flashify
granted root access; all good
installed TWRP via flashify; all good
step #3 backup via TWRP all good
step #4 flashed G4H811 10N xTreme ROM v2.0 from this via TWRP; All good
step #5 attempt to install xposed framework 64bit from xposed respository via TWRP
supposedly installed fine but thats where the problems started to occur
random crashes of main apps system apps touch screen stops responding android.system crashes etc
step#6 try to flash back to prior TWRP backup
flashed back but same problems still occur
#step 7 flashed back to xtreme rom still same problems
#step 8 flashed to H811 10N stock Restore found herehttp://forum.xda-developers.com/tmobile-g4/development/rom-g4-h811-10n-stock-restore-t3191756
still same problems even though twrp and root are now gone because "clean install of stock rom"
did i **** up during the xposed install? how do i fix this
thanks a ton guys
-ben
Click to expand...
Click to collapse
Did you flash the bootstack for 10N?
I did NOT flash the bootstack for 10n because the guide said not to if you were already on 10n
I was on 10h, rooted with TWRP.
I then installed Exposed.
After a couple of days, I flashed 10N when it was made available by MicroMod777.
Even though everyone was running smoothly with 10N, I was having:
- touchscreen issues where one of every two touches weren't recognized.
- lag up the wazoo while scrolling, etc.
I was like, wow, this ain't good.
So I uninstalled Exposed, and I was still having the issues.
Then I was going to flash my 10h Nandroid, where I wasn't having zero issues.
But then I figured I'd let 10N settle in, so to speak.
After several hours without any further changes, 10N was running like clockwork without any issues. Smooth as butter.
I mention this as it may pertain to you.
You've made the many changes, so now just let things settle down and see how it goes.
I know that sometimes things just have to settle in. Why for some and not for others? I don't know.
It just is.
You got twrp to work on att?
Sent from my LG-H811 using Tapatalk
I really hope that the issues will disappear its more than the touchscreen is unresponsive every other touch its like not working at all then it will work randomly. Also the power button doesnt seem to open the power menu either.
So as i stand rn im back on the custom room rooted twrp but no xposed. Still the same problems but i have twrp installed which hopefullyis a good thing.
I hope it resolves itself after time but that most likely wont work
And no this is a tmobile g4 i moved over to tmo the other day. Im talking on my att g4 and trying to fix the tmo g4
armadilloben said:
I really hope that the issues will disappear its more than the touchscreen is unresponsive every other touch its like not working at all then it will work randomly. Also the power button doesnt seem to open the power menu either.
So as i stand rn im back on the custom room rooted twrp but no xposed. Still the same problems but i have twrp installed which hopefullyis a good thing.
I hope it resolves itself after time but that most likely wont work
And no this is a tmobile g4 i moved over to tmo the other day. Im talking on my att g4 and trying to fix the tmo g4
Click to expand...
Click to collapse
Do a kdz restore to 10N.
Sent from my LG-H811 using Tapatalk
---------- Post added at 09:51 PM ---------- Previous post was at 09:50 PM ----------
http://forum.xda-developers.com/showthread.php?t=3107848
Sent from my LG-H811 using Tapatalk
is there a guide to do that? i cant seem to find it on here at all
armadilloben said:
is there a guide to do that? i cant seem to find it on here at all
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3107848
Sent from my LG-H811 using Tapatalk
so i did the KDZ restore booted up the phone play services crashes the power or volume buttons still dont work and the touchscreen/general ui are still extremely unresponsive and system.ui crashes like crazy
wtf is causing this i thought the KDZ restore was like a full wipe?
Just thinking out loud.
Was this device possibly plugged into an outlet and received a power surge?
Or did moisture get to it somehow?
Or something similar to the above scenarios?
I'm thinking it may be a hardware issue affecting the software, as compared to strictly a software issue.
Or maybe things just have to settle in for up to 48 hours.
Hello all. Generally I've been able to troubleshoot all my Android issues on my own. Most of the time someone has had the same problem (amirite?!). However, I'm stumped and could use a little help from the community.
I've been going along on Marshmallow with FK as my kernel. Generally, waiting a bit to take an update til SuperSU was confirmed all working correctly and that there wasn't any surprises. I had been putting off the MMB29V update for a bit just because everything was running fine and I had no real reason to upgrade. Well, one day I started getting a few FCs and things seemed a bit off performance wise so I decided that I'd go and move on to the next release.
Now, since I've had my N6 I really haven't had the need to run a custom ROM which is completely unlike my old habits on the S3. I decided that it's been a while since I've checked out AOSP so I flashed MMB29V using the batch file with no issues and then DU and their recommended GApps. Here's the first hint of an issue. When I loaded up the OS for the first time I got acore and phone FC's constantly. I instantly thought that I didn't wipe something or that I had a bad zip. I re-downloaded everything and checked MD5s. Everything looked good and after the flash I was able to get through the setup wizard without any issues. As I was sitting there checking out the tweaks and options available I started getting FCs again. It seemed related to Google apps. I did the whole process a second time and still had the same issues. Basically it seemed like at some random point in time the FCs would come and then shortly after the device would be highly unstable. I'd get random reboots, etc. Looking at the stack traces the errors seemed like odd NPEs and native errors.
I decided that AOSP wasn't going to cut it right now if I was going to have a relatively unstable phone and went to flash completely back to stock. Much to my surprise I still got the same errors! Apps like Feedly would never even be able to open. They would just FC on launch. The device hot reboots. The phone process seems to crash during most calls. I triple checked my MD5 on the download from Google. Made sure I wasn't doing something super stupid. I even tried doing the factory flash, booting to the welcome screen, then powering down, going to stock recovery, and factory resetting before continuing. All the same errors.
I've flashed back to complete stock a few times before without any issues. I've been able to flash system.img without any issues. Now it seems like the phone is completely unstable no matter what I do. I get the "Your device is corrupt. It can't be trusted and may not work properly." (red) message when doing a cold boot.
So... What gives? Am I completely blanking on a step here? Is it possible that I have a hardware issue that is corrupting stuff (I've suffered a bad DIMM before in a desktop and it was mind numbingly frustrating)?
I've burned through two backup cards of Google 2-Step backup codes! I'd really like to figure this one out!
mikejr83 said:
.
So... What gives? Am I completely blanking on a step here? Is it possible that I have a hardware issue that is corrupting stuff (I've suffered a bad DIMM before in a desktop and it was mind numbingly frustrating)?!
Click to expand...
Click to collapse
You could read the OP of the following thread and flash a debloated and prerooted ROM.
http://forum.xda-developers.com/showthread.php?t=3059493
I guess I'll try that. I'm still scratching my head why a flash from the factory image is still suffering from FC's and general instability. It also concerns me that I get the corrupted message at boot. It would be one thing if I flashed factory, then put a recovery, kernel, and rooted, but I haven't done that.
Hopefully I'll get a chance to try that this evening. Thanks for the link to that image. It's pretty much what I run when I take an update.
N, n, ne, necromancy!
I brought this thread back to life because I've never been able to solve the instability issues since my last post back in March.
Having some free time lately I decided to nuke my device and start again. I first grabbed the latest stock image and flashed stock. Then I downloaded the latest TWRP and Dirty Unicorns and decided that I'd give it a whirl again. I had FC issues right after the first go at it. I decided to try another GAPPs and do it again. I was able to get through setup. It took a few hours but the FCs started again.
I decided that I would try factory resetting the device and then starting a setup. I remembered that on my previous devices that I sometimes would have to do an immediate factory reset after flashing.
Well that did crap. FCs are random. The device is stuck booting now after a hot reboot.
How can I debug this? What do I need to grab from a logcat? Is there a way to run something like memtest to see if there is a bad section of RAM and something against storage to see if there is a bad sector?
This is frustrating as hell!