yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] bsmitty83:
OK here's a zImage to test .

0. DIRTY FLASH YOUR RUNNING ROM TO ENSURE THE RAMDISK IS STOCK

1. download the attachment

2. uncompress the zimage

3. change directories to the folder with the zImage

4. Reboot to bootloader and use USB

5. "fastboot flash zimage zImage"

thats it , run it as you normally would and lets see if we can narrow it down alittle

thanks in advance

:highfive:
[Samsung Galaxy Nexus] krweby:
I'll give it a shot tomorrow afternoon after dropping the little one at grandma and grandpa's.
[Samsung Galaxy Nexus] poo706:
Interesting thought. I have boot loops and I have version PRIMELC02 on my toroplus. I think that's what it says, it's really hard to read.

[poo]
[Samsung Galaxy Nexus] apollo07:
Dead Gnex

Welp I think my gnex just died. It stopped booting maybe the battery doesn't work or its the board.

When i try to boot it, it goes through the google logo but then it shuts itself down and when its on the battery with the bolt it keeps rebooting itself.

Is it really dead or there's something I can do to bring it to life again?

Thanks in advance
[Samsung Galaxy Nexus] LibertyMonger:
I have said this before but I just get ignored, I have never been able to run the "best" kernels. I always have SOD and freeze issues when running these type kernels especially with ASKP. While almost everyone else would rave over them about how amazing they were, I could never run them. I got ignored cause everyone else talked about how great they were lol. I haven't tried this latest version maybe I will. Thanks for all your work regardless! :good:
[Samsung Galaxy Nexus] crazyeats:
Can you get to boot loader?
[Samsung Galaxy Nexus] namtombout:
Could it be that data somewhere could be getting corrupted? Any way to check? Maybe something to do with fsync?

Are the regulator voltages stock?

And maybe a cm cherry picked commit in rom could be the culprit

Just some ideas
[Samsung Galaxy Nexus] DR3W5K1:
03 here have loops
[Samsung Galaxy Nexus] jhonnyx:
No kidding dude.... question:

Are you using wall charger or USB plug charger. Connect it to the wall charger and try to let it charge. Hope it's the battery only ;_;
[Samsung Galaxy Nexus] DR3W5K1:
Another random thought....

Possibly hardware revision differences?
[Samsung Galaxy Nexus] Hetalk:
[MENTION=4608636]bsmitty83[/MENTION] I'd add a strange twist to this issue. Earlier I got boot loops at every boot. I stopped using reboot option completely.

Now,no matter what I do I cannot get into a boot loop.
[Samsung Galaxy Nexus] DR3W5K1:
Changed anything from now to then?

Also FWIW IMO these reboot bootloops are really not an issue whatsoever.

If I was Smitty I'd just let them be. On the other hand I understand if he's anything like I am he shoots for excellence.

He's thrown everything including the kitchen sink at this problem and it persists.

TLDR> I vote for the forward movement of development instead of devoting some of the Dev time to this issue.
[Samsung Galaxy Nexus] Hetalk:
Nothing changed, that I didn't try when I got bootloops.

BTW, I was on paranoid then, and I'm still paranoid. :D
[Samsung Galaxy Nexus] p34rp34r:
+1. It's just too random. I had the bootloop issue as well through both filesystems, different ROMs, different kernel versions. I was resigned to turning off the device instead of rebooting, but just this morning, after more than 1 week uptime, I used reboot and it was fine. And just before this posting, I tried rebooting again (14 hours uptime) and it was still OK.

Since we're just throwing out all options, could it be a bootanimation thing? Could a large boot animation cause kernel panic or whatever that leads to a reboot? Omni FML has a tiny (~500 KB!) boot animation and I'm not sure I've seen the issue since the switch to this one.

Device: toro

ROM: Omni FML 20140705

Kernel: SmittyV 06-15

Tweak app: Synapse
[Samsung Galaxy Nexus] DR3W5K1:
You are proving our point with yet another theory.

