Database Info

Is it possible to restore bloatware apps?

Hello all.
I rooted my Razr HD after the most recent update (prior to KitKat), so I'm rooted but not unlocked. In my ultimate wisdom, I completely removed (did not merely freeze) some bloatware apps, and only today am learning they are necessary to receive OTA updates.
A factory reset did not restore the apps.
Is it possible to get these bloatware apps back onto my device, or am I pretty much screwed?
If there is a way to restore them, am I screwed anyway due to having previously rooted my device and not having a way to flash a ROM?
My apologies if these questions are dumb; I've been looking for information regarding this for a couple hours and have come up empty so far.

Depending on what version you are currently on, you will need to get the correct FXZ image to fastboot onto your device to return it to stock.
Go here to fix you right up:
http://www.droidrzr.com/index.php/topic/45494-how-to-xt926-upgrade-to-kitkat-ota/
Sent from my Nexus 7 using Tapatalk

Thanks a lot for the advice and the links. The process seems to work ok up until it tries to flash system.img.ext4, at which point it returns the message "Phone returned FAIL.; phone connected". If I remove that one line from the XML file, everything else goes through with no issues, so that seems to be the last thing holding me back.
When I attempt to boot the phone, I receive the following:
No valid PIV block in SP for system
piv validation failed (system)
Fastboot Reason: Boot Failure
Click to expand...
Click to collapse
I will double-check some things and try one more thing before I declare myself stuck again.

Well, I'm glad I ran my double-checks because I would have wasted someone else's time otherwise. After updating to a slightly more recent version of RSD Lite, it got all the way through the reflash process.
My phone boots now. The stock apps are back. I'm letting all my apps update before I attempt the KitKat update, but I'm feeling confident about this. iBolski, I can't thank you enough, and I will love you forever.

A little help..
Thanks for posting this! However I'm running into an issue. I downloaded the latest firmware for my XT907 as well as the latest version on RSD Lite, but when I go to flash the stock image I get an error message that says "unknown fastboot command [getvar]. Any ideas??

Worked for me
Thank you iBolski. The process failed the first time I ran RSD Lite, but it worked the second time. I did not unplug the phone or take it out of Fast Boot mode before trying it the second time. This is very helpful.

froyton said:
Well, I'm glad I ran my double-checks because I would have wasted someone else's time otherwise. After updating to a slightly more recent version of RSD Lite, it got all the way through the reflash process.
My phone boots now. The stock apps are back. I'm letting all my apps update before I attempt the KitKat update, but I'm feeling confident about this. iBolski, I can't thank you enough, and I will love you forever.
Click to expand...
Click to collapse
Eustace2 said:
Thank you iBolski. The process failed the first time I ran RSD Lite, but it worked the second time. I did not unplug the phone or take it out of Fast Boot mode before trying it the second time. This is very helpful.
Click to expand...
Click to collapse
Glad it helped.
---------- Post added at 03:05 PM ---------- Previous post was at 03:00 PM ----------
moodaddy said:
Thanks for posting this! However I'm running into an issue. I downloaded the latest firmware for my XT907 as well as the latest version on RSD Lite, but when I go to flash the stock image I get an error message that says "unknown fastboot command [getvar]. Any ideas??
Click to expand...
Click to collapse
Go back to the following link and get the latest FXZ generator. SamuriHL has been updating it as people have been reporting issues:
http://www.droidrzr.com/index.php/topic/45349-rsd-script-generator/
He updated it yesterday to handle issues for your phone (XT907) and the XT926s as well. See if that fixes your issue. Otherwise, I'm not sure how else to help you.

[Q] i KILLED IT

I have a razr hd. was experimenting trying to root it And killed it.. it will boot to the set up page but not set up. just said wait for ever. Can get into fast boot but when i run rsd light it shows connection but no data on the phone. when i try and restore phone with VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-2_VQW_CFC.xml.zip, it says unknown fast boot command. I amnot that save on this stuff but want to learn. can anybody help?

