New to Samsung, questions about firmware versions and heimdall - Samsung Galaxy S9+ Questions & Answers

Hello, forgive me for asking what are probably considered noob questions, but I've been reading quite a few threads and getting lost in the acronyms (not to mention the users that don't agree with one another).
I've got an S9+ with G965USQS3ARG8 with Verizon bloat. I'm trying to bring it over to Project Fi. Inserting my active sim from my Nexus 6 seems to work OK. I have a persistent message about it not being a Verizon sim though, and would also like to get rid of the Verizon bloatware to clean this thing up a bit. Can I flash a U1 firmware on here and call it a day? If so, can I use heimdall? I'm running Linux Mint, just updated to Java 11, and heimdall is correctly detecting my device. I don't have Windows, and it seems Odin is kind of the default around here, but it's not my best option.
Do I need to unlock my phone in any fashion first? I have adb, if necessary. I have G965U1UEU3ARJ2 downloaded already, I just don't want to brick this thing and am not sure if I should proceed. I'm used to using TWRP to flash Moto phones, this is a different ballgame. Also, am I likely to run into bootloader incompatibility issues? What do I watch out for?
Thanks!

Not to worry! I was in the exact same boat as you, was expecting to receive a G965U1 but got a Verizon G965U. I posted in this thread and a very helpful member here walked me through it: https://forum.xda-developers.com/galaxy-s9-plus/how-to/g965u-g965u1-firmware-links-t3763487/page144. My post started on page 144 and pretty much takes up the rest of the thread. The 5th number from the end is the bootloader version, and I was advised to pick a U1 firmware with the same bootloader version, so it looks like you want to pick something with a 3, as you have. The only other thing is I was advised to pick an XAA firmware, which I guess means completely carrier free, but I'm not sure how important it is, or if you can even find one with bootloader 3.
Anyway, it should all be spelled out in that link, as I was in your exact position and it didn't take me long to get converted to essentially a factory unlocked device. Only thing I'm not sure about is Heimdall, because here I had to use a patched version of Odin that would allow the flashing of a different models firmware.... If Heimdall will allow that then I guess it would work but I'm not sure, haven't used it in years and back when I did use it, Samsung firmware was just one file, was not broken up into parts like it is now. Anyway, good luck, you can do this.

YrrchSebor said:
Not to worry! I was in the exact same boat as you, was expecting to receive a G965U1 but got a Verizon G965U. I posted in this thread and a very helpful member here walked me through it: https://forum.xda-developers.com/galaxy-s9-plus/how-to/g965u-g965u1-firmware-links-t3763487/page144. My post started on page 144 and pretty much takes up the rest of the thread. The 5th number from the end is the bootloader version, and I was advised to pick a U1 firmware with the same bootloader version, so it looks like you want to pick something with a 3, as you have. The only other thing is I was advised to pick an XAA firmware, which I guess means completely carrier free, but I'm not sure how important it is, or if you can even find one with bootloader 3.
Anyway, it should all be spelled out in that link, as I was in your exact position and it didn't take me long to get converted to essentially a factory unlocked device. Only thing I'm not sure about is Heimdall, because here I had to use a patched version of Odin that would allow the flashing of a different models firmware.... If Heimdall will allow that then I guess it would work but I'm not sure, haven't used it in years and back when I did use it, Samsung firmware was just one file, was not broken up into parts like it is now. Anyway, good luck, you can do this.
Click to expand...
Click to collapse
Thank you very, very much, YrrchSebor! This was a very thoughtful and helpful reply. Your thread was a gold mine--it was nice to read about a problem that was actually applicable to my situation.
I can't remember if my copy of 3ARJ2 is XAA or not, so I'm grabbing a new copy of 3ARJ6 XAA from Updato. Hopefully Heimdall will work without protest, but if not, I guess I'll have to create a virtual machine with the patched Odin.

Well I tried to use Jodin3 with Heimdall to no avail. Now I'm installing VirtualBox and jumping through all the necessary hoops. Oh well, I'll get there eventually.

pvfjr said:
Well I tried to use Jodin3 with Heimdall to no avail. Now I'm installing VirtualBox and jumping through all the necessary hoops. Oh well, I'll get there eventually.
Click to expand...
Click to collapse
Keep us posted! I know with a virtualbox the trick is having the device recognized, once you get that you should be good I would hope.

YrrchSebor said:
Keep us posted! I know with a virtualbox the trick is having the device recognized, once you get that you should be good I would hope.
Click to expand...
Click to collapse
After messing with VB for a while, it dawned on me I still had a dual boot laptop on hand with a sad and degraded old Win7 install. I was able to make it work. The flash was a success! No more obnoxious notifications about sim cards. I do get odd strings of characters after texts though. May be a topic for another thread.

Related

Would it be possible to use Verizon SUA to get MDK?

I accidentally allowed that stupid program to run and I realized an answer could be staring right at me. Could we possibly trick the program into repairing your phone with an MDK install? (as if you were to repair an actual MDK phone?) Or possible use it to flash MDK thinking it's a newer version? I'd assume it'd basically think it had authority from Verizon themselves.
I definitely no developer but I figured it may be a question outside the box.
J Andersen said:
I accidentally allowed that stupid program to run and I realized an answer could be staring right at me. Could we possibly trick the program into repairing your phone with an MDK install? (as if you were to repair an actual MDK phone?) Or possible use it to flash MDK thinking it's a newer version? I'd assume it'd basically think it had authority from Verizon themselves.
I definitely no developer but I figured it may be a question outside the box.
Click to expand...
Click to collapse
Its defiantly an interesting suggestion, but i doubt it will work because the phone itself check if the signature matches what it has(each version has its own signature) and if it doesn't that's what causes it to brick. also it would require us getting a hold of either the source code of the program or the signature that Samsung signs there installs with.
Mtsprite said:
Its defiantly an interesting suggestion, but i doubt it will work because the phone itself check if the signature matches what it has(each version has its own signature) and if it doesn't that's what causes it to brick. also it would require us getting a hold of either the source code of the program or the signature that Samsung signs there installs with.
Click to expand...
Click to collapse
I thought it was lack of authority to flash roms? Since the ROMs would be legit, combined with Verizon SUA or even Samsung Kies it I'd assume the program would only do what it's told and everything would check out. It'd be interesting to try to say the least.
J Andersen said:
I thought it was lack of authority to flash roms? Since the ROMs would be legit, combined with Verizon SUA or even Samsung Kies it I'd assume the program would only do what it's told and everything would check out. It'd be interesting to try to say the least.
Click to expand...
Click to collapse
If it was just lack of authority to flash the firmware, then anyone with a JTAG box could get around that. On every boot, the bootloader performs several authentication checks. Among other things, a check against hardware q-fuses which cannot be set back once tripped. Either the signature needs to be leaked from the official source (Samsung) or the authentication checks must be bypassed via means of code exploits.