It could be "OVER 9000" different things.
[Samsung Galaxy Nexus] apollo07:
I think it's just the battery, because it turns on, goes on bootloader, but when i try to boot it goes through the google logo but then it keeps rebooting itself.

I've already tried to return to stock with no results

Yes I can.
[Samsung Galaxy Nexus] osm0sis:
fastboot format system

fastboot format userdata

fastboot format cache

Then flash the last full factory images, directly from Google, using the bootloader and the included flash-all shell/batch script. Reflash your bootloader and everything.
[Samsung Galaxy Nexus] Punkiderma:
sorry if this is a stupid question, but I don't know what a zImage is.

I have:

1. dirty flashed my rom (slimkat)

2. flashed zImage from fastboot

3. then, I've also had to flash smittyV kernel's zip, or it won't go past the google bootlogo. Is that correct, or I should have flashed only zImage and everything should have worked correctly?

Also, I wanted to say that for me test 3 went good, no reboots.
[Samsung Galaxy Nexus] freshgiammi:
zImage is the kernel without the ramdisk.

And no, it should have booted without flashing the kernel zip. Have you done "fastboot flash zimage zImage"? (careful, it must be zimage zImage)
[Samsung Galaxy Nexus] Punkiderma:
I have copied from topic, so it was correct. Could be the fact that default slimrom's kernel doesn't support f2fs?
[Samsung Galaxy Nexus] freshgiammi:
if you flashed the ext4 version on top of a f2fs yes. if you flashed a f2fs rom on top of a f2fs no, because it keeps the rom's ramdisk.
[Samsung Galaxy Nexus] Punkiderma:
slim has ext4 version only, the unofficial version I've made has changes only inside the updater-script, not the ramdisk or similar.

So with this rom I could not try this zImage right?
[Samsung Galaxy Nexus] freshgiammi:
So you're on the EXT4 version, right? If you dirty flashed a ext4 rom on top of a ext4 rom, there should be no problem.

The zImage works on both ext4 and f2fs since the kernel is compiled for both file systems.
[Samsung Galaxy Nexus] Punkiderma:
I'm using f2fs, but the rom doesn't officially support it. So the only changes I've made to make it run on f2fs are changes inside updater-script. So, rom's defaul kernel doesn't support f2fs.

If I can't flash smittyV kernel, because it would overwrite the zImage, I would remain with rom's default kernel, that won't boot since I'm on f2fs and it doesn't support it.

Is there any way to flash this new zImage to test AND smittyV kernel togheter?
[Samsung Galaxy Nexus] freshgiammi:
Ok, i thought you used the zip conversion script by poo. You created a zip file with a compatible rom and an uncompatible ramdisk/kernel. So, you can't test the zImage.

The only way to do this is to flash a old version of SmittyV (f2fs compatible of course) which will overwrite your ramdisk, then fastboot the zImage.

Also, change the boot.img inside your rom zip with the one included in bsmitty's kernel, so you'll install the f2fs compatible kernel when you flash the rom.
[Samsung Galaxy Nexus] Punkiderma:
Yes I already do this, the only doubt I've got is that smitty says "dirty flash your rom so you're sure you have the original ramdisk before flashing this zImage", so I thought that flashing that new zImage over a smittyV ramdisk would have false the test to know if the bootloop problem was due to the ramdisk :)
[Samsung Galaxy Nexus] pvkiniyan95:
Just dropping in to say

DirtyUnicorn + DirtyV = Epic Dirtyness....running flawless on F2FS....
[Samsung Galaxy Nexus] freshgiammi:
Osm0sis told us that the ramdisk isn't the problem, however every f2fs rom (almost) have bsmitty's kernel. You could also try fancy's one to have another ramdisk but be warned that wifiAP won't work as his ramdisk doesn't copy a needed file.
[Samsung Galaxy Nexus] crazyeats:
That's a whole lot of dirty! Let me send you some help! [url]http://www.dear-lover.com/productpic/Adult/3Pc-French-Maid-Set-LC8645-3.jpg[/url] [IMG]
[Samsung Galaxy Nexus] bsmitty83:
the zimage is the same that is in test3 , I just wanted to be sure it wasent in the ramdisk so that was the purpose of fastbooting just the zimage . in theory it should have booted on any ROM , regardless of filesystem .

