Database Info

[Q] xt910 downgrade

Hi xdadevelpers team unfortunately i have installed an unoficial rom for my device from this link http://forum.xda-developers.com/showthread.php?t=2069935 it works very good and no thing wrong with it but i have to send my phone to the Authorized agent here in egypt because of a problem at the sim card place in the phone so i need to get back to the official kernal which is ics is there any way to do this please help me

have you noticed, that this is the Razr HD section ?
And yes. MOAR fonts

Though you are indeed in the wrong forum, i'll help you out
There are 2 possibilities:
1. Your bootloader is unlocked:
Grab the appropriate Stock FW here: XT910 Stock Firmwares
And flash your phone according to this guide: http://www.andromods.com/tips-trick/how-to-restore-unroot-droid-razr-m-xt907-stock-original-firmware.html
Though the guide is for the xt907, it'll also work for xt910. As long as your BL is unlocked...
2. Your bootloader is locked and you're on safestrap:
Watch this
And above all: Next time post your question here: Droid RAZR Q&A

Xadro said:
Though you are indeed in the wrong forum, i'll help you out
There are 2 possibilities:
1. Your bootloader is unlocked:
Grab the appropriate Stock FW here: XT910 Stock Firmwares
And flash your phone according to this guide: http://www.andromods.com/tips-trick/how-to-restore-unroot-droid-razr-m-xt907-stock-original-firmware.html
Though the guide is for the xt907, it'll also work for xt910. As long as your BL is unlocked...
2. Your bootloader is locked and you're on safestrap:
Watch this
And above all: Next time post your question here: Droid RAZR Q&A
Click to expand...
Click to collapse
I'm so sorry that i did that mistake and i'm on my way to try your way thanks but also i have saved cid is it works and how to use it ?

mostafas60 said:
I'm so sorry that i did that mistake and i'm on my way to try your way thanks but also i have saved cid is it works and how to use it ?
Click to expand...
Click to collapse
What do you mean by saved cid? Is your phone carrier locked? Or what are you trying to say? You should pick a stock fw, which is at least your country/region better also from your carrier. It may also not be available at the site i mentioned.
If it is not available you could try and make a request. See the op of this thread

There is no such thing as an "unlocked bootloader" XT910 nor any other OMAP chipset Motorola device unless it is an engineering model with an NS bootloader.
There is no OEM unlock available for those devices and there never will be as the bootloader was never designed to be unlocked.
Motorola themselves have stated as much publicly.
This person has wiped their CID. partition in order to successfully flash a firmware from a different region onto his device.
He should seek advice in the proper forum fro those who have experience with this type of cross flashing issue.
It is precisely as a result of the locked bootloader status of these devices that these kinds of issues arise when users attempt to update their device with firmware not intended for their specific hardware or regional configuration.

Uh thanks for the heads up, wasn't aware of that. I assumed that motorola devices would be all similiar with this.

cellzealot said:
There is no such thing as an "unlocked bootloader" XT910 nor any other OMAP chipset Motorola device unless it is an engineering model with an NS bootloader.
There is no OEM unlock available for those devices and there never will be as the bootloader was never designed to be unlocked.
Motorola themselves have stated as much publicly.
This person has wiped their CID. partition in order to successfully flash a firmware from a different region onto his device.
He should seek advice in the proper forum fro those who have experience with this type of cross flashing issue.
It is precisely as a result of the locked bootloader status of these devices that these kinds of issues arise when users attempt to update their device with firmware not intended for their specific hardware or regional configuration.
Click to expand...
Click to collapse
Thanks a lot for your supply actually you did understood what happened with me
But now i faces problem i tried to get back to 2.3.6 and the phone stopped working totally and after two days of searching i found some way to get back to ics but it is opening only from Bp tools from the boot menu can you help me in that ?

mostafas60 said:
Thanks a lot for your supply actually you did understood what happened with me
But now i faces problem i tried to get back to 2.3.6 and the phone stopped working totally and after two days of searching i found some way to get back to ics but it is opening only from Bp tools from the boot menu can you help me in that ?
Click to expand...
Click to collapse
guys is there any one can answer me and how to solve this issue

http://forum.xda-developers.com/forumdisplay.php?f=1622

mostafas60 said:
guys is there any one can answer me and how to solve this issue
Click to expand...
Click to collapse
Probably if you go to the right forum man.
Sent from my PACMAN MATRIX HD MAXX

[Completed] Htc one mini m4 go back to stock rom

