yashsingh1/xdaforums huggingface dataset:
[JASJAR, XDA Exec, MDA Pro General] shuflie:
I've just recently been doing this, but I haven't used any special app on my PPC to do it. I installed orb on my PC and when I open my.orb.com on my PPC if it can't see the PC it will allow you to send a wakeup command to it. Things that I did to allow the wake up were,

1. Forward UDP port 7 from my router to the PC

2. Set the ACPI power saving mode in the computer BIOS to S3, this allows you to select wake from USB device in the BIOS. I did this too although my PC is connected by ethernet.

3. Well that was all really, if my BIOS had a wake on LAN setting I would have enabled it but it doesn't, so I didn't.

Perhaps you should make sure that UDP port 7 is forwarded to your PC's IP address. If the PocketPC wake on LAN app doesn't work give orb a shot, its a great service, and completly free. I have to ask why you have your modem between the router and PC, surely you would attach the modem to your router's WAN port and the PC to one of the LAN ports, or did you actually mean that the router was between the modem and the PC?
[JASJAR, XDA Exec, MDA Pro General] cool_case:
Hey, thanks a lot, shuflie, installing Orb and using it to send a wake-up worked!!! It wakes up the PC, then I can use my remote desktop app (z2Remote2PC) to send an [enter] command to log-on and control the PC. Nice one - thanks a lot!
[JASJAR, XDA Exec, MDA Pro General] shuflie:
Glad to be of help. :D
[JASJAR, XDA Exec, MDA Pro General] Mr.Sir:
Is this the right ORB? :)

http://www.orb.com/installing_orb
[Verizon HTC One (M8)] WorldOfJohnboy:
I've noticed that on some custom ROMs, the Verizon Visual Voicemail application doesn't work (If memory serves, it says something to the effect of "Media not supported"). Going back to my Rezound or Thunderbolt ownership days, I recall a workaround for this app, provided you are Rooted (and I believe need S-Off as well, but don't quote me on that). Here's the procedure to get VVM working on most HTC devices:

Download Visual Voicemail app from Store HERE.

Download Build Prop Editor HERE.

Open Build Prop Editor, allow SU access.

Locate/Search for "ro.HorizontalVVM"

Change from "True" to "False"

Reboot phone when prompted by Build Prop Editor.

Start the VVM App, login.

Profit.

Note: The App is not the one that comes with the One M8, but it is Verizon developed and has basically the same features as most of the "native" apps on stock ROMs.

Please note, I'm not a Dev by any means, so some questions I may not be able to answer. Also, if your custom ROM is missing the ro.HorizontalVVM line in the build prop, you would have to seek assistance from them. I can confirm that this procedure to work on the HTC One M7 (TeamVenom - Viper ROM) as well as the HTC One M8 (TeamVenom - Viper ROM). Note that the procedure has nothing to do with those ROMs, and I certainly don't mean to step on TeamVenom's excellent work in custom ROMs.

I will give credit to the original person that came up with this procedure once I can "dig" and locate. :)

UPDATE: For those running ViperOne M8 ROM, there is a (IMO) better workaround (MOD) that fixes VVM and MMS/Group Messaging. That process is listed HERE. Great job to JWhetstone02 !
[Verizon HTC One (M8)] WorldOfJohnboy:
Found one of the earliest posts regarding VVM on AndroidForums from 2010: http://androidforums.com/droid-x-all-things-root/164629-visual-voicemail-flyx.html#post1508119 user madAdam.

The post that I first saw on it was for my Thunderbolt: http://xdaforums.com/showpost.php?p=13969515&postcount=292 user ahart814

(Side note, I miss Team BAMF on my phones...) :cyclops:
[Motorola Atrix HD] dosmac:
Apparently the ONLY version of Android that is vulnerable to Heartbleed is 4.1.1. I ran a check on my phone, and sure enough I'm running that version, and heartbeats are definitely enabled. I used the Lookout security app to verify this. Is there a way I can patch my system myself and somehow disable the heartbeats feature without having to wait another 3 years for Motorola to come out with a fix? My phone is rooted, but something tells me that OpenSSL probably needs to be essentially recompiled with a flag set to disable heartbeats?

I was hoping there would be a quick config file for OpenSSL that can be modified, but I'm not usually lucky. Based on everything I've seen thus far, a recompile with a flag set is the only way to fix this. Figured i'd give it a shot and ask on here.
[Motorola Atrix HD] stevep2007:
I've been thinking about the same thing.