but yea , flash any ROM that you want , I just need someone who gets the bootyloops to flash the zimage over a stock ramdisk to see if the bootloops still happen . if you just want to use the zimage just because , flash the test3 kernel and it will be the same only with a ramdisk included

Hack the Tuna

Edit : and I don't doubt [MENTION=4544860]osm0sis[/MENTION] about the origin of the bootloops . but this is the only way to be sure . the month of April was a busy time for this kernel . the ramdisk got rebased at least once , and I made some big changes in the kernel itself , so while its helpful to know when the problem wasent there 4/19 , its harder to say which version it started on . someone would have to go back and test each release chronologically to see when it started exactly .
[Samsung Galaxy Nexus] krweby:
ok I flashed it. I'll keep you updated. [MENTION=4608636]bsmitty83[/MENTION]
[Samsung Galaxy Nexus] osm0sis:
I attempted to thread mine to track it back using reports at one point. We'll have to search back and see what I came up with. I think it was about the same, but before the rebase.

I agree, it's best to rule it out definitively, since I haven't bothered to test that personally; my logo loops are infrequent so I mostly ignore them.

---------- Post added at 06:37 PM ---------- Previous post was at 06:30 PM ----------

Here's the refresher. I think we tracked it once before that too.. Into the 3.xx builds. :(

Now we know that it happens on clean installs as well, so that rules out data corruption. It's baffling.

Edit: Back in March it was the blurry logo loop people were reporting. Possibly the same issue, ongoing since forever? :eek:
[Samsung Galaxy Nexus] bsmitty83:
[MENTION=4544860]osm0sis[/MENTION] , crazy right , Its beyond me how random it appears .

I should have completely removed the bootlogo stuff but in fact it may be a config setting that got left a =y instead of being commented out , I'll look again , its as good of a chance that it did as didn't lol

Hack the Tuna
[Samsung Galaxy Nexus] osm0sis:
First reports I can find.. March 6th:

Then my first reproduction of it was 3.12.

Yeah my best guess was always that it was something left over from one of the boot splash attempts, just because it's that early in the boot.

Ramdisk unpack is also that early, but a complete ramdisk failure is a hung boot, not a loop. It's too early to be any sort of script in the ramdisk. Not even the .rc files if I recall correctly.

---------- Post added at 07:14 PM ---------- Previous post was at 06:59 PM ----------

The blurry logo thing seemed to be related to the 4470 timings at the time, if it's not the boot splash, is there anything else along those lines still committed?
[Samsung Galaxy Nexus] angourakis:
[MENTION=4608636]bsmitty83[/MENTION] , something crazy happened today.

I was running the test2 version and my phone turned of because the battery which is already dying... that's ok. But then I tried to turn it on and it was stuck at CM logo until it turned off again.

Connected to a charger, tried again to turn on, 5 minutes and nothing...

Went to recovery, changed kernel, cleaned dalvik and cache and the phone started.

Would like to have a log but when this happens the only way is to pull out the battery (which when the phone freezes, the battery loses like 10% of it and idk why...)

Anyway, just reporting... unfortunately those stuff just happens when I am far from my computer =(
[Samsung Galaxy Nexus] DR3W5K1:
One last thought free space could the people experiencing this have more free space in /system. Correct me if I'm wrong but doesn't the kernel check the filesystem & partitions during boot?
[Samsung Galaxy Nexus] poo706:
I've found that a lot of devices behave really wonky when the battery gets run down like that. Let it charge for a good amount of time while its powered off and it should return to normal.

[poo]
[Samsung Galaxy Nexus] osm0sis:
There's a thought.. I run pretty low with Carbon. I have to move framework-res.apk out to update PA GApps right now and then run PA GApps Remover to make room so I can move it back (..I can't wait for the full shell script PA GApps to be complete. It's going to be epic! :D).

Don't think it has to do with checking though, only data and cache are checked (see the fstab :good:).
[Samsung Galaxy Nexus] DR3W5K1:
Man I can tell I've been up for 24 hours... Meant to say less free space

Well..... Cache being to full then?

Seems that would explain a clean flash as a temporary fix as well.
[Samsung Galaxy Nexus] osm0sis:
Yeah I knew what you meant. :p

/cache is generally pretty empty in my experience. :)

