yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] The Gingerbread Man:
Cheers will try although its easier said than done to 100% reproduce in any way. You just think your doing a normal reboot until find your self at recovery after boot screen, boot animation for normal length then recovery. Will see what I can do anyway if it can be triggered somehow. Cheers
[Samsung Galaxy Nexus] parkson:
RUU'd to stock/relock. Rooted + cwm touch 6.0.3.6, installed 4.3 bootloader and latest PA + GApps and fastboot flashed this new .img and still the same result - get kicked back into recovery after every attempt to boot. No more time to mess with this for the night, must restore backup, but will try again at the next day's end
[Samsung Galaxy Nexus] osm0sis:
When you try again, try and boot my image from power off, then just as it starts to loop back to the Google logo hold down Power + Vol Up + Vol Down to get to the bootloader, flash a working kernel with fastboot and then press Power to Start. Then give me /proc/last_kmsg so I can hopefully learn why it looped.
[Samsung Galaxy Nexus] ChazzMatt:
I know osm0sis really wants to find WHY it's doing this -- but in the meantime AFTER you send him the logs, try reflashing the bootloader to fix the rebooting issue. That way you could still continue to use this kernel, with no issues.

You would reflash the bootloader AFTER flashing the kernel, not before. See here:

http://xdaforums.com/showpost.php?p=45739197&postcount=43339
[Samsung Galaxy Nexus] stevensoaj:
Is your fsync turned off?
[Samsung Galaxy Nexus] The Gingerbread Man:
Will see what I can do, I'm not gonna stop using the kernel because of this though don't worry about that. Iv been here too long to quit lol :thumb up:

---------- Post added at 05:23 PM ---------- Previous post was at 05:09 PM ----------

Iv triggered it 3 times in 7 minutes of just sat here rebooting. I can't access boot loader loader though. Holding down the keys does nothing to stop the reboot process and it just carries on.

Sequence that this happens. Reboot from loaded up OS, Google splash, boot ani, Google splash, recovery

Twrp has a built in file manager,I have just copied prod last kmsg to my SD on my gnex, will upload it now

Here

https://db.tt/zgd3d2cZ

---------- Post added at 05:41 PM ---------- Previous post was at 05:25 PM ----------

25.671539] init: critical process 'daemonsu' exited 4 times in 4 minutes; rebooting into recovery mode

[ 26.037445] DSSCOMP: dsscomp_early_suspend

[ 26.053314] DSSCOMP: blanked screen

[ 26.053771] [MODEM_IF] xmm6260_off()

[ 26.266052] Disabling non-boot CPUs ...

[ 26.266784] CPU1: shutdown

[ 26.280456] Restarting system with command 'recovery'.

[ 26.280639]

[ 26.280731] Restarting Linux version 3.0.91-franco.Kernel-nightly (francisco@francisco) (gcc version 4.7 (GCC) ) #391 SMP PREEMPT Sun Aug 25 19:09:04 WEST 2013

[ 26.280731]

No errors detected

Boot info:

Last reset was warm software reset (PRM_RSTST=0x2)
[Samsung Galaxy Nexus] ChazzMatt:
Yeah, to reflash the bootloader (to fix the issue) you have to download the boootloader file to storage. Then re-flash it in recovery.

Now that you have sent the logs, you will re-flash the bootloader to fix the issue? ;)

or you are not able to move a file over to storage? When it happened to me, usually after 2 or 3 rebooting to recovery instances, the phone would finally boot up normally. That was the cycle... went on for days.

So, yesterday when I got a good boot, at that point I moved the new bootloader file to storage, then rebooted into recovery to flash it. Suddenly, NO MORE FAILED REBOOTS. Everything works fine.