If memory was encrypted that could solve all or part of the problem.

If the Chrome https browser cache were turned off, which I think requires an APK edit there would not be any clear text data in the browser cache.

What do you think?
[Motorola Atrix HD] skeevydude:
Yep, 4.1.1 is vulnerable to this. 4.1.2 has the no heartbeat fix added in and 4.1.1 took the update that was bugged. That said, we DO have TWO 4.1.2 Stock roms, Mexican Retail and Bell are both 4.1.2 and should have that fix -- needs confirmation. Our Stock ICS roms are all from before this bug was added in and are safe. In reality, only stock, locked AT&T Atrix HD's are vulnerable to this since all the other roms* have this fix.

Normally I'd say something around the lines of give me a few days and I'll look into this more, but I've been busy lately, and when I'm not busy I'm either tired or sore; did some heavy lifting a few weeks ago and my back is still sore from that day.

*Our 4.1.2 roms are untested, but 4.1.2 AOSP has the fix so our 4.1.2 stocks should too
[Motorola Atrix HD] stevep2007:
I was just thinking that ther eis no such thing as security. Security is achieved by being harder to exploit than the other computers. Even 3-DES can be cracked with enough computing power.

So encrypting memory and stopping https caching would close two big holes. I'm now wondering what holes would remain to be exploited by the heartbeat exploit on a 4.1.1 device if this were done?
[Motorola Atrix HD] skeevydude:
If I was on a stock phone running 4.1.1 and I was that worried about heartbleed, I'd unlock the bootloader and install Bell or Mex Retail because both are 4.1.2. I might even be possible to just swap the exploited binaries with the ones in our 4.1.2 roms, that's something someone else worried about this can do. Hell, it might even be possible to run the 4.1.2 roms with safestrap and the AT&T kernel...again, that's a someone else thing...I have no intention of dicking with SSR.

Think about Wifi being hacked....when it first came out a crappy password like 12345678 was good enough because computing power wasn't that good for consumers yet; nowadays, a basic gaming laptop can check 500,000 wpa2 passwords a second, a decent desktop with multiple GPU's can do over a million a second. All wpa2 hacking is sniffing out the verification md5*, then the tools generate passwords and their md5 and compare it against the sniffed out one, eventually you'll find one that matches, especially so if the password sucks. If you know how certain telecoms set up their wifi passwords, you can shorten the amount of time taken by limiting to the characters they use -- for example, AT&T U-Verse** uses 10 digit numeric passwords, so all you'd have to do is limit the tools to use numbers and start with 10 digits....hint: there are only 1 million codes if you use 10 numbers only....10 to the power of 10 and all....

That isn't a wifi hacking tutorial, just an example of how overtime good security unchanged becomes very bad security and how eventually an exploit will be found and security compromised, like how wpa2 for a split second sends out a the verification md5 unencrypted.

*not sure if WPA2 uses md5, but most of us know what md5's are

