yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] osm0sis:
That's really weird.. Even hung at the Google logo I've been able to connect with it set up like that. I'll see if I can reproduce/fix it.

Edit: [MENTION=4834554]Oehr[/MENTION], I'd settle for that same file once it's booted with ext4 encryption, should still be useful for seeing how blkid sees an encrypted partition before it's been decrypted and mounted. :)

Also, I managed to make it think my device was encrypted by intentionally breaking the f2fs fstab entry swapping, and after waiting a minute or so at the password prompt I have adb access; shell and everything! So it should definitely work on the one I posted. Maybe double check your Device Manager?
[Samsung Galaxy Nexus] Oehr:
okay, so i tested it again:

ADB is actually available until the password prompt shows up. once its there, only the MTP device is available. No matter how often i try to plug it in.

Encrypting the phone takes forever. any chance we can write the log to a more permanent mounting point such as /system? So that I can grab that log via TWRPs adb access.
[Samsung Galaxy Nexus] osm0sis:
It's before /system is mounted so not really. rootfs is all there is at that point. :eek:

No way to catch the adb pull before the password prompt?

Edit: I've got an idea.. I can add another hook after the mount_all and copy the previously saved debug file from root to cache. Headed to physio now so I'll try to do that up real quick when I'm back, before I inevitably take a nap. ;)
[Samsung Galaxy Nexus] Oehr:
doubt i can do that in time. its pretty fast and i somewhat doubt the necessary information is actually there when i try pulling it. since you had a better solution, lets try that first. ill be waiting eagerly :D
[Samsung Galaxy Nexus] osm0sis:
Perfect! Here you are, sir!

The file should be in /cache/fsdebug.txt once you return to recovery after the failed boot. :)

[ Attachment removed. Mission accomplished! ]
[Samsung Galaxy Nexus] danielstar13:
Your suggestion fixed it! I am now using Dirty-V! thank you so much!!
[Samsung Galaxy Nexus] Oehr:
/dev/block/platform/omap/omap_hsmmc.0/by-name/system ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/system /system ext4 nodev,noatime,nodiratime,barrier=0,data=writeback,noauto_da_alloc,discard wait
/dev/block/platform/omap/omap_hsmmc.0/by-name/cache ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/cache /cache ext4 nosuid,nodev,noatime,nodiratime,errors=panic,barrier=0,nomblk_io_submit,data=writeback,noauto_da_alloc wait,check
/dev/block/platform/omap/omap_hsmmc.0/by-name/userdata
/dev/block/mmcblk0p11: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p10: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p3: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
[Samsung Galaxy Nexus] osm0sis:
Interesting! It just doesn't see the partition

at

all

if it's encrypted. Probably the same whether it's f2fs or ext4.

Unfortunately this doesn't give me anything to work with to make Unified v2 do anything differently. :(

Edit: At least not intelligently. I could make it assume based on cache, but that's a step backwards in terms of freedom to format in whatever combo you want.. I'll think about it though.. in practice it might not really be a noticeable change outside of encryption users because of the swapping, and basically the guideline would be: if you're running data encrypted you also have to format cache to the same format.

[MENTION=4834554]Oehr[/MENTION], speaking for the security junkies, would that be a fair compromise? It's a workaround but it's the best I can come up with unless someone knows some clever way to detect an encrypted partition and then also the filesystem of that encrypted partition before it gets decrypted. :)

[MENTION=4608636]bsmitty83[/MENTION] [MENTION=4615478]boype[/MENTION] [MENTION=2838735]aosp[/MENTION] [MENTION=4443334]Grarak[/MENTION] [MENTION=3685904]ak[/MENTION] [MENTION=5310723]Amperific[/MENTION] [MENTION=5380162]pattyboi:)[/MENTION] [MENTION=2633638]Ziyan[/MENTION] [MENTION=2765426]styr[/MENTION] [MENTION=2633294]DHO[/MENTION] [MENTION=3390093]MWisBest[/MENTION] If you have any ideas I'd definitely appreciate them fellas! :cowboy:
[Samsung Galaxy Nexus] pattyboi:):
what if you (or anyone) set up a aroma based installer for dirtyv.that has a "encryption" installation and "multi-filesystem" installation?

that way.those needing encryption install the cache based version of anykernel 2 like you were talking about above :)
[Samsung Galaxy Nexus] osm0sis:
Hmm.. Interesting idea! I think I follow you, and it'd work but everything else for Unified v2 happens automatically on-the-fly during boot so someone can just go to recovery and format however they want, so that'd be a big step back in it being automatic.