can you get your phone to apfatboot? how did you get where you are? i mean what did you have on your phone, what did you flash....what errors are you getting if you try apfastboot....?

hbenz2008 said:
can you get your phone to apfatboot? how did you get where you are? i mean what did you have on your phone, what did you flash....what errors are you getting if you try apfastboot....?
Click to expand...
Click to collapse
There is no problem getting into fast boot. theres no errors other than when i get into apfastboot it says device is locked, status code 0 I was trying to root it off of instructions off of other posts it had android version 4.4.1 . sorry if if cant be more specific but i'm just learning about these things.

c:\fast>mfastboot update VZW_XT926_4.0.4-7.7.1Q-144_VQW_S3-34-25_CFC.xml.
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txtThis is what i get when i try running a update on fast boot.

That is old FW, like when the phone first came out. You really need to stop trying to flash random things and get the latest FW out of the General section and flash that.
Sent from my HTC6525LVW using Tapatalk

Thanks to all of any one is currently having probloms with ther "bricked" phone foloww this post.
http://forum.xda-developers.com/droid-razr-hd/general/fxz-4-4-2-183-46-15-t2873083
I used the rsd flash methode and it worked for me.

[Q] Flashing bootloader locked Cricket Moto G/LTE to retail firmware

I want to flash my Cricket Moto G (xt1045) 4.4.4 to the retail 4.4.4 version for a few reasons. Mainly to get access to tethering and the chance that I will be able to update to Lollipop since my hope of cricket releasing the update is fading.
I've been searching around and cannot find a definite answer to this. Lots of people say it should work but I have yet to find anyone who successfully did so. Some say to flash all files but the bootloader and it should be good while others say being the official Motorola firmware everything will flash without a problem.
Has anyone took the plunge and tried it? I would, but I really don't want to be stuck with my Lumia 520 backup phone if I screw something up. Thanks!

macgi77 said:
I want to flash my Cricket Moto G (xt1045) 4.4.4 to the retail 4.4.4 version for a few reasons. Mainly to get access to tethering and the chance that I will be able to update to Lollipop since my hope of cricket releasing the update is fading.
I've been searching around and cannot find a definite answer to this. Lots of people say it should work but I have yet to find anyone who successfully did so. Some say to flash all files but the bootloader and it should be good while others say being the official Motorola firmware everything will flash without a problem.
Has anyone took the plunge and tried it? I would, but I really don't want to be stuck with my Lumia 520 backup phone if I screw something up. Thanks!
Click to expand...
Click to collapse
Anyone? I found a link with instructions but I can't post it until I have 10 posts. If anyone wants to try it, search for "viraj's flash stock rom lock bootloader moto g"

macgi77 said:
Anyone? I found a link with instructions but I can't post it until I have 10 posts. If anyone wants to try it, search for "viraj's flash stock rom lock bootloader moto g"
Click to expand...
Click to collapse
http://dev-viraj.blogspot.in/2015/01/flash-stock-rom-firmware-lock.html
Is that the page? His instructions and ROM download seem to be for a XT1068, not a XT1045. Did you find the ROM files for a 1045 somewhere? I'd like to get access to wifi tethering, too...

Yes, that is the page. I'm assuming the software install would be the same for all models in the Moto G group. The ROM files are located in a thread on here titled "Moto G 4G/LTE Stock Firmware (XT1039/40/42/45)"
Would post a link, but I'm still not allowed.

macgi77 said:
Yes, that is the page. I'm assuming the software install would be the same for all models in the Moto G group. The ROM files are located in a thread on here titled "Moto G 4G/LTE Stock Firmware (XT1039/40/42/45)"
Would post a link, but I'm still not allowed.
Click to expand...
Click to collapse
Link for those looking for it.
Thanks for the link. Maybe I will give this a try, I'm buying an android stereo for my car and need wifi tethering to run the GPS.
If you wind up trying it before I do, let us know! This would theoretically only update the ROM, we'd still be stuck with a locked bootloader, right? If we could find a 4.4.2 ROM, then the Sunshine S-off unlock would work, and we'd be set.

