yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy J7 (2017) Questions & Answers] hacker812c:
see this method

https://xdaforums.com/showpost.php?p=76198074&postcount=6
[Samsung Galaxy J7 (2017) Questions & Answers] micaiahmorris:
https://xdaforums.com/galaxy-j3-2017/how-to/root-sampwned32-samsung-j3-prime-sm-t3761497

for the j327t same method should work for our model assuming it is working. It just says we need a engineering system img similar to the j3 prime's root file.

Perhaps with the combination file?
[Samsung Galaxy J7 (2017) Questions & Answers] bibob3d:
Hi all. I was wondering if it's possible to root J727T running Oreo 8.1 (and if yes, how?) and also if it's possible to install the original stock version OS that it came with before all the Samsung and T-Mobile updates (I think it was either 6.0 or 6.1). Thanks beforehand!
[Samsung Galaxy J7 (2017) Questions & Answers] FlyingSpark:
Galaxy J7 (SM-J727T) bootloader locked

I have been trying to find a way to root my galaxy J7 all day. I have the model SM-J727T (t-mobile) and am unable to find the OEM unlock setting under developer settings. I have tried using fastboot and many other methods. Has anyone else had luck with rooting this model? If so please share!
[Samsung Galaxy J7 (2017) Questions & Answers] ashyx:
Read the thread, not rootable.
[Samsung Galaxy J7 (2017) Questions & Answers] salman.093:
Hey. I got my hand on a j727t which has a converted rom to j727f .

But the thing is it is rooted. I'm gonna try on installing magisk what happens or you suggest something?
[Samsung Galaxy J7 (2017) Questions & Answers] BlackAxiom:
is this verizon or some other carrier model :confused:
[Samsung Galaxy J7 (2017) Questions & Answers] HACK3DANDR0ID:
This is the T-Mobile variant and that was many devices ago...
[Samsung Galaxy J7 (2017) Questions & Answers] BlackAxiom:
carrier specific devices aren't really supported on the Mid-range devices unfortunately.
[Samsung Galaxy J7 (2017) Questions & Answers] HACK3DANDR0ID:
No Samsung Flagship in the states no longer has OEM UNLOCK
[Samsung Galaxy J7 (2017) Questions & Answers] BlackAxiom:
umm it appears after 7 x 24hours of uptime.
[Xiaomi Redmi Note 4 Questions & Answers] sjadhav252:
Does miui 9 beta rom 7.8.10 supports exfat format sd card
[Xiaomi Redmi Note 4 Questions & Answers] RKStyles:
Many users have reported that it doesn't. You have to format your SD card in FAT32 format to make it work in MIUI 9.

Sent from my Redmi Note 4 using Thumbs
[Android Q&A, Help & Troubleshooting] _xray:
Hi! I have a new Xiaomi Redmi 4X and want to use it for app development with Android studio. I enabled the developer options, usb debugging, installing apps over usb and usb debugging (security settings) on the phone. When I connect the device to Windows 7, I see a device called "ADB Interface" in the device manager which is missing a driver. The hardware id of this device is "USB\VID_2717&PID_FF48&REV_0318&MI_01".

I already tried the following things:

