yashsingh1/xdaforums huggingface dataset:
[Android General] smtddr:
UPDATE#27

So, after manually patching my newer kernel video driver files to match what appears to be the intents of the BLU-dev in the older kernel... the panel gets init'ed properly. Now, I got tired of having to wait for the reboot to the flashed-working kernel before I could pull the dmesg.log. I wanted root while my newer kernel was running. That way I could see dmesg right there and reboot directly back into fastboot-mode for my next attempts. Before, I said that when I ran "su" it'd always fail. I discovered that is the intentional design of the "su" binary from the SuperUser.apk. They want "su" to communicate with it and since my device isn't booting up enough for the AndroidGUI(zygote?) to start up, SuperUser.apk apparently can't work either. Probably because SuperUser.apk cannot display that "toast" message I normally see "Adb Shell has been granted root permissions".

After some research, I ran into this thread: xdaforums.com/showthread.php?t=1463829 , they compiled a su that doesn't talk to SuperUser.apk. The link in that thread is broken, but this link: xdaforums.com/showthread.php?t=1197486 has a ROM (version 0.8.1) that contains f-su according to the change-log. So I downloaded this ROM and extracted its contents, searched and found the "su" binary. I then booted up my phone with the working kernel, became root, and copied this su binary into /system/xbin as "ultimate_su" and chmod'ed it 4755(rwsr-xr-x). Then booted into the newer kernel.

When I ran ultimate_su at first, it segfaulted, but if I waited long enough... maybe about 45secs after boot... then it gave me root. Interestingly enough however, while uid did return info indicating I was root... "dmesg" command still said operation-not-permitted. What I had to do was run the SuperUser's su, and because I was already uid=0 from ultimate_su, then SuperUser's su gave me root without talking to the apk. In summary, 45secs after boot I did this to get fully-powered root: ultimate_su -c su.

The issue I'm dealing with now is the following:

I'm pretty confused on this one. I do know that in the msm8916-pinctrl.dtsi , there's this:

If I change that 13 to a different number, then the error message still appears but it'll talk about that number instead of 13. I read stuff in this link elinux.org/EBC_Exercise_11a_Device_Trees , that taught me how to find pins that are free to use. Supposedly if I cat /sys/kernel/debug/pinctrl/1000000.pinctrl/pinmux-pins | grep "(MUX UNCLAIMED) (GPIO UNCLAIMED)" I get a list of pins I could use. For me, pin-50 was free so I changed the qcom,pins in pmx_ts_int_active to 50.... but I still got the error; just complaining about gp-50 instead of gp-13. Looking at the dts from the old working kernel, they also seem to be using the same pin with no problem. So I don't what to do yet... still researching & trying.
[Android General] smtddr:
UPDATE#28

So, after awhile of staring at this error message I decided to see if I really even needed thsi "msm-tlmm-pinctrl". Turns out, that the older kernel compiles version 4 of this. CONFIG_PINCTRL_MSM_TLMM_V4=y , while my newer kernel seems to have the first version "CONFIG_PINCTRL_MSM_TLMM=y". So, I did a search for all *.c & *.h files containing the string "TLMM_V4"(case INsensitive) on the older kernel to get an idea of how/where this tlmm_v4 module was used....then I modified the following:

* modified my .config to V4.

* In arch/arm/mach-msm/Kconfig, section config ARCH_MSM8916, modified it to V4.

* In ./drivers/pinctrl/Kconfig, copied the V4 version into it from the Kconfig of the older kernel.

* In ./drivers/pinctrl/pinctrl-msm.c, there was an "#ifdef CONFIG_PINCTRL_MSM_TLMM_V4" block of code that had to be copied into my newer kernel source.

* Copied whole file ./drivers/pinctrl/pinctrl-msm-tlmm-v4.c to my newer kernel, because my newer kernel didn't have that file at all.

* In drivers/pinctrl/Makefile, added dependency to cause the v4.c code to compile: obj-$(CONFIG_PINCTRL_MSM_TLMM_V4) += pinctrl-msm.o pinctrl-msm-tlmm-v4.o

And for my troubles, I got the compile error:

drivers/pinctrl/pinctrl-msm-tlmm-v4.c:883:3: warning: initialization from incompatible pointer type [enabled by default]
error, forbidden warning: pinctrl-msm-tlmm-v4.c:883

