Flashing ONLY the newest baseband on custom rom - Moto Z Play Questions & Answers

I have a question that might be simple to answer, but i need confirmation because i don't want to brick my device recklessly.
When i got my Moto Z play, i immediatley unlocked it, flashed TWRP and installed LineageOS. So my device (including bootloader and baseband) are still on the state it arrived i guess. But my OS ist the newest LineageOS (so android 7.1.2).
My Moto Z play is an XT1635-02 32GB (bootloader adds P7 as variant), software channel must be RETEU.
My bootloader is C0.14 (from 2016-07-11)
and my baseband is M8953_10208.08.04-47e (bootloader says M8953_10208.08.04.47R ADDISON_ROW_CUST)
Are there newer versions of baseband (which might more important) and booloader? And can i flash them without problems?
Just flashing the NON-HLOS.bin in fastboot and i'm fine? Can i also use the 7.0-modem from RETAIL?
Sorry, these questions might be dumb and too careful for old users, but i'm only used to nexus devices and i am scared of bricking my Z play! Nexus factory images always had baseband and bootloader version written in the filename so it was easy to find out if you need to update. In addition there was just one "software channel" which made it hard to brick a device or flash something wrong.

McFlypants said:
I have a question that might be simple to answer, but i need confirmation because i don't want to brick my device recklessly.
When i got my Moto Z play, i immediatley unlocked it, flashed TWRP and installed LineageOS. So my device (including bootloader and baseband) are still on the state it arrived i guess. But my OS ist the newest LineageOS (so android 7.1.2).
My Moto Z play is an XT1635-02 32GB (bootloader adds P7 as variant), software channel must be RETEU.
My bootloader is C0.14 (from 2016-07-11)
and my baseband is M8953_10208.08.04-47e (bootloader says M8953_10208.08.04.47R ADDISON_ROW_CUST)
Are there newer versions of baseband (which might more important) and booloader? And can i flash them without problems?
Just flashing the NON-HLOS.bin in fastboot and i'm fine? Can i also use the 7.0-modem from RETAIL?
Sorry, these questions might be dumb and too careful for old users, but i'm only used to nexus devices and i am scared of bricking my Z play! Nexus factory images always had baseband and bootloader version written in the filename so it was easy to find out if you need to update. In addition there was just one "software channel" which made it hard to brick a device or flash something wrong.
Click to expand...
Click to collapse
I'm running the original bootloader and baseband from 6.0.1 without any issue, so I would suggest leaving it.

I don't want to get on the wrong side of you but that wasn't my question.
I wanted to know this because i'm not sure if i get the most out of my phone with an older baseband. I can't use VoLTE for example which possibly is activated with a newer baseband. Or it might improve the signal.

McFlypants said:
I don't want to get on the wrong side of you but that wasn't my question.
I wanted to know this because i'm not sure if i get the most out of my phone with an older baseband. I can't use VoLTE for example which possibly is activated with a newer baseband. Or it might improve the signal.
Click to expand...
Click to collapse
Well I'll suggest you only flash the baseband that comes with your specific firmware, if you flash the baseband from another firmware package you will end up without a IMEI and you'll have a expensive brick, which you will send to me so I can use the screen to get my mzp working again. That will be payment for warning you

Good one, flashallthetime
Back in, uh, I think Atrix time or even HTC Desire it was normal to flash/change radio baseband. It supposed to improve radio, prolong battery life... In reality, most of the time didn't do anything, sometimes broke something...
So in theory, you can do that. Should be fine but I wouldn't recommend.
If you have to, to get VoLTE, I would make a backup of the current rom, follow guide to flash back to stock and then restore backup. But be extremely careful, so many users over here bricked their devices. As far as I can see, downgrading and the accepting OTA.
Sent from my LG-V940n using Tapatalk

flashallthetime said:
Well I'll suggest you only flash the baseband that comes with your specific firmware, if you flash the baseband from another firmware package you will end up without a IMEI and you'll have a expensive brick, which you will send to me so I can use the screen to get my mzp working again. That will be payment for warning you
Click to expand...
Click to collapse
Good idea, please return it to me afterwards if it's working! :good:

Related

H81009e? Same as H81010? Safe to update?

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

Can Moto Z Play Droid (XT1635-01) be flashed trough fastboot?

