yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 General] LastStandingDroid:
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.0 (Lollipop), which is designed to increase performance and reliability over stock Android for your device.

#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/

CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community.

It can be used without any need to have any Google application installed.

CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.

All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.

STATUS:

This is a direct port of CM11 to CM12.0 for n8010 and n8013 version of Galaxy Note 10.1

Rom is built with CM11 development branch, so bugs are expected

All the source code is available on my Github.

I do this on my free time and unfortunately I don't have much.

Any help is a appreciated!

LINKS:

CURRENT VERSIONS:

-20/11/2014:

unobootvercm12

Changelog:

Initial release - Proof of concept that we're building.

OLD VERSIONS:

None:

Source code: https://github.com/lirokoa

KNOWN BUGS:

Doesn't Boot Need a proprer updater.zip :D

FAQ:

I can't flash CM11, an error occurs.

You need to use a recovery that support KitKat ROM.

I can't flash CM11 on my n8010 tablet

You need to remove the assertion (1rst line until ; ) in the META-INFcomgoogleandroidupdater-script

Once this is done you won't need to do it anymore

CREDITS:

The whole Cyanogenmod team

All people who works on the Galaxy Note 10.1

XDA:DevDB Information

Unofficial Cyanogenmod for n8010/n8013/n8000, ROM for the Samsung Galaxy Note 10.1

Contributors

lirokoa

ME

ROM OS Version: 5.0.x KitKat

ROM Kernel: Linux 3.x.x

Version Information

Status: Experimental

Created 2014-11-20

Last Updated 2014-11-20[/QUOTE]
[Galaxy Note 10.1 General] LastStandingDroid:
reserved

unsecure boot.img

https://www.sendspace.com/file/qau7jp
[Galaxy Note 10.1 General] link6155:
So it current doesn't boot? Do you have any idea of when you'll get the updater.zip working?

Great work btw, really do appreciate the effort :)
[Galaxy Note 10.1 General] LastStandingDroid:
sorry no eta on that one, depends on if i can get make otapackage or mka bacon working or if i can use another updater script ;)
[AT&T Samsung Galaxy S 5] cstayton:
​

[B][U][COLOR="Red"]The download package includes all of the following:[/COLOR][/U][/B]
1. Original untouched eclipse source code from [URL="https://github.com/OTAUpdateCenter/ota-updater-2.0"][B][COLOR="Red"]HERE[/COLOR][/B][/URL]
2. Original modified decompiled source V2.0.5 apk
3. Modified decompiled source (My Modifications) V2.0.8 apk
4. Example "rom.ota.prop"
5. Required "ota.prop" (For SafeStrap support)
6. Text file containing links required to be posted in your OP

[B]Required tools for successful build[/B]
1. VTS (Virtuous Ten Studio) or (Apk MultiTool v1.1.0)
2. If working with the untouched Eclipse Source Eclipse Juno and the current version of Gradle
3. A text editor capable of Unix/Linux encoding (Notepad++ recomended)
4. A tool for comparing files (Winmerge is the tool I use)
5. A Dropbox account or other file sharing account that allows for Direct download links (No landing pages)

Instructions

​