Looking at the code at that line, and the struct it's initializingstruct msm_pintype_info in drivers/pinctrl/pinctrl-msm.h, there is indeed a difference in the pointer-type. It's actually a pointer to a function, but the function signature in the newer kernel has more parameters than the old... and there are some other things as well. It'll take time for me to figure out how to change this stuff without breaking other stuff or if I can just get TLMM_V4 wholesale and copy the entire .c & .h and whatever else is the TLMM_V4 version into my newer kernel.

UPDATE#28.b

I tried just copying over the files pinctrl-msm.c & pinctrl-msm.h from old kernel to the new one. Surprisingly it compiled, but the result was a phone that couldn't boot up, no adb-shell access and didn't progress enough to read init.qcom.rc allowing me to get it to dump dmesg to a file like I did before.
[Android General] smtddr:
UPDATE#29

Okay, I surrender now. :( I cannot upgrade PINCTRL_MSM_TLMM to V4 without the boot process falling on its face and I can't see any error messages. This is probably where I'll be stopping unless I suddenly have a eureka moment in a dream or something.

It was fun and I did learn a lot trying all this. I hope someone finds some good info from my adventures of kernel tampering.
[Wing, P4350 General] Zeroeo:
Hello everyone this is my first post on these boards and Id like to say after reading a

few posts its nice to see a well rounded forum with nice people.

As you now know I'm really new to the whole PDA cell phone thing. I just order a Wing from ebay:

http://cgi.ebay.ca/ws/eBayISAPI.dll?ViewItem&rd=1&item=320152545128&ssPageName=STRK:MEWN:IT&ih=011

and I was looking for any tips or guides that could help me out with my first PDA phone.

I've had the Moto V220 and Siemens SK65, so this is a big upgrade for me. Any help

at all would be awesome, I'm looking for tips on how to speed up the phone, free room

and upgrade it to the newest software/firmware. And even some apps or games that can be install on the Wing.

Thanks!

ZeroEO
[XDA Assist] :
so. i updated my phone from cm 12 to cm 13 and

i got into twrp recovery and installed the the downloaded file.

now the phone is in bootloop. i tried to flash twrp recovery again. but it says mismatched partition size(recovery).

if i get into fastboot and select recovery, i get the teamwin logo and thr phone goes into the bootloop again. same thing happens even if i factory reset it(through fastboot)

please help me

thanks
[XDA Assist] Droidriven:
Hello,

Welcome to XDA.

To further assist you, please post your device model number and I will guide you to where you may find your answers. Thank you.

Register an XDA account to post and reply in the forums.
[Nexus 5X Q&A, Help & Troubleshooting] gururoop:
I recently purchased Oneplus 2 after my previous phone Oneplus One. I got sick at the rate of development of OPT and just order Nexus 5x and here too I'm seeing that there are very few custom ROMs. I'm wondering whether this phone too suffers from development restrictions as OPT? OPT has several proprietory drivers which are halting development. As I can see, OPO and Nexus 6p both have tons of Marshmallow based ROMs.

Are the developers yet to jump on this device? Or are there other issues? I have limited ROM building abilities and would try to build some popular ROMs once I get my hands on this device. Please share your knowledge.
[Nexus 5X Q&A, Help & Troubleshooting] jeffallin:
I'm wondering the same thing. Development was awesome on hammerhead- I thought it would be the same with the 5X.
[Nexus 5X Q&A, Help & Troubleshooting] juryben:
I'm surprised too.
[Nexus 5X Q&A, Help & Troubleshooting] ilikesamsung:
Sorry to this noob qn but its been a while since i had toucher custom roms. What is the difference between original android development and android development? IIRC, OAD is for CM roms related whereas AD is for 3rd party customised.
[Nexus 5X Q&A, Help & Troubleshooting] KennyG123:
This http://xdaforums.com/nexus-5x/orig-development/guides-rules-posting-original-t3208283 explains the difference.

I see only about 25% more ROMs for the 6P than the 5X, I count 16 here. It is probably just that more developers went for the 6P with the larger size, front facing speakers and 3GB of RAM.
[Nexus 5X Q&A, Help & Troubleshooting] gururoop:
From what I gather, Google is hell bent on making android a flashoholic's nightmare. But there is no need to worry because of this huge developers' community. I'm sure there will be an alternative to Google's android.
[Nexus 5X Q&A, Help & Troubleshooting] PiousInquisitor:
Can you share a bit of what your have gathered? Sources would be nice.

I'd actually like to hear from the ROM developers on this subject.
[Nexus 5X Q&A, Help & Troubleshooting] graffixnyc:
Are you kidding me? That is such an incorrect statement. Other devices never have bootloaders that can be unlocked as easily as nexus devices or unlocking a bootloader on other devices will void your warranty.. Nexus devices have always been developer friendly have actually were always meant to be developer devices, not devices for the end user.

Hell they are more open that any other manufacturer. What device OEM do you know of that releases all rom source code? Kernel code all oems have to release, but not rom code. Why is it that aosp roms for other devices need to be hacked together to work right? Because the manufacturer does not release the binaries needed to do a proper build. Google releases these binaries for every nexus device so you can build the whole system from source without hacking things together to work. So your statement is totally false..

What phone do you know of that you can build the whole system and flash it to your phone and have it work? Besides nexus devices you really can't.. Not a rom released by OEM anyway.
[Nexus 5X Q&A, Help & Troubleshooting] gururoop:
Merely allowing bootloaders to be unlocked does not mean that Google is developer friendly. Now, look at the ugly warnings that pop up as soon as you unlock the bootloader of bullhead. Didn't happen when I used mako. And supporting developers doesn't mean only hardware, even if you look at software, rooting has become so difficult. Earlier, it was as simple as installing a custom recovery and flashing binaries. Now, its a long story. Moreover, as soon as you root Marshmallow, certain features such as Android Pay get screwed up (although I never use those features, have read a lot of complaints about this). Do you consider these moves developer friendly? I don't.
[Nexus 5X Q&A, Help & Troubleshooting] republicano:
im thinking 6p was a better option for developers to buy meanwhile the 5x owned by consumers and those who want a smaller phone.

i was planning to unlock my bootloader right now but i realised i dont have a usb-c to usb cable so i can only charge it.

can you hide/remove this warning logo?

im pretty sure the roms will be ported over to each other in the new year
[Nexus 5X Q&A, Help & Troubleshooting] gururoop:
Fortunately you can hide the ugly logo by flashing modified splash files. They can be found in this forum.
[Nexus 5X Q&A, Help & Troubleshooting] bobby janow:
That is just so wrong. On so many levels. But for one correction root is obtained with a single flash of one file and android pay works with it. Why do you post such nonsense?
[Nexus 5X Q&A, Help & Troubleshooting] PiousInquisitor:
LOL. Spoken like a true user. Google hates development so much it wrote a guide 'for carriers, OEMs, and developers' showing them how to build from source. (Hint: Check out 'Downloading and Building')

https://source.android.com/source/index.html

What you don't understand is ROM/app development and rooting are mutually exclusive. You can build and use a ROM and not have root. You can also root and not use a ROM. Your pathetic rant above is about root, not development.

You obviously don't understand security either. Google has been blasted for poor security in the past and are trying to change that. Hence monthly security updates. Root is a big 'ole backdoor. One that can be used by Uncle Sam, China, or your friendly foreign identity thief to steel your info. With root the user, the biggest security hole there is, is in control of who gets through the backdoor. Google doesn't trust us and nor do our banks. Its not hard to see why Android Pay doesn't work with us in control via root.

I don't blame Google and neither should you.
[Nexus 5X Q&A, Help & Troubleshooting] hopesrequiem:
He thinks a nexus is hard to root? Seriously? He has clearly never owned an HTC device. The HTC Rezound literally had to have its circuit board shorted out to be properly rooted and have an unlocked bootloader. lol "Tap these two points once, then 1.75 seconds later tap them again. Too slow and it will reboot, too fast and it won't do anything. Just right timing will unlock the bootloader." Those were basically our instructions. OH how about the HTC Thunderbolt!! Having to type like 30 lines (or copy paste VERY carefully) into command prompt. Oh, but you are right "Guru", nexus phones are so damn hard. HAHAHAHHA!!
[Nexus 5X Q&A, Help & Troubleshooting] gururoop:
FYI I have owned HTC Sensation which required similar wire trick and M8 which required $25 to S-Off. But they where not developer devices. This developer devices tells (not warns) the users that the device iz corrupt because it's bootloader is unlocked. Worse than HTC which tells that warranty is void. But I guess it's difficult to explain it to you guys. So I concede. You are right, Google is the most dev friendly organisation, nexus is the most dev friendly line of hardware and you guys are the most pro devs out here.
[Nexus 5X Q&A, Help & Troubleshooting] PiousInquisitor:
Come on bro, tell us how big bad Google is ruining your phone because they hold your hand through building Android from source. It would make my afternoon.

Obtaining root on Marshmallow was more difficult than other versions of Android, or at least that is what the root God Chainfire has said. No one is arguing that.

Anyway, I've got more to say on this that I'll post later. It's time to go enjoy the weather and the great outdoors.
[Nexus 5X Q&A, Help & Troubleshooting] bobby janow:
"Your device can't be checked for corruption..." That's what it says, not that the device is corrupt. If you want it checked please relock the bootloader is what is suggested. Come on just admit you were wrong and move on.
[Nexus 5X Q&A, Help & Troubleshooting] graffixnyc:
"mearly" allowing bootloaders to be unlocked allows a developer to do anything to the phone. You can port over Ubuntu touch to it if you wanted to because they release the binaries and such.. You can't do that so easily with other devices. So what there is a warning if you unlock the bootloader. It doesn't interfere with anything, it's just there to let say someone who isn't tech savvy with phones to know something is up. Moto has a unlocked bootloader warning as do many other manufacturers. And I have had no problems using android pay on my rooted 5x or 6p. I'm just rooted though with chainfires no system partition mod root method. I used android pay last night to get the 20 best buy gift card. Yes, they have made things more difficult from a root perspective but it's not impossible and think they needed to do this to make Android more secure. They seem to be wanting to make it more and more secure, which isn't a bad thing.. But that's not saying they are not developer friendly.. The fact that you can unlock the bootloader and pretty much flash any partition you want is not something you can do just by unlocking the bootloader. Look at HTC devices for example.. To be able to flash all the partitions you need s-off and can't do it by the traditional bootloader unlock. You have a device that you can unlock the bootloader, flash whatever you want, not lose your warranty unless you do something really stupid. Build the system from source, change the source.. That's not developer friendly!?! ? Come on..... What just because they make it harder to root now (which really isn't really that difficult if you know what you're doing which most seem to not) and they make it more secure make them not developer friendly? Again, what other phone do you know that you can take the source, change it, build it and have it work? Or port something like Ubuntu touch to it? You can't.. Other manufacturers just simply do not supply what is needed for developers to do this.. Google does supply this so developers could do this..
[Nexus 5X Q&A, Help & Troubleshooting] ShishkaBerry:
Because it's only been out for 2 months. ROMs aren't built in a day, much like Rome.
[Nexus 5X Q&A, Help & Troubleshooting] terrawatt:
Hahaha. Best answer:)

