Related
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
I've flashed lot's of rooms, but I'm no expert. To day I flashed ' trickster'
My root went, back ups, when I try to put my phone in to boot it won't,I get an error message. Is this a bad from?. Now I can't get boot or access to my files I'm stuffed it seems to me.HELP PLEASE!!!! Thx.
Can you get to recovery mode?
root taken
No I've no way. When I try nothing happens. Can't boot, go to recovery.I've lost all that.With the from being called trickster, NO OFFENCE! but I feel like I have been .
I've no way in to the phone. It works normally, except I can't go to recovery or re boot etc.
You checked "yes this is a question"
Guess where it belongs?
Thread moved!
Sent from my SPH-D700 using xda premium
I swear I cant even begin to imagine how stuff like this happens.
@op, boot to bootloader, reflash cwm with fastboot. Reboot to recovery straight from bootloader, wipe data/factory reset, reflash favourite rom.
Sent from my i9250
root taken
I CANT GET BOOT LOADER UP! Or any boot or of course I'd flash a from . I'm blocked from any way to do it ! Gonna sell as an in rooted and get another.
Seems all I can do
howard bamber said:
I CANT GET BOOT LOADER UP! Or any boot or of course I'd flash a from . I'm blocked from any way to do it ! Gonna sell as an in rooted and get another.
Seems all I can do
Click to expand...
Click to collapse
if you cant get into bootloader and/or recovery, i highly doubt it has anything to do with the rom. most likely a coincidence. getting into the bootloader/recovery has nothing to do with having root. even if you lost root, youd be able to use the rom, just not the apps or functions that needed root. btw, what error message do you get? maybe some more info is needed here, like what version galaxy nexus? and selling someone else a broken phone is wrong, unless youre selling it cheap and the person buying it knows that its not functional.
root taken
SORRY! Just checked your links but I've no way to put the code in! I'm that locked out! When I try I just get errors.I can use the from its just plain vanilla ics, I'm using the phone now. It's a GSM unlocked international. The phone is not broken at all just no way to root it again. I will of course point it out. Its got 4.4 ics and the update link. I'd happily buy it if I did not root
howard bamber said:
SORRY! Just checked your links but I've no way to put the code in! I'm that locked out! When I try I just get errors.
Click to expand...
Click to collapse
link me to that rom thread please. there is a chance that it is a "secure" rom, im not very familiar with it so id like to read up on it.
my root taken
Thank you 'does not exist'!!! I went to the links, typed code etc, and it worked! I'm so grateful to you . Its nice that in this day and age pple take time out to help!
As the title states, I finally got the prompt to do an update for phone, from Orange, but when I set it to install it, it reboots and says failed.
I think it is due to me having CWM on the phone, so it cannot do a clean restart, how do I get passed this, if anyone has a How To for this please help me, also will I be able to save all the apps, messages, contacts and settings on the phone.I have stock Rom on phone.
All and any help much appreciated in advance.
Duh! You need stock recovery. You need to unlock your phone again and flash stock recovery with this command
Fastboot flash recovery recovery.img
Relock and try again
shadehh said:
Duh! You need stock recovery. You need to unlock your phone again and flash stock recovery with this command
Fastboot flash recovery recovery.img
Relock and try again
Click to expand...
Click to collapse
Hi there, I am already unlocked, so do I have to Lock it again, then flash stock Rom.
Will I have to lose my apps and settings.
Sorry for the noob questions, but this phone is new to me so I don't know the correct way.
Seems a bit over the top to start off with Duhh, just because I don't know, so therefore I need to ask to know, I am a brainy person, but still I would rather ask for the right way rather than guess and brick my £400.00 phone.
Thankyou for your reply, but I still need help on this.
promethieus said:
Hi there, I am already unlocked, so do I have to Lock it again, then flash stock Rom.
Will I have to lose my apps and settings.
Sorry for the noob questions, but this phone is new to me so I don't know the correct way.
Seems a bit over the top to start off with Duhh, just because I don't know, so therefore I need to ask to know, I am a brainy person, but still I would rather ask for the right way rather than guess and brick my £400.00 phone.
Thankyou for your reply, but I still need help on this.
Click to expand...
Click to collapse
Sorry. Well you need to have stock rom as well as recovery. Once you have both you have to relock your phone and try to update again
Sent from my HTC One X using xda app-developers app
You do not need to relock to apply ota update. Just have the stock recovery and then try again. There are links to the stock recoveries of different versions in the cwm sticky
Sent from my HTC One X using xda app-developers app
All done Update installed, but I did do a backup of things, but when I got things back up and running again, it did not save my maps and such, I work as a mobile care support person, so the maps were important to me, so I wil have to find a better way to do things.
I also had to try to remember usernames and passwords, I never write any down. but its a shame that an image of phone, os and everything can not be done, so as not to have to put them in again, so that everything works straight off the bat.
Thanks for any and all advice, great forum here and alot of very helpful people.
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.