yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 4 Android Development (Snapdragon)] mahendrabiradar:
Anyone who has installed this rom, please provide some screenshots.
[Galaxy Note 4 Android Development (Snapdragon)] Wesleyvanneck1234:
how do you have not stock if flash the rom i have stock with all de apps
[Galaxy Note 4 Android Development (Snapdragon)] Hedi.Karray:
can anyone post some Screenshots ?
[Galaxy Note 4 Android Development (Snapdragon)] Tombias:
[emoji12]
[Galaxy Note 4 Android Development (Snapdragon)] Hedi.Karray:
lol :D wouldn't be more helpful if you just wasted your time showing me the rom instead ? xD
[Galaxy Note 4 Android Development (Snapdragon)] LazPL:
Wifi switch isn't sticky

Hey [MENTION=7546739]psycho_13[/MENTION], this is a great ROM in all respects! Thank you!

Not sure if this is my issue only but the wifi switch doesn't "stick" - I slide it to on, it goes back to off etc. Only after turning wifi on repeatedly maybe 6-7 times will it finally stick.

Any ideas?
[Galaxy Note 4 Android Development (Snapdragon)] LazPL:
Hello? Is it just me who has this issue?
[Galaxy Note 4 Android Development (Snapdragon)] Marteni:
Mate, that's gold. Wish I could upvote you :good:
[Galaxy Note 4 Android Development (Snapdragon)] CompuTechnoPro™:
Link offline !
[Galaxy Note 4 Android Development (Snapdragon)] FireEye:
can anyone give a new limk?
[Galaxy Note 4 Android Development (Snapdragon)] fohrums:
Immediately i'm attracted to your style and I say that to point out what's lacking in the Samsung Note 4 realm of Roms. But, there are a couple things that needs to be taken into consideration before I decide to use this Rom.

* Layout

+

Installation-instructions

- this should always be left-aligned. It's hard to read the way it is now which is formatted center

+

Mods

- should be under a seperate title labeled "Extras" because that's what it literally is

- sell us out on why we should use these mods

* Info-Missing

+

Download-links

- all dl links are now offline and no word on whether or not they're being worked on getting them available once again

+

HowTo-install

- because you've added 3-dl links you didn't provide info on what to do for bootloader & modem

- what is bootloader & modem? see what I mean?

+

Environment

- what's the launcher used and basically what's under-the-hood? because if this is for the Samsung Note 4 I want to be able to escape TouchWiz

- if this is using Samsung's stock TW then that's very unfortunate

+

Images

- great roms have these ;)

+

Bugs

- very much like Images, it's a standard to have a bugs label so we know what problems need to be focused on to begin being able to fix them :D

- while keeping in mind to cross out fixed bugs as-per the respective version of the bugg'd rom appropriately

As far as the instructions go I'm surprised you got so detailed in how to "look for the rom you've placed on your phone" but left out info on what is a modem and bootloader. Shocking! Also, please remove the salt you salty people. I've noticed a couple asking for screenshots (or images) and this thread provided none how pathetic :eek:
[Galaxy Note 4 Android Development (Snapdragon)] fohrums:
Does this work for the SM-N910G variant? I ask because there's no info regarding so :confused:

My phone:

samsung_galaxy_note_4_trltedt_N910GDTU1DPE3_india

I used the following

system-of-identification

:

"manufacturer_series_model_modelno_codename_baseband_location"

P.S. The first characters-appended on baseband usually means your phone's variant. So in my case it's the N910G variant. FACTS. Oh yeah, if more people used the standard system-of-identification could we solve more problems wayy quicker than this slow way of just simply stating basic phone info. You can't say phone without the proper identification. :good:

To me the greatest site to ever see good phone identification is from here (scroll down to the neatly columned list):

chainfire's autoroot (website)
[Galaxy Note 4 Android Development (Snapdragon)] pendor24:
Hello

There is no more than one active link

