Basically forgot that I'd unlocked the bootloader and allowed the update, pretty stupid
Pretty sure that the next step from here is to flash the stock firmware, unless I'm mistaken?
Looking for any firmware for the XT1922-2 JETER model, which I think is an exclusively UK thing. Haven't been able to find any thus far which is both Jeter and XT1922-2, so would be intensely grateful if someone could help me!
Craventoby said:
Basically forgot that I'd unlocked the bootloader and allowed the update, pretty stupid
Pretty sure that the next step from here is to flash the stock firmware, unless I'm mistaken?
Looking for any firmware for the XT1922-2 JETER model, which I think is an exclusively UK thing. Haven't been able to find any thus far which is both Jeter and XT1922-2, so would be intensely grateful if someone could help me!
Click to expand...
Click to collapse
Yes just reflash latest stock firmware and you'll be good and what's your sw channel version? Like does it say reteu or something like that. There alot of models under the xt11922-2 device number.
ninjakira said:
Yes just reflash latest stock firmware and you'll be good and what's your sw channel version? Like does it say reteu or something like that. There alot of models under the xt11922-2 device number.
Click to expand...
Click to collapse
Unfortunately I've already tried flashing a few different firmware versions without success, so it just says the most recent version of that. Are there any models under the XT1922-2 called Jeter? I haven't been able to find any.
Craventoby said:
Unfortunately I've already tried flashing a few different firmware versions without success, so it just says the most recent version of that. Are there any models under the XT1922-2 called Jeter? I haven't been able to find any.
Click to expand...
Click to collapse
That's not Jeter. It's Aljeter. There's a bunch with that model number. But helps if know your original software channel.
madbat99 said:
That's not Jeter. It's Aljeter. There's a bunch with that model number. But helps if know your original software channel.
Click to expand...
Click to collapse
I dunno what to tell you, it says Jeter on the bootloader screen. Will have another go at flashing Aljeter software, but hasn't worked so far.
Craventoby said:
I dunno what to tell you, it says Jeter on the bootloader screen. Will have another go at flashing Aljeter software, but hasn't worked so far.
Click to expand...
Click to collapse
Some say Jeter in one line of props, then Aljeter in another. I know it's stupid. But all the ones with your model number (that I have seen anyways) are Aljeter. I could be wrong. But I don't think there is a Jeter with 3 GB of RAM
ninjakira said:
Yes just reflash latest stock firmware and you'll be good and what's your sw channel version? Like does it say reteu or something like that. There alot of models under the xt11922-2 device number.
Click to expand...
Click to collapse
Having some trouble, I get error messages when I try and flash both gpt.bin and bootloader.img - for both I get an error saying that the image failed validation/ preflash validation/ remote failure. Is there something I'm not doing?
Craventoby said:
Having some trouble, I get error messages when I try and flash both gpt.bin and bootloader.img - for both I get an error saying that the image failed validation/ preflash validation/ remote failure. Is there something I'm not doing?
Click to expand...
Click to collapse
You're likely trying to downgrade or have a locked bootloader, or both.
Craventoby said:
Having some trouble, I get error messages when I try and flash both gpt.bin and bootloader.img - for both I get an error saying that the image failed validation/ preflash validation/ remote failure. Is there something I'm not doing?
Click to expand...
Click to collapse
You can't downgrade if the gpt.bin has been updated which it has. Use the latest most recent firmware and everything should be fine. If the latest firmware has not been uploaded then I'm sorry to say your stuck with a bricked phone until the latest firmware is uploaded. Keep checking the link with the firmwares untill you see the latest one
ninjakira said:
You can't downgrade if the gpt.bin has been updated which it has. Use the latest most recent firmware and everything should be fine. If the latest firmware has not been uploaded then I'm sorry to say your stuck with a bricked phone until the latest firmware is uploaded. Keep checking the link with the firmwares untill you see the latest one
Click to expand...
Click to collapse
Actually, after trying the whole thing over a second time, flashing each command line by line, my phone is fixed. Have no idea how if what you're saying about it being impossible to downgrade is right, but certainly not complaining. In the end, the RETGB software for ALJETER was the one that worked.
Craventoby said:
Actually, after trying the whole thing over a second time, flashing each command line by line, my phone is fixed. Have no idea how if what you're saying about it being impossible to downgrade is right, but certainly not complaining. In the end, the RETGB software for ALJETER was the one that worked.
Click to expand...
Click to collapse
Hey as long as my guide helped you that all I care about In the end lol the biggest common issue most people have is not paying attention to the command lines lol. Glad your able to enjoy your phone. And it sounds exactly it sounds once the gpt.bin is updated you can't use a older firmware which in turn would be downgrading.
lol am I the only one who's been taking updates with unlocked bootloader having no problems?
blowingoff said:
lol am I the only one who's been taking updates with unlocked bootloader having no problems?
Click to expand...
Click to collapse
it seems the problem people are having is after they have already rooted their devices they're trying to take an ota update. Which you can't do. Having an unlocked bootloader doesn't affect that. the reason is because the stock recovery has been replaced by twrp. In order to install an ota update when your phone is rooted you must reflash either the stock firmware of the current version you're on or just flash the new stock firmware. Or in this case accidentally using the command lines wrong lol
ninjakira said:
it seems the problem people are having is after they have already rooted their devices they're trying to take an ota update. Which you can't do. Having an unlocked bootloader doesn't affect that. the reason is because the stock recovery has been replaced by twrp. In order to install an ota update when your phone is rooted you must reflash either the stock firmware of the current version you're on or just flash the new stock firmware. Or in this case accidentally using the command lines wrong lol
Click to expand...
Click to collapse
yes, just what I thought. unlocked bootloader doesnt change anyrhing, but having the phone system modified may do
ninjakira said:
it seems the problem people are having is after they have already rooted their devices they're trying to take an ota update. Which you can't do. Having an unlocked bootloader doesn't affect that. the reason is because the stock recovery has been replaced by twrp. In order to install an ota update when your phone is rooted you must reflash either the stock firmware of the current version you're on or just flash the new stock firmware. Or in this case accidentally using the command lines wrong lol
Click to expand...
Click to collapse
Also, people confusing 2 different issues regarding updates.
The only REAL issue I've heard is, after flashing firmware on an unlocked bootloader, they are no longer receiving OTA updates. Maybe changed their update channel or something.
madbat99 said:
Also, people confusing 2 different issues regarding updates.
The only REAL issue I've heard is, after flashing firmware on an unlocked bootloader, they are no longer receiving OTA updates. Maybe changed their update channel or something.
Click to expand...
Click to collapse
Yea that's why I've been starting to ask for sw channel version ? its been alot more helpful knowing that before anything lol. I haven't had any issue flashing stock firmware then taking an ota update its how I was able to take the latest security patch update as well as the other updates before they were uploaded on the firmware site ( I hate saying mirrors.lolinet because well darkweb has sites called that also unfortunately and there just not good lol) but that's just me lol
Related
I just picked up a new g4 At&t. Pretty awesome phone. I would like to root it, But from what I can see I can only flash a "prerooted" stock image. Seems simple enough. But it looks like the only images that are out for the h810 are for h81010x software.
The software that is on my phone shows ip as H81009e
I assume that H81010a would be the newer software after OTA's. However I cannot update mine because I am using it unlocked on T-Mobile.
From what I read I can manually update using a stock KDZ or most likely a TOT file for at&t.
My question would be, Is it safe to flash the H81010a KDZ over my H1009e software?
I am new to LG and the info im finding out there is very contradictory and I couldn't find any info on h81009e.
If I am way off with what I am thinking. then please enlighten me.
Thanks.
( I did post this on the low effort root thread with no response)
Please let me know. If I can't root it. Then I will back to HTC. Just wanting to try something new.
myphonesbetter said:
I just picked up a new g4 At&t. Pretty awesome phone. I would like to root it, But from what I can see I can only flash a "prerooted" stock image. Seems simple enough. But it looks like the only images that are out for the h810 are for h81010x software.
The software that is on my phone shows ip as H81009e
I assume that H81010a would be the newer software after OTA's. However I cannot update mine because I am using it unlocked on T-Mobile.
From what I read I can manually update using a stock KDZ or most likely a TOT file for at&t.
My question would be, Is it safe to flash the H81010a KDZ over my H1009e software?
I am new to LG and the info im finding out there is very contradictory and I couldn't find any info on h81009e.
If I am way off with what I am thinking. then please enlighten me.
Thanks.
( I did post this on the low effort root thread with no response)
Please let me know. If I can't root it. Then I will back to HTC. Just wanting to try something new.
Click to expand...
Click to collapse
Never heard of v09e, so far as i know an earlier version of att is 10b..if its really an att device than it should be ok flashing 10o kdz but you will be in qfuse 2, that mean you'll loose an opportunity to unlock bootloader(if it happened)
faizalotai said:
Never heard of v09e, so far as i know an earlier version of att is 10b..if its really an att device than it should be ok flashing 10o kdz but you will be in qfuse 2, that mean you'll loose an opportunity to unlock bootloader(if it happened)
Click to expand...
Click to collapse
Now I'm even more confused. Its defiantly att. It has all the software and the leather back has an att logo.
So what your saying is by flashing to 10a, I would also be updating my boot loader.
Are you saying that as it sits. I may have a boot loader capable of being unlocked.
I did a quick search for qfuse but I don't know what you mean by I'll be in qfuze2.
Is there a way to check that info on my phone. Or check which bootloader I have.
Sorry for being a noob. This is my fist non htc phone in a while.
myphonesbetter said:
Now I'm even more confused. Its defiantly att. It has all the software and the leather back has an att logo.
So what your saying is by flashing to 10a, I would also be updating my boot loader.
Are you saying that as it sits. I may have a boot loader capable of being unlocked.
I did a quick search for qfuse but I don't know what you mean by I'll be in qfuze2.
Is there a way to check that info on my phone. Or check which bootloader I have.
Sorry for being a noob. This is my fist non htc phone in a while.
Click to expand...
Click to collapse
If your software version already in qfuse 2, there's no problem to flash tot file because either way you cannot unlocked bootloader anymore(as they're saying its for qfuse 0, yet it still doesn't available) but i doubt about your sw version..
can you screenshot software version in about phone
81010o
myphonesbetter said:
I just picked up a new g4 At&t. Pretty awesome phone. I would like to root it, But from what I can see I can only flash a "prerooted" stock image. Seems simple enough. But it looks like the only images that are out for the h810 are for h81010x software.
The software that is on my phone shows ip as H81009e
I assume that H81010a would be the newer software after OTA's. However I cannot update mine because I am using it unlocked on T-Mobile.
From what I read I can manually update using a stock KDZ or most likely a TOT file for at&t.
My question would be, Is it safe to flash the H81010a KDZ over my H1009e software?
I am new to LG and the info im finding out there is very contradictory and I couldn't find any info on h81009e.
If I am way off with what I am thinking. then please enlighten me.
Thanks.
( I did post this on the low effort root thread with no response)
Please let me know. If I can't root it. Then I will back to HTC. Just wanting to try something new.
Click to expand...
Click to collapse
Honestly your better trying to update to 81010o as it has alot of improvements in my opinion and is rootable although u will kinda have to dig through the forums to find the img
faizalotai said:
If your software version already in qfuse 2, there's no problem to flash tot file because either way you cannot unlocked bootloader anymore(as they're saying its for qfuse 0, yet it still doesn't available) but i doubt about your sw version..
can you screenshot software version in about phone
Click to expand...
Click to collapse
Under settings>about phone>software>software version It just says H81009e. under the battery it says h810.
I can post a pic if you want but I cant remember any passwords for hosting sites right now.
So how do I know which qfuse I am in? Does the qfuse only change once you update the phone?
dsilx said:
Honestly your better trying to update to 81010o as it has alot of improvements in my opinion and is rootable although u will kinda have to dig through the forums to find the img
Click to expand...
Click to collapse
Ok. is 10o a newer update than a&b? This phone does have some bugs.
I want to make sure I cant unlock my bootloader first. But i cant find any good info.
81010o
myphonesbetter said:
Under settings>about phone>software>software version It just says H81009e. under the battery it says h810.
I can post a pic if you want but I cant remember any passwords for hosting sites right now.
So how do I know which qfuse I am in? Does the qfuse only change once you update the phone?
Ok. is 10o a newer update than a&b? This phone does have some bugs.
I want to make sure I cant unlock my bootloader first. But i cant find any good info.
Click to expand...
Click to collapse
H81010o is the newest firmware for the Att varient but its not bootloader unlockable
To see your updates look in the about phone or try LG suite
dsilx said:
H81010o is the newest firmware for the Att varient but its not bootloader unlockable
To see your updates look in the about phone or try LG suite
Click to expand...
Click to collapse
I can't see the updates because I'm using the att phone on t mobile service.
Maybe if I connect to some Wi-Fi.
I will update manually as soon as I know if I can unlock my current bootloader.
myphonesbetter said:
I can't see the updates because I'm using the att phone on t mobile service.
Maybe if I connect to some Wi-Fi.
I will update manually as soon as I know if I can unlock my current bootloader.
Click to expand...
Click to collapse
To check qfuse dial *#*#244773825625#*#* - check your antirollback version(scroll down)
some info about bootloader thing
http://forum.xda-developers.com/showpost.php?p=63816757&postcount=2
for updates via ota att sim is required but you can flash tot file as its now in latest version
http://forum.xda-developers.com/att-g4/general/att-h810-to-stock-guide-tot-method-t3248532
dsilx said:
H81010o is the newest firmware for the Att varient but its not bootloader unlockable
To see your updates look in the about phone or try LG suite
Click to expand...
Click to collapse
faizalotai said:
To check qfuse dial *#*#244773825625#*#* - check your antirollback version(scroll down)
some info about bootloader thing
http://forum.xda-developers.com/showpost.php?p=63816757&postcount=2
for updates via ota att sim is required but you can flash tot file as its now in latest version
http://forum.xda-developers.com/att-g4/general/att-h810-to-stock-guide-tot-method-t3248532
Click to expand...
Click to collapse
Awsome info. Thank you.
However. In that sub menu there is no antirollback version. There is a sub sw version. Which is 0.
And sepolicy version: should be implemented.
Actually here's what's in the menu.
Sw version info
Sub sw version info
Ap app version
Firmware version
Baseband version
Kernel version
Hw version
Factory version.
Speed bin
We original version
Sepolicy version.
myphonesbetter said:
Awsome info. Thank you.
However. In that sub menu there is no antirollback version. There is a sub sw version. Which is 0.
And sepolicy version: should be implemented.
Actually here's what's in the menu.
Sw version info
Sub sw version info
Ap app version
Firmware version
Baseband version
Kernel version
Hw version
Factory version.
Speed bin
We original version
Sepolicy version.
Click to expand...
Click to collapse
So you have no antirollback, thats mean you're in qfuse 0..and i guess you're the one that came with an earlier version of att sw..
Depend on you whether you want update or not as your bootloader can be unlock(if you really,really, really wanted custom kernel or rom)..lol
Maybe @autoprimecan clear things out
faizalotai said:
So you have no antirollback, thats mean you're in qfuse 0..and i guess you're the one that came with an earlier version of att sw..
Depend on you whether you want update or not as your bootloader can be unlock(if you really,really, really wanted custom kernel or rom)..lol
Maybe @autoprimecan clear things out
Click to expand...
Click to collapse
Ok. Thats pretty awesome.
Of course, that opens up so many more questions. Especially since all the tutorials say it only works with t-mobile and a euro model.
I was honestly planning on stripping down the stock version. But if i can actually install a recovery and flash roms. That would be great.
I guess the problem would be all the custom roms are made for either t-mobile or h815.
Would it be safe to flash a t-mobile rom on my phone if the bootloader is unlocked?
That would be awesome considering im using t-mobiles service. Maybe i can get tethering to work.
I know ive used European roms on my phones for quite some time. But those were usually htc devices, Never a LG
I've been searching high and low for a full nougat firmware package for the RETUS model... and i cant find one. Has anyone else found one?
I know there are OTAs out there, I'm looking for an FXZ that can be used with fastboot.
filefactory, mirrors.lolinet, etc... seem to have most 7.0 firmware packages EXCEPT for RETUS which only have 6.0 packages.
I have not seen a release for RETUS as of yet... did you not make a nandroid of your original stock before you started flashing...?
If not, flash the 6.0 and the updates found here on XDA.
Jimi Mack said:
I have not seen a release for RETUS as of yet... did you not make a nandroid of your original stock before you started flashing...?
If not, flash the 6.0 and the updates found here on XDA.
Click to expand...
Click to collapse
I haven't unlocked or flashed anything yet... I wanted to try and find an up to date firmware package to have on hand before I start flashing anything.
Do you know if there would be an issue with using the latest 7.0 RETAIL firmware package on my RETUS device?
https://mirrors.lolinet.com/firmware/moto/addison/official/RETAIL/
I'm still trying to wade through all these posts about firmware packages and the lost imei issues.
FanDroid09 said:
I haven't unlocked or flashed anything yet... I wanted to try and find an up to date firmware package to have on hand before I start flashing anything.
Do you know if there would be an issue with using the latest 7.0 RETAIL firmware package on my RETUS device?
https://mirrors.lolinet.com/firmware/moto/addison/official/RETAIL/
I'm still trying to wade through all these posts about firmware packages and the lost imei issues.
Click to expand...
Click to collapse
Sorry to bump this thread, but I tried to root my 7.0 retus yesterday and it is now bootlooping and not working pretty much at all. I am having the same problem with being unable to find stock 7.0 retus fastboot firmware. Did you ever find a solution? Did you just install the retail version, or did you find a fastboot file?
chris23445 said:
Sorry to bump this thread, but I tried to root my 7.0 retus yesterday and it is now bootlooping and not working pretty much at all. I am having the same problem with being unable to find stock 7.0 retus fastboot firmware. Did you ever find a solution? Did you just install the retail version, or did you find a fastboot file?
Click to expand...
Click to collapse
What did you do to root? Unlock bootloader then what?
chris23445 said:
Sorry to bump this thread, but I tried to root my 7.0 retus yesterday and it is now bootlooping and not working pretty much at all. I am having the same problem with being unable to find stock 7.0 retus fastboot firmware. Did you ever find a solution? Did you just install the retail version, or did you find a fastboot file?
Click to expand...
Click to collapse
Unfortunately I was never able to find a Retus firmware package. However I did flash the Retail firmware package from this thread:
https://forum.xda-developers.com/moto-z-play/how-to/downgrade-7-1-1-soak-test-to-7-0-t3646807
If you follow that guide you should be fine. Worked good for me.
BTW
Nice I See Stars avatar. :good:
Listened to New Demons on repeat when it came out back in the day haha.
EspElement said:
What did you do to root? Unlock bootloader then what?
Click to expand...
Click to collapse
So I am on Retus and upgraded to April patch. Then I unlocked bootloader (successfully), flashed newest TWRP (successfully), flashed the f2fs patch kernel for 7.0 (successfully), then finally Magisk's newest stable (successfully). Phone booted up fine. I went into settings and tried to factory reset, and when the phone rebooted it went to recovery and then now it just doesn't ever boot. It just bootloops. No idea why that is happening.
I found a thread that has steps to downgrade to MM (without flashing bootloader or modem or things that would possibly hard brick) and then after the downgrade I can sideload the Nougat update.
I've seen a lot of people saying if you downgrade after April patch you may hard brick your device, which I am definitely trying to avoid. So if you have any other ideas or if you think what I'm doing is fine, any advice is appreciated!
---------- Post added at 09:14 AM ---------- Previous post was at 09:12 AM ----------
FanDroid09 said:
Unfortunately I was never able to find a Retus firmware package. However I did flash the Retail firmware package from this thread:
https://forum.xda-developers.com/moto-z-play/how-to/downgrade-7-1-1-soak-test-to-7-0-t3646807
If you follow that guide you should be fine. Worked good for me.
BTW
Nice I See Stars avatar. :good:
Listened to New Demons on repeat when it came out back in the day haha.
Click to expand...
Click to collapse
I might try that instead of taking the risk of downgrading. This seems to be much better. Do you know if I would still get OTAs going this route?
Nice!! Never found anyone else on here that likes that music. I've seen them live and met them twice, they are amazing.
Does anyone know where to get the latest either RETAIL or RETUS stock firmware with the May 1st security update? NPN25.137-24.4
chris23445 said:
So I am on Retus and upgraded to April patch. Then I unlocked bootloader (successfully), flashed newest TWRP (successfully), flashed the f2fs patch kernel for 7.0 (successfully), then finally Magisk's newest stable (successfully). Phone booted up fine. I went into settings and tried to factory reset, and when the phone rebooted it went to recovery and then now it just doesn't ever boot. It just bootloops. No idea why that is happening.
I found a thread that has steps to downgrade to MM (without flashing bootloader or modem or things that would possibly hard brick) and then after the downgrade I can sideload the Nougat update.
I've seen a lot of people saying if you downgrade after April patch you may hard brick your device, which I am definitely trying to avoid. So if you have any other ideas or if you think what I'm doing is fine, any advice is appreciated!
---------- Post added at 09:14 AM ---------- Previous post was at 09:12 AM ----------
I might try that instead of taking the risk of downgrading. This seems to be much better. Do you know if I would still get OTAs going this route?
Nice!! Never found anyone else on here that likes that music. I've seen them live and met them twice, they are amazing.
Click to expand...
Click to collapse
Do not side load android N!! You will brick.
Do as the person said here. Flash the N from the forms without .gpt and bootloader
EspElement said:
Do not side load android N!! You will brick.
Do as the person said here. Flash the N from the forms without .gpt and bootloader
Click to expand...
Click to collapse
Yep, I did exactly as that thread said and everything has been working great so far! Thank you both for the help, it is greatly appreciated. I was up until almost 3 AM last night trying to fix it.
chris23445 said:
Yep, I did exactly as that thread said and everything has been working great so far! Thank you both for the help, it is greatly appreciated. I was up until almost 3 AM last night trying to fix it.
Click to expand...
Click to collapse
Is it worth after all?
chris23445 said:
Yep, I did exactly as that thread said and everything has been working great so far! Thank you both for the help, it is greatly appreciated. I was up until almost 3 AM last night trying to fix it.
Click to expand...
Click to collapse
I've been there done that that's for sure. I just bricked one of my Moto Z plays last week doing what you were about to do.
StOP!!!! If you are on Custom firmware above 6, for the love of everything holy and merciful DO NOT downgrade so you can get the OTA. Some of us have and we are waiting for blankflash files that don't even exist yet.
tpx00 said:
StOP!!!! If you are on Custom firmware above 6, for the love of everything holy and merciful DO NOT downgrade so you can get the OTA. Some of us have and we are waiting for blankflash files that don't even exist yet.
Click to expand...
Click to collapse
He stopped and is all good! I am with you. Got a dead Moto Z Play. My new one from eBay is coming today. Sigh
EspElement said:
He stopped and is all good! I am with you. Got a dead Moto Z Play. My new one from eBay is coming today. Sigh
Click to expand...
Click to collapse
Ya I'm about to go pick up a nexus 6 from craigslist until mine comes back from Motorola.
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)
Hello.
First, sorry for my bad english, I hope you will understand what I say.
I bought a MotoG5 in France just after Chrismas, the retailer is Fnac.
He stays stuck with NPPS25.137-93-14 with Android 7.0 and with 1 july security patch.
He is really slow for booting, and YouTube playback is not smooth.
I'm pretty sure it comes from the fact that the ROM is not optimised, so I was searching for Oreo update but looks like it doesn't work with my firmware.
Can someone tell me if is it possible to change my ROM for having a smooth experience on this phone ?
Thanks, and have a nice day.
If I were you just wait until the oreo official ota rolls out (it's already started in some regions & obviously no one will know what you will get it)
Obviously you could flash specifically firmware & use the soak test ota but why bother - do it wrong you hard brick your device
Do it right you still may have issues updating it in the future
Just be patient if you want oero
If you want a custom rom use lineageos 14.1
elio612 said:
Hello.
First, sorry for my bad english, I hope you will understand what I say.
I bought a MotoG5 in France just after Chrismas, the retailer is Fnac.
He stays stuck with NPPS25.137-93-14 with Android 7.0 and with 1 july security patch.
He is really slow for booting, and YouTube playback is not smooth.
I'm pretty sure it comes from the fact that the ROM is not optimised, so I was searching for Oreo update but looks like it doesn't work with my firmware.
Can someone tell me if is it possible to change my ROM for having a smooth experience on this phone ?
Thanks, and have a nice day.
Click to expand...
Click to collapse
As long as you just flash boot, system (sparse chunk 0 thru 4), oem, non-hlos.bin, oem, fsg and dsp you should be all fine up/downgrading to any firmware version (when upgrading you may need to also flash bootloader).
People say all around here in XDA that's its "impossible to downgrade" Moto phones, this is all a myth.
I just downgrade my Cedric from stock Oreo to stock nougat. Only thing you need to know is:
1.NEVER downgrade bootloader... EVER... This will immediately hardbrick any motorola phone.
2.When you fastboot, there's no need to flash gpt.bin (at least on Cedric, I never do that, as I don't know what might happen).
3.erase Cedric's modemst1 and modemst2 and never see your imei again (I also don't understand why people say it's necessary to do this. When fastbooting a Motorola phone I always erase only cache and user data and never had problem)
4. You can downgrade to any firmware (since the newest bootloader will support the old firmwares) as long as you just flash system, fsg, dsp and oem and boot (it's not necessary to flash recovery, it will turn back to stock on the first boot.
5. To relock your bootloader.. You just need to flash the same files cited above.
freeZbies said:
People say all around here in XDA that's its "impossible to downgrade" Moto phones, this is all a myth.
Click to expand...
Click to collapse
It is impossible to fully downgrade. You can only partially downgrade, which doesn't allow to relock the bootloader on an older version. If you flash the latest soak test OTA you have to wait a fastboot version of the upcoming official, non-soak update comes out to be able to relock the bootloader because at that point you can't even go back to the latest fastboot flashable version of Nougat (though if you try to flash it, you won't hard brick the phone).
My recommendation would be to wait until the stable version of Oreo comes out and is flashable through fastboot.
freeZbies said:
When you fastboot, there's no need to flash gpt.bin (at least on Cedric, I never do that, as I don't know what might happen).
Click to expand...
Click to collapse
Flashing gpt.bin (re)creates partition scheme. If flash fails, partition scheme will mess up, which will end up in hardbrick.
fstabman said:
It is impossible to fully downgrade. You can only partially downgrade
Click to expand...
Click to collapse
True. I'm currently on stock Nougat but my bootloader is on B8.31, which is Oreo's BL version. As I can't Downgrade BL, once I downgraded the system
I didn't receive any OTA notifications anymore (due to mismatching BL version)
fstabman said:
If you flash the latest soak test OTA you have to wait a fastboot version of the upcoming official.
Click to expand...
Click to collapse
Also true. That's why after I downgraded from the official Oreo to Nougat I don't get any update notifications anymore(Oreo has already been out for a few weeks around here).
fstabman said:
which doesn't allow to relock the bootloader on an older version.
Click to expand...
Click to collapse
Not true AT ALL. I've relocked my bootloader after downgrading my phone and it's okay. Once you type "fastboot oem lock" twice on fastboot you just need to flash what fastboot demands you to, which is system, boot and oem. Recovery, dsp, modem and bootloader are not demanded, so you can theoretically relock any Motorola phone in any firmware version, using any firmware you want. I can't attest that for every device with the Motorola flag but I've already downgraded and relocked moto G2 and moto E5 - besides Cedric - using fastboot and never had any problems so far.
I think people come up with these stories in fear they might brick their devices but never try for themselves, so they come here and spread myths about the impossibility of relocking your device without ever paying attention to fastboot's own instrucrions on how to flash the device.
I really think that if the fastboot relock method didn't really accept downgrades it would make no sense for it to exist, since you'll presumably not always have a newer firmware version available to relock your device, because under the premise of unlocking your BL its assumed that you will move to an unnoficial OS and under the premise of relocking its assumed you'll have to downgrade/go back to stock. It's all logic. If fastboot didn't allow downgrades as a means of relocking bootloader, the relocking feature would not have a lot of sense unless it could be secured that every device would always have an updated firmware version available, one after the other, which is not only a false statement but also makes no sense.
In other words, this stories about not being able to downgrade/having to flash newer firmware to relock BL are all plain bull****. Relocking your bootloader never had anything to do with your firmware version afaik (I never had trouble doing it my self at least. Can't say for Others)
freeZbies said:
True. I'm currently on stock Nougat but my bootloader is on B8.31, which is Oreo's BL version. As I can't Downgrade BL, once I downgraded I didn't receive any OTA notifications anymore
Also true. That's why after I downgraded from the official Oreo to Nougat I don't get any update notifications anymore(Oreo has already been out for a few weeks around here).
Not true AT ALL. I've relocked my bootloader after downgrading my phone and it's okay. Once you type "fastboot oem lock" twice on fastboot you just need to flash what fastboot demands you to, which is system, boon and oem. Recovery, dsp, modem and bootloader are not demanded, so you can theoretically relock any Motorola phone in any firmware version, using any firmware you want. I can't attest that for every device with the Motorola flag but I've already downgraded and relocked moto G2 and moto E5 - besides Cedric - using fastboot and never had any problems so far.
I think people come up with these stories in fear they might brick their devices but never try for themselves, so they do here and spread myths about the impossibility of relocking your device but it makes no sense. I really think that if the fastboot relock method didn't really accept downgrades it would make no sense for it to exist, since you'll presumably not always have a newer firmware version available to relock your device if it was really as they say.
In other words, this is all plain bull****. Relocking your bootloader never had anything to do with your firmware version afaik (I never had trouble doing it my self at least. Can't say for Others)
Click to expand...
Click to collapse
So should I be "on safe side", if I lock bootloader with NPPS25.137-93-8 image but NPPS25.137-93-14 installed right now?
fstabman said:
It is impossible to fully downgrade. You can only partially downgrade, which doesn't allow to relock the bootloader on an older version. If you flash the latest soak test OTA you have to wait a fastboot version of the upcoming official, non-soak update comes out to be able to relock the bootloader because at that point you can't even go back to the latest fastboot flashable version of Nougat (though if you try to flash it, you won't hard brick the phone).
My recommendation would be to wait until the stable version of Oreo comes out and is flashable through fastboot.
Click to expand...
Click to collapse
Andrej_SK said:
So should I be "on safe side", if I lock bootloader with NPPS25.137-93-8 image but NPPS25.137-93-14 installed right now?
Click to expand...
Click to collapse
Yes. Take care of backing up your efs partition using twrp 64 bits first.
After that, download an official (signed) fastboot firmware and flash only system sparcechunks, oem and boot - in other words, do what fastboot tells you.
Dont "fastboot erase" anything but cache and user data and u should be fine. This command has been known for ages as being the cause of lost Imei (on moto g2 I think it broke if u erased the fsg partition, on Cedric its modem that breaks your Imei if erased).
If you for some reason have problems with signal/Sim cards not working, then u may flash the other partitions(fsg, dsp, and Non-hlos[modem])
I say these Because there may be incompatibilities related to The modem. For example, when downgrading from Oreo to NPPS25.137-93-2-5 using fastboot, everything went fine, but if I upgrade from npps25-137-93-2-5 to Oreo and don't flash modem And fsg, signal will not work. Also, if I downgrade from Oreo to Nougat using twrp and I don't flash fsg, fingerprint scanner wont work.
But in essence, as long as you don't "fastboot erase" anything unnecessary and don't touch bootloader (and seemingly gpt.bin, as someone mentioned above) , you should be safe.
freeZbies said:
Once you type "fastboot oem lock" twice on fastboot you just need to flash what fastboot demands you to, which is system, boot and oem.
Click to expand...
Click to collapse
The problem is, it fails at validating oem when trying to relock. At least on my end, after updating NPPS25.137-93-2-5 > First Oreo OTA > Second OTA > Back to NPPS25.137-93-2-5.
fstabman said:
It is impossible to fully downgrade. You can only partially downgrade, which doesn't allow to relock the bootloader on an older version. If you flash the latest soak test OTA you have to wait a fastboot version of the upcoming official, non-soak update comes out to be able to relock the bootloader because at that point you can't even go back to the latest fastboot flashable version of Nougat (though if you try to flash it, you won't hard brick the phone).
My recommendation would be to wait until the stable version of Oreo comes out and is flashable through fastboot.
Click to expand...
Click to collapse
fstabman said:
The problem is, it fails at validating oem when trying to relock. At least on my end, after updating NPPS25.137-93-2-5 > First Oreo OTA > Second OTA > Back to NPPS25.137-93-2-5.
Click to expand...
Click to collapse
Interesting.. Are you sure all files are signed? What error fastboot gives you?
I'll try making a video later today showing that it is possible to do it, so that u can see it.
freeZbies said:
Interesting.. Are you sure all files are signed? What error fastboot gives you?
I'll try making a video later today showing that it is possible to do it, so that u can see it.
Click to expand...
Click to collapse
Code:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:oem: not found
target reported max download size of 536870912 bytes
sending 'oem' (188494 KB)...
OKAY [ 6.023s]
writing 'oem'...
(bootloader) Security version downgrade
(bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.093s
I tried with 93-2-3 as well and get the same invalid signed image issue.
A question though, if the bootloader were to lock successfully after doing this (and since it still has some files from Oreo to prevent hard bricking), would it actually receive any OTAs?
fstabman said:
Code:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:oem: not found
target reported max download size of 536870912 bytes
sending 'oem' (188494 KB)...
OKAY [ 6.023s]
writing 'oem'...
(bootloader) Security version downgrade
(bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.093s
I tried with 93-2-3 as well and get the same invalid signed image issue.
A question though, if the bootloader were to lock successfully after doing this (and since it still has some files from Oreo to prevent hard bricking), would it actually receive any OTAs?
Click to expand...
Click to collapse
Really, the error you've been getting has to be related to you being unable to downgrade, since it attests the image is signed (error for unsigned I made says "unsigned or corrupt image).
Yep, seems like I was wrong, I might just have been lucky never to get an error like that before
Anyways, have you tried npps25-137-93-2-5 yet? It's the latest security patch (July) released in Brazil. I'm now somewhat confused lol.
Anyways, relocking your BL doesn't allow you to get otas, since some of the partitions will remain in the newest version, and that's long been known to render your phone unable to receive otas (I guess all partition's hashs are checked against stock ones before ota) and it will also not get your warranty back, so it's kind of useless unless you just want to test to see if u can downgrade OR if u want to go back to stock and never modify the device again.
EDIT: I was wrong, if you're on untouched stick you'll get OTA's, regardless of being unlocked or not.[/B] I thought I wouldn't receive OTA's anymore because it took me more than 2 weeks for me to get an OTA notification after it had already rolled out in Brazil, whereas for other updates I had gotten it really early By the way, I had other people confirm me that I wouldn't get it if I had modified my phone, but that's not true because when I got the OTA notification I had a rooted phone with lots of mosifixatiins. So I'm here to rectify this post and say that I was wrong: if you're on stock and there's an update rolling out, you should be getting it sooner or later regardless of your phone being rooted or not, but trying to apply the OTA in a modified phone will brick your device.
Anyways, I find it very strange that you're getting this error only when flashing the oem partition. You shouldn't be able to flash any of them.
If u want, I can send u the signed oem image I used to relock mine. I'm sure it won't cause any conflicts or glitches since this partition only contains some carrier bloat ware alongside some Motorola apks. I'm not sure if it will be Flash able alongside npp93-2-3 files during the same oem lock operation, due to mismatching firmware versions, but I think it'd be worth trying.
freeZbies said:
Anyways, have you tried npps25-137-93-2-5 yet? It's the latest security patch (July) released in Brazil. I'm now somewhat confused lol.
Click to expand...
Click to collapse
Yep, tried that one. I tried many different, older versions as well (got a hard brick or two as well, but I could restore it without issues). I can flash oem as long as it's not after I used the fastboot oem lock command twice. I do that and I am no longer able to do it.
Anyways I think I'll wait til Oreo stable comes out, all I was interested in was having the ability to take OTA updates again. Hopefully it will come out soon.
Well. If you wanted Official Oreo you wouldn't get it anyways.
But now that you said I'm curious to say how I managed to downgrade & relock without EVER getting that message.
To tell you the truth, I've seen many fastboot errors already, but this one is pretty new to me.
freeZbies said:
Well. If you wanted Official Oreo you wouldn't get it anyways.
But now that you said I'm curious to say how I managed to downgrade & relock without EVER getting that message.
To tell you the truth, I've seen many fastboot errors already, but this one is pretty new to me.
Click to expand...
Click to collapse
Did you downgrade from the first Oreo soak test or the second, more recent one?
fstabman said:
Yep, tried that one. I tried many different, older versions as well (got a hard brick or two as well, but I could restore it without issues). I can flash oem as long as it's not after I used the fastboot oem lock command twice. I do that and I am no longer able to do it.
Anyways I think I'll wait til Oreo stable comes out, all I was interested in was having the ability to take OTA updates again. Hopefully it will come out soon.
Click to expand...
Click to collapse
By the way could you tell me what exactly got your phone hard bricked?
freeZbies said:
By the way could you tell me what exactly got your phone hard bricked?
Click to expand...
Click to collapse
Doing a downgrade while flashing gpt.bin and bootloader with version B8.24.
ok so my phone is a tmo moto z2 force and i have no base band wifi it says all info like the imei meid and such are not there
heres what i did i was trying to root the phone and i accidentally flashed the wrong boot.img on to the device but i had a backup on that img on my pc so i just re-flashed it and it broke everything so i thought well i will just download a flashall and do it that way i did and it just broke more the problem was is i only had a backup on the boot.img ifi had a backup i would just flash that but i dont so i guess im sol if someone has a flashall for the latest TMO firmware you will be my god
https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783
41rw4lk said:
https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783
Click to expand...
Click to collapse
i dont think this will work i think i have tried this exact one with no avail
As long as you didn't flash pie and lose your baseband that way, you can fix it.
If you're on stock just go to recovery and do a factory reset from there, it should bring your baseband back. However, if you've flashed a modem from a firmware not intended for your phone, then you need to reflash the correct firmware then recovery, factory reset. If you flashed pie not intended for your phone, you might be out of luck depending on what variant you have.
41rw4lk said:
As long as you didn't flash pie and lose your baseband that way, you can fix it.
If you're on stock just go to recovery and do a factory reset from there, it should bring your baseband back. However, if you've flashed a modem from a firmware not intended for your phone, then you need to reflash the correct firmware then recovery, factory reset. If you flashed pie not intended for your phone, you might be out of luck depending on what variant you have.
Click to expand...
Click to collapse
i know i didnt flash pie but i honestly dont know what im doing because i haven't ever messed with motos before i dont know what version of firmware was on it originally
NovaPlayzGames said:
i know i didnt flash pie but i honestly dont know what im doing because i haven't ever messed with motos before i dont know what version of firmware was on it originally
Click to expand...
Click to collapse
you can test different firmwares depending of your variant, even is not recomended ,look at the box phone the company and settings of your phone
hello friends, i have a problem, i have a z2 force, with android 8.0.0, retbr software channel, security patch from january 1, 2018, installed version number is opxs27.109-34-4.
In fastboot mode I have baseband not found, I have BL: MBM-3.0-nash_retail-641a15b-180105, in product and variant I have: Nash radio2 64GB PVT and lastly I have Flashing_locked, can anyone help me with which firmware I can try to recover the cell phone ?
Note: no data band and no wifi
fallcaoalves said:
hello friends, i have a problem, i have a z2 force, with android 8.0.0, retbr software channel, security patch from january 1, 2018, installed version number is opxs27.109-34-4.
In fastboot mode I have baseband not found, I have BL: MBM-3.0-nash_retail-641a15b-180105, in product and variant I have: Nash radio2 64GB PVT and lastly I have Flashing_locked, can anyone help me with which firmware I can try to recover the cell phone ?
Note: no data band and no wifi
Click to expand...
Click to collapse
Stick to one thread or create your own, posting the same problem in 20 different threads won't help you in any way.