The Minimal ADB and Fastboot package from XDA developers (https://xdaforums.com/showthread.php?t=2317790 --> https://www.androidfilehost.com/?fid=745425885120698566)

Xiaomi Mi Flash Tool (http://en.miui.com/thread-345974-1-1.html --> http://api.bbs.miui.com/url/MiFlash)

The Google USB driver that can be downloaded in the Android SDK manager

ADB Driver Lite and Platform-tools (adb/fastboot) for Redmi 4X (https://xiaomifirmware.com/downl ... ols-redmi-4x-prime/ --> https://xiaomifirmware.com/download/3718/)

Xiaomi Redmi 4X driver For Normal Connecting (https://gsmusbdriver.com/xiaomi-redmi-4x --> http://gsmusbdriver.com/driver/8597/)

None of these worked. The Xiaomi Mi Flash Tool only contained unsigned drivers which I could not install. For the rest of these packages, Windows could not find any matching drivers in them. I then selected several drivers from these packages manually and installed them despite Windows warning me that this might not work. The drivers did install, but then Android studio would complain with the message: "Installation failed with message Failed to establish session."

Where do I find a working driver for the "ADB Interface" of the Redmi 4X?

Any help appreciated!

Thanks!
[Android Q&A, Help & Troubleshooting] _xray:
Ok, I was able to solve this myself. The error in Android Studio when trying to install apks on the Redmi 4X was not caused by the ADB Interface driver, but by "wrong" settings on the Redmi 4X. I followed the directions in this thread to solve this:

en.miui.com/thread-410773-1-1.html (1st answer, by hackhert)

I'll quote the answer here:

The ADB driver I used is the one that can be downloaded in the Android SDK manager:

SDK Manager -> SDK Tools -> Install "Google USB Driver"

Go to Windows Device Manager, find "ADB Interface" -> update driver -> select manually -> select from list -> all devices -> select folder "C:\Users\Username\AppData\Local\Android\sdk\extras\google\usb_driver" -> select "Android ADB Interface"

Windows will warn you that this driver might not work, install it anyway

Device manager will show "Android ADB Interface" in the category "SAMSUNG Android Phone"
[Android Q&A, Help & Troubleshooting] benluc:
Thank you, this solution works perfectly for me too. Find this two days after looking around and tried thousands things.

Hahaha.... !
[Android Q&A, Help & Troubleshooting] Vikash_:
By doing this step :-Go to Windows Device Manager, find "ADB Interface" -> update driver -> select manually -> select from list -> all devices -> select folder "C:\Users\Username\AppData\Local\Android\sdk\extra s\google\usb_driver" -> select "Android ADB Interface"

It gives message "windows was unable to install your ADB interface" while I am giving right path.
[Android Q&A, Help & Troubleshooting] iLuxi:
Simple way for installing adb drivers for redmi note 4 and others

1) Download & install MiFlash Tool to your pc

2) Connect your phone to pc , automatic driver install will start , wait till it fails. (Skip driver searching on microsoft database wich is "Windows Update")

3) Open Device Manager and find there "Other devices" >> "ADB Interface" , double-click on that and hit "Update Driver"

in the window just apeared.

4) Hit "Browse my computer for driver software"

5) Hit "Let me pick from a list of device of device drivers on my computer"

6) With "Show all devices" highlighted hit "Next"

7)Then hit "Have disk" button

8) "Browse" to "C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Google\Driver" and "Open" there "android_winusb.inf" and hit "OK" and press "Next" with "Android ADB Interface" highlighted.

9) It will prompt you that windows cannot verify driver sources, just hit "Yes"

10)hit "Install that driver anyway"

Thats all , for most users of windows 7 this should work. Some of you may face some troubles on 64-bit Windows versions because of unsigned drivers. Google how to solve this on your OS. Guide was created on 64-bit Windows 7 Professional it may differ a bit for other windows users but you got the point where to find the original driver.

Driver ids used in guide:

USB\VID_2717&PID_FF48&REV_0318&MI_01

USB\VID_2717&PID_FF48&MI_01

P.S. Also mi flash tool has adb and fastboot executables in "C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Google\Android"

i hope you will find this useful. Cheers !
[Android Q&A, Help & Troubleshooting] fede01_8:
I tried all of that too and the ONLY drivers that work is the one that comes on the MiFlash unlock tool.

Open Device Manager. Go "Other devices" >> "ADB Interface" , double-click on that and hit "Update Driver" and manually go to the MiFlash tool folder. There's one inside that name Driver :eek:

Voila

Now you phone will be listed when you type "adb devices" on a cmd windows
[Galaxy Note 4 Themes and Apps] Spotless:
**Mod edit - content removed**
[Galaxy Note 4 Themes and Apps] dicksteele:
While that is special, this is a developers forum and the desire is to assist developers to continue their work.

The same goes for themes. They request payment for the work they did, to encourage them to make more themes.

If no one is paying for their work, what's the use to make more? If they wanted them to be free, they would have released them for free.
[Galaxy Note 4 Themes and Apps] user2k10:
You pay for them or you get put in jail for theft.
[Galaxy Note 4 Themes and Apps] noppy22:
Thread closed.

It is against XDA rules to discuss or suggest ways to avoid payment for software. Forum Rules
[MTCB Android Head Units General] Rhoobarb2005:
RQ0110E

5.1.1

Single DIN

After trying to flash a firmware update that supposedly for my unit, it starts up but only toast messages are displayed on the screen.

I tried the same power/reset for 5 seconds method used for the double DIN units, and it seems like it works, but the screen folds down and I can't get the screen back up to select any recovery items.

Any ideas?
[MTCB Android Head Units General] typos1:
Pumpkin are a seller only - there are no "Pumpkin" units - "RQ0110E" is a made up name, go to settings/about device and tell us your MCU version, this will tell us what device you have, then we may be able to help
[MTCB Android Head Units General] Rhoobarb2005:
TIL, thanks.

