yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) Q&A, Help & Troubleshooting] Naddict:
I have tried both OTA and the stock rooted rom that is here in the development section, there are users who have had great success using the SU version 2.62...I personally have used 2.62, then 2.64 with great success...I have not used the system-less SU in these cases (although I have tested previously and they also worked)

so, feel free to flash the stock rom found in the development section, then flash 2.6(whatever works for you)...none of what I state is an endorsement of one rom over another, as all members here have contributed great efforts to get us this stuff...:good:
[X Style (Pure) Q&A, Help & Troubleshooting] pizza_pablo:
I am not really following....I think you are saying that the ROMs are safe.

Are you saying that a "regular" root method, for 6.0 OTA is available and stable and I shouldn't be worried about taking the 6.0 OTA?

If I were to take the 6.0 OTA, could I get back to 5.1, since unlocked bootloader is available?

Could this be done with the return to stock tool, even after 6.0?
[X Style (Pure) Q&A, Help & Troubleshooting] Naddict:
My point is, if you are rooted and unlocked, why take the OTA if you could just flash the 6.0 stock rom? why would you want to go back to 5.1?
[X Style (Pure) Q&A, Help & Troubleshooting] pizza_pablo:
I just want to learn what I can, before I start doing anything. I've read much, but I'm still confused as to what is possible and what is not. I've not had a phone this new, with the capability of unlocking the bootloader.

I believe that if the MXPE is on 5.1.1 when I fire it up, it will soon want to install the update.

I would like some time with the phone before I have to jump into unlocking and rooting, but I don't think I'll have it, so I would like to be prepared.
[X Style (Pure) Q&A, Help & Troubleshooting] 20degrees:
Did they lock the bootloader in 6.0?

I'm in the same boat as the op. Seems like there's no clear tutorial or anything. I just want stock with everything included (factory) 6.0 with xposed and root. I didn't even see a flashable stock MM zip with root anywhere.
[X Style (Pure) Q&A, Help & Troubleshooting] Naddict:
http://xdaforums.com/moto-x-style/development/rom-stock-rooted-debloated-x1575-6-0-t3262242 here is stock in several flavors...if you do not have root, there are several options to try...systemless, or the latest beta SU's...some have stated that version 2.62 has been good for them...I have tried 2.62 and have also flashed 2.64 and both worked for me. Do some reading in these threads, plenty of guidance and info already about these issues.
[X Style (Pure) Q&A, Help & Troubleshooting] pizza_pablo:
Believe me, when I say that I AM reading. I had shoulder surgery, last Wednesday, so I've got time on my hands. How else do you think I ended up finding and buying a relatively new Motorola, with unlockable bootloader? :)

There is just so much info and while reading, I keep going down rabbit trails of other interesting things to know about rooting it, but may not be the most important question I have. I read the entire thread on the (De)Odex Stock / Rooted / Debloated 6.0 MPH24.49-18, last night and am still confused.

It just seems to be unclear whether or not 6.0 is fully rooted and if there is any going back, once you're there.

I am leery, because if the Note 3, in safestrap. Once a LP ROM was flashed there was no going back to KitKat, even tho, early on, many stated that it was possible.

I've been away from Motorola rooting, since my RAZR M. I don't recall all the PC steps.
[X Style (Pure) Q&A, Help & Troubleshooting] Naddict:
6.0 is rooted...see attached
[X Style (Pure) Q&A, Help & Troubleshooting] pizza_pablo:
I believe that 6.0 is rooted.

My question is how.

Which root methods are available?

Is systemless the only choice?

What is the exact (step by step) flash order?

Once the 6.0 OTA is taken, is it possible to go back to 5.1.1 stock or rooted, if desired?
[X Style (Pure) Q&A, Help & Troubleshooting] Naddict:
here are my offerings to your questions...

My question is how.

Which root methods are available? SU silly! :p

Is systemless the only choice? No -- (note my previous screenshot is not systemless and is beta 2.64) see my previous posts on this

What is the exact (step by step) flash order? see this link, http://xdaforums.com/moto-x-style/general/xt1572-mm-twrp-root-xposed-t3276792 but note it is for the 1572 device, steps are the same...you will need the 1575 Stock rom found here instead http://xdaforums.com/moto-x-style/development/rom-stock-rooted-debloated-x1575-6-0-t3262242

Once the 6.0 OTA is taken, is it possible to go back to 5.1.1 stock or rooted, if desired? look in this thread, but start with this post...http://xdaforums.com/showpost.php?p=64463125&postcount=179
[X Style (Pure) Q&A, Help & Troubleshooting] pizza_pablo:
here are my responses to your offerings to my questions...

