yashsingh1/xdaforums huggingface dataset:
[IDEs, Libraries, & Programming Tools] acermedo:
Does anyone know how to upload SystemUI.apk and Framework-res.apk to UOT with galaxy y

beacous I don't have any pc and when I click (select file) on UOT with mobile nothing happens
[IDEs, Libraries, & Programming Tools] niranjan94:
Hi ... this is the forum for App development related queries ... This forum is not for ROM-related queries like porting CM, MIUI, AOKP, PA etc etc (or) Problems with scripts like Link2SD, Mounts2SD.... Please post your query in the proper forum ... Thank You ! :D

But anyway ... It is not recommended to use your mobile with UOT kitchen (as that site is not mobile friendly) .. But Upload should work.. Make sure you have a file manager installed ... ( Solid Explorer, Root Explorer, ES File explorer prefered )
[Galaxy S III Q&A, Help & Troubleshooting] OmniSliver:
Hi, so I was trying to follow this guide (I know that it's for I9305, but the procedure should work for I9300), but when I connect my phone to my PC, I get the message "USB device not recognized".

The devices manager lists the phone as "Unknown Device", the device status is "Windows has stopped this device because it has reported problems. (Code 43)" and the hardware Id is "USB\CONFIG_DESCRIPTOR_FAILURE".

I only have this problem when I put the phone in diagnostic mode ("RNDIS + DM + MODEM", "RMNET + DM + MODEM" or "DM + MODEM +ADB"). It works fine if I use the other modes.

I tried with various Samsung USB Driver versions (1.4.6, 1.5.09, 1.5.18 and 1.5.25) and roms (stock, omega and cyanogenmod, currently with stock 4.1.2), all with the same result. I'm using Windows 8 x64.

So, I wan't to use QPST but I can't, so any help would be greatly appreciated. If you need any more info just ask please.
[Galaxy S III Q&A, Help & Troubleshooting] JJEgan:
Whatever you are trying to do that is for qualcom cpu

Basics read first.

http://xdaforums.com/showthread.php?t=2344125

Critical you read the first two posts
[Galaxy S III Q&A, Help & Troubleshooting] OmniSliver:
Thanks so much, I didn't realize that my processor wasn't a Qualcomm.
[Galaxy S III Q&A, Help & Troubleshooting] Zobom:
Please, how did you solve this problem? I'm trying for hours and still is unknown device in diag mode! Help!
[Galaxy S III Q&A, Help & Troubleshooting] mattia_sp:
Unknown device (i9300 with 4.3 original rooted)

I'm in the same situation after I select: rmnet+dm+modem

Install and reinstall several version of usb driver, cable, port etc.. but when I select rmnet+dm+modem or option under my pc doesnt't install driver for it because it sees an unknown device
[Galaxy S III Q&A, Help & Troubleshooting] jmaher1023:
WHY?!?!?

Why are there no REAL helpful answers to these questions? Everyone is just saying "read this, or see that post..." but no real specific answers for fixes!!! I have been all over Google looking for a solution for this problem! I can get to the USBSettings menu on my 9300 by dialing *#0808#, but when I select RMNET+DM+MODEM, my computer no longer recognizes the device! Installing Samsung drivers did not help...my question is, does anyone know what drivers I need for Windows to recognize the phone?

Thanks!

~Jim
[Galaxy S III Q&A, Help & Troubleshooting] boomboomer:
You are looking for an instant easy answer to a varied and complex problem, made worse by people who don't read or understand before they break things.

This long dead thread you resurrected is a case in point, just read the first two posts to understand how a situation is made worse by impatience.
[Galaxy S III Q&A, Help & Troubleshooting] kingtemoo:
Please Really Help

Same exact problem I am having I just dont seem to get what to do now.

I have a NOTE 2
[Galaxy S III Q&A, Help & Troubleshooting] Droidsan:
Hey Jmaher, did you ever get to solve this? Seems getting these RMNET+DM+MODEM Diagnostic usb settings recognized on PC COM Port is one hell of a job! Trying to get Note 3to work with QPST. Kindly respond bro...
[Galaxy S III Q&A, Help & Troubleshooting] jmaher1023:
I never did! I pretty much gave up. It was a customer's phone I was working on, so I just gave it back and told him we couldn't fix the issue.
[Galaxy S III Q&A, Help & Troubleshooting] miniminus:
thought id through my thoughts and troubles into the bag ...

ive got a troublesome phone, is a I9300 (so the international version) had the s5 sensation rom on it..

went odd, wouldnt run/install any apps etc (errors out with -54 i think it was) then week or so passed (as not got round to fixing it as it stillworked as a phone)

and after it went through a stage of switched it self off...

the batt went flat, and then hung on samsung logo...

after trying to sort it out, reflashing a backup, and then back to original ODIN files etc .. still hung, but would go to download and recovery with many compliants ..

after goose chasing them, got it down to just complaining about the /EFS

so after trying to fix this one, an nowt worked, i formatted /efs ... and yeah ! all boots !

so ive now got a "blank" efs, but a booting phone ! (but no network)

ok so in pretty much 100% of all tutorials in fixing a imei/efs problem it stems on putting phone into "diag or diagnostic" mode

which EFS Pro will do for you, or you can *#0808#

BUT i to get the "unkown" device too ..

and like the posters here all other options of modes work/install, but the programs for imei repair etc need diag mode

and from what ive read (the posts linked on the first couple posts here, and whats actually in those links)

suggest that either to "take it for repair" or talks about imei repair progs in diag mode with CDMA qualcomm devices, and CDMA devices are US devices

so i am lead to believe that as the I9300 being international version, doesnt actually have a "DIAG" mode, only CDMA US versions ? ! ? is THIS what your all hinting at but not saying ???

so thus no drivers work for it, and thus "unkown device"

and the only way is for a appropriate "box" that im thinking emulates, or works like diag mode !?

is there a way to force/flash diag mode for international s3's ?

am i even correct in these assumptions ??!!

---------- Post added at 06:31 PM ---------- Previous post was at 06:11 PM ----------

thers NOTHING about qualcomm, and what it is and what isnt in phones in any of the quoted links :(

or anything related to CDMA

but am i presuming right what i said above, that the international version doesnt "have" a " diag" mode due to the type of processor used ?
[Galaxy S III Q&A, Help & Troubleshooting] OmniSliver:
I couldn't find any diag mode that worked. I had to send my phone to a repair shop that charged me around 20 USD.

Also, QPST (Qualcomm Product Support Tool) works only for phones with a Qualcomm processor.
[Galaxy S III Q&A, Help & Troubleshooting] kaizokush:
not qualcomm

Im stuck at RMNET+DM+MODEM "Device not recognized", seems i need the driver for it. what can be done if the device is not a qualcomm CPU?

Model : GT-I9300T
[Galaxy S III Q&A, Help & Troubleshooting] volkan.akbulut:
enable cp logging in recovery ....
[Galaxy S III Q&A, Help & Troubleshooting] sharky481232:
you are the man. thanks, that worked like a charm.
[Galaxy S III Q&A, Help & Troubleshooting] no captcha:
95
[Galaxy S III Q&A, Help & Troubleshooting] elisir:
volkan.akbulut gave the solution. Follow these steps:

1. Turn off the phone

2. Enter Recovery Mode by holding Vol Up + Home + Power

Release the buttons when you see "Recovery booting" on the left-top corner.​

3. Use Vol Down button to select Enable cp logging and press Power

Now try to connect. Drivers will be installed.

Good luck.
[Galaxy S III Q&A, Help & Troubleshooting] jg2013:
THANK YOU... holy $%^&* i wish this was referenced in the OP on the front page (missed it on page 2 days ago).

S4 i9505 on win7 64, samsung driver 1.5.59.0 for use with QXDM
[Galaxy S II Q&A, Help & Troubleshooting] cowen2006:
If anyone has any suggestions on good ROMs? Slimbean 4.3 build 1 is very very stable for me ATM but like a change and what best battery life possible
[Galaxy S II Q&A, Help & Troubleshooting] E.Cadro:
With that being said ^^^^^ Thread closed
[T-Mobile Samsung Galaxy S II SGH-T989] MrRogers642:
I'm going to start off with some background information. I have been using the SMS app Handcent for a little while now, and it has been giving me a lot of trouble with MMS messages with them not sending nor receiving, whereas the stock messaging app could receive them.

Alright, and now we are into where I screwed up... I read that if you made the stock messaging app a user app and handcent a system app, then the permissions will correct and I would be able to send/receive the MMS messages. However, when I made the stock messaging app a user app, it deleted itself. I figured it wouldn't be so bad after I got handcent to work, but handcent still doesn't receive/send MMS messages, and I have no way of sending/receiving them because the stock messaging app got deleted. So, I was wondering if there was a way to get back my stock messaging app for Android 4.1.2. If anyone could help me fix the handcent thing as well, that would also be greatly appreciated.

Thanks ahead of time!
[G2 Q&A, Help & Troubleshooting] nitric13:
Something bout the stock USB to microusb cable for the g2 is special....I need another cable for car charging purposes. POINT ME IN THE RIGHT DIRECTION PLZ!!

My dual usb car charger discharges 2.4amps. I tried all my usb to microusb and i can only output 900mA and (slow charge mode popsup

I use the stock usb to microusb cable and WAM.....charges at 1850mA :confused:
[Samsung Captivate Glide] mer80cedes:
Hello,

Captivate Glide i927 replaced cracked screen

I replaced the cracked screen assembly and installed a new ribbon. The lower lights (home, search, back button etc) work and also the keyboard lights. The ATT chime sound works too but the display does not light up when powered on.

Connected the phone after replacing ribbon/ screen to the comp for Kies to back up and it is saying the phone is locked. It is the lock code that you set to keep others from accessing. Since the display does not light, the correct code can not be placed in. Can someone please place a picture of the unlock screen mode here? The display touch pad works so if the position of the numbers can be acquired, this may help me to get the phone files accessed and reset hoping to get the display working.

The phone is not rooted and upgraded to the ICS as of October 2012.

Up $86 for the ribbon and new screen and the repair shops want $100 plus the cost of possible parts needed. Would like to try my best so this route can be avoided.

Cheers,

Robert
[Samsung Captivate Glide] mer80cedes:
By now the phone SIM is locked out. I believe there is a way to reboot the phone through a computer?
[Samsung Captivate Glide] AndyYan:
The only way I can think of is rebooting via adb. If you're not rooted (the "reboot" command in shell requires root, i don't know if "adb reboot" wants it), or haven't even turned on USB Debugging at all, then you're doomed.

However, since Odin-ing is not that hard (only requires several key pressing), you could try Odin in a custom recovery (or not, if you already have one), back your system up to external SD in tar or other formats, and then extract the data you want from the backed-up packages (I've done this with tar packages). If you ever need the screenshot of a particular version of recovery, ask again in this thread and I think we'll be more active (and easier) to help.

Sent from Samsung Captivate Glide @ CM10.1.2
[Samsung Captivate Glide] mer80cedes:
Thank you AndYan.

This Captivate has only been upgraded to the Sandwich version. Non-rooted nor modified in any other way. The only reason to remove the files is due to it having solar cell module prototype designs and concepts on it (Reason why it can not be shipped out for professional repairs). Since most of the information was wrote on paper, it's best to just wipe the phone out completely to get it back to working condition for use again.

This is quite interesting learning about programming and such since I have never done this before. Just like building cars, took many many years to do and this programming is just another cool thing to learn about :)
[Samsung Captivate Glide] mer80cedes:
It takes a special knowledge and experience to understand the programming of Odin and phones which I do not comprehend, I will be destroying the motherboard with a hammer and tossing it out. It is way too much to understand how to set coding and such. Best off investing in another phone and moving on.

The parts that will be saved if anyone can use will be the ribbon strip and also brand new display screen.

Paid $86 for the display and will sell for $75 free shipping with insurance.

Ribbon strip will be $20 free shipping with insurance. If both are wanted $95 free shipping.

Since I do love the Captivate so much another will be purchased.
[Samsung Captivate Glide] AndyYan:
You mean you smashed your Glide?! :( God, I just had mine 5 days ago. Anyway, hope my tip still helps when you're in any smaller trouble next time.
[Samsung Captivate Glide] mer80cedes:
No way lol! Only the mother board will be smashed to save the data on it from being used again. All of the other parts will be saved since another Captivate will be getting purchased.
[Samsung Captivate Glide] AndyYan:
That's still sad to see. Why not just solder off the storage chip, somehow destroy it, and find a similar model chip to replace it?

EDIT: I guess the Samsung-proprietary partition table and some data on special partitions like EFS are not reconstructible on a blank new chip. Then you did the easiest choice possible. :)

Sent from Google Nexus 4 @ CM10.2
[Samsung Captivate Glide] mer80cedes:
Is it cool for someone to take a photo of their Captivate i927 when it is at the display for the personal unlock code (PIN). It will make a good reference point enough to possibly use my touch screen to unlock my cell to reboot. Just have to get the location of the numbers and also the OK button.
[Samsung Captivate Glide] mer80cedes:
After many hours research (great learning experience), the phone was done on master reset without needing to see the screen. At least now it can be sent out to get repaired without the personal information being potentially taken by another.

Done :)
[Samsung Captivate Glide] AndyYan:
Woohoo, so no need to smash anything? You did an awesome deed to keep a nice phone alive :)
[Galaxy S II Q&A, Help & Troubleshooting] thebigdawg:
just a quick question...