I tried many other things, but re-flashing (re-installing) the bootloader solved the problem.
[Samsung Galaxy Nexus] The Gingerbread Man:
Nah I'll just leave it and persist. Its not like I generally reboot that often to care too much I just wanted to help and get a log to see if there's another possible fix. I'm not certain using an old bootloader is such a good idea even though no knows any changes between versions I'd feel happier keeping all up to date
[Samsung Galaxy Nexus] AutomaticFailure27:
Nope, fsync is on. I have a feeling it has something to do with PGM being turned on at boot. I tend to forget to turn off PGM and trickstermod before flashing a new kernel, which was never an issue because they detect a new kernel and turn themselves off anyways.

Lesson learned I suppose... to make a nandroid before attempting any system changes.
[Samsung Galaxy Nexus] ChazzMatt:
I only chose that boot loader because it's what osmosis uses. You can probably reflash the newest bootlaoder. They are all listed on that page, for our GNex.

_________

Sent from my Galaxy Nexus i9250
[Samsung Galaxy Nexus] osm0sis:
[MENTION=2918197]The Gingerbread Man[/MENTION] Huge thanks for grabbing the kmsg, are you using SuperSU or Superuser? What version? Please reflash the latest version and try again.

[MENTION=3250376]ChazzMatt[/MENTION] I use KK15 because it still works fine and it makes the Google logo bright white again like I remember it being when I bought my device. Anything after KK15 has a yellow tint to it. All the bootloaders work exactly the same so I have no problem deciding this one with vanity. ;)
[Samsung Galaxy Nexus] creeve4:
I remember seeing a thread with all the bootloaders, but I can't find it. Can someone please post a link?
[Samsung Galaxy Nexus] osm0sis:
Linked in my sig. :)
[Samsung Galaxy Nexus] creeve4:
Tapatalk needs an option for showing signatures...
[Samsung Galaxy Nexus] ChazzMatt:
It's also in my bootloader post.

http://xdaforums.com/showpost.php?p=45739197&postcount=43339

---------- Post added at 08:29 PM ---------- Previous post was at 08:26 PM ----------

Busybox updated, and now the rebooting issue has surfaced again. Related in any way? :confused:

Going to flash another bootloader to see if that helps.
[Samsung Galaxy Nexus] pkgnex:
What SU program are you using? I think Osm0sis may be on the right track. I was having the boot-loops, the rebooting into recovery issue, loosing root after flashing kernel zips, etc. with SuperSU versions after 1.55 (basically anything that started with 1.6*). It was a mess. I switched over to Koush's Superuser and I have not had a single problem since then. It could be a coincidence, but I doubt it.
[Samsung Galaxy Nexus] osm0sis:
And I'm using SuperSU v1.65 and it's been flawless, but clearly there's something going on.

One difference may be that I deleted install-recovery.sh and the 99SuperSU (or whatever) init.d script that the SuperSU zip installs. daemonsu is designed to bail if it's already running and something tries to run it again, that way there can only be one root daemon process.