1. Download the zip package [URL="http://xdaforums.com/devdb/project/?id=6766#downloads"][B][COLOR="Red"]"Unity_OTA_Mod.zip"[/COLOR][/B][/URL] and extract to a working folder.
2. Using your tool of choice either VTS or Apk MultiTool decompile both included apk files
3. Using Winmerge or other diffing tool compare the decompiled sources
4. you can easily see the changes between 2.0.5 and 2.0.8 [B]pay close attention to the downloadsactivity.smali.[/B]
5. Once you have completed your changes/modifications recompile the APK.
6. Go [URL="https://www.otaupdatecenter.pro/"][B][COLOR="Green"]HERE[/COLOR][/B][/URL] and follow their instructions for setting up your ROM
7. Reboot your device to SS Recovery
8. Push your compiled APK to /system/app/OTA-Updater.apk
9. Push your "rom.ota.prop" and the included "ota.prop" to /system
10. Push "com.unityota.feature.xml" to /system/etc/permissions/com.unityota.feature.xml
11. Wipe cache and dalvik-cache and reboot
12. Verify application opens and contains all of your modifications
13. Once you have an OTA file setup for your ROM [B][COLOR="Red"](see step #6)[/COLOR][/B] test the application for download and flash.

[B][COLOR="Red"]Special NOTE: Remember to change the hypelinks in the code to point to your threads, do NOT however, change the hyperlink inside of "APIUtils$APITask.smali" that points to the otaupdatecenter site that checks for your OTA packages.[/COLOR][/B]

!!THANKS!!​

@hashcode - for SafeStrap Recovery
@geohot - for root
[URL="https://www.otaupdatecenter.pro/"]otaupdatecenter.pro[/URL] - for the original source and OTA environment
Google - For Android
Virtuous Developers for VTS
github for providing source code control and open source access

!!!Disclaimer!!!​

XDA:DevDB Information

OTA-Updater, Device Specific App for the AT&T Samsung Galaxy S 5

Contributors

cstayton, https://www.otaupdatecenter.pro/

Source Code: https://github.com/OTAUpdateCenter/ota-updater-2.0

Version Information

Status: Stable

Current Stable Version: 2.0.8

Stable Release Date: 2014-11-20

Created 2014-11-20

Last Updated 2014-11-20
[AT&T Samsung Galaxy S 5] cstayton:
Reserved
[AT&T Samsung Galaxy S 5] Simon Hammers:
Bri needs to integrate this into Dynamic Kat!
[AT&T Samsung Galaxy S 5] mataflakitas:
Exelente ...amigo gracias x su duro trabajo

Enviado desde mi SM-G900F mediante Tapatalk
[AT&T Samsung Galaxy S 5] dabuddyhenry:
im a noob, wanted to know if i have to change anything like the instructions say to do, if i have stock rom. i have a gs5 with stock rom, just root. thanks in advance.
[AT&T Samsung Galaxy S 5] Simon Hammers:
Noob or not, at least somebody replied to this damn thread lol
[AT&T Samsung Galaxy S 5] FilthyFord:
I think this is more for developers bud. Unless you know how to do what was stated above. Unless your wanting to learn how to do it, this is not necessary for us who just flash roms.
[AT&T Samsung Galaxy S 5] cstayton:
this is for devs not a mod you can add to your stock rom
[Sprint HTC One (M7)] magni08:
When I try to flash any ROM that has M7SPR in the title, I get an error saying that my phone is the M7. But I have sprint and I am trying to get M7SPR becuase M7 ROM's make me lose data.

Background data:

M7_WLS

SuperCID

S-OFF

MID 20000

Basically my questions are:

1. What would cause my M7SPR to think it is a M7?

2. Is there a workaround to keep LTE with GSM ROMs?

3. If there is no workaround for the #2, how do I get my phone to flash M7SPR ROMs again where I can keep my at least my sprint data intact?
[Sprint HTC One (M7)] sauprankul:
How are you flashing gsm Roms on this phone. They have different partitions.

I think you dun goofed your partitions. Try RUUing to the latest Sprint firmware and never flash a GSM ROM again.
[Sprint HTC One (M7)] magni08:
I flashed a stock sprint RUU then while in bootloader, reflashed twrp 2.8, then flashed slimkat m7spr, now if I went back into twrp and tried to flash any other m7spr rom, I get a failure saying that this device is an m7 and this rom is for m7spr...
[Sprint HTC One (M7)] sauprankul:
fastboot getvar all

Post results here.

Remove serial number and imei.

Also, if you want a response, remember to quote.
[Sprint HTC One (M7)] magni08:
c:\adb>fastboot getvar all

< waiting for device >

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.56.5555

(bootloader) version-baseband: 1.00.20.1108

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 4.06.651.4

(bootloader) version-misc: PVT SHIP S-OFF

(bootloader) serialno: ------------------

(bootloader) imei: ---------------------

(bootloader) meid:-----------------

(bootloader) product: m7_wls

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0720000

(bootloader) cidnum: 11111111

(bootloader) battery-status: good

(bootloader) battery-voltage: 4258mV

(bootloader) partition-layout: Generic

(bootloader) security: off

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-4dab9d12

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

There you go, thank you for the advice regarding the response time and quoting.
[Sprint HTC One (M7)] sauprankul:
Your boot loader is outdated. Current is 1.57. Baseband is off, supposed to be 1.29(edit: I pulled this number from my butt, I meant 1.01) i think. Version is supposed to be 5.05. CID - set it to the default sprint, if that's not it.
[Sprint HTC One (M7)] magni08:
Have you got a url for the baseband? This is the only one I could find for this specific phone; http://xdaforums.com/showthread.php?t=2406330 and they seem to be slightly outdated.
[Sprint HTC One (M7)] sauprankul:
http://xdaforums.com/showthread.php?t=2795856
[Sprint HTC One (M7)] magni08:
I just flashed that RUU and the radio is still 1.01.20
[Sprint HTC One (M7)] sauprankul:
Still? It was 1.00.2 before the RUU.

Also did you change your cid?
[Sprint HTC One (M7)] Aldo101t:
latest baseband is 1.01.20.0904_2

why would you super cid a sprint phone, it's pointless, because you can't flash GSM roms on a cdma phone,period.
[Sprint HTC One (M7)] magni08:
I guess i might have overlooked it, since it was 1.xx.2 looking quickly I thought it was no change. I have not changed the cid. From what I was reading that is considered supercid, which is supposed to bypass carrier specific ROMs. Making it much more difficult to brick.
[Sprint HTC One (M7)] sauprankul:
Would you considering trying to change back to SPCS_001? (I think that's the right one)

I'm pretty sure changing CID doesn't allow you to flash GSM roms. Super CID only applies to GSM phones.
[Sprint HTC One (M7)] magni08:
Can anyone confirm that SPCS__001 is the correct cid for sprint m7? I am down to try it, but I want to be sure that's all.

I do appreciate your help as well!
[Sprint HTC One (M7)] sauprankul:
Here is my getvar

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.57.0000

(bootloader) version-baseband: 1.01.20.0904_2

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 5.05.651.2

(bootloader) version-misc: PVT SHIP S-ON <<note that this is actually S-OFF, I have a custom HBOOT

(bootloader) serialno: ****

(bootloader) imei: ****

(bootloader) meid: ****

(bootloader) product: m7_wls

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0720000

(bootloader) cidnum: SPCS_001 //here is the CID

(bootloader) battery-status: good

(bootloader) battery-voltage: 3748mV

(bootloader) partition-layout: Generic

(bootloader) security: off

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-0e1af350

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0
[Sprint HTC One (M7)] magni08:
I put my cid back to SPCS_001 and tried another M7SPR rom (http://xdaforums.com/sprint-htc-one/development/5-0-lollipop-unofficial-cm12-m7spr-t2943941 this one specifically) and I get the same message:

This package is for device: m7spr, m7wls: this device is m7.

I also just tried the aokp (http://xdaforums.com/showthread.php?t=2268789) same thing...

This is the only rom (http://xdaforums.com/sprint-htc-one/development/stock-rooted-5-05-651-2odex-11-15-2014-t2941907) that actually works, rather frustrating.
[Sprint HTC One (M7)] sauprankul:
[MENTION=4609217]BD619[/MENTION] any idea how this catch meachanism works? Like, what does it read? Seems like everything is set back to default for this one.

Actually did you run the RUU.exe (as opposed to flashing the firmware)? Or try to flash the latest stock ROM (4.4.3, 6.09)?
[Sprint HTC One (M7)] Sloth:
Sounds like the OP flashed the wrong recovery.

I would suggest run the RUU and start fresh.

OP you posted this in post 1 MID 20000 can you explain what that means?
[Sprint HTC One (M7)] magni08:
The recovery is the latest from the twrp team straight from their site. I did try and revert back from 2.8 to 2.6 but it hung up at the htc loading recovery screen. From that hangup I reflashed the 2.8 I was using just to get something moving. I will look into the changing twrp and try something from there.

The MID 20000 is a reference to; modelid: PN0720000 to indicate that I was in fact using the sprint variant of this phone.

Thank you for the assistance.
[Sprint HTC One (M7)] Sloth:
There is a version of twrp for every variant maybe you flashed one of the other variants by mistake (folks flash the M7_ul version all the time)

Official TWRP

tdhite version of TWRP (try this one first it has been polished a bit more then official)
[Sprint HTC One (M7)] magni08:
I think it might just have been the recovery, either bad download/flash/version who knows, I went that the 2.8.0.3 and was able to get cm12 to flash. I am going to try aokp just to be sure (last attempt at the m7 cm12 it went into a bootloop, going to try the m7spr cm12).

Thanks a bunch! You guys rock!
[Sprint HTC One (M7)] sauprankul:
nailed it

Now that I think of it, this should have been fairly obvious at first. The recovery was the only non-stock part of his entire setup.
[Sprint HTC One (M7)] magni08:
Definitely something I need to check first next time. (If there is a next time) I was certain that I had the correct recovery but it could be that the particular version I had was inaccurate. Thanks again for all the help!
[Moto G Q&A, Help & Troubleshooting] daniel1112333:
Is Android Lollipop out for Moto G (1st) GPE? or still not? (bought mine from Google's website)

:confused:
[Moto G Q&A, Help & Troubleshooting] eemgee:
Have you got it?

No?

Guess what......ITS NOT OUT
[Moto G Q&A, Help & Troubleshooting] rickastillo:
sorry if this is a stupid question, but if i've already unlocked the bootloader, and installed root and recovery but i didnt change/modify the original/official ROM 4.4.4 from my moto G, in order to get the lolipop update, i just need to install the original "stock" recovery or i will need to flash everything (firmware/radio/originalrom, etc) again? thanks in advance folks, im just new with moto g.
[Moto G Q&A, Help & Troubleshooting] eemgee:
If you have stock recovery and unmodified system you should be fine with the ota, when it comes.
[Moto G Q&A, Help & Troubleshooting] MarckozZ:
Listen to mw, if you dont wanna have trouble with the ota, flash entire firmware! Do that and you will see there will be no problem... Restore entire firmware before updating via ota.
[Moto G Q&A, Help & Troubleshooting] Qadir64:
Afaik you can also use CWM to update
[Moto G Q&A, Help & Troubleshooting] rickastillo:
Oh ok, well i guess i will have to do that, my motog is the dualsim type XT1033, i bought it on amazon, i asume it is the "brazilian" one nor the asian , but it would be any problem if it happens to be the asians one? or there is any different between these two? i guess i did the wrong thing (unrooting and install a custom recovery) days before loli pop update T_T

I guess the OTA notification still will show up even if it's recovery was modified
[Moto G Q&A, Help & Troubleshooting] laufersteppenwolf:
I guess the question is answered so we can close this one ;)

---> Thread closed
[Sony Xperia L] XperiaAwesome2000:
Hey So todaymy mum bought her new Magnetic dock for her Z3 and gave me her old LiveDock from SonyEricsson ,but the Phone doesnt charge can someone Help me ?
[Nexus Player Original Android Development] bunchies:
I am not responsible for whatever may happen to you or your device when using this, Run this at your own risk!!

Requires unlocked bootloader!

Based on SuperSU - v4.46 (the binary updates from within the app later on)

I put together root installer script that comes with SU-binary/App with a insecure boot.img, everything is done over adb shell since we don't have a recovery right now but i will be working on it and already booted CWM

For current firmware:

LMY47D - root-boot

For past firmware:

LRX21V - root-boot

For past firmware:

LRX21M - root-boot

[YOUTUBE]wngrpZWqSKQ[/YOUTUBE]

crappy video but simple demonstration :good:​

How to install:

Thanks [MENTION=631273]Chainfire[/MENTION] for Superuser

My Donation Box​
[Nexus Player Original Android Development] bunchies:
Troubleshooting:

Check to make sure your device gets picked up in adb before running the script - - - ADB Drivers

This tool uses an unlocked bootloader and i have not unlocked mine yet, does unlocking the bootloader wipe the device? - - - Yes unlocking the bootloader will wipe the device

After fastboot flashed the boot.img than rebooted to the home screen i continued the the script like the installation steps said but it returned "device not found" - - - As long as it shows transferring files a few seconds after than its fine, adb restarts at that moment which will than return "device not found" than it reconnects and transfers. if fastboot flashed than rebooted fine than adb shouldn't have an issue

Help! Something went wrong and im bootlooping but i dont want to loose all my saved data - - - Everything is fine, Download the factory zip from here for your android version than extract the zip and retrieve the system.img and copy it into a folder that contains adb/fastboot and boot your device into fastboot mode and do "fastboot flash system system.img" doing it this way wont wipe your "/data" partition leaving everything intact but will restore the system back to its defaults

(If you were to run the factory zip as an update than it would format everything)

I installed SU with this method but cant use adb commands on my device - - - Go into "Settings>About" and click on "Build" 7 times very fast and it will enable "Developer options" in the settings menu, Go back to the settings menu and open developer options (You may need to reboot if it doesnt show up immediately) and enable the "USB debugging" option
[Nexus Player Original Android Development] bunchies:
Ill be updating this as new version of lollipop get released

support for both firmwares are up, any issues let me know i tested them both though and everything looked okay
[Nexus Player Original Android Development] bunchies:
Reuploading, had a minor issue

Edit: LRX21M link back up, let me know if there's any issues
[Nexus Player Original Android Development] ftarules:
Whoa...

Let the games begin....
[Nexus Player Original Android Development] bunchies:
yeup, after recovery i have a few system modification ideas for the settings apk i was considering

i do have other devices to worry about though so it may take some time
[Nexus Player Original Android Development] mikereidis:
Working well, Thank you, after semi-manually adapting for working from Linux Mint. :)

I don't have permission to do "adb logcat" or "adb shell logcat" anymore though, unless I restart adbd as root.
[Nexus Player Original Android Development] bunchies:
Use adb shell

than type su to use root adb shell
[Nexus Player Original Android Development] ggrammer:
Since running the script everything seems all good except for using voice search. Anybody else having issues where voice search just closes?

Update: Erased and manually flashed the V firmware as I was on M and now it appears to be working correctly, not sure if this is going to be a problem with people stuck on M for now but you may want to think of upgrading your fimware.
[Nexus Player Original Android Development] xReaper7x:
Getting ADB device not found.. Anywhere I can download drivers from? I have the latest android-sdk
[Nexus Player Original Android Development] bunchies:
http://developer.android.com/sdk/win-usb.html

at what point, adb will restart about half way through and it shows it cant connect to device but it really is

but if your in fastboot and it cant connect to the device than thats an issue

i should note this in the OP
[Nexus Player Original Android Development] Snuzzo:
Subscribed for later. Awaiting someone else to port a recovery for this, I am lazy.
[Nexus Player Original Android Development] bunchies:
lol Snuzzo :good: recovery coming soon
[Nexus Player Original Android Development] prstorero:
Links are down. Does anyone have a mirror of 21V?
[Nexus Player Original Android Development] bunchies:
Links are up, hosted on android file host

Can mirror in a bit if needed
[Nexus Player Original Android Development] prstorero:
Looks like it's working now. Before I was getting that the file couldn't be found. Thanks I appreciate you releasing this :) I just got it unlocked so time to root and have some fun expanding the storage to 128gb :P
[Nexus Player Original Android Development] bunchies:
Glad to hear that!
[Nexus Player Original Android Development] prstorero:
The first time around I got into the bootloop so I had to start over. Second time and it worked :) now it seems that I can't get apps to install through the adb install command. I'm mainly trying to get es file explorer and stick mount so I can use an external flash drive. Is it possible that the root method somehow nuked this functionality? I've already restarted the adb server numerous times, rebooted the player, turned debugging off and back on, etc. Even after all that it just sits after displaying the transfer rate and never finishes.

Edit: Nevermind. Looks like this issue also goes back to having to do adb root and adb remount. Gotta do it for everything apparently :P
[Nexus Player Original Android Development] bunchies:
Weird, windows 8?
[Nexus Player Original Android Development] Elrondolio:
Just wanted to post a thanks for your work. It's wonderful to have some interest in this box early on by some competent people. Have a great one!
[Nexus Player Original Android Development] prstorero:
10 technical preview, actually :P
[Nexus Player Original Android Development] akarol:
So, rooting it for what as of now? What about future updates? Is the NP going to force us to update OTAs?
[Nexus Player Original Android Development] bunchies:
Until recovery yes, I'll update this as new OTAs come along
[Nexus Player Original Android Development] akarol:
Gotcha. I guess I should have asked before. Will rooting erase everything? I'm reluctant to having to set it up every time a new update comes out and breaks root.
[Nexus Player Original Android Development] bunchies:
Rooting won't wipe everything

Updates would just remove it since the update would write over the /system partition

In case of any bootloops our downgrades you can refer to post #2

If something were to happen you can always extract than flash boot.img and system.img in fastboot manually from an OTA zip to fix anything, all user data and configuration is held in /data and untouched if you do it manually
[Nexus Player Original Android Development] iamtek7:
:good: Could not get this method working without the notice of "manually do "adb root" then "adb remount" and remount" then it continued flawlessly!

Thanks for the info/update!
[Nexus Player Original Android Development] bunchies:
If we get LRX22C or anything after related to the 5.0.1 release than I'll look through the script again since I'll have to make another zip
[Nexus Player Original Android Development] pappingfandas:
root-boot.img

Hey I'm trying to root manually and I wanted to know if the root-boot.img file downloaded for LRX21V is the root.img needed for fastboot root. Thanks!

fandas
[Nexus Player Original Android Development] bunchies:
You use the .img to obtain insecure adb (root) to be able to push the su files to the device

It is flashed through fastboot