Keep 'em coming though! Lots of good knowledge, so I'm hoping there's a way to keep it seamless and without the script having to make assumptions. :good: :)
[Samsung Galaxy Nexus] Oehr:
knowing the FS hidden in the encrypted container should not be a security risk, assuming the implementation of encryption isnt flawed in a way, that lets us exploit said knowledge. and if it is, were already at the point of needing a new implementation altogether... that said: assuming cache and data to use the same FS is acceptable in my eyes. however guys like zimmerman will probably see it differently...

which brings me to my next topic (F2FS unrelated though):

cache should also be encrypted, as it gives a lot of information of the installed apps and other data... it provides much more - too much - information of the data that might be found on the data partition and also of the owner of said phone! *puts tinfoil hat on*
[Samsung Galaxy Nexus] osm0sis:
Haha all those recovery logs! :p

Fair point though!

Before we had the option to choose a different fs format it was still easy to just unpack the kernel ramdisk, look at the fstab and see all of them listed there, so hopefully even the die-hard people could find that acceptable. Thanks for the input and all the time and patience! You're an excellent, knowledgeable tester so it's been a pleasure! :)
[Samsung Galaxy Nexus] osm0sis:
I'll post this, at least until we see if our think-tank above can come up with anything that might work instead! Also I wanted to make sure [MENTION=4834554]Oehr[/MENTION] could have a booting device since he's put it out of commission for 2 days now testing for us. Huge thanks! :)

Here's the test version with my implemented idea for providing a workaround for f2fs encryption to function with Unified. I'm running it myself (unencrypted) and it seems as fast to boot as before, despite the extra partition fstype check on cache, which is good. You can still have whatever combination of partition fstypes you want if you're unencrypted. If you're running encrypted this will boot for you provided you have your cache partition formated to the same fs format (ext4/f2fs) as your data partition. The previous versions would only boot encrypted ext4. :good:

DirtyV-SR-8.15.14-2-Unified2:

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

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!
[Samsung Galaxy Nexus] DHO:
Nothing wrong with guidelines for how to format

have you tried?

sudo blkid | grep cache
[Samsung Galaxy Nexus] osm0sis:
Definitely leaning toward the guideline, especially for now since it (should) get all encryption working again with that one stipulation. Waiting for confirmation that it works before committing to GitHub though. :)

As for blkid, I've turned it into a function actually:

getfs() { $bb blkid $1 | $bb cut -d\" -f4; }

https://github.com/bsmitty83/DirtyV_tuna/blob/ramdisk/ramdisk-DirtyV/fscheck

Problem still remains that blkid doesn't return anything for encrypted partitions (as though they're not there), so I'm hoping there might be some other utility or method that could determine it, but I'm liking the workaround more hearing that you guys agree. :good:
[Samsung Galaxy Nexus] bsmitty83:
This should be good because if I was to run f2fs data , I'd do cache as well . so it shouldn't be a problem

PS osm0sis , I moved the any kernel /ram disk, and hostapd binary to its own branch . I kept the history intact as well . [emoji6] so you might have to git clone -b ramdisk
[Samsung Galaxy Nexus] osm0sis:
I saw! Nice and clean. :)

git pull to update and git checkout ramdisk had me covered. :good:

I just sent you a PM about bringing the zipfiles over too (might as well), so hopefully that's not too hard.

Feel free to can that hostapd binary too, since it's already in both the ramdisk and AnyKernel2 dirs.

I'm really happy with Unified v2 ext4/f2fs support now actually. It's solid. :highfive:
[Samsung Galaxy Nexus] Oehr:
works :)

now all thats left is a compatible TWRP revision.

for now, Ill recover my phone properly. I wonder how many SMS i missed lol
[Samsung Galaxy Nexus] osm0sis:
Woot! Thanks again buddy!

FML-TWRP is as close to official TWRP support we have at the moment, and like I said, I think MWisBest got encryption working correctly on it. The MultiROM-based ones in the OP here are good too, but I've seen a few people report issues with them; not sure how widespread it is though. I'm happy with FML-TWRP since I use [MENTION=2719389]z31s1g[/MENTION]'s badass Holofied themes and it all works perfectly. :)
[Samsung Galaxy Nexus] Oehr:
well, fmls TWRP suffers the same issue as android itself did, till you fixed it by assuming same filesystems, so it is broken. Ill report it in his thread tomorrow, so that he can fix it as well. dont have the will or power now: 5am >_>

P.S. multirom one and the specific device ones linked in this thread dont work with any encryption at all, so they are even worse.

