yashsingh1/xdaforums huggingface dataset:
[Sprint HTC One (M8)] alienngp:
Requirements:

HTC Dev unlock

Root

TWRP Recovery

Backup Of Original stock of your phone

some have had some problems with the backups of the phone i come to give you a simple way of stock without the bootloop

as stated before if you dont have whats above this is not for you

1. boot into Bootloader by restarting your phone with the volume button down held

2. go down to recovery and hit the power button

3. go to restore within twrp and restore the backup

4. let it run

5. instead of hitting the reboot button navigate back to the main screen of twrp and hit reboot then reboot bootloader

6. once in bootloader again navigate to the factory reset and hit the power button it should reboot and you have a fresh stock rom from your backup

if i helped hit the like button
[Framaroot] gianfranco1991:
Hello android fans, yesterday i installed with my friends help the maximus hd rom for my htc one s..all was perfect, until i had the stupid idea to change my font and downloaded the font installer app...the first time it was all ok, at the second change , when i rebootet my phone it wont start, there is only the white display with the htc one logo...the recovery mode does work but i don't know what to do please help me...sorry for my english i'm from italy..
[Verizon HTC One (M8)] jcase:
Random internet find, I have no validated it, and take no responsibility for it. Please do comment here if it works.

If you don't have s-off, and want s-off in the future, don't upgrade to 4.4.4 else you will have to wait. It is safe to flash this if you are already s-off.

0P6BIMG_M8_WL_K444_SENSE60_VZW_MR_VERIZON_WWE_3.28.605.4_R_Radio_1.09.20.0926_NV_VZW_2.11_002_release_393762_signed_2.zip

https://mega.co.nz/#!mEp0AaxK!eEdOTmC5vBp0clsacTlukBGdLcKNNSra9VK4o0IxBmo
[Verizon HTC One (M8)] dottat:
I have this posted in the q and a section.
[Verizon HTC One (M8)] jcase:
Thats great, I have not seen a signed one of this build yet, and didn't see it in general. May I ask why Q&A?
[Verizon HTC One (M8)] dottat:
Because its the q and a / troubleshooting section. Sort of a good fit for troubleshooting.

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

Official RUU 3.28.605.4 EXE/ZIP
[Verizon HTC One (M8)] jcase:
You might want to consider moving it to General, many people dont venture to Q/A for firmware
[Verizon HTC One (M8)] dottat:
Sounds like a good suggestion. If you didn't know it was there than most people dont either.

I have it in two forms there too. Exe for noobs ?

[MENTION=2376614]jcase[/MENTION] I pm'd you my hangouts address... lets chat when you get some free time.
[Verizon HTC One (M8)] ryan1977:
Can I flash th this through twrp over stock rooted 4.4.3? I'm s-off and unlocked via sunshine already
[Verizon HTC One (M8)] ytwytw:
C:\Users\YtwYtw>fastboot flash zip C:\Users\YtwYtw\Downloads\0P6BIMG.zip

target reported max download size of 1826418688 bytes

Invalid sparse file format at header magi

then fastboot crashed...
[Verizon HTC One (M8)] Neo:
Thread Closed as discussed.

Original Thread for this RUU is located here: http://xdaforums.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845

Thanks.

Neo

Forum Moderator
[Android Q&A, Help & Troubleshooting] dbart.hanna:
I recently got a Gear 2. I like the Tizen system, but it really lacks with customization. I can't use anything from the play store and their store leaves a lot to be desired. Is it possible to downgrade to and Android system on a Gear 2?im pretty positive you can revert back to it from Tizen on the Galaxy Gear because you're just stepping back into the original system. But because the Gear 2 came with Tizen out of the box, am I stuck with this system? I'm sure there will be roms and other good things to come in the future with the Gear 2, but I would love to have Nova Launcher and Google Now at my wrist. And I'm stumped with Tizen.

Really want some Android!

