yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy Note 3] Enso.Xv:
Hi.

So just recently I allowed the newest update to download on my phone....

and since then my Note 3 has been randomly freezing and rebooting, sometimes making odd noises when the screen is off...

Anyway, I just got this new Sony Vaio laptop with NFC beam on it and decided to try it with my phone. Now mind you, I have NFC turned ON on my phone and I know how to use the beam with both devices. Now, when I try to beam a picture or website to my phone from my laptop I get up to the point where my phone says to "now bring devices back together" but after I do that all I get is the little noise that basically indicates that the data is supposed to be transferred...but instead it keeps sporadically beeping. Does anyone have any idea how to solve this? I just recently did a complete factory reset, pulled the battery, restarted and everything. Nothing has worked.
[Sprint Samsung Galaxy Note 3] DevilDog512:
Are you referring to the 4.4.2 update or has there been another?
[Sprint Samsung Galaxy Note 3] Enso.Xv:
4.4.2

I was late to update.
[Sprint Samsung Galaxy Note 3] DevilDog512:
Hmm. I would try flashing one of the stock tars available in Odin. Make sure to remove your extsdcard and be aware it erases internal storage if you do. But sounds like you got a bad download. Or try with kies or something. The stock tars in Odin won't trip Knox.
[Sprint Samsung Galaxy Note 3] micmars:
This is exactly right...start by going back to completely stock. That'll get him back to a very good place...

After that, we will see if that fixes the biggest problems described (ie, phone not working). He can down the line worry about the the file sharing issue

Sent from my SM-N900P using Xparent BlueTapatalk 2
[Sprint Samsung Galaxy Note 3] DevilDog512:
Exactly. The whole phone making weird noises when screen is off would have been it for me. Lol. That can't be good.
[JAMin, XDA Neo, S200 General] laleyandasvivenporsiempre:
i am on the pc for 8-10 hours to solve the problm on this ****ing s200, after a hard reset the device start to work well , but when i ll do a soft reset it could not establish a connection with the pc again moreover "error opening the shortcut or locating the target filename" is shown when i click the comm manager button. i assume that it may be a problem because of the rom version, although i search all the forum and some other sources i cant find a s200 rom which is working, finally i installed the altest version of 818 pro 2.15.13.27 which i founded in the forum. then when i install some software and make a soft reset the device refuse to open and the calibration screen is shown. i dont know what is happened but i am sure that there are some hardware problem. i dont know if somebody else have this kind of problem?? i have also a jamin and it works perfectly with its latest rom. finally give a few dollars more and buy jamin if you really want to use those htc staff...