My question is how.

Which root methods are available? SU silly! :p yeah, I meant traditional or systemless, silly :D

Is systemless the only choice? No -- (note my previous screenshot is not systemless and is beta 2.64) see my previous posts on this got it, thanks!

What is the exact (step by step) flash order? see this link, http://xdaforums.com/moto-x-style/general/xt1572-mm-twrp-root-xposed-t3276792 but note it is for the 1572 device, steps are the same...you will need the 1575 Stock rom found here instead http://xdaforums.com/moto-x-style/development/rom-stock-rooted-debloated-x1575-6-0-t3262242 ok, I've read most of the second link

Once the 6.0 OTA is taken, is it possible to go back to 5.1.1 stock or rooted, if desired? look in this thread, but start with this post...http://xdaforums.com/showpost.php?p=64463125&postcount=179[/QUOTE] I've read most of this one, too.

I really appreciate you hanging with me, thru my confusion and apprehension!
[8125, K-JAM, P4300, MDA Vario General] vettegofast:
Hey guys. I just got a Wizard 8125 (HTC P4300). Seems to be a kool phone with windows mobile 5. I am comming from a MOto Razr. Do you guys have a noob guide or anything? I would like to learn the ins and outs of this thing.

Thanks!
[8125, K-JAM, P4300, MDA Vario General] peter petrelli:
There's a wiki for you to read and also about 15 sticky threads. There is alot of information for you to read but it is for your own good so you dont brick your device.
[8125, K-JAM, P4300, MDA Vario General] vettegofast:
Yeah its some good reading. I am kinda confused on what I can do to my WIzard since its a G4. I dont wanna mess it up.
[Other SmartWatches] blogmaster2003:
[IMG="zeblaze cosmo published at androidwearpro.com"]http://androidwearpro.com/wp-content/uploads/2015/12/zeblaze-cosmo.jpg[/IMG]

Zeblaze confirmed to our site that they are releasing a new model called: Zeblaze Cosmo.

The slogan for this new model is:

ZEBLAZE COSMO SVELTE AND SMART FASHION

We know that this new smartwatch will have curved surface design, the radian is higher than in previous model Crystal and it will be sold at the end of December.

English article: http://androidwearpro.com/1198/zeblaze-cosmo-svelte-and-smart-fashion/

German: http://androidwearpro.com/de/1205/z...-schlanke-smartwatch-erscheint-ende-dezember/

Portuguese: http://androidwearpro.com/pt-pt/1202/zeblaze-cosmo-svelte-and-smart-fashion/
[Other SmartWatches] jonahy:
I have this for 2 weeks now. over all good looking watch and good build quality. Real Watch is a bit thicker than rendering image. But its acceptable size. Screen is bright with good viewing angle. watchband also is easy to swap.

Notification, Heart rate monitor , pedometer all functional.

Fundowear connected ok but Fundowear seems has short ranger than other Bluetooth devices software. Pre-installed watch faces look good but wish have more to choose from. or have some sdk let user created more.

There is a usb mass storage mode you can copy some mp3 files into watch, but cant use it set your own ringtone, also vibration alert is a bit weak.

Battery life with pedometer notification on can last 1.5 day.

Future firmware update i assume is not gonna happen as for all the MT2502c based smartwatch?
[Galaxy S I9000 Android Development] sooti:
Change log

09/03/16

* Latest commits from Coldwindofnowhere's kernel

* Latest omni commits (Mar. security patches)

* some small patches and tweaks from xc-racer99 and Coldwindofnowhere

09/02/16

* Latest commits from Coldwindofnowhere's kernel

* TWRP 3.0.0

* Latest omni commits (feb. security patches)

28/01/16

* Fixed rotation sensor bug and AOSP camera thanks to [MENTION=5414656]xc-racer99[/MENTION]

* Lots of different performance and bug fixes again thanks to [MENTION=5414656]xc-racer99[/MENTION]

* SMS Messenger is now included in package

* Latest Coldwindofnowhere kernel commits + xc-racer99 kernel commits

* Latest omni commits

* Browser and AOSP camera now included, make sure you use the new gapps-install text file in the download link

17/01/16

* Latest Coldwindofnowhere's kernel commits

* Latest omni commits including January security patches from Google

* Changed statues to RC since I think we are getting close enough to stable, please comment what issues are still not working on my side, if I don't see any major issues I will change the RC to stable next release, keep in mind its only including my side of things, not Omni, i'm not sure what status they are at.

29/12/15