Perhaps these multiple ways of running it to ensure compatibility on varied stock and custom ROMs doesn't jive with the way I included the native service as a critical process. Can those with the loops try and delete /system/etc/install-recovery.sh and the 99SuperSU (or whatever it's actually called) init.d script and see if my images work afterwards? That may explain the discrepancy.
[Samsung Galaxy Nexus] Edward Stanbury:
omg im glad i tried the KK15 bootloader haha the whiteness! its amazing :P
[Samsung Galaxy Nexus] The Gingerbread Man:
Supersu 1.65. After busy box updated it didn't think it could a quite root, the only app which was playing up until I made supersu forget permissions then it worked fine. Haven't tested for me loops yet will try today at some point
[Samsung Galaxy Nexus] parkson:
Apologies for reporting without being able to provide logs, as I do not have access to my own computer (on a friend's laptop), but I tried deleting the two files using root explorer and flashing the new boot.img, per your instructions, but still get the same result - I see the lockscreen for half a second before being forced back into recovery.
[Samsung Galaxy Nexus] The Gingerbread Man:
Last ksmg happened after flashing kk15 boot loader https://db.tt/zgd3d2cZ

Last kmsg1 is boot straight after with kk15 and reflashing supersu1.65 https://db.tt/hG3gP7LG

The reboot after it booted succesfully

Trying now after deleting system/etc/init.d/99supersudeamom
[Samsung Galaxy Nexus] osm0sis:
Might be some SELinux **** then.. I know Chainfire added some more SELinux permissions stuff to the SuperSU zip in the most recent versions.

Also maybe now that he's trying to let SELinux do its thing, me having daemonsu as a critical process might be problematic. If reflashing the SuperSU zip doesn't work for everyone else then I'll upload a new version without the critical flag on the native daemonsu service.

Okay, but get me a log when you can please.. your reboot might be a completely separate issue, like Contrast Adaptive Brightness or something.
[Samsung Galaxy Nexus] inihccor:
I'm losing root access every time the device reboots. Can it be kernel related?

Inviato dal mio Galaxy Nexus con Tapatalk 4
[Samsung Galaxy Nexus] The Gingerbread Man:
If your using super su then I'd suggest using the clean up and unroot options then reroot it.
[Samsung Galaxy Nexus] Deeco7:
*wrong board*
[Samsung Galaxy Nexus] nickdc986:
Same here with supersu 1.65.

I can't even access supersu, it suggests to root manually.
[Samsung Galaxy Nexus] osm0sis:
Yes. You need to reflash the supersu zip.
[Samsung Galaxy Nexus] nickdc986:
Which version of supersu, 1.65 or 1.5?

I have 1.65 right now...
[Samsung Galaxy Nexus] osm0sis:
The latest, v1.65. :good:
[Samsung Galaxy Nexus] inihccor:
I have this problem both with 1.51 and 1.65...

Inviato dal mio Galaxy Nexus con Tapatalk 4
[Samsung Galaxy Nexus] osm0sis:
If you're talking about CWM recovery reporting root lost, root isn't actually lost. SELinux changes the perms of the su binaries from rwsr-sr-x to rwxr-x-r-x, but since su is run as a daemon now that doesn't matter. f.K running the daemon as a native service should also make sure this doesn't happen.

Are you using my fixed version or what?

[MENTION=2564730]parkson[/MENTION] [MENTION=3250376]ChazzMatt[/MENTION] [MENTION=2918197]The Gingerbread Man[/MENTION] [MENTION=2753983]garuhhh[/MENTION]

So what's the verdict guys? Does reflashing SuperSU fix the recovery bootloop problem?
[Samsung Galaxy Nexus] inihccor:
No man, I'm on TWRP and root is effectively lost at every reboot (no root binaries). I'm using the zip from Chainfire's official website... should I try your version?

Inviato dal mio Galaxy Nexus con Tapatalk 4
[Samsung Galaxy Nexus] pkgnex:
People with SuperSU root issues:

You could try doing the SuperSU "full unroot" from the app, then rebooting into recovery, wiping cache/dalvik, and flashing Koush's superuser, found here:

http://download.clockworkmod.com/superuser/superuser.zip

SuperSU was causing me fits, and this worked for me with no issues.
[Samsung Galaxy Nexus] creeve4:
I second this. I've had (and apparently many others as well) nothing but problems with SuperSU with 4.3. Koush's superuser works flawlessly.
[Samsung Galaxy Nexus] ChazzMatt:
Just re-flashing SuperSU does not fix the problem. REPLACING SuperSu seems to fix the problem. :)

Same here.

I re-flashed SlimROM's latest, which comes wth Superuser, not SuperSU. In the past, I would always immediately flash SuperSu as I liked it better. This time I did not. Kept what came with SlimROM.

Actually a dirty flash, clearing only cache and dalvik, and then flashed the latest weekly Slim ROM. SlimROM GAPPS stayed the same, but kernel of course changed to LeanKernel as that's what comes with SlimROM. Kept it temporarily just to make sure there were no reboot loops.

Set everything up -- allowing superuser access for all the apps that needed it. Reflashed Nexus Louder, and even re-installed MusicFX apk in system/apps for the Nexus Louder experience. Rebooted a couple times to check. NO REBOOT LOOPS.