i had previously installed lightening rom on my samsung galaxy s2 gt-i9100. recently i wished to upgrade to jellybean however as my home button is broken/recently stopped working i cannot enter into recovery mode to use odin. kies does not recognise the os so it will not allow any upgrades.

could anyone advise me on any options i might have, im new to all this so i would really appreciate some assistance from the more knowledgeable members on this site. is there any way of breaking into the recovery/download mode without having to go thru the power/volume down/home key route?

thanks in advance for any assistance
[Galaxy S II Q&A, Help & Troubleshooting] Hopper8:
Yes there's ways of booting into download mode. I'd advise against it though. Why? Because messing with the software with no escape route is playing with fire. If something goes wrong and you need the key combo to boot into recovery to factory reset, you're toast.

Moral of the story, get the hardware repaired before you continue to mess with the software.

Sent from a galaxy far, far away
[Galaxy S II Q&A, Help & Troubleshooting] cowen2006:
If u can get in phone. Download superuser....it will ask to update binary via cwm and boot u into recovery mode automatically. Must be an app that in playstore that does it to?? Search.
[Galaxy S II Q&A, Help & Troubleshooting] Karpfenhai:
Adb reboot recovery?

And there's a home button fix for certain kernels..

Tapatalked from my Galaxy SII
[Galaxy S II Q&A, Help & Troubleshooting] MistahBungle:
Hopper is right, 'messing' with the phone with busted hardware is asking for a 116gm plastic paperweight. Do the smart thing & fix the button first.
[Galaxy S II Q&A, Help & Troubleshooting] Karpfenhai:
Do you think it's really broken? If I remember right, it's a problem with litening Rom, it had a feature like "enable home button" so it could be a software issue, full wipe before flashing new Rom should fix it...afaik..