* Fixed RIL crash after call ends

* Added 720P patch from Coldwindofnowhere (commit )

* Testing Coldwindofnowhere's ART tweaks (if it causes slow downs I will revert next build)

* Added bigmem settings in device settings

* Updated to latest Coldwindofnowhere commits and his 5.3 arm-eabi GCC

* Latest omni commits

23/12/15

* Fixed 720p playback by going back to awesome player

* Latest Coldwindofnowhere kernel commits

* Latest omni commits

20/12/15

* Fixed internal storage, now shows up as it should, please note the feature adopting internal sd as /data is disabled since it doesn't like formatting our block device, might fix it later, for now you can adopt an external fat or ntfs formatted sd card using storage settings and it will see it as part of /data and you can install apps to it

* Fixed support for exfat and ext4 on external sd (tested on 64GB external card)

* Pulled commit from omni (plus all the other latest) that fixes FC on Launcher3

* Latest Coldwindofnowhere kernel commits

17/12/15

* Changed to beta since its finally stable enough

* Fixed selinux (permissive for now)

* External sd should work now (only fat or ntfs partitions)

* Latest kernel commits from 'Coldwindofnowhere'

* Fixed some small EGL bug and some other small things

* Latest omni commits

10/12/15:

* Performance enhancements, works much smoother now (actually usable!)

* Android 6.0.1 base

* Latest omni commits and changes

6/12/15:

* Fixed GPS (works pretty good)

* More stability (latest omni commits)

* Latest kernel commits from 'Coldwindofnowhere', and some tweaks of my own, feels much smoother then before (although still not as fast as 1GB ram devices, and probably will never be)

1/12/15: First release, happy 5 year birthday to i9000 (released on 4/12/10!)
[Galaxy S I9000 Android Development] dracov76:
I will test :D
[Galaxy S I9000 Android Development] Soryuu:
You're kidding, right? Marshmallow actually boots on the I9000?

Getting mine to test this right away.
[Galaxy S I9000 Android Development] falconscrest123:
I flashed this rom just to test it out but it say encryption unsuccessful, and it tells me to reset the phone to be able to do it. I have done all the wipes mentioned to flash. On the note i didnt flash any gapps just the rom and i have reset it a few times and same message
[Galaxy S I9000 Android Development] sooti:
Do a full wipe again, especially data and cache
[Galaxy S I9000 Android Development] dracov76:
All time..

"Encyption unsuccessful" and i need factory reset...

I try:

Full wipe

Wipe system etc. and reintall

Install with gapps 140 mb (no open gapps)

Without gapps also have this problem

Ohh!
[Galaxy S I9000 Android Development] sooti:
hmmm... no idea, try using an older recovery that's not TWRP and see if it works, I only had this issue once and it worked fine after wipe

EDIT: I think i know what you should do, in TWRP format that data partition to f2fs instead of ext4, I think that will solve it
[Galaxy S I9000 Android Development] Alokhacker:
go to recovery -> wipe select data & select change partition convert partion to f2fs and you will be able to boot into rom
[Galaxy S I9000 Android Development] althafvly:
Hey. Can i use opengapps?
[Galaxy S I9000 Android Development] sooti:
The package i attached is opengapps_pico with a list of system apps to remove to save space, next release i'll increase system partition space so we can use regular gapps
[Galaxy S I9000 Android Development] Alokhacker:
deleted
[Galaxy S I9000 Android Development] fir1996:
Wow good job friend [MENTION=4460995]sooti[/MENTION] even s3 didn't get ril working in their build nice job keep up.:good:

Hope to see you helping S3 devs. Fixing the most annoying bug(RIL).:highfive:
[Galaxy S I9000 Android Development] Thanhtho96:
You are famous now http://www.xda-developers.com/xda-e...gn=Feed:+xda-developers/ShsH+(xda-developers)
[Galaxy S I9000 Android Development] sooti:
The dev should look at this commit, it fixes ril https://github.com/lollipopi9000/android_device_samsung_aries-common/commit/d16d39ec1dce68945e7094578a5c59193eb2caec

Only thing is they need to remove the md5.h file, that's only related to the exynos3 board i believe, but the rest should work.
[Galaxy S I9000 Android Development] kdp162:
Will this work on the i897??
[Galaxy S I9000 Android Development] Gill Android:
Bro try this guide, highly recommended

http://xdaforums.com/showthread.php?t=1447303

