yashsingh1/xdaforums huggingface dataset:
[Palm Treo 750] drakmog:
Anyone know how to be able to Talk on the Phone (Using Voice) while tethering to a PC / Mac , I know I can talk on the phone while using PIE and other internet based applications on the Treo, but NOT WHEN I HAVE IT TETHERED via Dial-up Networking (either via Bluetooth or USB). Basically I have tried both, and am using a MacBook Pro, and successfully tethered to the internet through both BT and USB but it HANGS UP if I make a call (and I presume it hangs up when I receive a call), but either way it does not treat the TETHERING the same as using INTERNET on the Treo, is this just some Registry entry thats causing the problem or something?

Please help I have been trying 10098098034298 things to get it to work; however I only have a VERY limited knowledge of Windows Mobile 5.0 and am pretty useless. If someone could even just give me insight on what settings or registry entry(ies) deal with this I could play around with it an post any results once I stumble upon them...

Thank you so much in advance!!!!!!!!!
[Palm Treo 750] doedoe:
It all depends on the network connection you have.

GSM/GPRS doesnt support Voice and Data where UMTS does.

Make sure that you have a 3G connection.
[Palm Treo 750] drakmog:
Yes I do have a 3G connection, this same thing (Tethering when using Voice) works on my LG CU500 flawlessly both when using USB and BLUETOOTH to tether, no drop in speeds and voice is crystal clear.

Not sure if its the way in which I am dialing up or something, or if its some bug in the 750. let me know if you guys can helop. THANKS!@!
[Palm Treo 750] muller_1:
Go to Menu>Preferences>Phone Settings and select the Services tab. Select the band selection and make sure to turn off auto and bind to UMTS only. If you are in auto and connected to GSM network and try to place a call while connected to DUN, thte call should suspend for a total of 13 minutes before disconnecting. If you are selected to strict UMTS then you should be OK for DUN and voice.
[G3 Q&A, Help & Troubleshooting] ZigZaGz:
First off this a modified version of the LG G3 F400K10G build prop. Main attempt of this is to enable BOTH LED with individual Text Message tone in the stock Contacts app. IF done correctly it will allow use of message tone notifications for each of your contacts. Be warned when the mesagging app is open I think the default notification noise is used, not sure why this is but this is a temp fix really to enable this feature on the LG G3 F400K10G. I imagine it would work for most fo the F400 models but I cannot confirm as my wife only has the F400K model. This will also enable the 4G LTE icons commonly found on US phones in the status bar it also does away with the dual clock on lock screen and Roaming setting in the settings. The features are there but region specific, so on to the directions.....

1------>Device must be compatible with build prop LG G3 F400K10G recommended

2------>Device must be ROOTED and have R/W access to /system folder because this is where the build prop is located

3------>You must be able to set permissions properly or you device will not boot, usually rw-r--r-- or owner-> Read, Write Group-> Read only Others->Read Only

4------>Know what you are doing and how to restore phone from TOT or mod thru ADB just incase. I am not responsible for YOUR phone(mistakes)!!!

5------>Back up exist build prop as you see fit for example name it build.prop.bak or even copy it to SD card or PC.

6------>Download and extract the build.prop from the zip folder. ZIP Folder is

NOT

Flashable!

7------>Use your preferred Root Explorer to copy and paste and set permissions and back up as needed.

8------>Once you are sure everything is completed from Step 7 the reboot your phone and verify changes

9------>Feel free to mod the build prop to meet your needs for those advanced users.

Enjoy!
[General Questions and Answers] hejsek:
Hi,

I bought Lenovo S860, 1 GB RAM version and upgaded Android to 4.4.2 VibeUI 1.5 but it doesnt have gapps and there is chinese language everywhere. I trayed to root it by Vroot 1.7.3, SP flash tool to instal recovery or Root genius. Everything by manuals but nothing worked. Do you have some advices for me?
[Android Q&A, Help & Troubleshooting] ksatyaki:
Hello guys!

