Hi,
i'm currently on firmware 51.1.3.0 and i got my FT just lying around here and want to use it.
So my question is, should i upgrade to the latest firmware and just use it or be patient until a root for my version is released because of the efuse stuff?
Is anyone working on a new root method atm?
Raptor270 said:
Hi,
i'm currently on firmware 51.1.3.0 and i got my FT just lying around here and want to use it.
So my question is, should i upgrade to the latest firmware and just use it or be patient until a root for my version is released because of the efuse stuff?
Is anyone working on a new root method atm?
Click to expand...
Click to collapse
I doubt anyone is working on rooting newer firmware, cause they already have their firmware rooted so I doubt they have interest in rooting the newer firmware. Not trying to speak for any devs that have worked on these devices, but that seems to be the way it goes, they have already accomplished their goal of rooting the device so if newer unrootable firmware gets released its not really a problem for them. I am predicting right now that unless a new firmware with major updates gets released that requires you to have stock firmware to update then no newer firmwares will ever get root. I could be wrong, but I doubt it so its really up to you.
porkenhimer said:
I doubt anyone is working on rooting newer firmware ...
Click to expand...
Click to collapse
I have no doubt somebody is working on it. These are self-challenged, self-motivated people. And Amazon threw down the gauntlet.
As to Raptor's first question, you have it. Why not use it?
cant block updates on my router and dont want to update past the fuse update... -.-
Related
New firmware T700ZSU1ANL1 and T800ZSU1ANL1 (Hong Kong both).*
Can i install these in europeans tablets?
Thanks
Any ideas?
I have installed it on the US WiFi only version, so I don't see it being a problem, if it doesn't install you can always Odin back to your stock rom... if you have a 3/4g type tablet then you may want to not flash it..... I'm digging the new kernel personally.
Itchiee said:
I have installed it on the US WiFi only version, so I don't see it being a problem, if it doesn't install you can always Odin back to your stock rom... if you have a 3/4g type tablet then you may want to not flash it..... I'm digging the new kernel personally.
Click to expand...
Click to collapse
Thanks
I have installed it in european firmware, portuguese one to be exact (FNAB), no issues at all.
Zootopia said:
I have installed it in european firmware, portuguese one to be exact (FNAB), no issues at all.
Click to expand...
Click to collapse
I installed, thanks, no issues.
Tavocampana said:
I installed, thanks, no issues.
Click to expand...
Click to collapse
Can anyone confirm that flashing update from a different region manually via Odin on an unrooted device will have exactly the same result as if it was an official OTA update (apart maybe from overwriting /data).
So there should be no problem getting OTA Lollipop when it eventually arrives? And apps which check if device is rooted like the banking and TV ones(Barclays, Sky Go etc) should be seeing 100% official unrooted OS?
Restorer said:
Can anyone confirm that flashing update from a different region manually via Odin on an unrooted device will have exactly the same result as if it was an official OTA update (apart maybe from overwriting /data).
So there should be no problem getting OTA Lollipop when it eventually arrives? And apps which check if device is rooted like the banking and TV ones(Barclays, Sky Go etc) should be seeing 100% official unrooted OS?
Click to expand...
Click to collapse
Theres an app calplled root cloak to hide root from apps. I dont really care on being on stock rom just to get ota lollipop. There would most liekly be a custom rooted lollipop rom when lollipop is out.
DUHAsianSKILLZ said:
Theres an app calped root cloak to hide root from apps. I dont really care on being on stock rom just to get ota lollipop. There would most liekly be a custom rooted lollipop rom when lollipop is out.
Click to expand...
Click to collapse
Unfortunately none of the cloaking apps work on Sky Go or Barclays and other banking apps. Neither does RootCloak or RootCloak Plus Xposed mods .
That is why I asked the question. Not really bothered if it just means losing OTAs - provided everything else is still 100% official unrooted after Odin upgrade of UK tab with HK firmware. That's why I ask will this be the case?
Restorer said:
Can anyone confirm that flashing update from a different region manually via Odin on an unrooted device will have exactly the same result as if it was an official OTA update (apart maybe from overwriting /data).
So there should be no problem getting OTA Lollipop when it eventually arrives? And apps which check if device is rooted like the banking and TV ones(Barclays, Sky Go etc) should be seeing 100% official unrooted OS?
Click to expand...
Click to collapse
I do not know.
My intention when the Lollipop version is released is to repeat the procedure and flash via Odin. I live in Argentina and here things come too late.
Tavocampana said:
I do not know.
My intention when the Lollipop version is released is to repeat the procedure and flash via Odin. I live in Argentina and here things come too late.
Click to expand...
Click to collapse
Yeah, I'd do that too. But these apps are too important to me to risk losing them so I will probably just chicken out and wait for the OTA. Thing is, if the update works, I can't see any reason why the root-checking apps would be able to tell except if they were spotting non-UK codes. I do know their checks are a lot more sophisticated than looking only for the presence of SU and busybox. They for sure examine parts of the kernel and the DRM files as well.
My logic tells me that if the apps don't work with the HK firmware then all I need do is to flash back to the official UK XXU1 version. That's why I am just asking is anyone knows of any other differences that might be exposed using the Odin method to update?
Hello
Apologies if this has been covered before, but couldn't find anything in search.
I'm setting up a new UK unit which is currently running 51.1.4.0_user_514005520. Can I update to 51.1.4.0_user_514006420 (1 version up) without root? That's the version that fixes kodi/spmc launch crash. I'm thinking maybe there is a dir I can copy the update to and reboot the device. But, even then, I would hazard a guess that you need root to copy it there :/
This is my first experience with a unrooted box since US launch (I imported one and rooted from the start) so not sure if this is possible to do. I want to avoid updating to the latest firmware if I can.
Thanks!
eskay993 said:
Hello
Apologies if this has been covered before, but couldn't find anything in search.
I'm setting up a new UK unit which is currently running 51.1.4.0_user_514005520. Can I update to 51.1.4.0_user_514006420 (1 version up) without root? That's the version that fixes kodi/spmc launch crash. I'm thinking maybe there is a dir I can copy the update to and reboot the device. But, even then, I would hazard a guess that you need root to copy it there :/
This is my first experience with a unrooted box since US launch (I imported one and rooted from the start) so not sure if this is possible to do. I want to avoid updating to the latest firmware if I can.
Thanks!
Click to expand...
Click to collapse
Never mind. I think I found the answer. Remembered an old guide on aftnews. Guess you do need root.
http://www.aftvnews.com/how-to-manually-upgrade-or-downgrade-the-amazon-fire-tv/
I've gotten hold of an Amazon Fire TV that was already rooted, but has a very old Stock Rom on it.
It currently has software version: 51.1.0.1_
The newer versions of the the custom ROMS state don't install unless you have had version 51.1.4.0 and you just can't skip to it.
Can I install version 51.1.4.0_514006420? without any issues since my stock FW appears to be old. It doesn't list any pre-requisites on the page so I assume that it safe, but just want to make sure. Then after I install that firmware I should be able to load the latest, correct?
Does anyone have a link to a tutorial to updating the rooted firmware before the BOOT Menu requirement, or is the procedure essentially still the same?
Thanks for the advice!
Alvisaar said:
I've gotten hold of an Amazon Fire TV that was already rooted, but has a very old Stock Rom on it.
It currently has software version: 51.1.0.1_
The newer versions of the the custom ROMS state don't install unless you have had version 51.1.4.0 and you just can't skip to it.
Can I install version 51.1.4.0_514006420? without any issues since my stock FW appears to be old. It doesn't list any pre-requisites on the page so I assume that it safe, but just want to make sure. Then after I install that firmware I should be able to load the latest, correct?
Does anyone have a link to a tutorial to updating the rooted firmware before the BOOT Menu requirement, or is the procedure essentially still the same?
Thanks for the advice!
Click to expand...
Click to collapse
Read, read and re-read before you start installing anything or you will be regretting it .
start here:
http://www.aftvnews.com/start/
Alvisaar said:
I've gotten hold of an Amazon Fire TV that was already rooted, but has a very old Stock Rom on it.
It currently has software version: 51.1.0.1_
The newer versions of the the custom ROMS state don't install unless you have had version 51.1.4.0 and you just can't skip to it.
Can I install version 51.1.4.0_514006420? without any issues since my stock FW appears to be old. It doesn't list any pre-requisites on the page so I assume that it safe, but just want to make sure. Then after I install that firmware I should be able to load the latest, correct?
Does anyone have a link to a tutorial to updating the rooted firmware before the BOOT Menu requirement, or is the procedure essentially still the same?
Thanks for the advice!
Click to expand...
Click to collapse
Honestly as nice and sweet as the amazon fire is.. I don't think it is a "long term" solution for cheap android to home setups.. because as long as it remained locked like that (and we can't work around it) it's not a long-term solution.. (just cause you could root your device doesn't mean that it won't break.. and your root is gone )I've been following the development of phone hardware for hdtv's for a long time.. (stupid SMARTtv's suck what a waste of hardware!) the reason why I bought amazon fire is because all the other products out there.. (and there's plenty!)
Many have had over-heating issues.. and that's one thing that makes amazon's nice.. nice remote, no over-heating! (low price) So I wouldn't bank on it being around.. if people want stock android.. and I would have preferred that as well..
And now intel is selling a windows 8.1 stick with a additional usb port for storage.. hdmi version.. it's pricey at $150.. but maybe when it's $50.. it'll be worth it?
So I do think we should see lots more refinements on this technology.. and amazon's the only one who delivered a full usable product with decent spec's.. though I hear roku is much more "stable" in the apps department.. and now finally making one that has more then 512 mb ram..
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)
Samsung just put out a new update and the oreo rooting method listed on here fails at odin. Im wanting to root because i found some interesting things in the phone info app under secret codes. one of them was unlock kernel and a few others i wanted to check out but it seems its blocked so i need root to bypass the block. anyone know of how root can be achieved in this new update? THANKS
bjf189 said:
Samsung just put out a new update and the oreo rooting method listed on here fails at odin. Im wanting to root because i found some interesting things in the phone info app under secret codes. one of them was unlock kernel and a few others i wanted to check out but it seems its blocked so i need root to bypass the block. anyone know of how root can be achieved in this new update? THANKS
Click to expand...
Click to collapse
They blocked root on that update so you are now stuck on a non rootable device. Sorry
stang5litre said:
They blocked root on that update so you are now stuck on a non rootable device. Sorry
Click to expand...
Click to collapse
It's fine. I was gonna be rooted only for a short time just to check those things out. It sucks not having root but I'd rather not deal with the lag from the boot image if it worked on this update that is. Maybe someone will crack this update in time cause nothings unhackable.
So is downgrading possible still or does this update block downgrading to? I haven't tried yet but if you have then save me some time
bjf189 said:
It's fine. I was gonna be rooted only for a short time just to check those things out. It sucks not having root but I'd rather not deal with the lag from the boot image if it worked on this update that is. Maybe someone will crack this update in time cause nothings unhackable.
So is downgrading possible still or does this update block downgrading to? I haven't tried yet but if you have then save me some time
Click to expand...
Click to collapse
Yes, blocks downgrading, but you should be able to flash any other updated carrier firmware and the U version
stang5litre said:
They blocked root on that update so you are now stuck on a non rootable device. Sorry
Click to expand...
Click to collapse
lvpre said:
Yes, blocks downgrading, but you should be able to flash any other updated carrier firmware and the U version
Click to expand...
Click to collapse
What difference would it make flashing other carrier firmware over this one?
bjf189 said:
What difference would it make flashing other carrier firmware over this one?
Click to expand...
Click to collapse
The U firmware would remove the Verizon bloatware. For example, if you left Verizon and went to T-Mobile...the U firmware of T-Mobile firmware could be installed to get the full bands for LTE coverage available. But if you are on Verizon and happy, probably not worth the trouble.