RonnieTheBear said:
Link for those looking for it.
Thanks for the link. Maybe I will give this a try, I'm buying an android stereo for my car and need wifi tethering to run the GPS.
If you wind up trying it before I do, let us know! This would theoretically only update the ROM, we'd still be stuck with a locked bootloader, right? If we could find a 4.4.2 ROM, then the Sunshine S-off unlock would work, and we'd be set.
Click to expand...
Click to collapse
No problem. I will report back if I try, you do the same if you beat me to it! Yes, the bootloader would still be locked, but the software should install since it is an official Motorola signed software. I think I recall reading somewhere that flashing to 4.4.2 would not allow unlocking through sunshine though.

macgi77 said:
No problem. I will report back if I try, you do the same if you beat me to it! Yes, the bootloader would still be locked, but the software should install since it is an official Motorola signed software. I think I recall reading somewhere that flashing to 4.4.2 would not allow unlocking through sunshine though.
Click to expand...
Click to collapse
macgi , I gave this a try last night and the results were extremely not good. Wasn't able to flash the retail firmware, got a bunch of "prevalidation flash failed" on some items, but not others, and then it wouldn't boot. Tried to reflash the cricket firmware to revert back, and got the same prevalidation error for the boot image and the partition gpt.bat file, and now I can't get past the fastboot screen.

RonnieTheBear said:
macgi , I gave this a try last night and the results were extremely not good. Wasn't able to flash the retail firmware, got a bunch of "prevalidation flash failed" on some items, but not others, and then it wouldn't boot. Tried to reflash the cricket firmware to revert back, and got the same prevalidation error for the boot image and the partition gpt.bat file, and now I can't get past the fastboot screen.
Click to expand...
Click to collapse
That sucks. That was the only thing keeping me from trying, the process of fixing it if something screwed up. Hopefully someone has an idea how to fix it since I'm not quite and expert in recoveries.
Thanks for reporting back though!

macgi77 said:
That sucks. That was the only thing keeping me from trying, the process of fixing it if something screwed up. Hopefully someone has an idea how to fix it since I'm not quite and expert in recoveries.
Thanks for reporting back though!
Click to expand...
Click to collapse
Yeah, no problem - it's possible I messed something up in the flashing operation, but I thought you'd want to know.

RonnieTheBear said:
Yeah, no problem - it's possible I messed something up in the flashing operation, but I thought you'd want to know.
Click to expand...
Click to collapse
I'm assuming you tried using the link above? Or did you try flashing each individual file and skipping the bootloader file which was talked about in the firmware thread? (I believe it was around pages 20-30 if I recall)
Found it
@JoeSyr, maybe I'm missing something here specific to Moto G LTE, but flashing a firmware image does not require an unlocked Bootloader. I would do it manually, skip most of the steps, and only flash the system.img initially.
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
The only way you can get into serious trouble would by flashing the motoboot.img (Bootloader) and phone no longer loads fastboot mode. But even then, is there not a hardbrick mbm-ci recovery option for Moto G 4G
Click to expand...
Click to collapse

macgi77 said:
I'm assuming you tried using the link above? Or did you try flashing each individual file and skipping the bootloader file which was talked about in the firmware thread? (I believe it was around pages 20-30 if I recall)
Found it
Click to expand...
Click to collapse
I tried running the ROM Install.bat file the guy put together in the first page you/I linked to, which did attempt to flash the bootloader. It sounds like this person you're quoting is saying the flash should be operational even just flashing those three chunks of the system image file? I think those files wrote okay, but it still didn't boot. Problem might be with this other partition file i mentioned.