Made a backup.

Then flashed osm0sis fixed #391 from recovery. NO REBOOT LOOPS.

SuperSU seems to be the problem. :(

Everything is now set up as before -- now running Franco (osm0sis fixed) kernel on SlimROM, with Nexus Louder, but with superuser -- no SuperSU. No reboot loops.
[Samsung Galaxy Nexus] The Gingerbread Man:
I haven't been able to trigger the recovery being accessed today although I have only tried rebooting 4 times today. I haven't changed my set up since I posted those logs on the other day, I haven't flashed anything new (other than what I said I had changed in my posts) so I don't think the issue is fixed. How ever I can't find a way to 100% reproduce the error, it happens once as a fluke then it seems to be more likely to repeat if it has already happened for some reason if that makes sense. I'll try rebooting a few more times today.
[Samsung Galaxy Nexus] garuhhh:
Im still using the old fixed version of osmosis, but could not replicate the reboot into recovery. I've tried a couple of ways of rebooting, but could not reproduce It again.

Edit: same experience as gbreadman. It seems to happen at random ?
[Samsung Galaxy Nexus] osm0sis:
Alright, can you go ahead and break your ROMs again by flashing SuperSU to reproduce the bootloops, then try this new fixed version I just uploaded? ;)

http://d-h.st/l26

It might just be the way I was creating the daemonsu service was causing sh*t. Still, I don't know why I have zero problems on stock ROM and SuperSU v1.65...
[Samsung Galaxy Nexus] garuhhh:
I'll try your new kernel, then report whatever findings I can. By the way, I'm also on SuperSU 1.65, stock ROM.

By the way, [MENTION=1143630]osmosis[/MENTION], how do you track your fixed kernel versions? I'm having a hard time following which version I should use from the ones I've downloaded.

Can you put a release version number on the file name? Or how do you track yours?
[Samsung Galaxy Nexus] The Gingerbread Man:
Cheers will try. I'm also stock ROM supersu 1.65

---------- Post added at 05:09 PM ---------- Previous post was at 05:07 PM ----------

Just delete the old versions before moving the new version to your chosen destination. Or use a file manager to get a time stamp for creation or download time / date

Edit

Downloaded, flashed through fku, I manually rebooted to recovery and flashed supersu and cleared cache. Now testing.
[Samsung Galaxy Nexus] ChazzMatt:
osm0sis, do you have a zipped version we can flash in recovery? Since I am already running your (old) fixed #391, yes I can flash the new one using the Franco app. But when I install a new ROM, I would like to flash it from recovery as the Franco app seemingly does NOT allow you to use the "restore" function from a different kernel.

Twice now I have found if I am not already running Franco kernel, I cannot flash your fixed kernel img in the backup/restore function of Franco app.

This morning was running Lean kernel. Franco app would not let me recover backup img nor even change TCP Congestion method while running Lean kernel. Said I needed busybox installed when I already have busybox installed. I even re-installed busybox, and STILL gave me the congestion method error.

When I tried to change from Lean kernel to your fixed version, it rebooted back to Lean kernel twice with no changes. However, when running YOUR kernel, I was able to "restore" back to Lean. Just not vice versa.

Last week, I also noticed the inability to change TCP Congestion method in Franco app when running Fancy kernel. Again said I needed busy box installed, which of course is already installed.

So, today, I booted into recovery and flashed an osm0sis "fixed #391" zipped version I had. I don't know which "#391 fixed" version it is, however. Not the most recent. :)

POINT IS, unless Franco kernel is already installed, apparently not all functions of Franco app work.
[Samsung Galaxy Nexus] The Gingerbread Man:
After a further 8/9 reboots none ended up me being in recovery mode. The latest kernel 'seems' to have fixed it but I will continue to monitor and provide logs if it happens again.
[Samsung Galaxy Nexus] osm0sis:
Let me explain my M.O.: I didn't want to go to the trouble of uploading a zip until I had the fix confirmed, because that way it doesn't get too far and only the more savvy users know how to flash it.