Hello everyone!
I've had my m4 for about 5/4 years now and my battery has been getting worse more and more slowly for about 2 months now. Because I want to invoke my guarantee I tried to return the phone to stock rom from Insertcoin, unroot it and lock the bootloader. I flashed the stock rom from this(http://forum.xda-developers.com/showthread.php?t=2791725) thread and everthing was working fine. After that I went into fastboot and typed the command "fastboot oem lock", because I read so on the internet. Now there seems to be no rom or recovery on my phone anymore and everytime i reboot it just straigth goes into the bootloader. None of the tools I found on google worked so I thought somebody here could help me because I'm almost getting desperate.
I will also include a link to a photo of the bootloader, maybe it's helpful (https://www.dropbox.com/s/0j7830bw6mxjjrv/IMG_20150511_190346.jpg?dl=0).
Also notice that this is one of my first posts in this forum and english isn't my mother tongue.
I would really appreciate a fast but especially useful and relative easily written response.
Thanks!

Hi, thank you for using XDA Assist. I would unlock the bootloader, fasboot oem unlock, and flash the stock firmware from the link you provided.

fastboot oem unlock error
I tried fastboot oem unlock but it just wrote "[ERR] Command error!!!". I also tried to unlock it via HTCdev again but the sites seems to be down, everytime i select my device and click on Begin Unlock Bootloader it opens this small window and says that the site is unavailable, I also tried it a few different times. Is there no other tool to unlock the bootloader or somehow get my rom started again, because I'm wondering why it's erasing or at least not giving me access to the rom that was perfectly working before anymore after locking the bootloader.
-Edit:
OK so i found out how to do it with HTCdev. I just had to create an account, log in and do exactly the same as before. I had to give it a few tries, but in the end it worked. Now my question is how I can relock my bootloader without causing the same again? I didn't find anything other than the cmd prompt fastboot oem lock so if maybe somebody could help me.

Thread closed.

What version of firmware will remove all the metro by tmobile bloatware?

Hi guys I downloaded the REtail version of my firmware for my device here https://mirrors.lolinet.com/firmware/motorola/denver/official/RETUS/
But when I patched and installed it via adb it seems to be a success
HOWEVER
I am STILL get the metro by tmobile splash screen on booting and I still have metro by tmobile apps pre installed on my phone. AND THAT Annoying metro news screen when you swipe to the left.
Am I not installing the correct firmware xda bros? TIA

Futtbucker34 said:
Hi guys I downloaded the REtail version of my firmware for my device here https://mirrors.lolinet.com/firmware/motorola/denver/official/RETUS/
But when I patched and installed it via adb it seems to be a success
HOWEVER
I am STILL get the metro by tmobile splash screen on booting and I still have metro by tmobile apps pre installed on my phone. AND THAT Annoying metro news screen when you swipe to the left.
Am I not installing the correct firmware xda bros? TIA
Click to expand...
Click to collapse
You flashed it using the flash_file.xml as a reference for flash commands?
These are my recommended steps If you have a Windows machine.
How to Change Software Channel

sd_shadow said:
You flashed it using the flash_file.xml as a reference for flash commands?
These are my recommended steps If you have a Windows machine.
How to Change Software Channel
Click to expand...
Click to collapse
sd_shadow said:
You flashed it using the flash_file.xml as a reference for flash commands?
These are my recommended steps If you have a Windows machine.
How to Change Software Channel
Click to expand...
Click to collapse
Thank you sir I can confirm the flash_file.xml reference was followed in the commands. I double checked.
I LMSA says it can't verify my software and won't let me continue . I got the new september update and i think lmsa don't have it yet. idk why else it would say this.

bump. Anyone?

update: I Reflashed 3 times successfully only the SOFTWARE CHANNEL still shows Universal SKU
This picture i found from ebay is from the same model I have. Yet they have no metro bloatware and North America Retail under software channel, Mine says Universal SKU.
https://mirrors.lolinet.com/firmwar...T_regulatory-DEFAULT_cid50_CFC_R3_CFC.xml.zip Is the firmware I used to flash\

THanks in advanced!

Futtbucker34 said:
Thank you sir I can confirm the flash_file.xml reference was followed in the commands. I double checked.
I LMSA says it can't verify my software and won't let me continue . I got the new september update and i think lmsa don't have it yet. idk why else it would say this.
Click to expand...
Click to collapse

