yashsingh1/xdaforums huggingface dataset:
[Verizon HTC One (M8)] jtbndy:
I'll try and be as specific as possible as I hate having to resort to new threads when so many are out there, but I'm really at a loss.

Factory new phone (Verizon m8) or as close too it as possible.

Have tried multiple times installing Weaksauce and SU with the binaries but the binaries never install. Always fail and ask for reboot. The root is activated upon reboot after a minute or so. Rootchecker says root is activated and I have granted permission for a number of apps (Root Checker, Root Explorer, adb shell). I have uninstalled and reinstalled via the instructions and always the same issue of the binaries not installed.

Since the root was activated I have attempted to install firewater anyway.

I was unable to get the push command to work so instead I moved the firewater file into the /data/local/tmp manually with Root Explorer.

I attempt the firewater installation however get the following error when I input the chmod 755 command:

adb shell

shell@htc_m8wl:/ $ chmod 755 /data/local/tmp/firewater

chmod 755 /data/local/tmp/firewater

Unable to chmod /data/local/tmp/firewater: Operation not permitted

I have given SU privileges to the adb shell and accepted the prompt on my phone. Upon running the last command in the firewater instructions it executes, chugs, but then states the "whelp, firewater doesn't work on your device, yadadada".

I notice when I do the adb reboot command and the phone reboots the "HTC MTP Device" driver always fails when coming back from an adb reboot. I have installed the HTC Sync for the drivers and removed the Sync program. Could this be a driver issue? Or something else? I'm not sure why the chmod 755 command is not permitted? Is that potentially the issue as well?

I can wipe the phone to new if needed. Any assistance would be appreciated.
[Verizon HTC One (M8)] blestsol:
going through the same exact thing. I have a fresh verizon device and i checked to make sure everything matched up. and they do. Firmware, HBOOT, RADIO, everything.

I get to chugging and then bam..sorry this wont work on your phone etc. Whats also funny is this phone has a brighter clearer display and has a weird serial id. seomthing like FFA something when my original is HT something. Ive also factory reset 12 times.
[Verizon HTC One (M8)] Shadow Death:
Sounds like your phones have the newer boot loader. If that's the case you'll have to use the new root by jcase called sunshine or something like that. It'll cost you though. He started charging $25 for it.
[Verizon HTC One (M8)] jtbndy:
adb reboot bootloader yields the following:

HBoot-3.16.0.0000

Radio-0.89.20.0321

OpenDSP-v38.2.2-00542-M8974.0311

OS-1.55.605.2

eMMC-boot 2048MB

Apr 1 2014,00:26:53.0

I'll take a look at this sunshine. Thanks for pointing me in the right direction. Any further info from anyone else would be appreciated :)
[Verizon HTC One (M8)] thunderbls:
My phone yields the identical information.. Rooted soff'd and all custom romd up time and time again.
[Verizon HTC One (M8)] S1L3nTShaDoWz:
"Sounds like your phones have the newer boot loader" Are you saying Firewater was patched on the newer M8's with updated ones?
[Verizon HTC One (M8)] lucky_strike33:
I just exchanged phones with HTC and was still able to use Firewater
[Verizon HTC One (M8)] berndblb:
Did you follow the instructions here to the letter? http://firewater-soff.com/instructions/

If you could not push firewater to your device, it would indicate that weaksauce root is not working - or you did not wait long enough for it to re-root after the adb reboot. Or you did not catch the root request for an adb shell on your phone because the screen was off....

Make sure you use the second instructions, the Weaksauce method, not the root or temp root method.
[Verizon HTC One (M8)] jtbndy:
The only process I could not complete during the weaksauce root was installing the binaries with SU. It fails every time. I've uninstalled via the weaksauce instructions many times adb rebooted, and still the binaries will never install. Since I can move files around with Root Explorer is there any way to manually install the binaries?

If the root did not take, why does Root Checker say that I have root access a few minutes after reboot? I'm also able to grant SU permissions when asked for it (and approved the SU permission for Root Checker and adb shell).

Seems to me the issue lies with whatever the chmod command does and why that's not permitted or that the MTP drivers fail to install upon reboot.
[Verizon HTC One (M8)] Tigerstown:
you can't update binaries till your s-off. Just use weaksauce an download SuperSU from play store don't even open. Then run firewater commands to get s-off then uninstall weaksauce an SuperSU flash twrp an then flash SuperSU for root an you all set.