Skickat från min Nexus 5X via Tapatalk
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Rhaegon:
Hi I have a SGH-I337 on 4.4.2. If I wipe my Dalvik and cache I get the Swipe screen and can access my phone without ever entering my PIN! My phone has been set to PIN ever since i installed GOLDFINGER 9.0 XXUGNK4 . This only happens if i wipe Dalvik and Cache. Anyone ever encountered this?
[General Questions and Answers] orbitz52:
hi.. I just bought axon mini from China, is it possible to root this device? I wanted to install gapps to pla COC.. my android version is 5.1.1

thanks in advance..
[General Questions and Answers] xenreon:
Can't find a dedicated and trusted one... I suggest try the oneclick root apps
[General Questions and Answers] orbitz52:
I tried kingoroot and framaroot but no luck
[General Questions and Answers] xenreon:
Try a few more, that's the only choice now unless you build a prerooted firmware or recovery for rooting
[General Questions and Answers] orbitz52:
still not rooted..
[General Questions and Answers] demenicis:
Root Done, Solved

Gents, I just got this phone (Axon Mini, B2016, Totally English ROM) less than a month ago and managed to root it and to replace kingroot with SuperSU, perfect.

Can't find a custom recovery yet though, I looked everywhere, so no Xposed so far. But the Phone is pretty good after tweaking the governor and removing crap (touchpal keyboard and other stuff)

