My buddy tested this out on his Butterfly and it turned out to work good. Full ROOT with S-OFF.
I am not the creator of this one click, but I was told it could be shared freely, as it also describes in the .ZIP contents.
I did not personally try this out myself (My One X is already rooted + S-OFF) so be sure to check it out and read all the documents before trying out this new root exploit.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It did finally pick up my One X after about 10 mins (more like 2), but like I said I'm already rooted. It looks like it supplies a good amount of phones, and with the 3 different methods for rooting, especially the third, hopefully we will see some good results!
I'm not responsible for harm that comes from this file, I have ran and tested it out to SOME EXTENT. Please be aware of this, and like I said, READ THE DOCUMENTATION.
It states it can:
Root Android 2.x
Root Android 3.x
Root Android 4.x
Rooting Phones and Tablets
Supplies S-OFF as well (80% Chance)
So, like I said, try it out and let me know if it works!
Nice one !
Sent from my HTC Butterfly using xda premium
somebody please explain to us noob, what is the advantage of s-off? mine is rooted but s-on. is this worth the risk? Thank you!
royskeyz said:
somebody please explain to us noob, what is the advantage of s-off? mine is rooted but s-on. is this worth the risk? Thank you!
Click to expand...
Click to collapse
What Is S-OFF?
In their devices, HTC have installed a sort of security check whose level is determined by S-OFF/S-ON. Essentially, this security level is a flag stored on the device’s radio that checks signature images for any firmware before it is allowed to be written to system memory. This hinders using any custom ROMs, splash images, recovery etc., and also restricts access to the NAND flash memory. However, when security level is set to S-OFF, the signature check is bypassed, allowing a user to upload custom firmware images, unsigned boot, recovery, splash and HBOOT images, as well as official firmware that has been modified, this enabling maximum customization of your HTC Android device.
Furthermore, S-OFF also reduces restrictions on accessing the NAND flash memory on the device, allowing all partitions (including /system) to be mounted in write mode while the operating system is booted.
Is this for the X920D/X920E/Both? Really happy to know it works
Doesn't work.. I tried on the x920d (UB1).. while on, while in bootloader, while in fastboot.. doesn't work.. just sits there with message "looking for HTC Butterfly" for almost 20 mins, before I closed it.
Since I have tested it myself, I am going to close this thread, just incase someone tries something else and has a brick.
Related
Ok, so I've now been through SBFing my phone for the second time, and I'm starting to learn a little, but I'd like to get some clarification on how the different functions and components involved relate to each other. I'm trying to put together a mental picture of a smartphone's software components to understand all of this better.
Basically I'm trying to identify the differences and connections between the bootloader (specifically locked bootloaders, as found on my Droid X, et al.), the recovery partition, the kernel, SBF files, nandroid backups, and the customizable portions of a ROM. I've drawn a diagram that illustrates to the best of my ability the connections I've been able to put together, which I will explain here.
As I understand it the bootloader tells the phone what to load when it boots up. Apparently, locked bootloaders have some restrictions as to what can be loaded, which prevent custom kernels from being loaded. I'm not sure how this works exactly, but effectively it seems as though the bootloader ensures that the kernel being used is appropriate for the phone.
However I'm pretty certain that the OS image you put on a phone contains the kernel, but the entire OS is not locked down, so that makes it seem like the bootloader only ensures that the kernel portion of the image you use is kosher, and doesn't care about the customizable parts (e.g. all of the changes in a Cyanogenmod ROM versus a stock ROM).
As I understand it, a phone comes with a stock recovery... thing. I don't know if this is a separate partition that can be loaded or if it's somehow part of the OS itself. But clearly, on rooted phones this can be customized as well (i.e. clockwork recovery et al.). The diagram below puts the recovery thing inside the OS "bubble" but perhaps it should be outside.
Nandroid backups are clearly some form of image, but do they contain the entire OS, or just the custom ROM part, as in the diagram below? Does the success of a restored backup depend on the kernel that's loaded?
As for SBFs, how does an SBF file compare to a ROM ZIP file? And how do these compare to nandroid backups? Are they all just images? What makes them different? If the kernel can't be changed, then is a cyanogenmod release (for example) a full OS including a copy of the kernel it was built on (e.g. Froyo, GB), or is it only one part of the whole?
I hope I've explained what I'm looking for well enough. I know enough to be dangerous, as the saying goes, but I'm sure anyone who knows what they are talking about will read this (and the diagram) and go "wow is this guy confused". So help a brother out. Can anyone correct me where I'm wrong and help me build a more accurate mental image of how this all works? I'm a very visual learner, so a corrected diagram would be a big plus as well. Thanks for any insights.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Rooting, I love rooting devices, till now, I have rooted countless devices, for others too..
rooting gives you the access to everything and you get SuperUser access.
Advantages
It gives you full access over your phone and enables you to fully customize it
You can block ads from apps
gives you access to root-only apps like Titanium backup & root explorer.
You use custom kernels that can improve performance and increase battery backup
you can overclock the processor to increase (for fast performance) or decrease (for better backup)
use custom ROMs (that I'm also making for GS2)
you get the latest version of android (last night i installed jellybean on S2)
Unlock additional features like WiFi and USB tethering
Upgrades baseband (it controls radio, improve signal & quality of your smartphone)
now here we come to disadvantages, whoa.... you'll be scared
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It voids your warranty
Your phone may brick (however you can fix it if you have basic knowledge about ROMs, i fixed S2 too)
Security, viruses can enter (for explanation consider POST#2)
Source Code, android is open source and anyone can see the source code after rooting and it can be used for malicious purposes (refers to above point)
But don't worry, you can still Un-root it any time you want to
Hope you understood everything I said, still ping me back if you need to know anything else
Note: rooting process is different for every device.
Note2: I have written all I knew, pls let me know if I missed anyone
Getting root within Android does not guarantee the ability to flash custom kernels, radios, etc. Some devices have locked bootloaders, but can be rooted relatively easily (most Motorola devices).
Rooting isn't any more insecure than non-rooting as far as viruses go. If you have a Superuser app installed, any app that wants root will have to get your permission, so only allow apps you trust. This is somewhat similar to how any Linux distro operates and is part of the reason they are secure. Malicious apps that contain a root exploit would be dangerous even without root since the exploit can be done without superuser permissions.
spunker88 said:
Getting root within Android does not guarantee the ability to flash custom kernels, radios, etc. Some devices have locked bootloaders, but can be rooted relatively easily (most Motorola devices).
Rooting isn't any more insecure than non-rooting as far as viruses go. If you have a Superuser app installed, any app that wants root will have to get your permission, so only allow apps you trust. This is somewhat similar to how any Linux distro operates and is part of the reason they are secure. Malicious apps that contain a root exploit would be dangerous even without root since the exploit can be done without superuser permissions.
Click to expand...
Click to collapse
Thank you for this explanation
I hope there's nothing more that I missed
So in terms of getting my HTC One S repartioned I need to get hboot 2.16. In terms of getting hboot 2.16 i need my phone S-OFF. In terms of getting my phone S-OFF I need to get Super cid: 11111111. (What kind of absurd adventure is that? seriously!)
So in that very last step of the chain I landed here and while going through this instruction I fail getting permissions:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Guys, and tell me: Is it really that complicated or am I just missing something? I mean what is with that endless IF-Chain?
/edit: I am getting desperate here. I have even tried this rumrunner.us-thing.
Resultet in this:
Castor-designs said:
So in terms of getting my HTC One S repartioned I need to get hboot 2.16. In terms of getting hboot 2.16 i need my phone S-OFF. In terms of getting my phone S-OFF I need to get Super cid: 11111111. (What kind of absurd adventure is that? seriously!)
So in that very last step of the chain I landed here and while going through this instruction I fail getting permissions:
Guys, and tell me: Is it really that complicated or am I just missing something? I mean what is with that endless IF-Chain?
/edit: I am getting desperate here. I have even tried this rumrunner.us-thing.
Resultet in this:
Click to expand...
Click to collapse
is your device rooted, you need root to use rumrunner, and maybe close your virus program on you pc.
which windows version you have?
pauldey said:
is your device rooted, you need root to use rumrunner, and maybe close your virus program on you pc.
which windows version you have?
Click to expand...
Click to collapse
Yes My device is rooted, I have enabled root for both apps and adb and I also have superSU with the default option to allow root enabled. So I also see in the log, that shell is performing some root-action-stuff.
Windows 7. all Firewalls are off.
Hi,
I bouth a used Z5 and I just found that it was unlocked and then restored the drm.
I read some posts saying that you lose functionality, and that it also affect to the camera. Other posts say that that depends on the way you unlock it, others say that you cant restore it, and others that you can depend on your the method.
My security service info stands like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What functions am I missing? Can I get them back?
Look, about the drm keys, if the one who unlocked the phone kept the drm keys then you can restore it. If that person didnt keep the drm keys, then you lost them for good. You cant use any other z5's drm keys or you will brick your phone. The good news is, you can restore all the functionalities back by flashing a zip file. You will have to root the phone first.
Sent from my E6653 using Tapatalk
thanks. you said that it is possible to restore all the functionalities back by flashing a zip file. which zip file? there many different of them saying that can do it, an many people saying that some of them dont work and can brick the phone ....
Latiosman said:
thanks. you said that it is possible to restore all the functionalities back by flashing a zip file. which zip file? there many different of them saying that can do it, an many people saying that some of them dont work and can brick the phone ....
Click to expand...
Click to collapse
may be he reffers this thread, http://forum.xda-developers.com/xperia-z5/development/sony-credentials-restore-unlocking-t3296383
but you need to have root permissions and a custom recovery.... if you want to know how to install it here's a nice guide step by step
http://forum.xda-developers.com/xperia-z5/general/guide-sony-xperia-z5-unlock-root-tweaks-t3298224
I talked with the last owner, and he said that he already installed drmrestore.zip...
but the screen still stays like the screen I posted in the first message.
How can I check if I have lost functionallity? how cna I make sure that the camera and everything is fully working ok?
Latiosman said:
I talked with the last owner, and he said that he already installed drmrestore.zip...
but the screen still stays like the screen I posted in the first message.
How can I check if I have lost functionallity? how cna I make sure that the camera and everything is fully working ok?
Click to expand...
Click to collapse
Hi.
I think so in your first post have the solution about your questions...
When you flash drmrestore .zip restore marlin and widevine and it appears ok. But fido Keys appears not provisioned.
Then it's possible that mirrorlink doesn't work, and camera work slowly.
When you restore your drm Keys you can read in fido Keys: provisioned and all functions works fine.
Enviado desde mi E6653 mediante Tapatalk
Technical question. If I do root in oneplus 6 then generally this "android, embedded, hardware encryption" will be at risk now, yes? Getting to the files on my phone is now possible, yes? Such a simple scenario. I lose the phone or someone steals and by unlocked bootloader and TWRP can easily preview and rip files from the phone, yes? So it this situation encryption doesnt work. Am I right? However, if I won`t do root and will not unlock the bootloader, then encryption works and without my password or fingerprint there, the phone is only suitable for factory reset, so photo files, etc. are still 100% safe. I understand correctly? What do you think?
Post scriptum... and this fuc#@ng root is just so that you can record conversations in android pie because Google blocked this function
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
lxxxxxxl said:
Technical question. If I do root in oneplus 6 then generally this "android, embedded, hardware encryption" will be at risk now, yes? Getting to the files on my phone is now possible, yes? Such a simple scenario. I lose the phone or someone steals and by unlocked bootloader and TWRP can easily preview and rip files from the phone, yes? So it this situation encryption doesnt work. Am I right? However, if I won`t do root and will not unlock the bootloader, then encryption works and without my password or fingerprint there, the phone is only suitable for factory reset, so photo files, etc. are still 100% safe. I understand correctly? What do you think?
Post scriptum... and this fuc#@ng root is just so that you can record conversations in android pie because Google blocked this function
Click to expand...
Click to collapse
You are epic but, YES!
P.S. I would love someone to convincingly defend unlocking bootloader but preventing the breach of encryption.
That would be nice.
nabbed said:
You are epic but, YES!
P.S. I would love someone to convincingly defend unlocking bootloader but preventing the breach of encryption.
That would be nice.
Click to expand...
Click to collapse
Any solution? Maybe TWRP for password or something? It should be some kind of solution.