RonnieTheBear said:
I tried running the ROM Install.bat file the guy put together in the first page you/I linked to, which did attempt to flash the bootloader. It sounds like this person you're quoting is saying the flash should be operational even just flashing those three chunks of the system image file? I think those files wrote okay, but it still didn't boot. Problem might be with this other partition file i mentioned.
Click to expand...
Click to collapse
That's what it sounds like. Any luck restoring the phone yet?

no, haven't really gotten a chance to mess with it, yet. I popped my sim card into an old samsung galaxy Blaze I had laying around as a backup, and I've been getting by with that for the time being. I think I've still got to figure out what the next thing I should try is. Might try asking around in some more of the subforums, here.

RonnieTheBear said:
no, haven't really gotten a chance to mess with it, yet. I popped my sim card into an old samsung galaxy Blaze I had laying around as a backup, and I've been getting by with that for the time being. I think I've still got to figure out what the next thing I should try is. Might try asking around in some more of the subforums, here.
Click to expand...
Click to collapse
Good luck, let us know how you make out.

RonnieTheBear said:
no, haven't really gotten a chance to mess with it, yet. I popped my sim card into an old samsung galaxy Blaze I had laying around as a backup, and I've been getting by with that for the time being. I think I've still got to figure out what the next thing I should try is. Might try asking around in some more of the subforums, here.
Click to expand...
Click to collapse
Any update?

macgi77 said:
Any update?
Click to expand...
Click to collapse
I tried flashing with some more tools, different firmwares, and different combinations of commands, no luck.
I found a guy in the stock firmware thread that had the exact same problem as me, and has the same cid as my phone, cid 10, which no one else seems to have. They think it might be why the preflash validation failed.
Other users suggested that if a cricket lollipop firmware image is developed at some point in the future, that would be able to flash without error. I reached out to the user to see if he ever resolved it, but didn't get a response.
Anyway, the sense that I got is that my problems were because my cid didn't match. Is yours cid 10 as well? you can check from adb. If it's not, you might be fine attempting it.

It's been a while since I checked, but I believe it is cid 10 as well. Now just hoping cricket releases Lollipop soon.....

The lollipop release for the retail (non carrier) version just came out OTA yesterday, apparently, so hopefully Cricket is not too far behind...Though it will probably take a while to go from an OTA update to a downloadable firmware image.

I contacted Motorola tech support today, they said they would replace the phone for $75 + taxes (flashing firmware via adb fastboot voids the warranty, of course), and told me it wouldn't have the Cricket firmware on it, so worst case, i would be gaining tethering ability, best case, they might send me a variant (xt1039?) that is capable of being rooted and installing a custom ROM in addition to tether. I'll probably take this option if I'm not able to get it working once the lollipop xt1045 firmware file shows up.

That's not a bad deal. Hopefully you can get it working when lollipop comes out though. Thanks for the update!

endelss bootloop motog xt1068

MOTO G XT1068
Hi folks!!! Moto g xt1068, after several roms flash and tries of every kind my phone wont wake up, it just remains in logo, i does go to fastboot mode but i cant hard reset, once it did but it appeared fail 0 nowadays it wont react to de first command with lying android, please help!!! I would need to know what to do, some process to restaure the whole system of the phone it self, i repeat, i dont know what was actually done with this phone, it came to me on bootloop, and i cant unbrick it
I have flashed 5.2, 4.4.4, several times, on fastboot, and logs were just perfect. HELP please.

Pomar91 said:
MOTO G XT1068
Hi folks!!! Moto g xt1068, after several roms flash and tries of every kind my phone wont wake up, it just remains in logo, i does go to fastboot mode but i cant hard reset, once it did but it appeared fail 0 nowadays it wont react to de first command with lying sndroid, please help!!! I would need to know what to do, some process to restaure the whole system of the phone it self, i pepeat, i dont know what was actually done with this phone, it came to me on bootloop, and i cant unbrick it
I have flashed 5.2, 4.4.4, several times, on fastboot, and logs were just perfect. HELP please.
Click to expand...
Click to collapse
do you know if the bootloader is unlocked? if not, that may limit what you can flash and boot. are you wiping the data after flashing the firmware?
are you flashing everything in the stock firmware, or just parts?
if unlocked and didnt wipe, try fastboot -w
if locked, flash the newest firmware available, even that may not be good enough if the absolute newest isnt avaiable, then use the wipe command.
finally, i have no experience with your device. im just stating common practice from other motos i have owned.