DBH
[Moto X Q&A] Gundabolu SC:
Hey any devs out there will skills ,resources and the time PLEAAASE PLEAAAASE make an AOSP build for the Moto X.... I know Motorola will be quick with their updates but i just cant wait!!! I am just refreshing the Development sections of the Forum every hour hoping for a ROM build....
[Moto X Q&A] Travisdroidx2:
I believe devs would have to make a whole new kernel since L was not released for the moto x yet. Not sure if someone will do that before it is officially released for us.
[Moto X Q&A] Gundabolu SC:
I just want it! :P :P :D Caaant wait! :D i really hope some dev is already working his ass off to bring us some Lollipop!
[Moto X Q&A] Gafanhotz:
Without kernel and binaries = No deal. It was already tried with KitKat, I tried with the AOSP sources but without a Kernel developer dedicating it's precious time and the binaries/drivers, just give up on your dream.
[Moto X Q&A] Gundabolu SC:
Its definitely NOT impossible!!! When other devices like S3 mini,s3,Xperia Z can run without the binaries.... Why cant the Moto X? People have just given up on this phone! :D

I mean till now we were in the spotlight, but after Moto X 2014 we have been pushed back... We always have run the latest versions of Android till date n have never faced the need for porting n stuff... but i guess this will change when Motorola stops supporting us, then OSs would be ported withot Binaries! :D
[Moto X Q&A] Gafanhotz:
They worked on other devices because they have common parts inside of them. Commom snapdragon chips, when the Moto X has the "powerful futureproof Moto X8 Mobile Computing System", it still a snapdragon, yeah, but heavily modified. As I said, until we see sources we won't get it. Why? The work to make a KitKat kernel (specially the Moto X one) work on Lollipop isn't worth the effort. Unless you pay someone for it...
[Moto X Q&A] Gundabolu SC:
As far as I understand the modification to the processor is not to the Main processor itself but its just the addition of further coprocessors... I doubt if Qualcomm would keep quiet if Motorola messed with their processor and called it their own! :P Aaand.. Even with the sources we are not allowed to use the coprocessors right? So they are pretty much useless! I STILL don't think its THAT HARD! yeah it might be hard... But others have done it... People here just don't try as much I suppose! :D
[Moto X Q&A] 404 ERROR:
It's not worth porting over just so 50 people can have Lollipop on their Moto X 2013 when it's going to come within the next month anyway.'

Those other devices will probably either never get Lollipop or well get them much later.
[Moto X Q&A] Gundabolu SC:
I agree... Anyways... Already OmniROM seems to have started merging Lollipop...

I don't think it will be long b4 other pitch in too! :)
[Galaxy Note 10.1 (2014 Edition) Android Developmen] equilibriumtr:
Here is my port of CM11 to SM-P600, a.k.a lt03wifi. Source was almost entirely derived from the official source for SM-T520 which has almost the exact same hardware.

What works:

screen :)

wifi

bluetooth

logcat

usb otg storage

sound

microphone

multitouch

auto brightness

external sdcard

gps

softkeys

softkey backlight

flashlight

accelerometer

gyroscope

magnetometer

light intensity sensor

pen (without fancy Samsung menus of course)

both cameras

What doesn't work:

nothing as far as tested

Issues:

performance cpu governor causes sleep of death

stock cm camera app issue (see post below)

Links and how to install

Download link

ODIN flashable recovery

You won't be able to install it via TWRP for SM-P600, it will be complaining about the device name not being lt03wifiue. This is because they are mixing it up with SM-P601, it should be fixed on their side. I haven't tried but it might be the case for other recoveries as well. If you receive this error, flash the above recovery with ODIN and install from there. As a side note, the above recovery has much less features compared to TWRP but it's much faster, so it's better for quick test iterations.

I would be really glad if you can install, test and see what issues you might get.

Sources:

For those interested, here is the device source: https://github.com/ayberkozgur/android_device_samsung_lt03wifi.

You'll need the modified exynos 5420 kernel source: https://github.com/ayberkozgur/android_kernel_samsung_exynos5420

XDA:DevDB Information

CyanogenMod 11 - Note 10.1 (2014) WiFi, ROM for the Samsung Galaxy Note 10.1 (2014 Edition)

Contributors

equilibriumtr

ROM OS Version: 4.4.x KitKat

ROM Kernel: Linux 3.4.x

Based On: CyanogenMod

Version Information

Status: Testing

Created 2014-11-05

Last Updated 2014-11-05
[Galaxy Note 10.1 (2014 Edition) Android Developmen] SpoonlessCorey:
Thanks so much! I really appreciate the work you devs do. I'll install it this weekend and play with it. Thanks again!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] equilibriumtr:
Camera issue

There is a weird camera issue that I can describe as follows:

cm stock Camera app hangs when launched; after this, if killed, it will crash at its next launch and Torch will start crashing as well. This seems normal as the flashlight is probably using the same driver as the camera.

Torch will work if Camera is not launched at all.

If the Google Camera app is downloaded, installed and launched, the stock Camera app will properly launch and work until the next reboot, even if the Google Camera app is closed.

At this point, within the stock Camera app, if the mode is set to Video instead of Picture (the default), the Camera app will launch successfully even after a reboot. After launched, it can go back into the Picture mode no problem. So in other words, launching the Camera app in the Picture mode will freeze the camera and the flashlight until reboot.

This is very weird and I couldn't pin it down. The dmesg dump of the stock Camera app: http://pastebin.com/xPDYRG4X

dmesg dump of the Android Camera app: http://pastebin.com/WaqxQA5E

As you see, they are nearly exactly the same.

It could be a permission issue, a driver issue, a kernel module that's loaded on-demand, I have no idea at this point. I need help. Do any of you guys have any insight as to why this might be the issue?

Update: I tried the first ~10 camera apps in the market and ALL of them work perfectly fine. I think CM camera app is to blame here. Is anyone aware of such a thing on other devices?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Pazzu510:
I love you, where is your donation button , Sir? I dont use the camera and i can stand the sleep of death(although i know it can be fixed) but you have done something really important, with cm on p600 it is much more possible to be supported as a legacy device on many roms instead of only waiting for samsung and roms based on samsung software. Omnirom, PARom, Aopk are just a compile away with something like p600 working. Congratulations, and i still want to see your donate button. :)
[Galaxy Note 10.1 (2014 Edition) Android Developmen] cristighenea:
Thank you!

I replaced the camera app with Google Camera, in recovery, and it seems there are no more problems with it.

Is there any way to make the pen work?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Gandalf:
Make sure you are using CAF-NEW for the audio,media, and display HALs. Also, make sure that you have the proper commits in the kernel to coincide with the caf-new hals.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Pazzu510:
Got the lt03wifiue instead of lt03wifi problem.

I cant flash the recovery that you compiled. It says that md5 does not match on odin 3.07. any suggestions?

installed PhilZ Touch, supposedly based on cwm and still got the lt03wifieu name problem.

Can i change lt03wifieu to lt03wifi flashing a samsung rom from sammobil?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] equilibriumtr:
Well, I did flash the recovery I uploaded with Odin 3.09 and I didn't try Odin 3.07 so there might be a problem there. I think the device name should be lt03wifixx in one place and lt03wifi in another. I'll check this out along with the HAL issue tomorrow.

Yes, I forgot to test the pen and it doesn't work at all. Adding it to the list.

Thank you for your kindness, but I don't think I really deserve a donation here, all I did was adjust the obvious parameters in a ready-made source :)
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Pazzu510:
META-INF>com>google>android>updater-script

For its to work i deleted the first line that says:

After that and a data wipe on TWRP the installation went smooth. This will let you to flash the rom and also install cwm recovery that comes with CM roms so you can say bye to TWRP; from then, the "lt03wifieu" is not a problem for me on cwm as [MENTION=3551932]equilibriumtr[/MENTION] said. I can now flash the zip with the lines that didnt let me before.

I think we could recover the lost security from deleting that line by adding something like this:

Can someone please add the lines instead of deleting them first and try flashing? Since with CWM i dont get the "lt03wifi is not lt03wifiue" error so I dont know if my theory is correct.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] zeosson:
Will be testing

Thank you for porting cyanogenmod to our tablet. I will be testing it and report anything that goes wrong.:)
[Galaxy Note 10.1 (2014 Edition) Android Developmen] r4yN:
Does ART work or Dalvik only? 'cause AFAIK you can't select ART in the official Samsung firmware...

Also the Exynos 3 cm port reportedly has got the S Pen working (without samsung's s pen functionalities of course), so you might want to take a look at their sources / repos?

PS: Keep up the good work, having a fully functional cm rom one day would be amazing :fingers-crossed:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] equilibriumtr:
By the way, I always had a working pen in my Note II LTE, even back when only cm 10.2 was available. But I'll look at the pen functionality soon because we will be needing it ourselves.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] equilibriumtr:
I looked at the device name issue, rebuilt the source and I got exact same build.prop with the original Samsung ROM:

ro.product.name=lt03wifixx #This changed
ro.product.device=lt03wifi
ro.build.product=lt03wifi

It's basically TWRP's fault for mixing up SM-P601 (lt03wifiue) and SM-P600 (lt03wifi), it should be fixed on their side. I couldn't try philz touch because goo.im was down. For now, try to use my recovery.

I also tried flashing the recovery I provided with Odin 3.07, it works. Something might be wrong on your side.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] equilibriumtr:
I don't think Qualcomm hardware applies here, lt03wifi is Exynos-based.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] ollimi1:
:D:D:D

Good to see that someone finally directed his attention to CM11 for our P600.

Waiting a long time for a working CM11.

Keep up the good work!!:good:
[Galaxy Note 10.1 (2014 Edition) Android Developmen] lewmur:
If I'm not mistaken, the difference between Tab models and Note models is that the Tabs don't have an S-Pen. So it's not surprising the S-Pen doesn't work when using a Tab ROM.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] hitman1376:
Hi ...

Dear friend , is this ROM stable for Daily Use ? ( I were porting Ubuntu phone based on TW ROMs but as you made this ... it can have a better base ) ... also , do you know how is the RAM used in this ROM ? ( how much free ? )

With best Wishes

HItman1376​
[Galaxy Note 10.1 (2014 Edition) Android Developmen] r4yN:
Slow down there, mate - you can't expect a fully stable "Daily-use ready" Rom after just one day ;)

This is still in early testing...and I doubt you can call it "stable" when there is a sleep of death problem
[Galaxy Note 10.1 (2014 Edition) Android Developmen] hitman1376:
thanks ...

Thanks for the Fast response Dear friend ... Well, if the sleep of dead is all , you can get rid of it by increasing the Min CPU Freq using any CPU manager app ... can you tell me about the RAM ? ( we have RAM management problem in UP so we need some more free RAM comparing with TW ROMs ) ... Thanks in advance

With Best Wishes

Hitman1376​
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Stevethegreat:
First off thanks for the port. I find stock android roms the best to run Linux on so if you could release a separate kernel with Virtual Terminal enabled (VT_config) it would be great.

As expected the rom only has the barebones on it and seems far more lightweight than even the most debloated rom. Merely not running the Samsung frameworks does wonders me thinks...
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Pazzu510:
Ram is good, running some apps and got 1.5 free. I got rid of the sleep of dead(or at least havent expirienced it) increasing minimum from 250 to 300 and got awesome battery decreasing maximum from 1.9 to 1.5. Everything silky smooth and no force closes or ui crashes.

Your thinking is right, sams framework handicaps this awesome hardware and occupies a about 500mb more ram than it needs to(average from experience from 1.9gb-2.3gb on tw to 1.2gb-1.4gb in cm).
[Galaxy Note 10.1 (2014 Edition) Android Developmen] meirg:
Thank you very much!! I've been waiting for this since I got this tablet. I look forward to trying it out this weekend.

Keep up the great work!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Smac7:
this is awesome. I'll jump on it as soon as the pen starts working. How is the stability aside from the camera issue?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Shawn5162:
Odin 3.09

hi everyone....

i am very interested in installing this ROM. I tried to install the dev's recovery through odin 3.07 and it didn't work. Could someone please post a link or make a backup they could share of odin 3.09. thanx.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Aletheia:
Thanks!

This is truly awesome... CM/AOSP just feels so much smoother and once the pen is working this will be close to perfect.

I had the same problem flashing this ROM (md5 fails with your recovery, odin 3.09) as mentioned before and had to remove that line of code. I've got the "sleep of death" a few times even though I haven't touched governors. It also seems to have a the same wake delay as Sammy stock but I guess that's on the soc. Other then that (and the issues you listed), perfect.

[MENTION=5323673]Shawn5162[/MENTION]

Just follow Pazzu510 advice on page one (you don't NEED to ad that second line of code though). I.e, remove code, wipe data and flash with twrp.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] lewmur:
I got the same error trying to flash the recovery with Odin 3.09. Downloaded the recovery from a different mirror and it still won't install.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] mising:
Which gapps are you all using? Never mind, PA gapps work great.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] hitman1376:
Dear friends ... can anyone give me the Updater-Script ?

Dear friends ... can any of you give me the Update script of the ROM so that I can edit it for all ? ( then you should have no problem flashing it using TWRP using the edited ) ... here's where you can get it :

1 - extract the zip ROM

2 - go to the address : META-INF > com > google > android

3 - give me the " Updater-script " so that i Edit it for all users ... Thanks is advance

