Develop Bugs

Upcoming Update

If and when the Gingerbread update gets pushed out, how will us custom ROMmers be notified? Will we receive notifications asking us to download the update and then have to deny it? Will we have to unroot then upgrade? I wasn't around for the 2.2 update so I am a little curious as to how this all works on the Evo. Feel like such a noob right now but I really don't feel liking bricking my Evo due to an act of stupidity.

Don't have to unroot, it should show there is an update, update and it will take off root and go to stock 2.3, anyone correct me if I'm wrong.

You aren't going to need to do anything, other than NOT take the OTA. The only thing you will need to do is wait from 2-10 hours after the update is out in the wild for the devs to get their hands on it and give us a fully rooted build to flash. It does not take long around here. There is absolutely no need to unroot and take the OTA. Who knows, if you did that you may not even be able to root again. So basically all you're going to need to do for the update is wait for the devs, and then flash a rom as usual. Maybe some new radios or something too, who knows.
I'm more concerned about when they will push the damn update. *Supposedly* it's Q2, but I'd bet if that's true, it will be late Q2.

r916 said:
Don't have to unroot, it should show there is an update, update and it will take off root and go to stock 2.3, anyone correct me if I'm wrong.
Click to expand...
Click to collapse
Sure, lots of people say "wait for a rooted version of the update," but all I want to know is, is it POSSIBLE to safely upgrade even if you are rooted? Would flashing the stock update remove ClockWork recovery?

yes i was rooted before 2.2 and i was having a crazy day, long story short i accepted the OTA not paying attention and it got me a weird reboot then i was unrooted and on 2.2 i had to wait for a root method for it. but i heard of some people having their phone glitch in crazy ways, also that first OTA sprint rolled out had a bug that was bricking some phones

RileyGrant said:
If and when the Gingerbread update gets pushed out, how will us custom ROMmers be notified? Will we receive notifications asking us to download the update and then have to deny it? Will we have to unroot then upgrade? I wasn't around for the 2.2 update so I am a little curious as to how this all works on the Evo. Feel like such a noob right now but I really don't feel liking bricking my Evo due to an act of stupidity.
Click to expand...
Click to collapse
Developers will simply make new roms, and then you can flash the "update" of that rom. it'd be the same way of flashing CM7 nightlies.

Or just make sure you are s-off, take the update, install it. Then install SU from recovery and you are good to go. Thats the whole point of s-off (other than flashing PRI, NV, and Radios of course)

rugedraw said:
If you rooted with Unrevoked and have Unrevoked Forever, then theoretically you should be able to flash the update and still be s-off to flash a rooted rom over the update. You'd have to push the custom recovery back onto the phone, though. However, I wouldn't be the guinea pig for the theory myself. I'd keep 2.2 until a rooted 2.3 rom is available and then flash that. No one knows what will happen if you flash the OTA update as no one has is or knows what's inside of it.
Once it starts being pushed out, it will just be a matter of time before some posts a thread either:
a) crying because the update broke their root.
b) gloating because the update did NOT break their root.
Basically, don't accept it. Play it safe and wait. We've been on 2.2 for well over half a year, so 1 more day isn't going to kill anyone.
Click to expand...
Click to collapse
To make it simple, the result of accepting the OTA would either:
A- luckily do nothing
B- "Break" your phone and not be able to re-root

r916 said:
Don't have to unroot, it should show there is an update, update and it will take off root and go to stock 2.3, anyone correct me if I'm wrong.
Click to expand...
Click to collapse
You are correct!

Theoretical question... If you're on a custom non-stock ROM (Myn or CM or whatever) and you accept the OTA, what would happen to the ROM? I don't think it would revert you back to the stock ROM because that ROM isn't on your phone anymore. I can't imagine CM would continue to work since it's not Sense. Would a Sense-based ROM (assuming you reinstalled all the Sprint bloatware) continue working with all the customizations even though you don't have root any more? Or does the OTA rewrite the entire ROM? Or would you just screw up your phone unpredictably?
I'm certainly not going to try this myself, but I'm curious as to what would happen.