Someone with bad logo loops should try to free some space up on system (delete some GApps maybe?) and see if it helps.
[Samsung Galaxy Nexus] crazyeats:
I got bootloops while running liquid without any gapps installed. Not even play services. Just rk's build converted with poo's tool. And dirtyrsr.
[Samsung Galaxy Nexus] DR3W5K1:
[MENTION=4544860]osm0sis[/MENTION]

What about the possibility of corruption or incorrect permissions in /data/media. I noticed after converting to f2fs and had pushed the contents of my sdcard back then flashed your permissions fix my GL:BL issue disappeared
[Samsung Galaxy Nexus] Firewalker1980:
osm0sis, I can only talk from my own experience, but I think it might just be a flaw in my phone (like for instance some OnePlus One phones have yellow banding, others not). I have been having it since the day I bought the phone. The reason I started rooting/flashing custom roms is because my phone crashed trying to do the official update when it was still on Ice Cream Sandwich. I had to manually flash the update to get it working. Since then, I've had numerous custom roms / kernels / ...

All gave me the bootlooping more than 50% of the time. So I now never shut down the phone anymore, only when I really need to.

And then, most of the times, I need several battery pulls to get either to TWRP recovery or boot the phone to the OS.

I kinda gave up trying to fix it...

My phone storage stats now:

System: 652MB - Free 63.1MB

Data: 13.5GB - Free 3.5GB

Cache: 430MB - Free 303.1MB

Running C-RoM-KK-v7.1 on ART and F2FS

SmittyV 17-07

Nephilim Kernel Settings

---------- Post added at 07:52 AM ---------- Previous post was at 07:46 AM ----------

I've tried wiping everything possible and starting from a clean SD card even - not copying back anything. Also doing the fix permissions option in TWRP, Never solved it for me. I sometimes got a little less loops/freezes, but never got rid of them entirely.

I haven't checked out this permissions fix from osm0sis though.
[Samsung Galaxy Nexus] osm0sis:
It doesn't happen on other kernels though, so there should definitely be some way to "fix" it, even if it is a susceptibility issue.
[Samsung Galaxy Nexus] krweby:
[MENTION=4608636]bsmitty83[/MENTION] I just had a bootloop with zimage.
[Samsung Galaxy Nexus] pattyboi:):
[MENTION=4544860]osm0sis[/MENTION] [MENTION=4608636]bsmitty83[/MENTION] since its so early in the device boot would the loop deal with init.rc or any other init file?
[Samsung Galaxy Nexus] bsmitty83:
I might have found the cause , I think osm0sis was right about it being a leftover from the bootlogo stuff , I'm going to build a test kernel asap and hopefully I can solve this .

but the only nagging thought I have is still why its so random . I keep thinking that if it wasent some setting doing it , it would happen every time and for everyone across the board . so we'll see I guess but if not I have my eye on a few other suspects , Ill just keep firing off test kernels until we figure it out

heres the test kernel , try it out see if you get the bootloop on reboot still

Hack the Tuna
[Samsung Galaxy Nexus] Hetalk:
My phone screen turns into a martian(heavy greenish tinit, that could not be changed even by trying out different trickster color presets) after flashing this build. Flashing the build from 17th turned it back into a earthling.
[Samsung Galaxy Nexus] Rushead:
I've rebooted @ 20 times, no GLBL. I did have a "Dirty shutdown" lol, but that was uv'ed by 100. No problems with stock voltages (except for the greenies).
[Samsung Galaxy Nexus] bsmitty83:
in your opinion would you have gotten the bootloop in the same scenario with the affected kernels ?