[Q] q)GALAXY LIGHT METRO pcs I BROKE MY Phone

Ok so I got the samsung galaxy light from metro running 4.4.2 and I decided to root my phone got myself rooted but I used some**** that changdd my phone from metro to tmobile and I guess my pho j e is locked now and its on 4.2.2 and im a iphone guy and dont really understandwhat I did but any help with gettjng my phone back would really be awesome
themilkboy08 said:
Ok so I got the samsung galaxy light from metro running 4.4.2 and I decided to root my phone got myself rooted but I used some**** that changdd my phone from metro to tmobile and I guess my pho j e is locked now and its on 4.2.2 and im a iphone guy and dont really understandwhat I did but any help with gettjng my phone back would really be awesome
Click to expand...
Click to collapse
What?
I have a Galaxy Light, and I'm fairly knowledgeable about the device. But I don't understand gibberish. You need to tell us exactly what you did, and try to speak in English without typos.
Ok
Lol sorry, I rooted my phone, well I put twrp on my phone the flashed it with I guess a flash for tmobile and on jellybean instead of kitkat. I tried to flash the radio but dont think it did anything. And now I reboot my phone and its asking for the sim pin
themilkboy08 said:
Lol sorry, I rooted my phone, well I put twrp on my phone the flashed it with I guess a flash for tmobile and on jellybean instead of kitkat. I tried to flash the radio but dont think it did anything. And now I reboot my phone and its asking for the sim pin
Click to expand...
Click to collapse
Which TWRP did you flash? Did you flash T-Mobile firmware? I need to know EXACTLY what you did.
Ok
I used twrp 2.7.0.0-gardaltetmo.tar. The flashed a supers u update -v 1.94.zip, then I wanted to know how to unroot incase I needed to know and used SGH-t399-stock-MJA.ZIP
themilkboy08 said:
I used twrp 2.7.0.0-gardaltetmo.tar. The flashed a supers u update -v 1.94.zip, then I wanted to know how to unroot incase I needed to know and used SGH-t399-stock-MJA.ZIP
Click to expand...
Click to collapse
Don't use T-Mobiles firmware on your MetroPCS phone.
This is what you need to do.
And for the love of all that is good in this world, next time DO A BACKUP before flashing things. You installed TWRP, which gives you the ability to make a complete backup of your system exactly as it is at that point in time. If you had done a back-up before you screwed up your phone, it would have taken you but a few minutes to unscrew it.
I apologize for being harsh, but it seems to me like you really need to read and research a lot more. I always (well, usually...almost bricked my tablet the other day) read everything I can find about something potentially risky before doing it. Let this be a learning experience for you. Read as much as you can, understand what it is you are actually doing rather than just following some guide, and if you don't understand, just ask. I and most of us here would rather you asked a noobish question instead of going blindly ahead and screwing your phone up. Playing around with root and recovery and flashing without understanding it is like thinking you can perform open heart surgery with a meat cleaver because you've seen every episode of ER, Scrubs, and Grey's Anatomy.
thanks
ok thanks alot btw. just now got the files downloaded but im in twrp and the files are on my pc how could i get them to my phone? and i dont have a sd card either
themilkboy08 said:
ok thanks alot btw. just now got the files downloaded but im in twrp and the files are on my pc how could i get them to my phone? and i dont have a sd card either
Click to expand...
Click to collapse
Hm. I didn't think about that. I think you might need to get an SD card. Go on Amazon or eBay and pick one up. An 8GB one can be had for literally a few bucks, but a 64GB class 10 one for $35 is an awesome thing too.
Ok
Ok, and with the back up download how do I get the in twrp. Should I put it in a zip file or leave it how it is
ok im a retard
Planterz said:
Hm. I didn't think about that. I think you might need to get an SD card. Go on Amazon or eBay and pick one up. An 8GB one can be had for literally a few bucks, but a 64GB class 10 one for $35 is an awesome thing too.
Click to expand...
Click to collapse
ok so i cannot figure out how to do this.
i have the sgh-t399n galaxy light- with no os installed, i have twrp on my phone. and i have a backup a sd card. but when i go to restore in twrp the backup isnt there, and ive tried going threw the file options to move it to where is it suposed to go but no such luck. i thought maybe a terminal command would work but i have no clue what command to use. if you could help one more time that would be awesome
You can always use Samsung Kies 3 to flash your phone back to stock. You need your serial number though, and for some reason it is not printed on the back of the device(at least for me). A call to tech support should get that sorted anyway.
Alternatively, you can do this with Odin to a very similar effect. Search Google for something like "T399NUVUANK3 tar" to get the file you need, my personal backup is corrupt so I can't share.
fddm said:
You can always use Samsung Kies 3 to flash your phone back to stock. You need your serial number though, and for some reason it is not printed on the back of the device(at least for me). A call to tech support should get that sorted anyway.
Alternatively, you can do this with Odin to a very similar effect. Search Google for something like "T399NUVUANK3 tar" to get the file you need, my personal backup is corrupt so I can't share.
Click to expand...
Click to collapse
Ugh... I own a t399n and I'm doing some real development on it. . I've made a stock odex and deodexed rooted zip files for the t399n and haven't posted them yet. . If you're in a bad way still hit me up and I'll have you up and running in no time. Fun things coming for metro users. Who says you have to pay for a high end device to have a high end device? He he he....
Do you have a backup I bicked my samsung galaxy light metropcs then I unbricked it by restoring a backup for the samsung galaxy light that I found online. Search fresh backup for samsung galaxy light sgh t399n.
Planterz said:
Which TWRP did you flash? Did you flash T-Mobile firmware? I need to know EXACTLY what you did.
Click to expand...
Click to collapse
You're quite uppity, aren't you? I had no trouble understanding exactly what he did.
reholli said:
You're quite uppity, aren't you? I had no trouble understanding exactly what he did.
Click to expand...
Click to collapse
Are you seriously giving me crap about a post from over a year ago? Nice contribution to the discussion.:good: I have no idea if the OP ever fixed his phone, but at least I tried to help.
Planterz said:
Are you seriously giving me crap about a post from over a year ago? Nice contribution to the discussion.:good: I have no idea if the OP ever fixed his phone, but at least I tried to help.
Click to expand...
Click to collapse
And the age of the post, with respect to your attitude, is relevant how?
reholli said:
And the age of the post, with respect to your attitude, is relevant how?
Click to expand...
Click to collapse
I just love getting an email alert at 4am because someone quoted me to post absolutely nothing of substance.
It's relevant because IT WAS A YEAR AGO! I don't remember why I was so cranky that day. I did apologize to him for it. Did you notice that I also still did my best to help him? Do you have a solution to his problem? Does he even still have this phone, given that it was a year ago? If you want to fixate on my posts, fixate on the hundreds of times I've been thanked for helping others, especially going above and beyond helping people find the perfect device for them. I'm not here to be grumpy, I'm here to help people, and get help when needed. Why are you here? To pester me? Look, I respect my elders, and you're clearly older, but at the same time don't presume to talk down to me. Try reflecting on yourself and your motive in making a useless post, bumping a thread dead for several months (a severe breach of netiquette), purely to insult another member.
Come to think of it, my email alert wasn't because I was quoted (I have that feature turned off). I got the alert because I'm still subscribed to this thread, having done so in case there were new posts that might enable me to help the OP. I suppose I should unsubscribe, giving the fact that nobody has posted anything of use or substance in 7 months or so.