RQ00110E is on a sticker on top of the unit. The Model number in Settings says S07.

I cannot get to settings at the moment, like I said, I can only see toast messages.

But this was the version info before I tried flashing it. I made a note of it just beforehand.

MTCB-KLD5-V2.79

Sep 08 2015 20:11:32

Android 5.1.1

Screenshot

http://imgur.com/a/geCCP

It's a single Din unit with flip up screen.

Any help anyone can provide would be great.

I tried updating the firmware because when I plugged the USB DVR camera in, for some reason it disables media audio playback.

I saw that I had an older firmware, and thought I had found a newer version.
[MTCB Android Head Units General] typos1:
The only info we need is the MCU - "RQ00110E" is a made up number by Pumpkin and all MTCB/C headunits are called "S07".

You have a Klyde (KLD) MTCB headunit.

The MCU will not have changed unless you flashed an MCU as well.

Its good to update the firmware, but I need to know what you tried to flash to update it.

What USB port did you use for the DVR ?
[MTCB Android Head Units General] Rhoobarb2005:
It's a shame the whole rebranding thing seems a bit of a mess.

Good to know.

TBH, it does not say Pumpkin anywhere on the unit, box or anything to do with it. It was bought from Amazon as a Pumpkin HU, but nothing else seems to link it to Pumpkin.

I don't think so, it was a single file labelled update.img (see below). I'm not sure what a MCU is.

https://mega.nz/#!lFVVWS7Q!WvezHo2glWLudnsPHcT8godSdI6NvOZUoBNYnqVArUE

from this forum post:

http://www.autopumpkin.com/forum/viewtopic.php?t=1655

The USB connector labelled DVR.

The same as item 1 on the following picture;

http://www.autopumpkin.com/images/11-RQ0110E/1 Din Android 5.1 Lollipop Car GPS DVD Player (15).jpg

(although my connector also had an old ipod connector on it, not just the USB DVR port)

This camera:

https://www.amazon.co.uk/Pumpkin-Ca...qid=1502561032&sr=8-3&keywords=pumpkin+camera

The camera works and records using the software, it just seems to disable the media volume. Disconnect the camera and sound comes back. As per the following thread:

https://xdaforums.com/android-auto/android-head-units/connecting-usb-dvr-disables-sound-t3655299

The radio doesn't work either, and I bought the 12v booster from Pumpkin too, and neither does the bluetooth obd connector :/ not having much joy at all lol.

And thanks for your help so far!

EDIT: OK, having read your links on your profile, I now know what a MCU is :) Bookmarked!

OK, thanks to your wiki link, I think I know why the bluetooth OBD connector doesn;t link, wrong name. Ideally it would be worth getting a rooted firmware with xposed on to run some of the MTU modules.
[MTCB Android Head Units General] typos1:
Forget the pumpkin forum, use [MENTION=6041319]dsa8310[/MENTION]'s 5.1.1 firmware in this thread :

https://xdaforums.com/android-auto/mtcb-software-development/mtcb-mtcc-firmware-t3632100

its rooted and it has Xposed.

I dont know what you mean by the "5 second thing for double DIN units" - not heard of that for any units, but recovery is entered by putting a pin in reset and holding down power until it beeps and the lights flash then releasing reset and then releasing power, AFAIK the single DIN units are the same, or you could try the MTCD method which is just holding power for 10 secs until it beeps then it should enter recovery.

The radio will probably be to do with the setting its on in factory settings, or its to do with your OEM booster, but we can sort that later.

Theres no advantage in using BT for OBD if its going to be permanently wired - BT is for if you want to move the devices around and both the head unit and the OBD device are static, most people use BT for it but I can never understand why - USB OBD is faster, more secure and better, still theres a way to sort it, again we can do that once youve got into recovery and flashed a ROM.
[MTCB Android Head Units General] Rhoobarb2005:
OK, will do.

The 5 second thing was how Pumpkin describe putting their units into recovery, pretty much the same as you said; pin in reset and power, wait 5, release reset, wait 5 release power. Anyway, did that and it may have worked. But I can't tell as the screen closes and will not respond to the screen button to come out. So it may have worked, I just cant see it.

Ok, cool.

It was more the lack of spare USB ports (camera in one of the USB ports, plus I want to put a large HDD in the other, my current 500GB only seems to like the front USB port. I want to keep the front USB free for cosmetic reasons, so will need to buy a drive that needs less power I think.), and I dont recall seeing a usb listed obd as compatible, but nevermind. Bluetooth is what I have, if the xposed workaround works, that will do me.
[MTCB Android Head Units General] typos1:
The rear USB ports are not good, the front is the best, you can try sorting the rears out by adding a powered USB port (ther are threads about it in the MTCB hardware mod section). You can get USB OBD leads that work with Android, I have one, although I have to use it on the front USB, but I have dismantled my unit, added a lead and hidden it behind the unit.