Hack the Tuna
[Samsung Galaxy Nexus] apollo07:
It was just the battery, thanks everyone who tried to help me.

I got this onite extended one hope it last 6 months :)
[Samsung Galaxy Nexus] krweby:
Flashing now.

---------- Post added at 02:57 PM ---------- Previous post was at 02:34 PM ----------

Colors are really off in the test kernel. Really green.
[Samsung Galaxy Nexus] gohamstergo:
Sort of OT, but just trying to spread the word for a helpful post: Anyone with MMS issues on Toro should check out this fix: http://xdaforums.com/showpost.php?p=54546195&postcount=15 worked for me! it simply flashes Slim's APN settings over your current ones. Been struggling with this FOREVER, so glad it works for me now. Give it a try.
[Samsung Galaxy Nexus] amd_h4x0r:
Slightly off topic, but I am running f2fs and using TWRP-2.7.1.1-F2FS/EXT4-TORO linked in the main post. Every time I try to wipe /system, it formats /system as ext4 and I have to flash a different recovery to format /system as f2fs and then flash back to TWRP to dirty flash a new rom. How do I get TWRP to format /system as f2fs? I know there is a check box in advanced settings to force f2fs, but it says it will wipe everything which I do not want.
[Samsung Galaxy Nexus] bsmitty83:
checking the boxes will simply force twrp to format using the mkfs-f2fs tools instead of the ext tools , if you check the boxes then format system , it will only format system .

Hack the Tuna
[Samsung Galaxy Nexus] amd_h4x0r:
ok, I just wanted to make sure it wouldn't automatically format all partitions to f2fs by selecting that option
[Samsung Galaxy Nexus] Rushead:
For so long I've been running stock that it's hard to remember. However, I used to get the GLBLs every normal reboot, and I've yet to have one with the test kernel.
[Samsung Galaxy Nexus] demlv:
My screen is green but I can reboot properly. Admittedly a very small sample size, but I think you found and fixed the GLBL problem. I won't stick with the test version (color is just too weird) but I'm definitely looking forward to the next release!
[Samsung Galaxy Nexus] krweby:
Couldn't get the colors dialed in and charging was acting squarely. Was charging when first booted then would stop and wouldn't keep setting in trickster. So I'm back on 7/17. [MENTION=4608636]bsmitty83[/MENTION]
[Samsung Galaxy Nexus] pvkiniyan95:
Yet another blow to my GNEX, just damaged the sim card slot so no more phone, now its a GNEX POD, no idea what to do now.... Thankfully still its a Beast in its own way
[Samsung Galaxy Nexus] GilGameshn1:
Tried latest F2FS version of LS for maguro with your kernel and no random reboots whatsoever ... So I think there is something between ROM and kernel both ... I mean it is very depended on Roms ... Just my experience in a Noob way ... [MENTION=4608636]bsmitty83[/MENTION] ... And thanks for your hard work bro . ?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] paganwinter:
Poo, turned out, the .net errors were the cause. The fnr was failing, and hence the update script wasn't getting changed to use run_program. Updated my .net framework, but to be on the safer side used Smitty 6/15 with Vanir 7/13 (nuclear mistake's) and it worked. Did a dirty flash over Commotio's Vanir (5/26) that I had flashed earlier.
[Samsung Galaxy Nexus] rajputrajat:
I know how you feel, brother..

Happened with me with my last phone.
[Samsung Galaxy Nexus] crazyeats:
If you a Toro device it is really easy to swap out SIM card hardware. Just have to find one. Not sure bout the other variants gnex.
[Samsung Galaxy Nexus] poo706:
My bad, I had no idea that fnr used .NET. I'll add that requirement to the OP of my tool.