I had managed to root the phone once, but after playing with link2SD (I liked it to use to managed apps) it turned out that link2D destroyed and deleted the entire system/app folder, do not use this app on this phone, it doesn't suppert 64 bit either, it cannot even freeze apps at all. So......

I found the official ROM, and flashed it with the stock recovery......everything back to the beginning. I'm not sure where I found it, but I do have the file on the SD card and on my PC at home.

However I after 1 million attempts to root it again with every single "one click" root app, I gave up. I was away on holidays so I decided to wait til I was back home to try via PC.

Back home, once again I failed 258 times.....nearly giving up again.....than.....Eureka.....

Basically:

- Install PC king root on your COMPUTER as well as the phone driver (on my PC it installed automatically, no download needed)

- in dev options, debug on and bootloader unlocked.

- here is the magic trick.....when plugging to the PC choose "install driver option", and NOT "media device MTP" or any other option.

- Run the King root app and press ROOT.......done......finally.

If you got it right you should be very lucky and certainly relieved!!!!! what a pain!!! very little on the web.

Now, not being used with kingroot, I felt uncomfortable with it as I always had SuperSU.

but before the next step, I'd like to say that I found, in the end, Kingroot a more feature rich app. It had done so far a good job as a SU app, plus it gives you the option to turn ON/OF (safely) most of the app receivers, which can be used to stop undesirable apps to wake up the phone. I did not used the "purify" app though and I found I don't really need it, but it isn't a bad app either and looked very professional.