Your best bet is honestly to just either use a custom rom or to remove all the bloatware either manually or systemlessly.

Long Story - Short:
Just got home with an Unlocked sofiap XT2043 - Moto G Stylus , networked unlocked, and I am able to toggle the OEM Unlock switch in Developer Options, However:
how did y'all unlock the Bootloader to start with ?
fastboot flashing unlock = FAILED
fastboot oem unlock = FAILED
is there a method to discern my oem unlock code ?
Thanks in Advance for any assistance !

barguybrady said:
Long Story - Short:
Just got home with an Unlocked sofiap XT2043 - Moto G Stylus , networked unlocked, and I am able to toggle the OEM Unlock switch in Developer Options, However:
how did y'all unlock the Bootloader to start with ?
fastboot flashing unlock = FAILED
fastboot oem unlock = FAILED
is there a method to discern my oem unlock code ?
Thanks in Advance for any assistance !
Click to expand...
Click to collapse
[Guide]Un/locking Motorola Bootloader
UnLocking and ReLocking Motorola Bootloader https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a Moto Bootloader Unlocking site Re-Locking see Post #4 More about bootloader UnLocking Post #2 Can my...
forum.xda-developers.com

Question Questions about firmware, bootloder

Hello, this is my first Motorola phone, please bear with me, I have a Motorola G62 5G phone and I have a question about the firmware, where can I download it?
And how to install them on this phone?
Does anyone have a guide?
Or it's on the forum because I've been looking and can't find anything.
I would also like to unlock the bootloader, how do I do that?
Is TWRP for this model?
Thank you in advance for your response.

Firmware: https://mirrors.lolinet.com/firmware/motorola/rhodec/official/
Installation: If you really need it I can post a guide. But I can't explain all the steps in a few words.
Bootloader unlock: https://en-us.support.motorola.com/app/standalone/bootloader/unlock-your-device-a

Thanks for your answer, I'll see if I can do that.

WoKoschekk said:
Firmware: https://mirrors.lolinet.com/firmware/motorola/rhodec/official/
Installation: If you really need it I can post a guide. But I can't explain all the steps in a few words.
Bootloader unlock: https://en-us.support.motorola.com/app/standalone/bootloader/unlock-your-device-a
Click to expand...
Click to collapse
Bootloader unlock will give the weird message on boot, right?

SoundDrill said:
Bootloader unlock will give the weird message on boot, right?
Click to expand...
Click to collapse
that's correct.

also you cannot just flash super image files by fastboot -flash super super.img - you also need to have it including block size =256M command or you will find that it will fail - i also have the Moto Fastboot version which you can just use the base command with out including block size - i have also found some issues with later versions of fastboot r32+ i think off the top of my head (4am in the morning and i will update shortly as about to re-flash my super partition)
apart from that no issues flashing or unlocking bootloader - bootloader you just need to submit the form - you should get a reply from moto fairly quickly - but if it is a new phone you will have to have it connected to a network for at least 7 days before it will actually allow you to unlock bootloader
bootloader - yes that is if you want to jailbreak/root your phone

SoundDrill said:
Bootloader unlock will give the weird message on boot, right?
Click to expand...
Click to collapse
I have 1 more question: which firmware file to download from this site? I doubt that all of them, because together they weigh over 48 gb

the easiest option I actually found to make sure downloading the correct firmware for phone as there are a wide variety of RHODEC models xt2223-x(x being a different constant) - was use the motorola RSA(rescue & smart assistance) software, just connect phone via adb and it downloads the firmware for you, though for a boot image file - i dont see there being major differences except if single/dual sim variants

Question Can anyone tell me how to get my A125U to accept a repartition?

Attached are pictures of the error messages I'm getting. I've tried everything I come across on these forums, and nothing seems to fix the issue. Does anyone know how to get around this?

eddieofny said:
Attached are pictures of the error messages I'm getting. I've tried everything I come across on these forums, and nothing seems to fix the issue. Does anyone know how to get around this?
Click to expand...
Click to collapse
There should be a PIT file packaged into the AP.tar. You need to extract this and use it in the PIT tab in Odin.
See this guide

V0latyle said:
There should be a PIT file packaged into the AP.tar. You need to extract this and use it in the PIT tab in Odin.
See this guide
Click to expand...
Click to collapse
That's exactly what I did that caused it to throw these error messages

eddieofny said:
That's exactly what I did that caused it to throw these error messages
Click to expand...
Click to collapse
Are you using the correct firmware?

