yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Accessories] kush2.0:
I have been downloading and installing and downloading..... Reading and researching!!! I have an unlimited data plan so let's face it I kick the hell out of it. I like to watch movies a lot on showbox or on cartoon HD threw mhl HDMI to my TV (mirrored). Anyways after loads of messing around installing loads of different ROMs I realized the truth is that only Sammy tw ROMs have the USB drivers. This was all because I read on some post somewhere that said they had a custom ROM and a touchwiz launcher and to use mhl they simply boot the tw launcher for mhl use only and then back to Google launcher as a daily driver. Post didn't say which custom ROM they where using and/or if they had a custom kernel installed. So that's what set me of trying to conker making it work and my solution to this problem is "arter97 kernel" plus dual boot.zip plus back to noot ROM and I really do like the resurrection remix ROMs. I like the new marshmallow 6.0.1 but the arter97kernel doesn't support this so I settled for RR lollipop 5.1.1 v5.5.9 as the first ROM. installed this as per normal protocol and then flash the arter97 kernel using twrp recovery. I used v4.1 kernel because it has load more customizations than v5 for ex. Over clocking to 1800mhz and more Governors etc. Now arters back to noot kitkat 4.4.4 is very stable very good ROM. So once the first aosp ROM is OK and stable with the kernel (make sure you flash superSU) boot back into recovery and flash the dual boot zip and anything flashed during that visit to the recovery goes to the 2nd ROM partition. Next flash the back to noot v9 ROM and superSU and boot back into 1st ROM (automatically) but don't wipe cache/dalvic/data (this will just wipe from the 1st ROM). Now the aswitch app will work to boot into the 2nd ROM. And because you flashed the superSU into 2nd ROM the aswitch will work to allow you back to the 1st ROM!!!! Every time you want to flash to 2nd ROM use the dual boot zip first. Don't flash the kernel zip just leave it and it will have the same arter97 kernel once booted. If you flash the kernel to 2nd ROM it will just cause lag and instability so dont flash the kernel twice. The only problem I have had is whilst using this whole configuration is when inserting the mhl lead into sgs3 it freezes and/or shutdown. After a little tweaking I figured out it was a CPU issue and to enable the mhl and showbox use I used "atweaks config app" and changed Max over clock CPU to 1704mhz and governor setting to performance!!! Now this profile makes the CPU stick at 1704mhz permanently. This method works but unfortunately also creates massive*battery*drain so I have also been messing with the USB charge/power variables. But do be careful if you follow any instructions on this post as I am not responsible for a bricked divice so make sure you do your homework. This arter97 kernel is EOL @v5 for the sgs3 so versions 4.1 and 5 are only compatible for lollipop 5.1.1 so always read changelogs. Many thanks to arter97 for this dual boot and customisable kernel and ported ROM
[HTC Desire Eye] xXminiWHOOPERxX:
*this thread is for eye_ul and eye_ul_ca . it will NOT work on other variants without consulting me first to see if it will work with your variant, search your device general forum for a specific thread if their is one

1. What You NEED!!!

S-OFF

adb and fastboot tools - DevHost

terminal via pc or Android Terminal Emulator

Read this:

this will not work if your s on

Disclaimers:

i have tested this my eye_ul_ca Lollipop firmware ,but use this info at your own risk. if it melts your phone into a little pile of ash ,its not my fault.

2. Commands to Achieve Official Status

This is for experienced adb / fastboot users... if not experienced please use android terminal emulator.!!!!

adb shell

su (if needed to get a # prompt)

echo -ne '\x00' | dd of=/dev/block/mmcblk0p6 bs=1 seek=5314564

(i would very strongly recomend you copy/paste this)

exit

(exit a second time if you need to to get back to a normal > prompt)

adb reboot bootloader

verify official is their :)
[HTC Desire Eye] luisitox22:
Wow, this is great information! Thanks for sharing. Will have saved. Happy new!
[HTC Desire Eye] hbrajhbh1:
my phone is EYE_TUHL PVT ,S-OFF, unlocked, super CID and on 5.0.2

i used the above command prompt and successfully revert to the "official " thank u very much
[HTC Desire Eye] xXminiWHOOPERxX:
adb shell

su

cat /proc/emmc

And what variant is yours exactly
[HTC Desire Eye] hbrajhbh1:
i did not understood variant>

original CID is ht c_044 version 1,17,707.9 used your comd prompt and so many details found ?
[HTC Desire Eye] xXminiWHOOPERxX:
I need them.....
[HTC Desire Eye] hbrajhbh1:
View attachment 3596502