Flashing a touch recovery (dorimanx kernel) can also work around this.

Tapatalked from my Galaxy SII
[Moto X General] shane1:
Within a few days of release our new Moto devices have root with safestrap not far off. With this information id like to help developers get their hands on this lovely device. We need to raise the full retail value of the phone unless we can find one cheaper somewhere. Again this is for a Verizon consumer edition moto x so speed would help because future updates on the phone will be harder to root! if you need to check out some of Nitro's work here is a link: http://www.elementalxdesigns.com/eclipse/forum.php . Ive been using his roms since my Droid 3 and love his work. If you are able to donate please go to the link below and also post your donation amount. Thank you

http://www.elementalxdesigns.com/ec...ng-Eclipse-Rom-to-the-Moto-X!&p=8205#post8205
[Moto X General] bso44:
The link for Nitro's work is no good.
[Moto X General] shane1:
Sorry about that I redid the link should work now.
[Moto X General] nitroglycerine33:
Thanks guys!
[Moto X General] shane1:
I know I can't be the only person that would love to have Eclipse ROM on their moto x
[Moto X General] mazubo:
I'm all for it!
[Moto X General] WolfsFang:
God yes I loved your work on my Droid x2 and s3.
[Moto X General] shane1:
If people want eclipse on their x we need donations. It would be extremely hard if we can't get him the phone.
[Moto X General] nitroglycerine33:
If you want to see Eclipse on the X please stop by Rootzwiki and leave a comment supporting Eclipse!! Thanks!!

