yashsingh1/xdaforums huggingface dataset:
[One (M7) Q&A, Help & Troubleshooting] networkn:
Thanks for your help, how do I determine what versions of whatever I have?
[One (M7) Q&A, Help & Troubleshooting] networkn:
Hmm what is the best step by step guide I can follow to recover my device if it's bootlooping? I can get into download mode and recovery mode.
[One (M7) Q&A, Help & Troubleshooting] nkk71:
in bootloader: HBOOT-1.xx.xxxx
[JASJAR, XDA Exec, MDA Pro General] zachary.deponch:
Hello,

I have noticed with the new firmware (v0034) Jabra is no more storing ln the "Call List" incoming international call correctly. Indeed, the + sign is missing preventing the user from dialing the international entry from the "Call List". I'm wondering if someone in the comunity has experienced this "regression" (the International phone numbers were correctly handled in the v0032 firmware)

Thanks for your feedbacks,

Zak.
[JASJAR, XDA Exec, MDA Pro General] MvanIperen:
Yes, this is a known problem. As far as I know this update has only been offered on the Jabra US website. All site still offer the 0032 version which does show the + sign.
[JASJAR, XDA Exec, MDA Pro General] kasu:
Ooops...just few secs back i upgraded my jabra :(

Mvan -- Do you suspect this new upgrade deteriorate UK sets ?

Cheers
[JASJAR, XDA Exec, MDA Pro General] khaledelfeki:
The new thing in this update is that you can now set your device to vibrate when you are using any ringtone other than "from phone"
[JASJAR, XDA Exec, MDA Pro General] kasu:
hey with this new upgrade looks like i've lost 'Vibrate' option in 'Ring Type' though I selected 'old bell' in 'Ring Tone' :(

i've got just 'Normal' & 'Silent' in 'Ring Type'....any suggestions pls ?

Cheers
[Galaxy Note 3 Q&A, Help & Troubleshooting] iqxaaron:
Hey Guys,

I accidentally wiped my system while wiping dalvik cache etc and im stuck at the boot logo, i can still access download mode and TWRP recovery.

I'm using the Galaxy Note 3 SM-N900W8 (Canadian) Model and at the download mode screen it would say

Odin Mode

Product Name: SM-N900W8

Current Binary: Custom

System Status: Custom

Reactivation Lock: Off

Knox Kernel Lock: 0x0

Knox Warranty Void: 0x0

Qualcomm Secureboot: enable (CSB)

RP SWREV: S2. T2. R2, A2, P2

Write Protection: Enable

Any help please?
[Galaxy Note 3 Q&A, Help & Troubleshooting] Killberty:
Wait... u had twrp on your phone an it DOES say knox warranry void 0x0? 100% sure?

---

For fixing try flash lastest and your original firmware (the one u had before the system wipe)

hit 'thanks' if i helped you

SM-N9005 DBT-DMJ7 0x0

XDA Developers 4 premium app
[Galaxy Note 3 Q&A, Help & Troubleshooting] nannlp:
Simpler than flashing the rom is to just flash TWRP again via ODIN from a pc.

You will be up and running
[Verizon Samsung Galaxy S 4] Mechachrome:
I picked up a Verizon Galaxy S4 today, and it installed the OTA update.

Tonight I tried to root the phone, and it did not work, and now I can't get the phone to start back up. It gives me the "firmware update encountered an issue message."

I can get the phone into download mode, but I haven't been able to install a stock rom using ODIN. I think maybe I'm using the wrong ROM.

What should I be doing?
[Verizon Samsung Galaxy S 4] k1mu:
You're probably using the wrong ROM.

Which OTA? What baseband were you on prior to and after the OTA? What errors did you see in ODIN and on the phone.

If you were on MJ7 and updated to MK2, then you should be able to flash the MJ7 no-wipe ROM to recover.

Failing that, install Samsung Kies and use it to recover your phone.
[Moto G Q&A, Help & Troubleshooting] boogalah:
Hey all, Moto G US version owner here, and having trouble getting MMS working on at&t. I spent some time on the phone with them earlier and was more or less told that the phone wouldn't work right on network, or something to that effect. This was frustrating since everything else worked fine, and it is supposedly tailored for US networks after all. So I tried several different APN settings from online but to no avail. I even copied over the APN settings from my unlocked GS3 (which has no problems at all on at&t's network) and it still wouldn't work. I've contacted Moto's customer service as well and they've given me the number for Level 2 support, will be speaking to them soon.