**last time I read about that service that's what I saw...and I read that a few months ago
[AT&T, Rogers HTC One X, Telstra One XL] s996kingsm:
well good afternoon. I messed up my phone and I am not quite sure how. :( on the bootloader screen I have

***TAMPERED***

***UNLOCKED***

EVITA PVT SHIP S-ON RL

HBOOT-2.14.0000

RADIO-0.24p.32.09.06

OpenDSP-v34.1.0.45.1219

eMMC-boot

Nov 26 2012,18:37:14:-1

so I was trying to get a new ROM on it I can move stuff to it using fastboot and adb but nothing will install I keep getting signature errors.

most of the time I can not find the ROM's I send through adb when I go to install them. It is like my SDcard died or is formatted funny. Any help would be great what can I do I just wanted something other than AT&T's 4.1 oh I have twrp 2.7.0.0 on it. cid: 11111111

Thanks

Steven
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Why are you using adb to send the ROM zips to your phone? You can use the "mount usb storage" feature in TWRP to mount your sd card as a removable drive in Windows and copy files across. What are the exact filenames of the ROM zips you've flashed? I need the exact filename. You're s-on so have you been flashing the boot.img via fastboot after flashing the ROM zip?
[AT&T, Rogers HTC One X, Telstra One XL] s996kingsm:
one of them I tried today is CleanROM-7.0R2.zip. I have tried to mount usb storage and it seems to never mount my sdcard when windows finally does see it it is not recognized with in windows and ask to be formatted.
[AT&T, Rogers HTC One X, Telstra One XL] exad:
Did you do a factory reset in bootloader? This corrupts the sdcard and requires formatting it
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
My guess is that you've performed a factory reset from within the bootloader, which corrupts the sd card. You're gonna need to wipe the sd card using TWRP, then mount it and format it (fat32 format) using Windows.
[AT&T, Rogers HTC One X, Telstra One XL] s996kingsm:
I will try that i do think that is what I did I have no OS on my device now. so hopefully this will help. thank you I will let you know if it works.
[AT&T, Rogers HTC One X, Telstra One XL] s996kingsm:
what if i cant get it to wipe the SD and so i cant get it to ask me in windows to format it anymore?
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Don't worry about that unless it actually happens. I can't think of any reason why that would happen, as long as you can get into recovery you'll be able to wipe your sd card and then format it.
[AT&T, Rogers HTC One X, Telstra One XL] s996kingsm:
I finally got it. I had to down grade twrp to 2.6.3.3 then my pc recognized my phone and the SDcard. I formatted it (the SDcard) rebooted to fastboot-usb (fastboot flash boot boot.img) reboot into recovery transfer the ROM.zip to the SDcard install the ROM in twrp. rebooted and it came up. Now the only thing I cant seem to do is get S-OFF working. Oh I am on CleanROM-7.0R2.zip

thank you for all the help.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
No problems. But please press the thanks button as opposed to actually posting thanks, it's the proper way to show our gratitude on XDA. Cheers.

Sent from my Evita
[T-Mobile Samsung Galaxy Note 3] bondidave:
Hi folks, long time reader, first time noob answer seeker.

I'm no stranger to rooting, flashing, hacking about and such - I even spend most of my day as a software engineer, and I've finally given up on this one - so here I am (rock me like a hurricane), please be kind.

SM-900T - It was rocking pretty darn well on Jedi Elite which I had flashed over rooted stock 4.3 MI7 - then (probably after one too many XPosed modules) it just kept rebooting randomly. Thinking it was no biggie, I thought I could just reflash to stock and call it a day. Thirteen or so flashes later, I gave up on 4.3 and figured I'd just take the thing up to 4.4.2 NB4 by upgrading everything to 4.4.2 via Kies.

That's when I first ran into the bootloop issue, read a lot about it, and managed to get it up(ish) on stock, rooted, with Philz 6.X... Couldn't flash a ROM to save myself and wound up with another soft brick.

Flash forward to Friday - decided to start from scratch again - attempted to flash stock 4.4.2 from Kies, from Odin, From Heimdall... Nothing seems to be able to get me out of the current state it's in:

Only boots to download mode. Flashes seem to work fine, but on that first reboot where it tries to go to stock recovery to finish up on the device itself, it never gets there - boot loops trying to load recovery no matter how it wants to get there. If I pull the battery and start up (either straight to system or by cancelling out of download mode), it boot loops trying to load system. Boots fine to download mode, where I attempt to flash again with the same results.

Yes, I've tried Odin 3.0.9, 3.0.7, 1.8.5, Heimdall on Mac, Heimdall on Windows, Kies on Mac, Kies on Windows - repartition via PIT and not. Installed, uninstalled, and reinstalled all software and drivers multiple times, tried multiple cables on multiple USB ports.... Most of the time it looks like it's going to be fine (sometimes the flash fails, usually through Kies), but never surivives that first reboot after the flash.

Every answer I've seen says to do the things I've already done or cannot do (flash stock via Odin, pull the battery and boot to stock recovery and do a factory reset - which I'd LOVE to do, but can't). No problem recognizing the sucker on the PC/Mac

Next step: try flashing a N9005 ROM...

Any other thoughts? I do have another N900T that's working but has a blacklisted IMEI, and I've been tempted to swap the IMEIs a last resort (although either I'm too dumb to make it stick, EFS pro says it succeeds in writing the IMEI after I do a EFS format, but it doesn't stick.... Either I'm missing something, or I need a UART cable) - is there a way of swapping just the radio hardware or just the internal storage? OR, is there a way of taking a full system image of my working phone and making an Odin-flashable tar from that?

Failing any of these options, perhaps I'll wait for an Odin-flashable 4.4.3 if such a thing exists - or, hope to get lucky and swap it out at a store praying they don't see I've tripped Knox.
[T-Mobile Samsung Galaxy Note 3] noobtoob:
Looks like you've tried almost everything. Take it in and have them swap it.
[T-Mobile Samsung Galaxy Note 3] bondidave:
Coming from you...

Coming from you (I have read, and am quite thankful for, many of your posts), sounds like that might be the best option, however disconcerting.
[T-Mobile Samsung Galaxy Note 3] noobtoob:
Well, I do have a few ideas... Got done questions though.

1. Do you have an external SD card?

2. It goes all the way through flash on 4.4 even with heimdall?

3. Is there anything you have left out? Even the smallest detail can help, and by the op you are detail oriented, so I just need to know.
[T-Mobile Samsung Galaxy Note 3] Frank Westlake:
Yes, but I don't have the details handy.

All your attempts suggest to me that you might have some damaged hardware which is causing data corruption during transfer. Open the back and take a good look at the USB port. Tighten the screws and try a transfer while firmly holding the cable in place -- don't move it while transferring.

If that doesn't work then let 'noobtoob' walk you through booting with the removable sdcard. Your second N900T will be needed to write the data to the sdcard. If this works then you can 'dd' write stock partitions to an sd card with #2 then 'dd' write them in #1.

If either of those works then unroot and take it in for warrenty exchange.

Frank
[T-Mobile Samsung Galaxy Note 3] Frank Westlake:
This also indicates data corruption, and this is what started it all. Since you have tried various cables and computers that leaves the device, probably the USB port.

Frank
[T-Mobile Samsung Galaxy Note 3] bondidave:
Swapped the main board with the working phone to rule out the USB port - still no luck.

Definitely interested in trying the boot from external SD, I'll do my own search for it, unless you can quickly provide me with a link - but if it's as easy as it sounds (booting off of an SD in order to be able to send ADB commands to dd copy the partitions from the good phone to SD then from the booted SD back to internal) - I'm happy to give it a shot.

Tempted just to swing by TMO just to see if they'll swap it "under warranty" (despite picking it up from a private sale) - the only way they would notice it's been "tampered" with would be to check the knox counter by attempting to run download mode.

Oh, and yes, it does go all the way through with the flash (at least in Odin - I haven't tried a full flash through heimdall, just boot and recovery, Kies occasionally goes through to the end, but sometimes craps out at the same 57% point at which point the emergency restore screen shows up)

Thanks again guys
[T-Mobile Samsung Galaxy Note 3] Frank Westlake:
OK, but I still think the problem was initially caused by corruption. Maybe the files you have been flashing are corrupt.

This is the thread, it would be good to read the whole thing but if you need to save time begin at this message: http://xdaforums.com/showpost.php?p=48685247&postcount=158

I have not tried this procedure yet but [MENTION=4404580]noobtoob[/MENTION] was actively involved in it.

Please try the SD-boot first so that we can add that experience to this newly developed procedure.

You have probably tried it, but if not, download fresh copies of everything and check the MD5 values.

Frank
[T-Mobile Samsung Galaxy Note 3] noobtoob:
This was for hard brick method and no one has verified it works on 4.4 KK yet. There is an image in there though. My mediafire shows it was downloaded 11 times, but yet not a single "this works on KitKat" response. Located here you will find the kkunbrick.img. There is still a problem flashing anything through heimdall after updating to the 4.4 bootloader, so there is no way to tell if the phone actually took the recovery. I have had to switch to Odin for everything afterwards, and in personal experience 3.07 works best with my phone.

[MENTION=5820450]bondidave[/MENTION] I was thinking skipping the sd-card trick for now, and trying just a few other things first. Do you have a nandroid of any 4.4 ROMS saved anywhere? I was going to say try and flash the stock image. After it gets through flash and tries to boot into recovery, go back directly to download mode. Flash philz or twrp, whatever you need to. Try and perform a recovery boot, wipe everything, and nandroid restore of a 4.4 if you have one.

Also if you have an external find the efs fix zip and have handy on an sd-card, do the same steps above except the nandroid restore. Basically if we can get into a recovery we should be ok. I had a similar issue when it was just booting over and over into download mode and this was how I fixed it. I have never used the efs fix zip, but many others swear by it. I was able to recover fortunately enough.

Last resort try the sd-card boot. I don't necessarily think it will work with this particular case as you do not have the dreaded QHUSB_MODE and your phone is still recognized by the computer(s) you have been using.

As far as making a complete system backup of your current phone, I highly recommend against it, unless you just want to extract information from it and not re-write it. This could definitely cause some system corruption on a new device.

If none of these methods work, then try and have them swap it under warranty.
[T-Mobile Samsung Galaxy Note 3] bondidave:
Yessirreeebobbyjimmy, tried several copies from several different places - that and Kies is a moron and redownloads it every time anyways.
[T-Mobile Samsung Galaxy Note 3] Frank Westlake:
I download these things just to have them handy if something fails.

I don't think he got that far into installing 4.4, but I recommend not using anything that was saved after this problem began. If the problem was caused by corruption then the restore will reinstall the corruption.

If the problem is bad USB or other bad hardware causing corruption during transfer then the SD-card boot will get past that, then transferring the rest of the partitions by SD-card will continue to be corruption-free. He could then trade-in the phone.

But you are right -- he should try everything else before the SD-card boot. Because if something else succeeds then maybe the hardware is fine, and if he went immediately to SD-card boot he wouldn't know that.

Frank
[T-Mobile Samsung Galaxy Note 3] bondidave:
Thanks for the advice guys - I'm going to try the backup from my other phone, then the efs fix, then the sd-card boot... I'll report back, wish me luck.
[T-Mobile Samsung Galaxy Note 3] noobtoob:
A nandroid previous failure, or a ROM install from external SD card was all I meant.
[T-Mobile Samsung Galaxy Note 3] Lorettaa:
I got some answers I was looking for here. Glad I read this thread.
[T-Mobile Samsung Galaxy Note 3] bondidave:
Glad something good came out of my frustration!

Here's a quick update: I've done everything but the boot from SD card with no luck (and actually thought I had hard(er?) bricked it for a while after trying to copy over a few images from the other phone - turns out it needed to stay with the battery out for at least 20 minutes).

Good news - walked into a TMO brick-and-mortar last night, showed the guy my endless bootloop, and a replacement is on its way to my house for an affordable $20 warranty service fee.

At this point, I'm thinking the internal flash memory is just bad - as a software engineer, I'm ok with chalking this one up to a hardware issue (as much as I was hoping that my first post on XDA would result in some new profound solution to a longstanding issue common to a few folks).

Oh well - new Note 3 on it's way, and a new S5 shortly behind it (didn't hold out much hope on TMO hooking me up, so I ordered an S5)... let the battle of the Samsungs begin!

Thanks again to you guys who helped out - and the whole XDA community in general, I am very grateful.
[T-Mobile Samsung Galaxy Note 3] Lorettaa:
Finally you made it fix and enjoy the battle between your phones :)
[T-Mobile Samsung Galaxy Note 3] noobtoob:
Well, sucks it couldn't be fixed, but glad you got a replacement on the way. It pretty much sounded like the partitions were well over written before we attempted anything, but always worth a shot.
[T-Mobile Samsung Galaxy Note 3] jacqueline robert:
Yes, but I don't have the details handy.

All your attempts suggest to me that you might have some damaged hardware which is causing data corruption during transfer. Open the back and take a good look at the USB port. Tighten the screws and try a transfer while firmly holding the cable in place -- don't move it while transferring. :good:
[7" Kindle Fire HD Q&A, Help & Troubleshooting] Mineturtle33:
I have root, GPlay, etc. On a 2013 fire hd. How can i get the aosp settings app to work? Thanks in advance.

Sent from my KFSOWI, 11.3.2.1, rooted, Amazon stuff replaced with Google Services.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] LinearEquation:
No custom ROM's for this tablet yet.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] Mineturtle33:
I didn't ask for a custom ROM. I asked if there is a method to get working aosp settings.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] LinearEquation:
Amazon is not AOSP and the only way to get AOSP is a custom ROM. Makes it hard to have AOSP settings don't it.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] Mineturtle33:
._.

Sent from my KFSOWI, 11.3.2.1, rooted, Amazon stuff replaced with Google Services.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] Mineturtle33:
Not knowing what you are talking about makes it a little hard to seem credible don't it.

Sent from my KFSOWI, 11.3.2.1, rooted, Amazon stuff replaced with Google Services.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] Deleted member 3621712:
Can u tell me how u got the AOSP settings?
[T-Mobile Samsung Galaxy S 5] skrewler:
I've got an S4 w/ T-Mobile and am eligible for a JUMP! upgrade. So I went to try to do it online, but the S5 isn't one of the choices available to upgrade to.

Looks like they have the S5 in stock on their site to buy though..

Anyone know whats up? Or has anyone done the JUMP! upgrade to S5 online?