http://rootzwiki.com/news/moto-x-developer-edition-giveaway-round-3-developer/
[MDA II, XDA II, 2060 ROM Development] wokmanphone:
Hi guys. I have the following:

ROM Version: 1.60.00WWE

ROM Date: 12/03/03

Radio Version: 1.08.00

ExtROM Version: 1.60.44

Of course, I don't know what any of that means but would appreciate one of the Gurus on this site to suggest a suitable upgrade for me. Something tried, tested and suitable for technophobes like me (ie simple download, copy to device and run .exe?).

I am living in Singapore so a suitable Asian version please.

Also, does anyone have any problem with the ringtones on the XDA II (Himalaya)... I am forever missing calls because it just doesn't seem loud enough. My old mobile/hand phone had the neighbours complaining of noise pollution.

Is there a solution for this?

Thanks
[MDA II, XDA II, 2060 ROM Development] patrick_dube:
Try the SE CHS version, located on the FTP site. You should.
[MDA II, XDA II, 2060 ROM Development] imablackhat:
I had the same exact device information

ROM Version: 1.60.00WWE

ROM Date: 12/03/03

Radio Version: 1.08.00

ExtROM Version: 1.60.44

and tried the CHS translated and it made the screen all skippy and it was impossible to setup, etc. So what I did was I just used the genuine wm2003se in the wiki and created my own extended rom, much easier ;D
[HTC One X] iroczu:
hey everyone i just got a htc one x yesterday from Telus Mobility since my htc evo 3d has been acting up, i'm trying to root it and tried few different options like one click root, all in one root and so on. and now i'm down to trying to get the token code but when i submit it to htcdev this is the message i always get