Is this normal?
[Galaxy Note 4 Android Development (Snapdragon)] fohrums:
Good observation. I've also pointed this out before your post. It's looking like the moderators responsible for this thread aren't showing this rom any love :( That's really bad, because I do love the way it's presented. Do wish to hear from them soon :rolleyes:
[Galaxy Note 4 Android Development (Snapdragon)] pendor24:
I do not understand English and read very rarely the double positions (which are too often useless)
[Galaxy Note 4 Android Development (Snapdragon)] soulbreeder83:
Where i can download it? No files on this mega-link!! :)
[Galaxy Note 4 Android Development (Snapdragon)] happy2472:
So what no ROM?
[Zenfone 5 Q&A, Help & Troubleshooting] Naim Islam:
Dear Zenfone 5 Developers..

I recently Flashed My Zen5 to Lollipop via ADB From CM13.1

Now Its Running Latest Lollipop 87 Rom and Also Unroot

After flashing Stock 87 Rom I m Facing Some Unexpected Issues...

There Are,

1. process android.process.media isn't Responding.(When I Reboot)

2. SystemUi Isn't Responding (Too Much)

3. Google Play Service Isn't Responding. (Too Much)

4. Lagging My Ui (Some apps Stopped Working)

So What Should I do For This?
[Zenfone 5 Q&A, Help & Troubleshooting] Boomshiva:
I hope you did a clean install , if not then you know your problem .
[Zenfone 5 Q&A, Help & Troubleshooting] Naim Islam:
I have Done Clean Flash My Stock ROM

But "Goole Play service Stopped Working" Pop Up Arrived
[Zenfone 5 Q&A, Help & Troubleshooting] Boomshiva:
This is weird all these happens generally when you dirty flash or restore data , try updating gapps and other stuff .
[Zenfone 5 Q&A, Help & Troubleshooting] shanmukh2778:
Find it in apps ..

Then clear cache data..

May it works sometimes..
[Zenfone 5 Q&A, Help & Troubleshooting] Naim Islam:
I Flashed Fresh Stock ROM. not Dirty.........

Gapps are Updated.....
[Zenfone 5 Q&A, Help & Troubleshooting] fsl24862:
Dirty flash means flashing rom without any wipe or fomate, for flashing new rom it is advised to wipe system, cache,darvik cache and interal storage( atleast delete old app files) to avoid force close and other errors
[Zenfone 5 Q&A, Help & Troubleshooting] Naim Islam:
I know That

Before Flash, I Wiped Data n Cache

After Flash, I Also Wiped Data n Cache

After doing All process, Why am I faceing That Issue?

Sorry For My Bad English
[Zenfone 5 Q&A, Help & Troubleshooting] fsl24862:
Before flashing rom u have to wipe system and internal storage(backup important personal files from internal storage before wipe)
[Zenfone 5 Q&A, Help & Troubleshooting] Naim Islam:
I Already Done That
[Zenfone 5 Q&A, Help & Troubleshooting] fsl24862:
U said u Wiped Data and cache before flash, so I assume you are not Wiped system. I always go to advanced wipe and select cache, data,darvik cache, system and internal storage,. And I never ever faced force close issues
[Google Pixel XL Guides, News, & Discussion] blueyes:
I have the Verizon Pixel XL and can now toggle the oem unlock switch in developers settings. Annoyed with the "grey out" I have done several things to make the switch useable. Well... Something worked. Now it's time to figure out what did the trick.