I'm at a loss here.. yes, it is a new device and all, but is anybody else having this problem?
[Moto G Q&A, Help & Troubleshooting] oldcrow66:
Try Handcent

I was able to sent text messages just fine, but not MMS photos. I installed Handcent and set the photo size to 100k and the messages went through. I'll be calling Tmobile tomorrow to make sure it's not a provisioning issue.

I'll update if a solution is found.
[Moto G Q&A, Help & Troubleshooting] boogalah:
Would this help with receiving MMS messages though? I have issues sending and receiving them currently. Have not had an opportunity to speak with Motorola's level 2 support yet.
[Moto G Q&A, Help & Troubleshooting] angomy:
I'm on AT&T Gophone, not AT&T postpaid, so your experience may be different, but I've had no problem sending MMS to other phones (android + iphones) or receiving them.

The AT&T rep set up two APN that I can see, including them here for you to try out if you want:

Name: AT&T Phone

APN: phone

Proxy: not set

Username: not set

Server: not set

MMSC: not set

MMS proxy: not set

MMS port: not set

MCC: 310

MNC: Not set

APN type: default, supl, hipri, dun

APN protocol: IPv4

APN enable/disable: APN enabled

Bearer: unspecified

MVNO type: none

MVNO value: not set

AT&T US MMS

Name: AT&T US MMS

APN: phone

Proxy: not set

Username: not set

Server: not set

MMSC: http://mmsc.mobile.att.net

MMS proxy: proxy.mobile.att.net

MMS port: 80

MCC: 310

MNC: 410

Authentication type: not set

APN type: mms

APN protocol: IPv4

APN roaming protocol: IPv4

APN enable/disable: APN enabled

Bearer: unspecified

MVNO type: none

MVNO value: not set

FWIW I've also used this AT&T APN Suggested from ATT forum and it also works with MMS after a reboot.

NAME: AT&T Phone

APN: wap.cingular

Proxy: (not set)

Port: (not set)

Username: wap@cingulargprs.com

Password: CINGULAR1

Server: (not set)

MMSC: http://mmsc.cingular.com

MMS Proxy: wireless.cingular.com

MMS port: 80

MCC: 310

MNC: 410

Authentication Type: (not set)

APN type: (not set)

APN protocol: IPv4

APN: enabled (may need to check this, not sure about your model)

Bearer: unspecified
[Moto G Q&A, Help & Troubleshooting] anzistor:
Prepaid? Last I remember prepaid doesn't support 4G devices for data. And MMS uses data, not wifi. And while I'm aware the MotoG can use 3G(I have mine on Verizon)...AT&T tends to lock down their better phones to 4G only to get users on the contract.

I could be mistake and that phone is supported, but I don't believe they run 4G on prepaid/gophone and hence you might not be able to run data.

As of 2012 they had an inner memo to their call centers saying that 4G devices, Rimms, and iPhones wouldn't be supported for Data any further.
[Moto G Q&A, Help & Troubleshooting] ScottDB:
Having same problem as original post

I'm having the same problem as original post, except I'm using StraightTalk. My Moto G is the US version - GSM (uses AT&T network). I've set it up to use the APN that StraightTalk provided. Browser works OK, so I know data services are working, but I can't send or receive MMS messages. I've also tried Handcent that was mentioned in this thread, but it still doesn't seem to be sending. I've also tried the AT&T APN settings from this thread, but no go. Not sure what else to do...
[Android Q&A, Help & Troubleshooting] browny_amiga:
I have had it, after struggling with the media server for months now, the damn thing consistently wastes and kills my battery.

I downloaded rescan media root, which supposedly deactivates it, but not really. It keeps coming back and usually when I see it, it is already too late and the battery is low.

Now the question is which package do I have to deinstall (freeze) to kill the media server? I don't really need it, I can find my media alright myself.

And saving some well meant suggestions right now:

And yes, I do have a SD card. Yes, I do have media on it.

No, I will not remove that media. If media server is overwhelmed with more then 30 files, it has to go (not the media itself)

No, rebooting does not help.