phsteve said:
Theoretical question... If you're on a custom non-stock ROM (Myn or CM or whatever) and you accept the OTA, what would happen to the ROM? I don't think it would revert you back to the stock ROM because that ROM isn't on your phone anymore. I can't imagine CM would continue to work since it's not Sense. Would a Sense-based ROM (assuming you reinstalled all the Sprint bloatware) continue working with all the customizations even though you don't have root any more? Or does the OTA rewrite the entire ROM? Or would you just screw up your phone unpredictably?
I'm certainly not going to try this myself, but I'm curious as to what would happen.
Click to expand...
Click to collapse
The OTA update would include the new stock 2.3 rom in it. It would wipe whatever you have on your phone (regardless of whether it is Sense or not) and install the OEM Sprint 2.3-based rom that all will eventually be on all new Evos when HTC ships them out.

[Q] New HOX Owner, Few Questions

I just received my HOX today from Expansys, EU version I believe.
I plan to root, ROM and everything else I can do.
So, I've got a few questions on where I should go from here.
Should I install the OTA? Or should I wait just in case there's some unlock/s-off method related to older versions that get fixed/patched with the newer OTA?
Should I unlock via HTCDev or wait for devs to figure out unlock/s-off? As an app developer, I generally keep old phones laying around so I likely won't be selling it, and as long as the actual hardware is still under warranty, I'm not too concerned.
Is there a way to do a full backup of the phone as is? If I were to say, install CM9, do I need the full backup or can I just re-install a stock image?
Anything I should look at/inspect before I get too crazy with the phone? Serial number, where it's manufactured, specific defects, etc...?

fescen9 said:
I just received my HOX today from Expansys, EU version I believe.
I plan to root, ROM and everything else I can do.
So, I've got a few questions on where I should go from here.
Should I install the OTA? Or should I wait just in case there's some unlock/s-off method related to older versions that get fixed/patched with the newer OTA?
Should I unlock via HTCDev or wait for devs to figure out unlock/s-off? As an app developer, I generally keep old phones laying around so I likely won't be selling it, and as long as the actual hardware is still under warranty, I'm not too concerned.
Is there a way to do a full backup of the phone as is? If I were to say, install CM9, do I need the full backup or can I just re-install a stock image?
Anything I should look at/inspect before I get too crazy with the phone? Serial number, where it's manufactured, specific defects, etc...?
Click to expand...
Click to collapse
you should definitely install any OTA that you get. if there is an s-off method discovered, it will be time and it probably won't matter what version you're running. i don't know how it works, but these updates have important fixes. if you only update to 1.28, then it might be a long wait for another OTA so you have to decide for yourself if you want to wait or unlock. you can't do a backup without unlocking and installing CWM afaik. as for inspection, just use it normally and see what it does. i just noticed on mine in the sunlight the screen looks like a grid when it's off. that's not a flaw but some people would probably freak out and exchange it. if your whites are bright white and you have no dead pixels, then your phone is good.

If you aren't more concerned about warranty, unlock through htcdev.com, as s-off may take too long, I didn't see any update on that. Once you unlock through htcdev.com you're good for everything.
I suggest you to avoid installing OTAs if you have plans to unlock your device, as the s-off devs are currently working on hboot 0.4x version. If you update the phone with OTAs the hboot will be updated to 0.9x, so you have to find a way to get downgrade your bootloader to get s-off.
Sent from my HTC One X using xda premium

Just made a jump from note 2 to note 4 - Need suggestions

Hello community,
I got a Note 4 N910V and the jump was something incredible. I am in love with the thing.
My note 2 was rooted and had the Resurrection Remix rom. I felt free to customize it since I didn't have to worry about the bootloader or anything but it was really sluggish.
My note 4 came with 5.0.1(stock rom) and skiming through the forums I'm seeing things like 'safely upgrade to MM'. Makes me thing the OTA update ain't working right for everyone.
I'm not getting any OTA updates, could be because I'm not in the US and my phone is unlocked for a local telco.
I have a couple of questions
- Is the MM update fine? Battery, performance, root? how would I update if I'm not getting any OTA updates?
- I know about kingroot but is it recommended as the root option for my OS version. I found this but It's been a long time since I rooted a phone.
- Any popular ROM/Mods? RR was a big thing in the note 2 community (also a couple of custom kernels).
Pics of what I got down below.
Thank you for your time.