P.P.S. never used themes with twrp before. badass you say?
[Samsung Galaxy Nexus] osm0sis:
Most assuredly badass. Follow the link in my sig to get to his thread. You can add AROMA Filemanager as an add-on, and the latest versions actually integrate my Flashify script so you can choose to select whether you want to flash zips or an img file and do so directly from the TWRP file selector. It's genius what he's done with a theme. Life changing even, if you flash a lot of imgs like I do. :p

Can't recommend it enough. He's said he's working on "Materialized" themes in the future to go with Android L too. :cool:

(I went ahead and took the Play Curtain he's using on the N7 '13 now, which is much nicer, resized it and put it in FML-TWRP. If anyone's interested, I've put it up at http://v.ht/osmod.)
[Samsung Galaxy Nexus] DR3W5K1:
Found this in the toro shiny thread.
[Samsung Galaxy Nexus] pattyboi:):
hmmmmmmmmm,who knew even nexus bootloaders cause problems -_-
[Samsung Galaxy Nexus] DR3W5K1:
He probably flashed this kernel.

Maybe we should have a disclaimer.... I'm sure people would read it ;)
[Samsung Galaxy Nexus] pattyboi:):
lol,xda sometimes makes me wonder if half of earth is illiterate to warnings and disclaimers xD
[Samsung Galaxy Nexus] osm0sis:
Are people still having the logo loops? I haven't seen one since Smitty's last attempt at fixing it, and I've rebooted A LOT. :good: :)
[Samsung Galaxy Nexus] DR3W5K1:
That guy is getting them on shiny and only mentions changing bootloaders.

Probably a whole different issue.
[Samsung Galaxy Nexus] Rushead:
I'm on Shiny with l8st Smitty. I've rebooted @ 8 times with not one GLBL. I had one every reboot before. [emoji12]
[Samsung Galaxy Nexus] aosp:
[MENTION=4544860]osm0sis[/MENTION]

Can you please msg me on hangouts so we can fix the AnyKernel2 you got on Smitty's git for Omni and have you checked out the below binary?

https://github.com/ModdingMyMind/boot_manipulation

kernelassimilator: boot.img HOT-FIXer for 3rd party kernels · 4a33853 · VanirAOSP/vendor_vanir · GitHub - http://goo.gl/kko89z
[Samsung Galaxy Nexus] Punkiderma:
Today I was trying to do a backup, but backing up data faile constantly. So I looked in the recovery log, and I noticed that an app's folder was blocking the entire process, error 255. (data is on f2fs for me)

I tried to delete it, but I couldn't. I tried to repair file system from recovery, but it failed.

So, I had to copy my sdcard (thanks again [MENTION=4544860]osm0sis[/MENTION] for your script!), then format /data with ext4 and finally again with f2fs i order to have a "success" trying to repair the file system.

What could have been? Is that a bad sign of a damaged internal memory?
[Samsung Galaxy Nexus] krweby:
Yes
[Samsung Galaxy Nexus] osm0sis:
Yeah I helped Modding.MyMind with that tool a bit, not really useful for us though. And you showed me Vanir's "reverse-AnyKernel2" before. Very cool. :)

Hold on re: Hangouts. I don't use G+ so I'll just see if I can add you on my phone here since I use it for text.

Edit: Looks like I can, but you don't have a G+ shortname, so it can't find you.

Rogue root app? Did you identify which one? Uninstalling the app while booted didn't work? Very weird.

Maybe formatting data is what made the difference for me? Punki's post has me thinking perhaps there was a bad sector somewhere..
[Samsung Galaxy Nexus] Punkiderma:
Was an xposed module regarding NFC. Couldn't uninstall or reinstall the app, neither delete the folder (even from TWRP's file manager!)
[Samsung Galaxy Nexus] osm0sis:
So bizarre. Rogue root app it is. Must have made itself/its files immutable somehow.
[Samsung Galaxy Nexus] Punkiderma:
but I had this module installed for a very long time, never had a problem

Could another app have caused this, even if this was not his folder?
[Samsung Galaxy Nexus] osm0sis:
Oh possibly. Root apps have total control. It doesn't seem likely though, since why would it mess with just that one specific app?
[Samsung Galaxy Nexus] nixholas:
Another way is to allow the kernel to detect the encryption status so as to make necessary changes automatically.

This is a permanent workaround. :)
[Samsung Galaxy Nexus] Punkiderma:
so just a corrupted block? but how?
[Samsung Galaxy Nexus] osm0sis:
Nah, that was my possible explanation for why formatting userdata to f2fs might have fixed the logo loops for me, since that's around when I stopped seeing them. ;)