Yeah, thanks for replaying, I did.unlock bootloader bootloader in order to better work with fastboot, but I'm pretty sure such command was included, d wipe one, as I followed several co.vibration of commands I found here at xda, thanks again for attention and time, what u mean is hard reseting by fastboot seen I can't by d phone in fastboot mode right?

What do u think? When ever u have d time 4 sure, maybe u recommend me to an expert, do you know one?

Pomar91 said:
Yeah, thanks for replaying, I did.unlock bootloader bootloader in order to better work with fastboot, but I'm pretty sure such command was included, d wipe one, as I followed several co.vibration of commands I found here at xda, thanks again for attention and time, what u mean is hard reseting by fastboot seen I can't by d phone in fastboot mode right?
Click to expand...
Click to collapse
right
if you flash ALL the partitions in the stock file, and wipe (-w) with an unlocked bootloader, its extremely rare to not boot.

I have been trying this smartphones home fixing and motog is always been ok, it's just weird this, could u recommend me to an expert,and thanks so much

Pomar91 said:
What do u think? When ever u have d time 4 sure, maybe u recommend me to an expert, do you know one?
Click to expand...
Click to collapse
im actually quite knowledgeable with moto, just not your specifically.
there really is no special fix. if you flash all stock partitions, and all pass/install properly, there isnt much else you can do to fix it.

Ok my friend and allow me to call u that, I will review everything I have done, and I will freak u out with details ,logs screen shots, all of the d stuff, isn't it this d way u guys learn? So we both will get better, how about that, maybe tomorrow I will get u whole procedure, maybe u can send me the whole.commands list, a really complete one, another thing. What about kernel and cwm?

Pomar91 said:
Ok my friend and allow me to call u that, I will review everything I have done, and I will freak u out with details ,logs screen shots, all of the d stuff, isn't it this d way u guys learn? So we both will get better, how about that, maybe tomorrow I will get u whole procedure, maybe u can send me the whole.commands list, a really complete one, another thing. What about kernel and cwm?
Click to expand...
Click to collapse
yea, that would be good, copy all the text from the fastboot terminal so i can see it.
kernel is flashed as part of the stock firmware. cwm is a custom recovery and thats not something we need to think about until its fixed.

Man, even if we can't fix this at the end, I'M LIKE SO GRATEFUL FOR UR TIME, WE WILL IMPROVE together, won't let u down

Hey, @Pomar91, what our friendly fellow is telling you about was the wiping part. Did you do that? That might be the problem - the cause for your bootloop.
tetakpatalked from Nexus 7 flo

Well I.guess so, is this the procedure that equals hard reset in mobile but by fastboot in the case? Like a command fastboot wipe data, is that what u guys mean? I'm.with my daughter and she can't sleep, but I will.make a whole report tomorrow and let see what u think. Thanks for ur time, could u please send my this command exactly, and field my doubts about what this is, is it the same as hard reset but using fastboot?