I know its bootloader is locked, but what happens if I try to flash trough fastboot? I mean, in the black kinda console screen after you press Power button + Vol Down button.
ADB interface recognize this, but I'm pretty afraid to make my Moto Z a hard dead block. So, have anyone did this?
Just in case, I want to do exactly this https://www.youtube.com/watch?v=d_YO__aYM7M&t=448s but on my Droid version, the tutorial is on spanish but I know you will understand the video
rusa-raus said:
Just in case, I want to do exactly this https://www.youtube.com/watch?v=d_YO__aYM7M&t=448s but on my Droid version, the tutorial is on spanish but I know you will understand the video
Click to expand...
Click to collapse
So if I've understood you correctly, you're looking to flash Android Oreo onto your device via fastboot?
With a locked bootloader, it's pretty difficult to hard brick your device whilst flashing, just be careful that you have a stable power supply (both to your computer and to your device, and that you have plenty of time). With a locked bootloader, you can only flash the same or newer firmware than you currently have on your device, the bootloader will otherwise block you from flashing older firmwares.
That being said, you'd need the Verizon stock ROMs to flash on a Droid if I recall correctly. The retail Oreo stock ROM we have here may not work and your locked bootloader may force you to flash only Verizon firmwares, so your best bet may be to either wait for the Verizon Oreo OTA, find the Verizon OTA on XDA or hope that someone uploads the Verizon Oreo firmware.
echo92 said:
So if I've understood you correctly, you're looking to flash Android Oreo onto your device via fastboot?
With a locked bootloader, it's pretty difficult to hard brick your device whilst flashing, just be careful that you have a stable power supply (both to your computer and to your device, and that you have plenty of time). With a locked bootloader, you can only flash the same or newer firmware than you currently have on your device, the bootloader will otherwise block you from flashing older firmwares.
That being said, you'd need the Verizon stock ROMs to flash on a Droid if I recall correctly. The retail Oreo stock ROM we have here may not work and your locked bootloader may force you to flash only Verizon firmwares, so your best bet may be to either wait for the Verizon Oreo OTA, find the Verizon OTA on XDA or hope that someone uploads the Verizon Oreo firmware.
Click to expand...
Click to collapse
Understood, seems like Verizon is not gonna update Moto Z Play...

XT1922-2 with unlocked bootloader but no root bootlooping after update to Pie

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

No Baseband No Wifi and No imei

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.

Warranty problem: Flashing to stock Nougat from a custom Pie rom

Hi folks,
I searched the forum and did not find a suitable thread that answered my question.
My Moto G5 has a charging problem and I want to give it back for a repair - it still has warranty.
I have read that flashing a custom rom does not necessarily invalidate the warranty, but to ensure that Motorola will repair the phone I would like to flash a stock (nougat) rom.
Is it possible without the risk of losing IMEI or other stuff?
Or do you recommend to send it back to Motorola with the custom rom installed?
Thank you VERY MUCH in advance!!!
Kind regards
Wolf
They will be able to see you have unlocked the bootloader regardless of whether you re-lock it
Just download the latest stock firmware and flash it via fastboot
If your base firmware is already oreo you can skip flashing gpt and bootloader to avoid risking hard brick
Don't downgrade your base firmware eg if it's oreo don't flash nougat (base firmware is stock firmware not custom rom)
I would flash it back to stock rom so at least they can't blame custom rom
Thanks!! I'm not sure, if it was delivered with Android 7 or 8. But I can flash 8 in any case, because its no downgrade?
And a last question: can I flash it also with TWRP? It's installed anyways...
moped2000 said:
Thanks!! I'm not sure, if it was delivered with Android 7 or 8. But I can flash 8 in any case, because its no downgrade?
And a last question: can I flash it also with TWRP? It's installed anyways...
Click to expand...
Click to collapse
Yes flash android 8 - note if it was never updated to android 8 you will also have to flash gpt and bootloader as well the rest of the firmware
You will need to flash the firmware via fastboot
Flashing via twrp is just like flashing a custom rom with no modifications & you will still have twrp installed and not stock recovery & still have a modified system partition etc
Thanks! Android 8 was definitely installed, only possibly not as stock firmware, but only as custom rom.
But I guess it's okay if I just flash all the files to make sure?
Motorola says, I have lost my warranty because I have opened the bootloader. They won't even fix it for money ****.
moped2000 said:
Motorola says, I have lost my warranty because I have opened the bootloader. They won't even fix it for money ****.
Click to expand...
Click to collapse
Depends what country you are in
In America or Europe you can argue and would most likely win in court that if your issue is totally unrelated to the unlocking of the bootloader they must repair it
Eg if the camera doesn't work because of a faulty component they must fix it
However if the camera stop working because you unlocked the bootloader & did some modifications causing it to no longer work then you're not covered
This would be the same for boot issues - If your phone no longer boots and you have unlocked the bootloader they can claim you have done a modification that now stops it booting
The general rule is if you unlock the bootloader than software/firmware booting issues are not covered but hardware faults unrelated to a bootloader unlock are
Again it varies depending on your country but the above is true for USA & the majority of Europe (EU)

Categories

Resources