I'm using this phone on Bell Mobility in Canada and was unable to get the OTA. I have no intention of rooting this phone yet.
I was able to get the stock 6.0.1 OTA file from here:
http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2942937
I was able to update using the stock recovery without issue....

crutzulee said:
I'm using this phone on Bell Mobility in Canada and was unable to get the OTA. I have no intention of rooting this phone yet.
I was able to get the stock 6.0.1 OTA file from here:
http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2942937
I was able to update using the stock recovery without issue....
Click to expand...
Click to collapse
Hey man thank you for your answer!
Did you have any problems with the unlocked properties (telco wise, no bootloader) when flashing these things?
I also checked my download mode and doesn't say anything about developer. Seems fine showing up Odin mode so I'm going to assume this is a retail version.

demiorkan said:
Hey man thank you for your answer!
Did you have any problems with the unlocked properties (telco wise, no bootloader) when flashing these things?
I also checked my download mode and doesn't say anything about developer. Seems fine showing up Odin mode so I'm going to assume this is a retail version.
Click to expand...
Click to collapse
The only way to get an ota is to be on Verizon. Other wise you'll need to download the update and flash with Odin or flash with stock recovery.
The reason for the "safe update to mm" threads are for people who rooted and unlocked the boot loader. You'll need to follow one of those threads if you want root. Nothing wrong with just updating to mm other than you'll have to downgrade to 5.1.1 if you later decide you want root and unlocked boot loader
These phones become really unstable if you just try to root and you lose root once you restart the phone.
Sent from my SM-N910V using Tapatalk

Upgrading Modem?

Hello all. I recently spent 5+ hours rooting and turning my VZW Note 4 into a "developer" phone. I've rooted a lot of phones, but this particular process had me pretty frustrated. I had several problems with the software versions I was using. Anyway, I'm curious if I should upgrade just my modem firmware to the latest included in VZW's 6.0.1 release. On my old Android devices, I used to do this with great success. Signal strenght would increase (or worsen), GPS signal would be better, etc. Is this included in ROMS and/or is it safe to do this?

Oh man,lol don't tell me that. I just bought a note 4 off swappa and it'll be here wendsday probably. I have been wanting a note 4 for along time. Only reason why I never got it was because of root and BL being locked down. Now that there is custom roms & kernels I bought it and can't wait to get it. Is it really that bad to Root and BL unlock? If it took you that long it'll take me days because I work 12hr job 7 days a week. I'm just trying to find all the necessary files I need to download now that way that will be done with.
Sent from my VS990 using Tapatalk

av00va said:
Hello all. I recently spent 5+ hours rooting and turning my VZW Note 4 into a "developer" phone. I've rooted a lot of phones, but this particular process had me pretty frustrated. I had several problems with the software versions I was using. Anyway, I'm curious if I should upgrade just my modem firmware to the latest included in VZW's 6.0.1 release. On my old Android devices, I used to do this with great success. Signal strenght would increase (or worsen), GPS signal would be better, etc. Is this included in ROMS and/or is it safe to do this?
Click to expand...
Click to collapse
Look in @hsbadr's Jasmine ROM thread. There's a partial firmware to flash that will update both the bootloader and the modem to PF3, which is the latest and greatest. It's required if you want to use Jasmine 7.0 or @chevyrhoad's Grace 7 ROMs.

mwebb34 said:
Oh man,lol don't tell me that. I just bought a note 4 off swappa and it'll be here wendsday probably. I have been wanting a note 4 for along time. Only reason why I never got it was because of root and BL being locked down. Now that there is custom roms & kernels I bought it and can't wait to get it. Is it really that bad to Root and BL unlock? If it took you that long it'll take me days because I work 12hr job 7 days a week. I'm just trying to find all the necessary files I need to download now that way that will be done with.
Sent from my VS990 using Tapatalk
Click to expand...
Click to collapse
It's a matter of being familiar with the tools. The process is pretty rudimentary. If you have a knowledge of linux and/or abd you'll be fine. I had trouble when my phone decided to start boot looping. Turns out it skipped my mind to wipe the cache/data clean after a stock odin flash. After all is said and done, the process is fairly simple. Also, King Root is a big issue. If you dump a fresh ROM from odin onto your device, install King Root, and attempt to root it it will root successfully everytime, the first time. On some other ROMs it can give you a considerable amount of trouble. I recommend resetting your lollipop to defaults, rooting it, flashing to the 5.1.1/6.0.1 hybrid, rooting again, and then continue about your business. There's a certain set of steps that makes this process painless which you can only ascertain if you have done it.