Solved. Using a root file explorer, got to /data/system/users/ 0.xml Open it up and edit it to reflect no restrictions. Or clone mine, might wanna remove my name though.. One requirement for this to work, all testing shows it will not work on stock kernel. Not sure if its a selinux issue or not but the modified ElementalX I made does boot up permissive and removes forceencryption. And using it Confirmed working..
[Google Pixel XL Guides, News, & Discussion] blueyes:
I am decrypted and running permissive. All done through kernel editing. Not sure that made a difference or not but did notice any changes beforehand.
[Google Pixel XL Guides, News, & Discussion] jjayzx:
So you added the supercid through the kernel editing?
[Google Pixel XL Guides, News, & Discussion] dualityim:
Sorry to be a bit off-topic but do you plan to document how you did the decrypt and permissive mode anywhere?
[Google Pixel XL Guides, News, & Discussion] death2all110:
I'm guessing one of the unlock properties is what did it. I think something on the phone is recognizing it as a VZW model and is setting one of the properties to 0 and graying it out. I'll do some digging this weekend
[Google Pixel XL Guides, News, & Discussion] blueyes:
To decrypt you must fastboot format userdata. Flash a kernel the does NOT force encryption. Don't know if any are available so I edited the radial my self , on both kernel and boot-to-root images. To run permissive you simply add androidboot.selinux=permissive. I can upload the edited images later if your unfamiliar with modifications
[Google Pixel XL Guides, News, & Discussion] blueyes:
Just added it to the kernel cmdline
[Google Pixel XL Guides, News, & Discussion] jjayzx:
Thanks. I'll be back in a moment.

Update: It didn't work that way. Trying something a little different.

Update 2: Managed to change cid but still 0 for unlock support and grey. Going to try 1 more thing.
[Google Pixel XL Guides, News, & Discussion] blueyes:
The kernel cmdline has to be edited before flashing. Try adding the persist.sys.oem_unlock... Line. Before run su , then set enforce 0
[Google Pixel XL Guides, News, & Discussion] Rootuser3.0:
Why is being able to toggle it a big deal? If your unlocked then why does that matter ?
[Google Pixel XL Guides, News, & Discussion] blueyes:
Who said it was a big deal. I clearly stated in op that it annoyed me. If you've got nothing positive to say then don't say anything.
[Google Pixel XL Guides, News, & Discussion] blueyes:
And it's not just about being greyed out. I can now lock my bootloader and unlock it without any exploits. Simply using fastboot. Which sir, I do find to be a nice feature...
[Google Pixel XL Guides, News, & Discussion] Rootuser3.0:
I never said you said" it was a big deal" I said that. Go kick rocks
[Google Pixel XL Guides, News, & Discussion] jjayzx:
I lost my ability of changing the cid but then i remembered it was after i had did the supercid. So when i put them both back my cid is now changed but my unlock support is still 0. I tried adding persist to default.prop but it didn't take or i did it wrong.
[Google Pixel XL Guides, News, & Discussion] treIII:
Did you do the kernel command on the phone? How do I edit default. Prop? I feel like that's where the transformation takes place since it's not editable like the build prop
[Google Pixel XL Guides, News, & Discussion] blueyes:
Did you add the line persist.sys.oem_unlock_supported=1.

Persists seems to be equivalent to a system override
[Google Pixel XL Guides, News, & Discussion] blueyes:
Go troll somewhere else.
[Google Pixel XL Guides, News, & Discussion] blueyes:
Here's my build.prop

https://www.dropbox.com/s/bxgrk7ug66jiuz1/logs.zip?dl=0
[Google Pixel XL Guides, News, & Discussion] treIII:
Ok thank you and is this done through terminal or pc
[Google Pixel XL Guides, News, & Discussion] treIII:
That may be over my head as far as my abilities and I hate to create a new brick
[Google Pixel XL Guides, News, & Discussion] blueyes:
I am going to figure it out. I'm honestly surprised this phone hasn't died from the abuse I've given it. It's definitely confused. It's actually showing supercid as my cid now. And questionable return from getvar all while installing twrp last night. If you get a chance can you run getvar all so I can compare. Thx and apparently 96? battery life is s low now.
[Google Pixel XL Guides, News, & Discussion] blueyes:
Looking at the link to the pork explosion, not sure it's an actual exploit but the fastboot reboot-ftm cmd does reboot and is recognized. Ran it on sheer curiosity. Seemed to just reboot to me. Wasn't a safe mode.
[Google Pixel XL Guides, News, & Discussion] social-design-concepts:
Yeah i was only posting that as an example as to why one might want to dig into the various parts of the bootloader.

I think your CID change is because of your modification to the command line,

