Related
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.
Just ordered a new Nexus 5x a few days ago should be here soon. It'll probably still have Marshmallow on it. Should I only flash custom ROMs. Immediately to avoid bootloop issues u have been hearing about? I'm confused because it seems that the OTA or preview edition was causing this not custom ROMs.
To me, it depends what you want to do with your device.
For me, I downloaded the latest 6.X and flashed manually. Relocked the BL and enrolled in Android beta program. Then let the OTA 7.1.1 come down to upgrade the device so I continue to get updates, including upgrade to production release down the road.
mikeprius said:
Just ordered a new Nexus 5x a few days ago should be here soon. It'll probably still have Marshmallow on it. Should I only flash custom ROMs. Immediately to avoid bootloop issues u have been hearing about? I'm confused because it seems that the OTA or preview edition was causing this not custom ROMs.
Click to expand...
Click to collapse
More signs point to hardware failure rather than the update. I think it was just coincidence that 7.0 came out when phones were getting close to 1 year old. I've been running my replacement from last month on 7.1 beta and it's just fine.
Sent from my Nexus 5X using Tapatalk
Ezekial said:
To me, it depends what you want to do with your device.
For me, I downloaded the latest 6.X and flashed manually. Relocked the BL and enrolled in Android beta program. Then let the OTA 7.1.1 come down to upgrade the device so I continue to get updates, including upgrade to production release down the road.
Click to expand...
Click to collapse
So you have just been flashing new images manually? For me I don't care about the newest version I sill am using Marshmallow on my Nexus 6. I prefer customization so I'm going to unlock, TWRP, custom ROM etc........ I just want to potentially avoid any of the bootloop issues I have been hearing about.
It sounds like there was never a definitive conclusion as to why it was happening only with Nougat
mikeprius said:
So you have just been flashing new images manually? For me I don't care about the newest version I sill am using Marshmallow on my Nexus 6. I prefer customization so I'm going to unlock, TWRP, custom ROM etc........ I just want to potentially avoid any of the bootloop issues I have been hearing about.
It sounds like there was never a definitive conclusion as to why it was happening only with Nougat
Click to expand...
Click to collapse
Gotcha. I have only had my 5x for just over a month so not the most knowledgeable. My take is largely the same as the other guy, failures are from hardware or just bloat from long term use.
I start with the latest 6 and considered staying on it for root, xPosed, etc. I have always ran this way for years. But it is super annoying not having Android pay and a few other things. I sucked it up and decided to try not rooting or even unlocking BL. There are things I miss but I am staying locked down for now. The primary issue I have is for tethering, which I cannot do. The rest I have surprisingly been able to do without.
Flash away
Hey mate, you will not have issues flashing what ever you like, issues are caused by hardware failures ( unavoidable ) or just not following instructions correctly. I flash factory images, beta etc, and custom ROMs. Never have issues. Flash like crazy. It's just a phone and almost all of them can be fixed, if something goes wrong.
P.s. You gotta try the 7.1.1 beta. Its has potential.
I have tried to update my chinese XT1635-03 to 7.1.1 with OTA through ADB sideload and unfortunately it is not working.
I have sucessfully flashed the phone with reteu latest firmware with April security patch (ADDISON_NPNS25.137-24-1-9_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml) through fastboot.
But once I try to sideload 7.1.1 OTA (Blur_Version.26.1.22.addison.retail.en.US) the process terminates at 47% with notification that the package expects product name "addison" but actual value is "addison_retcn"
Is it possible to either change the product name or disable such check of product name? It seems to me, that at the moment there is no way to flash OTA and I need to wait for full 7.1.1 image.
Reading similar questions around, I have to ask. Why you people cannot wait couple of weeks to get OTA? Instead of risking to brick your device?
New update is not bringing revolutionary/awesome/amazing/mind blowing... new features. I understand if it's update to completely new Android version or that your device/region will not get update at all.
Sent from my XT1635-02 using Tapatalk
You have XT1635-03 and the update is for XT1635-02. So if you have a reteu phone you can really update over sideload without issues. And yes, I need android 7.1.1 and I wouldn't wait one day longer. I need app-shortcuts, because I had this on my old phone, too. There was android 7.1 since the first day. But if you don't have it before you can't miss it. So you can wait much easier For me it was important for other issues, too. For example Wifi problems and stability fixes and over 100 security fixes. Many reasons for the update
Edit: And one more reason for the update: To help google to get more than 0.6% for android 7.1 We should update all, otherwise android 7.1 will never get 1%
Everybody should help to get this 1% maybe next month. So update, just do it for the 1%, yes xD
:silly::good:
The reason is simple: I do not want to use chinese firmware and flashed reteu with fastboot. As OTA channel is still retcn I will not get any OTA over the air. I expected that it is possible to manually sideload OTA but I was wrong as OTA checks the name of the device.
freeman_g said:
The reason is simple: I do not want to use chinese firmware and flashed reteu with fastboot. As OTA channel is still retcn I will not get any OTA over the air. I expected that it is possible to manually sideload OTA but I was wrong as OTA checks the name of the device.
Click to expand...
Click to collapse
The point is, how can you change the channel...
freeman_g said:
The reason is simple: I do not want to use chinese firmware and flashed reteu with fastboot. As OTA channel is still retcn I will not get any OTA over the air. I expected that it is possible to manually sideload OTA but I was wrong as OTA checks the name of the device.
Click to expand...
Click to collapse
OK, makes sense for you but for many/most others is just matter of time.
I'm not blaming anyone. Do whatever you want with your phone, just be ready if something goes wrong
The surprise was a different phone name. Different channel is usually not a problem
freeman_g said:
The surprise was a different phone name. Different channel is usually not a problem
Click to expand...
Click to collapse
Flash a custom ROM, I have been warning people not to flash ota's cause eventually your going to end up hard bricked.
There's no possible way safely to change your channel.
Stock firmware that is an ota always has checks during the flashing process, which prevents bricking devices.
I always suggest if your running stock firmware on moto devices then remain on your firmware that is specifically designed for your channel.
If you want the latest that android offers, custom ROMs are your best bet.
I have had many moto devices and almost every brick was so idiot that flashed Firmware and bootloaders and accepted an ota and bam HARD BRICKED
flashallthetime said:
Flash a custom ROM, I have been warning people not to flash ota's cause eventually your going to end up hard bricked.
There's no possible way safely to change your channel.
Stock firmware that is an ota always has checks during the flashing process, which prevents bricking devices.
I always suggest if your running stock firmware on moto devices then remain on your firmware that is specifically designed for your channel.
If you want the latest that android offers, custom ROMs are your best bet.
I have had many moto devices and almost every brick was so idiot that flashed Firmware and bootloaders and accepted an ota and bam HARD BRICKED
Click to expand...
Click to collapse
Oh no, can't go back. What can I do now? But all is working. Can it be that my reteu phone will be bricked after next OTA?
allrightlite said:
Oh no, can't go back. What can I do now? But all is working. Can it be that my reteu phone will be bricked after next OTA?
Click to expand...
Click to collapse
I have no idea
flashallthetime said:
I have no idea
Click to expand...
Click to collapse
Is it ever happend?
But is the US-version not always the same as the EU-version? The only difference is over which channel it comes.
allrightlite said:
Is it ever happend?
But is the US-version not always the same as the EU-version? The only difference is over which channel it comes.
Click to expand...
Click to collapse
If you are not 100% bone stock and unmodified, there is always some risk when accepting an OTA carrier update. On any device. Some the risks are bigger than others. Moto seems to be fairly high risk in this regard.
If you want OTAs, and you want to be safe, don't modify anything. If you insist on mods (which I usually do, but not yet on MZP) then always update via a manual method, never accept an OTA.
dandrumheller said:
If you are not 100% bone stock and unmodified, there is always some risk when accepting an OTA carrier update. On any device. Some the risks are bigger than others. Moto seems to be fairly high risk in this regard.
If you want OTAs, and you want to be safe, don't modify anything. If you insist on mods (which I usually do, but not yet on MZP) then always update via a manual method, never accept an OTA.
Click to expand...
Click to collapse
I have all 100% stock. And all is working after update. Seems there is really no difference between US and EU channel. Can't find any changes. So OTA should work in future. But sure, there are channel with differences, for example the chinese version is not the same.
allrightlite said:
I have all 100% stock. And all is working after update. Seems there is really no difference between US and EU channel. Can't find any changes. So OTA should work in future. But sure, there are channel with differences, for example the chinese version is not the same.
Click to expand...
Click to collapse
If you sideloaded an update, you are no longer 100% bone stock. Welcome to beta tester land.
dandrumheller said:
If you sideloaded an update, you are no longer 100% bone stock. Welcome to beta tester land.
Click to expand...
Click to collapse
It feels not like a beta. It's more like a big bug fix with much patches. For example my Wifi is now stable as hell and never reconnections anymore. Hope it keeps stable, but looks very very good. I think this beta will be the final release in few months, or weeks? But it's much better than 7.0. And better than LOS14.1, which is not so stable (on my other phone). And I have no app crashes anymore. Gboard was crashing with 7.0 one time and few other apps like firewall. So, 7.1.1 is pure stable as hell and must have :laugh:
Afaik, it's not beta. It's soak. So, if test users reported as stable, it will be pushed to all as the final build. If not, Moto has to fixed and not all users around the world will be affected.
Regular and recommend way of releasing update.
Sent from my LG-V940n using Tapatalk
Here you can see that it's not test-keys like a nightly from LOS. It's really release keys :laugh:
If you are on XT1635-03 with reteu frmware you will not receice any OTA. My experience told that you can't even sideload an update. So no worry about bricks.
Very often devices are hardbricked when you are downgrading bootloader but once I have hardbricked my Nexus 6 with OTA (sideloading it). Well, it was not full brick, but I can't load the system (only fastboot) and my bootloader was locked. Without system loaded you can't allow unlocking procedure so the first thing I do with new phone is unlocking.
allrightlite said:
Here you can see that it's not test-keys like a nightly from LOS. It's really release keys :laugh:
Click to expand...
Click to collapse
I know the build is not a beta. I'm referring to the fact that once you leave the official upgrade path, taking any update is a scenario not tested by Moto. So you are testing for them. Maybe you win, maybe you brick.
It seems that the problem with "addison_retcn" may be fixed with editing build.prop but in this case systemless root is required (AFAIK there us no systemless root for Nougat)
Question related to "After updating, you will not be able to downgrade..." message
Hope you guys are safe and well.
Currently my A50 on August update. I have no problems with this update but I like to update to Android 10 for additional features. I'm reluctant to update because of this message. I'm afraid that if I had problems or something wrong with the new update, I won't be able to go downgrade to August update.
So, Is it really impossible to downgrade using Odin with an official firmware?
I'm coming from iOS and hence the fear of updating. As you may know, iOS downgrade is impossible when Apple sign-out the old software.
Thanks in advance.
Most major OS updates (i.e. from Android 9 to 10) also update the 'bootloader', which is a little piece of software that initializes your device, and runs before the system can even start (when you turn your phone on).
Once the bootloader is updated, it's often impossible and certainly not recommended to downgrade the OS, since you may permanently brick your device.
If Android 10 is out for your device model (eg. A505G in my case), just go ahead and update. I don't have any issues with it whatsoever, in fact it has fixed quite a few bugs (wifi connection would frequently drop for me in Pie with February/March updates, and now it doesn't anymore).
Greetings.
pripyaat said:
Most major OS updates (i.e. from Android 9 to 10) also update the 'bootloader', which is a little piece of software that initializes your device, and runs before the system can even start (when you turn your phone on).
Once the bootloader is updated, it's often impossible and certainly not recommended to downgrade the OS, since you may permanently brick your device.
If Android 10 is out for your device model (eg. A505G in my case), just go ahead and update. I don't have any issues with it whatsoever, in fact it has fixed quite a few bugs (wifi connection would frequently drop for me in Pie with February/March updates, and now it doesn't anymore).
Greetings.
Click to expand...
Click to collapse
But can't I backup the boot loader too? Also, I heard that the official firmware includes the boot loader and therefore I won't have problems downgrading. I'm confused.
Screen not responding after update
Hi. I updated to the new Android 10 which my phone prompt me to install. But after updating, my screen is not responding anymore. I already tried to restart and factory reset. What can i do regarding this? Thank you very much!
sheidyly said:
Hi. I updated to the new Android 10 which my phone prompt me to install. But after updating, my screen is not responding anymore. I already tried to restart and factory reset. What can i do regarding this? Thank you very much!
Click to expand...
Click to collapse
Try to flash the ROM manually using ODIN
redymedan said:
Try to flash the ROM manually using ODIN
Click to expand...
Click to collapse
I'm sorry but I'm new to all of this and I seem to read some comments saying the phone was bricked after flashing.
And if I will try flashing, do I use the old firmware or the new one?
Thank you so much!
mistpsn said:
But can't I backup the boot loader too? Also, I heard that the official firmware includes the boot loader and therefore I won't have problems downgrading. I'm confused.
Click to expand...
Click to collapse
I think... and I could be completely wrong, but it keeps track of the highest version of bootloader you installed. So it will not allow you to boot if you flash the older one. However, I am not sure how it behaves if the bootloader is unlocked.
If anyone have the same concerns I had. I found out that only security updates seems to have this message and risk bricking your phone in case you downgrade to lower version. Some people confirms that they were able to downgrade without any problems from android 10 to android 9 on their A50.
It also made sense that there are no problems since the warning message only included with security updates. The android 10 Update change list have no warnings related to downgrading to older versions.
March security update had the warning message. And I had to do the security upgrade before the android 10 update was available OTA.
Hi guys, I just bought a brand new note 10+ N975W (canada version). I'm on stock firmware. It keep asking me to update. Shall I update? which version is best to keep the battery last as long as possible?
Also, can i downgrade to previous versions or stock if i dont like the upgraded firmware?
Yes update. It's probably just security updates at this point, so there would be no reason to go back. The Note 10 firmware is fairly mature by now.
chances are if you bought it recently it is already an updated firmware unless the store is running really old stock, as they tend to produce the devices with the latest firmware at the time of manufacture. basically you would need to find a phone that was manufactured before any updates to get the original stock firmware.
chances are any phone produced this year likely has Android 10 pre installed instead of Android 9 and a much more recent security patch, so in that case you may as well update the phone as it is already updated to an extent.
as for downgrading to an actual launch firmware it's not possible as every so often they make a change that can't be reversed so it stops you going to an older firmware (I know it happend with both Android 10 and the One UI update, there are likely more points)
but in terms of battery use, everyone's numbers will differ no matter the firmware as a lot of it comes down to settings, what its used for and the environment it is ran in.
Belimawr said:
chances are if you bought it recently it is already an updated firmware unless the store is running really old stock, as they tend to produce the devices with the latest firmware at the time of manufacture. basically you would need to find a phone that was manufactured before any updates to get the original stock firmware.
chances are any phone produced this year likely has Android 10 pre installed instead of Android 9 and a much more recent security patch, so in that case you may as well update the phone as it is already updated to an extent.
as for downgrading to an actual launch firmware it's not possible as every so often they make a change that can't be reversed so it stops you going to an older firmware (I know it happend with both Android 10 and the One UI update, there are likely more points)
but in terms of battery use, everyone's numbers will differ no matter the firmware as a lot of it comes down to settings, what its used for and the environment it is ran in.
Click to expand...
Click to collapse
my phone is still running on android 9.0.
aznboix said:
my phone is still running on android 9.0.
Click to expand...
Click to collapse
Since the phone is new. Before getting to far into configuration, run the update, then do a factory reset. It'll do a fresh install of Android 10 and any security updates.
That will give you a nice clean install you can then setup.
Sent from my SM-N976V using Tapatalk
You should always update. They are mostly Security Updates, these are for security reasons (Hence the name ). Yeah there are some system modifications and enhancements too but the main reason is to ensure the device is as secure as possible
Is there a custom firmware that works perfectly?
can i root my device?
can i flash to another firmware? Asia firmware for exemple
what are the apps that i can't miss on note 10+?
which firmware that has vietnamese language?
thanks