Database Develop

Problem guys! Moto xt890 rsd lite - failed

Hello everyone! Need help to unbrick my Moto
My scenario: I got UK model JB 4.1.2 with locked bootloader. I was trying to flash official Brazilian JB and RSD failed ( I know my bad). So got all drivers, RSD Lite 6.1.5 and so far I was trying UK Retail JB, UK Orange, EU Retail all these failed, I've removed 2 lines from xml file mentioned by somebody on xda but no luck, also I've been on Motorola site to unlock bootloader but my device is not supported after verification (weird). I can restart to bootloader screen, any other option like "factory" or "recovery" gives me a red moto logo only.
Please see pictures for more details, any suggestions?

Solved! I've used mfastboot commands to erase cache and user data and I'm back to fresh UK retail JB

i think it failed because you need unlocked bootloader for flash official Brazilian JB rom in a UK phone
if you have a UK phone, you need unlocked bootloader for Brazil rom ( can be OTA to kitkat)
if you have a Latin American you don't need unlocked bootloader, can be a locked bootloader
the ROM and the phone need be the same region if the bootloader are locked.

That's right ManoBros, it was good lesson for me with a little bit of panic and happy end. I'm big fan of Android smartphones and changing my phones very often but always back to RAZR I, in this case I will wait for official UK kitkat.

[Q] Flash US Retail Firmware on Consumer Cellular Version

Hi,
I can see there are 2 US retail firmwares on http://sbf.droid-developers.org/phone.php?device=36
Which one should i use to restore a Consumer Cellular version to standard US Retail, also if you point me the steps guide using adb that would be great.
Also, would i need to unlock bootloader before flashing the retail version?
Thanks.

Any way to flash lollipop update to consumer cellular branded Moto g 2014?

Please check this link, i finally managed to downgrade to US Retail from Consumer Cellular version and flash lollipop via adb recovery!

How do I know what stock room I need to install to get the 5.1 OTA?

