Related
I ask forgiveness if this has been answered before, but the search function is currently down.
I'm receiving my GSM GN tomorrow, and I'd like to ask a couple of questions, in case anyone has done this with their phone:
I work in a corporate environment that wants encryption on their mobile devices due to the nature of our work (insurance). My ICS tablet, an ASUS TF101, has the ability to do full device encryption, and I'm assuming that the GN can as well. However, I'd like to root my phone as well. This means that I will need to remain stock (which I have no issues with) and also need to keep the stock recovery. I'm not overly interested in running custom ROMs.
Is it possible to root the phone without replacing the stock recovery via an exploit?
Is it more practical, or realistic, to instead:
Unlock bootloader
Install CWM or equivalent recovery
Root device via recovery
Reflash stock recovery
Encrypt device
With my tablet, I rooted it before I encrypted it. Since it did not have an unlocked bootloader or recovery, I had to use one of the exploits that was around at the time.
Anyone have any advice they might share?
With an unlocked bootloader, you can boot whatever kernel you want without flashing it. So, just boot cwm, flash the root files, and done. You have root + stock recovery. Then you can turn on encryption.
Sent from my Galaxy Nexus using Tapatalk 2
Ah, unlocking the bootloader allows you to flash anything you want via the stock recovery? That's quite useful, and I appreciate the response
randalla0622 said:
Ah, unlocking the bootloader allows you to flash anything you want via the stock recovery? That's quite useful, and I appreciate the response
Click to expand...
Click to collapse
No, you can flash whatever you want in recovery regardless if your bootloader is locked or not.
What an unlocked bootloader allows you to do is flash whole images to partitions and to boot any kernel you want, using fastboot. So, you can boot up cwm without flashing it: fastboot boot cwm.img
Sent from my Galaxy Nexus using Tapatalk 2
2 days back i bought new samsung galaxy nexus
PS ( im totally new to android world i really no idea about android at all )
i got ota update and im on 4.0.4
few issues which im really facing badly
1. my play store is all the time giving me connection time out error and even i tried to install apps from pc but i dont get
2. my wifi signals are all the time to the lowest.... but now it has become more problem to me as my wifi and mobile signals are completely off.. and they come back after few seconds please help me what to do ?
and yeah im really new user so sorry if i ask a reply with depth so i can understand
mukeshphanse said:
2 days back i bought new samsung galaxy nexus
PS ( im totally new to android world i really no idea about android at all )
i got ota update and im on 4.0.4
few issues which im really facing badly
1. my play store is all the time giving me connection time out error and even i tried to install apps from pc but i dont get
2. my wifi signals are all the time to the lowest.... but now it has become more problem to me as my wifi and mobile signals are completely off.. and they come back after few seconds please help me what to do ?
and yeah im really new user so sorry if i ask a reply with depth so i can understand
Click to expand...
Click to collapse
I'd post in your own thread, and not one about unlocking and encryption.
It's been coming up more often lately, and there's something that needs to be mentioned for people who don't understand what they are doing while messing with the bootloaders.
DO NOT LOCK THE BOOTLOADER ON A CUSTOM ROM!
The process of unlocking the bootloader replaces the A100 bootloader with an A200 bootloader which responds to fastboot oem unlock, running this is fine even fully stock.
If you unlock the bootloader to install and run custom recovery (CWM, TWRP) which is then used to install a custom ROM (CM9,CM10, Flex Reaper, anything NOT Acer official). If you go and lock the bootloader again by replacing the A100 bootloader you WILL BE LOCKED OUT OF BOTH. It will prevent the use of anything other then official Acer recovery or ROM.
There is no fix for this, it needs to be sent to Acer for repair.
It can happen in a couple ways.
1. Running the lock script included with the unlock script, he mentions it will lock it, but fails to mention what will happen if it's used on custom ROM and recovery device.
2. Running the official OTA from custom recovery, it will fail to install the system, but replaces the bootloader, which locks you out of both recovery and system.
If you happen to have done 2, and catch it BEFORE rebooting or leaving recovery, you can use the unlock script to unlock the bootloader again. Once you leave recovery, you're stuck and can't get back in.
PLEASE PAY ATTENTION TO WHAT YOU ARE DOING AND LEARN WHAT THE TOOLS ARE DOING AND HOW TO USE THEM CORRECTLY!
pio_masaki said:
It's been coming up more often lately, and there's something that needs to be mentioned for people who don't understand what they are doing while messing with the bootloaders.
DO NOT LOCK THE BOOTLOADER ON A CUSTOM ROM!
The process of unlocking the bootloader replaces the A100 bootloader with an A200 bootloader which responds to fastboot oem unlock, running this is fine even fully stock.
If you unlock the bootloader to install and run custom recovery (CWM, TWRP) which is then used to install a custom ROM (CM9,CM10, Flex Reaper, anything NOT Acer official). If you go and lock the bootloader again by replacing the A100 bootloader you WILL BE LOCKED OUT OF BOTH. It will prevent the use of anything other then official Acer recovery or ROM.
There is no fix for this, it needs to be sent to Acer for repair.
It can happen in a couple ways.
1. Running the lock script included with the unlock script, he mentions it will lock it, but fails to mention what will happen if it's used on custom ROM and recovery device.
2. Running the official OTA from custom recovery, it will fail to install the system, but replaces the bootloader, which locks you out of both recovery and system.
If you happen to have done 2, and catch it BEFORE rebooting or leaving recovery, you can use the unlock script to unlock the bootloader again. Once you leave recovery, you're stuck and can't get back in.
PLEASE PAY ATTENTION TO WHAT YOU ARE DOING AND LEARN WHAT THE TOOLS ARE DOING AND HOW TO USE THEM CORRECTLY!
Click to expand...
Click to collapse
Thanks for this Post. If I follow and use your A100 Flashing Toolkit v1.1 7-16-12 will this take a Stock A100 and Root it, Unlock the Boot Loader and Install ClockworkMod Recovery,and will the Boot Loader Remain being Unlocked ?
Izzyb914 said:
Thanks for this Post. If I follow and use your A100 Flashing Toolkit v1.1 7-16-12 will this take a Stock A100 and Root it, Unlock the Boot Loader and Install ClockworkMod Recovery,and will the Boot Loader Remain being Unlocked ?
Click to expand...
Click to collapse
Yeah it stays unlocked, generally there is only the 2 ways I mentioned before, so unless you try to do it manually it shouldn't ever occur unless you try to revert to stock or flash a stock rom and having it fail.
Basically, once its unlocked don't mess with it until you need it back to stock.
Tapatalked from my Galaxy S II.
pio_masaki said:
Yeah it stays unlocked, generally there is only the 2 ways I mentioned before, so unless you try to do it manually it shouldn't ever occur unless you try to revert to stock or flash a stock rom and having it fail.
Basically, once its unlocked don't mess with it until you need it back to stock.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
Thanks Again !
Honestly, I'd bet 90%+ of all the bricks created are by people unlocking/locking the bootloader when they don't have any business doing anything. The A100 also seems to be VERY unforgiving in terms of doing ANYTHING in the wrong order when flashing.
b1lk1 said:
Honestly, I'd bet 90%+ of all the bricks created are by people unlocking/locking the bootloader when they don't have any business doing anything. The A100 also seems to be VERY unforgiving in terms of doing ANYTHING in the wrong order when flashing.
Click to expand...
Click to collapse
I'd say 90% is due to emmc failure. I mean a100 wise, nit devices in general. There has been only a few reports of this scenerio happening, and its partly our fault as it is not documented anywhere in the instructions on using the unlocking script nor in my guide or anywhere else. Can't release a tool capable of bricking a device and not cover it in the instructions, however this is exactly what happened, and still hasn't been corrected, this is why I made this post.
Acer did make this very had to get back from making a mistake on, though, for sure. I really wish people would read and learn before doing this stuff, but for now all I can do is put it out there and hope its read before its to late.
Side note, not new to this stuff but flashing a boot loader still makes my brown eye pucker. Scares me beyond anything else lol.
Tapatalked from my Kindle Fire - Jellytime AOSP
pio_masaki said:
I'd say 90% is due to emmc failure. I mean a100 wise, nit devices in general. There has been only a few reports of this scenerio happening, and its partly our fault as it is not documented anywhere in the instructions on using the unlocking script nor in my guide or anywhere else. Can't release a tool capable of bricking a device and not cover it in the instructions, however this is exactly what happened, and still hasn't been corrected, this is why I made this post.
Acer did make this very had to get back from making a mistake on, though, for sure. I really wish people would read and learn before doing this stuff, but for now all I can do is put it out there and hope its read before its to late.
Side note, not new to this stuff but flashing a boot loader still makes my brown eye pucker. Scares me beyond anything else lol.
Tapatalked from my Kindle Fire - Jellytime AOSP
Click to expand...
Click to collapse
lol you haven't owned an HTC device
-DarkKnight- said:
lol you haven't owned an HTC device
Click to expand...
Click to collapse
My first android device was an HTC, not sure of your point?
Tapatalked from my Galaxy S II.
my friend has an HTC device and he is always talking about how annoying the boot loader is
Sent from the My Little Pony Official App
pio_masaki said:
Yeah it stays unlocked, generally there is only the 2 ways I mentioned before, so unless you try to do it manually it shouldn't ever occur unless you try to revert to stock or flash a stock rom and having it fail.
Basically, once its unlocked don't mess with it until you need it back to stock.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
Thanks Again:
Ok Im rooted, Boot Loader is Unlocked, Installed TWRP with the Acer Recovery Installer, made a Back Up of the Stock ICS in TWRP. On now to the CM10 Preview which I think is Great. If I restore the Stock ICS Backup I made in TWRP will that in anyway Effect the Boot Loader and Lock It Up and Brick this ?
Izzyb914 said:
Thanks Again:
Ok Im rooted, Boot Loader is Unlocked, Installed TWRP with the Acer Recovery Installer, made a Back Up of the Stock ICS in TWRP. On now to the CM10 Preview which I think is Great. If I restore the Stock ICS Backup I made in TWRP will that in anyway Effect the Boot Loader and Lock It Up and Brick this ?
Click to expand...
Click to collapse
No the backup doesn't include the boot loader so nothing to worry about there. You can also choose what you want restored or backed up.
Tapatalked from my Galaxy S II.
pio_masaki said:
No the backup doesn't include the boot loader so nothing to worry about there. You can also choose what you want restored or backed up.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
Thanks once again for such a Quick Response.
This is What I worry about being a NewBuB with the A100. From Past Experience with TWRP it does Back Up Boot but with the Craziness of this A100's Boot Loader is what has Me Scared. Just Taken Precautions if you know what I Mean.
Izzyb914 said:
Thanks once again for such a Quick Response.
This is What I worry about being a NewBuB with the A100. From Past Experience with TWRP it does Back Up Boot but with the Craziness of this A100's Boot Loader is what has Me Scared. Just Taken Precautions if you know what I Mean.
Click to expand...
Click to collapse
Boot and bootloader are different, boot is the kernel and ram disk which doesn't affect the boot loader. The boot loader calls on boot to start android. Backing up and restoring boot is recommended with the rest of the backup and restore.
Tapatalked from my Galaxy S II.
Back to Stock
It is a strange thing, but ZeroNull, the autor of the unlocked bootloader, suggested me to lock bootloader by flashing the stock ics. And everything was fine. I think, you should add to your first post that flashing honeycomb while somebody on custom rom will brick a tablet, but flshing the stock ics on a custom rom is ok. It is proved by me and some other persons from the other forum.
ilyuha1108 said:
It is a strange thing, but ZeroNull, the autor of the unlocked bootloader, suggested me to lock bootloader by flashing the stock ics. And everything was fine. I think, you should add to your first post that flashing honeycomb while somebody on custom rom will brick a tablet, but flshing the stock ics on a custom rom is ok. It is proved by me and some other persons from the other forum.
Click to expand...
Click to collapse
Not quite understanding what you are saying, flashing a stock ics on a custom rom is fine because it puts a stock rom with stock boot loader, this doesn't add anything different from what I posted.
If you mean stock ics boot loader on custom rom it will lock it out, period.
Maybe I'm just not understanding what you meant.
Tapatalked from my Galaxy S II.
pio_masaki said:
Not quite understanding what you are saying, flashing a stock ics on a custom rom is fine because it puts a stock rom with stock boot loader, this doesn't add anything different from what I posted.
If you mean stock ics boot loader on custom rom it will lock it out, period.
Maybe I'm just not understanding what you meant.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
I mean that if somebody want to lock his bootloader he should flash the official ics in recovery and everything will be fine.But locking the bootloader by script or flashing official honeycomb wiil lead to unrecoverable tablet. Now is it clear?
I just practice my english skills
ilyuha1108 said:
I mean that if somebody want to lock his bootloader he should flash the official ics in recovery and everything will be fine.But locking the bootloader by script or flashing official honeycomb wiil lead to unrecoverable tablet. Now is it clear?
I just practice my english skills
Click to expand...
Click to collapse
From the way I understand it that would be playing with fire, I take it that one should never restore an OTA update.zip from custom recovery while running unlocked bootloader, and one should never try to lock the boot loader from custom recovery via script.. Restoring a stock ROM from recovery via nandroid backup is different than trying to flash the .zip from recovery. I'm not really sure why anyone would even want to attempt flashing an OTA update.zip from custom recovery, as the first rule of thumb when modding your device is to create a nandroid backup of your original unmodded install, so why not just restore that? Why would you want to intentionally lock the bootloader unless you have bricked the device already and wanting to send off for repair???
ilyuha1108 said:
I mean that if somebody want to lock his bootloader he should flash the official ics in recovery and everything will be fine.But locking the bootloader by script or flashing official honeycomb wiil lead to unrecoverable tablet. Now is it clear?
I just practice my english skills
Click to expand...
Click to collapse
OK I think I get what you mean now. As Linux society mentioned above, flashing stock from cwm or twrp usually fails (as mentioned in the OP) to install system, but does install the boot loader which locks you out. Its happened before.
This post wasnt about how to lock it or whatever, it was a warning about locking it on a custom ROM and recovery and the usual mistakes made that lead to it. Locking it safely is another topic for another thread.
Tapatalked from my A100 - Jellytime X B6
And this is why I said earlier that most people flashing these devices are the real problem. This is an easy device to brick compared to many. I've improperly flashed my Optimus One so many times and oft bricked it yet it is easy to recover. I have little sympathy for people that flash before reading. You have the patience of a saint pio.
b1lk1 said:
And this is why I said earlier that most people flashing these devices are the real problem. This is an easy device to brick compared to many. I've improperly flashed my Optimus One so many times and oft bricked it yet it is easy to recover. I have little sympathy for people that flash before reading. You have the patience of a saint pio.
Click to expand...
Click to collapse
aint that the truth, and then the irony of the whole thing, the one that makes the guides and provides tons of courtesy to the community ends up getting a random emmc failure that bricks his. I'd be sick keeping on with people who won't listen if it was me. all i know is everyone here should just READ pio's guides and his threads/posts from the past 2 weeks, it will serve them well and at least make them think twice before they do something off the wall, well maybe ... there is always those people who are like "I want to see what it does, that sounds cool, I want a brick" or at least it seems there are a few like that..
Soooooo,
for years I have spent hours and hours every time I got a new android, reading up on the tips and tricks, root methods etc. and in those years I have managed to brick the **** out of a few ( all ) of those devices. but through xda I was always able to get them back.
well, today isn't one of those days. I got a new M8 last week. and in the span of a few hours I have managed to render it dead I think.
I initially installed the temp root, I don't have my notes with me....
then I installed SU
then I installed twrp
everything was going fine, until somehow I deleted my OS without having a back up recovery.
thennnn, somehow I managed to relock the device.
adb will not find the device, fast root isn't allowed to write to any partitions.
im completely and utterly hosed. right now I don't even have twrp installed, it just boots into fastboot over and over.
ive managed to get s-on back on it and well.....its not been a good day.
id really love to see what you guys think. at this point id try anything, but I feel like with me not able to install a rom because its locked, and not able to unlock it because I don't have an OS, I dunno what to do.
You don't need an OS to run fastboot to unlock it.
Just start at the beginning and make sure you get the recovery for Verizon model.
im not sure where to even start now. the verizon M8 apparently has to have weaksauce and SU to get root. my phone was botoable and i used those on the front end.
id really appreciate any help you guys could offer. right now if i tried to install a recovery it would fail due to the lock . im at a loss
BenPope said:
You don't need an OS to run fastboot to unlock it.
Just start at the beginning and make sure you get the recovery for Verizon model.
Click to expand...
Click to collapse
HTCdev Unlock.
fastboot flash recovery recovery.img
fastboot erase cache
adb push rom.zip /sdcard
Use recovery to flash ROM
Don't panic as long as you can use fastboot, there is always a way to get things back. As said first and foremost you need to unlock the boot loader. You will need the original unlock.bin file then just use the instructions on htcdev to apply the unlock.
Get a custom recovery on there or boot into one.
From there you could try and restore the system partition from a stock nandroid in the stock backup thread.
thanks for the help. I knew I could count on you guys.
heres the main issue with your suggestions. both depend on the htcdev unlock. I tried that first thing when I decided to root. Verizon does not allow their m8 to be unlocked using that method. it always fails. so I will need another way to unlock ;( if I can get past that I feel pretty sure I can get it back together.
ashyx said:
Don't panic as long as you can use fastboot, there is always a way to get things back. As said first and foremost you need to unlock the boot loader. You will need the original unlock.bin file then just use the instructions on htcdev to apply the unlock.
Get a custom recovery on there or boot into one.
From there you could try and restore the system partition from a stock nandroid in the stock backup thread.
Click to expand...
Click to collapse
Hey guys,
I'm kinda new to the HTC/Android world, found this community a damn good place to find support.. But now I've hit a road block.
Basically, I've been eager to root from day 1 of getting my first htc handset, I came across from jailbreak and loved the fact of customizability with Android.
So I had the Google play edition(I think, all geared towards Google) running Kit Kat 4.4.4. Love it, big Google user so this all tied together lovely.
Here is the Situation.
I found a video on youtube, cannot provide URL as I'm in work at the moment, but it was root guide from scratch. Fresh windows OS, seemingly a phone fresh out the box.. you get the idea.
I used the Hasoon2000 tool to root the device. Installed ADB etc on my pc, signed up as a a dev, got the Key for device, sent in and received my .bin file. I got up to actually rooting my device, well pleased and happy. Using TWRP via Hasoon2000.
But here is where **** hits the fan.
The device needed to update, It took me back to 4.4.2 but Im unsure on how to get back to most up to date OS and keep the root.
But when I reboot to install this, it goes into TWRP. no other way around this.
Queried this on another forum, decided to continue to be patient... but no replies, in the mean time I restored my apps and have a fiddle, see what the root function can do for myself.
I installed "Freedom 1.0.6" and a program called "Market Share"- Hate iAP, some games are ridiculously priced for the smallest of things, I just wanted to sandbox plague inc. ;(
Now the device is stuck in a boot loop, phone starts up, see the home screen for a bout 40 seconds/ one minute.. Some times I unlock the device and it goes back to flash screen then.. others I boot an app and its slides away once more.
This happened close to 15x before I left for work this morning and I imagine its just going to repeat this and run the battery - I tried to stop this loop by going into TWRP and possibly choosing to boot system this way may of stopped it.. but when I was on the boot screen with those options.. It said Tampered at top of screen and S-On- which has scared me quite a bit..
What the hell has happened!?
I'm desperate to know and don't want to have this damn thing bricked! Please help.. try explain like I'm 5, as said I'm new to a lot of this! >.<
first off, if the screen comes on, its not bricked.
esenfur said:
But here is where **** hits the fan.
The device needed to update, It took me back to 4.4.2 but Im unsure on how to get back to most up to date OS and keep the root.
But when I reboot to install this, it goes into TWRP. no other way around this.
Click to expand...
Click to collapse
Do you mean you accepted an official OTA? I think that is what you are saying. You should not be accepting OTAs on a phone that has been bootloader unlocked, custom recovery, etc. unless you know exactly what you are doing and what the result will be (which is clearly not the case).
Stock recovery is needed to install an OTA. That is why it keeps going to TWRP, then it doesn't find stock recovery and reboots, hence the loop you are stuck in. Try to find the OTA file and delete it.
redpoint73 said:
first off, if the screen comes on, its not bricked.
Do you mean you accepted an official OTA? I think that is what you are saying. You should not be accepting OTAs on a phone that has been bootloader unlocked, custom recovery, etc. unless you know exactly what you are doing and what the result will be (which is clearly not the case).
Stock recovery is needed to install an OTA. That is why it keeps going to TWRP, then it doesn't find stock recovery and reboots, hence the loop you are stuck in. Try to find the OTA file and delete it.
Click to expand...
Click to collapse
Thank you for fast response.
Official OTA - being that the phone its self said "Update the OS" - I just accepted this, hit download and began install as a reboot- didnt spot implications. As said, noob, followed a tut. If it highlighted DO NOT UPDATE or.. IF U WANT UPDATE NOW FOLLOW THIS- Great, but nothing of the sort?
Is the OTA file basically the .exe for the OS- so find it and delete it.. although I dont have enough time to navigate and establish where the file actually is located!
Or do you have any links to tutorials I could possibly follow?
Side note- when this loop started I deleted
esenfur said:
Or do you have any links to tutorials I could possibly follow?
Click to expand...
Click to collapse
This is really your main issue. By following a YouTube video and using a Toolkit, you've failed to actually learn anything or gain any real understanding or knowledge. Do yourself a favor and ditch the tutorials and videos (and toolkit for that matter) and do it the old fashioned way . . . by reading. Videos and step-by-step guides do you no good when things go south (as you've now discovered). And with the prior proper knowledge (usually not gained by following tutorials) this whole mess probably would have never happened in the first place.
A cardinal rule of Android phone modding: DO NOT accept/download/install OTAs (official OS updates) on a modded device unless you know what you are doing, and what the result will be. If in any doubt, simply DO NOT do it.
esenfur said:
Is the OTA file basically the .exe for the OS- so find it and delete it.. although I dont have enough time to navigate and establish where the file actually is located!
Click to expand...
Click to collapse
.exe file is Windows specific. You are looking for a zip file, and it typically starts with "OTA". Don't remember where its saved to, so you will have to search for it. If you can't keep the phone running long enough to do so, mount the memory on your computer and search that way.
Deleting the OTA file worked for me on a past device, although one M8 user in the same position said deleting the file didn't get him out of the loop. Flashing your ROM again, or wiping the internal memory (backup any important personal data first) might be options for you.
redpoint73 said:
you've failed to actually learn anything or gain any real understanding or knowledge.
Click to expand...
Click to collapse
Ive seen quite a fair few ratings for Hasoon2000 and decided to go with it..
redpoint73 said:
Videos and step-by-step guides do you no good when things go south (as you've now discovered).
Click to expand...
Click to collapse
agreed.. theres FAR much more I need to learn.. its scary haha.
redpoint73 said:
DO NOT accept/download/install OTAs (official OS updates)
Click to expand...
Click to collapse
taken on board. I know with my jailbreaks in past it has been a pain, assumed Android would be alot more stable to over write- due to functionality of OS and unlocked features.
I was being generic when I said .exe- basically the installer..
I returned from work to see phone stopped looping.. i could stop the install and deleted the file ASAP.. but now what.. Phone is still bugging me to update, lost the root(got a checker).. so whats the correct procedure!?
I am confused to what you are trying to accomplish at this point, is it to install a OTA, or a recovery? What exactly is going down here?
Me personally to take an OTA is to relock bootloader, install stock recovery, and make sure CID matches. I am S-Off so bootloader means very little, but you can unlock and relock at will when you are S-Off. You will not lose S-Off accepting an OTA.
Try to re-flash the ROM, with stok ROM, using TWRP and clean install. It should work.
hack14u said:
I am confused to what you are trying to accomplish at this point, is it to install a OTA, or a recovery? What exactly is going down here?
Me personally to take an OTA is to relock bootloader, install stock recovery, and make sure CID matches. I am S-Off so bootloader means very little, but you can unlock and relock at will when you are S-Off. You will not lose S-Off accepting an OTA.
Click to expand...
Click to collapse
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8
esenfur said:
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8
Click to expand...
Click to collapse
First of all once the bootloader is unlocked you don't have to relock it to get OTA.
As I undersand you have done the following:
1) Unlock using HTCDev-Method
2) flashed a custom revocery (TWRP in your case)
3) flashed a supersu too!?
To install the OTA means loosing root acces. Thus you have to re-root it after the OTA is done. The other problem ist that STOCK OTAs don't work with a custom recovery. Meaning you would have to flash a stock recovery first, install the OTA second (as long as you didn't change anything an just root), and re-root third.
Let's have a look which stock recovery you would need:
1) reboot to bootloader
2) connect the phone to you PC and open cmd in you adb/fastboot folder
3) enter "fastboot getvar all"
4) paste this information here (but DELETE the IMEI and SERIAL NUMBER before posting!!)
As soon as we know which stock recovery you need we will go on.
esenfur said:
Ive seen quite a fair few ratings for Hasoon2000 and decided to go with it..
Click to expand...
Click to collapse
I'm not saying there is anything "wrong" with the toolkit, per se. For the most part, it does what its intended to do.
But it also shortcuts the learning process, and facilitates folks rooting the phone without gaining the proper knowledge. This is a dangerous thing.
This is just my opinion. But I strongly believe it. If you can't accomplish these things without a toolkit, you shouldn't be rooting your phone in the first place.
Others use the toolkits, and love them. They are more than entitled to have their own opinion. But when things go south, the toolkits aren't going to help; and those folks don't have the proper knowledge and they come running here. So you tell me what is the "best" way to root the phone?
esenfur said:
I was being generic when I said .exe- basically the installer..
Click to expand...
Click to collapse
I already figured this was probably the case. But I found it better to provide the exact information on what file to delete; rather than leaving it open to the possibility of you and/or others being misinformed.
esenfur said:
Phone is still bugging me to update, lost the root(got a checker).. so whats the correct procedure!?
Click to expand...
Click to collapse
Sounds like you still have TWRP installed, so just flash SU or SuperSU to gain root.
After that, you can use Titanium Backup or similar app to find the update process and freeze it, to stop the update notifications.
Don't remember the exact process (this is where searching and reading comes in for you) but its something like "drm..." or "updater".
I have this situation before,what i do is find the right stock recovery and flash..after ota done flash back custom recovery..?
esenfur said:
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8
Click to expand...
Click to collapse
At this point after seeing this, I would suggest you take some time and start reading. All of your answers are here in the forums. Knowledge is power and within the pages of this site you will find everything you need.
To take the OTA find a stock recovery, to flash ROM's find the one you like and flash via your favorite recovery.
HTC one m9 on Sprint network
First, I am a noob at all this.
I got all my info and instructions from sakitech on YouTube. I was trying to unlock the bootloader and root my phone.
My Process:
-I unlocked the bootloader with minimal problems
-I installed twrp (team win recovery program)
-Then I was told to install
UPDATE-SuperSU-v2.46.zip
I guess this is a OS but not sure
-I unzipped and installed this in twrp
-Side note: In the twrp it kept telling me no OS had been installed
-I rebooted my phone and checked for root access. It was not enabled.
-I couldn't figure out why and got frustrated and decided to factory reset everything and start over
-When I rebooted my phone, several basic functions could not be used.
-I had to go back into the twrp (which I was surprised didn't get wiped) and do a advanced wipe to restore normal function.
-I haven't tried rooting after that and I relocked the bootloader
Questions:
-Did I simply not install something? If so, what?
-How can I get rid of twrp if I decide to give up on this? And how can I get the bootloader to say "locked" instead of "relocked"?
So if you have any suggestions, questions, or see anything wrong please help me out. Thanks!
NotSatan said:
HTC one m9 on Sprint network
First, I am a noob at all this.
I got all my info and instructions from sakitech on YouTube. I was trying to unlock the bootloader and root my phone.
My Process:
-I unlocked the bootloader with minimal problems
-I installed twrp (team win recovery program)
-Then I was told to install
UPDATE-SuperSU-v2.46.zip
I guess this is a OS but not sure
-I unzipped and installed this in twrp
-Side note: In the twrp it kept telling me no OS had been installed
-I rebooted my phone and checked for root access. It was not enabled.
-I couldn't figure out why and got frustrated and decided to factory reset everything and start over
-When I rebooted my phone, several basic functions could not be used.
-I had to go back into the twrp (which I was surprised didn't get wiped) and do a advanced wipe to restore normal function.
-I haven't tried rooting after that and I relocked the bootloader
Questions:
-Did I simply not install something? If so, what?
-How can I get rid of twrp if I decide to give up on this? And how can I get the bootloader to say "locked" instead of "relocked"?
So if you have any suggestions, questions, or see anything wrong please help me out. Thanks!
Click to expand...
Click to collapse
Your steps are good, beside one thing: repeat everything until you are told to install the SuperSU.zip. Do not extract this file, but flash the zip file via TWRP. This will install the SuperSU app and its related services, which is responsible for super user access. And before you start flashing or modifying your system, please make a backup first via TWRP. So if anything went wrong, you can simply restore your previous backup. This requires some time, yes. But it is way easier to restore a backup than to completely recover from scratch.
To truly lock the bootloader again, you have to flash the KDZ file for your phone (seach for it).
Thanks for the help, I got it figured out!