yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Easy_as_Pi_3.14:
You need to flash stock GApps. Dunno why, but for some reason it just works.

And with the repartition, you have more than enough space for that.

By the way, the Settings FCs are from a bad update. Flash 12/6 and you're good.
[X Style (Pure) Q&A, Help & Troubleshooting] Donkan694:
somebody know if i can install the firmware of the moto x style on a pure edition?
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
Computerfreek274 Stock Android KK 4.4.4 ROM​

This is a flashable ROM with twrp. I will not be updating or supporting this ROM.​

Please Read: If somehow this ROM or any of it's software kills your phone I am in no way to be help responsible for it or any data loss backup your data.

Based on the last STOCK .4.4.4 There was before lollipop.

Tether/Hotspot

Root

Deodexed

No Bloatware

No Tweaks or any other mods have been done.

Download Here

You must update/Downgrade radio.

fastboot flash radio radio.img or you can go to install under twrp and switch it to .img and flash the radio.img that way.​

Download Radio.img here​

Please remember I will not support or help in anyway with this ROM me and my son just putting it out there in case someone like to play around with a KK ROM that is deodexed and can be themed. This ROM has been tested and it boots up with no boot animation. Also after it boots you will get a msg that Motorola software will ask you to to downgrade sensor firmware will be removed/Downgraded.

I will keep this forum open for users to use. I may pop in from time to time. Please remember no PM's about this ROM I will not give support for this ROM I am way to busy to give support for this.

​
[Verizon Motorola Droid Turbo Android Development] mikelikesbikes:
Tried flashing this last night. went fine, but WiFi will not stay on. 4g works fine though. It turns on, but right back off. If I remember correctly this is something with radio, since I am downgrading? Google didn't have any answers that I could find. Anyone care to chime in?
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
Yeah sorry I forgot you do need to downgrade radio. I think firstEncounter had and still may have his radios for KK up. If not I will try and get a KK radio .img pack up soon.
[Verizon Motorola Droid Turbo Android Development] mikelikesbikes:
Have been looking through his threads, but I couldn't find the radios for KK. Entirely possible I looked at them and didn't see them however.
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
Yeah sorry been crazy busy! I will try and get them to you asap. Thing you just need the radio. You can just download a stock 4.4.4 unzip it and grab the radio.img out of it.
[Verizon Motorola Droid Turbo Android Development] mikelikesbikes:
No need to apologize. Is it as simple as flash rom then fastboot KK radio image (or possibly Flashify)?
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
Twrp under install you can switch it from zip to img and flash .img also.
[Verizon Motorola Droid Turbo Android Development] mikelikesbikes:
Having trouble finding the KK modem. Would downloading stock KK firmware from Motorola then extracting the modem be something you would suggest? If KK firmware is still available. Just prefer the looks of KK over LP.
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
Download this unzip and flash radio only with fastboot or twrp https://mega.nz/#!wU8DlLxK!sETqKOrPY33XDWdDLj5XA8_R-f9m3u3rlFA7z_N9-BE
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
I updated OP I put the radio.img up for downloads. I tested this last night and seems to be working just fine.

Give it five more minutes to upload.
[Verizon Motorola Droid Turbo Android Development] Qutayba Khader:
Which one has the best battery life in

kitkat rom Or LP rom ??
[Verizon Motorola Droid Turbo Android Development] mikelikesbikes:
I found what was labeled as Droid Turbo stock KK firmware the other day online. I flashed your KK ROM and I extracted the radio.img from the KK firmware I downloaded and flashed it using Flashify. Decided to reboot before I checked WiFi and all I had was bootloader when it rebooted. Had to unbrick and start over. Been away from home and my laptop for the holidays so I will give your method a go when I get home. Thanks.
[Verizon Motorola Droid Turbo Android Development] mikelikesbikes:
They're both great, I just prefer the looks of KK.
[Verizon Motorola Droid Turbo Android Development] mikelikesbikes:
I tried to flash radio.img in TWRP and I get the option "boot" or "recovery". Both of which fail to flash. So not sure what to do.
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
Then use "fastboot flash radio radio.img" from bootloader.
[Verizon Motorola Droid Turbo Android Development] iceblitz4:
on 4.4.4 now thanks for the ROM dude much appericated but now when i go in bootloader baseband it shows nothing is this normal? i already flashed the radios..
[Verizon Motorola Droid Turbo Android Development] decimeter:
Where can we find the newer radio to flash if we want to go back to 5.1?
[Verizon Motorola Droid Turbo Android Development] munchy_cool:
http://xdaforums.com/droid-turbo/development/droid-turbo-xt1254-bootloader-radio-t3259327
[Verizon Motorola Droid Turbo Android Development] decimeter:
Thank you!
[Verizon Motorola Droid Turbo Android Development] iceblitz4:
How would we add a boot animation?
[Verizon Motorola Droid Turbo Android Development] M.Nabeel:
You can try liveboot from playstore, that's the only one working
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
Any of them from here will work. http://xdaforums.com/moto-x/themes-apps/bootanimation-share-custom-t2959698
[Verizon Motorola Droid Turbo Android Development] iceblitz4:
for some reason when i flashed it it booted up but it didnt fit the screen..?
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
Most of them work if you search around you will find 100+ that will work. Or try live boot from Google play. You can also copy your own to /system/media there just is so many out there.

I remove then as they just slow down booting I do this on all my roms. The one you see is just part of any Android booting without one.

Try this one here I used it before and fits just fine.
[Android Q&A, Help & Troubleshooting] FireLord:
Credits

First of all this is not your tree.. This my tree... And secondly how you completed the build? With cortex a5 value in android 6.0? Unbelievable man..

And for kernel add custom tool chain value you are using 4.8 tool chain i guess

Confirm me by flashing the rom again and follow this

adb devices

adb shell

cd /proc

cat version

And paste the line here..

my boardconifg.mk

https://github.com/FireLord1/android_device_samsung_logan2g/blob/master/BoardConfig.mk

identical

https://github.com/FireLord1/android_device_samsung_logan2g (full source)
[Nexus 6P Q&A, Help & Troubleshooting] GuestK00194:
Hi xda community,

I have always sideloaded the OTA in recovery using a Windows machine. Yesterday, I tried to use my Chromebook running Ubuntu. I can see my device when Android is up and running (meaning Android is running and not in recovery or bootloader) by typing "adb device" using the terminal within Ubuntu. The problem I'm having is not being able to see my device when in Recovery mode and selecting the sideload adb mode.

$adb devices

List of devices attached

<---------this line is blank

$adb sideload update.zip

error: device not found

I've made sure /etc/udev/rules.d/51-android.rules are configured. I also checked the post regarding .android/adb_usb.ini but this is only for the Nook and should not apply to the Nexus 6P.

I also tried adb kill-server and adb start-server with no luck.

I've read post about being able to see the device in fastboot. I tried this as well and can't see the device either. My device does not have an unlocked bootloader but this should not matter. The device doesn't need to be for a sideload. This worked in Windows with no issues. You might ask, what is the problem then? I just want it to work in Ubuntu.

Does anyone have any suggestions on how I can fix this?

Thank you in advance for just reading.
[Nexus 6P Q&A, Help & Troubleshooting] GuestK00194:
After some more searching I found a suggestion to run the following command and it fixed my problem:

/etc/init.d/udev restart

http://android.stackexchange.com/questions/58187/adb-can-discover-devices-but-not-fastboot

My Acer Chromebook 11 only has two ports: 2.0 and 3.0 USB. I noticed the device would not show up after typing in "lsusb" which would normally show the Google device. I unpluged the USB cord from the 2.0 and plugged it into the 3.0. I read another post online stating this sometimes causes the problem.

When in fastboot I can type "fastboot devices" and "adb devices" in recovery and my device now shows up.

I hope this helps someone. Thank you all.

Mods feel free to close out this thread.
[Huawei Watch] zumstin:
Is anyone else having a delay in phone notification? By the time my watch starts vibrating to notify me of a phonecall I have already missed the call on my phone. That's irritating. One of the reasons I got the watch was to let me know when my phone starts ringing. My emails and texts seem to be notifying me just fine. It's just the phone notification.

Ideas?
[Huawei Watch] foo:
I have only a small delay like 0,5s. So I think this is not normal. Are you connected by bluetooth or maybe by wifi?
[Huawei Watch] zumstin:
I'm connected by BT. Like i mentioned all of my other notifications are working just fine. It's just the phone notification. I wiped my watch and reloaded everything so i am waiting to see if that fixed anything.
[Huawei Watch] zumstin:
Update: It did not work. Sigh...
[Huawei Watch] kellybrf:
I have this at times, though not always. I also get it where after I answer the call it continues to vibrate on my watch. hangouts messages do take a few seconds to push to the watch though. that said, this behavior has been consistent with my zenwatch, smartwatch 3 and my hwatch so I think it's just inherent in the platform
[Huawei Watch] Scott:
Same here.

I just tested a call and it was about .5 to 1.0 seconds which is considered very good by my taste. But I did notice SMS and Hangouts does take a few seconds.

Maybe they set the priority like that on purpose.
[Huawei Watch] Ossaratam:
Same problem for me...

I am experiencing the same exact problem with my Nexus 6P - no amount of resetting seems to have fixed the problem. This has been extremely frustrating.
[Huawei Watch] uniqueflips:
Anyone else figure this out without having to warranty the watch. Mine is a good 3 seconds behind with a Nexus 6. The call can go to voicemail before the watch vibrates.
[Huawei Watch] zumstin:
I'm hoping with the new update to Wear announced today that it will fix the delay. Hoping....
[Huawei Watch] kellybrf:
it has nothing to do with the watch, I've got a sw3 as well that behaves the same with my 6p. previously I had a zenwatch, and it had the same delay with my n6 and later the 6p
[Huawei Watch] kpjimmy:
I believe it's the android wear app itself. If you can find the AW 1.3 apk from apkmirror or the like, you should see a difference. Hopefully the new OS update will help alleviate the issue.
[Huawei Watch] thomascook:
Same here with HW Watch Active. Phone get instant Message since Doze Settings on Marshmallow were edited, Watch still delayed... :(
[Huawei Watch] rimz808:
I am having problems as well. Sometimes I would get notifications on my watch, other times the notifications would be delayed. I just tried and I am not even getting calls to my watch. I had to perform a factory restart twice now in order to get it to work. Why is that? I have a Huawei watch sync with a Huawei Mate 9. I would figure they both should work seamlessly.

any advice would be appreciated
[Huawei Watch] Badelhas:
Did you find a solution? I am experiencing the same issue, the incoming calls are not working and I also cant therefore receive calls directly on the watch. I am using an updated Huawei Watch with the HTC One M8, which is also updated to Android 6.0, with the latest version of Android Wear.

Cheers
[Huawei Watch] rimz808:
The incoming calls seem to have fixed itself. However, what really solved the issue was that I had to make sure, on my Huawei phone, Android wear was set to close after the screen lock. I made sure that Android wear was always running in the background. Not sure if there is a similar setting on the HTC One M8, but making sure android wear was not in any power saving mode solved the problem for me.

Hope it help,
[Huawei Watch] Badelhas:
I fixed the issue with a "wipe partition cache" procedure. Thanks :)
[AT&T LG G4] cmlucht:
Ok i have found 2 links for the rooted image file i have downloaded both but phone wont root and when i try to open the image on the computer it says corrupt.

I have tried downloading from both links and every time its image corrupt.

Does anyone have a good link or suggestions?
[AT&T LG G4] cmlucht:
Bump
[AT&T LG G4] faizalotai:
Can you post that link, seems there's no one facing that issue so far..
[AT&T LG G4] cmlucht:
Got it herehttp://xdaforums.com/att-g4/help/root-h81010o-t3252902
[AT&T LG G4] faizalotai:
I got root from the same link and no problem for me..try download using internet download manager
[AT&T LG G4] cmlucht:
Will do do you have a link to the instructions you followed?

Mine would not flash than it soft bricked so i used tot to restore
[AT&T LG G4] faizalotai:
If you're already have an image, you can try open it with this

Download it and try open the image, its for extracting the image file..

if success than maybe your method of rooting is the problem..

make sure to activate the ports 1st by double click ports windows batch file..

than copy and paste this code

1. Send_Command.exe \\.\COM4

2. id

3. dd if=/data/media/0/system.img bs=8192 seek=65536 count=579584 of=/dev/block/mmcblk0 ([B]i'm setting my image as system, system.img[/B])

4. LEAVE

those command after #
[AT&T LG G4] cmlucht:
I re downloaded the image and checked it with ext2explore.

well this time around it worked great now have root.

thank you much.

I have been rooting and twrp / cmw for years and this is the only phone I have ever had any problems with.
[MDA III, XDA III, PDA2k, 9090 General] ppchkn:
Just like the title means... i have a killer question

My little brother has a Cingular 8125, here are the aspects:

(WM5)

cpu : OMAP8590

speed : 195 mghz

ram: 64 MB

flash size: 128 MB

flash chip type: m-systems

bus: 16 bits

Storage size: 42 MB

mine are on a O2 xda iis (blue angel)

(WM6)

cpu: intel (r) PXA263

speed: 400 mghz

ram size 128 MB

flash size 32 MB

flash chip type: 28F128K3

bus: 32 bits

Storage size: 60 MB

both with 230 x 320 lcd screens with 65536 colors.

I just have moved (after reading A LOT!) to windows mobile 6.... i grab his pda just to compare, and he has A LOT of speed than mine :confused: :confused: :confused:

It's because of the rom that i had installed? (it's the one with the sticky on the threads on WM6 around the corner in here)