douger1957 said:
Look in @hsbadr's Jasmine ROM thread. There's a partial firmware to flash that will update both the bootloader and the modem to PF3, which is the latest and greatest. It's required if you want to use Jasmine 7.0 or @chevyrhoad's Grace 7 ROMs.
Click to expand...
Click to collapse
Can I flash "N910VVRU2CPF3_PartialFirmware_PatechedKernel.tar.md5" from his thread overtop of my TRWM and CM 13 ROM? I have both installed, and I'm wondering if I can just boot into the bootloader and odin this to the phone. CM 13 supports it, so why not? I'm just worried about it a kernel malfunction.

av00va said:
It's a matter of being familiar with the tools. The process is pretty rudimentary. If you have a knowledge of linux and/or abd you'll be fine. I had trouble when my phone decided to start boot looping. Turns out it skipped my mind to wipe the cache/data clean after a stock odin flash. After all is said and done, the process is fairly simple. Also, King Root is a big issue. If you dump a fresh ROM from odin onto your device, install King Root, and attempt to root it it will root successfully everytime, the first time. On some other ROMs it can give you a considerable amount of trouble. I recommend resetting your lollipop to defaults, rooting it, flashing to the 5.1.1/6.0.1 hybrid, rooting again, and then continue about your business. There's a certain set of steps that makes this process painless which you can only ascertain if you have done it.
Click to expand...
Click to collapse
I will absolutely take you're advice on this and apply it as soon as I get my note 4. Should be receiving it in about 3 or 4 days.
Sent from my VS990 using Tapatalk

av00va said:
Can I flash "N910VVRU2CPF3_PartialFirmware_PatechedKernel.tar.md5" from his thread overtop of my TRWM and CM 13 ROM? I have both installed, and I'm wondering if I can just boot into the bootloader and odin this to the phone. CM 13 supports it, so why not? I'm just worried about it a kernel malfunction.
Click to expand...
Click to collapse
To the best of my knowledge, it does nothing to the kernel. All it does is upgrade the modem.

Question Custom OTA sideload with November radio?

My P6P (on T-Mobile) was working fine for me on the November release.
I did not sideload the December release.
With the January release, I started to notice significant radio issues.
I am seeing the same issue with the February release and after taking a look, I see that the radio has NOT changed between January and February. (But is a different radio from the November update)
I would definitely like to try flashing the November radio, but my Pixel bootloader is locked and can't be unlocked since it is still carrier locked. (I am working on that.)
In the meantime, is it possible for someone to make a custom OTA sideload package with just the November radio in it for those with locked bootloaders?

The 12L radio is different. I flashed it yesterday (12L factory image) and Signal is back to normal, and switching from Wifi to LTE/5G is much better than it's ever been on my 6 Pro. but its only been 24hours, but worth a try/

Good to know, but if I don't want to go 12L... again, could someone create a custom OTA sideload package with just the radio from 12L?

If this is even possible, which I'm dubious of, you might want to think twice. With a locked bootloader, your recovery options are more limited, so if someone creates such a custom OTA zip (again, if that's even possible to work with an unlocked bootloader), and something goes seriously wrong, it might be either more difficult or impossible to recover.

I would think (and could be completely wrong), that in the event of an issue, I'd be able to flash the original full OTA sideload package to recover.

chp said:
I would think (and could be completely wrong), that in the event of an issue, I'd be able to flash the original full OTA sideload package to recover.
Click to expand...
Click to collapse
I just wanted to add, I tried flashing a different radio in December after flashing that image before it got pulled, and my phone wouldn't boot (but my bootloader was unlocked so I was able to save it but I wouldn't try it). I suggest you unlock your bootloader and flash 12L on both slots. That's what I did yesterday. Just kind of kill 2 birds with one stone by wiping, reflashing, and using a new build/radio (3 birds I guess?)

Creating a custom OTA won't work. That will break the cert chain and the phone won't validate it and install it.