I faced the exact same problem on my Note 2 last week. Not able to find exact solution for my device and ROM. Then I tried this and everything is restored. Though the internal got wiped. Please note for this method to work you need to install CWM using Odin.
[Galaxy S I9000 Android Development] sooti:
I9000 only!
[Galaxy S I9000 Android Development] dracov76:
sooti my friend, I don't know how i can look last turn on application
[Galaxy S I9000 Android Development] sooti:
Not sure what you mean, are you talking about recents? the home button has issues right now, i will add it later, for now you can enable soft settings from advanced settings
[Galaxy S I9000 Android Development] sooti:
Our device is basically an external sd, it uses an internal physical sd on board instead of a removable one, pretty sure we don't use an emmc for storage, emmc is used for mmcblk0p2 if im not mistakin, that is all the difference, there needs to be a few fixes to the vold code no doubt but it should work, we need to figure out how is all. anyway as i said, post a commit and we will try it out, you need to setup a tree though, then push some commits, posting a modded fstab isn't the way to go, push the commit with your changes and make sure it works first, then let people code review and see if they accept it, if they do were good to go.
[Galaxy S I9000 Android Development] (°_o):
Uhh.. Just google eMMC... its a cheap storage basically SDCard soldered on motherboard.... our device has an eMMC. .. mmcblk0 is the eMMC.

eMMC mmcblk... see the MMC.. mmc. .

mmcblk0p1 is the first eMMC partition... used as FAT32 13gb

mmcblk0p2 is the second eMMC partition.. used as LVM, /system and /data..

Im sorry I dont know how gerrit works.. I just wanted to make an comment and share info ... I think I clicked add file by mistake...

See, the problem we are facing is..

Our physical storage isnt working because MountService is using mmcblk0p2 instead of mmcbk0p1. See logcat..

Thats all what I wanted to say in the comment at gerrit. I wasnt proposing it as a solution.. Just discussing the isssue, and share my findings . sorry for any misunderstaning...
[Galaxy S I9000 Android Development] sooti:
Ah ok, sorry i missunderstood you, thanks for the info
[Galaxy S I9000 Android Development] Gokulbalram:
You guys do realize that SD won't work unless you get SE working right?
[Galaxy S I9000 Android Development] sooti:
If you mean enforced then your wrong, same with permissive, you are right about disabled but that was fixed and only fixed external sd, internal sd is not related to selinux, since it permissive avc spits out messages but does not enforce and block requests
[Galaxy S I9000 Android Development] devloz:
Hey [MENTION=4460995]sooti[/MENTION] Apparently you moved us entirely off EXT4 (updater.sh formats both partitions to F2FS). However in updater-script there is still line that formats to EXT4. Is it to be removed? If not, what purpose it fulfill?
[Galaxy S I9000 Android Development] sooti:
where are you looking at? this is the updater.sh script https://github.com/lollipopi9000/android_device_samsung_aries-common/blob/android-6.0/updater.sh#L173

EDIT: oh you mean the one in the zip, ya, not sure why those are generated, i think that's TWRP's fault... in any case as long as you format your system + data f2fs once, it detects it in TWRP/CWM and formats accordingly
[Galaxy S I9000 Android Development] xc-racer99:
Sorry for the late reply, I think I'm in a different timezone....

Yes, apps can access the SD card - or at least I can download from the Browser and Open Camera can save pictures to it. I can also mount it via MTP.

I think the reason its not showing up as primary is either that I set "ro.vold.primary_physical 1" or that I didn't adopt the storage (because I can't without removing my /data partition).
[Galaxy S I9000 Android Development] MICHAELMAGED:
great rom better than the lollipop and kitkat for me & call delay is gone but it is missing some apps like mms.apk dspmanager.apk & browser.apk but no problem i took them from the lollipop &they worked. thank you [MENTION=4460995]sooti[/MENTION] for this great rom.
[Galaxy S I9000 Android Development] (°_o):
Never mind, that was my old finding.. vold is smart enough you dont need that prop... noemulatedsd only works .. I already found the issue in our case..

In our case MountService is using second partition which is lvm and vold is trying to link the nothing, as primary storage.. giving /dev/null

If you do 'ls -l /mnt/user/0/' .. you will see primary is linked to /storage/[uuid] which means your sdcard is primary storage...
[Galaxy S I9000 Android Development] (°_o):
About the warning about battery.. I dont think its related to battery at all...

This seems to happen if the kernel cannot mount /data partition in normal boot... It will go to endless loop at Samsung logo after that...

If we forgot to format /data to as f2fs.. then system is at least mounted so we see bootanimation.. but /data is not... then we pull out battery .. its on bootloop forever.. no recovery too

The updater.sh wont format to f2fs... the command is wrong....