Anyway I m not sure what to do about your screen disappearing, did it disappear when you updated the ROM ?
[MTCB Android Head Units General] Rhoobarb2005:
The screen tries to hide anytime there is power loss to the ignition 12v or the unit is trying to shut down/restart, to the point it can get annoying. It usually responds to the screen open command. Just not after doing the power and reset thing.

When I entered recovery mode when I flashed the bad firmware I did it from the settings menu, the screen went in then, but did respond to the open command.

EDIT: To clarify, the screen opens and closes fine when not attempting recovery mode.

Can do a video of the behaviour if need be :)

EDIT 2: Supposing that it is in recovery mode, just unseen, can I not just rotate the volume knob counter clockwise one click and hold the power button to accept the "img/mcu from USB" option (working from a bad memory here)?
[MTCB Android Head Units General] typos1:
So the problem atmo is that the screen is black apart from toast messages ? If so then put [MENTION=6041319]dsa8310[/MENTION]'s firmware on an sd card, put it in the sd slot (the gps one if you have 2) and hopefully it will autosense the update, if it does you ll get a toast asking if you want to continue, touch ok.

---------- Post added at 09:31 PM ---------- Previous post was at 09:25 PM ----------

I would also try updating the MCU to MTCC KLD5 v2.97 (find it on either of the fileservers in my signature) - KLD Lollipop ROMs usually only work with MTCC MCUs and the very last MTCB MCUs (2.85 and 2.86), I notice your MCU is MTCB v2.79 and I m surprised its such a low version, [MENTION=6041319]dsa8310[/MENTION]'s ROM has a feature that allows L ROMs to work with ANY MCU, which is one of the reasons I suggested you flash it, but updating to an MTCC MCU is a "belts n braces" approach.
[MTCB Android Head Units General] Rhoobarb2005:
Yup, you get the lollipop splash, then 2 droids dancing around each other as the boot screen. Then to black (booted) If I insert an SD card the toast message pops ups saying sd card mounted, I think the volume slider works as well. And the "shutting down" splash works too.

Will do, will report back in a few, need to find my sd adapter :/ lol
[MTCB Android Head Units General] typos1:
Right, I think its the fact that the MCU is too old a version of MTCB/not MTCC.

You got no sd card slot ??
[MTCB Android Head Units General] Rhoobarb2005:
"SD GPS Card mounted", but nothing else. Same in the other sd port :(

OK, does that help us at all?

2x micro SD. on the front of the head unit, yes. I just didn't have the means to get it from my computer :) If it isn't usb I usually just use bluetooth or wifi.

I found an old micro- sd to usb, so all good. Well at least as far as that goes.
[MTCB Android Head Units General] typos1:
The GPS port is the one you want, you can update in recovery but if you cant get into it . . . you have the MCU on the root of the sd card ?

It helps in that I think I know the problem.

Try turning it off and on again.

You can try seeing if it auto detects the update on usb not sure it will though.
[MTCB Android Head Units General] Rhoobarb2005:
Only .img file that came with the download you linked to get.

Is it bad?

It's a bit late to do that tonight, darkness spoils the plans, will have to be in the morning.

Will give that a try too.

And again, thanks for your help so far :)
[MTCB Android Head Units General] typos1:
I d do the MCU update first, as I said earlier you want MTCC KLD5 v2.97 its on both the fileservers on my signature, it takes a ciouple of mins to do and should restore your screen. Then you can do the ROM update tamoz.
[MTCB Android Head Units General] Rhoobarb2005:
OK, tried it, and only the "card mounted" toast message popped up, nothing else.
[MTCB Android Head Units General] typos1:
Try rebooting with the card in the unit.
[MTCB Android Head Units General] Rhoobarb2005:
Ok, tried it. Still no joy.

Going to try with the mcu and image on the usb then right turn the volume knob 3 times then hold
[MTCB Android Head Units General] typos1:
Hmm, this is where it gets tricky as usually you d just go into recovery, have you also tried with the ROM in the sd card ?
[MTCB Android Head Units General] Rhoobarb2005:
SUCCESS!!!