sent from my red HTC M8 using the free XDA app cause the paid one keeps f/c non stop?
[Verizon HTC One (M8)] jtbndy:
Without opening SuperSU I still get the same errors (HTC MTP Device Driver fail on adb reboot and the same error for chmod 755 command) as I did before including the firewater whelp message.
[Verizon HTC One (M8)] lucky_strike33:
Fastboot turned off?
[Verizon HTC One (M8)] jtbndy:
Fastboot has been off every attempt.
[Verizon HTC One (M8)] lucky_strike33:
backup your phone and then do a factory reset then do the process all over again? This might be the way to go. ONce you are back up, install weaksauce then supersu from play store. then go ahead and try the firewater. If no go, then try sunshine but I know its $25 but its easier to use than using firewater.
[Verizon HTC One (M8)] EKnofsky:
Can I chime in and ask if this should be done on ART or Dalvik? Or if that even matters
[Verizon HTC One (M8)] lucky_strike33:
Both times I have done it has been on dalvik. Hope that helps.
[Verizon HTC One (M8)] EKnofsky:
Thank you very much, I am switching over to Dalvik to test and see if anything works for me.

I have the same bootloader version as was mentioned earlier

HBoot-3.16.0.0000

Radio-0.89.20.0321

OpenDSP-v38.2.2-00542-M8974.0311

OS-1.55.605.2

eMMC-boot 2048MB

Apr 1 2014,00:26:53.0

I will report back if firewater works or if SunShine does.
[Verizon HTC One (M8)] lucky_strike33:
Try Firewater first since its free. Good luck.
[Verizon HTC One (M8)] EKnofsky:
I ran the SunShine app from http://theroot.ninja/ and it allowed me to S-OFF. At what point was I supposed to pay?
[Verizon HTC One (M8)] lucky_strike33:
After it says your phone can be s off and unlocked. Then takes you to PayPal to pay
[Verizon HTC One (M8)] EKnofsky:
Oh it never took me to paypal it just S-OFF'd my phone

http://imgur.com/Tzb1Av1
[Verizon HTC One (M8)] lucky_strike33:
Awesome! Enjoy flashing!
[Verizon HTC One (M8)] EKnofsky:
Are you using any specific rom? Any thoughts on http://xdaforums.com/showthread.php?t=2716306&page=174
[Verizon HTC One (M8)] lucky_strike33:
I'm on viper Rom. I have yet to try that Rom. Seems still in nightly stage and fixing errors. You can try it out and see if you like it or not.
[Verizon HTC One (M8)] lucky_strike33:
[MENTION=487576]teaman[/MENTION]dIRC: Ran an impromptu promo for SunShine this morning, anyone that tried to buy it for an hour got a free license! Congrats!"

U got lucky!
[Verizon HTC One (M8)] geosnipe:
BOO HOO :.(.

I have a new M8 because I pitched a fit to VZW and they gave me $400 of the device, but now I cant get permanent ROOT. This really does suck, I even tried the Sunshine and No Love there either. Can SOMEONE/ANYONE please help me?

Thanks in advance!

* ALL IS WELL_ SOLVED!
[Verizon HTC One (M8)] BadUsername:
What error does firewater throw?

And what is sunshine doing specifically when you open it? Are you getting to the PayPal page?
[Verizon HTC One (M8)] geosnipe:
Firewater gave me whelp my device is a terd..lol

Sunshine did not work last nite but tonite it did take my money and give me s-off with root. I guess I'm good now, I just would've liked to donate on my own rather than be forced to purchase ROOT. Anyhow, all good and I appreciate all devs work. Me and My M8 are happy!
[Verizon HTC One (M8)] BadUsername:
Lots of people would gladly donate, but most wouldn't.

Glad it worked out for you.
[Verizon HTC One (M8)] geosnipe:
donate more

I actually just donated to scottsroms cause I finally got a cleanrom!
[Verizon HTC One (M8)] alibhatti:
Hi friend i need some unguent help. I am stuck on this 2 screen cant go no where. any kind of reboot brings me back on this 2 screens. if i connect with my pc via usb and try to flash recovery its keep giving error signature verify fail some if i try to flash any rom by put it into sd card.

All i have done is run following command and now i am not able to do anything.

adb shell

su

echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796

exit

exit

adb reboot bootloader

fastboot oem writesecureflag 3
[Verizon HTC One (M8)] jsaxon2:
Not sure what you were trying to do, but those are the commands to lock your bootloader and go back to s-on. I don't know if there is a way for you to now get your phone working. Hopefully someone knows something you could try. Good Luck.
[Verizon HTC One (M8)] Tigerstown:
This has been fix a few days ago. :)
[Verizon HTC One (M8)] jsaxon2:
Copy. What was the fix?
[Verizon HTC One (M8)] Tigerstown:
That's guys super jackup phone. He had no os locked an s-on. An dottat got him a os an s-off an re unlocked an up an running. What a mess that picture is tho lol
[Verizon HTC One (M8)] awalysis:
Please i need someone to help me firewater i cannot find
[Verizon HTC One (M8)] dottat:
Totally off topic man...

