Related
Hi
I have been playing around with my Atrix HD for quite a while now, installing almost all custom roms out there for MB866 (Found Gummy and Carbon to be the best, batakang and holoblur never worked for me).
Restored back to stock using RSD Lite many times (after editing the xml file, no problems)
The bootloader was of course unlocked during "all that".
Now here is the problem. After restoring to stock 4.1.1 (98.4.20.MB886.ATT.en.US) using RSD Lite, I updated to 98.5.38.MB886.ATT.en.US (small 6.2 MB Update recently released).Worked fine till here.
Then I downgraded to ICS and it also worked fine. What made things worse was when I checked for updates via About Phone--> System Updates and it prompted for an Update 98.4.20.MB886.ATT.en.US (the same i used to flash via RSD). But when the download finished, the phone is permanently stuck in fastboot mode with the following message:
----------------------------------------------
AP Fastboot Flash Mode (s)
10.9B(*) (sha-2e68372, 2012-11-17 23:33:08)
eMMC Info: Size 8GB
Device is LOCKED. Status Code:0
Battery OK
Transfer Mode: USB Connected
downgraded security version
update gpt_main version failed
Failed to hab check for gpt_backup: 0x35
failed to load GPT
CID Read Failure
Invalid CID Status 0x69
No SP Partition found
Fastboot Reason: Invalid GPT
----------------------------------------------
You can see the phone is locked and RSD Lite doesent work at all giving "phone returmed fail" or " invalid partition error (battery is charged atleast 70%).
Any help in restoring the phone to "something" will be highly appreciated.
One of the problem is that i cannot find stock files for the latest 98.5.38.MB886.ATT.en.US update anywhere
Secondly is there any way to unlock Bootloader in fastboot?
capricorn85 said:
Hi
I have been playing around with my Atrix HD for quite a while now, installing almost all custom roms out there for MB866 (Found Gummy and Carbon to be the best, batakang and holoblur never worked for me).
Restored back to stock using RSD Lite many times (after editing the xml file, no problems)
The bootloader was of course unlocked during "all that".
Now here is the problem. After restoring to stock 4.1.1 (98.4.20.MB886.ATT.en.US) using RSD Lite, I updated to 98.5.38.MB886.ATT.en.US (small 6.2 MB Update recently released).Worked fine till here.
Then I downgraded to ICS and it also worked fine. What made things worse was when I checked for updates via About Phone--> System Updates and it prompted for an Update 98.4.20.MB886.ATT.en.US (the same i used to flash via RSD). But when the download finished, the phone is permanently stuck in fastboot mode with the following message:
----------------------------------------------
AP Fastboot Flash Mode (s)
10.9B(*) (sha-2e68372, 2012-11-17 23:33:08)
eMMC Info: Size 8GB
Device is LOCKED. Status Code:0
Battery OK
Transfer Mode: USB Connected
downgraded security version
update gpt_main version failed
Failed to hab check for gpt_backup: 0x35
failed to load GPT
CID Read Failure
Invalid CID Status 0x69
No SP Partition found
Fastboot Reason: Invalid GPT
----------------------------------------------
You can see the phone is locked and RSD Lite doesent work at all giving "phone returmed fail" or " invalid partition error (battery is charged atleast 70%).
Any help in restoring the phone to "something" will be highly appreciated.
One of the problem is that i cannot find stock files for the latest 98.5.38.MB886.ATT.en.US update anywhere
Secondly is there any way to unlock Bootloader in fastboot?
Click to expand...
Click to collapse
"fastboot oem fb_mode_clear" should get it to stop booting into fastboot mode
The problem is the gpt partition is security locked and one of the fastboot commands thrown is to lock the phone into fastboot mode for every boot until the flashes are done. The command above is the one used to revert the first one (fastboot oem fb_mode_set if you're curious). Your bootloader isn't, or shouldn't I should say, locked again. The RAZR HD does the same thing if you directly flash a fastboot without removing the bad partitions and commands for unlocked phones flashing non-stock fastboots. The bad ones are the gpt partition and the oem fb* commands....there are a lot of guides that explain this and Mythtools (in AHD Developer forums) will do it all for you.
skeevydude said:
"fastboot oem fb_mode_clear" should get it to stop booting into fastboot mode
The problem is the gpt partition is security locked and one of the fastboot commands thrown is to lock the phone into fastboot mode for every boot until the flashes are done. The command above is the one used to revert the first one (fastboot oem fb_mode_set if you're curious). Your bootloader isn't, or shouldn't I should say, locked again. The RAZR HD does the same thing if you directly flash a fastboot without removing the bad partitions and commands for unlocked phones flashing non-stock fastboots. The bad ones are the gpt partition and the oem fb* commands....there are a lot of guides that explain this and Mythtools (in AHD Developer forums) will do it all for you.
Click to expand...
Click to collapse
fastboot oem fb_mode_clear doesnt work, i tried it before as well, mythtools also cannt help as device status is locked and if rsd cannt flash it i believe myth also cannt.and the reason i say its locked is because it does not respond to any oem command.
it probably got locked after the ota which failed
if i could find fxz for 98.5.38.MB886.ATT.en.US, it may be restored otherwise is there any way around to unlock bootloder from fastboot??
these are the only two options i can think of amoungst which later is has the least probability.......
capricorn85 said:
fastboot oem fb_mode_clear doesnt work, i tried it before as well, mythtools also cannt help as device status is locked and if rsd cannt flash it i believe myth also cannt.and the reason i say its locked is because it does not respond to any oem command.
it probably got locked after the ota which failed
if i could find fxz for 98.5.38.MB886.ATT.en.US, it may be restored otherwise is there any way around to unlock bootloder from fastboot??
these are the only two options i can think of amoungst which later is has the least probability.......
Click to expand...
Click to collapse
There isn't an fxz for that update yet. The one I would be able to make wouldn't include the correct gpt partition because I've flashed the Nextel fxz and none of the other gpt partitions from our stock fxz's will flash on my phone (there's a security lock on that partition). Though I know that between two or three of us here on xda, an fxz could be made with all the correct partitions from the update.
If you're positive that you were unlocked then just flash the Bell or Nextel 4.1.2 fxz's. They're not vulnerable to the heartbleed exploit which is the main reason that AT&T released the 98.5 update to begin with.
Have you tried "fastboot continue"? You might get lucky and the phone will at least boot up. And tried booting to recovery? Boot menu?
You can only unlock the bootloader from a rooted, running phone with ADB enabled. Can't do it in recovery or fastboot mode (unless you have a developer edition).
skeevydude said:
There isn't an fxz for that update yet. The one I would be able to make wouldn't include the correct gpt partition because I've flashed the Nextel fxz and none of the other gpt partitions from our stock fxz's will flash on my phone (there's a security lock on that partition). Though I know that between two or three of us here on xda, an fxz could be made with all the correct partitions from the update.
If you're positive that you were unlocked then just flash the Bell or Nextel 4.1.2 fxz's. They're not vulnerable to the heartbleed exploit which is the main reason that AT&T released the 98.5 update to begin with.
Have you tried "fastboot continue"? You might get lucky and the phone will at least boot up. And tried booting to recovery? Boot menu?
You can only unlock the bootloader from a rooted, running phone with ADB enabled. Can't do it in recovery or fastboot mode (unless you have a developer edition).
Click to expand...
Click to collapse
i tried bell's 4.1.2 earlier thinking the same as you said,but didnt work either, wont boot to recovery or boot menu.....
fastboot continue also takes to the old prompt...
capricorn85 said:
i tried bell's 4.1.2 earlier thinking the same as you said,but didnt work either, wont boot to recovery or boot menu.....
fastboot continue also takes to the old prompt...
Click to expand...
Click to collapse
IIRC, the Nextel (Mex Retail) is the highest version we have unless the new AT&T one supersedes it.
I've only seen this issue one other time over at the RAZR HD forums. With the latest KK OTA they had, his failed and the phone booted to a similar screen you have. Nothing has worked for that guy yet that I'm aware of (haven't checked in about a week now).
Have you tried manually flashing an fxz, not with RSD or Myth (though Myth does flash manually via a script but it skips the gpt partition, IIRC). I'd start with the ATT fxz and if it fails manually then I'd flash the Nextel one...after that I'm out of ideas.
skeevydude said:
IIRC, the Nextel (Mex Retail) is the highest version we have unless the new AT&T one supersedes it.
I've only seen this issue one other time over at the RAZR HD forums. With the latest KK OTA they had, his failed and the phone booted to a similar screen you have. Nothing has worked for that guy yet that I'm aware of (haven't checked in about a week now).
Have you tried manually flashing an fxz, not with RSD or Myth (though Myth does flash manually via a script but it skips the gpt partition, IIRC). I'd start with the ATT fxz and if it fails manually then I'd flash the Nextel one...after that I'm out of ideas.
Click to expand...
Click to collapse
Came here after trying all that
Tried manually flashing but the phone returns FAIL on EVERY command, same with myth tools it executes but nothing really happen in the phone, dont know what went so wrong with the OTA
i am just confused if i should let it be or keep trying until i find a solution
COuld battery charge level be the problem, when it all started it was more than 70 percent and i didnt keep it on for long. it says battery ok but dont know whats the exact battery level as fastboot oem battery-status or voltage level are also restricted
Well, it seems that skeevydude told you all I want to say
Solved: Using Nextel (Mex Retail)
Thanks all for your replies
The device is alive now after restoring to Mexican Retail using RSD (editing the xml file and deleting ONLY the two lines having getvar)
Myth Tools never worked, RSD DID!
BTW the mexican retail is much much better than the ATT version because:
It gets rid of the ATT bloatware
SPecially the att address book
Hotspot is working out of the box
its speedier
android version is upgraded (4.1.2 instead of 4.1.1)
provides an option of manually switching to 2g/3g
and much more
thanks skeevydude, nextel was the last option remaining anyway...........and it automatically fixed the gpr issue
capricorn85 said:
Thanks all for your replies
The device is alive now after restoring to Mexican Retail using RSD (editing the xml file and deleting ONLY the two lines having getvar)
Myth Tools never worked, RSD DID!
BTW the mexican retail is much much better than the ATT version because:
It gets rid of the ATT bloatware
SPecially the att address book
Hotspot is working out of the box
its speedier
android version is upgraded (4.1.2 instead of 4.1.1)
provides an option of manually switching to 2g/3g
and much more
thanks skeevydude, nextel was the last option remaining anyway...........and it automatically fixed the gpr issue
Click to expand...
Click to collapse
Isn't it already stated somewhere that if you are going to downgrade or change versions, you need to delete those lines anyways?
palmbeach05 said:
Isn't it already stated somewhere that if you are going to downgrade or change versions, you need to delete those lines anyways?
Click to expand...
Click to collapse
Yes it is, but thats only for upgrade, if downgrading the gpt line also need to be deleted, as i was not downgrading, only those two were required to be deleted which need to be specifically mentioned to avoid confusion
capricorn85 said:
Yes it is, but thats only for upgrade, if downgrading the gpt line also need to be deleted, as i was not downgrading, only those two were required to be deleted which need to be specifically mentioned to avoid confusion
Click to expand...
Click to collapse
I told ya Mex Retail would work....
skeevydude said:
I told ya Mex Retail would work....
Click to expand...
Click to collapse
It is worth a shot for me too!
I have RSDLite and attempted to flash. It gives me error about unknown <getvar>. Deleted those line(s) according to another post I found.
Then everything passes but I am stuck on the Fastboot Flash Mode?
God I will be happy when uncle same gets through with my son so he can help is ole man, lol.
---------- Post added at 06:14 PM ---------- Previous post was at 05:55 PM ----------
PROGRESS! I recalled skeevydude saying to stay alway from front USB ports and moved to back one and I now also have the Mex Retail version working. What a relief.
Now the bearing question is should I move on to another version like carbon or holoblur?
If ok to stay with this version, meaning will NOT get busted out by AT&T by using hotspot?
What do you recommend skeevydude?
Thank you so so so much.
Woody
Mexico Retail link
can someone provide me any link of Mexico Retail stock rom? Please.
ErickST18 said:
can someone provide me any link of Mexico Retail stock rom? Please.
Click to expand...
Click to collapse
http://sbf.droid-developers.org/phone.php?device=7
quasihellfish said:
http://sbf.droid-developers.org/phone.php?device=7
Click to expand...
Click to collapse
Thanks man
Pleas hlep me for alive my set thanks advance
dear i have a working phone MB886 with jellybean 4.1.1 unfortunately i flash the custom ROM of kitkat but set is dead i tired to alive the phone with myth tools rsd lite but no success my phone boot-loader locked i try to unlock the boot loader but nothing please anybody send ma working link of flash file Mexican or any other which are flash with rsd lite easily i am very thankful of that plzzzzzzzzzzz customer on my neck sorry for my bad English
shamshadhashmi said:
dear i have a working phone MB886 with jellybean 4.1.1 unfortunately i flash the custom ROM of kitkat but set is dead i tired to alive the phone with myth tools rsd lite but no success my phone boot-loader locked i try to unlock the boot loader but nothing please anybody send ma working link of flash file Mexican or any other which are flash with rsd lite easily i am very thankful of that plzzzzzzzzzzz customer on my neck sorry for my bad English
Click to expand...
Click to collapse
Please stop whining and being pathetic and actually search for moto sbf files. A new site popped up and comes up very easily. No need to make us die of laughter at someone begging for an sbf like a guy begging to get with a girl b/c he's thirsty. Smh lol
Sent from my ATRIX HD using XDA Free mobile app
need working link of file
i search everywhere but no file found i need file if anybody have so please share with me or upload thanks
quasihellfish said:
http://sbf.droid-developers.org/phone.php?device=7
Click to expand...
Click to collapse
Need 4.1.1..where can I find it? Tyvm
Hi guys, yesterday i tried to install ROM "XT1058_GHOST_RETBR_5.1_LPA23.12-15_cid12_CFC.xml" to my moto X 1058 At&T (android 4.4.4) with RSD litle.
It failed and now i only can turn on the phone and it goes to bootloader menu and i cant do anything. I can connect it to my PC and RSD detect it but i cant put any kind of ROM ((
I know that my moto x is not dead yet i have hope u.u :crying:
Please someone can help me? :crying:
PS: SORRY MY ENGLISH
PS2: I ADD A SCREENSHOT WITH SOME DETAILS ABOUT MY MOTO X after DO what i explain.
First off, you have an ATT XT1058... why are you trying to flash XT1058_GHOST_RETBR.... which is for RETAIL BRAZIL!?!
Is your bootloader locked or unlocked?
EDIT: never mind, I read here -> http://forum.xda-developers.com/showpost.php?p=61834453&postcount=78 then you have a locked bootloader...
so my advice...
Try to boot into stock recovery, and wipe cache, and reboot.
If that doesn't work.. try a factory reset (also from inside stock recovery) NOTE: this will delete your data, apps, pix, music, anything on the phone's /sdcard... etc..
Next, would be to try to re-flash Stock ATT 4.4.4 SBF using mfastboot (see the requirements and option 5 in post 2 of -> http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425 )
If that doesn't work... then you have no choice but to wait until the 5.1 SBF for ATT XT1058 leaks and is posted... and flash that using mFastboot.
KidJoe said:
First off, you have an ATT XT1058... why are you trying to flash XT1058_GHOST_RETBR.... which is for RETAIL BRAZIL!?!
Is your bootloader locked or unlocked?
EDIT: never mind, I read here -> http://forum.xda-developers.com/showpost.php?p=61834453&postcount=78 then you have a locked bootloader...
so my advice...
Try to boot into stock recovery, and wipe cache, and reboot.
If that doesn't work.. try a factory reset (also from inside stock recovery) NOTE: this will delete your data, apps, pix, music, anything on the phone's /sdcard... etc..
Next, would be to try to re-flash Stock ATT 4.4.4 SBF using mfastboot (see the requirements and option 5 in post 2 of -> http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425 )
If that doesn't work... then you have no choice but to wait until the 5.1 SBF for ATT XT1058 leaks and is posted... and flash that using mFastboot.
Click to expand...
Click to collapse
Into bootloader any option work, only for get pictures from IMEI, ID, etc.
I will try re flash stock ATT using mfastboot cause trying do this in RSD doesnt work
One friend told me he solved his problem unlocking bootloader by a program that unlock it automatic, then he instaled android 4.4.4.
My question is that if can i do what you are telling me cause in stock recovery appear 30.BE unde AP Fastboot Flash Mode (s) line. And it mean 30.BE= android 5.1 brazil so maybe i have to do a downgrade?
i dont know if you undestand me.
Thanks for your time
NEW INFO
i will writte more datails:
After i tryed install failed Brasil ROM the info about my cellphone is the next:
Bootloader version: 30.BE (sha-34b7ccb, 2015-04-22 12:57:17)
Bootloader is: LOCKED (and can´t be unlocked by motorola steps cause my moto x is AT&T)
Thinking about it and looking for a lot places from 2 days i have next conclusion:
How now i have bootloader version "30.BE" i have two options:
First: Downgrade android but i need unlocked bootloader for do it.
Second option: Wait until ROM android 5.1 by AT&T (i read update is ready but i cant find ROM, i only found ZIP for put in my internal memory and update android from old android but i cant access to my internal memory cause my PC does recognized like memory device)
What do you think guys?
zloopa said:
Into bootloader any option work, only for get pictures from IMEI, ID, etc.
I will try re flash stock ATT using mfastboot cause trying do this in RSD doesnt work
One friend told me he solved his problem unlocking bootloader by a program that unlock it automatic, then he instaled android 4.4.4.
My question is that if can i do what you are telling me cause in stock recovery appear 30.BE unde AP Fastboot Flash Mode (s) line. And it mean 30.BE= android 5.1 brazil so maybe i have to do a downgrade?
i dont know if you undestand me.
Thanks for your time
Click to expand...
Click to collapse
I can tell that English (or at least USA Engish) isn't your primary language, so hopefully you can understand me too
An ATT XT1058 that has never been updated to 4.4.4 or above can use Sunshine to unlock the bootloader. Since you've had 4.4.4 and above on there, you can't unlock.
30.BE is a 5.1 bootloader. That is part of your problem. Somehow, parts of the XT1058_GHOST_RETBR... 5.1 SBF did flash to your phone, but not all of it..
Are you sure you didn't unlock your bootloader? Boot to FastbootAP/Bootloader screen and tell me what you see.. Do you see LOCKED STATUS 0, or Locked Status 2, or Unlocked Status 3?
---------- Post added at 07:23 AM ---------- Previous post was at 07:18 AM ----------
zloopa said:
i will writte more datails:
After i tryed install failed Brasil ROM the info about my cellphone is the next:
Bootloader version: 30.BE (sha-34b7ccb, 2015-04-22 12:57:17)
Bootloader is: LOCKED (and can´t be unlocked by motorola steps cause my moto x is AT&T)
Thinking about it and looking for a lot places from 2 days i have next conclusion:
How now i have bootloader version "30.BE" i have two options:
First: Downgrade android but i need unlocked bootloader for do it.
Second option: Wait until ROM android 5.1 by AT&T (i read update is ready but i cant find ROM, i only found ZIP for put in my internal memory and update android from old android but i cant access to my internal memory cause my PC does recognized like memory device)
What do you think guys?
Click to expand...
Click to collapse
Your first option is not correct. You can't fully downgrade, even with an unlocked bootloader. You can partially downgrade, but that isn't 100% safe. There is a very good chance it wont work, or you'll brick even worse when trying to downgrade, or later when taking the OTA.
For your second option.. Correct. As of yet, the FULL SBF of 5.1 for ATT hasn't leaked. Only the OTA Zip file which is an incremental update, not a full update, and therefore can't be used to recover in this state. Sit tight. Its only a matter of time.
I know you probably want to use your phone NOW, so waiting isn't a good option... but it is likely your only SAFE option right now.
KidJoe said:
I can tell that English (or at least USA Engish) isn't your primary language, so hopefully you can understand me too
An ATT XT1058 that has never been updated to 4.4.4 or above can use Sunshine to unlock the bootloader. Since you've had 4.4.4 and above on there, you can't unlock.
30.BE is a 5.1 bootloader. That is part of your problem. Somehow, parts of the XT1058_GHOST_RETBR... 5.1 SBF did flash to your phone, but not all of it..
Are you sure you didn't unlock your bootloader? Boot to FastbootAP/Bootloader screen and tell me what you see.. Do you see LOCKED STATUS 0, or Locked Status 2, or Unlocked Status 3?
---------- Post added at 07:23 AM ---------- Previous post was at 07:18 AM ----------
Your first option is not correct. You can't fully downgrade, even with an unlocked bootloader. You can partially downgrade, but that isn't 100% safe. There is a very good chance it wont work, or you'll brick even worse when trying to downgrade, or later when taking the OTA.
For your second option.. Correct. As of yet, the FULL SBF of 5.1 for ATT hasn't leaked. Only the OTA Zip file which is an incremental update, not a full update, and therefore can't be used to recover in this state. Sit tight. Its only a matter of time.
I know you probably want to use your phone NOW, so waiting isn't a good option... but it is likely your only SAFE option right now.
Click to expand...
Click to collapse
I never tried to unlock bootloader and before start to trying to upgrade to 5.1 brazil, bootloader appear "DEVICE IS: LOCKED" and now appear the same "LOCKED AND STATUS 0". (check the image if you can)
The question now is: maybe you know if the solution is wait until 5.1 Android for AT&T or even if i have this ROM maybe exist a possibility that my moto doesn't get fix? Maybe the question is hard to confirm 100% but maybe it is a 90 % possible that my moto get fix with this way.
I love this phone but i was too newbie and I confused ways to change ANDROID by mys XPERIA and HTC's phones.
zloopa said:
I never tried to unlock bootloader and before start to trying to upgrade to 5.1 brazil, bootloader appear "DEVICE IS: LOCKED" and now appear the same "LOCKED AND STATUS 0". (check the image if you can)
The question now is: maybe you know if the solution is wait until 5.1 Android for AT&T or even if i have this ROM maybe exist a possibility that my moto doesn't get fix? Maybe the question is hard to confirm 100% but maybe it is a 90 % possible that my moto get fix with this way.
I love this phone but i was too newbie and I confused ways to change ANDROID by mys XPERIA and HTC's phones.
Click to expand...
Click to collapse
I hate to say it, but yeah, you're likely stuck until an ATT 5.1 SBF is posted somewhere.
KidJoe said:
I hate to say it, but yeah, you're likely stuck until an ATT 5.1 SBF is posted somewhere.
Click to expand...
Click to collapse
I have this:
http://www.filefactory.com/file/2kmrq89bx1h/XT1058_GHOST_ATT_5.1_LPA23.12-21.1_cid1_CFC.xml.zip
What do you recommed to do?
Whit RSD or do you have some guide for fix my cellphone
zloopa said:
I have this:
http://www.filefactory.com/file/2kmrq89bx1h/XT1058_GHOST_ATT_5.1_LPA23.12-21.1_cid1_CFC.xml.zip
What do you recommed to do?
Whit RSD or do you have some guide for fix my cellphone
Click to expand...
Click to collapse
As I said earlier... flash using mfastboot (see the requirements and option 5 in post 2 of -> http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425 ) just use that 5.1 SBF... and I would consider including the mfastboot erase userdata command, or doing a factory reset after you flash... Yes it will erase your data, apps, SDCard, etc...
GHOST_ATT_5.1_LPA23.12-21.1_cid1_CFC.xml
also failed
error on GPT ..
Bootloader 30BE
accidentally flashed verizon Lollipop bootloader on it ..
now LP 5.1 ATT not working on it
aamszia said:
GHOST_ATT_5.1_LPA23.12-21.1_cid1_CFC.xml
also failed
error on GPT ..
Bootloader 30BE
accidentally flashed verizon Lollipop bootloader on it ..
now LP 5.1 ATT not working on it
Click to expand...
Click to collapse
Hi in same situation. Did u fixed it?
Hi guys,
I (and some of my friends) had a problem with XT1254:
1. We updated to 6.0.1 via recovery with update.zip. This process had successfully done.
2. Several felt something wrong with new 6.0.1 system, so they re-updated via recovery again (still the same update.zip). This made the system dead. They could not enter system, except bootloader and recovery. The problem is that source system needs to be Lollipop SU4TL-49 so the re-update process will fail.
3. I did like them and tried to find the solution from old methods:
- tried to downgrade to 5.1;
- tried to flash new 6.0.1 system.img;
- deleted some lines in "updater-script" and tried to sideload via recovery;
but all failed because of "invalid signed image" (for both RSD and fastboot). The partion, boot, kernel have been the newest ones.
4. I tried to downgrade my XT1060 to Kitkat (another mine), and it also failed with flashing system.img. I had to flash the Lollipop's system.img and the problem solved.
Conclusion:
1. Unlock bootloader and flash TWRP will solved the problem for XT1254. The phone could not boot to system so buying a unique key is the only solution (but how to buy?).
2. Wait for the 6.0.1 flash file (xml) then flash via RSD. Several security patches from Verizon may lock the downgrade process.
3. Can some one give other solutions?
Thanks guys!!!!
mr_5kool said:
Hi guys,
I (and some of my friends) had a problem with XT1254:
1. We updated to 6.0.1 via recovery with update.zip. This process had successfully done.
2. Several felt something wrong with new 6.0.1 system, so they re-updated via recovery again (still the same update.zip). This made the system dead. They could not enter system, except bootloader and recovery. The problem is that source system needs to be Lollipop SU4TL-49 so the re-update process will fail.
3. I did like them and tried to find the solution from old methods:
- tried to downgrade to 5.1;
- tried to flash new 6.0.1 system.img;
- deleted some lines in "updater-script" and tried to sideload via recovery;
but all failed because of "invalid signed image" (for both RSD and fastboot). The partion, boot, kernel have been the newest ones.
4. I tried to downgrade my XT1060 to Kitkat (another mine), and it also failed with flashing system.img. I had to flash the Lollipop's system.img and the problem solved.
Conclusion:
1. Unlock bootloader and flash TWRP will solved the problem for XT1254. The phone could not boot to system so buying a unique key is the only solution (but how to buy?).
2. Wait for the 6.0.1 flash file (xml) then flash via RSD. Several security patches from Verizon may lock the downgrade process.
3. Can some one give other solutions?
Thanks guys!!!!
Click to expand...
Click to collapse
me too
i updated to 6.0.1 via recovery with update.zip. This process had successfully done and re-updated via recovery again (still the same update.zip) and i factory reset tin recovery so it stuck screen 'erasing...'They could not enter system, except bootloader and recovery vesersion (6.0.1),can not into apply update sdcard , it turn e:\unkown volum path [sdcard]... and I did like them and tried to find the solution from old methods:
- tried to downgrade to 5.1;
- tried to flash new 6.0.1 system.img;
but all failed because of "invalid signed image" (for both RSD and fastboot). The partion, boot, kernel have been the newest ones.
Conclusion:
1. Unlock bootloader and flash TWRP will solved the problem for XT1254. The phone could not boot to system so buying a unique key is the only solution (but how to buy?).
2. Wait for the 6.0.1 flash file (xml) then flash via RSD. Several security patches from Verizon may lock the downgrade process.
3. Can some one give other solutions?
longbin said:
1. Unlock bootloader and flash TWRP will solved the problem for XT1254. The phone could not boot to system so buying a unique key is the only solution (but how to buy?).
2. Wait for the 6.0.1 flash file (xml) then flash via RSD. Several security patches from Verizon may lock the downgrade process.
3. Can some one give other solutions?
Click to expand...
Click to collapse
1. I have never heard of anyone selling bootloader unlock keys for the XT1254. If you want to unlock your bootloader, Sunshine is your only option, and as of right now it will only work on lollipop builds. If your phone is on marshmallow, Sunshine will not work. If your phone cannot boot, it won't work no matter what build you're on.
2. If your phone is bricked and on marshmallow, waiting for the full firmware package is your only option. However, a downgrade to a previous firmware with a locked bootloader isn't, and has never been, possible.
mr_5kool said:
Conclusion:
1. Unlock bootloader and flash TWRP will solved the problem for XT1254. The phone could not boot to system so buying a unique key is the only solution (but how to buy?).
2. Wait for the 6.0.1 flash file (xml) then flash via RSD. Several security patches from Verizon may lock the downgrade process.
3. Can some one give other solutions?
Thanks guys!!!!
Click to expand...
Click to collapse
unlock the bootloader and install TWRP BEFORE doing any updates, while still on Lollipop. That is the only safe, logical answer. An unlocked bootloader -- especially with custom recovery -- will let you do lot of things and is more forgiving of mistakes than a locked bootloader.
We keep telling people that and they won't believe us.
---------- Post added at 10:37 AM ---------- Previous post was at 10:32 AM ----------
TheSt33v said:
If your phone is bricked and on marshmallow, waiting for the full firmware package is your only option. However, a downgrade to a previous firmware with a locked bootloader isn't, and has never been, possible.
Click to expand...
Click to collapse
Right. Several people who didn't like Lollipop but preferred the original Kitkat "speed", "battery life" or whatever successfully downgraded back to 4.4.4 -- but only AFTER they unlocked their bootloader. Even then you have to make sure you don't flash the old gpt.bin in ADB, but downgrading is possible with an UNlocked bootloader.
Even when flashing XT1250 firmware over XT1254 or vice versa, it CAN be done with a locked bootloader, but if you mess something up you are in big trouble. UNlocked bootloader? Just do it again, correcting your mistake the next time.
---------- Post added at 10:43 AM ---------- Previous post was at 10:37 AM ----------
TheSt33v said:
1. I have never heard of anyone selling bootloader unlock keys for the XT1254.
Click to expand...
Click to collapse
There was a guy on some website who was selling some Verizon keys a long time ago, known as "the Chinaman". He disappeared.
China Middleman Back??
http://forum.xda-developers.com/moto-x/moto-x-qa/china-middleman-t2751177
dschill said:
Well the china man added me back on skype today. And sadly said that he can no longer get the codes and refunded my 45$ via paypal.
Heres a little bit of the skype transcipt
[12:08:22 PM] live:dschillinrecovery: k i just got the refund
[12:08:25 PM] live:dschillinrecovery: so you cant get the code any more?
[12:12:41 PM] VIP-UNLOCK: No time to deal with the accident, we default to a refund
[12:13:08 PM] VIP-UNLOCK: Sorry, goodbye
[12:13:32 PM] live:dschillinrecovery: Its alright. Thanks for the refund though. Let me know if you can ever get the codes again
Guess the best we can do for now is to wait for jcase and sunshine to release the 3.0 version.
Click to expand...
Click to collapse
and another thread discussing same guy:
http://forum.xda-developers.com/moto-x/general/4-1-vzw-att-moto-maker-bootloader-t2680651
The process seems to involve sending approximately $45 to a Chinese middle-man via eBay and another website, along with your IMEI and cell phone number, and you will receive an unlock code.
It seems like this is all one guy handling this process. Turnaround time seems to be 24-48 hours beginning to end.
Click to expand...
Click to collapse
Theory was that someone with access to Motorola's engineering software had a side business going. You know they unlock their bootloaders for testing and such. Someone with access to that software could make some money if they made sure they covered their tracks.
Also people who visited China were able to buy unlocked bootloader Droid Turbos well before Sunshine was released. One guy posted in this forum. In that case, it was probably pilfering some phones from the factory -- but again with unlocked bootloaders. So, there is some software out there somewhere, just kept under wraps.
Haha the Chinaman? Really? Sounds like an evil arms dealer from a 90's action movie. Man, if only the magic official bootloader unlocking software was leaked. That would be like Christmas times infinity.
TheSt33v said:
Haha the Chinaman? Really? Sounds like an evil arms dealer from a 90's action movie. Man, if only the magic official bootloader unlocking software was leaked. That would be like Christmas times infinity.
Click to expand...
Click to collapse
I updated my post to include XDA links. I can't find any examples of Droid Turbos being unlocked via this eBay "purchase" only other Verizon phones, but there are the legitimate reports of unlocked Droid Turbos for sale in China in the year prior to Sunshine being released November 2015. One guy even posted on here because he was trying to install CM12.1 at the time on his BOOTLOADER UNLOCKED Droid Turbo he had purchased in China.
Note the Chinese middleman guy was charging $45 for bootloader unlock at the time, and Sunshine only charges $25.
xml flash file is the last solution =))
@ChazzMatt: I think it's impossible to cross flash 1250 to 1254, but 1254 can flash to 1250
Doesn anybody know how much does usually takes for Verzion ( or whoever does it ) to release xml sbf firmware file? And do they release every? I need latest MCG24 or at least system file (s) is enough.
I have everything except system files, if anybody can provide system files or knows hot to convert ones from ota , I can make complete fastboot xml zip.
EDIT: System from OTA is not enough. If somebody can provide system / backup from MCG24 phone, I might be able to make it.
mr_5kool said:
@ChazzMatt: I think it's impossible to cross flash 1250 to 1254, but 1254 can flash to 1250
Click to expand...
Click to collapse
No, people have done both. One guy messaged me on Hangouts telling me what he did, so I know it can be done.
ChazzMatt said:
No, people have done both. One guy messaged me on Hangouts telling me what he did, so I know it can be done.
Click to expand...
Click to collapse
Can you give little more info on this. Changed cid? Unlocked bootloader? Maybe we can use x1250 xml fastboot files until they release Marshmallow fastboot. I need one for backup , I know I'll brick the phone sooner or later , as guys above did lol..
Yes, unlocked bootloader and you don't flash the XT1254 bootloader. This was before Sunshine, and he converted XT1250 to XT1254 with unlocked bootloader.
We chatted over a few days, while he tried to find an XT1250, ordered one, then it arrived. Then he flashed the Verizon firmware. Here's the relevant portion of what he wrote:
Flashed the Verizon radio and 5.1 FW (firmware)
The only problem I have right now is upload speeds are super slow.
gonna try wiping the radio and re-writing the radio
Click to expand...
Click to collapse
I then asked him a couple of questions and he answered this:
Yes I flashed the Verizon Radio to the device
not the bootloader image, for obvious reasons
I wanted 5.1, so I didn't test until I had the VZW 5.1 with my SIM card
I'm going to try an reflash soon, and then get a new SIM just in case
I hope Verizon doesn't give me any trouble getting a new SIM at my local store
Click to expand...
Click to collapse
I didn't hear from him anymore after that, so guess everything turned out OK. This in August 2015, was about a month after 5.1 was released for the Droid Turbo XT1254 (XT1250 was still on 4.4.4) but before Sunshine released their bootloader unlock for the XT1254 in November 2015.
ChazzMatt said:
Yes, unlocked bootloader and you don't flash the XT1254 bootloader. This was before Sunshine, and he converted XT1250 to XT1254 with unlocked bootloader.
We chatted over a few days, while he tried to find an XT1250, ordered one, then it arrived. Then he flashed the Verizon firmware. Here's the relevant portion of what he wrote:
I then asked him a couple of questions and he answered this:
I didn't hear from him anymore after that, so guess everything turned out OK. This in August 2015, was about a month after 5.1 was released for the Droid Turbo XT1254 (XT1250 was still on 4.4.4) but before Sunshine released their bootloader unlock for the XT1254 in November 2015.
Click to expand...
Click to collapse
Yeah but we're talking about vice-versa here, flashing xt1250 Firmware to xt1254 .
Flashing xt1254 firmware to xt1250 with unlocked bootloader doesn't seem like a big deal, it should be possible anyway..
Ej?iSixo said:
Yeah but we're talking about vice-versa here, flashing xt1250 Firmware to xt1254 .
Flashing xt1254 firmware to xt1250 with unlocked bootloader doesn't seem like a big deal, it should be possible anyway..
Click to expand...
Click to collapse
That's been done, too. I didn't know that was the question.
One guy didn't want Verizon bloatware and his solution was to flash the "pure" Motorola firmware from the XT1250 over his XT1254.
Yes, he had unlocked bootloader and could have just uninstalled the bloatware. I'm not saying it was logical, I'm just telling you what he did.
So there's no question these two phones are exactly the same device, with exactly the same FCC ID.
The issue is the XT1250/XT1254 being flashed needs to the other needs an unlocked bootloader. And you can't downgrade (gpt.bin) when you flash.
So, for the purposes of this thread that information doesn't help you, if your XT1254 bootloader isn't unlocked.
mr_5kool said:
Hi guys,
I (and some of my friends) had a problem with XT1254:
1. We updated to 6.0.1 via recovery with update.zip. This process had successfully done.
2. Several felt something wrong with new 6.0.1 system, so they re-updated via recovery again (still the same update.zip). This made the system dead. They could not enter system, except bootloader and recovery. The problem is that source system needs to be Lollipop SU4TL-49 so the re-update process will fail.
Conclusion: Wait for the 6.0.1 flash file (xml) then flash via RSD.
Thanks guys!!!!
Click to expand...
Click to collapse
[FXZ] Official Stock Firmware 6.0.1 MCG24.251-5
https://forum.xda-developers.com/dr...-official-stock-firmware-6-0-1-mcg24-t3531571
Hello im looking for the firmware for flashing with RSD Lite with the following phone.
My phone is stuck on the red moto logo screen and needs flashing with new software, i can boot it into AP Fastboot Mode, don't know if it is bootloader unlocked, it won't seem to install the flash from original OEM version's such as jellybean using RSD Lite.
I did a OTA update via the phone's system to Kitkat,
The Kitkat OEM flashing file for RSD Lite does not seem to be available for the unit after searching for it on the web,
System Version
990.43.74.XT890.Retail.en.GB
Model number
MOTOROLA RAZR I
Android version
4.4.2
Build number
KIA20.74
when i flash the phone with the stock firmware rom im getting the following,
fastboot reason: flash failure
Fastboot: max dowload size 100mb
USB connected
Getvar max-download-size
downloading...
downgraded security version
update gpt_main version failed
preflash validation failed for GPT
fastboot commnd failed
Hello,
here you will find the rom for your smartphone
https: // firmware.center
sercari said:
Hello,
here you will find the rom for your smartphone
https: // firmware.center
Click to expand...
Click to collapse
What file is the right one?
I have issue now with my battery not keeping charge and I already wasted money on a new battery and it's do the samething.
What is the exact name of the firmware and is it possible with RSD?
Does anyone ever look at these Threads anymore?
BallyS said:
Does anyone ever look at these Threads anymore?
Click to expand...
Click to collapse
Hi is the battery a motorola original, or a chinese branded one off ebay ? and what firmware are you running on the phone ?
Junofirst said:
Hi is the battery a motorola original, or a chinese branded one off ebay ? and what firmware are you running on the phone ?
Click to expand...
Click to collapse
The Original was the one which came with it, and it was going mad, 0%, 65% 97% 15% off , back on etc.
Then I ordered one off Ebay and it doing same, it is Chinese brand I would think.
The problem I got is, I flashed the XT890 back when the EU version was the only GB closest, since no GB version of 4.4.2.
Now when I try RSD Lite to reflash or go back to 4.1 it fails.
I had a folder with the Items back from 2013 or 2104 maybe, but can't remember the process and so I need to Unroot?
I have tried putting FW on SD but it fails there too.
BallyS said:
The Original was the one which came with it, and it was going mad, 0%, 65% 97% 15% off , back on etc.
Then I ordered one off Ebay and it doing same, it is Chinese brand I would think.
The problem I got is, I flashed the XT890 back when the EU version was the only GB closest, since no GB version of 4.4.2.
Now when I try RSD Lite to reflash or go back to 4.1 it fails.
I had a folder with the Items back from 2013 or 2104 maybe, but can't remember the process and so I need to Unroot?
I have tried putting FW on SD but it fails there too.
Click to expand...
Click to collapse
Hello you could a have a look at this thread about your battery issue,
https://forum.xda-developers.com/showthread.php?t=2198774
What i have learned is that you can not downgrade the firmware if it is older than the current software on the phone.
So if you have android KITKAT 4.4.2. you cannot flash to jellybean or ice cream sandwich and they are the only firmwares available at the firmware centre.
If you have a unlocked bootloader it is possible to reflash downgraded firmware but do so at your own risk !
Have you tried the Motorola app called Smart Actions for battery ?
You could try to intstall this firmware software from your SD card, using TWRP,
Blur_Version.990.43.74.XT890.Retail.en.EU.zip?dl=0
and this one too,
KIA20.74STOCK
Junofirst said:
Hello you could a have a look at this thread about your battery issue,
https://forum.xda-developers.com/showthread.php?t=2198774
What i have learned is that you can not downgrade the firmware if it is older than the current software on the phone.
So if you have android KITKAT 4.4.2. you cannot flash to jellybean or ice cream sandwich and they are the only firmwares available at the firmware centre.
If you have a unlocked bootloader it is possible to reflash downgraded firmware but do so at your own risk !
Have you tried the Motorola app called Smart Actions for battery ?
You could try to intstall this firmware software from your SD card, using TWRP,
Blur_Version.990.43.74.XT890.Retail.en.EU.zip?dl=0
and this one too,
KIA20.74STOCK
Click to expand...
Click to collapse
I don't see the links, did you link them right?
I had 2015-02-03--12-50-05 KIA20.74 , but it wouldn't accept it via fastboot.
What is TWRP?
I've been to that Thread before and many other's but they are all old and none working links.
BallyS said:
I don't see the links, did you link them right?
I had 2015-02-03--12-50-05 KIA20.74 , but it wouldn't accept it via fastboot.
What is TWRP?
I've been to that Thread before and many other's but they are all old and none working links.
Click to expand...
Click to collapse
Here is the link to KITKAT,
https://www.dropbox.com/s/4np6wx9enwsyyv9/Blur_Version.990.43.74.XT890.Retail.en.EU.zip?dl=0
Junofirst said:
Here is the link to KITKAT,
https://www.dropbox.com/s/4np6wx9enwsyyv9/Blur_Version.990.43.74.XT890.Retail.en.EU.zip?dl=0
Click to expand...
Click to collapse
I have this already, but when I put on SD and goto Fastboot and choose install from SD, it fails.
This is why I have been asking what is the process?
I get libwvphoneApi.so unexpected contents
BallyS said:
I have this already, but when I put on SD and goto Fastboot and choose install from SD, it fails.
This is why I have been asking what is the process?
I get libwvphoneApi.so unexpected contents
Click to expand...
Click to collapse
When you said early in the post that you have changed the firmware on the system motherboard (The problem I got is, I flashed the XT890 back when the EU version was the only GB closest, since no GB version of 4.4.2.) how did you flash the phone with KITKAT EU ? did you do it with system menu OTA update via the internet ? or did you flash it with firmware from a file downloaded from the internet ?
I think the problem will be the firmware that you installed because when you flash firmware you need the serial number from under the battery or where the number is located to get the right version of software for the phone.
It has to be the same or newer for it to work properly, or the phone to operate correctly.
So you could only downgrade the phone to the original stock rom firmware for it to operate and function correctly.
Is the bootloader locked or unlocked ? because with a locked bootloader you will not be'able to downgrade to original stock rom firmware. With locked, the firmware is stuck as it is unless it is original stock rom on the system motherboard which you can easy reflash with RSD lite recovery software.
Junofirst said:
When you said early in the post that you have changed the firmware on the system motherboard (The problem I got is, I flashed the XT890 back when the EU version was the only GB closest, since no GB version of 4.4.2.) how did you flash the phone with KITKAT EU ? did you do it with system menu OTA update via the internet ? or did you flash it with firmware from a file downloaded from the internet ?
I think the problem will be the firmware that you installed because when you flash firmware you need the serial number from under the battery or where the number is located to get the right version of software for the phone.
It has to be the same or newer for it to work properly, or the phone to operate correctly.
So you could only downgrade the phone to the original stock rom firmware for it to operate and function correctly.
Is the bootloader locked or unlocked ? because with a locked bootloader you will not be'able to downgrade to original stock rom firmware. With locked, the firmware is stuck as it is unless it is original stock rom on the system motherboard which you can easy reflash with RSD lite recovery software.
Click to expand...
Click to collapse
It would have been from this Thread
https://forum.xda-developers.com/razr-i/help/qa-razr-xt890-4-4-2-eu-ota-update-t3094784
I asked at the start here, what is the Process, as all I remember is, I got the files from here back 2015 by the looks.
Then either updated by RSD or put on SD and done it.
Since mine is a GB phone, there was no GB version and I had to use the EU one.
I have no clue now if I locked or unlocked it.
I had to boot up my old XP machine and it had all the Adb and Moto files in one folder. but none of those files seem to work, eventhough RSD shows my Phone on USB on the XP machine, but not on the Win10 machine I have now.
I retried RSD and I took out a few lines from the xml and it bricked my phone.
I did recover it and the onlything that seemed to have changed was the baseband.
How can I Downgrade or reflash the FW?
BallyS said:
It would have been from this Thread
https://forum.xda-developers.com/razr-i/help/qa-razr-xt890-4-4-2-eu-ota-update-t3094784
I asked at the start here, what is the Process, as all I remember is, I got the files from here back 2015 by the looks.
Then either updated by RSD or put on SD and done it.
Since mine is a GB phone, there was no GB version and I had to use the EU one.
I have no clue now if I locked or unlocked it.
I had to boot up my old XP machine and it had all the Adb and Moto files in one folder. but none of those files seem to work, eventhough RSD shows my Phone on USB on the XP machine, but not on the Win10 machine I have now.
I retried RSD and I took out a few lines from the xml and it bricked my phone.
I did recover it and the onlything that seemed to have changed was the baseband.
How can I Downgrade or reflash the FW?
Click to expand...
Click to collapse
Is there no way to put the Original FW on or Reflash?
I have just got the Unlock Bootloader info and applied it.
I just need to reflash the right FW or go back to 4.1 ?
BallyS said:
Is there no way to put the Original FW on or Reflash?
I have just got the Unlock Bootloader info and applied it.
I just need to reflash the right FW or go back to 4.1 ?
Click to expand...
Click to collapse
I managed to get to CFC_9.8.2I-50_SMI-26_S7_USASMIJBRTEU and it has gone back to 4.1.2
It see's CFC_9.8.2I-50_SMI-29_S7_USASMIJBRTGB.xml on my SD as an Update, not sure why?
Is it not the same?
Since doing this, my battery only lost 60% in 2 1/2 days.
Clearly either the FW got bugged or an App was doing something.
I have installed a Security software and it came up with phishing warning, but how would I know if that was true with that FW version?
BallyS said:
Since doing this, my battery only lost 60% in 2 1/2 days.
Clearly either the FW got bugged or an App was doing something.
I have installed a Security software and it came up with phishing warning, but how would I know if that was true with that FW version?
Click to expand...
Click to collapse
Hi the firmware should be fine with no issues and you installed Jellybean 4.1.2 european version, my phone is the same as yours but with KITKAT 4.4.2. and the battery discharges about the same. Install eset security from google play store or any other website, and install DU Battery Saver Pro and other DU software for android, these are all available at the google play store and you should have no problems with the battery.
Junofirst said:
Hi the firmware should be fine with no issues and you installed Jellybean 4.1.2 european version, my phone is the same as yours but with KITKAT 4.4.2. and the battery discharges about the same. Install eset security from google play store or any other website, and install DU Battery Saver Pro and other DU software for android, these are all available at the google play store and you should have no problems with the battery.
Click to expand...
Click to collapse
Mine is 4,4.2 also.
It's why I was asking earlier about the two versions.
It seems to be working now.
preflash validation for gpt signed
Hello everyone,
I'm facing an error which is update gpt_main version failed.
please help me about this.
I bricked my G7 Plus and finally got it restored with the wrong firmware image (T-Mobile Revvlry+). It no longer has an IMEI or radio. Fastboot getvar all does return the IMEI correctly and it also reports radio: TMO and ro.carrier: retla.
I would like to get it working again with a stock rom.
Is there one available?
Is there a way to get the radio working and IMEI restore with the T-Mobile rom?
Stock ROMs from Lolinet:
Moto G7plus roms
But you need to find out what folder to pick according to your 1965 model.
Learn about the EFS and how to make a EFS backup, this is essential. It seems to happen often to loose cell network or IMEI with the G7 plus.
My phone is the same and got many problems when i unlocked it and tried to install LineageOS, fortunately they all be solved and now it is ok.
how about the status of your phone now?
black - no display?
slot a/b error?
fall to an old bootloader?
youzi0335 said:
My phone is the same and got many problems when i unlocked it and tried to install LineageOS, fortunately they all be solved and now it is ok.
how about the status of your phone now?
black - no display?
slot a/b error?
fall to an old bootloader?
Click to expand...
Click to collapse
Lineage OS 11242020 build installed. No WiFi, no IMEI (although the IMEI shows in getvar), no service.
first i install the newest version (Lineage OS 20210105), it is no service.
then back to 20201124, now it's ok.
i'm not sure if this problem is caused by LineageOS.
so may be change to another version is a solution.
otherwise, if you have a stock rom, you can reflash the BP/BL and try it again.
below is the Tinyfastboot, it's a useful tool can help you try it.
TinyFastbootScript - mirrors.lolinet.com > software > windows > TinyFastbootScript
Did you have any luck finding the ROM for the XT1965-T (Non-TMo, Moto)?
I have the same model, XT1965-T. In my attempts to flash Lineage (which included hard bricking it and then a bootloop) I did have to flash blankflash (to fix the hard brick) and then later a stock boot.img from the stock TMO ROM from lolinet, but I have not flashed any other parts of the stock TMO ROM.
My fastboot getvar all also identifies the device with radio: TMO and ro.carrier: retla.
From what I can tell, this is the same device that Moto licensed to T-Mobile as the "Revvelry+" and now Moto is selling it without a carrier lock. So it would not surprise me if some T-Mo remnants were there...
Would be interested to hear from someone who has a fresh unmodified device what their fastboot getvar output says.
For this phone, unlock and flash TMO rom didnot change the info of " radio: TMO and ro.carrier: retla. ", It was these at the beginning .
use twrp to make a nandroid backup especially the persist partition and do not wipe the persist partition that's were your imei is stored
PROBLEM SOLVED. See my post.
https://forum.xda-developers.com/t/moto-g7-plus-no-service.4201229/post-84335207
My main phone its a g8 plus but I bought this "T" unlocked version from amazon to my wife. She wants YT Vanced with her google acc so I decide to root this phone.
Fortunately I been use my G8+ for while until I brick and unbrick this... Then I learn what can and cannot do with this motorola phones. The first reason for do not touch the stock firmware in this phone its because Lenovo rescue software reconize this G7+ like XT1965-3 version, not XT1965-T version. I tried "rescue" with this (XT1965-3) firmware on the Lenovo software and do not work. So if you bricked it, its probably sure that software do not work.
(I tryed this before unlock bootloader)
The second warning its after you unlock the bootloader, if you proceed to install TWRP and choose flash the main partition your done. I guess this phones still recive security patchs (the last one was feb 21) So, even if your do not root but flash TWRP into the main partition you can not be able to "update" your phone again.
(What I do was temporally flash TWRP from cmd to install magisk).
This phone its a "master piece" very useful and cheaper but this version could be a pain in the As*. I still figured out how to get back into android 9 becuase this brought android 10 outted box. I guess we can got a little more battery with this version... So any suggestion are welcome : )
Just picked this phone up at best buy (119 new) and unlocked bootloader, and installed pixel exp rom and so far no problems( haven't tried rooting yet but will)
903tex said:
Just picked this phone up at best buy (119 new) and unlocked bootloader, and installed pixel exp rom and so far no problems( haven't tried rooting yet but will)
Click to expand...
Click to collapse
I saw a guy with a moto XT1965-2 device flashing android 9 stock rom in this video. But I'm a little afraid to do that because this its a single sim device.
Expert here, please help. I have moto g7 plus i got from Motorola directly as replacement variant (XT1965-T) but its going on boot loop. I tried to use Moto recover tool but it does read phone to do rom install. I tried manual also still not working. I tried to do install myself rom by using info and rom from another forum (https://motostockrom.com/motorola-moto-g7-plus-xt1965-t) but it fails to write using flasfile.bat. even though it says usb connected. in recovery mode it also shows OEM locked. is that's the reason ? I just want this phone to work with standard rom of it suppose to work as i got it unlocked version. Please help.
coolarun1980 said:
Expert here, please help. I have moto g7 plus i got from Motorola directly as replacement variant (XT1965-T) but its going on boot loop. I tried to use Moto recover tool but it does read phone to do rom install. I tried manual also still not working. I tried to do install myself rom by using info and rom from another forum (https://motostockrom.com/motorola-moto-g7-plus-xt1965-t) but it fails to write using flasfile.bat. even though it says usb connected. in recovery mode it also shows OEM locked. is that's the reason ? I just want this phone to work with standard rom of it suppose to work as i got it unlocked version. Please help.
Click to expand...
Click to collapse
HI What did you do in first place to get a bootloop? Did you unlock the bootloader or something?
RON4LD7 said:
HI What did you do in first place to get a bootloop? Did you unlock the bootloader or something?
Click to expand...
Click to collapse
No. I just got this from Motorola as replacement from my previous Moto G7 Plus which had screen problem. But the one send me as replacement looks new but as soon as turn it on and it try to connect to Wifi during initial setup it reboot and keep doing. Seems to either issue with OS or wifi hardware. Moto is not willing to replace as it just passed warranty period. Please help.