i can post getvar output for you a little later but not sure it be good to compare as i have a pixel not a pixel xl.

i have to finish some device upgrades then i'll post getvar for you.
[Google Pixel XL Guides, News, & Discussion] death2all110:
Fastboot oem rebootRUU just reboots the device as well.
[Google Pixel XL Guides, News, & Discussion] treIII:
You gave me the answer. No need. We still haven't defined what triggered the toggle
[Google Pixel XL Guides, News, & Discussion] social-design-concepts:
I don't think file encryption had anything to do with it outside of the factory reset and running setup wizard again.

The kernel probably probably played a roll having something to do with the way it mask the bootloader unlock combined with the correct combination of early prop changes and the version of Android he was on when it happened.

When I get off I plan to flash the first GS factory shipped rom, with a modified boot.img and use the resetprop tool to change all the props in early init on first boot and see if it makes a difference.

Another thing to test is a clean first boot with a modified boot.img that disables the setup wizard and booting with no sim and not connected to wifi, I think the boot.img being modified to mask that the device is unlocked is important.
[Google Pixel XL Guides, News, & Discussion] blueyes:
PM me your uploaded prop
[Google Pixel XL Guides, News, & Discussion] social-design-concepts:
i haven't made any changes yet. currently using View attachment resetprop.zip to change props.

but can you run this : sailfish:/ # od -A x -t x4 /dev/block/platform/soc/624000.ufshc/by-name/frp
[Google Pixel XL Guides, News, & Discussion] blueyes:
marlin:/ # od -A x -t x4 /dev/block/platform/soc/624000.ufshc/by-name/frp

000000 cd1e951d 313e80d1 22c728d5 a3954ed5

000010 5c164ae6 b59b7208 cb1af9ae fa83df2b

000020 73189019 4b000000 a208490a 1a20104e

000030 58f4c820 085426fd 96271f47 798a1fcd

000040 2cf91e65 98b06de5 fa16cb2e 2ea8d5f6

000050 19202246 9097de03 d95ea3dd 5d823326

000060 c3848073 c28147ed 797edb9e 84c5ab53

000070 0035785a 00000000 00000000 00000000

000080 00000000 00000000 00000000 00000000

*

07fff0 00000000 00000000 00000000 01000000

080000

Now whats all that mean? frp is a factory reset protection so cant make heads or tails from those values.
[Google Pixel XL Guides, News, & Discussion] social-design-concepts:
That's what I expected to see that last bit is written to the frp partition when enabling the OEM unlock from developer options and is only cleared when factory reset is performed from with in Android OS settings, it isn't set on my device, that's why you can lock and unlock your device with out depixel8. So now that we have root can we just set that bit directly?
[Google Pixel XL Guides, News, & Discussion] blueyes:
Its going to be something simple, nothing outrageous. Weve probably been over analyzing it. Check your pm, sent you a message.
[Google Pixel XL Guides, News, & Discussion] DA6030:
Isn't that the bit that depixel8 sets, via an exploit, to enable fastboot OEM unlock (without toggling the Android OS Setting)? I didn't realize it only gets reset by an Android OS factory reset; I assumed it was a one-time-use sort of thing that gets cleared by the "fastboot oem unlock".

And just to refocus this discussion, isn't this discussion about being able to freely toggle the OEM unlock setting within Android OS Settings, not about being able to freely fastboot oem lock/unlock? (Ultimately I think we mostly care about the latter, but these are subtly different, and I observe most of the research is being done on the former. And people may disagree about which one is more of a long-term persistent fix.)
[Google Pixel XL Guides, News, & Discussion] death2all110:
Yes! I was thinking the FRP partition had a role in this. I was reading how people on Nexus 5x/6p that locked their BL while having a custom rom and recovery can actually flash a frp image from recovery to unlock the bootloader again.
[Google Pixel XL Guides, News, & Discussion] social-design-concepts:
The only point to be able to toggle that option is to be able to use oem unlock without an exploit later. Toggling that option doesn't automatically unlock your device it just enables you to unlock it from fastboot.