I have a Huawei Ascend Y300 phone.

What did I do? - I was trying to expand the data partition. So I tried partitioning my sd card (external flash). I was very careful not to touch anything that said blk0 in /dev/mmcblk . My external flash was at /dev/mmcblk1 and the internal flash was at /dev/mmcblk0. I was clear and was doing everything right. But, I formatted the /dev/mmcblk0p2 accidentally while copy-pasting the code :crying: :crying: :crying: :crying: ....

Then I did "reboot to recovery" from ClockWork Recovery. (I was running a CWM recovery and CyanogenMod, very smoothly with no problems in the past 2-3 months).

That was the last time my phone was ever alive. :crying:

How is it now?

Super bricked with the following symptoms

- Power button / volume buttons won't work.

- The phone won't turn on in any mode whatsoever.

When I ran lsusb, the only mode that was detected was Qualcomm modem.

I used some tutorials and QPST to do some 'fixes'. It didn't seem to work though.

The tutorial I referred to was this: http://xdaforums.com/showthread.php?t=2341320

I only went till getting the phone recognized as an sd card (even when the battery is off). Power buttons still don't work. On linux it shows 4 partitions:

/dev/sdb1 20KB

/dev/sdb2 150KB

/dev/sdb3 5KB

/dev/sdb4 600KB

Unallocated Space 3.64 GB

I am stuck here now. Is there a way I could simply flash an image/kernel onto this space and get my phone working again?

I have a few questions:

1. Is this a hard-brick? Can I get my phone working again?

2. Can the partition where fastboot or boot lies be deleted?

3. If the boot manager is deleted, the phone will not know what to do when it is powered on right? So it will look as dead as it looks in my case?

4. Are there any parts of the phone that are write proof?

Any help is greatly appreciated!

Thank you so much.

p.s. would it not be so easy if phones had BIOS like computers have - on a real ROM or EEPROM and not flash ? And if android came in a bootable flash SD card; so that we could boot from SD card and install android like we install other OS's ....?
[Android Q&A, Help & Troubleshooting] darkspr1te:
OK, before you follow anymore "guides" let's try and get a understanding of what you have, where you are and where its possible to go from here.

Start by researching and posting about the device, its CPU etc, I can help once I know what it is, I don't have time to research every device I get asked to look at. Check the partition super thread too and see if your device is listed.

darkspr1te
[Android Q&A, Help & Troubleshooting] ksatyaki:
The processor is a Snapdragon S4 MSM8225 - the same is used in HTC Desire SV, HTC Desire X, Huawei Ascend G510, LG Optimus L7 II

http://xdaforums.com/showthread.php?t=1959445 = This thread doesn't have my phone's info. Is this the one you were talking about?

Thank you so much for replying!!!

Chittaranjan
[Android Q&A, Help & Troubleshooting] rophaq:
try this might help you unbricking your device : http://en.club.vmall.com/forum.php?mod=viewthread&tid=13433&highlight=unbrick+huawei
[Android Q&A, Help & Troubleshooting] darkspr1te:
That guide seems to be aimed at mediatek chip set.

---------- Post added at 09:00 AM ---------- Previous post was at 08:03 AM ----------

What is the devices pid/vid in Linux or windows, in Linux do

lsusb

at prompt, in windows, goto device manager,
[Android Q&A, Help & Troubleshooting] ksatyaki:
lsusb returns:

Bus 002 Device 003: ID 05c6:9006 Qualcomm, Inc.

dmesg (with battery):

[ 5961.920193] usb 2-1.3: new high-speed USB device number 4 using ehci_hcd

[ 5962.013745] usb 2-1.3: config 1 has an invalid interface number: 20 but max is 1

[ 5962.013757] usb 2-1.3: config 1 has no interface number 1

[ 5962.015114] usb 2-1.3: New USB device found, idVendor=05c6, idProduct=9006