Pomar91 said:
Well I.guess so, is this the procedure that equals hard reset in mobile but by fastboot in the case? Like a command fastboot wipe data, is that what u guys mean? I'm.with my daughter and she can't sleep, but I will.make a whole report tomorrow and let see what u think. Thanks for ur time, could u please send my this command exactly, and field my doubts about what this is, is it the same as hard reset but using fastboot?
Click to expand...
Click to collapse
yes its the same as a hard reset, its what i was asking you in my first reply if you did it.
fastboot -w <--this is the hard reset fastboot command
---------- Post added at 06:35 PM ---------- Previous post was at 06:34 PM ----------
Pomar91 said:
Well I.guess so, is this the procedure that equals hard reset in mobile but by fastboot in the case? Like a command fastboot wipe data, is that what u guys mean? I'm.with my daughter and she can't sleep, but I will.make a whole report tomorrow and let see what u think. Thanks for ur time, could u please send my this command exactly, and field my doubts about what this is, is it the same as hard reset but using fastboot?
Click to expand...
Click to collapse
one more thing, please use the "Quote" button when you reply, so i know you replied to me. thanks

Thanks I will check it out, he did talk.about it, I thought it was a short form, let say the lad version I did flash was kit Kat, successfully flashed, so now I just go and try this command on fast boot, like there should be no need for reflashing, right, just this last command, I'm I right?

Pomar91 said:
Well I.guess so, is this the procedure that equals hard reset in mobile but by fastboot in the case? Like a command fastboot wipe data, is that what u guys mean? I'm.with my daughter and she can't sleep, but I will.make a whole report tomorrow and let see what u think. Thanks for ur time, could u please send my this command exactly, and field my doubts about what this is, is it the same as hard reset but using fastboot?
Click to expand...
Click to collapse
On the example of an entire firmware flash on moto G (which is my preferred way to do it manually, one by one command) you can see the lines including "erase" what my point was:
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system xxxfilename
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
tetakpatalked from Nexus 7 flo

Pomar91 said:
Thanks I will check it out, he did talk.about it, I thought it was a short form, let say the lad version I did flash was kit Kat, successfully flashed, so now I just go and try this command on fast boot, like there should be no need for reflashing, right, just this last command, I'm I right?
Click to expand...
Click to collapse
right
and please stop using the "quick reply" button and use " "reply" thanks
---------- Post added at 06:49 PM ---------- Previous post was at 06:47 PM ----------
tetakpatak said:
On the example of an entire firmware flash on moto G (which is my preferred way to do it manually, one by one command) you can see the lines including "erase" what my point was:
tetakpatalked from Nexus 7 flo
Click to expand...
Click to collapse
hmm, will these new motos actually re-write the partition table using fastboot? the older ones wouldnt. you had to use mfastboot.

bweN diorD said:
hmm, will these new motos actually re-write the partition table using fastboot? the older ones wouldnt. you had to use mfastboot.
Click to expand...
Click to collapse
Possibly some of the partitions had to be enlarged after KitKat. Numerous devices have been doing that step due to ever growing Android OS
I think it was the procedure for the 1st gen Moto G
Do you own it? I have just flashed it on some occasions for friends and family who own it.
tetakpatalked from N7100

all i got
Ok people, i didnt do the whole procedure again, as im sure i have done it properly. The erasing two last steps have been done two. I also used an auto restore script that contains all of the commands, and I have tried before successfully. For sure it includes erase data and cache, now I have found some problems, like preflash validation failed, and preflash validation for tz failed too, the rest just seems ok. So the problem with appear at Motorola screen while flashing in two pink lines I have captured for you. But I do have some other details. After unlock B logo, and Motorola logo, the one in blue, the phone does that part with the world, like that one that turns into many thins with the airplane, and the earth turning around, after it will just go to the black screen, were it will just remain. One of you said something about using Mfasboot and not fastboot it self, I don’t even know the diference, thanks, im sending shots about it. As I don’t know if this auto script I talked about actually works, im gonna retry manually to send u the shots, im using mfastboot this time I guess, I used the v2 zip on the rom file. So as u see I did not finish as the error appears the same preflash validation and for tz, as the same screen showed in the cellphone. That is it.
Another thing, im using 4.4.4 retail, I guess this is stock rom, maybe its all about that, thanks a lot friends, that s all I got.
dudes i dont know how to make this message reach all of u that are helping, please could u help me with that.

