yashsingh1/xdaforums huggingface dataset:
[Networking] manda.fatpanda:
Hi Everyone,

I'm just wondering if anyone has had the issue where their Panache Hotspot doesn't turn off? I will outline the problem below...

On Day x, I turn on my Hotspot and gave access to my sister, who has an iPod Touch -> she finishes what she needs to do, and I turn it back off

Day y, I do not turn on the Hotspot (meaning that the Hotspot box is NOT checked - I can't post an example, as I don't know how to do it off my phone and xda won't allow me to post outside links - sorry!) but I find out she still has access. I consult with a couple other people about why this might be, and it turns out that they can all find my Hotspot (HTC Portable Hotspot) on their phones too. Also, even after I went into my Hotspot and blocked her IP, she still was able to have access. The only thing I could do was turn off my phone, or change my password and turn on my Hotspot and then turn it off again.

Anyone have any ideas why this might be? I'm on mobilicity, so I have unlimited data, but this still bothers me, and I'm only into day 4 of my 14 day 'trial' period, so if this is a huge bug, I'll probably take it back and swap for a Nexus S.

Please let me know if I'm missing any information. I really appreciate any help anyone can give!!

Thanks!

Manda
[Networking] vallentz:
Hi,

a few month ago, my mobile network automatic turn off if WiFi hotspot on my HTC sensation was turn on. I already check setting until 2 week but the problem still not solve. I am happy right now after my software flashing with ROM Android Revolution HD, change kernel, radio. etc.

Not only my WiFi hotspot was working properly but my htc was faster and very faster.

Sorry if my answer not make you happy
[Desire HD General] stellarocksme:
Hi people, just a quick question. How come when i install a new rom the wallpaper stays the same. E.g i flashed leedroid months ago, now when i do a full wipe and flash another rom i still get the leedroid wallpaper :confused:

Thanks all for your advise :)

