Related
First time rooting a phone. This is of course very different then my hd2 using the sdcard to load a ROM. I tried to do a lot of reading on this and make sure I really understood what I was getting in to but I have missed something, I'm hoping small.
Here is the thread I am using to root http://forum.xda-developers.com/showthread.php?t=1311194 .
I have android version 2.3.6 towards the end (last 2 pages) of this someone says that 2.3.6 needs to download a different cwm and a different su version. I have downloaded these and am now trying to root.
I got the cwm to work made a backup and then installed the superuser. Every step is confirmed complete with a message that appears to be successful and then I reboot. I now have a superuser icon but when I click on it it opens and is blank. I then try to update the su binary and it tells me its legacy. I tell it to update and it tries to install busy box and then fails on gaining root access.
After writing all of this I realize they said I need su-3.0.7-efgh-signed.zip and I have Superuser-3.0.7-d-signed. Before I go any farther is this my problem. Sorry this is so long I just don't know what step I messed up and thought all the info possible was best.
Not sure if this is what your looking for. But since you have the custom recovery installed, you could always down load and flash a custom rom. They are all rooted.
Sent from my SGH-T989 using xda premium
yep if you want to stay stock, just flash a stock deodexed rom or something. Should be the easiest solution.
I just used the instructions in that thread you referenced to root my brand new T-Mo GS2 this morning and got it to work. I did use su-3.0.5-efgh-signed.zip instead of what you described you used.
I also used the CWM version that one of the posters referred to in the later parts of that thread.
Thanks guys for answering. I was very tired when I posted so I just went to sleep. After taking a fresh start today I found it was the su version. I found it after a couple of mins did it over and was rooted. Lol so close on first try.
My nexus is rooted and unlocked running stock 4.0.2, no custom ROMs. Received the 4.0.4 ota update this morning. Will it install if I let it, or do I need to follow the instructions that others used to do the early install of the update?
Sent from my Galaxy Nexus using XDA
I am just like you. I have the stock 4.0.2 that came with my phone but I've unlocked and rooted it. Received the upgrade notice this morning and said, "yes", but during reboot all I get is the android lying on its back with a red triangle and exclamation point. I have to pull the battery to reboot but then it only comes back in 4.0.2.
Ok, that's what I expected. Sounds like we need to run the manual update. I'm in the process of packing and moving this weekend so I was hoping for an easy fix. Thx for your reply.
Sent from my Galaxy Nexus using XDA
hey there guys i once had the same problem when i was on stockrom with root:
It is simple : Do not do it!
Either U will get what is described above but atleast you will loose your root rights/ unlockes status.
To upate properly use ClockworkMod (App RomManager) and download an already unlocked version of the current update.
I recommend you to switch to a non stock rom hence u will not get these OTA notifications anymore which you may accept "by accident". Good ROms are CM9, Trickster, Paranoid, just haver a look in the dev section.
cryptiq said:
My nexus is rooted and unlocked running stock 4.0.2, no custom ROMs. Received the 4.0.4 ota update this morning. Will it install if I let it, or do I need to follow the instructions that others used to do the early install of the update?
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
If you did not change anything (other than root), you can install it no issue. However, if you have changed your radio, kernel, recovery, or any system file, then the update will not work.
Not however, that you need to install something like OTA Rootkeeper BEFORE you go through the update process, as you will lose root otherwise.
dogunter said:
I am just like you. I have the stock 4.0.2 that came with my phone but I've unlocked and rooted it. Received the upgrade notice this morning and said, "yes", but during reboot all I get is the android lying on its back with a red triangle and exclamation point. I have to pull the battery to reboot but then it only comes back in 4.0.2.
Click to expand...
Click to collapse
That is because you have something that is not stock 4.0.2, be it a kernel, radio, modified system file, recovery, etc.
FellX said:
hey there guys i once had the same problem when i was on stockrom with root:
It is simple : Do not do it!
Either U will get what is described above but atleast you will loose your root rights/ unlockes status.
To upate properly use ClockworkMod (App RomManager) and download an already unlocked version of the current update.
I recommend you to switch to a non stock rom hence u will not get these OTA notifications anymore which you may accept "by accident". Good ROms are CM9, Trickster, Paranoid, just haver a look in the dev section.
Click to expand...
Click to collapse
An update does not affect the "unlocked status" as you say.
See my comments above about root.
You comments about switching to a non-stock ROM don't really make sense for someone who likes stock ROMs and wants to update...
Here you go, a rooted 4.0.4...
http://www.droid-life.com/2012/05/3...6k-build-for-galaxy-nexus-flash-over-any-rom/
efrant said:
That is because you have something that is not stock 4.0.2, be it a kernel, radio, modified system file, recovery, etc.
Click to expand...
Click to collapse
He is right, once upon a time I had flashed a rom and then wanted to go back to stock. I used someones method first (I dont remember whose it was) and I thought I was on stock but I got the android guy on his back and it wasnt working properly (I think the radio was the wrong one) so I then flashed the stock image from Google to 4.0.4 and I was able to get the 4.0.4 OTA no problem and I didnt see the android guy on his back at all during the process.
So more than likely there is something that isnt stock on your phones.
WiredPirate said:
Here you go, a rooted 4.0.4...
http://www.droid-life.com/2012/05/3...6k-build-for-galaxy-nexus-flash-over-any-rom/
Click to expand...
Click to collapse
That is NOT an update. The guy wants to update his build, not flash a brand new one...
same issue
first time poster here. stumbled upon this thread earlier this morning while searching for a solution to what appears to be the same problem that "dogunter" is experiencing. i have a stock 4.0.2 verizon galaxy nexus that i purchased through eBay a few months back. it was listed as brand new but when it arrived it had already been unlocked. from what ive gathered thus far, im assuming that the seller not only unlocked it, but also modified a system file(s), as i am getting the "android on its back with a red triangle" whenever i attempt to update to 4.0.4 via OTA push.
what steps should i take in order to correctly install 4.0.4? i see that "jonnyg1097" claims he "flashed the stock image from Google to 4.0.4 and I was able to get the 4.0.4 OTA no problem and I didnt see the android guy on his back at all during the process. " how would i go about doing this, and is this the best/only method to install the update? thanks in advance!
galaxy_sexus said:
first time poster here. stumbled upon this thread earlier this morning while searching for a solution to what appears to be the same problem that "dogunter" is experiencing. i have a stock 4.0.2 verizon galaxy nexus that i purchased through eBay a few months back. it was listed as brand new but when it arrived it had already been unlocked. from what ive gathered thus far, im assuming that the seller not only unlocked it, but also modified a system file(s), as i am getting the "android on its back with a red triangle" whenever i attempt to update to 4.0.4 via OTA push.
what steps should i take in order to correctly install 4.0.4? i see that "jonnyg1097" claims he "flashed the stock image from Google to 4.0.4 and I was able to get the 4.0.4 OTA no problem and I didnt see the android guy on his back at all during the process. " how would i go about doing this, and is this the best/only method to install the update? thanks in advance!
Click to expand...
Click to collapse
I would follow the instructions here, which takes you through the whole process set-by-step (make sure you do the optional steps in part D). That way you can be certain that you are fully stock. (Leave the bootloader unlocked.) Once you do that, then you can have a look here for how to use the OTA update file to update.
hmm
thanks for that, efrant. im currently in the process of getting it back to stock so i can receive the 4.0.4 OTA update. i am, however, running into a slight issue. in step D, number 2, you say to unlock the bootloader by typing "fastboot oem unlock". upon doing that, the cmd prompt gives me "...FAILED <remote: Already Unlocked>" i suspected it would say that as my phone was already unlocked by the seller. however, im not getting the prompt on my nexus about the device being wiped...do you know why that is and what i need to to in order to continue?
...by the way, a blue line of text appeared at the bottom of the phone's screen that reads "FASTBOOT STATUS - FAILALready Unlocked".
again, thanks in advance for all of the help.
galaxy_sexus said:
thanks for that, efrant. im currently in the process of getting it back to stock so i can receive the 4.0.4 OTA update. i am, however, running into a slight issue. in step D, number 2, you say to unlock the bootloader by typing "fastboot oem unlock". upon doing that, the cmd prompt gives me "...FAILED <remote: Already Unlocked>" i suspected it would say that as my phone was already unlocked by the seller. however, im not getting the prompt on my nexus about the device being wiped...do you know why that is and what i need to to in order to continue?
...by the way, a blue line of text appeared at the bottom of the phone's screen that reads "FASTBOOT STATUS - FAILALready Unlocked".
again, thanks in advance for all of the help.
Click to expand...
Click to collapse
You are good to proceed. You won't get the wipe prompt if your bootloader is already unlocked. No worries, just keep going with the steps.
Sent from my Galaxy Nexus using Tapatalk 2
thanks
thanks for the quick responses! you are quite helpful. everything appeared to install successfully, but upon the first reboot after finishing, im unable to get any service! it reads "Searching for service...", sits there for about 2 minutes, then tells me it cannot find service and thus cant activate. i skipped instead of restarting, and checked the settings to see if anything looked suspicious. im seeing that under "Baseband version" it says "Unknown". did i screw something up?!
sorry to keep troubling you with such noobish problems, but although im an experienced PC user im fairly new to smartphones and android. please have mercy on me.
galaxy_sexus said:
thanks for the quick responses! you are quite helpful. everything appeared to install successfully, but upon the first reboot after finishing, im unable to get any service! it reads "Searching for service...", sits there for about 2 minutes, then tells me it cannot find service and thus cant activate. i skipped instead of restarting, and checked the settings to see if anything looked suspicious. im seeing that under "Baseband version" it says "Unknown". did i screw something up?!
sorry to keep troubling you with such noobish problems, but although im an experienced PC user im fairly new to smartphones and android. please have mercy on me.
Click to expand...
Click to collapse
The first thing i would do is reboot. If that doesn't work, then I would just flash the images one more time. (Just in case one of them messed up.) Make sure both radios flash successfully.
Sent from my Galaxy Nexus using Tapatalk 2
got it
figured it out! when i did the cmda radio install i accidentally typed "fastboot flash radio" instead of "fastboot flash radio-cdma". doh! worked perfectly the second time around. thanks again, man. youve been a fantastic help.
galaxy_sexus said:
figured it out! when i did the cmda radio install i accidentally typed "fastboot flash radio" instead of "fastboot flash radio-cdma". doh! worked perfectly the second time around. thanks again, man. youve been a fantastic help.
Click to expand...
Click to collapse
useful thread
Hey Guys,
I have read a burch of different threads about my problem and nothing has seemed to help or it was too advanced for me to understand. So here it is:
I tried to root my S3 and at first Oden 307 said the root failed, then i was able to try a different file and it said pass. but now when it boots up it gets stuck on the samsung galaxy s3 screen. I can still get into download mode and recovery mode. I have already tried the factory reset in recovery mode. Please help I have only had this phone a month. At this point I dont even care rooted or not I just want my phone back lol
Thanks for any help
+rep
garrett.burn said:
Hey Guys,
I have read a burch of different threads about my problem and nothing has seemed to help or it was too advanced for me to understand. So here it is:
I tried to root my S3 and at first Oden 307 said the root failed, then i was able to try a different file and it said pass. but now when it boots up it gets stuck on the samsung galaxy s3 screen. I can still get into download mode and recovery mode. I have already tried the factory reset in recovery mode. Please help I have only had this phone a month. At this point I dont even care rooted or not I just want my phone back lol
Thanks for any help
+rep
Click to expand...
Click to collapse
First you need to tell us which build you were on, and then what build did you try flashing...
GS4 Stock Rooted MJA 4.3,Philz Touch CWM,HotSpot Mod,Transparent Weather Widget...
BIGSAMDA1st, can I call you "Sam?" Your post count would indicate you've got more experience than I do so I thought I'd ask: aren't all the Sprint S3s on the MK3 build by default? Or are there inconsistencies within the Sprint-branded line of S3s?
Oh man. At least you've still got access to the download console. Can you also access the recovery console? Also, sounds like you're new to rooting (I could be wrong, just going on your comment about certain techniques being too advanced for you to wrap your head around). If you're new, you really picked both one hell of a time and one hell of a phone to cut your teeth on. Samsung's official 4.3 update (which, for all I know, is shipped standard now) comes with the KNOX bootloader which is, in certain situations, basically a bomb designed to ruin your week... and your phone. In particular, it has a REALLY nasty reaction to attempts at downgrading to the old (and much happier) bootloader. It also seems to really hate the older versions of TriangleAway (might hate the new one too, for all I know. I won't touch it anymore). It has other ways to make you hate life as well, but those are two big ones.
How to tell if you have the KNOX bootloader: Did you install the official OTA update to 4.3? If so, you've got the bomb. Did your phone come with 4.3 right out of the box? If so, you've probably got the bomb. Are you still unsure? Look in your Download console for red text that says something like "Warranty Void Bit" or anything that mentions KNOX. If so, you guessed it, you've got the bomb.
If you have the Warranty Void thing listed, then check to see: is it a 0, or is it a 1? If it's a zero, don't do anything else with trying to flash your ROM or root the device until we try some things in your Recovery Console (assuming it's also accessible). Once that flag is tripped, there's no going back... Not a huge deal if it's just a personal device, assuming you're not still under warranty... If you are, well, don't trip that bugger if you can avoid it.
FallenZen said:
BIGSAMDA1st, can I call you "Sam?" Your post count would indicate you've got more experience than I do so I thought I'd ask: aren't all the Sprint S3s on the MK3 build by default? Or are there inconsistencies within the Sprint-branded line of S3s?
Oh man. At least you've still got access to the download console. Can you also access the recovery console? Also, sounds like you're new to rooting (I could be wrong, just going on your comment about certain techniques being too advanced for you to wrap your head around). If you're new, you really picked both one hell of a time and one hell of a phone to cut your teeth on. Samsung's official 4.3 update (which, for all I know, is shipped standard now) comes with the KNOX bootloader which is, in certain situations, basically a bomb designed to ruin your week... and your phone. In particular, it has a REALLY nasty reaction to attempts at downgrading to the old (and much happier) bootloader. It also seems to really hate the older versions of TriangleAway (might hate the new one too, for all I know. I won't touch it anymore). It has other ways to make you hate life as well, but those are two big ones.
How to tell if you have the KNOX bootloader: Did you install the official OTA update to 4.3? If so, you've got the bomb. Did your phone come with 4.3 right out of the box? If so, you've probably got the bomb. Are you still unsure? Look in your Download console for red text that says something like "Warranty Void Bit" or anything that mentions KNOX. If so, you guessed it, you've got the bomb.
If you have the Warranty Void thing listed, then check to see: is it a 0, or is it a 1? If it's a zero, don't do anything else with trying to flash your ROM or root the device until we try some things in your Recovery Console (assuming it's also accessible). Once that flag is tripped, there's no going back... Not a huge deal if it's just a personal device, assuming you're not still under warranty... If you are, well, don't trip that bugger if you can avoid it.
Click to expand...
Click to collapse
First thing is THANK YOU and as i am a noob, where is the +rep button for you? Second and maybe you could help with this, since I posted this I was able to flash back to the official 4.3 :/ so I got my phone back but made my life harder in the process...I got clockwork recovery working and I was able to flash KNOX app remover .zip and I flashed team epic v5..it said everything was installed I rebooted and Im stll not rooted..Supersu says something about not having binary something another and root checker says I dont have root access. According to the step by step I followed I should be rooted :/ Any advise other than nex time dont upgrade to 4.3? lol
-Thanks Bro
BIGSAMDA1ST said:
First you need to tell us which build you were on, and then what build did you try flashing...
GS4 Stock Rooted MJA 4.3,Philz Touch CWM,HotSpot Mod,Transparent Weather Widget...
Click to expand...
Click to collapse
Im not quite sure what you are looking for but it says "Build Number JSS15J.L10VPUCMK3" And its a GS3 4.3 Model SPH-L710
Thanks for the reply
Hey mate,
I'm not familiar with the method of rooting 4.3 that you used. I'm glad to hear you got around the soft brick though! As far as running a rooted 4.3, I can tell you that what I wound up using was CNexus's pre-rooted ROM and the various fixes (s)he's compiled here:
http://forum.xda-developers.com/showthread.php?t=2541900
I've also shared my personal installation notes as well as hosted the files that worked for me on my Google Drive. That information is here:
http://forum.xda-developers.com/showthread.php?t=2560478&page=3
You shouldn't need the files I've got hosted on my Drive though... The ones CNexus has assembled in that thread should work just fine (that's where I got most of them, after all).
I cannot speak to whether or not any of the steps in my notes will trip your KNOX Warranty Void bit since I tripped mine (and damn near hard-bricked my phone) before I even knew what the KNOX bootloader was, let alone that Samsung had gone ahead and installed it for me.
I hope that helps.
-Zen
I assume since this is the AT&T Galaxy S 3 section, you already know that I have the SGH-i747 model.
So I've been looking for a while, and I can't find anyone that has caused my same problem the way I did. I'll give the entire story: After having my S3 for a while, I decided to try rooting. I did it successfully, and got CyanogenMod installed. I don't know what, but I wanted to go back to touchwiz. I loaded a backup because it was exactly what I had before CM. fast forward about a month and a half, AT&T keeps bugging me about some update. It's the 4.3 update, I find out, after I installed it. Now, here's the confusing part. The SuperUser app was left over, but I have no CWM and no root privileges. I used this watch?v=yuBuD9aL12o (Paste after yt url) tutorial to root and get SuperSU, and it worked. The phone restarted many times in that entire process, and in the end it worked. One forum told me to install and apk called EZ-Unlock12.apk to unlock my boot loader. (I have included the exact APK if you want to look at it.) It just said successful and I closed out. Now, I wanted to flash CWM again with ODIN. I installed the drivers, and booted up ODIN. This is when it happened. I loaded up the CWM.tar.md5 file into ODIN, (not exact file name but you get what I mean), and it did it's verification and said it was good. I don't remember having my phone plugged in while doing this. I went to shut down my phone and put it in DL/ODIN mode. But now it has happened. I tried to bring my phone back up, but it didn't give ANY feedback. The only possible way to make it do ANYTHING is to plug it in without the battery, and i get the red light. I think it may have been that boot loader unlock program that messed it up, but I can't say for sure.
TL;DR I hardbricked my phone and don't know what went wrong.
Is that app for the verizon version of the s3? I believe the AT&T version of the s3 is the SGH-i747; however, your post refers to the sch-747 in the first line. From everything I have read, there is no way to unlock the AT&T s3 bootloader.
Not sure if this would help: http://forum.xda-developers.com/showthread.php?t=2549068
audit13 said:
Is that app for the verizon version of the s3? I believe the AT&T version of the s3 is the SGH-i747; however, your post refers to the sch-747 in the first line. From everything I have read, there is no way to unlock the AT&T s3 bootloader.
Not sure if this would help: http://forum.xda-developers.com/showthread.php?t=2549068
Click to expand...
Click to collapse
I meant SGH-i747, sorry for any confusion.
Did you try the unbricking method I linked? I think that may be the only way to unbrick the phone since it appears that your bootloader has been corrupted. If the unbrick method doesn't work, you'll probably have to have it repair via jtag.
Were you able to get it back to normal state? I am in the same situation as you with the same problem and was wondering if i should go do the method someone provided or just go ahead and pay for a jtag service.
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.