For me figuring out how to enable the toggle has been about figuring out what makes a GS version vs VzW version my Pixel was on a GS firmware with a Fi sim yet still after sometime automatically reverted to the VzW firmware.
[Google Pixel XL Guides, News, & Discussion] Fate0n3:
I am I'm the same boat I am unlocked via dePixel but OEM unlock is grayed out And below it shows bootloader already unlocked. Is there an issue with it being like that?
[Google Pixel XL Guides, News, & Discussion] death2all110:
I get a similar output to [MENTION=6207927]blueyes[/MENTION]
[Google Pixel XL Guides, News, & Discussion] social-design-concepts:
Look at the last line it's different...

*
07fff0 00000000 00000000 00000000 01000000
080000

from mine:

sailfish:/ # od -A x -t x4 /dev/block/platform/soc/624000.ufshc/by-name/frp
000000 c14d988f 25793093 a91a6564 7bab4d94
000010 96b107d5 ffb70ec7 a3ac8c6d 23436914
000020 73189019 4b000000 a208490a 1a20104e
000030 23cdde20 294ba12b 77978ade 3a1df299
000040 bb196b5a be2e78df 76fd97bd dc51c3e4
000050 42202228 1239478c 073b860e d328c15d
000060 8950fb2a 7bf7abe2 e8734e4d b92af002
000070 00f705e2 00000000 00000000 00000000
000080 00000000 00000000 00000000 00000000
*
080000
[Google Pixel XL Guides, News, & Discussion] death2all110:
Looks like that last line needs a bit flipped...

Pretty sure dePixel8 is using a temp root method (dirty cow?) and flipping the bit in the FRP partition to allow the unlock to happen then.
[Google Pixel XL Guides, News, & Discussion] social-design-concepts:
My understanding is the bit flip is permanent until toggled off or factory reset from with in Android, I'm not going to speculate how depilex8 works but I don't believe it has anything to do with the frp, from what they originally said it was a bug in the bootloader, if they were just flipping the bit in frp that wouldn't be a bootloader bug cause that's how the bootloader is supposed to function.

https://android.googlesource.com/pl...oid/server/PersistentDataBlockService.java#50
[Google Pixel XL Guides, News, & Discussion] blueyes:
This here ? 07fff0 00000000 00000000 00000000 01000000 ??

Howd you find that mole
[Google Pixel XL Guides, News, & Discussion] treIII:
@ blueyes. I'll let you know in about an hour and a half or so I'm at work right now and XDA app will not let me p.m. anybody for some reason so I had to get back to you like this
[Google Pixel XL Guides, News, & Discussion] death2all110:
Ah. Okay. My Bad.
[Google Pixel XL Guides, News, & Discussion] social-design-concepts:
[MENTION=6207927]blueyes[/MENTION] i don't know what i'm doing wrong but i can't get a repacked boot.img to boot, ugh
[Google Pixel XL Guides, News, & Discussion] blueyes:
Using AIK by osm0sis?
[Google Pixel XL Guides, News, & Discussion] blueyes:
When I have to, I use this app. But I'd much rather flash or self install his Android AIK.

https://play.google.com/store/apps/details?id=com.redlee90.imagekitchenforandroid
[Google Pixel XL Guides, News, & Discussion] social-design-concepts:
I'll give that a try, I've tried a few tools
[Google Pixel XL Guides, News, & Discussion] blueyes:
http://xdaforums.com/attachment.php?attachmentid=3725442&d=1461180809

