[GUIDA] [S-OFF] FIREWATER

Ciao a tutti, sto cercando di scaricare firewater ma il sito è offline. Qualcuno ha una copia del file da darmi o può indicarmi un link alternativo?
Grazie 1000!

 

Hai provato dal link presente nella guida?

 

Probabilmente è proprio il sito offline e quindi il link, se trovo una versione nel pc la posto, ma sarà vecchiotta

Send with my HTC One M8 from Tuttoandroid

https://docs.google.com/file/d/0BwIEvj1cuMC5WUc4a1IteFdrdlE/edit?usp=docslist_api

Send with my HTC One M8 from Tuttoandroid

 

Se può servire la versione aggiornata può essere scaricata da qui

 

Innanzitutto grazie! Solo non capisco come mai è un file zip. Non dovrebbe essere un file chiamato "firewater" senza nessuna estensione?

 

Si scusa, è questo.

 

Ok, grazie! è recente?

 

è l'ultimo da quando il sito è andato off, preso dal web archive

 

al link che ha postato kalel77 trovi quello che chiedi tu ...

 

grazie a tutti! Siete preziosi ;-)

- - - - post aggiornato - - - -

Rieccomi...
Dunque quando digito l'ultimo comando non succede niente, la procedura non parte.
Ecco il listato dei comandi che ho dato. Cosa sbaglio?

C:\Users\Federico\Google Drive\HTC-ONE-M8 Tools\adb>adb reboot

C:\Users\Federico\Google Drive\HTC-ONE-M8 Tools\adb>adb wait-for-device push firewater /data/local/tmp
3030 KB/s (4522136 bytes in 1.457s)

C:\Users\Federico\Google Drive\HTC-ONE-M8 Tools\adb>adb shell
shell@htc_m8:/ $ su
su
root@htc_m8:/ # chmod 755 /data/local/tmp/firewater
chmod 755 /data/local/tmp/firewater
root@htc_m8:/ # /data/local/tmp/firewater
/data/local/tmp/firewater
root@htc_m8:/ #

 

Ok, ho verificato cosa succede ad ogni comando:
"adb wait-for-device push firewater /data/local/tmp" carica il file nella suddetta directory. Ho verificato con solid explorer ed effettivamente il file si trova nella cartella.
"chmod 755 /data/local/tmp/firewater" cambia i permessi di lettura/scrittura/esecuzione sul file. verificato con solid explorer e i permessi sono corretti.
Poi, lancio il comando "/data/local/tmp/firewater" e non succede nulla. inoltre il file "firewater" scompare dal telefono; Non è più presente in data/local/tmp...
Cosa sbaglio?

- - - - post aggiornato - - - -

Ho notato che nel bootloader non compare la scritta tampered, può voler dire qualcosa?

 

Che recovery hai?

Send with my HTC One M8 from Tuttoandroid

 

TWRP... Può essere il file "firewater" danneggiato? Scaricato da webdirectory...
Webarchive, intendevo.

 

no, il fatto che non sia tampered e' strano, come e' strano che sparisca dalla temp...su che firmware lo usi?

 

Il firmware è il 3.32.771.10 brand h3g ITA

 

Ragazzi forse non abbiamo considerato un fattore fondamentale

ATTENZIONE  

Prerequisiti

A working internet connection ON YOUR DEVICE - wifi, 3g, 4g, etc. are all supported.
There is no way around this requirement, don’t ask

se il firwater ha bisogno di una connessione attiva
significa che necessita di comunicare con un server
se il sito è Down ... credo proprio che non si possa fare nulla !

 

il sito è di nuovo on line con questa brutta notizia :-(

NSTRUCTIONS/DOWNLOAD
firewater is officially discontinued, please read

For nearly 3 years, I have spent a significant portion of my personal time developing methods to unlock and s-off HTC devices. I’ve developed, or been a part of the development of 5 different s-off methods, all of which are used by many users every day.

firewater s-off was a unique product for a few reasons:

It was based on a true “hardware exploit”
It was able to execute fully in userspace from within Android
It could not work on all targeted devices, even on release day
#3 is an important distinction. As many users discovered shortly after release, firewater could not work on many devices, even devices that seemingly were the “exact same” as other devices that firewater did work on. While I was very vague with users regarding the reason their device couldn’t be supported, users figured it out on their own: a specific brand of eMMC was not vulnerable to firewater’s attack.

Some time after firewater was released, HTC began shipping the m8. While the m8′s architecture is significantly different than the m7 that firewater initially targeted, I was able to find a method to adapt firewater’s strategy to the m8.

Much like the m7, that same specific brand of eMMC was used in many m8′s – rendering firewater useless on those devices- there are countless threads about firewater’s dreaded “whelp” message.

Besides the “whelp message”, firewater was always a tempermental thing – it relied on more than one hardware race condition, and as such took the average user nearly 5 runs to achieve success.

Since the release of firewater for the m8, we’ve seen HTC employ 4 different strategies to block firewater:

patching the Android kernel to remove the hooks we target in userspace
updating low level loaders to xpu-protect firewater’s target registers
removing some critical kernel functions
updating eMMC firmware in eMMC controllers that were “known-working”
None of this comes as any surprise to us, nor should it surprise you. Other projects I’ve been involved in have been patched at a similar pace – facepalm, moonshine, rumrunner, even sunshine – all of these vulnerabilities have been predictably addressed by HTC.

Prior to the release of firewater for the m8, I discovered the vulnerability that would later turn in to sunshine s-off, our first “paid” release. The sunshine team has shared many times our reasons for making sunshine s-off a paid product, I won’t regurgitate it all here. Sunshine s-off is a great product that took significant resources to develop. Most sunshine users are great supporters of the project and more importantly – they are satisfied with the product.

TLDR; why is firewater discontinued?

firewater is being discontinued for these reasons:

due to all the mitigation strategies employed by HTC, it is not feasible for us to advise users whether or not firewater will work for them. As such, there are many reports of “chugging all 12 bottles and no buzz”. It is very difficult to accurately read and manage eMMC firmware versions
Due to those same strategies, it no longer works on most m7′s or m8′s
The rampant speculation and accusations by many users that we have intentionally ruined firewater in order to spur sales of sunshine. I will update this page later with a list of all of those users, but rest assured: they have ruined it for the rest of you. While it disappointed me every time I saw a post about the dreaded “whelp message”, I’m truly shocked and disappointed to see the accusations that we are somehow doing this intentionally. jcase and I have spent far too much time defending ourselves in these cases, and it’s caused a SIGNIFICANT amount of wasted time and stress within the sunshine team. I’m truly disappointed to have had my credibility questioned – all for a product I provided FOR FREE.

By discontinuing firewater, we can now end the speculation and related drama and focus our time and efforts on the future.
RIP firewater, I wish I could say I’d miss you.



–beaups

Forse è questo il problema...

 

puoi anche togliere il "forse" !!!
... sapevo già di questa situazione
ma avevo pensato che successivamente avessero chiuso anche il sito
ed era questo che intendevo dire prima !!

 

A questo punto non resta che sunshine, o fallirà anche questo?

 

nelle ultime versioni firmware dell'M8 non funziona ... si deve aspettare una nuova versione ?