chp said:
I would think (and could be completely wrong), that in the event of an issue, I'd be able to flash the original full OTA sideload package to recover.
Click to expand...
Click to collapse
It depends on how badly things went wrong. I would hope so, too, but would be a bigger gambler than someone who has the bootloader unlocked in the same situation. But of course, if you had an unlocked bootloader, you could flash only the radio.img without any customization needed. But as @TonikJDK indicates, the question is effectively moot, anyway.

TonikJDK said:
Creating a custom OTA won't work. That will break the cert chain and the phone won't validate it and install it.
Click to expand...
Click to collapse
Interesting. I didn't realize that was in place (signing of the various components such as radio+recovery+bootloader+image), and that the checking was disabled as part of the bootloader being unlocked.

chp said:
and that the checking was disabled as part of the bootloader being unlocked.
Click to expand...
Click to collapse
I could be wrong, but to clarify, the phone still checks the OTA to make sure it's valid even with an unlocked bootloader.
No one * bothers creating a custom OTA to install their ROMs as it would be more trouble than it's worth to do it that way.
What the unlocked bootloader gets us is the ability to install things in other ways than the normal OTA process.
* Other than possibly more fully developed custom ROMs such as GrapheneOS and such might use the normal OTA method since you can re-lock the bootloader once you're on it - I have no first-hand experience with GrapheneOS other than reading their site and what other users have said about it.​

roirraW edor ehT said:
I could be wrong, but to clarify, the phone still checks the OTA to make sure it's valid even with an unlocked bootloader.
No one * bothers creating a custom OTA to install their ROMs as it would be more trouble than it's worth to do it that way.
What the unlocked bootloader gets us is the ability to install things in other ways than the normal OTA process.
* Other than possibly more fully developed custom ROMs such as GrapheneOS and such might use the normal OTA method since you can re-lock the bootloader once you're on it - I have no first-hand experience with GrapheneOS other than reading their site and what other users have said about it.​
Click to expand...
Click to collapse
Ah yes, you're right. I was overthinking it. The sideload OTA does have a cert, so without the private key, we wouldn't be able to create a new cert to match the custom OTA contents.

I also use T-Mobile and was always using the November radio image whilst still updating everything else to the latest release. I was in the same boat as you with the November radio image working so much better than the others. Granted, right now I'm using the 12L beta radio image as it's (thankfully) much better than the others.
But yeah, with an unlocked bootloader you can flash whichever radio image that you want - even if it's from a different release than your current Android build. It won't cause problems if you know what you're doing and only takes a few minutes. Feel free to shoot me a message once your bootloader is unlocked if you need any help with this.

NippleSauce said:
I also use T-Mobile and was always using the November radio image whilst still updating everything else to the latest release. I was in the same boat as you with the November radio image working so much better than the others. Granted, right now I'm using the 12L beta radio image as it's (thankfully) much better than the others.
But yeah, with an unlocked bootloader you can flash whichever radio image that you want - even if it's from a different release than your current Android build. It won't cause problems if you know what you're doing and only takes a few minutes. Feel free to shoot me a message once your bootloader is unlocked if you need any help with this.
Click to expand...
Click to collapse
Thanks. I've been with Android and Pixel/Nexus for a long time, and other than needing to brush up, I'm still familiar with the ins-and-outs to flashing, etc.
My Pixel 6 Pro is carrier locked, and would have to be unlocked before I could unlock the bootloader. I was just hoping to make my Pixel 6 Pro usable again without having to try to get it unlocked.
Since my radio issues started with the January update, I was hoping the February update would fix things. At first it did seem better, but then the poor behavior returned. And when I realized that the radio was unchanged in February from January, that explained things.

chp said:
My Pixel 6 Pro is carrier locked, and would have to be unlocked before I could unlock the bootloader. I was just hoping to make my Pixel 6 Pro usable again without having to try to get it unlocked.
Click to expand...
Click to collapse
I feel ya. That's partially why I started buying my phones from the company that makes them (and also because my phone carrier stopped offering any interesting upgrades after being with them for a few years lol). But supposedly, a quick text chat with a T-Mo representative via the T-Mobile app can get your device carrier unlocked via the SIM card if you're polite with the whole thing and ask the right questions. I'm not sure if anything specific needs to be asked or stated, but you could always give that a shot. I just quickly skimmed through a post from someone who did that the other day but I didn't give it too much thought since my device is factory unlocked.
But I wish you the best of luck with your phone service!