Related
I tried flashing an ICS ROM on this I9020 via CWM and the phone would just keep tying to boot over and over...
I tried flashing a GB ROM (GRH78) through ODIN and now I'm unable to get into recovery.
My goal is get this thing back to stock rom with no root so it can receive OTA updates. Any odin files I can use to get me going? I haven't had any luck finding anything useful. Just fastboot references which I'm unfamiliar with.
Thanks to anyone that can help
Correct me if i am wrong, but there aren't any official odin tar files for Nexus devices since they get updates from Google.
I think you have to flash the stock rom using fastboot method, here are the stock roms: http://forum.xda-developers.com/showthread.php?t=1063664
Thanks for the response...I was finally able to use fastboot to get CWM installed (Phew). Now I want to restore this phone to factory (stock) settings so it can get OTA updates. How do I do that? I've been searching but all I see is GB ASOP.
Solved
Well I finally got it working. The issue I was experiencing was that I needed to root the device to be able to flash a stock ROM. Once I was able to root the i9020a, I was able to get it back to stock. I even had a Nexus 4G rom on the phone at one point. I had a hard time, but once I read about 37 different posts I was able to piece it together. So if anyone is having trouble getting back to stock, I'd recommend rooting the phone and using CWM to flash a stock ROM. Hope that helps anyone else that may have been struggling the way I was.
Hi all,
I apologize if this has been answered before, but I had trouble finding it here. I am currently rooted on a stock backup, but I am running a custom recovery. I am not sure where to find the stock recovery image for my device. I am using the HTC One M8 through Verizon, and I know that the new firmware update is coming out soon, and I'd like to be able to just OTA update my phone so that I can reflash a custom recovery and install the newest VenomROM. I have flashed a custom recovery before (obviously), but I didn't know if it mattered which firmware base you are running. I read somewhere that the recovery is totally separate from the OS, and it is meant to be an alternative to booting into the OS in case of a problem, but I want to be sure. If there is a specific recovery I need to use and someone here knows where I can find it, that'd be great. I found the collection of stock recoveries, but I'm having trouble figuring out which one I need to use. Any and all help is appreciated, thanks.
EDIT: My CID is VZW__001
My VERSION-MAIN is nothing. There's is just nothing next to this label.
I tried locating it on the collection of stock recoveries, but couldn't find it. I'm not sure why this is.
It takes more than stock recovery to take the OTA. The /system has to be essentially stock. Some mods (e. g. enabling powersave) may also csuse the OTA install to fail. There is a thread with a pseudo RUU. You ought to be able to get stock recovery there.
My name is Harold and I'm a flashaholic....
hgoldner said:
It takes more than stock recovery to take the OTA. The /system has to be essentially stock. Some mods (e. g. enabling powersave) may also csuse the OTA install to fail. There is a thread with a pseudo RUU. You ought to be able to get stock recovery there.
My name is Harold and I'm a flashaholic....
Click to expand...
Click to collapse
Hi there,
I actually just used the psuedo RUU tool (I assume this is the one you are talking about? http://forum.xda-developers.com/showthread.php?t=2727831)
I just finished using this tool, but when I went to check the recovery, all I get is a big red triangle with an exclamation point in the middle. Nothing else. So, I'm guessing that recovery didn't flash properly? But I'm honestly not completely sure. I would screenshot it, but I can't do that. Any help is appreciated.
EDIT: I found out that pressing volume up and power gives more options. I assume I am all good to go now? I am still rooted, and I'm not sure if that is a problem. I am stock, s-off and rooted, but I don't have any mods installed.
You can't do anything in stock recovery except take an OTA, assuming everything else is stock. You can't do Nandroids, flash zips, etc. Looks like you have stock recovery.
My name is Harold and I'm a flashaholic....
hgoldner said:
You can't do anything in stock recovery except take an OTA, assuming everything else is stock. You can't do Nandroids, flash zips, etc. Looks like you have stock recovery.
My name is Harold and I'm a flashaholic....
Click to expand...
Click to collapse
Yeah I just figured out how the more options appear. I assume I'm good to go for the OTA now? I've got stock recovery, running a stock backup, s-off and I'm still rooted, but I think those are not a problem. I am not running any mods.
ChuckFinley1992 said:
Yeah I just figured out how the more options appear. I assume I'm good to go for the OTA now? I've got stock recovery, running a stock backup, s-off and I'm still rooted, but I think those are not a problem. I am not running any mods.
Click to expand...
Click to collapse
You should be good to go. A cautionary note, however, is that if you are rooted (even if S-OFF), it's not always advisable to take the OTA because frequently OTA's plug exploits used to secure root, etc. There was a definite difference between the original stock Verizon M8 ROM releated 3/25/14 and the minor update which followed, and some were unable (myself included) to secure stable root and/or S-OFF with weaksauce, having to acquire a license to Sunshine instead.
I intend to stick on my custom ROM and recovery and trust the developers to massage the OTA once it's out and have, literally within days if not hours, an updated ROM/firmware zip file that will more than adequately fit the bill.
hgoldner said:
You should be good to go. A cautionary note, however, is that if you are rooted (even if S-OFF), it's not always advisable to take the OTA because frequently OTA's plug exploits used to secure root, etc. There was a definite difference between the original stock Verizon M8 ROM releated 3/25/14 and the minor update which followed, and some were unable (myself included) to secure stable root and/or S-OFF with weaksauce, having to acquire a license to Sunshine instead.
I intend to stick on my custom ROM and recovery and trust the developers to massage the OTA once it's out and have, literally within days if not hours, an updated ROM/firmware zip file that will more than adequately fit the bill.
Click to expand...
Click to collapse
That does sound pretty appealing. I've never flashed firmware before though, and I wouldn't want to mess anything up. I remember seeing on the VenomROM firmware section, the easiest way to flash new firmware is to just grab the OTA update. The other way involved using some other program that I have not used before. I am overestimating how difficult installing new firmware is?
ChuckFinley1992 said:
That does sound pretty appealing. I've never flashed firmware before though, and I wouldn't want to mess anything up. I remember seeing on the VenomROM firmware section, the easiest way to flash new firmware is to just grab the OTA update. The other way involved using some other program that I have not used before. I am overestimating how difficult installing new firmware is?
Click to expand...
Click to collapse
Firmware (splash screen, radios, hboot, recovery) are "flashed" with an S-OFF handset via fastboot from the bootloader, while connected to PC. I believe (again, based upon the RUU thread I mentioned previously which you seem to have found) that it may also be possible to flash from hboot using an update.zip file (I think the M8 file is called PB06IMG.zip, but don't hold me to that --- every phone has its own such file format/name.)
ROMs and mods are typically flashed via recovery.
hgoldner said:
Firmware (splash screen, radios, hboot, recovery) are "flashed" with an S-OFF handset via fastboot from the bootloader, while connected to PC. I believe (again, based upon the RUU thread I mentioned previously which you seem to have found) that it may also be possible to flash from hboot using an update.zip file (I think the M8 file is called PB06IMG.zip, but don't hold me to that --- every phone has its own such file format/name.)
ROMs and mods are typically flashed via recovery.
Click to expand...
Click to collapse
Okay, I may look into that. I've only seen an RUU flashed via hboot, so I'd have to look into it. At the very least though, I'd imagine someone will post the instructions on how to flash the firmware when it comes out.
Thanks so much for your help!
hgoldner said:
I intend to stick on my custom ROM and recovery and trust the developers to massage the OTA once it's out and have, literally within days if not hours, an updated ROM/firmware zip file that will more than adequately fit the bill.
Click to expand...
Click to collapse
+100 for this!
I am reading dozens of posts in all kinds of threads of people just dying to take that OTA...
Why???
I would not touch that new firmware with a 100 foot pole until the devs have figured out what it breaks!!!
I predict a flood of posts in the line of:
"I flashed back to stock to take the OTA and now weaksauce is not working - how do I get root back?"
What's the hurry?????
I currently have S-Off and have it rooted through Weaksauce and SuperSu I believe. I have flashed ROMs through TWRP but did not like them, so I recovered back into my 4.4.2 stock. If I update to 4.4.4 by Verizon's OTA, will I lose my root and S-Off?
kinda a noob but...
steezy123 said:
I currently have S-Off and have it rooted through Weaksauce and SuperSu I believe. I have flashed ROMs through TWRP but did not like them, so I recovered back into my 4.4.2 stock. If I update to 4.4.4 by Verizon's OTA, will I lose my root and S-Off?
Click to expand...
Click to collapse
I'm not a hundred percent but I think the only way you lose it is if it upgrades the boot.img search for tigers posts because from the way it sounded to me if you flashed back to stock you'd have all ready lost your s-off.... Unless you've flashed one of the stock with the boot.img and recovery img removed. If so I'm pretty sure your good for the firmware upgrade if it'll ota without stock (or forged) boot.img file... Anyway man I'm slightly baked and never been accused of being smart enough to remember **** I read two weeks ago so search "tigerstown" posts and threads and read man and when you understand all a bit better than me then come message me and we'll discuss it a bit so it'll stick to my head a lil longer than last time man. Hope my rambleing might have shed some light on the subject or at least pointed you to the posts that know lol goodluck
The only way to "lose" s-off is to issue the fastboot command to set that flag which many smart people would never advise you do anyway. Nothing we are talking about here will do that automatically.
If you're s-off and on a custom Rom of any sort, I would recommend updating the firmware through tigerstown's method the previous poster referred to. If you're going to the trouble to flash everything necessary to take the ota, you may as well just flash his file and be done.
If you prefer stock, I would recommend you flash a stock-based Rom like CleanRom or NuSense. They come pre-rooted with some bloat removed and just a few tweaks added like write-protection removed, init-d support, etc.
If you really insist on running pure stock with root then you should at least root properly by uninstalling weak sauce and flashing the su binaries in recovery.
cntryby429 said:
The only way to "lose" s-off is to issue the fastboot command to set that flag which many smart people would never advise you do anyway. Nothing we are talking about here will do that automatically.
If you're s-off and on a custom Rom of any sort, I would recommend updating the firmware through tigerstown's method the previous poster referred to. If you're going to the trouble to flash everything necessary to take the ota, you may as well just flash his file and be done.
If you prefer stock, I would recommend you flash a stock-based Rom like CleanRom or NuSense. They come pre-rooted with some bloat removed and just a few tweaks added like write-protection removed, init-d support, etc.
If you really insist on running pure stock with root then you should at least root properly by uninstalling weak sauce and flashing the su binaries in recovery.
Click to expand...
Click to collapse
Thanks for all help, I'll start readin up. Just one question: let's say I update my firmware to 4.4.4 from Verizon's OTA, will I be able to flash this clean rom via TWRP? http://forum.xda-developers.com/showthread.php?t=2732877
The only reason I ask is because it says the user must be running 4.4.4 firmware to flash the rom and the only way I know how to get 4.4.4 is from Verizon's OTA
You can get everything you need from Verizon's 4.4.4 release by flashing the no boot no recovery file from the tigerstown thread mentioned earlier. It's the first file listed in his op. The rest of the ota contains the recovery (which you don't want since you need your custom recovery to flash custom ROMs) and the boot.img/kernel (which you don't need since every room comes with a kernel). It's not wrong till go back to stock to take an ota, it's just unnecessarily difficult when people like tigerstown make it so easy for us to accomplish the same thing.
ok. is it even possible to have two recoveries running at once? On normal boot-up, I get the safestrap screen asking to continue or enter recovery. I have flashed TWRP and I can get to TWRP by fastbooting and entering recovery that way. I feel i have set myself up to brick in the hard sense. I just unlocked w/ sunshine and am trying to make a backup before i really start screwing stuff up.
If you're unlocked with TWRP then safestrap is redundant since you can't utilize the extra ROM slots.
Sent from my XT1080
that was kind of my thoughts too. I did remove safestrap manually. Im still tying to update with the latest OTA, but with no luck. thanks.
teerout said:
that was kind of my thoughts too. I did remove safestrap manually. Im still tying to update with the latest OTA, but with no luck. thanks.
Click to expand...
Click to collapse
The update isn't going through because you have TWRP installed. Flash to stock recovery and try again.
Sorry I left that out, I have removed TWRP. I have returned to as stock as I can. Flashed back to factory. Still no success on OTA update. Im hunting for the files now and i will hopefully flash it myself.
Moto Droid Maxx firmware found here->https://motorola-global-portal.cust..._detail/a_id/95417/p/30,6720,8882/reg/1192476 - you have to sign in...
Ok, let me start by saying that I'm fully capable of updating my phone with a computer, I'm just hoping there is a better way. So far every time I've downloaded a new firmware, update the flash-all.bat and run it, something will fail towards the end of the update and the only way I've been able to successfully update is by using one of those tool kits (forget which one, it's on my computer). I'm not that concerned about all of that with this thread. I'm wondering if there is a way to do it without a PC.
I'm on NMF26O (root, ElementalX, etc) and tried flashing Pure Nexus over the weekend. Since it's based on NMF26V, I kept receiving an error on boot about updating my vendor.img. So I downloaded that firmware, extracted it, and flashed the vendor.img in TWRP. That led to a plethora of other issues that I couldn't resolve by flashing the boot.img, reflashing the rom, ect. Several hours later I ended up flashing the boot.img and vendor.img for NMF26O, restoring my backup, re-installing Elemental, and rooting again.
Since these updates will be coming out every month, and roms will always be based on the latest update, I feel like I'll be pulling out the computer every month, downloading the updates, modifying the flash-all.bat, and running it through the tool, just to be able to update my rom. The first time I forget to update flash-all.bat, I'll lose the 60+ GB's I keep in internal storage. There has to be an easier way. TWRP is capable of flashing images. Has anyone been able to update without using a computer? I don't care if my radio is out dated, or something is mismatched as long as my phone works as intended.
Sent from my Pixel using Tapatalk
Not sure why you ran into issues with PN. You need to be on the latest build NMF26U. You can flash the ROM via recovery. Then tku have to reboot once and go back to recovery and flash the V vendor image because the ROM is based on NMF26V. Each time a new ROM comes out on a new build you can flash in recovery.
If your talking about flashing stock OTAs via recovery that's not possible yet. No need to do this if you're going to be using custom ROMs though
aholeinthewor1d said:
Not sure why you ran into issues with PN. You need to be on the latest build NMF26U. You can flash the ROM via recovery. Then tku have to reboot once and go back to recovery and flash the V vendor image because the ROM is based on NMF26V. Each time a new ROM comes out on a new build you can flash in recovery.
If your talking about flashing stock OTAs via recovery that's not possible yet. No need to do this if you're going to be using custom ROMs though
Click to expand...
Click to collapse
I'm on NMF26O. What's the difference between it and NMF26U and why would the vendor image from NMF26V work with NMF26U but not NMF26O?
Seems like all you would need is the /system from the rom, the vendor image, and maybe the boot image (or a custom kernel). I think I'm missing something here.
Sent from my Pixel using Tapatalk
If you install PN its based on NMF26V. So unless you are already on that then you would need to flash the ROM, reboot back to recovery, then flash the NMF26V vendor image.
I'll play devil's advocate here... Yeah there is an easier way, use your Pixel stock and take OTA's. Enjoy a phone that always works, with or without a laptop!
I understand my audience and realize this isn't a popular mantra here but I felt exactly like you did with my 6p and vendor images. I got to the point where I sacrifice root now just for my own sanity. My phone works for me, not the other way around.
What I do is side load the full OTA ( which you can get from the same place you get the factory images ). I only use the fastboot boot version of TWRP so that my stock recovery stays in place. Then all you have to do is boot into the stock recovery, adb side load the OTA file and re root. Then you're fully up to date without worries of your data being wiped :laugh:!
( Although if you look in the flash fire thread from Chainfire, he's working on a version that will let rooted pixels flash otas like normal ones :fingers-crossed: )
I think you guys are missing the point. I have no desire to ever be stock, which rules out the possibility for an OTA in any form.
What I'm trying to figure out is exactly what is necessary to make a custom rom (based on the latest OTA), work if flashed over an older build, without first somehow applying the full OTA. Or is it impossible?
On just about every other phone I've owned, we could piecemeal the files needed for minor updates, along with a custom rom. The only time we'd have to flash a full update is for major updates ( 4 to 5 to 6, etc).
Sent from my Pixel using Tapatalk
Ok, I figured it out. Just download the OTA.zip (not the full firmware), flash in TWRP, immediately flash TWRP again, and reboot.
I'm now on nmf26u.
Sent from my Pixel using Tapatalk
joshw0000 said:
Ok, I figured it out. Just download the OTA.zip (not the full firmware), flash in TWRP, immediately flash TWRP again, and reboot.
I'm now on nmf26u.
Click to expand...
Click to collapse
I don't think we can just flash OTAs in twrp yet. Haven't heard of Antone doing it. There is a beta Flashfire out that I guess works to flash updates. J have it but haven't needed to try it cause I'm running PN and DU
aholeinthewor1d said:
I don't think we can just flash OTAs in twrp yet. Haven't heard of Antone doing it. There is a beta Flashfire out that I guess works to flash updates. J have it but haven't needed to try it cause I'm running PN and DU
Click to expand...
Click to collapse
I've done it several times tonight. Went from O to U to V, flashed Pure Nexus, screwed up the rom, restored to O, then O flashed back to U and V.
Just flash it like a rom in TWRP RC1. Make sure you flash TWRP again before rebooting if you want to keep it.
Sent from my Pixel using Tapatalk