For you, I think that xposed mod somehow made some or all of its app files immutable so that they couldn't be wiped with app data/cache. One legit reason they might have done that is because those files missing could break NFC or fry the secure element or something. That's me giving the benefit of the doubt, anyway; I'd ask the mod dev.
[Samsung Galaxy Nexus] DHO:
Yea,.. in that case you would need to package something like cryptsetup and add it to busybox.
[Samsung Galaxy Nexus] Rushead:
Holy Crap! I have never seen anything like this on the GNex before. 2100mah battery. Latest Shiny Dirty Smitty.
[Samsung Galaxy Nexus] osm0sis:
Yesterday I thought my battery or USB jack was finally f*cked after 2.5 years of abuse, because it started charging really slowly and the percentage would still drop if the screen was on. Was dreading replacing parts. Luckily it was just my old charger, huge relief; stupid goddamn cat had chewed most of the way through the cord. :rolleyes: ;)

Still got my eye on Shamu though. If it's 5.2" like that benchmark site showed then that puts it in between the S5 (5.1) and the Note 1 (5.3), but with the way Google likes their phone bezels small and the lack of need for physical key space I'm thinking it'll still be the size of the S5. And with the other reported specs? Hell yeah. :cool: :D
[Samsung Galaxy Nexus] krweby:
I'm a dork I thought the newest kernel was still 8/12. I just flashed 8/15. I'll give it some time and see. :eek:
[Samsung Galaxy Nexus] ToS_phoenix:
I know the feeling..sometimes my GN won't start charging or reboots a few times in a row. My USB jack doesn't allow data transmission anymore..but otherwise i'm totally fine with LS and dirtyV ^^

But i'm also opting for a Shamu, mostly because i like the build quality of Motorola devices (my old milestone still lives :D). Or maybe a N5 when it gets a discout like the N4 ;)
[Samsung Galaxy Nexus] Oehr:
gotta charge fast!

[IMG="charge me!"]http://storage.superconnected.org/img/chargeme.jpg[/IMG]
[Samsung Galaxy Nexus] Jar3112:
I'm sorry to ask this again and hope not to bother, but when will the f2f2 recovery be updated to support USB otg? I really miss that feature since I have very little space left on sdcard..

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] bsmitty83:
Whenever I can fix it . if you have any ideas why otg doesn't work I'm all ears lol . I don't have a otg cable . I'm a married father of 2 and work 40+ hrs a week . I do what I can when I can . have you tried mwisbests' recovery ? I never changed anything from mainline twrp except the f2fs stuff. I guess till then if you really need otg that bad there's always regular recoveries ........
[Samsung Galaxy Nexus] Jar3112:
Thank you, I thought it could be fixed. I guess that if I make a backup with regular recovery it could be restored afterwards even if filesystem is f2fs am I right?

Sent from my Galaxy Nexus

---------- Post added at 03:38 PM ---------- Previous post was at 03:37 PM ----------

BTW it only says "unable to mount USB otg", I'll try and check with adb to get done other info

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] bsmitty83:
It should as long as the kernel in your backup is f2fs , I know its been tried before , not sure what the outcome was .

I'll try to get some updated stuff out . just haven't had much time to do anything myself lately .
[Samsung Galaxy Nexus] krweby:
Well it still does it. I formatted everything when you first talked about this a while back. So I don't think that is the issue.
[Samsung Galaxy Nexus] Reinvented:
A quiet thread is a happy thread.
[Samsung Galaxy Nexus] peterlemonjello:
I've switched back to DirtyV-R-5.3.14. The latest kernel stuttered and I couldn't tolerate the boot loop problem any more. IMHO, 5.3.14 has been the smoothest and most stable for my gnex
[Samsung Galaxy Nexus] bsmitty83:
If anyone is bored and wants to do me a favor , if anyone who runs older versions can comment if they do not suffer a bootloop on reboot , it would help narrow down when it was introduced , due to the comment above me I'm going to assume that it started after 5/3 .

No rush , just if you happen to flash a version older than the current and it doesn't bootloop on reboot , let me know .

I'll put out a new version soon , hoping to have some spare time in the next few days
[Samsung Galaxy Nexus] Culex316:
That happened to me too. But I used a knife to carefully pull up that piece of metal so that it would charge again.

The good thing about the Gnex is that the USB module is separate from the main motherboard and can be easily replaced for $9.99.

http://www.dealsishop.com/samsung-g...uoWrom5tRPJWyv2Ed0i6RUcnBigL2inr8LxoCXZXw_wcB
[Samsung Galaxy Nexus] Firewalker1980:
I've had it happen from the first day I got it, so I can't say your kernel's to blame for it. It could be multiple issues all tied together.

Different behaviors I encounter:

- loops indefinitely approx every 10 sec's and I can interrupt it to go to boot loader using the key combo.