[ 5962.015126] usb 2-1.3: New USB device strings: Mfr=3, Product=2, SerialNumber=0

[ 5962.015132] usb 2-1.3: Product: Qualcomm CDMA Technologies MSM

[ 5962.015138] usb 2-1.3: Manufacturer: Qualcomm, Incorporated

[ 5962.017375] scsi7 : usb-storage 2-1.3:1.20

[ 5963.018250] scsi 7:0:0:0: Direct-Access Qualcomm MMC Storage 2.31 PQ: 0 ANSI: 2

[ 5963.020249] sd 7:0:0:0: Attached scsi generic sg2 type 0

[ 5963.021533] sd 7:0:0:0: [sdb] 7634944 512-byte logical blocks: (3.90 GB/3.64 GiB)

[ 5963.022398] sd 7:0:0:0: [sdb] Write Protect is off

[ 5963.022409] sd 7:0:0:0: [sdb] Mode Sense: 0f 0e 00 00

[ 5963.023242] sd 7:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

[ 5963.030465] sdb: sdb1 sdb2 sdb3 sdb4

[ 5963.036936] sd 7:0:0:0: [sdb] Attached SCSI removable disk

lsusb when battery removed:

Bus 002 Device 005: ID 05c6:f006 Qualcomm, Inc.

dmesg when I remove the battery:

[ 6010.193475] usb 2-1.3: USB disconnect, device number 4

[ 6010.196912] sd 7:0:0:0: [sdb] Synchronizing SCSI cache

[ 6010.197026] sd 7:0:0:0: [sdb]

[ 6010.197033] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK

[ 6010.904344] usb 2-1.3: new high-speed USB device number 5 using ehci_hcd

[ 6011.038520] usb 2-1.3: New USB device found, idVendor=05c6, idProduct=f006

[ 6011.038523] usb 2-1.3: New USB device strings: Mfr=3, Product=2, SerialNumber=0

[ 6011.038525] usb 2-1.3: Product: Qualcomm CDMA Technologies MSM

[ 6011.038527] usb 2-1.3: Manufacturer: Qualcomm, Incorporated

[ 6011.108889] usbcore: registered new interface driver usbhid

[ 6011.108897] usbhid: USB HID core driver

[ 6011.131114] hid-generic 0003:05C6:F006.0001: hiddev0,hidraw0: USB HID v1.10 Device [Qualcomm, Incorporated Qualcomm CDMA Technologies MSM] on usb-0000:00:1d.0-1.3/input0
[Android Q&A, Help & Troubleshooting] ksatyaki:
Any insights yet?
[Android Q&A, Help & Troubleshooting] darkspr1te:
When the device is in sd card mode, does it always boot like.that with the battery?
[Android Q&A, Help & Troubleshooting] ksatyaki:
I don't understand what sd card mode is. How do you put it in sd card mode?
[Android Q&A, Help & Troubleshooting] darkspr1te:
In the log it shows a 3gb partition sdb when battery is in, this is sdcard mode
[Android Q&A, Help & Troubleshooting] ksatyaki:
The answer to your original question is yes.

Thanks.
[Android Q&A, Help & Troubleshooting] darkspr1te:
So the first thing to do is take a copy of that partition, we then analyze it to see what data is not corrupt or missing, we should then be able to re-write the bootloader section and hopefully get it back online, that's a simplification of the actual tasks though.

darkspr1te
[Android Q&A, Help & Troubleshooting] ksatyaki:
Hi,

You make it sound simple. I hope I can get it back online.

I think all partitions are now reset. This, I assume, is a consequence of using QPST. Is this right?

Or does QPST restore important partitions again?

How do I write/flash a bootloader?