[MENTION=2753983]garuhhh[/MENTION] [MENTION=2564730]parkson[/MENTION] [MENTION=4793042]pkgnex[/MENTION] [MENTION=3250376]ChazzMatt[/MENTION] Is it resolved for everyone?

As for the f.Ku busybox issue, that's because f.Ku must be looking for its own /sbin/bb/busybox where the other kernels have it elsewhere. I think that's a decent bug report as f.Ku should try to use any installed busybox. You should go mention it in the N4 thread where he handles these things lately.

Simple. I don't track them. There is only ever one and I delete the previous. These were only ever intended as a temporary release until Francisco could incorporate the fixes into the main build.
[Samsung Galaxy Nexus] pkgnex:
I haven't had any problems since your second version from a couple weeks ago... but I'm not using SuperSU, either so it's hard for me to tell if more recent versions did anything to help the others. I'd like to help more, but don't really have time to re-flash SuperSU and try stuff out right now. Hopefully those who are currently having issues can tell you more.
[Samsung Galaxy Nexus] garuhhh:
[MENTION=4544860]osm0sis[/MENTION], I tried all possible means to restart my device, and so far doesn't go to recovery after restart, using the most recent kernel you gave us.
[Samsung Galaxy Nexus] osm0sis:
Perfect! Thanks for testing it out. Flashable zip (which I uploaded earlier ;)) going public now for everyone else!

franco.Kernel-tuna-nightly-r391-fixed: http://d-h.st/users/osm0sis/jb4_3/tuna/

Hopefully that resolves our root problems for good. :fingers-crossed:

There were 247 downloads of the previous version when taken down.
[Samsung Galaxy Nexus] inihccor:
It works :D

Inviato dal mio Galaxy Nexus con Tapatalk 4
[Samsung Galaxy Nexus] nickdc986:
So i just have to flash this zip, without doing anything else?
[Samsung Galaxy Nexus] greyhd:
Osmosis,