how to find and flashing a Stock Rom on my Noka 7.2 with unlocked bootloader?

hello does anybody know a working method to how to find and download and flash a Stock Rom on my Nokia 7.2 all Tutorials i try so far but did not work well i stuck as well in security patch problem it will not install thats why i want try to find a Stock Rom to flash again with working update
It's pretty easy. Use the NFT tool to flash any full update package and/or flash a full firmware package (HMDSW type).
singhnsk said:
It's pretty easy. Use the NFT tool to flash any full update package and/or flash a full firmware package (HMDSW type).
Click to expand...
Click to collapse
Sorry for the necro, and not asking if phone can be rooted as wow, am not surprised how many asked already lol.
I purchased four unlocked Nokia 7.2 which forced updated to 10 upon bootup. I'm trying to deal with two issues, one of which I believe is either the Google phone dialer stopping all other phone dialer recording programs from working with a message "call to short to record". Phone has an oem unlock feature in developer section and I see the bootloader is locked, and all research says OS 10 stops this from getting unlocked. After seeing absolutely zero posts on YouTube about downgrading a Nokia 7.2 to OS 9, and so many scam sites, I figure best option is to ask here.
Can a Nokia 7.2 be flashed down to OS 9 where bootloader can then be unlocked, or are all the posts I'm seeing, just wishful thinking fakes? Thanks.
Lord-Xanthor said:
Sorry for the necro, and not asking if phone can be rooted as wow, am not surprised how many asked already lol.
I purchased four unlocked Nokia 7.2 which forced updated to 10 upon bootup. I'm trying to deal with two issues, one of which I believe is either the Google phone dialer stopping all other phone dialer recording programs from working with a message "call to short to record". Phone has an oem unlock feature in developer section and I see the bootloader is locked, and all research says OS 10 stops this from getting unlocked. After seeing absolutely zero posts on YouTube about downgrading a Nokia 7.2 to OS 9, and so many scam sites, I figure best option is to ask here.
Can a Nokia 7.2 be flashed down to OS 9 where bootloader can then be unlocked, or are all the posts I'm seeing, just wishful thinking fakes? Thanks.
Click to expand...
Click to collapse
Hi, essentially the only way to downgrade a locked device is via a Nokia Care point or otherwise tools which can replicate what the Nokia Care tools do. All of these will have a price and unfortunately, no free way exists. You can opt for some remote services.
The tutorials on random websites will help in no way because a locked bootloader will not let you flash any device partitions, thereby disallowing downgrades as well. You cannot load an older OTA package from recovery mode because its date will mismatch.
singhnsk said:
Hi, essentially the only way to downgrade a locked device is via a Nokia Care point or otherwise tools which can replicate what the Nokia Care tools do. All of these will have a price and unfortunately, no free way exists. You can opt for some remote services.
The tutorials on random websites will help in no way because a locked bootloader will not let you flash any device partitions, thereby disallowing downgrades as well. You cannot load an older OTA package from recovery mode because its date will mismatch.ii
Click to expand...
Click to collapse
I don't mind paying.
singhnsk said:
Hi, essentially the only way to downgrade a locked device is via a Nokia Care point or otherwise tools which can replicate what the Nokia Care tools do. All of these will have a price and unfortunately, no free way exists. You can opt for some remote services.
The tutorials on random websites will help in no way because a locked bootloader will not let you flash any device partitions, thereby disallowing downgrades as well. You cannot load an older OTA package from recovery mode because its date will mismatch.
Click to expand...
Click to collapse
I have no trouble paying to get this done. It's finding the place to do it that's in the way. I called metro and tmobile and both said they don't offer this service. Least the ones in California I called. One site offered at $4.50 rollback and $8 to root and I am more wary of that then the free ones lol. Any suggestions to real places? Thanks for getting back.
Lord-Xanthor said:
I don't mind paying.
I have no trouble paying to get this done. It's finding the place to do it that's in the way. I called metro and tmobile and both said they don't offer this service. Least the ones in California I called. One site offered at $4.50 rollback and $8 to root and I am more wary of that then the free ones lol. Any suggestions to real places? Thanks for getting back.
Click to expand...
Click to collapse
I will edit this after, if this works so others can try as well. It's not free and is costing me $150 to do. Will update in a few weeks.

Question Moto G Pure - XT2163-4 vs XT2163-2 - LTE bands