Firewater is dead. It relied on a server side piece to function so even if I gave you the files it would never work again.
[Nexus 7 Q&A, Help & Troubleshooting] Gloftking:
I already had a problem where I was stuck in a bootloop and was told to flash the stock image (see here for previous issue : http://xdaforums.com/showthread.php?t=2783631 ). I did this and tried it with the Nexus root toolkit with no wipe mode enabled and when I tried turning on the nexus I get this very annoying looping screen which shows the word google in the middle and the green start button at the top pointing towards the power button. every time I press the power button the green sign reapears and nothing happens. when I do this from the fastboot screen (using cmd on PC) I see a little message in the upper left corner saying "booting failed". I cannot seem to get the adb working at all which is a real problem and I am not sure if this tablet is reparable but I need someones help urgently http://xdaforums.com/images/smilies/mad.gif
[Nexus 7 Q&A, Help & Troubleshooting] deltatux:
Have you tried to flash the stock Android images using fastboot?

Note: Following command WILL WIPE your device.

fastboot -w update image-nakasi-ktu84p.zip

For Nexus 7 (2012 WiFi): https://developers.google.com/android/nexus/images#nakasiktu84p

For Nexus 7 (2012 3G): https://developers.google.com/android/nexus/images#nakasigktu84p

deltatux
[Nexus 7 Q&A, Help & Troubleshooting] Gloftking:
I just tried that

I tried what you said and when I entered the code in the cmd I got the following

"archive does not contain 'boot.sig'

archive does not contain 'recovery.sig'

archive does not contain 'system.sig'

< waiting for device >" (without quotes)

and it just hangs here. Any idea what the problem is?
[Nexus 7 Q&A, Help & Troubleshooting] Gloftking:
for some reason whenever I try to execute your code I get

"archive does not contain 'boot.sig'

archive does not contain 'recovery.sig'

archive does not contain 'system.sig'

< waiting for device >" (without quotes)

and it just hangs there

I appear to have bricked my nexus 7 as the tablet is not starting at all and I can recall that at some stage I accidentally used the fastboot command "fastboot erase bootloader" (not sure if it actually did that)

any ideas how to reverse this?

BTW in device manager the tablet shows up as UNKNOWN Device
[Nexus 7 Q&A, Help & Troubleshooting] deltatux:
If you erased the bootloader without flashing another one back in, you just bricked your device. The only course of action to save it is to do an nvflash but that would have required you to back up the nvflash blob before this incident. If all else fails, your tablet's a dud.

I would recommend either replacing your entire tablet or buy a replacement board on eBay and replace the motherboard yourself and then it will run like new.

deltatux
[Nexus 7 Q&A, Help & Troubleshooting] Erovia:
If you entered that command, your device is hardbricked and the only thing you can do about is to send it to Asus/Google for RMA.
[Nexus 7 Q&A, Help & Troubleshooting] deltatux:
I doubt Google/ASUS will repair it and if they do, it'll likely cost you as much as a new tablet. I still stick to what I said and either get a new tablet or replace the motherboard yourself.

deltatux
[Nexus 7 Q&A, Help & Troubleshooting] Gloftking:
That is so annoying

I was trying to flash another bootloader called ("bootloader-grouper-4.23.img") but I think some error occurred in the command prompt and I am very surprised it actually let me do that unknowingly.

Is there another boot loader inside the nexus 7 that allows this procedure of swapping bootloaders to take place or is there any kind of hard reset button inside the nexus (I don't care what happens to my data on it)
[Nexus 7 Q&A, Help & Troubleshooting] Gloftking:
how on earth are you meant to use the nvflash software and does it definitely require a blob file.

BTW I do seem to recall that I saw a "writing to bootloader message" in cmd before it became inoprable. does that mean there is any better chance of this thing being revived?
[Nexus 7 Q&A, Help & Troubleshooting] deltatux:
nvflash is meant to be a debugging software as an absolute last resort to restore a Tegra based device. More on nvflash here:

http://xdaforums.com/wiki/Nvflash

The blobs are tied to your device because nvflash works pretty much at hardware level, so without your own blobs, it's nearly impossible to recover. Here's the procedure to extract the blob before brick: http://www.xda-developers.com/andro...nexus-7-and-other-asus-tablets-with-flatline/

As for "writing to bootloader", if you can't access the bootloader now, it may be because you flashed the wrong bootloader (likely from the 3G variant of the Nexus 7 instead of WiFi-only or vice versa). Unless you can somehow gain access to fastboot, you'll need to recover via nvflash.

Without the blobs backed up, you'll probably be better off replacing the Nexus 7 motherboard with a working OS and all.

deltatux
[Nexus 7 Q&A, Help & Troubleshooting] Gloftking:
cant believe this

are you people seriously saying that one command sent electronically through a wire can physically break a device to the extent that it is 100% impossible to repair electronically (if there are no blob files made in advance to preform a recovery). It just makes me wonder how could such a command exist (who on earth would use it). as fer as replacing the motherboard is concerned my n7 is a 32 gb meaning it will be hard to find an affordable replacement.

BTW I am pretty sure the bootloader was for the wifi version (my n7 is wifi) and I am also suspicious that the nexus toolkit had bricked my tablet because I tried the temporary boot feature and I saw in the corner something like "downloading bootloader img". At some other point in time I used the dreaded command (either before or after). I cant remember which one of these these operations had caused the brick because it was only later I noticed the tablet was in a Sleep of Death http://xdaforums.com/images/smilies/mad.gif

thanks for the advice anyway
[Nexus 7 Q&A, Help & Troubleshooting] ArXiLaMaS:
Deltatux can you tell me pls if I can use this guide with KK 4.4.4?

Sorry for asking here but I can't post yet in the developers threads.
[Nexus 7 Q&A, Help & Troubleshooting] Gloftking:
Just a potential fix proposition

guys I have managed to get my nexus 7 into APX mode by pressing the buttons on the side however I am not sure where to go from here. Every time I try to update driver in device manager I get the error "There is no driver selected for the device information set or element" and as a result cannot update it to the asus apx mode interface thing that nvflash provided. if there is any other possible course of action I can take from here that does not involve physical repair then please do let me know after all I Only plan to replace the motherboard as a last resort option
[Nexus 7 Q&A, Help & Troubleshooting] Erovia:
To be able to recover from APX mode, you'd have to have a backup of your tablet. Without a proper backup, you can't do much. Also, there is no way of using someone else's backup, since every motherboard has a different signature key.
[Nexus 7 Q&A, Help & Troubleshooting] nihil sleighride:
Could someone confirm if my assumptions are correct?

Mine is stuck in APX mode therefore if I send it to ASUS to repair my data will lost? If the motherboard is replaced my data is lost? In its current state my data on it is unrecoverable?

Just wondering if it's safe to sell for spares, seeing that I've got no way to wipe it.
[Nexus 7 Q&A, Help & Troubleshooting] Gloftking:
hold on a minute

I thought NVFlash could somehow be used to flash a completely new bootloader with a 'new' crypto-signature as that is the sort of thing that can be achieved with the nexus 5 and various other non Tegra 3 devices. What is the big deal with the n7 and besides how can you expect anyone to use a system like that (blobing in advance) when perhaps 90% (or more) of people who run into this problem have never herd of such a system and would then be completely SOL.

Also is there any way in which one could get hold of the internal SD card practically so it can be taken out and surgically re-implanted into the new motherboard or vice-versa with the bootloader to prevent me from having to purchase another 32GB logicboard (such a waste).
[Nexus 7 Q&A, Help & Troubleshooting] Gloftking:
Oh and yes all data will be lost if they replace the motherboard as they will throw away the old one or re-use it and re-solder etc. However if you're lucky they will use special tools to flash the software back into the main board although this is almost guaranteed to format everything on the internal SD unless you can detach it somehow beforehand (still waiting on an answer for that one) or ask the data recovery people to rescue the data when you get it back (that's only if they did not throw it away) or even tell the asus repair service not to delete the data if possible. The main issue is when you flash a tablet or phone you will be re-installing the operating system and the internal SD is part of that operating system so there is almost no way to save the data on it in just a soft-bricked state never mind a hard-bricked one.

And yes most of your assumptions would match that of my own right now. having said the above there is probably no way an end user could get data off it if you sold it as a spare because there would be no way to access it unless they managed to escape the apx mode and used some kind of file recovery program via the adb which is why I do then again say don't give up hope just yet (I am not an expert)

BTW how did you get into APX mode because if you did what I did (erased the bootloader via fastboot) then you are as of now SOL (awaiting further confirmation of that) whilst on the other hand if it was a charging issue or anything else then I would not recommend any of the above suggestions. There are numerous stories of people being stuck in apx mode and got out again after some time and if you did not modify your tablet before this happened then all your data will still be their

there seems to be too many APX 'ed devices right now and I just wonder what Google must be thinking about this and if they will do something or not
[Nexus 7 Q&A, Help & Troubleshooting] nihil sleighride:
Mine was rooted and had been pretty much updated when a new Paranoid Android was released. I flashed a new release, which took way longer then normal to update. All seemed OK but a few hours later, it completely locked, so I attempted to reboot and that's when it got stuck in APX.
[Nexus 7 Q&A, Help & Troubleshooting] bshiznit:
RMAed $165 HELP!

[MENTION=3967911]deltatux[/MENTION], et al. - so the cable came out when I was trying to flash bootloader (which was taking FOREVER... very unusual) in my daughter's tablet and I had to send it in for RMA. They want $165 for the motherboard ALONE. I've asked them to ship it back to me.

If I get a new motherboard off like eBay is it just a simple swap? I'm just checking I have built many PCs over the year and think I can handle the swap...
[Nexus 7 Q&A, Help & Troubleshooting] Gloftking:
Guys have any of you seen this

This is a known story of a guy who actually managed to escape the SOL situation we are all in (bricked by entering "fastboot erase bootloader" in cmd) and I am not sure why it happened

http://androidforums.com/nexus-7-ge...icked-bootloader-erased-help.html#post5289634

post number 15 by rootbrain

does this mean the n7 2012 has a backup mechanism of some sort or did he just install his own on the bootloader? http://xdaforums.com/images/smilies/fingers-crossed.gif
[Nexus 7 Q&A, Help & Troubleshooting] bshiznit:
$30 motherboard off eBay - installation wasn't too bad - and now tablet is working
[Galaxy S 4 Q&A, Help & Troubleshooting] kerko:
Hi all, is there a way to increase the sound of our device? I think viper does not work or its it my mistake? My s4 is rooted. Thanks
[Galaxy S 4 Q&A, Help & Troubleshooting] BigBugHmb:
Viper4Android… not only louder, better Sound incl.
[Galaxy S 4 Q&A, Help & Troubleshooting] kerko:
It says that there are some changes to be made...because of LPA...and I was afraid to allow it. because I do not have a custom recovery to make backups..so viper is not functioning correctly...I need to uninstall it I guess
[Galaxy S 4 Q&A, Help & Troubleshooting] BigBugHmb:
Uninstall is not a problem… in menu you can uninstall drivers and after that you can uninstall the apk normaly. Works fine for me on five different devices.

1) SGS 3, 4 & 5

2) Galaxy Note 10.1 (2013)

3) Huawei G700

… no fear

The LPA modding is only to set them from True to false. You need them for working with third party music Apps.

Backup the "build.prop" is enough security.
[Galaxy S 4 Q&A, Help & Troubleshooting] kerko:
Thank you for your answer. How do I back up the build.prop please?
[Wear OS Q&A, Help & Troubleshooting] sergiuhusca:
I want to buy a smartwatch and i don't know what to choose?

SAMSUNG GALAXY GEAR o SAMSUNG GEAR LIVE?
[Wear OS Q&A, Help & Troubleshooting] sergiuhusca:
nobody?
[Wear OS Q&A, Help & Troubleshooting] Edge330:
Wait for motorola 360.
[Wear OS Q&A, Help & Troubleshooting] jimbohurt:
Live. Android wear operating system will be awesome dude
[Wear OS Q&A, Help & Troubleshooting] AstroDigital:
Have a Gear Fit, ordered Gear Live.

Android Wear, is the future I think now devices are soon here Tizen based Gear 2/Neo will fail.
[Wear OS Q&A, Help & Troubleshooting] sergiuhusca:
Yes...but without english, android wear is dead...
[Wear OS Q&A, Help & Troubleshooting] AstroDigital:
Why would anybody waste my time by replying with such a stupid comment?

You know and I know Android Wear supports English, so I assume you are posting as a grammarian..... I do not care what you think.

I can care less if YOU think everybody posting should proof read, have perfect English grammar and spelling.
[Wear OS Q&A, Help & Troubleshooting] Karthickgandhi:
Pls upload
[T-Mobile Samsung Galaxy S 5] superhtchd2:
ive tried every root method and none are working on my phone. towel root, didnt reboot after so says should be rooted and not. tried cf auto root and goes through the steps and into recovery but doesnt root. tried philz recovery and root and went into recovery and flashed update root and still nothing. what am i missing? with the tool kit after flashing twrp i can actually get a su icon error on the phone saying it needs to be flashed via twrp or play store and neither of those methods work after doing so..
[T-Mobile Samsung Galaxy S 5] masanamuthu:
Whats ur model ¿¿¿
[T-Mobile Samsung Galaxy S 5] superhtchd2:
sm-g900t