See recovery.log 'make_f2fs' command not found.. The correct command is mkfs.f2fs.. but thats different story..

So guys format data to f2fs in TWRP.. or you need odin...

[MENTION=4460995]sooti[/MENTION] [MENTION=6794010]Coldwindofnowhere[/MENTION] why is kernel going loop frenzy if it cannot mount /data at normal boot.. .. are we saving some config in /data ?
[Galaxy S I9000 Android Development] SiriusCybernetik:
Hi. It looks like I am going to need Odin.. Although I did format data to f2fs.

Btw, I realized that I have deleted my collection of i9000 stock ROMs some time ago. Does anybody have a working link to xxjvs or xxjvt ROM? All the links I could find on Google are broken.

Thanks in advance for your help.
[Galaxy S I9000 Android Development] sooti:
Thanks, ill fix the script, no idea about the boot /data crazy thing, ill need a logcat or kmsg if you want me or Coldwindofnowhere to address it
[Galaxy S I9000 Android Development] althafvly:
Hey

The home button doesnt fixed yet?

So a build with fix. But not now
[Galaxy S I9000 Android Development] (°_o):
[MENTION=3265540]SiriusCybernetik[/MENTION] Just flash any kernel before shift to LVM like Semaphore KK.. Then you can flash any ROM zip .. reboot recovery... then restore TWRP backup..

This seems to be some bug at stage1 init .. The second stage ramdisk isnt being extracted and executed... so no android or recovery..... so we can guess the kernel panics and reboots. but theres nothing to reboot too hence the fast bootloop ..

Its hard to say where the bug is though.... if we look through commits after lvm was brought up maybe we can find it.. but thats too much for something that can be avoided by precautions...

on a side note [MENTION=4460995]sooti[/MENTION] Setting vfat in fstab for internal formats the second partition as vfat.. thats how i found the above stuff....

we gotta find some way for vold to ignore the second partition... lets wait for caio input on this..
[Galaxy S I9000 Android Development] sooti:
I agree
[Galaxy S I9000 Android Development] sooti:
Home button works fine
[Galaxy S I9000 Android Development] SiriusCybernetik:
I have tried flashing the latest semaphore kk kernel but even the I keep getting the Status 7 error, no matter what room I try to flash.

See attached screenshot.
[Galaxy S I9000 Android Development] (°_o):
No wonder.. why we cannot switch /system...

Its hardcoded in stage1..

https://github.com/Coldwindofnowher...droid-5.1/usr/galaxysmtd_initramfs_files/init

Lines 20 and 40

I was confused how Line 20 and 40 worked... if we have f2fs... but then I check mounts in device.. it's ext4 for /system...

Good thing the updater-script formats /system to ext4...

We need to fix updater.sh.. so it formats /data as f2fs.. but /system as ext4....
[Galaxy S I9000 Android Development] sooti:
Flash stock then kitkat and then back to 6.0
[Galaxy S I9000 Android Development] SiriusCybernetik:
Thanks. I finally found a backup with old stock ROMs.

Flashed and back in the game.
[Galaxy S I9000 Android Development] devloz:
Do we have problem with supporting auto mode? There was something like:

busybox mount -t auto /dev/lvpool/system /system

or even:

for fs in f2fs ext4
do
busybox mount -t $fs /dev/lvpool/system /system
done
[Galaxy S I9000 Android Development] (°_o):
Ah,.I think I flashed Ressurection Remix 5.0 in CWM it worked... It asked for repartition.... then i reboot to its TWRP recovery and restore boot only of Omni 5.0... reboot to recovery again.. and restore.. rest of Omni 5.0...

Trying to minimize the flashing process...

Staus 7 errors are because of aborts... Something wrong with assertion checking...

Man you gotta be careful while flashing stuffs to this device... :|
[Galaxy S I9000 Android Development] (°_o):
Not really.. We have to test it though.. The stage1 busybox is rather limited.. but the second option might work...

I just thought fixing it in one place is easier to implement... just have to change a line in updater.sh

Than to fix it in 3 different places.. updater.sh, updater-script., init of kernel... and test it too...

Besides, f2fs reserves some 200mb for its use... so it will impact storage of little we have in /system..
[Galaxy S I9000 Android Development] devloz:
Yeah, it's just... the whole idea of hardcoding values is awful to me. And what about $(cat /proc/filesystems) as reference for the loop? Dunno if it's gonna work, gosh. I think I'll configure Ubuntu#Android environment, get my phone, and start messing around with it.

PS: Can't we update lvm prebuilt binary? I think it's a bit aged.