Previously, I asked something similar when the JSS15R was released. I was told that when OTA is installed, it overwrites the custom recovery with the stock one and that we can flash the custom recovery later. But why does everybody seems to be going back to stock version.
Also, if I go back to stock recovery will the root work?
littleromeo said:
Previously, I asked something similar when the JSS15R was released. I was told that when OTA is installed, it overwrites the custom recovery with the stock one and that we can flash the custom recovery later. But why does everybody seems to be going back to stock version.
Also, if I go back to stock recovery will the root work?
Click to expand...
Click to collapse
Flashing back to stock recovery will insure a successful installation. Usually if you're on a custom recovery it'll go through the process of installing then fail towards the end. You can always flash back to custom recovery after you confirm the installation has gone through.
littleromeo said:
Previously, I asked something similar when the JSS15R was released. I was told that when OTA is installed, it overwrites the custom recovery with the stock one and that we can flash the custom recovery later. But why does everybody seems to be going back to stock version.
Also, if I go back to stock recovery will the root work?
Click to expand...
Click to collapse
Traditionally stock recovery is what OTAs work with and what the manufacturer tests with so you are assured everything will work.
That being said, on a platform by platform basis, it is possible the custom recoveries will flash the OTAs fine.
From past OTA updates, people have found custom recovery successfully flashes the OTA for the Nexus 7 2013.
You can flash back to stock or use TWRP/CWM. Either will work (I've tested on WiFi/Flo but I believe folks on LTE/Deb have said the same)
Thanks. flashed the ota with latest twrp along with super su. Everything works fine.
Hi i just recently unlocked s-off and rooted my HTC one and played around in custom roms. I disliked most of them and when back to the stock rom. The only thing is now a new update came out and i cant update because when i try to install it i just go into my custom recovery (TWRP). I don't care about re locking, s-on and unroot all i want to be able to do is update the stock rom. thanks fro your time hope you can help.
Kojoez said:
Hi i just recently unlocked s-off and rooted my HTC one and played around in custom roms. I disliked most of them and when back to the stock rom. The only thing is now a new update came out and i cant update because when i try to install it i just go into my custom recovery (TWRP). I don't care about re locking, s-on and unroot all i want to be able to do is update the stock rom. thanks fro your time hope you can help.
Click to expand...
Click to collapse
This is all i did to get the updates to 15:
I have used Santod040 roms in case i need to go back to pure stock ROM only: http://forum.xda-developers.com/show....php?t=2485319
You will need the odex one to run any OTA . i would download/flash the stock 10 to be sure you get the full firmware to get the 15 update.
then
Get into fastboot and flash the stock recovery you can get below:
You can get it here:
https://www.dropbox.com/s/hgzgq84svzahvnv/htconerecovery_signed.img
fastboot flash recovery htconerecovery_signed.img
You can try to update.
That should resolve your problem and you might want to post this kinda stuff under help and troubleshooting since it fits that better.
Good Luck
htconerecovery_signed.img
MD5: E3F5208454689BE7F09835D4A60953A8
SHA-1: 1B0734D97732039528159AD1409AFEE858B5E9F1
SHA3-256: E0741EB77E5DEBEA932EE74F374FAC9E1037776178944279E8 B12832C30E2546
Hey guys, short background, upgraded to the HTC one at my brothers urging (showed me how sweet the phone can be after rooting and installing custom ROMs) and I absolutely love the phone. I bought the phone this last Sunday (Mar 2) and unlocked it with s-OFF, and installed the Viper 5.0 rom without too much trouble (had my brothers help). Since then I have come to learn that when making phone calls the only way for them to work properly is by using a headset with a mic built in. If I have the headset unplugged the call will go through (either receiving or making) but once it is picked up on either end there is no sound at all, even with speakerphone active. When someone calls me, my phone will ring, but again, no sound on either end.
I also never used the phone to make any calls before I rooted the phone, but I have ran a recovery back to stock ROM and still nothing. I have spent a lot of time on google searching the issue and everything I came across basically said get a new phone. Although it is annoying as hell, I would like to explore every option of fixing it before I take it back, and I think you guys can help!
Some friends have suggested updating radio's, and trying different ROM's, but to be honest I'm not sure I fully understand how to flash/run other ROM's on my own (my bro did most of the work while I watched) . I did reinstall the kernel I was using (ElementalX something) and reset all my power settings back to stock, but that didn't help any. Sorry for the wall of text but any help will be appreciated. Also, feel free to dumb it down for a HTC noob here
Thanks in advance!
p.s. using the HTC one 5.0 Viper ROM ElementalX kernel
Do you know if your brother ever updated it to the kitkat firmware? Running a kitkat rom with jellybean firmware is known to cause call issues. I would update the firmware using fastboot. You will need a pc with adb setup, and this file http://vzw1files.dyndns.org/FIRMWARE/3.11.605.1_firmware.zip If you feel up to trying it your self i can tell you how to do it.
Awesome man, that was it. Had to update the firmware/radio and now it works like a charm! Thanks very much!
Ok, so what I thought worked initially is no longer working . After I updated firmware/radio here http://forum.xda-developers.com/showthread.php?t=2485319 my phone started working correctly. After that I went on to download a HTC one color theme, and thats when problems started happening!
After I downloaded the theme and got my phone set up just the way I wanted it, it started freezing on me at the HTC splash screen. So after much deliberation I wiped everything back to the stock ROM and proceeded to reinstall my Viper 5.0 ROM and ElementalX kernel. During this process my phone went back to it's original problem of not wanting to give me any sound during phone calls. So I re-updated the firmware/radio again using the same zip file and steps that I had before from the link above ^^^ and my phone started restarting itself on its own, over and over. After I got into the recovery and yet again restored it back to stock roms and settings, the phone sound worked again. So, again, I installed the Viper 5.0 rom and elementalX kernel and checked to see if the phone was working properly, which everything was except for the phone sound (yet again). After another installation of the above firmware/radio update my phone decided to start restarting on its own again!!!
So currently I have wiped the ROM back to stock settings, and have not touched a thing! From what I understand there is not a problem with the ROM or the kernel (my brother is using the same files from my computer on his HTC one without any problems) but in my firmware/radio files. I have looked up a few firmware updates on my own but am hesitant to install them because I don't know if they're compatible with my phone/viper ROM. Again any help would be awesome, and I thank you in advance!!!!!!
-at wits end here
JMink10 said:
Ok, so what I thought worked initially is no longer working . After I updated firmware/radio here http://forum.xda-developers.com/showthread.php?t=2485319 my phone started working correctly. After that I went on to download a HTC one color theme, and thats when problems started happening!
After I downloaded the theme and got my phone set up just the way I wanted it, it started freezing on me at the HTC splash screen. So after much deliberation I wiped everything back to the stock ROM and proceeded to reinstall my Viper 5.0 ROM and ElementalX kernel. During this process my phone went back to it's original problem of not wanting to give me any sound during phone calls. So I re-updated the firmware/radio again using the same zip file and steps that I had before from the link above ^^^ and my phone started restarting itself on its own, over and over. After I got into the recovery and yet again restored it back to stock roms and settings, the phone sound worked again. So, again, I installed the Viper 5.0 rom and elementalX kernel and checked to see if the phone was working properly, which everything was except for the phone sound (yet again). After another installation of the above firmware/radio update my phone decided to start restarting on its own again!!!
So currently I have wiped the ROM back to stock settings, and have not touched a thing! From what I understand there is not a problem with the ROM or the kernel (my brother is using the same files from my computer on his HTC one without any problems) but in my firmware/radio files. I have looked up a few firmware updates on my own but am hesitant to install them because I don't know if they're compatible with my phone/viper ROM. Again any help would be awesome, and I thank you in advance!!!!!!
-at wits end here
Click to expand...
Click to collapse
You only need to flash the firmware/radios one time.
If you read the firmware radio install instructions in my thread, you should be using the one without the Boot.img/kernel.
The stock kernel is not gonna work on Viper apparently.
So you either flash the firmware which includes the stock Boot.img and then flash your choice of custom rom, or flash custom rom and then flash the firmware without the Boot.img that I posted.
If you are getting the files from my thread, that's where the instructions and proper files are located.
But once you have flashed the firmware it doesn't change until you flash new firmware again, no point in doing it over and over.
Flash firmware then Viper or use the one I posted without the stock kernel(boot.img)
So if you have no sound after updating firmware, flashing Viper and then a custom kernel, the issue is your kernel/rom combo.
You can flash any of the firmwares here http://vzw1files.dyndns.org/FIRMWARE/, or the ones from post 2 of santods stock rom thread in development. But it is recomended to match the firmware with the rom. So kk rom kk firmware, jb rom jb firmware. To me it sounds like a rom issue, a kernel issue, or a incompatibility between the two. But you said your bro is using it just fine so i dont know.
Does viper come with its own custom kernel built in, or does it just use the stock one?
santod040 said:
You only need to flash the firmware/radios one time.
If you read the firmware radio install instructions in my thread, you should be using the one without the Boot.img/kernel.
The stock kernel is not gonna work on Viper apparently.
So you either flash the firmware which includes the stock Boot.img and then flash your choice of custom rom, or flash custom rom and then flash the firmware without the Boot.img that I posted.
If you are getting the files from my thread, that's where the instructions and proper files are located.
But once you have flashed the firmware it doesn't change until you flash new firmware again, no point in doing it over and over.
Flash firmware then Viper or use the one I posted without the stock kernel(boot.img)
So if you have no sound after updating firmware, flashing Viper and then a custom kernel, the issue is your kernel/rom combo.
Click to expand...
Click to collapse
Thanks Santod, so far that appeared to have done the trick. Stayed up well into the AM last night to get this phone figured out. I downloaded your firmware without the Boot.img, flashed the custom rom, and then flashed the firmware and everything has been working so far.
If I could ask you two more quick questions, What is the significance of having the Boot.img or not having the Boot.img? And if down the road I install a new ROM and factory reset the phone, wont I have to update the firmware again?
JMink10 said:
Thanks Santod, so far that appeared to have done the trick. Stayed up well into the AM last night to get this phone figured out. I downloaded your firmware without the Boot.img, flashed the custom rom, and then flashed the firmware and everything has been working so far.
If I could ask you two more quick questions, What is the significance of having the Boot.img or not having the Boot.img? And if down the road I install a new ROM and factory reset the phone, wont I have to update the firmware again?
Click to expand...
Click to collapse
The Boot.img is basically the kernel and the files that initiate it(ramdisk).
If you are on a custom rom, you do not need nor want the stock kernel.
Most custom roms have a nice custom kernel included that is known to work on their rom.
If you simply wanted a stock rom and full stock firmware, then you would be using the stock kernel/boot.img.
As I stated above, the firmware doesn't change until you flash new firmware.
Flashing a new rom is not gonna overwrite the firmware, as it's done in fastboot, not in Recovery.
So if you flash a new rom, your firmware will not change and does not need to be flashed again until a newer one is posted.
A factory reset just resets your current rom to fresh install state, it doesn't effect firmware at all.
I have been reading through many threads last night and today trying to figure out the best way to get rooted stock back on my AT&T S3 i747. I had hoped to figure it out myself, but have come to the realization that I need a little guidance.
In light of that, I'll try to give concise information. First of all, I am simply looking to end up with stock.
Series of events:
*Have had stock since given this phone in August; it was kept up to date with OTA and it was current (4.4.2) as of yesterday morning when att pushed the newest update to the phone.
*I rooted the phone in September using CF root and Supersu to both root and block Knox and it had been working very well until the attempted update yesterday.
*I no longer have a custom recovery backup
*yesterday my phone went through the update (download and install), but when it rebooted, it only made it through the Samsung splash screen and then went black.
*I am able to boot up both stock recovery and into download mode
*Using the stock recovery to reset the phone has not fixed the problem
Having never used Odin or installed a custom ROM, I am hesitant to flash anything to the phone until I verify that the new bootloader (that is now possibly there due to the OTA update) and anything I try to install won't conflict and make my problem worse.
It seems to me that I should use Odin to load a custom recovery, make a backup, and then flash a ROM. If that is correct, would the recovery ROM found in this thread be the correct one: http://forum.xda-developers.com/galaxy-s3-att/general/ucufne4-to-ucufnj1-update-t2941792
If it is not the correct ROM, what would be the correct one?
Thank you,
M
For a custom recovery, flash the most recent tar.md5 file from here using Odin: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Boot into recovery, create a backup, and flash a custom ROM. I recommend the most recent CM10.2 so you can determine the bootloader currently installed on your phone. Once you determine the bootloader, you can decide how you want to proceed.
Thank you so much for your response.
I did as you suggested and I do indeed have the UCUFNJ1 bootloader. That does help me determine which direction I can take. Although, now having tried out a non-Samsung ROM, I may have changed my mind about keeping stock on the phone. If I decide to go back to stock, I'll just keep my eyes open for a stock ROM that states it requires that bootloader, correct?
Again, thank you so much for your help!
Hello guys,
following situation:
Long time I had a 4.4.something Rom installed. Before I flashed a custom Lollipop rom, I followed the advice to just go back to stock and let it update to Lollipop so that the firmware will be updated accordingly and I won't run into problems when flashing a Lollipop Custom Rom. Everything worked fine. Now I had to send my phone to HTC for display repair and just to make sure they won't nag about the custom Rom I reflashed some older stock rom via TWRP backup I found here, I think it was a 4.0 or so. The question is, does this also affect my phones firmware or is it still on the current newest level? So when I get it back, would I need to update to stock Lollipop again before flashing a custom rom or can I go for it straight away?
fBx said:
Hello guys,
following situation:
Long time I had a 4.4.something Rom installed. Before I flashed a custom Lollipop rom, I followed the advice to just go back to stock and let it update to Lollipop so that the firmware will be updated accordingly and I won't run into problems when flashing a Lollipop Custom Rom. Everything worked fine. Now I had to send my phone to HTC for display repair and just to make sure they won't nag about the custom Rom I reflashed some older stock rom via TWRP backup I found here, I think it was a 4.0 or so. The question is, does this also affect my phones firmware or is it still on the current newest level? So when I get it back, would I need to update to stock Lollipop again before flashing a custom rom or can I go for it straight away?
Click to expand...
Click to collapse
It won't affect your firmware.
Okay thanks, so Firmware should still be up to date and I can flash a Lollipop Custom Rom. I don't know what they do at HTC repair, if they only reset it or if they also update it, well I'll see.