Hmm, i cannot get my Google Play Store runnning after i downloaded it from website, and when i tried to install my Whatssap it said installed eventhough i didn't (maybe from my previous ROM?). Im not entirely understand what S-OFF means but what can i do after S-OFF? If i do backup now in recovery, can i get the previous files, images etc?
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root [International] My HTC One M7 becomes tampered and locked. Please help
- Thread starter Alvanista
- Start date
-
- Tags
- htc one m7
Did you flashed the Gapps as well ?
Take them one at a time, big boy. Remember: They didn`t built Rome in a day.
here are the Gapps ( to be flashed in TWRP ): http://slimroms.net/index.php/downloads/dlsearch/viewcategory/1150-addons4-4
Chose from what variety you want. Be careful, as far as I can remember, some Gapps were giving errors.
You can also try Paranoid Android Gapps.
None tendered.
Post was restored with due process.
Along with @frosthax1 who suggested it first.
As @scotty85 verifies, the phone is still sick but operational. Lucky. And nothing wrong with luck.
If the OP is happy that's all that matters.
He`s still missing the Gapps.None tendered.
Post was restored with due process.
Along with @frosthax1 who suggested it first.
As @scotty85 verifies, the phone is still sick but operational. Lucky. And nothing wrong with luck.
If the OP is happy that's all that matters.
Ain`t nothing lucky about that process. I`ve applied around 100 times on softbricked phones. Successfully.
Yes, the phone is still sickly, but it can be cured now. He can get S-Off ( either with RumRunner or with Sunshine ) and go from there. Like I told the OP, they didn`t built Rome in a day
Good to see it going.
Alvanista: S-Off removes security checks from the phone. Although put like that it sounds a bad thing, it lets you do things you couldn't otherwise, including running a different RUU from those intended for your phone's region.
As for backups, what was suggested was going back into TWRP and taking a backup from there. That will back up your current ROM as well as whatever apps and data you've installed. Then copy that backup to a computer for safekeeping. The idea is that now you've got it working you may as well back up its current state!
You could even do this before flashing gapps - then if you have a problem there (e.g. flash the wrong version), restore the backup and try again.
Alvanista: S-Off removes security checks from the phone. Although put like that it sounds a bad thing, it lets you do things you couldn't otherwise, including running a different RUU from those intended for your phone's region.
As for backups, what was suggested was going back into TWRP and taking a backup from there. That will back up your current ROM as well as whatever apps and data you've installed. Then copy that backup to a computer for safekeeping. The idea is that now you've got it working you may as well back up its current state!
You could even do this before flashing gapps - then if you have a problem there (e.g. flash the wrong version), restore the backup and try again.
What it is:
Your storage is divided into a number of sections - and those sections are mapped into various functions - radio firmware, the boot area where the kernel lives, the system area where Android (and optionally Sense) lives, the data area for your info and apps and so forth, including your media storage area.
There are number of cross-references in the system to maintain the integrity of that information.
What you have:
Yours are broken. That's why normal roms won't install and neither can your backups.
Where are you now:
I disassembled the Slim rom to see what it's doing for you and why it worked - everything is causal.
As expected, it has an excellent installer and an s-on-safe boot image install method.
How it differs from full roms like Viper 7.02 is that its system image, along with all installer actions, is less than 290 MB. The compressed zip download was 154 MB.
The raw Viper rom is 1.3 GB, and it's cooking away for me in the background so I don't have the exact system stats yet - but - it's going to be well over 1 GB. (EDIT - the Viper rom zip isn't compressed, the system image is just under 1.2 GB. So - it's 4 times the size of the Slim rom (and therefore the Slim rom's name becomes apparent).)
Your good fortune hit because the *much smaller* system in the Slim rom could be contained within the target area - without hitting the boundaries where the corruption is.
The system area as designed by HTC is oversized and that *could have been* sufficient for Viper to install but it wasn't - the difference between the normal spare and the reported/as-corrupted sizes didn't match up and leave the space that Viper required.
What's the fix:
An RUU is an HTC method that's basically a nuclear option from the user point of view.
It's basically a factory tool that overwrites *everything* - including all of the definitions of what blocks of storage are how big and used for what purpose.
We can't get access to every possible RUU, HTC doesn't prevent RUU leaks but they don't help either.
An RUU, just like a rom, normally has to match your version exactly.
Getting s-off allows you to play a parlor trick so that another RUU, not originally marked for your exact region or carrier but still perfectly ok for you, can be accepted by the phone.
And fortunately, even though you can't do everything intended by the Slim rom developers because of your corruption, you can now get s-off with it according to @r3w1NNNd.
Why that's the fix:
The HTC hboot bootloader has an encrypted signature security protection to ensure that only HTC-signed modules can be written in some reserved areas, even when the bootloader is unlocked. That state is called s-on.
S-off removes that and is normally permanent. Supposedly it can be reversed but in practical fact nearly everyone that attempts it (and there is never a good reason to attempt it) converts their phone into a paperweight in one big jiffy.
Hope that's not too much information, it's simply the complete answer to your question. Any readability issues, I apologize for sincerely.
Last edited:
Thanks for the info. I installed Android_Revolution_HD-One_6.1_GE which is version 4.4.2 and could not get it to work. Stuck on the animated Google logo, apparently only SlimROM works for me now.
May i know how to solve this : why i cannot hear the caller's voice and they cannot hear my voice?
May i know how to solve this : why i cannot hear the caller's voice and they cannot hear my voice?
Last edited:
Your phone was broken when you came - it is still broken. Only not 100% broken.
Sadly, fixing it is not done just by flashing the rom.
Thanks to @r3w1NNNd you have a rom working a little, not 100%, so you can take the next step.
His experience that now you can take the next step - getting s-off.
He suggest two ways - first trying rumrunner - http://rumrunner.us/
But I do not think it will work because your bo0tloader is 1.57 because it was tried here - http://forum.xda-developers.com/showthread.php?p=59001690&highlight=1+57#post59001690
So the other way to try is Sunshine - http://theroot.ninja/
In my experience, Sunshine requires the stock HTC rom - but @r3w1NNNd says that the Slim rom can work.
You will have to try both to see if one works.
If it does, then we can try the next step.
If not, maybe @r3w1NNNd has some ideas on how to make your phone work.
In the meantime, please confirm your APN settings for your carrier.
scotty85
Extreme Android User
Well said. I really hate it when people turn s on when they want to be stock,or want to sell the device. Being s on offers no advantages whatsoever.
Back in the old days phones were much simplier,only having half a dozen or so partitions,so things were a lot easier to stabilize. In many cases going back to s on was as simple as replacing an eng or patched hboot with a stock one.
The security flag is now not within hboot,the devices have 3-4 times as many partitions to Wich very subtle changes are made and checked. It's almost impossible to know what changes are made,and even more so to predict what ones will be important.
Once you've altered the phones security,the safest option is to leave it that way.you'll just need to use more caution in what you do to the device. That may sound a bit scary,but all it means is that you should know and understand the mods that you intend to install,and be very diligent about checking the integrity of any files you use by verifying their md5 sums.
S off will not prevent you from owning a stock device and having a stock experience,if that is what you desire
The next step to fixing the phone is to flash an AOSP Rom that will let you attempt to achieve s off with rum runner
The hboot is at 1.57 - per my references, isn't rumrunner out of reach?
scotty85
Extreme Android User
In very well may be. Been awhile since m7 was my daily driver, and even longer since I did s off. My experience with rum runner on other devices is that the exploit is not necessarily hboot dependent, but rather on other firmware surrounding it, so hboot version whatever may work on some variants, but not others. Sorry that's not a real definitive answer, lol.
shauny13
Android Expert
No, i don't think so. You could try firewater. It's no longer supported, but you never know.
http://forum.xda-developers.com/showthread.php?t=2632351
anoniemouse
Android Expert
I tried both on mine but they both failed.
In the end used sunshine & i must say it is so easy to use, as a consequence i would recommend it.
In the end used sunshine & i must say it is so easy to use, as a consequence i would recommend it.
shauny13
Android Expert
Like it says, sunshine needs to be as close to stock as possible to work, A sense based rom will usually work {I used maximus}. But you still have your original problem of not getting another sense based rom to work, you are probably stuck. Sorry. The boot.img is the kernel. You could try a different kernel, but i doubt it will work as you haven't got a sense rom only aosp.
Last edited: