After updating the latest KtManta kernel my nexus 10 lost its root capabilities, super user won't just work, it is just me or it is a known issue?
I've flashed the December version of the kernel afterwards and the problem prevails (ktoonsez doesn't include every kernel download link, a bad practice in my opinion)
I am on CM now and everything is working fine, I wonder if anyone has been victim to this weird issue
Sent from my Nexus 10 using Tapatalk HD
zombiegenerator said:
After updating the latest KtManta kernel my nexus 10 lost its root capabilities, super user won't just work, it is just me or it is a known issue? ...
Click to expand...
Click to collapse
I am guessing but is this a permissions issue? I've flashed KTManta a number of times including just yesterday with TWRP and never had the issue you describe. Occasionally, right after flashing a ROM or Kernel, I have seen from TWRP a "Fix Permissions" message which I always execute. Some custom ROM/Kernels flash instructions even include a "Fix Permissions" instruction.
Also sometimes after flashing then rebooting I've had to "reinstall" Superuser so it can grant root permissions to various programs. As a habit, right after a new flash, I start Superuser once just to see if it says it needs to be reinstalled. This is not a reinstall from an apk but is a dialogue message displayed when the app is started.
As I wrote this is purely a guess on my part.
I had a laugh at the thread title. (sorry) You either have a corrupt download or something else really weird going on. A kernel wont remove root from your unlocked firmware and ROM files unless the flashing script is actually programmed to remove the files needed. Which its not.
Well this is strange, because I have fixed the permission issue and wiped cache and dalvik, not once but multiple times (I set up the kernel thrice, after it was malfunctioning).
But seeing you two replying, I set up KtManta over CM today and it is not giving me a bit of trouble, strange indeed.
btw, is it true that KTManta fixed the color issue a bit?
Yes it does fix the color a little bit.
What ROM were you on that you had this problem?
EniGmA1987 said:
Yes it does fix the color a little bit.
What ROM were you on that you had this problem?
Click to expand...
Click to collapse
Stock
Sent from my Nexus 10 using Tapatalk HD
zombiegenerator said:
Stock
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
It won't cause you to lose root but it is also not really designed to use with stock either. Most if not all custom kernel users are on CM, AOKP or AOSP ROMS.
brees75 said:
It won't cause you to lose root but it is also not really designed to use with stock either. Most if not all custom kernel users are on CM, AOKP or AOSP ROMS.
Click to expand...
Click to collapse
What's the difference between AOSP and stock roms?
And yes it's now working flawlessly with CM.
Sent from my Nexus 10 using Tapatalk HD
Related
Entropy recently stated that using any leaked build was dangerous.
I have used every single version of AOSP and CM9 from the beginning to current, jumping between and back and forth from GB many times with no issues.
I have also never SEEN a report of anyone bricking (when properly) flashing around with these roms.
Just curious if a case actually exists.
crawlgsx said:
Entropy recently stated that using any leaked build was dangerous.
I have used every single version of AOSP and CM9 from the beginning to current, jumping between and back and forth from GB many times with no issues.
I have also never SEEN a report of anyone bricking (when properly) flashing around with these roms.
Just curious if a case actually exists.
Click to expand...
Click to collapse
No but there is a risk. And the question is : "Do you want to take this risk while CM9 is announce next week with a safe kernel".
I was using Imilka Cm9, and yesterday i flashed back to GB. Maybe you could wait one week and avoid flashing a hazardous repack !
I had no issues with Imikas cm9 roms, I used all 3 of them and have since flashed to a stock gingerbread as the video playback in all the ICS roms is not good enough yet compared to GB roms.
I have tried all the ICS leaks and gone back to GB with no issues, just waiting for a proper stable release of ICS with good video playback performance as I get in GB then I will stick with the Ice Cream
remixtech said:
No but there is a risk. And the question is : "Do you want to take this risk while CM9 is announce next week with a safe kernel".
I was using Imilka Cm9, and yesterday i flashed back to GB. Maybe you could wait one week and avoid flashing a hazardous repack !
Click to expand...
Click to collapse
I wasn't stating that there isn't a risk, or that anyone should chance it. Just simply that I have not heard of a single case of anyone having a problem with iMilka's releases (killing the board). Therefore my none developer point of view is that the risk must be VERY small IF said risk does truly exist with all Kernel Leak builds.
It SEEMS to me that the problem does not lie with the kernel build but the way it is scripted and executed. Hence why no one has ever had the problem with AOSP/CM9, but the problem came up with Angelom's kernel and the last Stunner build. The problems were also immediate in both cases, again where no one has ever had this problem caused by AOSP/CM9. So YES, I am sure AOSP/CM9 could have caused the problem if iMilka made whatever mistake was made by Stunner/Angelom, but I would say to me it is quite obvious he did not, and that the problem IS a mistake in the way the kernel is handled. Speculation and opinion only of course.
I have been running them since the beginning, so I am not saying I personally would have chanced it this close to offical ICS / Official CM9, but i've been running his releases for quite some time.
crawlgsx said:
Entropy recently stated that using any leaked build was dangerous.
I have used every single version of AOSP and CM9 from the beginning to current, jumping between and back and forth from GB many times with no issues.
I have also never SEEN a report of anyone bricking (when properly) flashing around with these roms.
Just curious if a case actually exists.
Click to expand...
Click to collapse
Flashed all imilka Roms from day one, and never had as much as a hiccup on any one of them.
The question is if anyone tried to restore a cwm backup ? The most of the bricks were caused by doing that task..
Sent from my GT-N7000 using xda premium
No issues here either with Midnote or TeamMid ROMS (also tried a couple of Alba versions and Stunner).
I have flashed many times and with LP5 kernel through CWMR or Mobile Odin including full wipes.
I have made nandroid backups but haven't tried to restore any, perhaps this has saved me?
Tried CWM restore twice on ICS (missed reports that it is not recommended). Both times ended with corrupted system partition. But both times fixed this problem by flashing stock ROM with desktop Odin. Had no problems after.
Sent from my GT-N7000 using xda premium
dimcus said:
Tried CWM restore twice on ICS (missed reports that it is not recommended). Both times ended with corrupted system partition. But both times fixed this problem by flashing stock ROM with desktop Odin. Had no problems after.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Exactly the same here. Unable to format /system partition after restoring.
Odin managed to fix it tho.
jscurtu said:
The question is if anyone tried to restore a cwm backup ? The most of the bricks were caused by doing that task..
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I have multiple times. CWM Backup restore works sometimes for me ICS to ICS, and fine GB to GB. ICS to GB or GB to ICS causes issues but I can easily fix them with a flash/odin/etc and still have complete access to download mode / CWM. ICS to ICS I have run in to problems such as funky root or partition issues, once again still easily fixable and still have plenty of access to the phone/flash abilities, By no means even close to a brick.
That said at this point in the game I wouldn't even consider doing a CWM restore, why even chance it!
dimcus said:
Tried CWM restore twice on ICS (missed reports that it is not recommended). Both times ended with corrupted system partition. But both times fixed this problem by flashing stock ROM with desktop Odin. Had no problems after.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Just to report, I experienced exactly the same.
Regards!
Sent from my GT-N7000 using xda premium
dimcus said:
Tried CWM restore twice on ICS (missed reports that it is not recommended). Both times ended with corrupted system partition. But both times fixed this problem by flashing stock ROM with desktop Odin. Had no problems after.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Which kernel were you on?
chill392 said:
Which kernel were you on?
Click to expand...
Click to collapse
The first leaked one - LP1.
jscurtu said:
The question is if anyone tried to restore a cwm backup ? The most of the bricks were caused by doing that task..
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I think you are wrong.Bricks caused when trying to format /system
Sent from my GT-N7000 using Tapatalk
Bricks were caused by anything that tried to wipe a partition - and restoring a nandroid will first wipe a partition.
What kernel is imilka's a repack of? Maybe it's an unaffected one. I recall seeing stuff in imilka's thread saying not to use its CWM.
Without source for the leak kernels it's impossible to tell what's changed and declare one kernel "safe" and another "dangerous" - as long as some are proven dangerous they should all be considered dangerous.
afilopou said:
I think you are wrong.Bricks caused when trying to format /system
Sent from my GT-N7000 using Tapatalk
Click to expand...
Click to collapse
When restoring a backup , you usually format /system ; )...so basically yes that is correct, I only mentioned that it mostly happened while doing that task..
Sent from my GT-N7000 using xda premium
Entropy512 said:
What kernel is imilka's a repack of? Maybe it's an unaffected one. I recall seeing stuff in imilka's thread saying not to use its CWM.
Without source for the leak kernels it's impossible to tell what's changed and declare one kernel "safe" and another "dangerous" - as long as some are proven dangerous they should all be considered dangerous.
Click to expand...
Click to collapse
It was multiple different kernels, up to LP5 and LP6 even.
I understand the logic and respect your words of caution with what is most certainly from someone who has a much better understanding than I, I just feel it is the way the kernel was used/modified/implemented that caused the potential problems (by the devs), not the kernel itself. Based on the logic I provided earlier in the thread. I am not saying the problem still does not exist in the kernel, I have no idea, but it is obviously something that did not come out in many rom implementations, just those 2.
Flashed all roms from maxicet and some repack stock ICS roms. Never got any problems. Tested over 10 ICS roms... And now using maxicet's ROM as daily.
crawlgsx said:
It was multiple different kernels, up to LP5 and LP6 even.
I understand the logic and respect your words of caution with what is most certainly from someone who has a much better understanding than I, I just feel it is the way the kernel was used/modified/implemented that caused the potential problems (by the devs), not the kernel itself. Based on the logic I provided earlier in the thread. I am not saying the problem still does not exist in the kernel, I have no idea, but it is obviously something that did not come out in many rom implementations, just those 2.
Click to expand...
Click to collapse
The thing is, this has happened over multiple devices, with multiple recovery implementations, including recovery implementations that work fine with other kernel bases. The end result is the same - fried eMMC that can't even be recovered with JTAG.
Entropy512 said:
The thing is, this has happened over multiple devices, with multiple recovery implementations, including recovery implementations that work fine with other kernel bases. The end result is the same - fried eMMC that can't even be recovered with JTAG.
Click to expand...
Click to collapse
Agreed, very bad.
All I am saying is that it ONLY happened on those 2 botched kernel implementations. It is obviously SOMETHING the Dev's did with the kernel that caused this, seeing how ALL the other roms/versions clearly have not caused this. Since the result was immediate with both of those and many of us have jumped/cwm'ed/etc from MANY different Leaked kernel builds and NOT had that problem.
I am not trying to put them at blame, running any rom/dev is strictly at your own responsibility and risk, just stating that I don't think it is fair to place every leaked rom build in the same category of danger. Is there a risk, certainly, as the dev's could accidentally make said same mistake (I am not even clear if "we" know what causes it?) in a future version. That said I feel pretty confident that if the "final" versions of iMilka's roms were going to cause that issue, it would've happened by now. That is why I wanted to see if anyone had ever been bricked (fried eMMC) from them, and it seems, no.
I'm still on my stock ROM with just root permissions and I'm getting random reboots every once in a while. Before I was rooted I had one or maybe random reboots that I remember and one of the times it just reboot while it was in my pocket. I rooted my phone two days ago and since then my phone has randomly rebooted itself about 4 times already. I had the two mods added which were the touch screen and video bitrate mod. After I seen it happen more than usual after adding those mods I reverted back to stock. I was wondering if anyone else is having these types of issues maybe perhaps a bug in the stock 4.2.1.
Sent from my Nexus 4 using xda premium
AnthonyAldrete said:
I'm still on my stock ROM with just root permissions and I'm getting random reboots every once in a while. Before I was rooted I had one or maybe random reboots that I remember and one of the times it just reboot while it was in my pocket. I rooted my phone two days ago and since then my phone has randomly rebooted itself about 4 times already. I had the two mods added which were the touch screen and video bitrate mod. After I seen it happen more than usual after adding those mods I reverted back to stock. I was wondering if anyone else is having these types of issues maybe perhaps a bug in the stock 4.2.1.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
might be a widget. a lot of people are having luck with the franko kernel. but his r16 build released earlier today started giving people random reboots. he either has it fixed already or is in the middle of doing so. the r15 build that i am on is great. but i would wait for the 16. the changelog looked pretty good.
phermey said:
might be a widget. a lot of people are having luck with the franko kernel. but his r16 build released earlier today started giving people random reboots. he either has it fixed already or is in the middle of doing so. the r15 build that i am on is great. but i would wait for the 16. the changelog looked pretty good.
Click to expand...
Click to collapse
I saw an article from android authority that said Google is aware of the random. Reboots and working on a fix soon. I just reed that after the post.
Can I flash francos kernel on my stock ROM ? Won't that cause problems. ?
Sent from my Nexus 4 using xda premium
AnthonyAldrete said:
I saw an article from android authority that said Google is aware of the random. Reboots and working on a fix soon. I just reed that after the post.
Can I flash francos kernel on my stock ROM ? Won't that cause problems. ?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
yes if rooted. lots of people are stock and running franco.
phermey said:
yes if rooted. lots of people are stock and running franco.
Click to expand...
Click to collapse
So if I want to flash francos kernel on my stock ROM just wipe delvik right ?
Sent from my Nexus 4 using xda premium
AnthonyAldrete said:
So if I want to flash francos kernel on my stock ROM just wipe delvik right ?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
franco says you dont have to wipe anything. then another guy came in right behind him and said to wipe dalvik. its on one of the last three pages in his thread. id say wipe just in case.
phermey said:
franco says you dont have to wipe anything. then another guy came in right behind him and said to wipe dalvik. its on one of the last three pages in his thread. id say wipe just in case.
Click to expand...
Click to collapse
wouldn't hurt to wipe anyway. ill stop wiping and see if i notice a difference though, so far i dont notice any. so id probably just skip out on wiping as it does seem useless because my phone still feels the same
I posted this over at rootz earlier today and didn't get any bites so I figured I'd give it a shot over here.
I may be the only one in the world experiencing this problem. Looked around quite a bit and don't see any sign of others having this issue... Anyway, my N7 doesn't seem to like it when I flash a new kernel. I've tried several different kernels and when ever I flash one my display will not wake up once it times out or if I turn the display off manually. Once the screen goes dark i have to hold the power button down and reboot. I have zero issues with custom kernels as long as they are baked into the rom. I typically wipe cache and dalvic after flashing kernels...
Sent from my Galaxy Nexus using xda app-developers app
Little bump here... 130 views and not a peep... :-/
scram99 said:
Little bump here... 130 views and not a peep... :-/
Click to expand...
Click to collapse
youre experiencing "sod", which is a fairly common problem with android 4.2.1 source code(not as common on the n7 as the gnex, but common enough). do you flash the kernel with the rom or do you flash the kernel separately?
This happens after switching out the kernel on any ROM I've used. Have not flashed a different kernel at the same time I flashed a ROM. I don't think that will make a difference. I can however flash kernels over my stock rooted backup... I don't know. Just weird and bums me out being limited like this...
scram99 said:
This happens after switching out the kernel on any ROM I've used. Have not flashed a different kernel at the same time I flashed a ROM. I don't think that will make a difference. I can however flash kernels over my stock rooted backup... I don't know. Just weird and bums me out being limited like this...
Click to expand...
Click to collapse
I would just factory reset and start from scratch. Do you have any settings set like UV??
Sent from my Nexus 7 using xda premium
I have tried flashing back to stock, relocking and starting from scratch. I do not undervolt...
A few good folks in the android community had experienced similar happenings and suggested lean kernel... Flashed it earlier this evening and working like a charm.
UPDATE: don't need anyone testing this anymore as it is not fixing most reboots
Can someone who is running custom recovery and has bad/frequent reboots install the attached file and see if it alleviates your reboots?
Please let me know what version of the OS you are running and if you are on JSS15J or JSS15Q, whether you updated via factory image or OTA.
I am 99.99% sure nothing bad will happen to your system. This will not disable your ability to get OTAs, nor change any system files, nor affect touchscreen, nor affect GPS, ...
I'm running a version of cm which has worked better than stock but still a daily reboot. What is this file going to alter / Will it work on cm?
Sent from my Nexus 7
joeshmoo said:
I'm running a version of cm which has worked better than stock but still a daily reboot. What is this file going to alter / Will it work on cm?
Click to expand...
Click to collapse
If it works, it should work ok with CM as long as you run it in TWRP.
It doesn't actually touch the ROM. It uses the kernel to reset the DDR3 memory timings and allows the system to retrain.
Thanks, I like to know what I'm flashing. Just flashed, will report back.
Sent from my Nexus 7
getting desperate and flashing this to try..
Didn't work. Just had my first reboot.
Sent from my Nexus 7 using Tapatalk 2
fkfs9 said:
Didn't work. Just had my first reboot.
Click to expand...
Click to collapse
Could you tell me what OS you are running and whether you've run an OTA before?
sfhub said:
Could you tell me what OS you are running and whether you've run an OTA before?
Click to expand...
Click to collapse
I'm on 15Q odex stock ROM. I never had an ota before.
I rooted and unlocked the boot loader and flash this ROM yesterday.
Just had a reboot on mine as well.
Running build 8 of this:
http://forum.xda-developers.com/showthread.php?t=2391779
[ROM][CM10.2][4.3][CyanogenMod FLO Kangs][DJL10.2][LINARO][Build 8][2013/08/25]
Ok, then it looks like this won't fix the random reboots.
Sorry, back to your regularly schedule program.
sfhub said:
Ok, then it looks like this won't fix the random reboots.
Sorry, back to your regularly schedule program.
Click to expand...
Click to collapse
Thanks for trying
Sent from my Nexus 7 using Tapatalk 4
joeshmoo said:
Thanks, I like to know what I'm flashing. Just flashed, will report back.
Sent from my Nexus 7
Click to expand...
Click to collapse
Don't you mean you like to know who you are flashing?
Sent from my Nexus 7 using xda app-developers app
im on clean rom with elemental x 1.2 and i have never had a reboot or anything bad happen since. i did have issues on stock 4.3 with small tweaks but since clean rom i have had no issues whatsoever
Edit also was on slim bean flo and had same issues so it's something messed up in the rom i would assume and not the software version it self
KiaraTheDragon said:
im on clean rom with elemental x 1.2 and i have never had a reboot or anything bad happen since. i did have issues on stock 4.3 with small tweaks but since clean rom i have had no issues whatsoever
Edit also was on slim bean flo and had same issues so it's something messed up in the rom i would assume and not the software version it self
Click to expand...
Click to collapse
can i flash clean rom without losing data or apps? im on modded stock rom + elementalX
I haven't had a reboot since the newest update.
Sent from my Nexus 7 using xda app-developers app
I installed Pure Nexus on my Nexus 6P the other day. I was using the phone as stock for the past couple of months. I'm an old user of CM mind you.
Since the last 2 days, Ive had nothing but problems with the ROM. I've got several apps that keep crashing,, namely Minimalistic Text, Camera and others. This never happened at all on stock. Even when I use Airdroid to scan the QR code, it uses the wrong camera.
Unfortunately, I've decided to flush Pure Nexus and just in the middle of flashing CM 13 and will try it in a few minutes.
I think I've given enough time for Pure Nexus, but I can't blame the apps that I'm using, as I've used them before on various ROMs on my old Nexus 4 without incident as well as on my Nexus 7.
I've tried to post in another forum thread but since I'm unable to as I haven't posted many times, the forum has driven me here instead.
barry123 said:
I installed Pure Nexus on my Nexus 6P the other day. I was using the phone as stock for the past couple of months. I'm an old user of CM mind you.
Since the last 2 days, Ive had nothing but problems with the ROM. I've got several apps that keep crashing,, namely Minimalistic Text, Camera and others. This never happened at all on stock. Even when I use Airdroid to scan the QR code, it uses the wrong camera.
Unfortunately, I've decided to flush Pure Nexus and just in the middle of flashing CM 13 and will try it in a few minutes.
I think I've given enough time for Pure Nexus, but I can't blame the apps that I'm using, as I've used them before on various ROMs on my old Nexus 4 without incident as well as on my Nexus 7.
I've tried to post in another forum thread but since I'm unable to as I haven't posted many times, the forum has driven me here instead.
Click to expand...
Click to collapse
Hey Barry,
After you flashed Pure Nexus ROM, did you delete the cache? I would try it again, since things can go wrong and others are on Pure Nexus without issue.
deleted cache, dalvik, wiped entire phone, yes
LeftHandedWave said:
Hey Barry,
After you flashed Pure Nexus ROM, did you delete the cache? I would try it again, since things can go wrong and others are on Pure Nexus without issue.
Click to expand...
Click to collapse
Try flashing vendor image. Pure Nex is a solid rom one of the most stable roms there is.
Sent from my Nexus 6P using Tapatalk
I've done that too in my initial flashing
flashback7 said:
Try flashing vendor image. Pure Nex is a solid rom one of the most stable roms there is.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
barry123 said:
I've done that too in my initial flashing
Click to expand...
Click to collapse
Maybe grab some logs of these apps crashing and post them on pure nexus thread.
Sent from my Nexus 6P using Tapatalk
the apps you are having issues with, did you restore those from a backup (i.e. Titanium Backup)? If so i'd clear the app data/cache and force close them. Typically that helps.
I've lost everything since I've put in a different ROM, but have contacted the developers of the apps of my problem. After mant apps crashing, I decided that it was futile to contact the developers as I realized it was due to the ROM and not the apps I was using, as I've used them before without problems
flashback7 said:
Maybe grab some logs of these apps crashing and post them on pure nexus thread.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Nope, I did a fresh install of all my apps
one7dchevy said:
the apps you are having issues with, did you restore those from a backup (i.e. Titanium Backup)? If so i'd clear the app data/cache and force close them. Typically that helps.
Click to expand...
Click to collapse
barry123 said:
I've lost everything since I've put in a different ROM, but have contacted the developers of the apps of my problem. After mant apps crashing, I decided that it was futile to contact the developers as I realized it was due to the ROM and not the apps I was using, as I've used them before without problems
Click to expand...
Click to collapse
If I were you, I would try again. Download the ROM and verify that is the correct checksum. Like I said, others here have Pure Nexus without issue.
did a hashcheck [md5] of all files as I usually do. Now I'm even having problems flashing new ROMs since in the last hour or so. I've made a backup of Pure Nexus ROM, so I know I'm able to use it, but might have to do other things here in the next couple of days to get rid of it
LeftHandedWave said:
If I were you, I would try again. Download the ROM and verify that is the correct checksum. Like I said, others here have Pure Nexus without issue.
Click to expand...
Click to collapse
barry123 said:
I've lost everything since I've put in a different ROM, but have contacted the developers of the apps of my problem. After mant apps crashing, I decided that it was futile to contact the developers as I realized it was due to the ROM and not the apps I was using, as I've used them before without problems
Click to expand...
Click to collapse
I guarantee you it was not due to the rom. If it was others would be reporting the same thing you are. Logs are the only way to diagnose a problem. Its a waste of time discussing anything workout logs..
Sent from my Nexus 6P using Tapatalk
I just reverted to Pure Nexus again from my backup as I can't seem to flash any other ROM. I did some logs on one app but I can only do it while the app is running and not when it's crashed. I'm unable to attach the file here but only put the text which is too long for an xda submission. I've gone through help to attach but it seems I have to make a new post and not reply to this thread. Weird!
flashback7 said:
I guarantee you it was not due to the rom. If it was others would be reporting the same thing you are. Logs are the only way to diagnose a problem. Its a waste of time discussing anything workout logs..
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
barry123 said:
I just reverted to Pure Nexus again from my backup as I can't seem to flash any other ROM. I did some logs on one app but I can only do it while the app is running and not when it's crashed. I'm unable to attach the file here but only put the text which is too long for an xda submission. I've gone through help to attach but it seems I have to make a new post and not reply to this thread. Weird!
Click to expand...
Click to collapse
What recovery are you using? What version? How are you flashing?? Wipe data, system, cache, delvik cache, flash rom, flash gapps, reboot??
Sent from my Nexus 6P using Tapatalk
flashback7 said:
What recovery are you using? What version? How are you flashing?? Wipe data, system, cache, delvik cache, flash rom, flash gapps, reboot??
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Using TWRP 2.8.7.2 wiped everything u mentioned above but unable to attach log files, no attachment box is available to me here
flashback7 said:
What recovery are you using? What version? How are you flashing?? Wipe data, system, cache, delvik cache, flash rom, flash gapps, reboot??
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
did everything u mentioned above. I've flashed my old Nexus 4 many times over the past couple of years
Use pastebin and include a link to your logs.
dodgerslim said:
Use pastebin and include a link to your logs.
Click to expand...
Click to collapse
<script src="//pastebin.com/embed_js/NHEvqKc9"></script>
BTW I've installed CM 13 and minimalistic text works flawlessly on it, no hiccups no crashes, weird!!
When stuff like that happens to me and I feel I've tried everything I can think of, I usually make it easier on myself to run the script in Google's factory image and start new. Flash TWRP with ADB tools, format, reboot TWRP, transfer flashables, and start with that ROM from scratch with GApps. Most variables of messing up would have been avoided and chances of success should be high. Anyone else agree with that?
PKFR4Life said:
When stuff like that happens to me and I feel I've tried everything I can think of, I usually make it easier on myself to run the script in Google's factory image and start new. Flash TWRP with ADB tools, format, reboot TWRP, transfer flashables, and start with that ROM from scratch with GApps. Most variables of messing up would have been avoided and chances of success should be high. Anyone else agree with that?
Click to expand...
Click to collapse
LOL! I've done that a few times reverting to stock and going from there. I'v had to do that in the past to get out of trouble. But seeing how I've done this countless of times over the past few years and the last phone was also a Nexus [albeit quite a change from Lollypop to Marshmallow], the rules are the same for flashing. One thing I was concerned with initially was that the vendor.img file for Pure Nexus was MMB29P but I'm on MMB29T. I don't know if that's an issue. I'm using 6.0.1 Android.
I may try it again in a few days mind you and re-flash. Will def post something if it's a positive change!!