"Unlocking Bootloader Failed!

We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.

Error Code: Invalid Bootloader Token Length.

Error Reason: The submitted Token appears to be the wrong length and won't work"

now when is cmd prompt when i execute command "fastboot oem get_identifier_token" it only shows the Bootloader token and on htcdev it shows I should have Bootloader and a Info window with token information am I doing something wrong?

not sure if this helps but I can't get into bootloader manually i have to use a program on my laptop to get into itwould like to unlock that and s off also
[HTC One X] iroczu:
hang on i finally got it to submit!
[HTC One X] iroczu:
ok well now i'm stuck at the sending unlocktoken
[Verizon HTC One (M7)] Sonic2756:
Found a copy of HBOOT 1.44 that can still be hit by revone lying around online. Figured this would be useful to anyone who was super paranoid about their phone randomly S-ON'ing.

Download the zip Here and reboot to RUU (fastboot oem rebootRUU)

Flash the zip (fastboot flash zip zipname.zip)

Done.

Edit: You're going to have to edit the android-info.txt to match your device info.
[Verizon HTC One (M7)] GrayBoltWolf:
So, basically this gives us s-off people a plan-B if we accidentally do something wrong?

HECK YES!!!!!

I will flash this, then go S-On to protect my sweet sweet phone from bad flashes.

Edit:

Have you actually tried this?
[Verizon HTC One (M7)] Sonic2756:
It flashed no problem. I couldn't get revone to kick to me to S-ON. However whatever it uses to lock/unlock the bootloader works and the hboot version is just 1.44.0000 so I'm assuming its revone'able. Fastboot wouldn't do it either due to hboot signature checks. Do you know another way to get S-ON?
[Verizon HTC One (M7)] GrayBoltWolf:
Oh, that's a problem isn't it?

How would we go about getting back on 1.44 then?
[Verizon HTC One (M7)] Sonic2756:
fastboot oem writesecureflag 1 works.

fastboot oem writesecureflag 3 fails due to hboot check.

I'm not sure if revone offers the ability to turn S-ON actually, I'll keep looking into it after my homework is done.
[Verizon HTC One (M7)] GrayBoltWolf:
After your homework, go s-on, and then try to s-off again with revone to humor me and make sure it works.
[Verizon HTC One (M7)] Kraizk:
What is the date on that 1.44 iirc anything after july can not be revone'd
[Verizon HTC One (M7)] Sonic2756:
Probably due to my GPE RUU. Gonna flash back to stock and try again.
[Verizon HTC One (M7)] GrayBoltWolf:
1.44 as a whole can't be S-Off short of a java card I am pretty sure.
[Verizon HTC One (M7)] 123421342:
No if it's the one before the newest hboot you need to run revone as su in shell otherwise revone works
[Verizon HTC One (M7)] GrayBoltWolf:
Sorry, I had myself confused.
[Verizon HTC One (M7)] Lykarsis:
I'm pretty sure 1.45 is the on that was patched.

Sent from my HTC One
[Verizon HTC One (M7)] Sonic2756:
This one says May 3, 2013. Also even after flashing back to stock, trying to S-ON with 1.44 flashed, fastboot gives me the hboot verification error.
[Verizon HTC One (M7)] Sonic2756:
Eh. Apparently you can't S-ON with even a older stock bootloader. Which is probably good because apparently the phone would have refused to boot with S-ON and 1.44 flashed. Either way I would leave 1.44 flashed as a just in case. Especially since it's not an easy fix if something S-OFF related goes wrong.
[Verizon HTC One (M7)] andybones:
Very nice bro, this will help keep many people feel safer that don't know entirely the full risks involved with S-OFF
[Verizon HTC One (M7)] lluke04:
So, when I get my phone back with S-Off I should flash this file to downgrade bootloader to 1.44? Do I keep it 1.44 and flash roms as usual? Sorry for the dumb questions... Just don't want to mess up my phone. :)
[Verizon HTC One (M7)] andybones:
messing with hboot is a perfect way to do just that actually.

wrong hboot file.,

hboot file not downloaded fully (corrupted)

it is (Was) back on the inc4 you'd have a bricked phone with no way to fix it, except maybe jtag

but if Sonic confirms it safe, I'd trust him and just double check that md5 :)