But if you still want to replace it with super SU, it is DEAD EASY, in 2 steps.

- google and download an app called SuperSU Me.apk (my version was 6.7(64), and the actual package name is darkslide.com.supersume), run it and that is done. Kingroot will disappear and super SU will be installed.....sooooo easy.

- now you can go to playstore and update superSU, it WILL install the binaries fine via NORMAL method. Reboot and smile.

Done, no recovery needed.

But now I would consider you THE MASTER if you can come up with a custom recovery (kernel 3.10.49) so I could try install Xposed.......I miss gravitybox sooo much.

Cheers

D....
[General Questions and Answers] Crisvendetta:
great!

Can I know what governor settings you have, as I strugle with lag
[General Questions and Answers] demenicis:
CPU tuner

screen on, ondemand, max=min=1344,threshold 25

screen of,battery saver,max 400,min 200

it only works every other reboot.

---------- Post added at 11:30 PM ---------- Previous post was at 11:19 PM ----------

AXON MINI (B2016).....GUESS WHAT? XPOSED INSTALLED......up and running... gravity box works perfectly.....menu button on Nov bar and everything

amazing.

no recovery yet.

download flashfire....from chain fire, obviously!, exposed.zip.....sdk22 (arm 64bit)

tried once it went black and never back......volume + & power for 10 secs

then I tried again ticking "auto mount" option.

stuck on the the boot logo for far more than usual, ~3mins, then it run some command lines for while then the logo move ahead. reboot again and it seems the dalvik cache had been cleared.....updating 205 apps.. 10 minutes later...... done. simple but my heart was pumping hard!

please note I had super SU and not king root.

axon mini b2016, international ROM.

cheers.

---------- Post added at 11:35 PM ---------- Previous post was at 11:30 PM ----------

i mean I did all that without a custom recovery.....stock one is still there but pretty useless so far other than for flashing stock ROM.

to make this phone simply perfect I still need a custom ROM to be able to backup my OS. but as long as I don't mess the system up....I already have all i need.

---------- Post added at 11:40 PM ---------- Previous post was at 11:35 PM ----------

phone is now smooth like butter. no lag at all. it seems xposed actually made it faster on its own.

even the gallery,which was lagging a bit is just fine now.

---------- Post added at 11:42 PM ---------- Previous post was at 11:40 PM ----------

sorry, one more. installed asus browser which is basically the old aosp browser.....chrome uninstalled (this ****, thanks goodness)
[Galaxy Note 4 Q&A, Help & Troubleshooting] mikoro33:
Hello guys. I bought a samsung note 4 running on android 5.5.1 and was ready to follow the youtube tutorials on how to root it..but i foumd out that it already has root access (i checked it on cpu z and root checker) but there is no supersu installed. I was just wondering if i could just download it from the playstore but im worried that something might go wrong. The youtune tutorials show that after rooting..it automatically has a supersu installed so i am wondering why there is none installed on my device. Thanks in advance. (I've got the n910f variant btw.)
[Galaxy Note 4 Q&A, Help & Troubleshooting] :
Greetings,

Thank you for using XDA Assist. To get you the expert advice you need, I'm going to move this thread to the specific device Q&A forum.

Good luck!
[Upgrading, Modifying and Unlocking] bogdan_wrc:
What solution shall be used? Windows 10 OS.

how can i find IMEI?

thanks
[T-Mobile Samsung Galaxy S 4] dhaval.jari1:
Hello, I am using T-mobo galaxy s4 (SG-M919). I've rooted my phone. I want to install custom rom of galaxy s4 i9505's in my T-mobo. I've read that we can install it. I want to install lollipop version of it. Please someone tell me how? I need it so badly.

And another problem is that nowadays whenever I am trying to install T-mobo's rom on my phone, it stuck at galaxy s4 logo every time. So, I have to flash it through odin every time. And T-mobo has kitkat firmware and i don't want to use it. Someone please help me out.