No, reinstalling the whole OS or doing a factory reset is not a solution and not a proper way to do troubleshooting (you also don't just kill a person instead of giving them surgery) I can't wipe out all my data everytime I got a problem.

Any other suggestions I am eager to hear.

I'm ready to suffer any consequences by a disabled media server, at this point it can only get better. I just want the blasted thing stopped and switched off.
[Android Q&A, Help & Troubleshooting] browny_amiga:
Wow, nobody??? Shocking how something as trivial as this gets no answer.

Android has strayed far from its Linux roots, where people are a lot more knowledgable about how their OS works.

Well, if somebody runs into this problem, I now kill it on a regular interval.

I will post the script in the next post. There are quite a few people suffering from this and it seems that it does not take much to make the media scanner crap up and crash and then go into a restart loop forever.
[Android Q&A, Help & Troubleshooting] polobunny:
Agreed, strayed really far, because if you made the searches you'd see most of the media scanner related issues are usually due to corrupt media/unknown characters in id3/exif. There's even some apps available on the Play Store that create broken jpg when taking a picture... Trying to kill the media scanner is akin to trying to cure a fever. The crash is the symptom, not the problem.

If you want to disable it, I'd imagine you could use

pm disable com.android.providers.media/com.android.providers.media.MediaScannerReceiver

This will disable scanning on boot. I'm pretty sure that's what Rescan Media does though.

I do however agree that the error handling on media scanner is piss poor, it shouldn't crash but rather skip problematic files.

Either way, all troubleshooting can be done with logcat/ddms if you feel like finding the culprit file(s).
[Galaxy Note 3 Q&A, Help & Troubleshooting] nazstyle:
Hi :)

I'm with Telstra ( Australia ) I replaced my Note 3 after I lost it with there $180 replacment plan. With this, the old phones IMEI is blocked and you are given a new phone. I ended up finding my old Note 3 last night.. Now its as good as a paper weight because I got my new one from Telstra and they will not unblock it because of the ToS of the replacement plan. What options do I have? I'm rather new to EFS and IMEI stuff.. Can I use an EFS back up of my old HTC one X to use its IMEI?

Sorry again for my lack of knowlage but I haven't been able to find much info on it at all.

Thank you <3
[Galaxy Note 3 Q&A, Help & Troubleshooting] xclub_101:
Well, the honest thing to do would be to give the locked phone back to Telstra. Everything else would be illegal - starting from selling the phone for parts and ending with highly-illegal ways to change your IMEI.
[Galaxy Note 3 Q&A, Help & Troubleshooting] a.cid:
Unfortunately, we do not allow discussions on IMEI modifications as it is considered illegal in several parts of the world.

Thread Closed

A.cid

Forum Moderator
[T-Mobile Samsung Galaxy S 4] avillal87:
So the rom fin without t-mo compatible fix but when I install in recovery it fails. In both cwm and twrp. Com.android.phone pop up and see the phone lag. When I uncheck wifi it stop and begins to work like before. I have read about loki doki but I dont understand if has anything do with this but am not sure or where to read. Do I have unlock my bootloader to fix this problem with wifi. Am sorry if this question been ask but I look not found that say about t-mobile m919.
[Nexus 7 (2013) General] orlandoxpolice:
niche application, but very very cool.
[Nexus 7 (2013) General] rulk:
Just wanted to say thanks for the tutorial!

I am a security student and I purchased my Nexus 7 Tablet with this exact application in mind!

I have been stumbling through things and keep having to start over..

With this tutorial (assuming it works for me) You just saved me probably another 8+ hours screwing with it.. And the look on my class mates faces when i come in with a full Kali installation... ;)

I will post again once I have it all installed and go from there. And thanks for the part for the wifi. I might have to go and order atleast one now. I am building a mobile hacking station into my vehicle and a couple other machines. Was not aware of this WiFi also working.

Now that I have my stock rom back on for the 6th time today... (grrr) I am off to follow this tutorial!

One quick question for you...

Can you use the built in WiFi with this to hack with as well?

I understand you won't likely be able to hack wifi without the USB wifi adapter but I am also interested in hacking in the network once I am in. In otherwords it makes sense to use the USB wifi adapter to gain access to a network then unplug it and use the built in to hack the actual network.

I will mention again I am a security student learning this stuff and I will not be using these to break any laws. I will likely be hacking into my own computers setup for this experience or other computers setup for this.

I assume you could use a similar style USB wired lan interface as well.

have you tried the latest kali rom that was posted?

Rodney
[Nexus 7 (2013) General] droidshadow:
[MENTION=591969]rulk[/MENTION]

Hey i am glad that you like the tutorial! People have reported getting the internal broadcomm wifi chipset that is built into the Nexus 7 tablet to work with monitor mode. So you technically could use wifite and aircrack-ng with your tablets built in wifi. The only problem with that is that you will loose all internet connection once you put your internal wifi cad into "monitor mode"