that is it friend
all i got
Ok people, i didnt do the whole procedure again, as im sure i have done it properly. The erasing two last steps have been done two. I also used an auto restore script that contains all of the commands, and I have tried before successfully. For sure it includes erase data and cache, now I have found some problems, like preflash validation failed, and preflash validation for tz failed too, the rest just seems ok. So the problem with appear at Motorola screen while flashing in two pink lines I have captured for you. But I do have some other details. After unlock B logo, and Motorola logo, the one in blue, the phone does that part with the world, like that one that turns into many thins with the airplane, and the earth turning around, after it will just go to the black screen, were it will just remain. One of you said something about using Mfasboot and not fastboot it self, I don’t even know the diference, thanks, im sending shots about it. As I don’t know if this auto script I talked about actually works, im gonna retry manually to send u the shots, im using mfastboot this time I guess, I used the v2 zip on the rom file. So as u see I did not finish as the error appears the same preflash validation and for tz, as the same screen showed in the cellphone. That is it.
Another thing, im using 4.4.4 retail, I guess this is stock rom, maybe its all about that, thanks a lot friends, that s all I got.
dudes i dont know how to make this message reach all of u that are helping, please could u help me with that.
maybe u know what exactly stock rom for xt1068 brasil moto g
aanother thing, this mobile screent shot is the same mistake i got for the auto restore and the manual on fastboot

Pomar91 said:
Ok people, i didnt do the whole procedure again, as im sure i have done it properly. The erasing two last steps have been done two. I also used an auto restore script that contains all of the commands, and I have tried before successfully. For sure it includes erase data and cache, now I have found some problems, like preflash validation failed, and preflash validation for tz failed too, the rest just seems ok. So the problem with appear at Motorola screen while flashing in two pink lines I have captured for you. But I do have some other details. After unlock B logo, and Motorola logo, the one in blue, the phone does that part with the world, like that one that turns into many thins with the airplane, and the earth turning around, after it will just go to the black screen, were it will just remain. One of you said something about using Mfasboot and not fastboot it self, I don’t even know the diference, thanks, im sending shots about it. As I don’t know if this auto script I talked about actually works, im gonna retry manually to send u the shots, im using mfastboot this time I guess, I used the v2 zip on the rom file. So as u see I did not finish as the error appears the same preflash validation and for tz, as the same screen showed in the cellphone. That is it.
Another thing, im using 4.4.4 retail, I guess this is stock rom, maybe its all about that, thanks a lot friends, that s all I got.
dudes i dont know how to make this message reach all of u that are helping, please could u help me with that.
Click to expand...
Click to collapse
is there any possibility you can post the actual fastboot dialogue right into the post? not a screen shot.

HELP PLEASE! Phone bootlooping. Missing key ro.build info.

Moto G7 Power is missing ro.build.baseband, ro.build.fingerprint and ro.build.version.full all listed as not found when running getvar all command. Have flashed stock firmware multiple times. All flashes okay but neither fixes the bootloop or the missing info. I have been messing with Motorola phone for years now and never seen this before. Any help would be greatly appreciated. Thanks in advance.

eluallen said:
Moto G7 Power is missing ro.build.baseband, ro.build.fingerprint and ro.build.version.full all listed as not found when running getvar all command. Have flashed stock firmware multiple times. All flashes okay but neither fixes the bootloop or the missing info. I have been messing with Motorola phone for years now and never seen this before. Any help would be greatly appreciated. Thanks in advance.
Click to expand...
Click to collapse
U on stock rom or custom right now

Stock with locked bootloader. Was doing a standard update after it sat turned off for 7 months. I got it to try to boot but it said failed to load kennel. Can't get a boot image to flash now tho

Here's a picture of what the screen said the one time it tried to boot and failed.