V0latyle said:
Are you using the correct firmware?
Click to expand...
Click to collapse
I guess I should have specified this in the original post. I'm trying to convert it from T-Mobile firmware to carrier unlocked firmware, which is exactly why I was trying to repartition the devices. Right now, it has TMB firmware on it, I'm trying to put XAA firmware on. I'm using the latest version of Patched Odin to try and accomplish that, and to the best of my knowledge, none of the files are corrupt.

eddieofny said:
I guess I should have specified this in the original post. I'm trying to convert it from T-Mobile firmware to carrier unlocked firmware, which is exactly why I was trying to repartition the devices. Right now, it has TMB firmware on it, I'm trying to put XAA firmware on. I'm using the latest version of Patched Odin to try and accomplish that, and to the best of my knowledge, none of the files are corrupt.
Click to expand...
Click to collapse
Ah. Are you following a specific guide that tells you to do this? Carrier unlocking is generally done by the carrier in question. If you're the original owner of the device, contact TMobile and ask them to unlock your phone for use on another network. Your account must be paid off and in good standing to do this.
You can't unlock a phone simply by flashing new firmware, at least not to my knowledge.
A brief search through your post history shows that you already asked the relevant question, so it would appear that you're attempting to do something no one recommended without the knowledge that it will work.
It's better to ask questions before you try to do something you don't really know anything about, because the knowledge and expertise held by many here on XDA can save you a lot of pain. Trying to do things your own way can result in your device becoming no more useful than the average pebble.
As I said above, you cannot carrier unlock a device by flashing different firmware. It is hardware locked to the TMobile network, and to unlock it, the original owner and account holder must contact TMobile for the unlock code.
There are professional methods that can perform an unlock but this is not in the realm of the average user, and those tools are not available here.

V0latyle said:
Ah. Are you following a specific guide that tells you to do this? Carrier unlocking is generally done by the carrier in question. If you're the original owner of the device, contact TMobile and ask them to unlock your phone for use on another network. Your account must be paid off and in good standing to do this.
You can't unlock a phone simply by flashing new firmware, at least not to my knowledge.
Click to expand...
Click to collapse
It's not to carrier unlock it, the phone is already carrier unlocked. But the TMO firmware does not allow for OEM unlocking and comes with a ton of bloatware as well. From all the research I've done, flashing unlocked firmware solves both of those problems

eddieofny said:
It's not to carrier unlock it, the phone is already carrier unlocked. But the TMO firmware does not allow for OEM unlocking and comes with a ton of bloatware as well. From all the research I've done, flashing unlocked firmware solves both of those problems
Click to expand...
Click to collapse
What research where?
Is this a Snapdragon device?
You shouldn't need to repartition your device to flash a different CSC. However, flashing firmware with a different CSC won't enable OEM unlocking.

V0latyle said:
What research where?
Is this a Snapdragon device?
You shouldn't need to repartition your device to flash a different CSC. However, flashing firmware with a different CSC won't enable OEM unlocking.
Click to expand...
Click to collapse
No, it's a MediaTek device. Honestly, I've read so much stuff, I wouldn't be able to remember where. I've read alot from here, as well as Stack Overflow and pretty much anywhere on the internet that looked like it had answers. I came away with the impression that carriers could choose to remove OEM Unlocking from their firmware, but that non-carrier firmware as a general rule of thumb would have that option available. As it stands, I don't have OEM Unlocking in my Developer Options at all

eddieofny said:
No, it's a MediaTek device. Honestly, I've read so much stuff, I wouldn't be able to remember where. I've read alot from here, as well as Stack Overflow and pretty much anywhere on the internet that looked like it had answers. I came away with the impression that carriers could choose to remove OEM Unlocking from their firmware, but that non-carrier firmware as a general rule of thumb would have that option available. As it stands, I don't have OEM Unlocking in my Developer Options at all
Click to expand...
Click to collapse
Well...Yes and no.
There are a couple of properties that determine whether OEM Unlocking is visible: ro.oem_unlock_supported which is set at build time, and sys.oem_unlock_allowed
The first one is generally set at build time. The second one can be dynamic, like if the OEM/carrier wants the device to normally be unlockable, but wants E.T. to phone home to determine whether it should be allowed.
It's hard to say what the circumstance is here. But, in most cases, simply flashing different firmware will not permit unlocking the bootloader; in fact, a locked bootloader will generally prevent flashing anything but the firmware intended for that specific device.