If you get an OTG Cable with multiple Y-Cables you could plug in multiple usb wifi adapters...

There is one gentleman on the other zetaboards forum that has multiple usb wifi adapters (multiple ALFA's) that you could check out...

I just ordered a different ALFA NOT THE AWUS036H that has the RTL8187L chipset the ALFA i ordered i believe has an ATHEROS chipset i believe, and once i try it out I will let you know how it works,,,

Have fun brother, and let me know if you have any questions!

-droidshadow
[Nexus 7 (2013) General] droidshadow:
Oh which latest kali rom are you talking about?...

Can you give me a link?..

-droidshadow
[Nexus 7 (2013) General] rulk:
If you go to the link in your tutorial there is another one listed now:

update-kalipwn-v05-1.zip = 1.46 GB | Update 18 DEC | Uncomfirmed working on Android 4.4+.

I loaded this one onto my tablet and about half of the programs exit abruptly.

I just screwed up my tablet again...

I had backed up the rom before installing kali but since it didnt work I tried to restore but there is not a restore option for just the rom so I did the main restore... Looks like I over wrote my stock rom with the CM rom and lost the second rom..

Ugh

Looks like it will be cool once I get it working though..

If I can use the WiFi to do my internet stuff then switch it off to use this stuff then I am good. I really don't need two wifi adapters on it yet.

Although I may be ordering some new ones so I can...

Rodney
[Nexus 7 (2013) General] droidshadow:
Rulk:

Yes Binky has just added that Kali pwn update but as you can see in the comments it has not been tested...

You need to make sure that you are using the custom CM ROM I mentioned the CM11-bruce ROM and make sure you use Binky's kernel for 4.4+ then only use the update-kalipwnv0.5 that I mentioned in the tutorial.

If you have Multirom installed you will be fine just remove (delete) the ROM and start over.

The custom cm11 ROM and kernel are crucial to getting Kali pwn pad to work!

-droidshadow
[Nexus 7 (2013) General] droidshadow:
[MENTION=591969]rulk[/MENTION] I forgot to get you the link so that you can turn your internal WiFi card on your Nexus 7 into monitor mode but if you do a Google search for 'android monitor mode' one of the very first links that comes up is bcmon.blogspot (something like that) and they have actually created an APK file to get monitor mode on the Nexus 7. Granted this was tested on N7 2012 and on CM 9 but other guys have told me they got it working on newer CM10+ ROMs

When I get home I will give you the link

-droidshadow
[Nexus 7 (2013) General] AlchemicalVibrations:
Fantastic tutorial! I greatly appreciate the detail that went in 2 this masterpiece. I just checked the link 4 CyanogenMod download and the only ones posted for the Flo model are 12 / 18 and 12 / 17
[Nexus 7 (2013) General] p4rot:
Just a little question,

Do we need a USB WiFi device like the one linked to amazon so that this whole setup works?

BTW the flo Roms available don't say odexed but bricked linaro, is that the one we need?
[Nexus 7 (2013) General] droidshadow:
[MENTION=4794126]AlchemicalVibrations[/MENTION]

You do NOT download the CM ROM from the official CyanogenMod website. You have to download it from the xda thread that is in the link I provided.

[MENTION=5048020]jonathanxx1[/MENTION]

You do not necessarily need the USB WiFi device like the one I linked from Amazon but then it would leave apps like wifite kismet and aircrack-ng useless. But there is still some great apps such as metasploit SET (social engineering toolkit) and openvas just to mention a few...

For the $15 the TP-LINK USB WiFi device costs it is truly worth it!

-droidshadow
[Nexus 7 (2013) General] droidshadow:
[MENTION=1021772]johnathan[/MENTION]x

You are right he has updated the ROM...

Go with the second to last zip should be fine...

Try flashing that zip with Multirom and it should work just fine...

If for any reason you have a problem I will upload the cm11-bruce-odexed.zip file that I have I promise

-droidshadow
[Nexus 7 (2013) General] p4rot:
The file (ROM) that I got is cm 11 2013/12/18 bruce2728 bricked linaro, is that it, just to make sure before flashing and messing everything up.
[Nexus 7 (2013) General] AlchemicalVibrations:
Ok on bruce's page I see two downloads:

cm-11-20131217-bruce2728-bricked-linaro-flo.zip

cm-11-20131218-bruce2728-bricked-linaro-flo.zip

Just to be sure, did you mean the cm-11-20131217-bruce2728 one? Also, SuperSU updated to 1.86 so is that okay to go with or do we need the 1.8 you referenced in OP?
[Nexus 7 (2013) General] p4rot:
In gonna wait for an answer also before flashing

---------- Post added at 04:29 AM ---------- Previous post was at 04:27 AM ----------

I mean an answer to the question the poster above me just asked.
[Nexus 7 (2013) General] droidshadow:
Jonathanxx1:

Do you have multirom installed? It is almost impossible to mess up your tablet with MultiRom installed...

You can go with either zip file i would probably go with the latest zip file the 12-18 one. With multirom installed you can't go wrong...

If your rom messes up you can just hold down the power button it will reboot your tablet and you can delete the rom from TWRP recovery and you can easily start over again.

Now go ahead and try that rom and if it works great, if it doesn't work then i will upload the cm11-bruce-odexed.zip file that i use specifically for my installation.

Does anyone know of a good (and free) upload site where i can upload a zip file around 180MB?

As for SuperSU updating itself always go with the most recent SuperSU zip file that is available...

I stated in the tutorial that you may not even need the SuperSU zip file it is just good to have just in case you have problems adding SuperSU to your cm11-bruce ROM installation.

Have fun brother!

-droidshadow
[Nexus 7 (2013) General] p4rot:
I will try with the latest Bruce ROM and the latest super su and report back after.
[Nexus 7 (2013) General] droidshadow:
Want to try a different ROM?...

Jonathanxx1:

I wanted to let you and everyone else who is interested in putting Kali Pwn Pad on their Nexus 7 device that I was in fact able to get Kali Pwn Pad to work with another custom ROM. The ROM I choose was recommended to me by another *tester* and it worked very well for me.

The ROM I choose was "Ice Cold ROM" and here is a link to the XDA Thread -> http://xdaforums.com/showthread.php?t=2488056

Ice Cold Rom is a very nice and stable ROM that runs on Android 4.3.1

If you would like to use this ROM to put Kali Pwn Pad on you are going to want to choose the ROM for "FLO" if you have the Nexus 7 2013 WIFI only tablet like i do.. (if you don't choose the correct Rom for your device).

Okay so the whole process is the same if you want to use Ice Cold ROM except you are going to be adjusting a few things...

1st. You are going to want to get the correct GApps.zip file. For Ice Cold Rom you can use the same GApps.zip file that Cyanognemod uses for their 10.2 version. Here is a link -> http://wiki.cyanogenmod.org/w/Google_Apps

(choose the gapps.zip for CM 10.2 the 0813).

2nd. You are going to want to use a slightly different kernel. You will be using Binky's kernel for Android 4.3 which is based off of

ElementalX v1.8

Here is another link -> http://w11.zetaboards.com/Pwnie_Express/topic/9369003/21/#new

Make sure you get this kernel -> Android 4.3 Based off ElementalX v1.8.. Defconfig can be found here for developers. The trick was cfg80211. This is confirmed working by BeNe.

3rd. Instead of using Kali Pwn Pad v0.5 you are going to need to use

Kali Pwn Pad v0.4.

Now i know you might be thinking that kali pwn pad v0.5 is probably better than v0.4 but let me tell you that i have been playing with kalipwnpadv0.4 for about 3 days now and it is quite stable..

Well that is it...

The whole process for using Ice Cold Rom instead of Bruce2728 Custom CM11 project is the same except you are going to be using those 3 files mentioned above instead..

If anyone has any questions please dont hesitate to ask...

*NOTE* if you used Bruce2728 updated CM11 zip file (1217 or above) please let me know how it worked for you so i can relay it into my tutorial.

If i have to i will try it out myself...

I hope this has been helpful for you...

-droidshadow
[Nexus 7 (2013) General] droidshadow:
DEB vs FLO

lokolyokol:

You have the Nexus 7 2013 LTE version which is the 4G version. This is model DEB. You need to find a ROM that works with your DEB version. The file that i uploaded is for model FLO which is the Nexus 7 32GB WiFi only model.

Edit:

Sorry brother, I missed where you said that you are using the deb version of Bruce2728's CM ROM. Give me the error that you are getting again so we can work it out..

Now i know a guy on the zetaboard forum, he is one of the original testers...

He uses your exact tablet the 32GB 4G model.

He also used the bruce2728 ROM you just need to get the DEB version not the FLO version. If you want to try another good ROM look into OMNI ROM but look for their DEB version again.

Hope it helps...

If you need any other assistance let me know...

-droidshadow