ps: I am not sure but maybe if s200 ROM will be installed the problem is solved but it refused to install an older rom , now all the soft reset cause the setup screen of windows!!! :( :(
[HTC Droid DNA] 24ky:
This is a port of a features from lyapota's modPack5 from the One X.

All credit goes to its original author.

This Mod is A Port From The

HTC One

To The

HTC Droid DNA

. So If Some Thing Doesnt Work Please Let Me Know, This Will Work On All Sense KitKat Roms Except ViperDNA

Images

ChangeLog

MusicBox Ver 1.0

*Fixed Music app FC when opening sound enhancer. Thanks 2 @V6-Maniac for pointing this out.

*One more try to fix "endless FC"

*Beats now has to be ON before flashing.

Download

DevDB - HERE MD5 556af535b7739fb6eaa3f99342016c52

Terms of Use

modPack is completely free software. You can flash it, decompile, build into ROMs, or use parts of it on your decision all i ask is credits. As any custom software made in free time, it can contain bugs. After flashing zip file you can get bootloop or hanging your device if your ROM does not meet the requirements.

XDA:DevDB Information

MusicBox, a ROM for the HTC Droid DNA

Contributors

24ky

ROM OS Version: 4.4.x KitKat

ROM Firmware Required: Any Sense KitKat 4.19 Rom, Except ViperDNA

Version Information

Status: Stable

Current Stable Version: v1.0

Stable Release Date: 2014-03-14

Created 2014-03-14

Last Updated 2014-03-14
[HTC Droid DNA] nitsuj17:
since its advertised as compatible with "all sense kitkat roms" please mention that is NOT compatible with viperDNA kitkat

we already have a version of music box in our roms and at best this would break certain tweaks if not bootloop
[HTC Droid DNA] 24ky:
Will do, sorry about that.
[HTC Droid DNA] agsalman:
thanks for all works.

your kickdroid v2.0 was perfect for gsm range.i think that's mod work great too.
[HTC Droid DNA] mike_augie:
it boot loops ... verified ... :eek: wish I would have seen your post earlier ,,,
[HTC Droid DNA] 24ky:
Yeah that's my fault for not saying " doesn't work on viperDNA ". Sorry bout that.
[HTC Droid DNA] theseabass:
What's the advantages of this compared to Viper4Android? I'm all for better sound, I'm just curious in the major differences.
[HTC Droid DNA] eriknors:
Or is it compatible with viper4android

sent from my DNA
[HTC Droid DNA] 24ky:
Can't answer what the advantages, because everyone has there opinions about things. MusicBox Is sound profiles for headsets

And not sure. I don't use viper4android
[HTC Droid DNA] theseabass:
Moo

Thanks for the response. I'll try it out.

---------EDIT--------

It will *NOT* work in Conjunction with Viper4Android. It's either one ore the other. They both rely on the Same .lib file, with different contents within the file.

----EDIT 2----

It does work. You just have to reinstall V4A's driver. My bad.
[HTC Droid DNA] 24ky:
Expect next update to fix

- Fixes SystemUI FC

- Fixes Phone FC

- Fixes Music FC

MusicBox Will Now Work On All 4.19 roms except viperDNA, Accidently Released The Buggy Version. Im Sorry Guys.
[HTC Droid DNA] theseabass:
Here's a bug for you. The settings don't disable when the headset is unplugged. Even though the app shows settings are unavailable without a headset, the settings are still in place. I discovered this with the SRS setting. I was trying to use my phone speaker and it was practically undistinguishable through the static. I plugged in my headset and dissabled audio effects and all is good.
[HTC Droid DNA] 24ky:
Music Box was ported from 4.2.2 source that lyapota left and it's been ported to 4.4.2 so it's came along way, expect bugs and what Rom are you using ?
[HTC Droid DNA] theseabass:
Santod's M8 4.4.2
[HTC Droid DNA] 24ky:
Note to users

If anyone has flashed this mod on a 4.19 and has little to no issues with musicbox please tell me what Rom your on. And if you had beats audio on or off before installation. Been trying to narrow out issues with it but can't get it to install on any Rom I try. And I forgot what Rom I had it on and working
[HTC Droid DNA] 24ky:
Okay so after numerous flashing ( kickdroidv3, v2, santods 4.19 musicbox wouldn't stop with force closed) ( sun_dream rom after smali edits I got it to work ) so after today I found out that musicbox will only work on my next release of Kickdroid. And if I can't fix for all other roms I will be removing this thread and making music box a kickdroid exclusive.
[HTC Droid DNA] rajkatiyar07:
Hay !

Hey ! will it work on HTC BUTTERFLY DLX1 ?
[AT&T Samsung Galaxy Note I717] hyelton:
So I was playing around with my old Note 1, its the AT&T Version I flashed a Jelly Bean Touchwiz rom via TWRP and all the sudden it said failed, SO I flashed back what was on there and TWRP froze on the screen I pulled the battery and NO life at all. Holding down power and vol down no Download mode either.
[AT&T Samsung Galaxy Note I717] 440bro:
Yup your in paperweight mode.

You can order a usb jig called jtag and it will force download mode.

Or you can send it to mobiletechvideos.com and they can revive it for you.
[AT&T Samsung Galaxy Note I717] hyelton:
Thats so odd, I`ve done all kinds of things to this thing and this not happen lol. I`ve even flashed N7005 modems with no issue. But I flash a ROM MEANT for the AT&T i717 and it screws up

Heck that website wants to charge $40 lol. If I needed a backup phone so badly I`d just buy a cheap Moto G
[Nexus 4 Q&A, Help & Troubleshooting] souleater11:
hello everyone,

is there an effective method to remove the cracked back glass without tearing/ damaging the back plastic cover ?
[Nexus 4 Q&A, Help & Troubleshooting] xSharpi:
A hairdryer to soften the adhesive then some scraper tool. I wouldn't want to cut my hand
[Dell Venue] social-design-concepts:
Downloads :

CLICK HERE DONATE NOW : AND MAKE MY LIFE EASIER BY HELPING BUY ME A VENUE 8

Stock Image Downloads

:

Note : do not extract the <file name>.system.img.gz contained with in the 7zip file .img.gz is the correct format for flashing through fastboot for intel. . .

Acer

A1-830_WW_GEN1 :

JB4.2.2 : ro.build.fingerprint=acer/a1-830_ww_gen1/ducati:4.2.2/JDQ39/eng.svnadmin.20140620.161423:user/release-keys

Acer_AV052_A1-830_1.014.00_WW_GEN1_FLASHPKG.7z

KK4.4.2 : ro.build.fingerprint=acer/a1-830_ww_gen1/ducati:4.4.2/KOT49H/241:user/release-keys

Acer_AV0K0_A1-830_1.006.00_WW_GEN1_FLASHPKG.7z

Dell

Venue 7 WiFi 3730 :

JB4.2.2 : ro.build.fingerprint=dell/Tablet7/thunderbird:4.2.2/JDQ39/eng.XYX.20131114.170109:user/release-keys

Venue_7_WiFi_JB4.2.2v1.42_FLASHPKG.7z

JB4.3 : ro.build.fingerprint=dell/Tablet7/thunderbird:4.3/JSS15Q/eng.XYX.20140226.114853:user/release-keys

Venue_7_WiFi_JB4.3v1.25_FLASHPKG.7z

KK4.4.2 : ro.build.fingerprint=dell/Tablet7/thunderbird:4.4.2/KOT49H/eng.build.2014062.120901:user/release-keys

Venue_7_WiFi_KK4.4.2v1.33_FLASHPKG.7z

Venue 7 HSPA+ 3730 :

JB4.3 : ro.build.fingerprint=dell/Tablet7/thunderbird:4.3/JSS15Q/eng.XYX.20140111.111157:user/release-keys

Venue_7_3G_JB4.3v1.22_FLASHPKG.7z

KK4.4.2 : ro.build.fingerprint=dell/Tablet7/thunderbird:4.4.2/KOT49H/eng.build.20140624.122423:user/release-keys

Venue_7_3G_KK4.4.2v1.33_FLASHPKG.7z

Venue 8 WiFi 3830 :

JB4.2.2 : ro.build.fingerprint=dell/Tablet8/yellowtail:4.2.2/JDQ39/eng.DYY.20131114.160805:user/release-keys

Venue_8_WiFi_JB4.2.2v1.42_FLASHPKG.7z

JB4.3 : ro.build.fingerprint=dell/Tablet8/yellowtail:4.3/JSS15Q/eng.XYX.20140226.115029:user/release-keys

Venue_8_WiFi_JB4.3v1.25_FLASHPKG.7z

KK4.4.2 : ro.build.fingerprint=dell/Tablet8/yellowtail:4.4.2/KOT49H/eng.build.20140624.115655:user/release-keys

Venue_8_WiFi_KK4.4.2v1.33_FLASHPKG.7z

Venue 8 HSPA+ 3830 :

KK4.4.2 : ro.build.fingerprint=dell/Tablet8/yellowtail:4.4.2/KOT49H/eng.XYX.20140624.150615:user/release-keys

Venue_8_3G_KK4.4.2v1.33_FLASHPKG.7z

CLICK HERE DONATE NOW : AND MAKE MY LIFE EASIER BY HELPING BUY ME A VENUE 8
[Dell Venue] social-design-concepts:
Tethered CWM Recovery Trial 11/5/14

CLICK HERE DONATE NOW : AND MAKE MY LIFE EASIER BY HELPING BUY ME A VENUE 8

Tethered CWM Recovery Trial

:

Note : This is a Trial CWM Recovery for some Intel Devices with locked boot loaders , it still has a few bugs . . .

WARNING : This is Tethered CWM Recovery is for some Intel Devices with locked boot loaders , it is not intended for installing custom roms as if the devices has a locked boot loader the device will fail to boot the unsigned images

This recovery uses the CWM Recovery [MENTION=2472806]vampirefo[/MENTION] built for the Dell Venue 8 3830 NoModem original thread : Dell Venue 8, CWM, unsecure boot/recovery

Tethered CWM Recovery Trial 11/5/14 : INTEL_TRIAL_TETHERED_CWM_PKGKIT.7z

Launch the recovery by placing it in the mykit-downloads folder the start myKIT_BATCHv1.1.x from the main menu select option A2 then select the tethered recovery program.

See this post for latest version : http://xdaforums.com/showpost.php?p=57227753&postcount=2310

Note : WORKING

adb root shell

backing up to external storage

unsigned .zip installation

you tell me

Note : KNOWN BUGS

backing up to internal storage is currently broken

installing using adb side-loading of zips doesn't work and breaks adb

you tell me

CLICK HERE DONATE NOW : AND MAKE MY LIFE EASIER BY HELPING BUY ME A VENUE 8
[Dell Venue] maxld:
I just wrote a PM to Chainfire. Let`s see if he`ll respond.
[Dell Venue] tikblang:
If this thing is flawless....

Then I would understand Dell for locking the boot loader.. But I am very very mad at Dell. This piece of device IS piece of junk with Android 4.3. Almost all appLications at some point in time will locked up and froze and for you to get back to it, you would have to press the power button momentarily, i.e turn off the display and turn it back on. Too bad I did not play with it very hard w/in 21 days of owning it. Now I don't know if it is worth talking to dell of repairing (AND/or REPLACING IT.)

Dell you can PM me. I will be actively watching this V8 (i GOT A 32 GIG v8) on www-facebook-com-DellHomeUS.

Thanks,

Tik
[Dell Venue] social-design-concepts:
Tik, while i under stand your frustration, I started this thread to move the devices out of the low activity section and for discussing and sharing any information that may lead to root method and aid in future development of these devices not to complain about Dell or the device..

if you wish to address to Dell your frustration with the device i urge you to post a commit to the facebook post:

Dell Venue 7/8 Intel Unlock Request

if you have a general question about the device please feel free to post in the new QA thread:

Dell Venue 7 & Venue 8 Intel General Q&A

or search in the original dell thread:

Original 2013 Dell Venue Tablet - root progress
[Dell Venue] wowbro:
If anyone can upload rooted 4.3 dumps I can help. PM me thanks
[Dell Venue] maxld:
I think that social-design-concepts has them.
[Dell Venue] social-design-concepts:
Tell me what you want, jcase rooted 1 Venue 8 on 4.3 but the exploit was never made public, but that user allowed me access so i have, extracted boot, recovery, droidboot, kernel and ramdisk only no real images, and the rooted system.img, also took cat /proc/kallsyms from the rooted device, but have since figured out how to get kallsyms from a non rooted device, i probably have most everything you just tell me what you need.

i hope to have everything i have up by the end of the weekend, till then list what your wanting and ill post what i can provide.
[Dell Venue] kairnage:
Quick couple questions, how are you getting into fastboot? I can't get it. Have you tried using fastboot to flash the rooted system image?
[Dell Venue] social-design-concepts:
adb reboot-bootloader even works powered off as the device use a charging os mode, or from powered off hold down vol down and the power key to boot to droidboot.

No I have the V7 not the V8, flashing a fake data.img to data I've had issues flash any img larger than 100mb or sparse images. Dell hasn't released a full restore firmware yet so I've not risked flashing system.img.

By the end of the weekend I should have everything I know up. The flashing a prerooted system image does seem to be a common root for Intel devices but with out a factory restore firmware / full-install.zip that's a huge risk knowing if it doesn't work dell won't warranty the device. So you'd be stuck with a soft brick until Dell released a full-install.zip and i don't think dells done that for any device they have ever released. Knowing that the device can be rooted with out flashing a prerooted system.img this should be a last option.
[Dell Venue] maxld:
I am just wondering, can we dump partitions without root? If yes, then we could dump them, try to flash this rooted img`s and in case of any errors we could go back by flashing dumped files via fastboot.
[Dell Venue] deansouth8:
OK. I don't know how much side chat anyone has has with jcase. He literally says the root method on his webpage i think he has registered in his xda profile. We also know he required Linux with the one and only root on the current dell ROM. He also posts on his site the basic method which he explains pretty clearly. Looks to have adb waiting for a device during the boot process to; I'm sure quickly mount something RW and script out a copy and execute a root. So, I know Linux treats hardware different and it may require less time to initiate communication with devices. Windows may not be showing you all the hardware/hardware ID's this thing reports it is so quickly during boot. It may not be possible to apply his method in a Windows environment. That said have you tried to get all the different types off hardware this thing reports that it is running on Linux and attempted a adb wait then immediate adb root method while its booting/rebooting?
[Dell Venue] social-design-concepts:
I was never able to get it to work on the dell venue, I actually discovered it independent of jcase, he wasn't gonna publish it but I leak it, mine is down at the moment, when I get my new one i'all try it again.
[Dell Venue] social-design-concepts:
how it is in the HP 1800la

init.debug.rc:

....

on charger

# basic networking for "adb root"

ifup lo

hostname localhost

domainname localdomain

#mount ext4 /dev/block/mmcblk0p7 /logs nosuid nodev barrier=1,data=ordered

mount ext4 /dev/block/mmcblk0p9 /data nosuid nodev barrier=1,data=ordered

mkdir /data/logs 0755 system system

mkdir /data/logs/modemcrash 0775 system system

mkdir /data/logs/stats 0775 system system

mkdir /data/logs/gps 0775 system system

mkdir /data/logs/aplogs 0775 system log

setprop persist.service.apklogfs.enable 1

setprop sys.usb.config adb

setprop ro.debuggable 1

how it is on the venue 8 JB-4.2.2

init.debug.rc:

....

on charger

# basic networking for "adb root"

ifup lo

hostname localhost

domainname localdomain

# mount data partition for get charger log

#mount ext4 /dev/block/mmcblk0p7 /logs nosuid nodev barrier=1,data=ordered

mount ext4 /dev/block/mmcblk0p9 /data nosuid nodev barrier=1,data=ordered

mkdir /data/logs/modemcrash 0775 system system

mkdir /data/logs/stats 0775 system system

mkdir /data/logs/gps 0775 system system

mkdir /data/logs/aplogs 0775 system log

setprop persist.service.apklogfs.enable 1

setprop sys.usb.config iadb

setprop ro.debuggable 1

how it is on the venue 8 JB-4.3

init.debug.rc:

....

on charger

on charger

# basic networking for "adb root"

ifup lo

hostname localhost

domainname localdomain

mount ext4 /dev/block/mmcblk0p7 /logs nosuid nodev barrier=1,data=ordered

mkdir /logs/modemcrash 0775 system system

mkdir /logs/aplogs 0775 system log

setprop sys.usb.config iadb
[Dell Venue] kairnage:
Do you have an uncompressed boot.img off the 4.3 ? I'd like to try enabling ADB and making system mount rw. That was how we got root on the Le Pan S originally.
[Dell Venue] maxld:
All files we have are here:

https://www.dropbox.com/sh/tqx1j2cpi155v2n/hPZPEnsZfi
[Dell Venue] kairnage:
Right, unpacked, I would like the original boot.img.
[Dell Venue] maxld:
Sorry, I misread that. I think that Social-design-concepts has them. I will try to contact him, cheers.
[Dell Venue] kairnage:
Thanks, If I try to pack it and fastboot can't boot it I won't know if it's the edit or the method I used to pack it. With the original image I can try to boot it first, and make sure that the system will even allow it. Then I will be certain I am a screw up if my version doesn;t work. :doh::eek:
[Dell Venue] ns218:
Also a warning for anyone that is going to install the xposed framework, looks like doing this will cause the tablet to not boot, I'm going to take a break now, and try to figure out what is causing that later this evening.
[Dell Venue] social-design-concepts:
no real need to thank me, i didn't do much, just package it all together and modified the batch files to make it easier for the average user, i don't want some real developer on xda to rip on me for just putting everything together in a single package and modify a batch file. it was simple enough process. i've talked to a few quote unquote devs that would consider a user taking any credit for this a joke since it was dell releasing the files that made it all possible the real thanks goes to the Venue 8 users working together on a task for the community so thanks to everyone here.
[Dell Venue] darklordofthesith:
What a bunch of assclowns. Don't even know anything about the product they aren't really pushing.
[Dell Venue] joanthanmajh:
which xposed version is it,

all or just one
[Dell Venue] social-design-concepts:
I've only just become hip to xposed framework not sure how the whole under workings work yet. I would suggest researching other Intel android devices and their success parts might have to be rebuilt for Intel remember most devices are arm not x86 based. So binary files needed might be an issue. I'll look deeper into it later.
[Dell Venue] EricdellT:
Do you think you will have the easier instructions by tomorrow morning?
[Dell Venue] darklordofthesith:
The developer who made it says it's compatible with x86 tablets. I encountered the bootloop but followed the directions to get out of it. Something isn't right with it on this tablet but I'm sure it will be fixed.
[Dell Venue] ns218:
I just tried installing the latest version, rebooted, got stuck on the dell boot screen. I have not tried to research what is causing that yet. Pressing a hardware key multiple times to disable xposed at least allowed the tablet to boot up.
[Dell Venue] social-design-concepts:
Yeah it really isn't all that hard though
[Dell Venue] EricdellT:
It's just that some parts are confusing and since this is my only tablet I don't want to mess things up. By the way thanks for your work!
[Dell Venue] social-design-concepts:
Really the hardest part getting the intel-soc driver installed but yeah no later than tmrw,

the process is actually use by other Intel android device users to unbrick there device you just have to have the correct files and dell finally gave them for the v8 so I hope they do for the v7
[Dell Venue] joanthanmajh:
yeah i had root with 4.2.2 and xposed worked fine
[Dell Venue] social-design-concepts:
If it worked on 4.2.2 I suspect its a compatibility issue with 4.3

From working on porting allwinner to 4.3 there are a lot of major framework diff between 4.2.2 and 4.3 that was my biggest headache was 4.2.2 proprietary blobs not compatible with 4.3.

does it say supports 4.3 if it doesn't more than likely won't work 4.3 is closer to kk than jb in my opinion from looking at source.

Also 4.3 on intel-mid is what 3 months old. I suspect most references to working on Intel tablets are dual boot PC based not actual intel-mid.
[Dell Venue] cline2:
I downloaded files. When I tried to run step1 Intel soc devices detection failed attempt 0 til 20 then stop. What's wrong?
[Dell Venue] social-design-concepts:
Did you install the Intel Soc driver?

do you see Intel soc under device manager?

Did you power off unplug and plug back in after installing the intel-soc driver?

This is the hardest part make sure to skip searching windows update on clover view device found.
[Dell Venue] cline2:
Yes but the step1 failed and step2 worked and it won't boot up.

I will try again with step1.
[Dell Venue] blutruck:
Did you reboot your computer? I had that problem as well and rebooted, then it worked correctly.
[Dell Venue] cline2:
Got it to work becuz no one explained how to do it for step 1. Had to use reboot droidboot.

Now I have it rooted!! Thanks!
[Dell Venue] lovemyram4x4:
I'm still running it on my 4.2.2, it does make the light sensor quit working if any of my modules are enabled.

I guess I'll stick with 4.2.2 for now, or at least until we have TWRP so I can my own themed framework and apps.

Sent from my Venue 8 3830 using Xparent Red Tapatalk 2
[Dell Venue] social-design-concepts:
The instructions need some work but its covered in the dell instructions for setting the Intel soc driver its the hardest part. after that as long as you power off unplug start the step 1 then plug it if the clover view plus driver installed correct it should work with out a hitch the Intel soc driver is the trickiest part but glad your working now.
[Dell Venue] minhdaubu:
yes its droidboot,and hanging on reboot4root => [waiting for device] screen

My device is B1 730HD_WW_GEN1 andoird 4.2.2