Thank you so much for your help.
[Android Q&A, Help & Troubleshooting] ksatyaki:
If this means anything at all, now my phone vibrates for a small duration when I press the power button. It is the same pulse that occurs when the phone boots. But now it keeps giving those pulses (as though in a loop trying constantly to boot but failing). Doesn't switch on.
[Android Q&A, Help & Troubleshooting] goat seller:
Hiya mate, just wondering if you managed to sort your y300 out? I got a similar problem with mine, it says emmc is read only and can't do force update but can get into stock recovery and bootloader.. is there anyone with any idea of how to solve this problem?
[Android Q&A, Help & Troubleshooting] ksatyaki:
No luck

I didn't get any fixes. I am thankful to what happened in a sense. Life is much better without a "smart" phone.

:)
[General Questions and Answers] roozxx:
Hello all

Firstly I'd like to thank admin for activating my account and now finally (after 4 years!) i can post something! :D :cowboy:

So my first question is - what ROM would You recommend for my as far best phablet - Note2

I've flashed it a milion times during last two weeks and there are many fine roms like Liquid Smooth, AOSB etc. but most of them have problems that

can't be ignored.. currently I'm on JellyKat which graphically is not as pretty for me as native android but it works well enough but it's a true power drainer - it can discharge battery even when plugged into charger (and I know how to save my battery so everything is off, only BT is running and it still drains like hell)

I would like to have stable 4.4.4 it may not be too fast but it has to work well with my jabra BT headset, I also would like it to be power saving.