With Best Wishes

Hitman1376​
[Galaxy Note 10.1 (2014 Edition) Android Developmen] mohamadreza33:
what about P601 version?

will this work on P601 version?? :confused:

P601 da chalishior mu??
[Galaxy Note 10.1 (2014 Edition) Android Developmen] hitman1376:
Yes Man ... It sure Does ...
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Aletheia:
[MENTION=5052547]hitman1376[/MENTION]

Here ya go. (just remove the .zip)
[Galaxy Note 10.1 (2014 Edition) Android Developmen] hitman1376:
Here Is the Edited Updater Script ... ( For Guys who Want to Flash in TWRP )

Alright Dear friends ... Here is the Updater Script which is Edited to be able to flash this Great ROM on TWRP ... So Just Extract the Zip and Replace the " Updater-Script " in the address ( in extracted ROM zip ) " META-inf > com > google > android " and Re compress the ROM and try flashing it using TWRP ... I think it should work Now ... Thanks [MENTION=1176416]Aletheia[/MENTION] for providing me the File ... Please inform me if it's OK now or not ... Thanks in advance

With Best Wishes

Hitman1376​
[Galaxy Note 10.1 (2014 Edition) Android Developmen] benjamimgois:
Thanks !

O man, i was waiting for this day since i bought this tablet. Thankyou so much for the effort ! I have a P601, but will install the p600 ROM as soon as i can. Any comments about the battery life on this rom ?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] lewmur:
With my Linux Mint 17 box, I just edited the script within the zip, without extracting it, and it automatically updated the zip file. Flashed from TWRP, and booted with no problems. Had to also flash latest GAPPS. Currently restoring my apps from Google Play Store.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] equilibriumtr:
OK, time for some updates:

Pen works, without the fancy Samsung menus of course :)

Menu softkey is fixed, it is not recognized as recent softkey anymore.

Battery life is not good as far as I tested, could be because of not being able to enter deep sleep. Because of this, it drains (much) more battery when turned off compared to the Samsung 4.4.2 ROM. I would be glad if you guys could also test this. In a period of 10 hours, I saw about 20% drain in CM vs. 4% drain in Samsung's 4.4.2 ROM.

Answers to some questions and issues:

What's up with the recovery md5 issue? The most recent recovery is not md5 hashed so it should be OK everywhere.

Is the ROM good enough for daily use? Probably not until the battery issue is resolved, it will only last a couple of days even if turned off at this discharge rate.

How is RAM doing? Pretty good actually, probably the only performance metric that's actually better than Samsung's ROM. About 500M more free space when idle.

Will it work on P601? Everything but GSM will probably work. I don't have the device so I can't test it.

Will it be official in the future? If the CM devs pick this device up, yes. But if they don't, I won't commit myself as the maintainer of this device, so it won't go official and won't be maintained.

What's next?

Try to improve battery life (this will be a low priority job as I'm not using this in my daily life but as a development device)

Try to improve CPU performance:

Try to compile kernel with NEON

Try to compile kernel with other optimizations

Maybe turn on overclocking up to 2100MHz

etc.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] C2Q:
Omg thanks a bunch!

How exactly do I flash this with the updater script? And which Gapps do you use?

Thanks!
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Smac7:
Is this fix still needed even after the latest update?
[Galaxy Note 10.1 (2014 Edition) Android Developmen] lewmur:
Unless you install the OP's recovery, then, yes, it is required.

---------- Post added at 12:23 PM ---------- Previous post was at 12:08 PM ----------

I use MagicJack voip service and when I installed it, it gave me a message that Google Play Services needed to be updated in order to improve battery life. Could this be the problem? I updated but haven't had time to check if battery life improved while tab is in sleep mode.
[Galaxy Note 10.1 (2014 Edition) Android Developmen] detrexer:
**** yeah thanks op! Finally we get to remove all the samsung crap
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Aletheia:
I must say I haven't noticed the battery being any worse then on stock. Admittedly I haven't really focused on that but I think I only lost 5-6% over the night. Got a weird drainage when browsing a gif heavy site with chrome though, but that's all.

Daily driver for me now that the pens working. :)
[Galaxy Note 10.1 (2014 Edition) Android Developmen] Shawn5162:
Hi....

What application did u use use to port this rom (android kitchen, archikitchen, ricky's rom kitchen, etc. I am looking into porting the L preview for this device

Thanks