or because the WM edition itself :confused:

In advanced, thanxs, its a big big thing because if i am right, i had at least the double that he has, so, all of this is not right... right????
[MDA III, XDA III, PDA2k, 9090 General] cyberjak:
I think you will find that some of it is the rom. The blue Angel was originally as you know released with WM2003 if not WM2003SE

which was optimised by both the manufacture and the carrier of the network. These roms are made by very experienced rom cookers/developers but they are working withexisting material not rewriting code from scratch.

Also I've even noticed that my BA slowed down it's boot up time substantially from wm2003se now that it's running wm6. as well some things appear to take a bit longer. your relative's rom is likely to be the original unchanged rom and is optimised for the device it's loaded on. there are tweaks to help with the diffrence even then. but just like pc's the newer is not always faster on the same hardware.
[MDA III, XDA III, PDA2k, 9090 General] Wexx:
The main problem with Blue Angel is it's very slow flash memory. Even it's own SD slot with today's cards is a lot faster. On WM2003/SE that wasn't a problem because of flash memory was used only for backup purposes while in WM5/6 the whole system runs from it.

BTW: I think there exist original WM5 ROM for Blue Angel which was made by HTC for one of the operators (who leaked it) and it is therefore optimised greatly.
[MDA III, XDA III, PDA2k, 9090 General] SilverIce:
That's odd, the bootup did takes sometime but the overall is certainly great even testing it with WM5. Is it just me or everyone else ? So far, I kinda like it, the loading speed from SD card somehow it's slowed down for some unknown reasons but overall it works great.

Maybe we should give Helmi & Xplode sometime to find a way to optimise the WM6, I believe they can do it, after all they are the genius who made and cooked the WM6 rom.
[MDA III, XDA III, PDA2k, 9090 General] hatoncat:
Couple things here. First, many think that the TI OMAP in Wizard is slower than the XScale in Blue Angel. It's not... that's simply the Megahertz Myth™

Note: The Megahertz Myth is a registered trademark of Apple. :)

Anyways, the Wizard is a faster, more modern device, that has been optimized for Windows Mobile 5.

The HTC drivers that were used for WM5/WM6 on Blue Angel are very poor quality... they were never meant to have the OS store files in ROM, rather than in RAM. In short, HTC never optimized the drivers Blue Angel for WM5/WM6, which is why it runs slower.

As experienced as helmi_c, xplode, and others are at this, HTC still holds the keys to their drivers, and the amount of modification anyone outside of HTC can do to them is limited.
[MDA III, XDA III, PDA2k, 9090 General] flyboy_____:
HTC should free up BA drivers for editing.

If they discontinued BA and do not give support, then give the tools to the costumers so that we can finish their work.

BA as great hardware it only needs good drivers, because Windows Mobile is handeled great by xda-developers team!
[MDA III, XDA III, PDA2k, 9090 General] Rudegar:
i dont believe htc write most the drivers

most of them would be included in the oem stuff they get

like the screen or bluetooth chip and the likes

in which case they could get in trouble if they did

even if they had access to the sourcecode of the drivers

they might not
[MDA III, XDA III, PDA2k, 9090 General] Wexx:
Of course Wizard is faster for most tasks. It is because of it's all-in-one design. But when comparing the CPUs RAW power, the Blue Angel is even stronger than contemporary devices like Hermes. This is however visible only when using heavy games or multitasking so it is not a major advantage for most of us. BTW: The OMAP CPU used in many devices today was not originaly made for WM5, it was first used on Smarthpone platform back in 2003 days. Even old Motorola MPx200 (Smartphone 2002) has OMAP with very similiar design to OMAP 850 in Wizard.

In WM5/WM6 for Blue Angel the slow flash memory is compensated by using more paging memory then in other devices. This is why the device seems to respond quickly but it is not perfect.

Personally, I would prefer having Wizard over Blue Angel because of it's more power efficient design. But it has poor ergonomics and one-handed navigation / text entry is impossible. Therefore I have chosen Blue Angel.