Works the best , can be flashed in recovery or placed with proper permissions.
[Google Pixel XL Guides, News, & Discussion] social-design-concepts:
thanks the linux version of AIK worked just fine, added androidboot.cid=11111111 androidboot.oem_unlock_support=1 androidboot.flash.locked=1 androidboot.verifiedbootstate=green to the cmdline all showing set with getprop could i add something to the cmdline to disable setupwizard our just do it through default.prop
[Google Pixel XL Guides, News, & Discussion] thewebsiteisdown:
Hold on, so now we figured well you along with some help I'm sure, figured this all out? We do have to change cid etc.? Dude this is sweet... What all needs to be done and I will do it right now?
[Google Pixel XL Guides, News, & Discussion] social-design-concepts:
Nothing's changed yet haven't factory reset I was having issues modifying the boot.img, I was only commenting on being able to finally pack the boot.img and get it to boot.
[Google Pixel XL Guides, News, & Discussion] thewebsiteisdown:
Thank you! Thank all of you in the community that are working on this! I'm assuming this will be made like a tool or flash-able zip here soon to where we can just flash it or change it ourselves?

Thank you again seriously, I mean no rush by all means just curious is all.
[Google Pixel XL Guides, News, & Discussion] social-design-concepts:
alll I've done so far is add your changes to cmdline plus a couple of additional prop changes to the begining of the cmdline :

androidboot.cid=11111111 androidboot.oem_unlock_support=1 androidboot.flash.locked=1 androidboot.verifiedbootstate=green

these changes report the supercid and make the devices think it's locked in a secure state. i don't have the Fi sim at the house but going to factory reset with no sim and see if anything changes.
[Google Pixel XL Guides, News, & Discussion] blueyes:
Along with the build.prop edits, make a duplicate for the major players, using "persist..." That creates the override, and creates a file -flag in data/property.
[Google Pixel XL Guides, News, & Discussion] social-design-concepts:
no change in in toggle with just but saw this in logcat :

OobConfig: zeroTouchConfig set: false, simLockConfig set: false, disallowOemUnlock restriction set: true
[Google Pixel XL Guides, News, & Discussion] vacaloca:
The ideal experiment would probably be to get identical pixels... say one 32gb from VZW another from Google, then root/make a dd backup of each partition and compare each one individually... chances are the differences won't be very much, except for any sensor calibration data and other unique markers -- serial number, IMEI, etc. Just my 2 cents.
[Google Pixel XL Guides, News, & Discussion] blueyes:
Partitions that you have access to wouldn't make a difference. It's hard coded. Now you could build it from source editing out he flags. Which is my next move.

https://github.com/blueyes27/android_device_google_marlin
[Google Pixel XL Guides, News, & Discussion] social-design-concepts:
just realized i was on the vzw image, guess i'll redo everything on the gs images later
[Google Pixel XL Guides, News, & Discussion] blueyes:
Lol. I'm still on P
[Google Pixel XL Guides, News, & Discussion] jjayzx:
I don't know if anyone else has tried on P, I'm on X. I haven't had time to mess around with it lately cause I've been busy but been reading though.
[Google Pixel XL Guides, News, & Discussion] blueyes:
Build P,XYZ or whatever , I doubt that it matters. Probably only a radio.img that makes the V&X differ..
[Google Pixel XL Guides, News, & Discussion] thewebsiteisdown:
If you need anything tell me as I have the google 32 and vzw 32. My vzw 32 is unlocked and rooted and a weta's custom rom installed however.
[Google Pixel XL Guides, News, & Discussion] blueyes:
Thanks , may pic your brain, or device. Ive got the vzw branded. I finally got off the P build. I'm on V/X now. V system, X bootloader&radio. Running fine. Bootloader oem toggle switch still alive.
[Google Pixel XL Guides, News, & Discussion] blueyes:
Finally having success building Marlin, had to get my environment set right , ninja and a/b crap suck. Anyway, just finished the first Marlin AOSP. Now I just need to make edits , and nullify the whole who gets to swing the unlock switch. And build then theoretically , anyone can use it.
[Google Pixel XL Guides, News, & Discussion] social-design-concepts:
Haven't messed with the a/b stuff yet but ninja yeah, I had to stop building with 4 threads cause 8GB wasn't enough.
[Google Pixel XL Guides, News, & Discussion] jjayzx:
Get this, I'm about to go to bed but the best thoughts are while on the ****ter. I'll give info when I have time in the morning.