please refer attachments copies of my command prompt results? are files helpful?
[HTC Desire Eye] xXminiWHOOPERxX:
eyetuhl? Asia?

mmcblk0p6 is pgsfs , which is where the tampered flag is, but with newer hboot it's a official or modified flags... so commands will work only if your s-off... do not try with s-on
[HTC Desire Eye] hbrajhbh1:
please clarify that what I used command prompt to get official is ok? it remains as official?
[HTC Desire Eye] arnob_apon:
when i update it's said i'm using modified version?what should i do?

EYE_UL_CA pvt ship S-OFF

CID-11111111

HBOOT-3.19.0.0000

openDSP- v47.2.2-00564-m8974.1024

OS-2.09.502.3
[LG Optimus G Pro] akshaybose:
i came across an issue with mounting of external sdcard in my lg optimus g pro of course after installing a stupid apk file -_- lg g pro recovery. the sd card haven't had any problem. it was the phone.it just shows sd card inserted it wont mount,manual mounting was also kinda disabled. and the only fix was FLASHING .kdz to the phone. but there is an alternate fix for this using lg mobile support tool.

1. Download lg mobile support tool from the link below .

2. install in your pc .open it plug in your phone.

3.it gets detected after that go to the options on the top right corner of the window.

4.You'll see UPGRADE RECOVERY option.

5.click that and follow the instruction.make sure you have internet connection.

your data's are safe .it wont go.but if you arent so sure it will be good to make a back up if you'd like to..

yea and you will have to re-root your phone (if you may have to)as the root will be gone after upgrading the recovery.

here is the download link:- http://lg-support-tool.en.lo4d.com

thanks hope this helps:good::D
[P3300, MDA Compact III ROM Development] thormdac:
@all, i would like to remove the battery symbol in the top bar, next to the sound icon!

have been looking through the registry searching for power.exe, but no luck removing the display!

any idea, please!?
[P3300, MDA Compact III ROM Development] NikMel:
just search for the same subject:confused:
[P3300, MDA Compact III ROM Development] ouioui01:
Hi thormdac,

HKLM/Software/Microsoft/Shell/ShowTitleBarClock = 0 -> 1

:D :D

Cheers
[P3300, MDA Compact III ROM Development] thormdac:
sorry, that removes the clock,- i want to remove the battery symbol

many thanx though
[P3300, MDA Compact III ROM Development] raymonds:
that registry tweak should show the clock, and at the same time, remove the battery symbol.
[P3300, MDA Compact III ROM Development] thormdac:
on my device i disabled title bar clock via htc-home-customizer. once tweakeing registry as above, nothing happens!

btw. like to have neither, no clock and no battery!:)
[P3300, MDA Compact III ROM Development] NikMel:
From Wiki of Artemis:

Show Time,Date,both or Battery on top bar at Today screen

[HKLM\Software\Microsoft\Shell\]

Time:

"ShowTitleBarClock"=1

"TBOpt"=1 (This key will need to be created)

Date:

"ShowTitleBarClock"=1

"TBOpt"=2 (This key will need to be created)

Both:

"ShowTitleBarClock"=1

"TBOpt"=3 (This key will need to be created)

Nothing:

"ShowTitleBarClock"=1

"TBOpt"=0 (This key will need to be created)

Battery:

"ShowTitleBarClock"=0

"TBOpt"=1 (This key will need to be created)
[P3300, MDA Compact III ROM Development] thormdac:
ok,ok, but this leaves a rather nasty gap:

see attachment:
[P3300, MDA Compact III ROM Development] thormdac:
@all, once i changed my tody theme back and forth, in between times the screen appears as it should: no battery, clock and NO GAP, mostly though the gap REAPPEARS!!!

any remedy for that?

thanx
[P3300, MDA Compact III ROM Development] NikMel:
this is a microsoft "future" :rolleyes:
[P3300, MDA Compact III ROM Development] layer1:
Not sure if the gap problem is the issue when part of the signal bars are missing. I've seen this as well but noticed when the bars drop down to 1 or 2 bars it chops of the right side as you indicated. I've yet figured out a way to resolve. Very annoying issue.
[P3300, MDA Compact III ROM Development] buggers999:
bump.

has anyone heard anything about a fix or workaround for this? very annoying bug indeed.
[P3300, MDA Compact III ROM Development] nusul:
any news about the gap created when removing clock and time?
[Galaxy Tab S Q&A, Help & Troubleshooting] Zwhlol-Zniper:
Hello all,

I have so many questions for you but here is the latest one. Which version of Odin would be best used to root my tab s?