Oh is there a section where i introduce myself ?
[Desire HD General] 314:
Google automatically Syncs (At least on Sense based roms. Doesnt seem to happen on CM/Miui) when you install a new rom (You'll get your wallpaper - assuming its not a live wallpaper, all your apps [unless cancel installation on android market], all your contacts and sometimes all your settings[Depending on ROM. Seems to happen on RCMix Runny])
[Desire HD General] stellarocksme:
Ahhh i see, thanks for clearing that up for me. I thought i was going crazy.....
[HTC EVO 3D] tjb3401:
I've been theming my own APKs for a while just doing png edits, now I'm trying to do xml edits with notepad++ (after decompiling the apk with apkmanager), and every time I open up the xml it looks like this. Why?
[HTC EVO 3D] thoughtlesskyle:
that really doesn't look like it compiled correctly, i use a program called xml marker for my edits. if it was decompiled right none of those nulls would be there
[HTC EVO 3D] tjb3401:
Hm, how would I decompile it correctly? I've tried extracting the apk with 7zip and apkmanager and this is what I always get. Is there something else I need to do?
[HTC EVO 3D] thoughtlesskyle:
What apk is it, and are you using option 9 to decompile or are you just pulling the files out with 7zip
[Nexus S Q&A, Help & Troubleshooting] callison.168:
I'm going to probably get a lot of hate for this because there are a ton of forums that might get me here. I did search for about 3 hours tonight and discovered some things but am still confused. I hope someone can help this be more simple. So a friend has a Nexus S that isn't working (I have a Nexus S by the by too). It's unlocked but no ClockWork on it. I can press volume up and power to get to fastboot mode. When I click on "reboot," the phone will just loop on the Google logo. If I click recovery, it starts to boot then shows the triangle with the exclamation mark. From there, I can press power and up or down on volume to get the blue screen which says reboot system now, apply update, wipe, wipe. You get it. I'm stuck...I can also turn off the phone, hold volume up/down and plug in the usb to get to "downloading..."

I want to get this phone working and back to stock. I have the SDK Manager (my phone isn't rooted so I use it to take screenshots) and pda net (which I still don't understand why or how to use with this) and two versions of Odin. It seems like Odin can get this working but I can't get it to work or find a clear guide on how to use it and which ones to use. This is a Tmob Nexus S, I think the i9020. Any help would be so greatly appreciated and I will give you all the credit. Oh, and i can pull up the device on ddms with the sdk manager and can explore the files but there is nothing. I can't find a way to drag a file on the phone to "apply update from /sdcard." Sorry again and thanks again!
[Nexus S Q&A, Help & Troubleshooting] rapidreinsta:
It seems your boot.img file either corrupted or missing.

Find a working copy of file, flash it via ADB interface or fastboot. Flash recovery file CWM. If that doesnt work, Try flashing CM7 Rom or someother ROM.

Did you check http://xdaforums.com/showthread.php?t=895545 ?

Odin should be your last resort, if nothing really works for you.

If you want to return to stock, simply flash the NAND backup found here: http://xdaforums.com/showthread.php?t=884093 .

Disclaimer : I take no responsibility of what so ever happens to your phone, however you should be good if you follow proper steps.
[Nexus S Q&A, Help & Troubleshooting] callison.168:
Thanks so much for the quick reply. I think I've made some headway...I can "see" the device with cmd by typing adb devices. After that though, I don't understand how to get the stock nexus s rom on the phone. How do I move that file to my phone (what's the line of code I type)? I've tried "adb install <c:\grh78> but it says the syntax isn't correct. Any more help is so greatly appreciated and I appreciate the already prompt response. Thanks!!!
[Nexus S Q&A, Help & Troubleshooting] krohnjw:
Download your rom of choice (stock, custom)

Flash Cwm via fastboot if you haven't already

Boot into recovery.

Use adb push to push your zipped rom to the sdcard (adb push file.zip /sdcard/file.zip)

Use cwm to flash this zip.
[Nexus S Q&A, Help & Troubleshooting] rapidreinsta:
http://xdaforums.com/showthread.php?p=9866675

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

These threads should be a complete solution to your issue.

Disclaimer : I take no responsibility of what so ever happens to your phone, however you should be good if you follow proper steps.
[Nexus S Q&A, Help & Troubleshooting] callison.168:
Wow fast responses. I bet it's annoying to help yet another person having issues (again, phone was given to me like this but yeah...) while you guys or gals already know how to do these things very well. Here's where I'm stuck. I enter this code in cmd:

fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img

and it just says < waiting for device >.

Here's a pic of the screen that I'm on with my phone when i enter the command.

http://imgur.com/Pey3W

If I'm just in the first screen by holding volume up and power, the computer won't read the phone. So I click recovery, the screen shows it's trying to install something then the triangle exclamation mark, i press volume up/down with power and get this screen and the computer can "see" my phone on cmd.

How do I get this flipping clockwork on this phone or get the stock image on my sd card? Thanks again for helping me out guys. I have taken a look at the links you have sent me and that's where i found the download as well as the code to enter. I will keep looking at them but if you find a faster solution, please let me know.
[Nexus S Q&A, Help & Troubleshooting] callison.168:
One more thing to be super clear on...when I'm on the screen on the Nexus S that says Fastboot Mode on top in red and Lock State - Unlocked...my computer won't read the phone, therefore I cannot fastboot the recovery img...
[Nexus S Q&A, Help & Troubleshooting] irishrally:
So you already tried "fastboot devices" while in fastboot mode?

Edit: Actually it sounds you really want stock so download the complete stock OTA ROM (including boot.img etc.), rename it to update.zip and put it on the root of your sdcard. Boot into the stock recovery like you did already and hit apply update.

EDIT: Go here to download the correct OTA http://xdaforums.com/showthread.php?t=1056062

Find the correct 2.3.6 "Full ROM" for your phone model. Sounds like in those instructions you don't need to rename to update.zip. Haven't seen stock recovery for a while so I don't remember.

If there is a wipe option in the stock recovery then do that first.
[Nexus S Q&A, Help & Troubleshooting] callison.168:
Yes I have tried fastboot devices in fastboot mode but nothing because my computer doesn't read the phone in that mode. And yes, I want to put the stock rom on there but that's the key, I can't get access to the root of my sdcard. I can't push anything into the sdcard to flash it. Any ideas what to type or how to access the sdcard? Thanks a million, billion.
[Nexus S Q&A, Help & Troubleshooting] callison.168:
Also, I can't get the phone to boot at all, like I can't get passed the Google Logo if I reboot so I can't access the sdcard in the traditional way.
[Nexus S Q&A, Help & Troubleshooting] irishrally:
Connect with adb and type this:

adb shell mount /sdcard

Then type:

adb push rom.zip /sdcard/update.zip
[Nexus S Q&A, Help & Troubleshooting] krohnjw:
If fastboot devices returns NOTHING then this is most likely a driver issue. Remove the device through device manager, make sure you have a recent SDK (for the USB driver) and let it re-detect.

If you can get into the boot loader and get a proper USB driver you should be able to flash a recovery.

Once you've flashed Clockwork Mod (recovery) you'll be able to push to the sdcard using ADB or possibly mount the sd card through the CWM menu (although I've yet to have that work).

In order to get a recovery flashed though you need to get fastboot to see your device (unless you can already boot into recovery, then just use ADB).
[Nexus S Q&A, Help & Troubleshooting] krohnjw:
If he's stuck at the Google logo and has a trash boot.img it's not likely he'll be able to get a shell via ADB. Now, if the system is hanging starting a device or looping during boot then that's possible.
[Nexus S Q&A, Help & Troubleshooting] irishrally:
He said he can access stock recovery and has connected with adb, unless I read wrong.
[Nexus S Q&A, Help & Troubleshooting] krohnjw:
Indeed - I saw no clockwork and figured he'd toasted his recovery image as well, but it does look like stock recovery is there. ADB should push fine to the sdcard from recovery then.
[Nexus S Q&A, Help & Troubleshooting] callison.168:
More...so if i type in adb reboot bootloader in the recovery screen, it does just that...great. But then my computer makes a noise, a double tap if you will...like a dun dun, like something didn't work. When you plug in something to the computer it usually goes like dun na...but the phone clearly won't read when I'm in bootloader/fastboot mode. So when I type a command, nothing will work...
[Nexus S Q&A, Help & Troubleshooting] krohnjw:
That noise is that it detects a device has been connected (assuming a recent version of windows). If you want to flash CWM you need to get the driver sorted for the device. No amount of plugging/unplugging is going to fix it.

If you have the stock recovery you can boot into the stock recovery, use adb to push the full OTA package to the sd card and then just flash that from the stock recovery.
[Nexus S Q&A, Help & Troubleshooting] irishrally:
Go to the stock recovery like you have done before and type the adb command I wrote above.
[Nexus S Q&A, Help & Troubleshooting] callison.168:
Thanks is all I can say. Okay so when I type in the command, this is what I get:

- exec '/system/bin/sh' failed: No such file or directory (2) -

the "stock recovery" I can get into is the picture I posted a link for. That's what I can access as well as the fastboot mode when I first turn on the phone with volume up/power. But when my computer makes the noise that it's connected (using Windows 7 64bit) it makes a different sound then the normal "device connected." Like it's corrupted.
[Nexus S Q&A, Help & Troubleshooting] callison.168:
by the way...if we can get this working, I'll post a picture of me holding the fixed phone!
[Nexus S Q&A, Help & Troubleshooting] irishrally:
You need to download the stock ROM I linked to for the correct version of your phone. Then get to the stock recovery, the place you describe here: "I can press power and up or down on volume to get the blue screen which says reboot system now, apply update, wipe, wipe."

then to make sure you can connect with adb type:

adb devices

Then type:

adb shell mount /sdcard

Then type:

adb push rom.zip /sdcard/update.zip

where rom.zip = the name of the full stock ROM you downloaded

This pushes the stock ROM to the sdcard and renames it to update.zip

Then you can apply update.zip (apply update) from there. Make sure you download the "Full ROM".
[Nexus S Q&A, Help & Troubleshooting] callison.168:
So here's a link to the image of what's happening in my command prompt:

http://imgur.com/wTHfo

I can't access the sd card....
[Nexus S Q&A, Help & Troubleshooting] irishrally:
That might not be good.

Try:

adb shell

Then

mount /sdcard
[Nexus S Q&A, Help & Troubleshooting] callison.168:
That sadly made me laugh a bit...ughhhhhh So when I type in just adb shell, I get the same error. I think the guy that originally had this phone deleted everything by accident...would my next step be to try some Odin? Or any other ideas to get this on the "sdcard"?
[Nexus S Q&A, Help & Troubleshooting] irishrally:
Ok, so now we know adb shell is not happening.

Type:

adb remount

then try adb shell again

EDIT: Oh wait, go to fastboot mode and "mount system" first. Then go to recovery and do adb shell and push the file. That might work.
[Nexus S Q&A, Help & Troubleshooting] callison.168:
probably more bad news...when I type adb remount I get:

remount failed: Unknown error: 0
[Nexus S Q&A, Help & Troubleshooting] krohnjw:
adb remount will only work if he has an insecure boot image

adb shell won't work if /system isn't mounted (can't exec something that's not there).

Try to use adb push - if you're in recovery it can read from the SD card, there's no reason to try to manually mount it.

adb push file /sdcard/file

If that doesn't work then you need to get fastboot working, you can fastboot a new recovery image, and if this is a stock rom the boot.img as well from the full OTA package.
[Nexus S Q&A, Help & Troubleshooting] callison.168:
So imagine I'm a five year old...i downloaded the full stock rom as was advised and I put it in my platform-tools folder. It's a really long name, so do I need to rename it update.zip or rename it something else and then?...if so, can you please tell me what exactly I need to type in my command prompt? for example adb push update.img /sdcard/update.img or...? Thanks again guys
[Nexus S Q&A, Help & Troubleshooting] irishrally:
That makes sense. Listen to krohnjw, he actually knows what he's talking about.
[Nexus S Q&A, Help & Troubleshooting] krohnjw:
rename update.zip

adb push update.zip /sdcard/update.zip

Edit: This is going to look like it's hanging. The transfer rate isn't awesome and it gives no progress indicator. If it looks like it's hanging you're probably ok.
[Nexus S Q&A, Help & Troubleshooting] callison.168:
Thanks for dumbing it down for me :-). Okay here's a pic of what's going on:

http://imgur.com/nicN1

it says no such file is found but clearly it's there. I think this though is a user error. Am I pointing it to the wrong place?
[Nexus S Q&A, Help & Troubleshooting] krohnjw:
Heh, it's actually named update.zip.zip as you have file extensions hidden. Enable file extensions and you'll see.
[Nexus S Q&A, Help & Troubleshooting] callison.168:
Very impressive. I'm so out of my league here. Okay so I did that and the cursor on the cmd prompt just went under it and is just sitting there blinking...is it working and how do I know if it's on there now? Do i need to go to apply update from /sdcard on my android system recovery screen now to see if it's there?
[Nexus S Q&A, Help & Troubleshooting] krohnjw:
It will return to the command prompt when the transfer finishes (it's going to take a while).

At that point navigate through recovery and select apply update.zip.
[Nexus S Q&A, Help & Troubleshooting] callison.168:
Noooooo...okay I really hope this is good news sort of and an easy fix...this is what happened:

failed to copy 'update.zip' to '/sdcard/update.zip/: Permission denied

this may be a simple mistake; do i need to run cmd as administrator or is there something else wrong?
[Nexus S Q&A, Help & Troubleshooting] krohnjw:
That's not good news :) Did it hang for some time and then return that or did you get it right away?
[Nexus S Q&A, Help & Troubleshooting] callison.168:
:-) ugh...it did hang for a couple minutes...
[Nexus S Q&A, Help & Troubleshooting] krohnjw:
Try it again - that is odd that you got permission denied. I'm going to assume you'll get the same thing again, but it's worth a shot.
[Nexus S Q&A, Help & Troubleshooting] callison.168:
So the same thing, it hung for about 4 - 5 minutes and got the same error message. I reopened cmd.exe as Administrator (just for the heck of it)...same. NOOOOOO
[Nexus S Q&A, Help & Troubleshooting] krohnjw:
Yeah, perhaps the stock recovery mounts the /sdcard without write permissions (boo).

Time to get fastboot working. This will potentially be easier over a form of messenger (gtalk / irc) than posting repeatedly. Any preference?
[Nexus S Q&A, Help & Troubleshooting] callison.168:
thanks so much..yes gtalk...callison.168
[Nexus S Q&A, Help & Troubleshooting] kibmcz:
Also keep in mind fastboot mode doesn't use drivers from the sdk it uses different ones oddly.

Here are my drivers from when i unlocked mine.. http://dl.dropbox.com/u/7812800/Nexus_S-Drivers.zip

(the x86/x64 folders are the fastboot drivers)

Not sure if this was thought of but this is what id do:

1. Get fastboot working

2. "fastboot oem unlock"

3. Usb boot clockwork recovery "fastboot boot recovery-clockwork-5.0.2.0-crespo.img"

4. Enable usb storage in CWM "mounts and storage" > "mount USB storage"

5. Copy update.zip to usb storage root and flash it "Unmount" > {back} > "apply sdcard:update.zip"

6. "fastboot oem lock" (optional could be useful to keep it unlocked)

Just my 2 cents from up here in canada lol
[Nexus S Q&A, Help & Troubleshooting] irishrally:
Did you get it working?
[Nexus S Q&A, Help & Troubleshooting] krohnjw:
Unfortunately no - but it was not due to lack of effort (about 3 hours worth).

Essentially they received it in this condition (i9020t). Recovery wouldn't flash via fastboot, couldn't boot recovery via fastboot, couldn't boot a valid boot image via fastboot, couldn't flash a valid boot image.

After erasing the partitions themselves writes would often fail with error unknown. Multiple tries were required to write any valid image to the internal storage (we went through multiple USB cables just to make sure we didn't have a wonky cable).

We did eventually get CWM up and running, then the SD card could not be mounted or read from - although it could be written to.

A manual format got the SD card mounting again and he attempted to flash the full 2.3.6 OTA from recovery. The flash appeared to go fine, but CWM bombed writing the radio. The assert failed writing the full radio image. However, /system, boot and bootloader all flashed without issue.

Upon reboot the device is now completely non functional. This is baffling as it was the full OTA for the i9020t (confirmed model on the physical device). The screen won't power on at all. The device is no longer recognized by the computer appropriately (booting "normally", into boot loader or fastboot). It is detected by the computer only as SEC S5PC110 Test B/D.

Unfortunately all results for this point to bricked Galaxy S devices. It's odd to me that the device somehow bricked writing a signed package from Google through recovery for his correct model.

Given the numerous errors writing to the internal storage though I'm guessing they didn't buy a model that "went wrong" when flashing a custom rom as was described to them. It seems like there has to be some damage to the internal storage. Both boot and bootloader flashed fine and passed the assert, so they in theory should be fine - but that doesn't appear to be the case.

At this point I'm close to out of ideas for it. No display is activated ever for Download mode, boot loader, normal boot. The PC no longer detects the device properly either (so fastboot / odin as seemingly useless). The Google USB Driver package as well as the Samsung Driver package don't install the correct driver for this SEC S5PC110 either. I'm going to do some more digging, but it's not looking good right now.
[Nexus S Q&A, Help & Troubleshooting] irishrally:
I'm sorry to hear that. I had to send my NS back to Samsung because the internal storage was corrupt. I tried everything to fix it to no avail. Samsung replaced the PBA (Printed Board Assembly) as they called it free of charge. A search for corrupt storage will show a thread with more info. This has happened to a small percentage of people but certainly more than just me. The previous owner probably ran inti to this issue, couldn't fix it and sold as is.

I suggest trying to contact Samsung to replace the PBA.
[Nexus S Q&A, Help & Troubleshooting] krohnjw:
I figured that's where it would end up at this point - there's not much left to do. Even IF we managed to get a good image onto the thing, given the number of write errors going on I don't suspect it will work as expected for long.

Anyone have any experience with Samsung's warranty for non-original owners? Perhaps the original guy didn't register it with Samsung :)
[Nexus S Q&A, Help & Troubleshooting] callison.168:
Hello everyone. Sorry to just write back now. I started a new job this week and it's been crazy! Okay so a huge thank you for everyone who assisted. I had a few people (just read the thread) that really worked with me. The biggest thanks goes to krohnjw for being patient with me while we worked on this for hours! I learned so much though and I hope I can learn half of what he knows someday.

The phone kept giving us problems at every turn, like stated above. It's unfortunate but it was basically a "play" phone that if fixed would be great but if not, it's okay. When we got CWM on there though, I was smiling! Thanks again!!! XDA rocks.
[HTC Sensation] Vince_be:
Hi,

I'm currently using ARHD 4.1.3 but for stability reason (phone call cuts), I want to re-install a stock rom + S-OFF + SU.

Which is the "best" ROM (Sensation Original or XE, it doesn't matter) that won't lock my bootloader?

Thanks in advance for your help!

Regards.
[HTC Sensation] petrosk73:
Both are safe as both Hboot 1.17 (original sensation) and 1.18 (sensation XE) can be handled by revolutionary
[HTC Sensation] Vince_be:
Hi,

Is there a release that is better than others?

Regards.
[HTC Sensation] petrosk73:
And by better you mean....?
[HTC Sensation] Vince_be:
The fastest one (knowing it's the stock one) and the most stable...
[HTC Sensation] petrosk73:
Its all a matter of preference. Personally, I liked the XE better. Having said that, ARHD as well and wanted to move back to stock, but thought I give inserstcoin a go before switching to RUU. I have been using the IC rom for the past two weeks and don't think I will change to another rom soon! ;) To cut a long story short, I would suggest giving IC a test for a couple of days before changing back to RUU