New here. Didn't see a forum for the Moto G Pure XT2163. Mods - I am sorry. Please move wherever's best.
Discovered that the version Verizon is selling (notably the slickdeals thread on the one from Visible) is different. It's -2 vs. -4.
Looks like VZW disabled most of the bands that T-Mobile/Sprint use - 25, 41, 71, for example.
Looking to see if it's possible to enable those bands. One report on SD thread says they bricked their device trying RETUS version but IDK if the bootloader needs to be unlocked first, or if it would even help. Probably more work to unlock these bands if it's even possible.
Downloads look available here https://mirrors.lolinet.com/firmware/moto/ellis/official/
Haven't messed with flashing a phone in years. May be able to try later but hoping anyone else here can look into this.
I'm going to guess as is the case with most other Android devices branded by Verizon that the bootloader will be restricted from being unlocked. There is really no way around this as it's an OEM based policy. If you want to play with custom ROMs or root based modding, I would highly recommend ditching the Verizon or any other carrier branded variant with the exception of T-Mobile/Metro and Google Fi (there are others) that actually allow OEM unlock. Not only that, but if you're looking for certain connectivity bands, you don't want to settle for a carrier device variant designed to use a particular set of bands which don't include the ones you need. No sense getting a Verizon variant to run on T-Mobile/Sprint bands when you can, you know, get the T-Mobile variant in the first place. Get the global unlocked variant model if you can and start from there. Far easier than the headaches you'll get trying to transform VZW to TMUS.
Cross-flashing is not going to unlock bands, you need to change modem configuration. Throw your SoC(Mediatek) followed by "unlock bands" into Google and see if you have any luck.
I also didn't see a forum for the Moto G Pure and was wondering if anyone knows of a custom bootloader like TWRP or CWM for it? I think I have enough understanding of how to sideload the app, I just need something to send the phone. I tried using a random TWRP mod on it but it fails, invalid signature. I haven't tried doing the phone rooting thing in years now, but I have this Moto G Pure phone without any service on it that I'm willing to experiment on. It can be used as a test bed or data extraction device to put code from it on the internet if someone needs it to help custom rom makers for example by testing stuff on it. Perhaps that's why no one has a custom recovery for it yet.
I don't know exactly how to extract the phones current ROM data so all I've done so far is unlock the bootloader. The phone's carrier based on the unactivated sim card shows it's a T-Mobile branded device, but the T-Mobile and other carrier software is inactive other than the few Moto apps. An article on XDA say's the phone's suck, but that's just not true at least not to me. It's a fine phone like it is, but if I can format it's SSD and only install what I want it to have on it that would be great. It's just a spare sim locked phone that I can't use my active sim card in. So with that it's now a project phone. I would like to mainly just unbloat it and free up all that used space occupied by the recovery partition. I don't necessarily need a whole new ROM, just want to root it. That's the only way to erase those factory files that I know of.
For me unlocking the bootloader wasn't to hard to do. You have to make sure the drivers from Motorola are installed and have a current version of ADB available on a computer. I still had a version of ADB tools that was almost a decade old now so I had to update that for the fastboot oem_unlock_unlockcode (automated code from Motorola support) command to work. To find out if it can be unlocked or not go here:
https://motorola-global-portal.custhelp.com/app/standalone%2Fbootloader%2Funlock-your-device-b
At the Moto site they will guide you on how to generate the code they want you to send them. You have to sign in to their site to use that function though. After I finally figured out what to type in the CMD window it generated that code and I edited it down to one long line of numbers and give it to the page. In seconds I had an email with the unlock code inside.
Unlocking it seems to help with uninstalling some of the built in stuff, before I could only disable most of the apps that come with it. The apps are still probably on there I just have to factory reset it and they'll come back. Now however the removed apps don't show as using any internal storage, all the apps info numbers go to 0 bytes, but still even doing that it's still over 10GB of unmovable data. When it should really be more like 2-3 GB for the entire system. I hate how Google just inserts itself in your life even when you don't want it at all.
I anyone passing by reading this post needs more details please let me know and I'll try to get the information or even data files from the phone. Would a copy of it's stock firmware be of any help? If so let me know how I would go about saving a copy of it. I'll keep looking for answers but it seems this phone is not high on the priority list or is new or something. So there is only scam guides trying to tell you "How to unlock your phone" or "Install TWRP on Motorola devices" and other clearly click bait sites. I can't even find the stock rom for it on Motorola's site, just outdated versions from 2016, with different build numbers, that can't be right.
All I know is unlocking the bootloader was the first step on all the guides and I've done that. Got a warranty voided notice and everything. There currently isn't a custom recovery mod for this model as far I can tell. If I can ever find that then I can try Linage or just debloat Android 11 which is probably the safer and easier option provided I can find that Custom Covery'.
When it boots up now, it has to tell me it's unlocked and all the dangers it poses. Dangerous if you cared about what was on it I suppose. There is nothing on it I can't just copy back over to it, other than the stock operating system.
Oh yeah, it's model number and other side of the box information is:
Model Name: Moto G PURE
SKU: MO-XT21634-AJB (MOXT21634AJB)
Software Version RRH31.Q3-46-20
Production date was 12/15/2021
I'm not sure what other information to include.
BrittonCBurton said:
I also didn't see a forum for the Moto G Pure and was wondering if anyone knows of a custom bootloader like TWRP or CWM for it? I think I have enough understanding of how to sideload the app, I just need something to send the phone. I tried using a random TWRP mod on it but it fails, invalid signature. I haven't tried doing the phone rooting thing in years now, but I have this Moto G Pure phone without any service on it that I'm willing to experiment on. It can be used as a test bed or data extraction device to put code from it on the internet if someone needs it to help custom rom makers for example by testing stuff on it. Perhaps that's why no one has a custom recovery for it yet.
I don't know exactly how to extract the phones current ROM data so all I've done so far is unlock the bootloader. The phone's carrier based on the unactivated sim card shows it's a T-Mobile branded device, but the T-Mobile and other carrier software is inactive other than the few Moto apps. An article on XDA say's the phone's suck, but that's just not true at least not to me. It's a fine phone like it is, but if I can format it's SSD and only install what I want it to have on it that would be great. It's just a spare sim locked phone that I can't use my active sim card in. So with that it's now a project phone. I would like to mainly just unbloat it and free up all that used space occupied by the recovery partition. I don't necessarily need a whole new ROM, just want to root it. That's the only way to erase those factory files that I know of.
For me unlocking the bootloader wasn't to hard to do. You have to make sure the drivers from Motorola are installed and have a current version of ADB available on a computer. I still had a version of ADB tools that was almost a decade old now so I had to update that for the fastboot oem_unlock_unlockcode (automated code from Motorola support) command to work. To find out if it can be unlocked or not go here:
https://motorola-global-portal.custhelp.com/app/standalone%2Fbootloader%2Funlock-your-device-b
At the Moto site they will guide you on how to generate the code they want you to send them. You have to sign in to their site to use that function though. After I finally figured out what to type in the CMD window it generated that code and I edited it down to one long line of numbers and give it to the page. In seconds I had an email with the unlock code inside.
Unlocking it seems to help with uninstalling some of the built in stuff, before I could only disable most of the apps that come with it. The apps are still probably on there I just have to factory reset it and they'll come back. Now however the removed apps don't show as using any internal storage, all the apps info numbers go to 0 bytes, but still even doing that it's still over 10GB of unmovable data. When it should really be more like 2-3 GB for the entire system. I hate how Google just inserts itself in your life even when you don't want it at all.
I anyone passing by reading this post needs more details please let me know and I'll try to get the information or even data files from the phone. Would a copy of it's stock firmware be of any help? If so let me know how I would go about saving a copy of it. I'll keep looking for answers but it seems this phone is not high on the priority list or is new or something. So there is only scam guides trying to tell you "How to unlock your phone" or "Install TWRP on Motorola devices" and other clearly click bait sites. I can't even find the stock rom for it on Motorola's site, just outdated versions from 2016, with different build numbers, that can't be right.
All I know is unlocking the bootloader was the first step on all the guides and I've done that. Got a warranty voided notice and everything. There currently isn't a custom recovery mod for this model as far I can tell. If I can ever find that then I can try Linage or just debloat Android 11 which is probably the safer and easier option provided I can find that Custom Covery'.
When it boots up now, it has to tell me it's unlocked and all the dangers it poses. Dangerous if you cared about what was on it I suppose. There is nothing on it I can't just copy back over to it, other than the stock operating system.
Oh yeah, it's model number and other side of the box information is:
Model Name: Moto G PURE
SKU: MO-XT21634-AJB (MOXT21634AJB)
Software Version RRH31.Q3-46-20
Production date was 12/15/2021
I'm not sure what other information to include.
Click to expand...
Click to collapse
hey i just came up on one of these today, nice phone considering... Any luck with trying to find a custom recovery? I have been looking as well but development seems pretty sparse right now. I am in the same boat as you, unlocked bootloader, locked everything else lol. I cant even find a way to root it without TWRP! I am curious if one of the other moto G series phones would have the same TWRP? Also check this out. It sounds legit but IDK...https://www.getdroidtips.com/root-motorola-g-pure-xt2163/
Agent_Orange1488 said:
hey i just came up on one of these today, nice phone considering... Any luck with trying to find a custom recovery? I have been looking as well but development seems pretty sparse right now. I am in the same boat as you, unlocked bootloader, locked everything else lol. I cant even find a way to root it without TWRP! I am curious if one of the other moto G series phones would have the same TWRP? Also check this out. It sounds legit but IDK...https://www.getdroidtips.com/root-motorola-g-pure-xt2163/
Click to expand...
Click to collapse
Well I was able to use Magisk to "root" it with the patched boot file trick, but still that's not the same thing as I did before with a Samsung phone and the CWM recovery deal. That gave the user all the control they wanted. Even though the phone claims I have root access, I'm not sure what to do with Magisk's root trick. I still don't see a way to backup or install a different operating system or just a blank Android 11 OS. My knowledge there is limited and there isn't a custom recovery for this model as far as I can tell.
So I still can't wipe the drive or remove the OEM partition that contains the installers for the bundled stuff. I'd still need some form of interface that has more features than the stock Fastboot and Bootloader modes offer I guess, or I just don't know how to use the software tools correctly. It's still locked even with root as far as I can tell but if there is something more I'm missing or an additional app to install for example, like SU. Is that still a thing? If I'm on the right track let me know.
BrittonCBurton said:
Well I was able to use Magisk to "root" it with the patched boot file trick, but still that's not the same thing as I did before with a Samsung phone and the CWM recovery deal. That gave the user all the control they wanted. Even though the phone claims I have root access, I'm not sure what to do with Magisk's root trick. I still don't see a way to backup or install a different operating system or just a blank Android 11 OS. My knowledge there is limited and there isn't a custom recovery for this model as far as I can tell.
So I still can't wipe the drive or remove the OEM partition that contains the installers for the bundled stuff. I'd still need some form of interface that has more features than the stock Fastboot and Bootloader modes offer I guess, or I just don't know how to use the software tools correctly. It's still locked even with root as far as I can tell but if there is something more I'm missing or an additional app to install for example, like SU. Is that still a thing? If I'm on the right track let me know.
Click to expand...
Click to collapse
Thanks for the reply!!! I am speaking from a place of semi-ignorance here but I would thing that you could install SuperSU from inside the system, right? As long as the root binary is there...idk though and from what I hear, chainfire is not responsible for SuperSU anymore so it has become somewhat sketchy. I saw a post (about this phone, I think) that mentioned having to install terminal emulator and running root command from there to achieve legit root after flashing the patched boot.img. I will see if I can find the post again and update you. Is there anyway you could post the boot.img? Or give me a link for it?
Agent_Orange1488 said:
Thanks for the reply!!! I am speaking from a place of semi-ignorance here but I would thing that you could install SuperSU from inside the system, right? As long as the root binary is there...idk though and from what I hear, chainfire is not responsible for SuperSU anymore so it has become somewhat sketchy. I saw a post (about this phone, I think) that mentioned having to install terminal emulator and running root command from there to achieve legit root after flashing the patched boot.img. I will see if I can find the post again and update you. Is there anyway you could post the boot.img? Or give me a link for it?
Click to expand...
Click to collapse
Well I can try and learn how to extract the phones information to my computer. I don't know how to do that exactly. The way I was able to get a hold of the phones stock firmware data was by using Lenovo's Smart Rescue and Recovery software.
You have to enable usb debugging mode, attach the phone to the computer with the software running and make sure that you didn't disable/delete Device Help. That app is what makes the Lenovo software work, otherwise the Recovery software fails to see the phone. If it sees the phone correctly then you can see the preselected target firmware it wants you to download under the Rescue tab along the top.
So I did that and grabbed the files it created without actually applying them to the device. The whole thing is a little over 2GB and difficult to host but I put the stock boot.img file here for anyone who needs it. If anyone wants all the files I can try to upload the whole thing one file at at time. That's the way it was sent to me, an uncompressed folder. If I zip it all up and try to upload it most sites will say file size exceeded. Anyway here's the link...
boot
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Thanks I was able to patch it with Magisk and achieve root. It looks like Magisk is an SU manager anyway. I have never used it before so this is a first for me. The root and bootloader unlock seem a little pointless without any recovery or ROM though....I guess it's time to learn how to compile one lol
I just picked up the Moto G Pure (XT2163-4) Android 11 aka Red Velvet Cake *sounds yummy lol*....I've been searching around and not seen any info about any rooting method for this device....besides the "Root All Motorola Phones" crap...and I don't feel like risking making a paper weight with it. Even on here it doesn't show up in the...add device list....was going to add to my profile...but can't.
Agent_Orange1488 said:
Thanks I was able to patch it with Magisk and achieve root. It looks like Magisk is an SU manager anyway. I have never used it before so this is a first for me. The root and bootloader unlock seem a little pointless without any recovery or ROM though....I guess it's time to learn how to compile one lol
Click to expand...
Click to collapse
Yeah now we're on the same page then. I thought the same thing, not much use to have an unlocked boot loader and root access without software to make use of it. I gave the phone to my nieces to play with for now, but it's with in arms reach if I need it for instructions yet to be defined. I should receive updates to this post if anyone else responds.
Gamekeeper408 said:
I just picked up the Moto G Pure (XT2163-4) Android 11 aka Red Velvet Cake *sounds yummy lol*....I've been searching around and not seen any info about any rooting method for this device....besides the "Root All Motorola Phones" crap...and I don't feel like risking making a paper weight with it. Even on here it doesn't show up in the...add device list....was going to add to my profile...but can't.
Click to expand...
Click to collapse
Yeah appears it was produced in late 2021 or sold at that time so it's new and no one has made any custom firmware's or recoveries for it as far as I know. I don't know how to do that, requires computer programming skills. I don't have any of those.
Gamekeeper408 said:
I just picked up the Moto G Pure (XT2163-4) Android 11 aka Red Velvet Cake *sounds yummy lol*....I've been searching around and not seen any info about any rooting method for this device....besides the "Root All Motorola Phones" crap...and I don't feel like risking making a paper weight with it. Even on here it doesn't show up in the...add device list....was going to add to my profile...but can't.
Click to expand...
Click to collapse
I feel your pain! Had mine a few days and of course came to XDA immediately to find the DL on this joint but no luck... Ya I definitely don't recommend one click root method for this. If you want, I can post/link the patched boot.img i made with magisk. Mine boots with it and have confirmed root.
BrittonCBurton said:
Yeah now we're on the same page then. I thought the same thing, not much use to have an unlocked boot loader and root access without software to make use of it. I gave the phone to my nieces to play with for now, but it's with in arms reach if I need it for instructions yet to be defined. I should receive updates to this post if anyone else responds.
Click to expand...
Click to collapse
Excellent, it's nice to be caught up with everyone else haha!! I am going to do some digging and posting and whatnot to try to find some info on porting a recovery for this model. I feel like it can't be too different from at least one or two of the other G series phones. I will see updates as well so please post if you come up with anything!!
BTW does anyone know the process of creating a device page for this joint?! I think this phone is definitely worth some development...
Agent_Orange1488 said:
Excellent, it's nice to be caught up with everyone else haha!! I am going to do some digging and posting and whatnot to try to find some info on porting a recovery for this model. I feel like it can't be too different from at least one or two of the other G series phones. I will see updates as well so please post if you come up with anything!!
BTW does anyone know the process of creating a device page for this joint?! I think this phone is definitely worth some development...
Click to expand...
Click to collapse
Good luck finding anything that will load onto the phone. Seems like it would be possible to install LineageOS on it if nothing else. You'd think by now installing a phone's operating system would be similar to how operating systems are installed on other computers. All I get is invalid signature, way to much security (for them) on phone OS'es. With phones and PDA's apparently you can't just find the OS you want to use and install it. Where's the generic and bloat free Andriod 11 stock OS/firmware at? No such thing? It's either "Gaggles" way or nothing apparently. (It's ok if you don't know either, maybe someone else has more information about that.)
BrittonCBurton said:
Good luck finding anything that will load onto the phone. Seems like it would be possible to install LineageOS on it if nothing else. You'd think by now installing a phone's operating system would be similar to how operating systems are installed on other computers. All I get is invalid signature, way to much security (for them) on phone OS'es. With phones and PDA's apparently you can't just find the OS you want to use and install it. Where's the generic and bloat free Andriod 11 stock OS/firmware at? No such thing? It's either "Gaggles" way or nothing apparently. (It's ok if you don't know either, maybe someone else has more information about that.)
Click to expand...
Click to collapse
Ya I'm definitely not going to try anything on the actual device, (ESPECIALLY if I am trying to put it together myself) but I am pretty sure you can test that stuff on a virtual system. Some kind of android emulator or whatever. As for a stock/debloated/de-odexed ROM, I haven't seen one but that couldn't be all that difficult to put together, right? I mean as long as the patched boot.img is included anyway. I feel like a recovery would be a higher priority though...? BTW, I have never used Lineage before, how is it?
Agent_Orange1488 said:
I feel your pain! Had mine a few days and of course came to XDA immediately to find the DL on this joint but no luck... Ya I definitely don't recommend one click root method for this. If you want, I can post/link the patched boot.img i made with magisk. Mine boots with it and have confirmed root.
Click to expand...
Click to collapse
That would be great if you could share that patched boot.img......it is for the XT2163-4 MOTO G PURE correct?
Gamekeeper408 said:
That would be great if you could share that patched boot.img......it is for the XT2163-4 MOTO G PURE correct?
Click to expand...
Click to collapse
Agent_Orange1488 said:
I feel your pain! Had mine a few days and of course came to XDA immediately to find the DL on this joint but no luck... Ya I definitely don't recommend one click root method for this. If you want, I can post/link the patched boot.img i made with magisk. Mine boots with it and have confirmed root.
Click to expand...
Click to collapse
I would also like the patched boot.img if it is for the XT2163-4. Thanks
Hey boys I actually got rid of the moto g pure...for now at least lol! GREAT phone and I would be willing to get it back once there is some dev work done on it...will definitely be watching the threads on it. Good luck boys!!!
Hi
I read the above posts, and it seems like even if I am able to root it using Magisk, I won't be able to flash it with custom rom?
Thank you Agent_Orange1488 for the posts.