I have 3.0.9 but that does not have the PDA option that I would like to be able to flash [MENTION=2739548]tamirda[/MENTION]'s new version of his phoenix rom.

Any links to existing threads that answer this question would also be appreciated.

Thank you very much!
[Galaxy Tab S Q&A, Help & Troubleshooting] ashyx:
That will be fine.
[Galaxy Tab S Q&A, Help & Troubleshooting] Zwhlol-Zniper:
I'll add another thanks to your count. After playing around with the odins, 3.6 is the best for flashing pda files. But I plan on getting more samsung phones in the future. I'm loving these new mods on my devices.

But one question, why can't I enable the pda option in 3.10.9?

I know that won't matter if I have a bunch of odins with that option, but still.
[Galaxy Tab S Q&A, Help & Troubleshooting] DUHAsianSKILLZ:
PDA has been renamed to AP in odin 3.09 and 3.10+. You can simply place PDA files into the AP slot with no issues flashing.
[Galaxy Tab S Q&A, Help & Troubleshooting] Zwhlol-Zniper:
Oh damn, with out any hint of sarcasm, that was really helpful!!!! Now I can flash with confidence! Thanks. :)
[Galaxy Grand Prime Q&A, Help & Troubleshooting] adrwill2000:
As the topic says. I'm working on a custom rom...and frankly I'm ready for mine to come back to life. Much appreciated!
[Galaxy Grand Prime Q&A, Help & Troubleshooting] sdw1988:
https://drive.google.com/folderview?id=0Bza7IYQ7uyQYX2hTM1dmckdqYUE[/URL]

Here u go.. it's the full system dump for Straight Talk's.

SM-S920L~ SAMSUNG GALAXY GRAND PRIME~ All 1.71 gb of it.. I have been messing with it here & there reading + studying the methods trying to port a functional custom recovery of whichever type I can.. So far I have manged to unpack the boot.I'm & recovery.img partitions using android kitchen with cygwin.. Been trying this & that copying files from stock ramdisk and using them to replace files from an unpacked custom recovery ramdisk folder... I picked a custom recovery of a similar device to make it easier.. So far each late night attempt has ended with "SEANDROID ENFORCING" & or Odin mode as recovery.. Hopefully by putting this out there I will further development & speed up the process somewhat as the chances of me succeeding in a successful port are looking slim.. If more files are needed Im more than willing to provide whatever & also have no issue with doing the testing if the developer won't have this particular device in hand at the time.. Thank you in advance and good luck...
[Galaxy Grand Prime Q&A, Help & Troubleshooting] ordinarykid23:
Change enforcing to permissive
[Galaxy Grand Prime Q&A, Help & Troubleshooting] sdw1988:
I have been trying to do that with this phone using same techniques that have been successful on my other devices but to no avail.. I've used adb commands,terminal emulator, int.d scripts at boot + several other methods but when I run getenforce I'm still getting enforcing as a result. Can't even get it temporarily permissive.. I have the t-mobile version of this phone as well (SM-G530T) which I had no problem achieving permanent permissive with.. Although during rooting it I used sunshines kernel flash which might be where I acomplished this.. If there's anot her method I'm overlooking please let me kno how to do so
[Nexus 6P Q&A, Help & Troubleshooting] holic_2:
It's on all of our minds. Maybe it's just a bad batch or maybe it's really real. Regardless, has anyone actually *returned* theirs just based off of fear?
[Nexus 6P Q&A, Help & Troubleshooting] Soulfly3:
that'd be pretty pathetic, imo.

we're adults, not children.