eluallen said:
Stock with locked bootloader. Was doing a standard update after it sat turned off for 7 months. I got it to try to boot but it said failed to load kennel. Can't get a boot image to flash now tho
Click to expand...
Click to collapse
Locked bootloader is your problem.

Stock firmware can be flashed in a locked bootloader and it shouldn't have had any effect on the OTA. While LMSA won't flash because of missing info fastboot will flash it fine. I just wrote my own batch file to making flashing multiple times easier. All flashes end with okay but does nothing for the missing info.
I also figured out the issue with flashing the boot image. As long as they're not altered in any way the files will flash on locked bootloader.

eluallen said:
Stock firmware can be flashed in a locked bootloader and it shouldn't have had any effect on the OTA. While LMSA won't flash because of missing info fastboot will flash it fine. I just wrote my own batch file to making flashing multiple times easier. All flashes end with okay but does nothing for the missing info.
I also figured out the issue with flashing the boot image. As long as they're not altered in any way the files will flash on locked bootloader.
Click to expand...
Click to collapse
You are soft bricked u need blank flash file for carrier easy fix moto drivers qail com drivers and the right blank flash pc with terminalhttps://t.me/joinchat/MmtXRlRyFn498KnQGBsmyw. Go here

The link isn't working for me. How do I run the blank-flash batch file when I can't get to edl mode. Have functional fastboot so it won't go to edl. Can you run blank-flash.bat file in fastboot mode as well? And again I appreciate any and all help I get.

eluallen said:
The link isn't working for me. How do I run the blank-flash batch file when I can't get to edl mode. Have functional fastboot so it won't go to edl. Can you run blank-flash.bat file in fastboot mode as well? And again I appreciate any and all help I get.
Click to expand...
Click to collapse
IF you follow the link in post #7 when offered you will get the immediate help you need instead of piecemeal hours between answers help.

As I said in the next post that link isn't working when I try it. Sorry bud.
Simply says "sorry this post does not seem to exist".

As I said follow the link when it's offered. Sometimes the links don't work the next day.

eluallen said:
As I said in the next post that link isn't working when I try it. Sorry bud.
Simply says "sorry this post does not seem to exist".
Click to expand...
Click to collapse
https://t.me/joinchat/MmtXRlRyFn498KnQGBsmyw

Couldn't get the link to work from the LG phone I'm using. Once I got the Moto working it went to the link no problem. Only issue now is no IMEI. Flashing NON-LOS and fsg don't help Making an EDL cable to force boot to EDL mode. Fastboot command came back restricted command and did nothing. Maybe flashing from EDL will make a difference.

Couldn't get the link to work from the LG phone I'm using. Once I got the Moto working it went to the link no problem. Only issue now is no IMEI. Flashing NON-LOS and fsg don't help Making an EDL cable to force boot to EDL mode. Fastboot command came back restricted command and did nothing. Maybe flashing from EDL will make a difference.

eluallen said:
Couldn't get the link to work from the LG phone I'm using. Once I got the Moto working it went to the link no problem. Only issue now is no IMEI. Flashing NON-LOS and fsg don't help Making an EDL cable to force boot to EDL mode. Fastboot command came back restricted command and did nothing. Maybe flashing from EDL will make a difference.
Click to expand...
Click to collapse
U need blank flash for ur phone carrier

roadkill42 said:
U need blank flash for ur phone carrier
Click to expand...
Click to collapse
I didn't know the blank-flash files were carrier specific. How do you find out which carrier they are for? I have for PCOS29.114-134-2 but that number is used for multiple carriers. And when using edl cable is the phone supposed to be off to use it? If you've ever used that method.
Never mind about the phone needing to be off. Just found a video about using the cable that said it needs to be off.

You tell by the model number. For example, mine is XT1955-5 (MetroPCS).

fddm said:
You tell by the model number. For example, mine is XT1955-5 (MetroPCS).
Click to expand...
Click to collapse
If ur metro T-Mobile or on consumer celuiar u can use retus firmware less bloat