Motorola Droid Razr XT910 stuck on Logo

Hi, as said in the title, my Motorola XT910 is stuck on the logo, and will not boot, even after charging, and letting it do its thing overnight. I tried everything I could, including trying to wipe the cache via recovery mode, and I do not have access to it via adb in any ways. The only communication I can establish between it and my computer is via fastboot. The RSD Software doesn't recognize it either, though it appears on the computer as "ADB Device". Biggest problem is, I have seen threads from years ago on other forums, all over the internet with people having this issue, some had it fixed via a factory reset, some had to send it back. Obviously, I cannot send it back to motorola, as for the factory reset, I really cannot do it, since my whole objective of making this phone function again was to recover old very important videos and photos on it, which is rendered impossible due to android not starting.
I really hope someone has a solution (does anyone still even come by these threads ?).
Thanks in Advance,
Dylan.
LaMontreBelge said:
Hi, as said in the title, my Motorola XT910 is stuck on the logo, and will not boot, even after charging, and letting it do its thing overnight. I tried everything I could, including trying to wipe the cache via recovery mode, and I do not have access to it via adb in any ways. The only communication I can establish between it and my computer is via fastboot. The RSD Software doesn't recognize it either, though it appears on the computer as "ADB Device". Biggest problem is, I have seen threads from years ago on other forums, all over the internet with people having this issue, some had it fixed via a factory reset, some had to send it back. Obviously, I cannot send it back to motorola, as for the factory reset, I really cannot do it, since my whole objective of making this phone function again was to recover old very important videos and photos on it, which is rendered impossible due to android not starting.
I really hope someone has a solution (does anyone still even come by these threads ?).
Thanks in Advance,
Dylan.
Click to expand...
Click to collapse
RSD lite doesn't work with most Windows 10 machines, use Windows 7. http://forum.xda-developers.com/showpost.php?p=59348530&postcount=6
If you want to save data you need to modify the .XML file if using RSD Lite
Lots of issues can cause a boot loop, bad battery, bad app, bad hardware... even a bad charger or USB cable.
Try [Utility] - = MotoFlashPro =
Hi, thanks for replying, I took note of the software not functionning with windows 10, do you think it will work if I run 7 in VmWare and pass the phone through or do I absolutely have to use a physical 7 machine ?
Also, I really cannot make a factory cable like the one pictured in the post you linked, since none of my cables permit such a modification (the fifth pin does not have a spot to solder onto).
About the bootloop, well I'm not sure it really is one, since it doesn't loop at all, it just stays on the starting screen.
It shouldn't be a battery problem since even when giving power straight to the battery terminals, it does not boot, though the fastboot thing says "battery ok".
It shouldn't be a bad app either since last time I used the phone, like 3 years ago before I broke the screen which I replaced recently, it worked perfectly fine, and obviously I could not install an app in the meantime. The battery just ran down to 0 volts but I managed to make it work again. And what do you mean by bad charger ? Something like not powerful enough perhaps ?
LaMontreBelge said:
Hi, thanks for replying, I took note of the software not functionning with windows 10, do you think it will work if I run 7 in VmWare and pass the phone through or do I absolutely have to use a physical 7 machine ?
Also, I really cannot make a factory cable like the one pictured in the post you linked, since none of my cables permit such a modification (the fifth pin does not have a spot to solder onto).
About the bootloop, well I'm not sure it really is one, since it doesn't loop at all, it just stays on the starting screen.
It shouldn't be a battery problem since even when giving power straight to the battery terminals, it does not boot, though the fastboot thing says "battery ok".
It shouldn't be a bad app either since last time I used the phone, like 3 years ago before I broke the screen which I replaced recently, it worked perfectly fine, and obviously I could not install an app in the meantime. The battery just ran down to 0 volts but I managed to make it work again. And what do you mean by bad charger ? Something like not powerful enough perhaps ?
Click to expand...
Click to collapse
Hi again, quick update, I plugged it into my Windows Xp machine as I do not have a windows 7 computer, and it appeared. Also, could you please tell me what to change in the xml file in order to keep the data ?
Please, are you there ? I really need this help with the XML file, what do I need to edit ? I got the phone to be recognized in windows, even in rsd lite, i just need to know what to edit in the file
LaMontreBelge said:
Please, are you there ? I really need this help with the XML file, what do I need to edit ? I got the phone to be recognized in windows, even in rsd lite, i just need to know what to edit in the file
Click to expand...
Click to collapse
I've never had to use RSD Lite, and you might be better off waiting for him to respond incase I'm wrong (haven't touched this phone in a while). But I've done some digging and heard you can remove the line near the end of that XML file that goes something like
Code:
<step operation="erase" partition="userdata"/>
and it should skip the data wipe. I don't think it's necessary to remove the ones for cache and stuff. It might be a bad idea.
Smu1zel said:
I've never had to use RSD Lite, and you might be better off waiting for him to respond incase I'm wrong (haven't touched this phone in a while). But I've done some digging and heard you can remove the line near the end of that XML file that goes something like
Code:
<step operation="erase" partition="userdata"/>
and it should skip the data wipe. I don't think it's necessary to remove the ones for cache and stuff. It might be a bad idea.
Click to expand...
Click to collapse
Thanks for the info, I will indeed wait for him to reply, but i just checked in the XML file, and I do not have that line anywhere in the file. Does that mean it is incomplete or does this one just default to not erasing ? Also, this is the only file I could find that is a perfect match for my french market xt910.
LaMontreBelge said:
Thanks for the info, I will indeed wait for him to reply, but i just checked in the XML file, and I do not have that line anywhere in the file. Does that mean it is incomplete or does this one just default to not erasing ? Also, this is the only file I could find that is a perfect match for my french market xt910.
Click to expand...
Click to collapse
Also, I just checked in the other file I found, for an english-languaged model this time, it does have these lines, but is only 560mb instead of the 800 something of my french file
LaMontreBelge said:
Thanks for the info, I will indeed wait for him to reply, but i just checked in the XML file, and I do not have that line anywhere in the file. Does that mean it is incomplete or does this one just default to not erasing ? Also, this is the only file I could find that is a perfect match for my french market xt910.
Click to expand...
Click to collapse
Huh, yeah I don't really know then. The model I have is the XT912 (Verizon). I just got this info from a thread for a newer Moto. It could very well just simply not wipe, but I wouldn't go ahead and try incase you end up actually wiping it permanently. I'm not an expert at all, so I'd just wait until he gives you advice. Does this French firmware have similar lines like that for cache or other partitions? It might be in a completely different format then what I'm looking at. But I doubt it's corrupt.
Smu1zel said:
Huh, yeah I don't really know then. The model I have is the XT912 (Verizon). I just got this info from a thread for a newer Moto. It could very well just simply not wipe, but I wouldn't go ahead and try incase you end up actually wiping it permanently. I'm not an expert at all, so I'd just wait until he gives you advice. Does this French firmware have similar lines like that for cache or other partitions? It might be in a completely different format then what I'm looking at.
Click to expand...
Click to collapse
Actually I think the xt912 is pretty much identical unless I'm mistaking something. But either way, I do appreciate your cautiousness about the subject. Yes exactly I really cannot afford to lose the data that remains on the phone. Actually yes it does seem to have fairly similar lines, here have a look, on the left is the french firmware and the right the international. Now, I do not know what the files you're used to working with look like, but they may very well have similar if not identical lines.
Edit: I just re-read your question and realized I completely misunderstood what you asked. No, the french version doesn't have formatting lines at all. Deeply sorry for this misunderstanding.
LaMontreBelge said:
Actually I think the xt912 is pretty much identical unless I'm mistaking something. But either way, I do appreciate your cautiousness about the subject. Yes exactly I really cannot afford to lose the data that remains on the phone. Actually yes it does seem to have fairly similar lines, here have a look, on the left is the french firmware and the right the international. Now, I do not know what the files you're used to working with look like, but they may very well have similar if not identical lines.
Edit: I just re-read your question and realized I completely misunderstood what you asked. No, the french version doesn't have formatting lines at all. Deeply sorry for this misunderstanding.
Click to expand...
Click to collapse
I've noticed the left one is a "1FF" firmware. Which from what I've looked up, is supposed to not have the erasing lines. While the "CFC" ones are. Which is why the right one has those. But I've noticed the left firmware has what seems to be Gingerbread. I don't know if dirty flashing an older firmware will cause issues, if it's even possible. I've found an old thread on droidforums where someone tried to go back to ICS from that JB leak and ended up bricking. I don't think I can post links because I haven't posted 10 times unless they changed something.
Smu1zel said:
I've noticed the left one is a "1FF" firmware. Which from what I've looked up, is supposed to not have the erasing lines. While the "CFC" ones are. Which is why the right one has those. But I've noticed the left firmware has what seems to be Gingerbread. I don't know if dirty flashing an older firmware will cause issues, if it's even possible. I've found an old thread on droidforums where someone tried to go back to ICS from that JB leak and ended up bricking. I don't think I can post links because I haven't posted 10 times unless they changed something.
Click to expand...
Click to collapse
Actually, the phone is still on gingerbread (2.3.5) as I never found updates when it still worked, so this shouldn't be an issue (hopefully) and okay, thanks for the info, so it means my file is sound, right?
LaMontreBelge said:
Actually, the phone is still on gingerbread (2.3.5) as I never found updates when it still worked, so this shouldn't be an issue (hopefully) and okay, thanks for the info, so it means my file is sound, right?
Click to expand...
Click to collapse
I believe the file should be good unless you somehow got a bad download or something. But it seems 2.3.5 and 2.3.6 have different bootloader versions, and it looks like the firmware on the left doesn't have the "mbm" stuff. The last thing you need is a hard brick, so I'd be pretty hesitant to flash unless someone who has more knowledge tells you it's okay. I'm guessing you'd have to find a French CFC firmware and edit out that userdata wipe line (if that even works) or find a 1FF 2.3.5 firmware with an identical bootloader.
Smu1zel said:
I believe the file should be good unless you somehow got a bad download or something. But it seems 2.3.5 and 2.3.6 have different bootloader versions, and it looks like the firmware on the left doesn't have the "mbm" stuff. The last thing you need is a hard brick, so I'd be pretty hesitant to flash unless someone who has more knowledge tells you it's okay. I'm guessing you'd have to find a French CFC firmware and edit out that userdata wipe line (if that even works) or find a 1FF 2.3.5 firmware with an identical bootloader.
Click to expand...
Click to collapse
Alright, then I won't flash it, just in case. Also, do you have any way to check if the bootloader version is different ? If yes, I could check it. And alright, I'll try finding another file that happens to be on 2.3.5. Thanks again for the info sir.
LaMontreBelge said:
Alright, then I won't flash it, just in case. Also, do you have any way to check if the bootloader version is different ? If yes, I could check it. And alright, I'll try finding another file that happens to be on 2.3.5. Thanks again for the info sir.
Click to expand...
Click to collapse
I hyperlinked a link I found with some info on that. I just looked at the build number of the versions listed in that doc, looked at the bootloader version next to it, and looked at the firmware's filename. In your case, "6.5.1-167" has bootloader version "0A.6C" while 2.3.5 with the build number "6.5.1_73" has bootloader version "0A.66". My source was this Doc https://docs.google.com/document/d/1CWZU-4i7jWO26RXJ7YFJV-Ze-mJrDaTuCuVI-ZwxDBE/. I honestly don't know if the bootloader matters, but I wouldn't want to risk it in case it makes the situation worse. Hopefully shadow can help you out.
https://forum.xda-developers.com/t/index-motorola-droid-razr-2012.3023837/post-58684547
Here's a pinned thread with some firmwares if it helps any.
Smu1zel said:
I hyperlinked a link I found with some info on that. I just looked at the build number of the versions listed in that doc, looked at the bootloader version next to it, and looked at the firmware's filename. In your case, "6.5.1-167" has bootloader version "0A.6C" while 2.3.5 with the build number "6.5.1_73" has bootloader version "0A.66". My source was this Doc https://docs.google.com/document/d/1CWZU-4i7jWO26RXJ7YFJV-Ze-mJrDaTuCuVI-ZwxDBE/. I honestly don't know if the bootloader matters, but I wouldn't want to risk it in case it makes the situation worse. Hopefully shadow can help you out.
Click to expand...
Click to collapse
Okay, i just took a look at the doc linked, and I have no idea how you found it, but it is mind boggling. All the roms, listed, just like that. Thank you so much. And yes indeed the bootloader is different, and I wouldn't risk it. I'll keep looking for the 2.3.5 ROM, but for now it seems like a lost cause. Perhaps they have it over on the Motorola forums. I'll make a thread later today.
Smu1zel said:
I hyperlinked a link I found with some info on that. I just looked at the build number of the versions listed in that doc, looked at the bootloader version next to it, and looked at the firmware's filename. In your case, "6.5.1-167" has bootloader version "0A.6C" while 2.3.5 with the build number "6.5.1_73" has bootloader version "0A.66". My source was this Doc https://docs.google.com/document/d/1CWZU-4i7jWO26RXJ7YFJV-Ze-mJrDaTuCuVI-ZwxDBE/. I honestly don't know if the bootloader matters, but I wouldn't want to risk it in case it makes the situation worse. Hopefully shadow can help you out.
Click to expand...
Click to collapse
Also, in the document there is a link that leads to an archive, but no files are downloadable, do you happen to have any of them by chance ?
Smu1zel said:
https://forum.xda-developers.com/t/index-motorola-droid-razr-2012.3023837/post-58684547
Here's a pinned thread with some firmwares if it helps any.
Click to expand...
Click to collapse
This thread does indeed help a little bit, but the firmware center link does not, as it is where i got my 2.3.6 ROM from, and as far as I know, is the only french one. Honestly I do not care if it's an English one, I just want to make sure that it won't mess up the phone
LaMontreBelge said:
Also, in the document there is a link that leads to an archive, but no files are downloadable, do you happen to have any of them by chance ?
Click to expand...
Click to collapse
Yeah I think those links might be out of date. Go under "XT910" and look at some of the links. Also I found that doc under that section.
https://forum.xda-developers.com/t/index-motorola-droid-razr-2012.3023837/post-58684547
I hope I'm not leading you down a wrong path, hopefully he responds soon. Maybe the bootloader doesn't matter, I don't know.

Categories

Resources