it COULD bend? so what? Do you retun your device because you COULD drop it and the screen smashes into 1000000 pieces?
[Nexus 6P Q&A, Help & Troubleshooting] 400ixl:
Not on everyone's mind at all, certainly not mine. I just wouldn't ever put a phone of that size (no matter what make) in a back pocket for example where it would be stressed in such ways. In the UK you can't return it because something may happen anyway, so it would be a moot point. You could only return it within 14 days if bought directly off the internet under the distant selling rules.
[Nexus 6P Q&A, Help & Troubleshooting] PaisanNYC:
My pencil MAY break the point. Let me return the whole lot of them and get some pens :)
[Nexus 6P Q&A, Help & Troubleshooting] dratsablive:
I might break some wind, ....oh wait. No not on mind what so ever!
[Nexus 6P Q&A, Help & Troubleshooting] tfly212:
Definitely not. Considering what these devices are (hand held internet PCs) I am surprised people expect indestructibility. I wouldn't sit on my laptop or Surface Pro. Why would I sit my phone and expect nothing could happen?
[Nexus 6P Q&A, Help & Troubleshooting] Olddog828:
When is this going to end? Just when I haven't seen anything on bending for a week or so, up pop's a post about it in some form or the other. I can not imagine after using this phone for 2 months that it will bend unless its done on purpose or as some say in this thread left in a pant's pocket and bent that way. If the fear is so great, lock yourself in a room and stay away from all large size phones.
[Nexus 6P Q&A, Help & Troubleshooting] Gorgtech:
My device is slightly warped though I literally took care of it. I always held it in my front left pocket without anything else inside. I wear regular jeans and also use a Spigen Rugged Armor. I might try to RMA it though if the area around the volume buttons will be damaged sooner or later.
[Nexus 6P Q&A, Help & Troubleshooting] Pain-N-Panic:
Did the rugged armor warp your frame? I just ordered that same case yesterday....
[Nexus 6P Q&A, Help & Troubleshooting] WizeGuyDezignz:
I didn't return 2 of them because of fear of bending. I returned 2 of them because they were bent.
[SuperSU] Efreak2004:
I've spent the past couple of hours trying to get various tools (busybox, supersu, xposed, etc) installed in the microsoft android emulator, including SuperSu, and all I've managed so far is busybox (all I had to do was copy it over and rename it). The microsoft android "emulator" is a hyper-v virtual machine with an x86-based android installed in it. You can get root simply by running

su

and/or

adb shell

. Unfortunately, it doesn't have a recovery. It has a simple script to install binaries by running install_zip.sh, but this doesn't seem to be calling updater-binary at all, and I'm not sure how to fake my way around that. Is there any chance of getting a flashable zip file (or a command to manually run the updater-binary script) for installing SuperSu in such an environment? A large number of root apps expect a su daemon like SuperSu and will not work without it, even if the su binary doesn't require it.
[Galaxy Y GT-S5360 and Duos 6102 Q&A, Help & Troubl] Samuel KinG:
Hello,

At first time when I rooted n flashed rom (petrux) it worked finethen I wanted to change my rom I reverted it in stock, after rooting stock again., it booted successfully but then it started to show Samsung animation again plz helllp I wanted to flash another rom:crying:

Sorry for bad english
[Xperia Z3 Q&A, Help & Troubleshooting] xo.en:
Hello,

happy new year.

I have a question regarding repartitioning of Z3 parttable.

Ace2 was simple device with VERY bad partitions sizes.

I noticed, that Z3 has similar problem, BUT: I need to know, if something similar is possible with Z3:

I want to resize sdcard0, cache, and system partitions, mainly.

while repart for a2 looked like this(adb, pc, cmd used there), :

adb shell
su
parted /dev/block/mmcblk0
unit kb
print
rm 9
rm 8
rm 4
rm 5
rm 3
print
### SYSTEM ###
mkpart primary 105906 540000
print
### CACHEFS ###
mkpart primary 1525907 1705907
print
### DATAFS ###
mkpart primary 540000 1525907
print
### UMS ###
mkpart primary 1705972 3948937
print
### HIDDEN ###
mkpart primary 1705907 1705972
print

name 3 SYSTEM
name 4 CACHEFS
name 5 DATAFS
name 8 UMS
name 9 HIDDEN
print
### Format HIDDEN ###
mkfs
y
9
ext2

Is something like this possible with Z3 too?

I mean, by this method, tbs.
[Zuk Z1 Q&A, Help & Troubleshooting] DAVMARS:
hello, my Z1 for 15 days to work very well . I have a sim for calls and the other for Internet. The two networks have more but I pine codes. when I go to test information telelphone I did that I'm on gsm only sfr but with other sim is the same. I 'm doing wipe and return to factory settings . my imei is what normal.donc is 00 for 15 more days I will walk you have lost ideas. we say that something is missing because with sim I capture the network sfr but I can not save myself and the other sim does nothing captures it goes astray directly networks . my two sim work well in my old phone ZOPO zp999 . thanks a lot for your help
[Galaxy Grand Prime Q&A, Help & Troubleshooting] rezaveros:
hello Guys /:o:highfive:

I Need Custom Rom Like Cm13 Or Aosp Or ResurrectionRemix For Galaxy Prime Sm-G530H.

My Phone have Some Lag when I Use it.I've heard that if I install Android 6.0.1 marshmallow phone will be without lag.:angel:

Can anyone for me and all those in need Make this Rom ?:cool:

thank you .:angel:
[Galaxy Grand Prime Q&A, Help & Troubleshooting] Soki99:
Wait the developer dude :)
[Galaxy Grand Prime Q&A, Help & Troubleshooting] pauloribeiropassos:
Please for the g531h too...:)
[Galaxy Grand Prime Q&A, Help & Troubleshooting] WinKarbik:
We will doing cm13 later, when cm11 will be ready for daily use
[Galaxy Grand Prime Q&A, Help & Troubleshooting] Soki99:
Really ! Wow :) Awsome
[Galaxy Grand Prime Q&A, Help & Troubleshooting] maamiradina:
I am also waiting for 530H
[Galaxy Grand Prime Q&A, Help & Troubleshooting] rezaveros:
Has anyone tried to make a rom 6 for this phone?

Please help Me :)
[Sony Cross-Device Development Themes and Apps] mpourfath@gmail.com:
In The Name of GOD​

[IMG="Rocks Xperia Theme"]http://s1.upload7.ir/uploads/HFzFMtkM.jpg/sketch-1451644056548.jpg[/IMG]

Hello and Happy New Year everybody!

Today i want to share my second Xperia theme called Rocks Xperia, i wish that you'll enjoy it.

i tested it on my Dear unrooted Xperia Z2 stock lollipop 5.1.1 rom. it will work on kk as well as lollipop. i made it by Sony Theme creator app.

Just download it and install it on your Beloved Sony Xperia Device

:highfive: Please feel free to test it and drop your comments below :highfive:

Link: Rocks Xperia Theme​

Reza Pourfath a Design Lover from IRAN​
[X Style (Pure) Q&A, Help & Troubleshooting] Tinkerer_:
It looks like Marshmallow is following the usual pattern of Android "x.0" alpha release to the public, followed by "x.0.1" beta release with initial defect ('bug") corrections starting with Nexus beta testers (I.e. Nexus users in general).

Reading about the MM 6.0 problems on MXPE, I'm sitting out the 6.0 alpha testing on the sideline with LP 5.1.1. Most trouble-free phone I've had yet, and I don't yet need the only compelling feature I see with MM on the MXPE (T-Mobile Band 12 support).

Any noises yet about MM beyond 6.0.1? (I know I can look for this elsewhere too, but thinking maybe some of the XDA community may have inside info from the Android community.)

TIA...
[X Style (Pure) Q&A, Help & Troubleshooting] MattBooth:
The marshmallow update give me some new features and better battery life (though I do own the X Style, not pure). Unless you are dead set on being intentionally obtuse, then this isn't considered an alpha update.

Also the 6.0.1 update is quite minor, the largest change being some ART performance improvements, the rest is adding bands to the Nexus line and some emoji's: http://www.androidheadlines.com/2015/12/google-posts-android-6-0-1-changelog.html
[X Style (Pure) Q&A, Help & Troubleshooting] Tinkerer_:
I know the label "alpha" is not not the official label for something like 6.0. But with so many substantial defects, and multiple forthcoming revisions to correct those defects a certainty, that's really what it is IMO. Maybe "public release alpha" would be a better description, since pre-release revisions go through even more defect-ridden levels including pre-release alpha, prior to public release.

Similar situation with previous Android versions, and in fact most software foisted on the public these days (I'm looking at you, Microsoft and Apple). Look at Lollipop and the multiple public release revisions it took to iron out most of the substantial defects, finally, with 5.1.1.

6.0.1 is not just "...some ART performance improvements, the rest is adding bands to the Nexus line and some emoji's...", it also includes defect corrections. (Bluetooth, anyone?) And if the changelog doesn't list a significant number of defect corrections, that doesn't necessarily mean it is already polished at 6.0.1. The fragmented Android ecosystem and separation between Google, phone manufacturers, carriers, and users guarantees a plethora of various non-trivial defects in the ecosystem, many of which Google will address only slowly or even never for most phones.

For example, the memory leak defect in LP was not fixed until 5.1.1. How may revisions and months did that take? How many phones still run pre-5.5.1 with this defect?

One reason I bought the MXPE was the idea that it would be one of the first to get the updates. That turned out to be overly optimistic. It looks like Nexus is the only one still close enough to the source to get timely updates, and it also looks like Google is not pursuing Android defect corrections with any kind of urgency at all nowadays, maybe because the hardware ecosystem is becoming way too diverse to adequately support any more (or maybe because the profits roll in no matter what). Motorola phones, with the Moto alterations to Android, outsider status with carriers, and now hollowed-out Motorola support, appear to be no closer to adequate Android support from Google than any other non-Nexus phone.

"Obtuse"? A "bug" is a euphemism for a defect. Let's stop being obtuse, and call it what it is.

Any other info also appreciated.