A couple of months ago, I bought this smartphone unlocked from Amazon USA (I'm from Argentina). After getting it, I updated it up to 4.4.4. Now, I'm on 5.1 after following this guide: http://forum.xda-developers.com/moto-x/general/how-to-install-5-1-lollipop-moto-x-t3089594
Now I want to comeback to the stock rom so I can get the official 5.1 update but I'm not sure what rom should I get. How can I know that?

daninoz said:
A couple of months ago, I bought this smartphone unlocked from Amazon USA (I'm from Argentina). After getting it, I updated it up to 4.4.4. Now, I'm on 5.1 after following this guide: http://forum.xda-developers.com/moto-x/general/how-to-install-5-1-lollipop-moto-x-t3089594
Now I want to comeback to the stock rom so I can get the official 5.1 update but I'm not sure what rom should I get. How can I know that?
Click to expand...
Click to collapse
Normally I would suggest BEFORE you flash away from Stock, on the phone you first go App Drawer -> Settings -> About Phone... Make note of what is listed under System Version, Android Version, and build number. Then visit one (or all) of the sites until that host the leaked SBF files until you find the SBF that matches and down load the file to your PC for use later.. The file name will usually contain parts or all of that info listed under settings, and possibly the carrier name, or acronym for the carrier name (Verizon might be VZW, Rogers Canada might be RCI, etc).
But seeing as you are no longer using your stock ROM, you need to provide us with some details...
1. Who is your carrier?
2. Was the phone you purchased from Amazon branded for your carrier, or was it "Unlocked"?
3. Is there any model info imprinted into the lower portion of the back case (in very fine print)?

KidJoe said:
Normally I would suggest BEFORE you flash away from Stock, on the phone you first go App Drawer -> Settings -> About Phone... Make note of what is listed under System Version, Android Version, and build number. Then visit one (or all) of the sites until that host the leaked SBF files until you find the SBF that matches and down load the file to your PC for use later.. The file name will usually contain parts or all of that info listed under settings, and possibly the carrier name, or acronym for the carrier name (Verizon might be VZW, Rogers Canada might be RCI, etc).
But seeing as you are no longer using your stock ROM, you need to provide us with some details...
1. Who is your carrier?
2. Was the phone you purchased from Amazon branded for your carrier, or was it "Unlocked"?
3. Is there any model info imprinted into the lower portion of the back case (in very fine print)?
Click to expand...
Click to collapse
1 & 2. My carrier is Claro Argentina but I bought the phone unlocked in Amazon, no branded.
3. It says XT1050. I guess that's the model. I tried to find a 4.4.4 room for that model but nothing.
Thanks for the answer.

daninoz said:
1 & 2. My carrier is Claro Argentina but I bought the phone unlocked in Amazon, no branded.
3. It says XT1050. I guess that's the model. I tried to find a 4.4.4 room for that model but nothing.
Thanks for the answer.
Click to expand...
Click to collapse
Can you boot the phone to bootloader mode and tell me what you see on the 2nd line?
And I've only seen 4.4.2 leaks for XT1050, and also they were for regional carriers in the USA, so possibly not what you need.

KidJoe said:
Can you boot the phone to bootloader mode and tell me what you see on the 2nd line?
And I've only seen 4.4.2 leaks for XT1050, and also they were for regional carriers in the USA, so possibly not what you need.
Click to expand...
Click to collapse
Ok, thanks.
The 2nd line says: 30.B7 (sha-bae5e20, 2014-06-23 18:24:49)

daninoz said:
Ok, thanks.
The 2nd line says: 30.B7 (sha-bae5e20, 2014-06-23 18:24:49)
Click to expand...
Click to collapse
30.B7 is the bootloader for a 4.4.4 ROM.
So you don't want to flash a 4.4.2 rom on there.
At this point, unless you can find a Stock Moto 4.4.4 XT1050 SBF, I would just sit with your phone as is.
I mean, you could try finding any XT1050 4.4.4 SBF and flashing it, but I've only seen one SBF for XT1050, and it was 4.4.2. So you'd risk bricking if you flash it, or if you take an OTA after you flashed it (since gpt/motoboot on your phone will be the wrong version). And even then, I'm not sure if it has any "carrier specific" settings in it.
Maybe You'll get lucky if 5.1 SBF's start leaking, and we'll see an XT1050 SBF.

KidJoe said:
30.B7 is the bootloader for a 4.4.4 ROM.
So you don't want to flash a 4.4.2 rom on there.
At this point, unless you can find a Stock Moto 4.4.4 XT1050 SBF, I would just sit with your phone as is.
I mean, you could try finding any XT1050 4.4.4 SBF and flashing it, but I've only seen one SBF for XT1050, and it was 4.4.2. So you'd risk bricking if you flash it, or if you take an OTA after you flashed it (since gpt/motoboot on your phone will be the wrong version). And even then, I'm not sure if it has any "carrier specific" settings in it.
Maybe You'll get lucky if 5.1 SBF's start leaking, and we'll see an XT1050 SBF.
Click to expand...
Click to collapse
Ok, thanks for the help. I think it will be better to go for a custom rom like CM.

No signal after Android 6.0 update

A few details:
First, I'm running 100% stock everything. However, this issue has also happened on Cyanogenmod 13, and both Motorola support and my carrier aren't very helpful, telling me to clear the cache which obviously hasn't worked.
I did an OTA update from Android 5.1 and I get no signal at all now. I have no idea why this is, it only seems to occur on Android 6.0.

What model is your device? Have you tried just flashing the modem files for your device?

Red_81 said:
What model is your device? Have you tried just flashing the modem files for your device?
Click to expand...
Click to collapse
Apologies, I should add this as an edit. Model number says Moto X (2nd Generation), System version 24.11.18.victara_tmo.tmo.en.US tkpca. Not sure what else you need, modem files have been reflashed but still no luck Out of ideas.

what is "tkpca" end of system version? Telus ? And this FW is for T Mobile XT1095. I guess your phone is XT1097. Maybe you flashed wrong FW before update . You should flash right FW or you can flash only modem to get signal back

md07 said:
what is "tkpca" end of system version? Telus ? And this FW is for T Mobile XT1095. I guess your phone is XT1097. Maybe you flashed wrong FW before update . You should flash right FW or you can flash only modem to get signal back
Click to expand...
Click to collapse
It worked on the 5.1 FW that I flashed though, and doesn't work on any version of 6.0. I flashed the FW provided by Moto on here:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images (Moto X (2nd Gen) Pure Edition: L-5.1-LPE23.32-21.3 TMO)
(And yes I have reflashed the modem)

I had this issue too with the OTA I received on xt1092 EU. I reflashed the modem with 5.1 fw, while keeping everything else on 6.0 fw. Worked for me, might work for you too. Good luck.

I have the same issue, on what I had thought was an EU xt1092. I uploaded the xt 1095 5.1 stock files to it a while ago and rooted and it has been fine. Did Marshmallow original OTA yesterday and it's lost cell signal. Some more investigation shows the imei of the phone to a be a AU variant! Wasn't expecting that. Reflash to xt1095 stock 5.1 bought service back again. Have tried a few different modem files, But I can't get signal with 6.0. Any ideas? Or any magic modem files . I also can't sideload the EU 6.0 OTA, it fails with signature problems.

I'm experiencing the same problem. I received the OTA a few days before Christmas, and now I'm still without signal. Just tried flashing Android 5.0 modem partition (from Motorola), but it didn't work.
My phone is the XT1097, but everywhere I searched said that the XT1097 and XT1095 were the same phone. I'll try flashing the modem partition from the 5.1 recovery image, I'm just waiting for Motorola to give me access to it.
EDIT: and yes, I flashed 5.1 from Motorola and it worked like a charm. Then OTA came and it messed up my phone's signal.

I have 5.1 modem files from moto for the xt 1095 and they haven't worked for me .
StillBrilliant, did you have the 1092 modem files or the 1095 ones? If you have 1092 is there any chance you can post them.

Just flashed the 5.1 image modem, and it still doesn't work. Any ideas?

RockyTV said:
Just flashed the 5.1 image modem, and it still doesn't work. Any ideas?
Click to expand...
Click to collapse
The modems from xt1095 and xt1097 are not the same. Which xt1097 do you have?(country and carrier)
TobeXtobes said:
I have 5.1 modem files from moto for the xt 1095 and they haven't worked for me .
StillBrilliant, did you have the 1092 modem files or the 1095 ones? If you have 1092 is there any chance you can post them.
Click to expand...
Click to collapse
You need the xt1092 modem. However there is more than one xt1092. Do you have reteu, retes, or retde?
Sent from my XT1095 using Tapatalk

AGISCI said:
The modems from xt1095 and xt1097 are not the same. Which xt1097 do you have?(country and carrier)
Click to expand...
Click to collapse
My XT1097 is from Brazil, no carrier, bought it directly from Motorola's site. The weird thing I've found is that the update version has retbr in its name.
EDIT: fixed it. Found a thread that had the retail images for XT1097. Downloaded the Brazil version and flashed the modem. It works now.

I thought mine was a reteu, but not so sure now.... Imei listed it as an Australian phone! (I bought it from someone who reviews tech) I am in the UK, but now not so sure which modems I need!

TobeXtobes said:
I thought mine was a reteu, but not so sure now.... Imei listed it as an Australian phone! (I bought it from someone who reviews tech) I am in the UK, but now not so sure which modems I need!
Click to expand...
Click to collapse
In fastboot run:
fastboot getvar all
It should tell you what the phone truly is.
Sent from my XT1095 using Tapatalk

Ah, ro.carrier says reteu

TobeXtobes said:
Ah, ro.carrier says reteu
Click to expand...
Click to collapse
Ok, here is the full 6.0 for reteu:
http://www.filefactory.com/file/6q0pj4hr2sh5/VICTARA_RETEU_XT1092_6.0_MPE24.49-18_cid7_CFC.xml.zip
Use the commands in fastboot:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
That should get you back on the correct modem for your phone. Or if you want just flash everything in this zip to be 100% stock 6.0 for the reteu model.
Sent from my XT1095 using Tapatalk

Thank you, I think I might flash the whole thing back to stock with that and start again.

As a bit of a newb here, the fastboot system system.img command isn't working for this chunked image. What is the system image command for sparse, or the quickest way to rechunk them together. I've been searching but I have come up with about 15 different methods!
By the way, flashing the modem files from that image worked. Thank you but I would still like to go back to stock.

Same issue signal drop after upgrading to 6
i am having the same issue after upgrade to 6. Signal drops a lot. Works fine when connected to 3g or 4g networks, but drops to 2g networks. What could be the reason.

Note 9 T-mobile possible to get rid of bootlogo?

Well i have a Note 9 128gb T-mobile unlocked N960U that is carrier unlocked
Is it possible to reflash it with clean firmware from samsung for n960u so i can get rid of The T-mobile logo every time i start the mobile ?
i don't want to try to root i know it's not possible just want original firmware if it works hope someone can answer

LennartL said:
Well i have a Note 9 128gb T-mobile unlocked N960U that is carrier unlocked
Is it possible to reflash it with clean firmware from samsung for n960u so i can get rid of The T-mobile logo every time i start the mobile ?
i don't want to try to root i know it's not possible just want original firmware if it works hope someone can answer
Click to expand...
Click to collapse
You can flash it using modded or patched ODIN to the U1 non-carrier firmware to get rid of the T-Mobile boot animation. It will also remove the T-Mobile video calling dialer though but WiFi Calling will still work.

What he said^^^ flash the U1 firmware. Note your device will be wiped.
Sent from my SM-N960F using Tapatalk

Well that doesn't matter to me. Have never used it yet so it doesn't matter if I wipe it. But will I get regular updates if I flash it with u1 firmware ?
And which firmware should I select it exists a few on this page or do I need to take the tmb one for T-Mobile but I'm not using T-Mobile and will probably never do
Here is the page samsung-updates.com/device/?id=SM-N960U1

LennartL said:
Well that doesn't matter to me. Have never used it yet so it doesn't matter if I wipe it. But will I get regular updates if I flash it with u1 firmware ?
And which firmware should I select it exists a few on this page or do I need to take the tmb one for T-Mobile but I'm not using T-Mobile and will probably never do
Here is the page samsung-updates.com/device/?id=SM-N960U1
Click to expand...
Click to collapse
Do not use the one labeled TMB U1. That firmware isn't official and could potentially break OTA's. You want to use the U1 XAA with the same version or newer bootloader than what your device currently has. The the first character of the last five characters of the build number contains your bootloader version. I don't believe the Note 9 has a v2 bootloader yet, but I have only really followed ATT U firmware, U1 firmware, and TMB U firmware. When you flash, do not use the HOME_CSC! remember your device will be wiped and factor reset so back up what you want before starting.

I'm running the TMB U1 firmware. No bloat or boot screens and I get OTAs around the same time as the U t mobile devices. I honestly dont see a real difference from the XAA u1 vs the TMB U1 firmware to be honest

Well that's it's not a problem haven't started to use the device yet. But it's not any risk that I'm brick my phone when flashing with u1 firmware.
One thing I noticed it exists unbranded firmware what I can see on Samsung's page for n960U can I not use that firmware ?
But I should not flash home_csc ? I'm guessing that contains special files for u1 ?

LennartL said:
Well that's it's not a problem haven't started to use the device yet. But it's not any risk that I'm brick my phone when flashing with u1 firmware.
One thing I noticed it exists unbranded firmware what I can see on Samsung's page for n960U can I not use that firmware ?
But I should not flash home_csc ? I'm guessing that contains special files for u1 ?
Click to expand...
Click to collapse
The non-branded firmware is the U1. The reason the modded or patched ODIN is needed is to skip the check that you are flashing the same carrier firmware. The hardware for the US and Canadian models are exactly the same. The firmware on Sansung's page isn't meant for flashing in ODIN.
Although I have only seen one user experience issues with the TMB U1, which for some reason, gave him a modded software warning when they tried to check for updates. I would stick to using the actual non-carrier specific firmware, which has T-Mobile's WiFi Calling and still has band 71 enabled.

ok so the SM-N960U is carrier branded and the SM-N960U version ubranded i thought it was some more technical difference between the different models.
Well the phone i have is new just carrierd unlocked but it's coming from t-mobile but i'm not going to use it in usa right now. So unless i need to have t-mobile's software i gladly skip it and use unbranded and that is the "U1 XAA" i need to use ?

LennartL said:
ok so the SM-N960U is carrier branded and the SM-N960U version ubranded i thought it was some more technical difference between the different models.
Well the phone i have is new just carrierd unlocked but it's coming from t-mobile but i'm not going to use it in usa right now. So unless i need to have t-mobile's software i gladly skip it and use unbranded and that is the "U1 XAA" i need to use ?
Click to expand...
Click to collapse
The U is carrier specific, the U1 is a generic non-carrier specific firmware that should work with most US carriers, and the W is the Canadian equivalent of the U1. The hardware for all three is exactly the same.
The unbranded and non-carrier specific firmware does have its advantages. No carrier bloat, it works well with T-Mobile, and if you switch carriers, the phone will reconfigure for the SIM inserted. The only time the U firmware is recommended is if you need a specific feature for a particular carrier that isn't available in the U1 firmware. Video Calling for T-Mobile, WiFi Calling on AT&T, and so on.

jcsww said:
The U is carrier specific, the U1 is a generic non-carrier specific firmware that should work with most US carriers, and the W is the Canadian equivalent of the U1. The hardware for all three is exactly the same.
The unbranded and non-carrier specific firmware does have its advantages. No carrier bloat, it works well with T-Mobile, and if you switch carriers, the phone will reconfigure for the SIM inserted. The only time the U firmware is recommended is if you need a specific feature for a particular carrier that isn't available in the U1 firmware. Video Calling for T-Mobile, WiFi Calling on AT&T, and so on.
Click to expand...
Click to collapse
Ok so with other words i can use the unbranded XAA firmware and keep OTA now. But if i ever want to use T-mobile or AT&T further on i just install corresponding firmware for that carrier right ?

LennartL said:
Ok so with other words i can use the unbranded XAA firmware and keep OTA now. But if i ever want to use T-mobile or AT&T further on i just install corresponding firmware for that carrier right ?
Click to expand...
Click to collapse
That's correct! The U1 non-carrier firmware is like a stepping stone, If you want to move from one U firmware to one from a different carrier, you need to flash to U1 first and always make sure you never use the HOME_CSC. The HOME_CSC doesn't wipe the device, which can cause a number of issues when converting. Being on the U1 though, makes it very easy to go back to any U firmware because you are already at the point where you could just straight flash to any U or W firmware as long as the bootloader version is the same or newer than what your device has at that time.

ok thanks for all advice
just to be curious because i don't know but wish to learn. Why should u never flash hone_csc and what does that file do?

LennartL said:
ok thanks for all advice
just to be curious because i don't know but wish to learn. Why should u never flash hone_csc and what does that file do?
Click to expand...
Click to collapse
The HOME_CSC prevents wiping while flashing. If you skip the wiping part, you risk having no data, no potential cellular connectivity, no different unlocked bands for the firmware you are flashing to, etc. You pretty much put yourself in a position where you have to flash again, but actually use the other CSC to ensure your device works properly.

Any unlocked USA note 9s willing to upload there modem files somewhere wanna try and make a sim unlock

Help on Flashing Tmobile firmware on Unlocked Note 9
jcsww said:
The U is carrier specific, the U1 is a generic non-carrier specific firmware that should work with most US carriers, and the W is the Canadian equivalent of the U1. The hardware for all three is exactly the same.
The unbranded and non-carrier specific firmware does have its advantages. No carrier bloat, it works well with T-Mobile, and if you switch carriers, the phone will reconfigure for the SIM inserted. The only time the U firmware is recommended is if you need a specific feature for a particular carrier that isn't available in the U1 firmware. Video Calling for T-Mobile, WiFi Calling on AT&T, and so on.
Click to expand...
Click to collapse
Hello all. I am new to this community. I have read several of the posts that mention that the US Snapdragon variant of the Note 9 cannot be flashed with TWRP or custom roms. However I see that based on this post regarding T-Mobile that the U1/ublocked variant can be flashed with any of the other U variants as long as the bootloader is the same. Does this mean that I can flash the T-Mobile firmware on my unlocked note 9? If so can anybody guide me on how to do this? I am trying to go back to having T-Mobile's built in multiline and voicemail functionality which I lost after going from the T-Mobile branded Note 8 to the unlocked Note 9. Thanks!

lguti46 said:
Hello all. I am new to this community. I have read several of the posts that mention that the US Snapdragon variant of the Note 9 cannot be flashed with TWRP or custom roms. However I see that based on this post regarding T-Mobile that the U1/ublocked variant can be flashed with any of the other U variants as long as the bootloader is the same. Does this mean that I can flash the T-Mobile firmware on my unlocked note 9? If so can anybody guide me on how to do this? I am trying to go back to having T-Mobile's built in multiline and voicemail functionality which I lost after going from the T-Mobile branded Note 8 to the unlocked Note 9. Thanks!
Click to expand...
Click to collapse
Yes you can. Use ODIN to flash the T-Mobile firmware. It's that simple. You don't need an unlocked bootloader or root. No it won't trigger Knox.
If you need detailed instructions, they have been posted in some of the firmware threads here, o you can go to the Note 8 forums and read through the carrier switching thread. Just follow the steps for flashing carrier firmware. The steps are all the same, you just make sure you're using the right firmware for your device.

Thank you so much! I was able to successfully flash to T-Mobile using the forum threads.

Hi there again i have Little bit trouble to locate the exat firm i need. The baseband my phone is using seems to be N960USQS1ARH6 i do understand i should use xaa but i dont find any baseband N960USQS1ARH6 xaa im litte bit lost can someone help please ?

LennartL said:
Hi there again i have Little bit trouble to locate the exat firm i need. The baseband my phone is using seems to be N960USQS1ARH6 i do understand i should use xaa but i dont find any baseband N960USQS1ARH6 xaa im litte bit lost can someone help please ?
Click to expand...
Click to collapse
That's because U1 XAA is on ARJ9. There won't be a U1 Firmware with an ARH6 build number.