- hangs on Google boot logo and does not loop, battery pull needed

- shows boot logo and afterwards black screen or green washed out screen and freezes, battery pull needed

- reboot to recovery only works less than 50% of the time but reboot to boot loader always works. (luckily :p )

Booting from powered off state is also not a success the first time. Almost always need at least 3-4 tries.

But hey, once it's running, it's stable and fast though :cool: (running Omnirom FML now with your SmittyV).

What I find strange is that there's no pattern at all among these behaviors. It's randomly one or the other and I always get it to boot eventually without changing anything (like wiping caches).

I tested this just now: First indefinite loop so I let it reboot to boot loader using combo, then it just hung on the Google logo, no looping. Pulled battery, hung on Google logo again. Pulled battery again and booted to bootloader. Let it sit on that screen for a while and chose start, it then booted into Android.

Beats me! :confused:
[Samsung Galaxy Nexus] GilGameshn1:
Hi bro ... I didn't experience it even one time after 8-15 ... Whatever bit was gone or not happened for now ... I changed many ROMs since . so I think it is gone finally . Thanks .

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] peterlemonjello:
The bootloop issue started for me with the 7/17 build. It's been in every version since and occurs on every reboot. Hope this helps.
[Samsung Galaxy Nexus] bsmitty83:
Yes very much thank you
[Samsung Galaxy Nexus] Rushead:
I've been on 8-15 since @ 8-16. No bootloops whatsoever. I used to get one on each reboot (manual, not random). Hold buttons, reboot into recovery, reboot system solved it each time. Haven't had one since 8-15 on Shiny, but will migrate back to FML when I get some "free" time.
[Samsung Galaxy Nexus] peterlemonjello:
Also I'm running OminMetal on a VZW Gnex
[Samsung Galaxy Nexus] osm0sis:
I'm in this camp myself. No loops anymore. Finally!

So 5.3.14, 7.17.14, and I know we've got at least another couple guys who are adamant it started after 4.19.14.

Personally I'd say stick with whatever's in 8.15, it seems to fix it for the majority, and like Fire said, there may also be a hardware issue for some.
[Samsung Galaxy Nexus] Punkiderma:
Same here, no more since 8 15
[Samsung Galaxy Nexus] bsmitty83:
Amazing . well at least for the most part that is fixed . I was starting to think it would be around forever . but as there are still people who experience it I'm going to look around some more and see what I can find
[Samsung Galaxy Nexus] osm0sis:
Right now Smitty and aosp are hard at work hunting down the commit making Omni not boot with test zImages from after 8.15.14. :good:

In the meantime, I've got a couple more goodies I've been working on. ;)

DirtyV-SR-8.15.14-3-Unified2 and MultiV-8.15.14-AnyKernel2:

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

The SR ramdisk build has all the updated workarounds and script fixes I added in while getting AnyKernel2 to work, plus some Synapse updates, working f2fs encryption and all the other fixes from my previous Unified2 builds (which will be included in the next nightly).

https://github.com/bsmitty83/DirtyV_tuna/commits/ramdisk

MultiV is our brand new AnyKernel2 zip. Should work on Android 4.2+, which I tested out myself on Stock and CM (for older Android, ext4 should work everywhere, but f2fs will work more likely on CM-based). It contains all three 8.15.14 zImages and depending on what you name the zip it'll AnyKernel2 flash the variant you choose. All you have to do is change the zip name prefix from MultiV- to DirtyV-, DirtyV-SR-, or SmittyV-.

To be certain tweaks are being applied correctly, AnyKernel2 zips should be flashed over generic ROM kernel ramdisks

only

, not over another custom kernel, and not dirty flashed over itself. Flash your ROM zip or its included boot.img

first

.

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!
[Samsung Galaxy Nexus] aosp:
if you using Omni and would like to help test new Dirty builds let me know
[Samsung Galaxy Nexus] windfrenzy:
FWIW, I still got the loop this morning on 8/15 DirtyV - SR with Omnimetal on Toro. I turned off Tasker, rebooted, and no loop. Turned Tasker back on, still no loop. I will let it run for 24 hours, reboot and see what happens.

P. S. I loaded 4/19 and found it to be bootloop free as reported by others here.
[Samsung Galaxy Nexus] Jar3112:
I, too, still face the reboot loops. 8/15.

I take the chance to ask a question:

Why was uksm removed? Could it be re-added or were there issues about it?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] bsmitty83:
Uksm has been depreciated in mainline Linux . even though this is a 3.0 kernel . a lot has been backported from 3.4+ . at some point uksm broke for me and I never fixed it . I just tried to catch up regular ksm .