Firstly though, out of frustration I thought I would hold the screen instead of letting it hide when I go into recovery mode. Well, it briefly flashed the Lollipop logo, and then darkness. Oh well :(.

So I tried blind selecting USB and clear, nothing, tried another short click and long click, nothing, tried another short click and long click. It restarted. So I think it does go into recovery mode, just that the display is not visible. Tried again, this time with; single click, long click, wait. If nothing after a few minutes, single click, long click, wait, repeat, etc.

On the third or so go, after waiting it restarted itself. Back to the dancing droids. I thought I had just got the reboot action again :(.

Only this time the dancing droid stayed for minutes instead of seconds. Screen closed and opened again, more dancing droids. Then a welcome screen!!! :D

http://imgur.com/a/IRxb9

It must have been pure luck I hit the right entry. But it seems to be working better than it did before, looks a lot nicer than it did before and the music works WITH the DVR camera now!!

Plus I have a rooted, debloated and xposed HU instead of the crippled stock one!!!

Cool beans!! A bad day, turned into a great day :)

So... Thank you very much for all your help. If it were not for your help and guidance (and perseverance) I would be quietly rocking in the corner, sobbing.

Donated, enjoy a beer or two on me! :highfive: A little token of my thanks!

Now if only I could get the pesky radio working :confused:, well, another day :p
[MTCB Android Head Units General] typos1:
Cool !

Often, if the screen is blank you can try going into recovery and doing a blind flash like you did, but I never thought of suggesting it cos the screen was going in ! Well done for that.

And many thanks for the very generous donation - red wines my thing, it ll buy me a bottle :)

The radio should be easy, probably a case of going into factory settings and selecting the right tuner type, did it ever work ?

Was the mcu on the sd card as well ? Cos if it was you should now have an "MTCC" unit.

Do you know how to get into factory settings ? Password is 126, often when the mcu is updated the settings change, you need to :

Change the radio area to "Europe" (I ve assumed youre in the UK cos your car is RHD, of course it could be Japan, Australia, S.Africa, etc lol)

The logo to your car type

The volumes to your preference (I wouldnt bother changing them unless and until you find a problem with the volume of anything on the unit TBH)

The BT to "BC6"

DVD to "yes"

TV to "no" (assuming theres no tv tuner in your unit)

CAN Bus to "no" (unless you have a CAN Bus decoder in which case your ll have to change it to your car type and the name on the decoder - Raise, Union etc)

iPod to "no" (unless you have one)

And the radio tuner type - your ll have to play around with the 4 or 5 types there are if you dont know what one it ll be on, I d try TEF6686 first as most KLDs have this tuner, if not then try TDA7786

On the last screen you need to check "RDS" ,"RGB LED" (I think those units have user changeable LEDs), "Rudder" (its Chinglish for RHD) and "keylight" (if you want the LEDs on always, I like them on cos its the units off in the dark you need to see the buttons to turn it on, but its personal preference).

Hit "apply" then exit, it ll reboot, you may have to go back to change the radio tuner if TEF6686 doesnt work
[MTCB Android Head Units General] Rhoobarb2005:
Thanks, it was such a relief to see the welcome screen.

Whatever your poison :)

When I got the unit, it didn't work. I am not a big radio listener, so was not too bothered for a while, the real estate behind the HU is limited at best, I did not relish the thought of trying to pull it all out to check what might be wrong. I bought the DVR camera a few weeks ago, and thought I would buy the 12v booster and sort the radio too as it would be all out. Fitted the camera and the 12v booster and then I hit the no sound problem when the camera was plugged in. So I look in the factory settings, while browsing them I saw the radio settings were set for the wrong IC. Changed it to the proper one, and now I get static and maybe 2 stations that come through as poor quality.

Yes, I thought I would gamble and put both on, hopeing they would both install. Will it now say on the info that it is a MTCC?

Yep, password was the same.

Done, yes am UK.

It has come up a couple of times when using it earlier about safety volume or something similar. Not sure what that is to do with, it certainly wasn't there before.

OK, OK, OK, No not Canbus, and no, no ipod (I cut the connector off the cable to try and save some space)

If only 1 option gives any response at all, then I think it is TEF6686, it was on Pumpkin's sales blurb.

No, no changeable LED. Just blue. IIRC the upgraded 6.0 single DIN HUs do, along with a wifi aerial and external mic!

Just a few question, as you seem like you know a lot about them.

It does seem to be a common theme with these HU's, but is there any way to increase the brightness? On a bright but overcast day it is hard to see, any sunlight and you might as well put the screen in.

Are there any good xposed modules, I could do with the one that allows me to use my BT OBD.

Any way to teak the LCD display on the front?

Any way to change any settings for the remote control?

Again, many thanks for all your help.!!