Can You suggest something (or maybe other kernel for JellyKat? (it's 4.4.2 I know :P ) )

Regards

RooZ
[Verizon Samsung Galaxy S III] J CGPhones:
So I have a VZW S3 on NE1 rooted and running xposed. I am not sure what module it was that I installed but my phone is now stuck with the SystemUI constantly crashing to the point of me being unable to use the phone. Then I, like a moron, Unrooted my phone thinking that would stop the issue. It didn't. I do have usb debugging enabled and my phone connects to the computer. Can I just boot into recovery and use the Xposed-disabler-recovery zip to fix this? will that wreck my phone since VZW is so annoying? Would that wipe my memory? And if that doesn't work what else could I do except pull everything I can off my phone and and reflash the entire thing using Odin?

Thanks a million!
[Verizon Samsung Galaxy S III] buhohitr:
There is an option in xposed to uninstall.
[Verizon Samsung Galaxy S III] J CGPhones:
Right but I can't even get past my homescreen at the moment
[Verizon Samsung Galaxy S III] buhohitr:
OK, I see then just flash the xposed-disabled-recovery.zip using custom recovery. If you locked with only stock recovery, you may need to do a factory reset,
[Verizon Samsung Galaxy S III] J CGPhones:
From stock recovery? That won't make my phone trip the fuse for modifying the system? By the way Thank you SO much for replying.
[Verizon Samsung Galaxy S III] buhohitr:
I accidentally hit send before finished typing, if you only have stock then a factory reset probably your best bet,
[Verizon Samsung Galaxy S III] J CGPhones:
Sigh that's what I was afraid of. Oh well I'll get going on pulling all of my files off. Thanks so much for all your help.
[T-Mobile Samsung Galaxy S 4] Red One:
So I don't know if I've been out of the loop, or I'm not reading something right or what, but I need some help. I've been searching up and down and everything applies to Verizon, not T-Mobile.

I have a T-Mobile Galaxy S4. It is currently on MK2 running WICKED V10. I want to use HyperDrive RLS17. However, I have heard whispers here and there about a proper upgrade process. Everything from something called SafeStrap, to being on the MDK bootloader, etc.

I want to be able to flash Hyperdrive RLS17 (a Verizon based ROM, with carrier compatibility packs) on my current device which is MK2.

Can anyone shed any light or point me in the right direction? I've been searching for 2 days and I think I'm getting misinformation from Verizon based roms.
[T-Mobile Samsung Galaxy S 4] serio22:
Is that ROM on this section or the Verizon section?
[T-Mobile Samsung Galaxy S 4] Red One:
All sections. The ROM was built for Verizon, but then Carrier Compatibility Packs were developed for each carrier. So they a pinned in each carriers version, however, originating from the Verizon carrier forum.

Here it is in the T-Mobile Android development towards the top:

http://xdaforums.com/galaxy-s4-tmobile/development

And here it is as a direct link:

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

I'm just really confused because it being an original Verizon only ROM, a lot of the questions are for Verizon. But I have seen on T-Mobile speicfic ROMs something about staying on MDL or MK2, or something along those lines. If I could just get to a KitKat ROM, I don't think I would have an issue, but my concern is jumping to 4.4 due to all the warning tape about going about it in the right order.

*EDIT* I also realized I posted this in General instead of Help. Can one of the mods please move this? My bad.
[T-Mobile Samsung Galaxy S 4] ShinySide:
Order doesn't matter. I don't know why someone would say that . updating/flashing the tar wipes everything off the phone (except data/sd card) so doesn't matter what order you do it in. If you're on mdl, flashing the nb4 tar is going to remove everything of mdl and replace it with nb4.

Btw there is no NC5 unless weve gotten an update no one has talked about or mentioned.
[T-Mobile Samsung Galaxy S 4] serio22:
Thought so but wanted to make sure.. As for the NC5 and safestrap I think that's for Verizon users.. You should be able to flash it like any other ROM
[T-Mobile Samsung Galaxy S 4] Red One:
I was thinking that. I was more afraid of any caveats like a bootloader version or anything like that. I see a lot of posts about running a pre-kitkat version and what not.

Thanks. Thats what I was thinking too, but ever since Knox came into play, a lot of red tape has gone up on how to properly do this. Plus I saw things about LTE modems not working if you use the newer version. Audio goes bad or something.

Just been out of the loop for some time and jumping back in i feel like warnings are coming at me from every direction.
[T-Mobile Samsung Galaxy S 4] serio22:
What is your current set up?
[T-Mobile Samsung Galaxy S 4] serio22:
Bootloader? I think you should be fine, MK2 modem works on KitKat but NB4 is recommended.. You won't lose audio as long as you follow the instructions on flashing the modem
[T-Mobile Samsung Galaxy S 4] Red One:
Whatever this brought.

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

Heres a camera shot. I can't remember how else to get it.

I think its MK2 if I'm not mistaken. Wicked was supposed to make a V11 Kit Kat, but his priorities shifted to his new note and his home life. So time to move on. I'm sure this would have had a newer bootloader
[T-Mobile Samsung Galaxy S 4] serio22:
You actually have the older bootloader with no Knox, probably MDL.. So you can flash the ROM and the modem if you wish

Edit: well even with NB4 full firmware you can do this but you won't be able to flash previous firmware, only ROMs, so its up to you.. Some experience better results with full NB4 package but you will trip your Knox if you update it which I don't know if you really care about it
[T-Mobile Samsung Galaxy S 4] Red One:
Well I went ahead and flashed, and I'm good. Still on MK2 modem, but getting ready to flash the newest. Also, I don't want to trip the Knox. I sell my phones when I go to upgrade and I don't need people getting cranky because knox is tripped. I'll upgrade to newest OTA when I go to sell it and call it a day.

FYI, I'm having very little issues on Hyperdrive 17.1 for T-Mobile. I think its an app problem right now because all was smooth until I started restoring apps. Thanks everyone for the help!
[T-Mobile Samsung Galaxy S 4] saagar_mistry:
Hey, I have the same mk2 phone as yours and I've been searching up to update to nc5 as well. I couldn't find anyone with tmobile and then I stumbled upon this post.

Just one question about this. You said you are still on MK2 modem, did u follow surge's method?? Did u use the same files as provided for verizon forum??

Then shouldn't the mk2 change to NC5?? Also, when u said u went ahead and flashed, did u mean u flashed hyper 17?? Cuz I tried and ROM didn't boot up on my mk2.

Please let me know. I wanted to go forward with this method just don't have the guts to take chances and brick my phone.
[T-Mobile Samsung Galaxy S 4] Red One:
Yes, flashed 17 from tmobile version, but selected AT&T on Aroma, and didn't flash the compatibility pack. Then I followed Surges method to upgrade the modem. I also flashed the ktoonz kernel for tmobile directly after the modem, as the instructions said to do.

Hope that helps.
[Verizon LG G2] sdgmcdon:
I can't seem to find a process for backing up my current "stock" setup, then rooting it and installing TWRP and ROM's.

I had a G2 previous to it getting kitkat and had done all of this with that, fairly easily too...but can't seem to find the same process to do it after the kitkat update (4.4.2)...?

Any help would be greatly appreciated.
[Verizon LG G2] mjones73:
You need to root it (using ioroot), install a recovery (using autorec) then you can back it up.
[Verizon LG G2] sdgmcdon:
This worked to get twrp on it thanks! ks (i was able to eventually get it rooted using ioroot and did a nandroid backup), i am however not able to flash a new rom (using cm's latest nightly for the vs980 now...going to try the snapshot next, but the nightly just fails almost immediately and i did have twrp fix permissions????

thanks again!

EDIT: And crap, stuck in a boot loop...said it flashed the snapshot ok, almost immediately, rebooted and boot loop.
[Verizon LG G2] sdgmcdon:
It's official, I'm bricked...lg logo boot loop, nothing else. Somehow in the process my nandroid and twrp backups no longer show up in twrp either (have to do the factory reset (hold down vol down and power twice, then power twice to confirm reset)...I've looked in the backup folders using twrp file manager and the folders have lots of stuff in them (not sure if it's correct stuff though?) and the folders are named as I named them when I did the backups...also, most other data seems to be on the phone and only 13gb's free according to twrp, so has to be a "system" there, but just get boot loop...

I've since read that the cm builds dont work on 24a kk 4.4.2 vs980; results in boot loops, but I can't get adb to work either so I can't even download a different rom to get it going...

I'm stuck...way stuck....
[Verizon LG G2] njstein:
Did you use jackpotcalvin's cm11? If not then you're in a bootloop because the official cm11 for our phone users 4.2.2 kernel base, whereas jpc's uses kk kernel.

Can you get into download mode? If so, return to stock using kdz or tot method (I've used tot, fairly easy).
[Verizon LG G2] mjones73:
ADB Sideload may work for you.

http://teamw.in/ADBSideload

Boot into TWRP, Advanced, ADB Sideload.
[XDA Assist] sierrasunset:
I am extremely new to this. I have a Samsung Galaxy S III Mini SM G730A on At&T. I need to unlock it so that I can use a different carriers sim card in it. I have searched and searched this site for answers and I guess I just dont understand. Is rooting the same as unlocking? Also I read somewhere that if the phone was running Android 4.1.1 or 4.1.2 I could unlock by dialing a few numbers in my phone. Unfortunately, my version is running Android 4.2.2. Is there any way to take it back to 4.1.1 or 4.1.2?

I have read the rules and I sorry if these questions have already been answered, but I could not find them.

Any help would be greatly appreciated.

Thanks,

Sierra

Oh this is what it says in about device:

Model Number: SAMSUNG-SM-G730A

Android version 4.2.2

Baseband version G730AUCUAMH4

Kernel version 3.4.0-1299773

se.infra@R0210-01#1

Wed Aug 21 13:15:42 KST 2013

Build number JDQ39.G730AUCUAMH4
[XDA Assist] Perseus:
You might be better off Posting in Galaxy S III Mini Q&A, Help & Troubleshooting

Rooting and Unlocking are two different things. Rooting allows you to remove System apps that you can not remove otherwise. It allows you to install other firmwares on your phone. It will not allow you to use other carrier's sim card. You will need to look for older firmware for your phone in order to do so. This thread will help you once you have that firmware. you can pose the question about the firmware in the forum I linked above.