What is the difference between this new r391fixed and the one you posted a few weeks ago?
[Samsung Galaxy Nexus] The Gingerbread Man:
Basicly root with supersu has been playing up for a few of us and join rebooting end up in recovery mode. Osmosis has changed something to do with how the root process is ran internally. Read back over the last couple if pages to see the cinversation. Nothing extra for performance stuff I don't think but you should update anyway as its the most up to date verion.
[Samsung Galaxy Nexus] joefso:
can franko kernel be installed on stock without rooting?
[Samsung Galaxy Nexus] kuyam:
No.
[Samsung Galaxy Nexus] The Gingerbread Man:
If you fast boot it you can, you won't be able to control any of the features though and only use stock settings (which are best). Its not hard to root, you need to just flash a zip in recovery then you will have control over your device once your boot loader is unlocked and rooted.
[Samsung Galaxy Nexus] osm0sis:
There are alternatives to rooting though if it's just for customizing your personal default settings; once you've got a kernel with init.d support (like f.K) you can use init.d, since it gets executed as root on boot but you don't need to be rooted since busybox is a system binary, and run-parts a service. You won't be able to change them once booted up, however, you'll just have to edit the init.d script on your desktop and push the file to /system/etc/init.d in custom recovery every time you want to tinker.
[Samsung Galaxy Nexus] ToMeRv32:
I'm using PA 4.3 but the built in superuser doesn't work (I accidentally deleted it's init.d script), so I installed supersu, and flashed something that I found online cause I had problem with su binaries.

It's working fine for now, but should I try different root method?

Can I fix the built in superuser?
[Samsung Galaxy Nexus] siddardha21:
Hey guys.

The download link isn't working. Can someone point me out to a solution? Or post it?

Thank you.
[Samsung Galaxy Nexus] bigknowz:
Try this

Uploaded to dropbox, try this.
[Samsung Galaxy Nexus] ToMeRv32:
What are the differences between r391 and r391 fixed?
[Samsung Galaxy Nexus] shawnaye:
The latter has something fixed that the former didn't?

Why wouldn't someone prefer used something labeled fixed compared to one that isn't.

Haha.

Just joking around, but just use the fixed one.
[Samsung Galaxy Nexus] osm0sis:
Someone reported it worked fine with superuser recently. Make sure you're using my fixed version.

Explained a page ago. Please read back before you post a question.
[Samsung Galaxy Nexus] mjemec:
I think this one fixed the issue, thanks. :good: I also think the phone feels snappy after flashing the fix. My phone has been really sluggish and frustrating to use in the past few weeks. This is all gone now and I haven't changed anything else, only applied the kernel fix. :)
[Samsung Galaxy Nexus] osm0sis:
I just noticed Francisco put the hispeed_freq to 1228MHz with the rebase in r391, where our winning governor tunables have always had it at 729MHz; can everyone try it at 729 and see if it feels better, worse or same?
[Samsung Galaxy Nexus] The Gingerbread Man:
I just cleared app data and its showing 729 for me. That's with your latest 'fixed' 391
[Samsung Galaxy Nexus] osm0sis:
Clear App data and reboot? Because it's definitely not set in init.tuna.rc where it used to be, and mine showed 1228MHz without having changed anything or set on boot (since I assumed they were still our winners).

True kernel defaults won't be shown until you reboot since any previous setting of them in the current boot is still in the sysfs.
[Samsung Galaxy Nexus] The Gingerbread Man:
Yeah you were right it was 1228, I changed it back to 729 and then took a screen shot. The rest is the stuff we decided was best I think. I know deadline still has the values from all the testing, I can't remember what we came up with for cfq and row. It might just have been a typo from Franco maybe, I think Mako hispeed freq is 1228 currently.
[Samsung Galaxy Nexus] EnricoTFYKD:
Sorry for changing subject abruptly, but lurking around the Nexus 4 thread I noticed that franco has added the "double tap to wake feature" as in the LG G2 directly in the kernel... Any chance that franco might be looking at us too? :p
[Samsung Galaxy Nexus] The Gingerbread Man:
I'm not saying it will be but if we get it I think it maybe 'a parting gift' although personally I'm still holding out for the reworked sound enhancements and kernel level speaker boost
[Samsung Galaxy Nexus] ChazzMatt:
What were the winning tunables again for CFQ? Those are still hard-coded in, right?

Are you going to release another fixed version to put this back to 729 MHz?
[Samsung Galaxy Nexus] The Gingerbread Man:
There was a page off xda where this is was all discussed, I don't have it book marked any more. I think the values should be the right ones still though as deadline is still right. As for releasing another version to change just one setting which can be easily changed and set on boot is probably unnecessary. Just go to, freq / voltage/gov control/hi speed freq and change to desired value and set on boot. For those new round here this value changes the CPU speed the CPU jumps to under a heavy load. Currently at 1228mhz (max) where as at 729mhz the CPU will still ramp up higher if really needed but will save you a little battery in the long run.
[Samsung Galaxy Nexus] bigknowz:
Tunables

Here you go

http://xdaforums.com/showthread.php?p=45100258&highlight=echo#post45100258
[Samsung Galaxy Nexus] ChazzMatt:
Hmmmm... mine high speed freq was already at 729 -- but my boost pulse duration is at 60000 instead of your 80000.
[Samsung Galaxy Nexus] osm0sis:
I'd like to know if the majority are okay with it at 729 before I release another fixed, which is why I asked. 80000 is the correct boostpulse_duration from before, though it shouldn't really matter since we don't use boostpulse.

And actually, you're right, cfq has one incorrect value: 328 fifo_expire_async should be 335 (resolving from our winning 330). All the other tunables are fine, though of course bfq is missing altogether.

The page TGM was referring to is the Franco's Dev Team Google Group: https://groups.google.com/forum/#!forum/francosdevteam :D