[poo]
[Samsung Galaxy Nexus] bsmitty83:
So I finally reproduced the bootloop on reboot issue on my device . I left it for ~24 hrs . and rebooted and sure enough , it bootlooped . so I learned two things , 1. Its not random , 2. Its uptime related . there isn't a whole lot that I know of that is time related that would cause a bootloop only upon reboot . its something trying to do something because if you pull the battery it effectively kills whatever it was and the phone "resets" , thereby letting it boot again normally .

So I'm glad that I finally reproduced it . I'm going to continue to explore the possibilities bit this might take a while as I only know for sure it happens after 24hrs uptime .
[Samsung Galaxy Nexus] osm0sis:
[MENTION=4608636]bsmitty83[/MENTION]

I see you've got some f2fs fstab changes (inline_data) in the latest build's ramdisk that aren't on GitHub yet (also one of those pesky ~ files ;)). I wanted to run my own changes to it by you, since I'm not running f2fs, but we should try to use something slightly more "normal" for read/write, suid permissions etc. as per [MENTION=3390093]MWisBest[/MENTION]'s feelings here: https://github.com/MWisBest/android...mmit/3dfe5fcc44aeb7a267017879ed21d4064acf7b8c

/dev/block/platform/omap/omap_hsmmc.0/by-name/system /system f2fs nodev,noatime,nodiratime,flush_merge,background_gc=on,inline_xattr,active_logs=2,discard wait
/dev/block/platform/omap/omap_hsmmc.0/by-name/cache /cache f2fs nosuid,nodev,noatime,nodiratime,errors=panic,flush_merge,background_gc=on,inline_xattr,active_logs=2,discard wait,check
/dev/block/platform/omap/omap_hsmmc.0/by-name/userdata /data f2fs nosuid,nodev,noatime,nodiratime,errors=panic,flush_merge,background_gc=on,inline_xattr,active_logs=2,discard wait,nonremovable,check,encryptable=/dev/block/platform/omap/omap_hsmmc.0/by-name/metadata

I just took what's on GitHub and brought it into line with the ext4. Feel free to add inline_data back or whatever. :)
[Samsung Galaxy Nexus] bsmitty83:
Agreed , yea I thought I commited those changes but I don't think all the flags are necessary.

I'm really perplexed by this bootloop . I'm really not sure what would cause it after a certain time period .

I did notice that my phone was running super sluggish , and I checked dmesg and there were all kinds of stacks from voltages not being set , so I looked and all my mpu volts were showing set 0 . so I restored a profile and it fixed it . the two are not related , but interesting none the less .
[Samsung Galaxy Nexus] osm0sis:
Mind committing your changes? I've got Unified v2 ready to roll out but I don't want to make you have to do any funky same-branch merging because things are out of sync on your end. :)

I'll add the extra fstab changes after I push that. :good:
[Samsung Galaxy Nexus] bsmitty83:
Go ahead and do your thing , it won't mess anything up .
[Samsung Galaxy Nexus] osm0sis:
Unified v2 Ramdisk

[MENTION=2838735]aosp[/MENTION] [MENTION=4015637]rkpeterson[/MENTION] [MENTION=3390093]MWisBest[/MENTION] [MENTION=4615478]boype[/MENTION]

Unified v2 f2fs/ext4 support allows you to mix-and-match your partition formats however you want!

DirtyV-SR-7.17.14-Unified2:

http://v.ht/osmod -- http://d-h.st/users/osm0sis/osmod

Examples

:

data+cache+system f2fs;

data+cache f2fs, system ext4;

data f2fs, cache+system ext4. :cool:

GitHub commits: https://github.com/bsmitty83/DirtyV_tuna/commit/c1b776dfc3d0f360e432db67e5782c7cd2ad5796, https://github.com/bsmitty83/DirtyV_tuna/commit/4beb0b0b18471ce815709058d5643aa15cb07a00 (AnyKernel2)

Info post updated: http://xdaforums.com/showpost.php?p=53191173&postcount=9923

If you don't want to flash the .img through a tweaking app like Synapse/Trickster or a flashing app like Flashify, and can't fastboot it, then use my recovery flashable Flashify Script zip!