Related
Hi, a few months ago i unlocked bootloader and rooted my Android 4.4.4 Moto G (locked to Tesco UK) and that was fine but then i went to lock it all again so i could get the OTA update for Android Lollipop.
This is where the problems began... I thought i found the write files to do it but then i discovered after that it was an US version so it wouldn't work with Tesco.
Today i went to roll it back again to a UK version but it doesn't seem to work.
I have all the files I think but I am getting errors such as 'Mismatched partition size' and 'Image file is too big'. I'm not the best with these things so any help would be much appreciated. I currently have a bricked phone so the sooner the better please.
"Hab check failed for boot"
"Hab check failed for recovery"
gingerandroid said:
Hi, a few months ago i unlocked bootloader and rooted my Android 4.4.4 Moto G (locked to Tesco UK) and that was fine but then i went to lock it all again so i could get the OTA update for Android Lollipop.
This is where the problems began... I thought i found the write files to do it but then i discovered after that it was an US version so it wouldn't work with Tesco.
Today i went to roll it back again to a UK version but it doesn't seem to work.
I have all the files I think but I am getting errors such as 'Mismatched partition size' and 'Image file is too big'. I'm not the best with these things so any help would be much appreciated. I currently have a bricked phone so the sooner the better please.
"Hab check failed for boot"
"Hab check failed for recovery"
Click to expand...
Click to collapse
She tried running the following commands:I also I suffered from it and still could not solve this problem to check the images ... the phone be unlocked or not does not affect the system upgrade , only the root so.
you could try downloading the version to install and usually with unlocked bootloader and flash the logo.bin to take the message unlocked bootloader
as the issue of operators, rom provided by different countries does not change the radio frequency of your ... I faced when it lost radio when I used my cell **** fastboot ERASE ALL ( NEVER USE IT IN YOUR LIFE ) ****
Partitions where there are these radio information is not modified when you put another ROM same as original ...
You will have to leave the unlocked bootloader and install the rom normally without root with nothing if it's what you want, if you block the bootloader will not be able to boot
https://mega.co.nz/#F!29RX1L6I!gfxcXgqkAhf5GDhr_aPGYg
You can download this link from roms of all official ROMS that exist on the Internet of all Motorola G2 this link below , I've tried to use one of them it is original with all files more still blocking the bootloader you will not able to boot .
Recently purchased an AT&T XT1097. It was on Android 4.4.4 which I temp rooted with Kingroot and then bootloader unlocked using Sunshine. I'd like to upgrade to 5.1 so I haven't bothered yet with rooting or installing a recovery. Frankly, I'm a wee bit confused by the information I've found in numerous threads on this and other sites simply because it seems the AT&T and Verizon versions of the Moto X 2014 are problematic to work with.
Does having my bootloader unlocked at this point mean that any root method will work on the device? I believe flashing should be a non issue at this point (because the bootloader is unlocked) but will it also allow me to downgrade to 4.4.4 or 5.0.2 if I am not pleased with 5.1? Is using TWRP a good idea or would it be best to manually flash images thru fastboot (which I couldn't do without clear instructions)?
On a related note my device initially reported an available OTA system update but since unlocking via Sunshine I haven't had the notification return. MDM also doesn't see an available update. Is this due to Sunshine or left over vestiges of Kingroot despite having done a FDR?
Further update...
With no replies to my questions I've taken it upon myself to try a few things. Figured out that MDM will not see an available update unless the device can connect with AT&T via wifi at which point it tells me that an update is already in progress because the OTA is downloading to the device. I would prefer to download and flash the full image via MDM but it is refusing to do so. I'm assuming that this may be because the update the phone wants to install is now considered an interim update (5.0.2) and the full image has been pulled from Motorola's or AT&T's servers.
I have been able to successfully root 4.4.4 but have since removed it in the expectation of updating the device shortly. I have also been able to boot a TWRP image in the hopes of doing a backup before making any significant changes but the device becomes unresponsive to touch commands at the write protect warning screen. Any ideas???
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
Hey Guys! I write to know that how can I update my moto x 2nd gen. from lollipop to marshmallow without opening its bootloader or root because I think these two options are not safe and somehow will damage my device. By the way its a verizon variant xt1096. So guys please help me, will be very grateful
Sapper Morton said:
You could update to MM without unlocking the bootloader, unfortunately the XT1096 ( Verizon ) didn't ever received the Stock MM Firmware, so no lucky to you mate.
Flashing Stock firmware from other variants with locked bootloader could become a nightmare very quickly, so I don't recommend doing that.
If you want a phone that is more or less secure, you better be staying on locked state on Lollipop.
Unlocked bootloader + partition encryption is a reasonable security measure for smartphones, but yet is vulnerable to injection of custom binaries due to the unlocked state.
On daily use, you will hardly ever be vulnerable, however you could be exploited if you become a specific target.
Other than that I recommend buying a new phone that supports security updates officially, for a least to the next 2-3 years.
You know your daily life and your priorities, you can decide for yourself.
Click to expand...
Click to collapse
Thanks for the advice! I really appreciate your thoughts. Well you said that I can update to marshmallow by flashing other variants firmware without opening my device's bootloader. So how can really do that? By the way I have already tried updating through recovery mode, but it didn't work. So is there any other way to update my device.
I have the Verizon model too, and same situation. Phone still works fine, but I couldn't tolerate being 4 major Android versions behind. Eventually, I bite the bullet, unlocked the boot loader (since device is well out of warranty anyway), flashed a Oreo-based Linage OS ROM, which really brought new life into the phone. Some minor issues here and there but nothing huge. You should be okay if you know what you're doing and backup your stock configuration properly.
Sapper Morton said:
You could flash other variants firmware, however the stock MM doesn't support CDMA, only GSM.
With locked bootloader you will only get your XT1096 to work on non-verizon carriers, or partially work on verizon, since they don't use CDMA exclusively anymore.
There was a modded stock MM OS in the past, made to work on verizon network, unfortunately, you need an unlocked bootloader to flash it.
In case you should consider unlocking your bootloader, I recommend flashing the LineageOS 14.1, Android 7.1.2.
Any AOSP ROM, based on CM13, Android 6.0.1, should support CDMA and GSM from the source.
In which case, the Lineage 14.1 supports it, and it has the latest security patches, as I said before, using /data encryption on a unlocked state, is a reasonable security measure you should consider, that way, anyone that may get hands on your device will be unable to read the data, being naive.
Click to expand...
Click to collapse
Thanks once again for your time! Actually I am not on CDMA, I'm using GSM network. So how can update to marshmallow now and I prefer stock marshmallow rather than custom or any other roms. So please guide me in that.
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.