HTC releaing scources to their drivers? That is only a dream. And I think the license agreements with makers of parts do not allow this.
[MDA III, XDA III, PDA2k, 9090 General] LandRaider:
I bet if someone were to get friendly with a person working at HTC, We could get some BA stuff from them. It's not like they stand to lose a bunch of $ for it.
[Galaxy Tab 4 General] mac231us:
Got xposed working too wanam arm (32) v78.1 sdk22
[Galaxy Tab 4 General] rheckr:
[MENTION=3105136]mac231us[/MENTION]

Doesnt work for me. Did everything as your thread guides but i still can't get the SU permissions.

Enabling SuperSU gives me the note "There is no SU binary installed[...]"

Any idea what i did wrong?

1. Flashed to 5.1.1 from CM12.1 and didn't boot

2. Flashed TWRP and booted directly to recovery

3. Flashed BETA-SuperSU-v2.62-20151210170034 and reboot

4. Got SuperSU app installed but it don't let me launch it (not installed binaries)
[Galaxy Tab 4 General] mac231us:
that is odd..i just did a fresh install..wiped fully formatted...went to download (do NOT install SU as twrp prompts) odin flashed the 5.1.1 (nordic)...in fact this time even rebooted and set up google account..then went back to download...installed twrp again...again rebooted but this time straight to twrp...then installed the latest su 2.62-3...rebooted (again do not check the SU install prompted by TWRP)...and the su app was there..and so was the binary

noticed chainfire now has BETA-SuperSU-v2.64-20151220185127.zip

curious did you do a 5.1.1 odin flash from cm12.1 or a twrp nandroid recovery...just wondering if it makes a difference

twrp is from here

http://xdaforums.com/tab-4/general/sm-t235-lte-rooted-twrp-2-8-alpha1-sm-t3027059

again...am only speaking of the T235 (or T235Y) not any other variant

the 5.1.1 I used is from here

https://www.androidfilehost.com/?fid=24052804347821380

in order to prevent stock recovery from coming up always first go to download step (not actual download) but using the volume down, power and home to get to the choice of download and reboot..then reboot but quickly go to volume up home and power to get to the twrp recovery
[Galaxy Tab 4 General] rheckr:
[MENTION=3105136]mac231us[/MENTION]

Aww, i cant get it working..

Did exactly what you said:

1. Format everything from TWRP (5.1.1 rom)

2. Flash 5.1.1 (nordic)

3. Configure google account

4. Back to download and flash TWRP

5. Back straight from download to recovery

6. Flash 2.62-3 and reboot (didnt checked the SU install prompted by TWRP)

7. When i open SuperSU app i am getting exactly:

Btw. i am getting red and blue text when booting - Kernel is not seandroid enforcing.

Galaxy Tab 4 7.0 LTE (SM-T235)
[Galaxy Tab 4 General] mac231us:
EDIT...also

cannot think of anything else at the moment except that am using older version of odin v 1.85 (i too get the red and blue text..the recovery is not default as simply rebooting to recovery takes one to the stock unless doing the 3button to download to recovery process to get to twrp)

try it again w odin 1.85 and maybe go back to the way I 'instructed' the first time (where I did not set up the rom at all and went back to straight to twrp and flashed supersu...formatting internal storage is important but think you are doing that already)

you may want to ask some of the other folks who also got root

though imo there were no explicit instructions but enough for me to go on with..here....

http://xdaforums.com/tab-4/general/sm-t235-lte-rooted-twrp-2-8-alpha1-sm-t3027059/page15

except for K94U's post here which was very informative

http://xdaforums.com/showpost.php?p=64182938&postcount=15

and

http://xdaforums.com/tab-4/general/to-root-samsung-galaxy-tab-4-t3264281/post64216314#post64216314

EDIT another thought i may have done this at some point do not recall (but not today for example on this new installation) is to format the internal card using the stock recovery itself after installation of the odin-rom

then do the other steps of twrp etc from download mode again
[Galaxy Tab 4 General] rheckr:
[MENTION=3105136]mac231us[/MENTION]

Giving up and waiting for CM13.

I've did everything exactly how it should be done and SuperSU is showing information about mising SU binary.

Tried every SuperSU zips from Chainfire but effect was the same every time even with fresh flash of nordic rom and recovery. Ive tried cleaning data through stock recovery but it didnt helped.

Thanks for trying.