Database Info

[Q]Anyone have a stock KitKat image for RSD-Lite? Bricked phone

Well, I bricked my phone because I'm assuming I made a change to one of the read-only partitions that gets checked for the OTA update. Phone is bricked. Can't flash anything right now. Returned to LOCKED status. Can't even get the unlock code anymore. Also tried the unlock code from my e-mail a few years back. So, that's all out. Can't flash older images with RSD-Lite even after removing the get-var, partition and tz lines from XML. I've heard of people restoring their phones with the exact same Fastboot screen except they had the older bootloader. That's why I suspect I need a stock KitKat image...
It's an XT925 (my spare).
Code:
AP Fastboot Flash Mode (S)
10.9B(*) (sha-07671a2, 2014-07-29 12:35:27)
eMMC Info: Size 16GB
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
usb connected

damn dawg, another of the same....you ll be back, however there is no KK image for xt 925. Join this thread...http://forum.xda-developers.com/showthread.php?t=2273574&page=4
---------- Post added at 12:52 PM ---------- Previous post was at 12:46 PM ----------
use this too
http://forum.xda-developers.com/droid-razr-hd/help/xt925-fastboot-reaoninvalid-gpt-flash-t2949748
Scourge1024 said:
Well, I bricked my phone because I'm assuming I made a change to one of the read-only partitions that gets checked for the OTA update. Phone is bricked. Can't flash anything right now. Returned to LOCKED status. Can't even get the unlock code anymore. Also tried the unlock code from my e-mail a few years back. So, that's all out. Can't flash older images with RSD-Lite even after removing the get-var, partition and tz lines from XML. I've heard of people restoring their phones with the exact same Fastboot screen except they had the older bootloader. That's why I suspect I need a stock KitKat image...
It's an XT925 (my spare).
Code:
AP Fastboot Flash Mode (S)
10.9B(*) (sha-07671a2, 2014-07-29 12:35:27)
eMMC Info: Size 16GB
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
usb connected
Click to expand...
Click to collapse

Thanks! Anyway, at least I ripped the modem partition using "dd if=/dev/block/mmcblk0p1 of=modem.img" before I bricked it... I managed to do the Fido update the first time around. I think that's where I went wrong... I was going to try testing this on another stock KitKat image (which I needed to OTA upgrade to). That's when it died.
I've been waiting forever for this Rogers/Fido KitKat modem file. Never been able to find another stock image to give me the same speeds. Problem is, it's stuck on my SD card. Anyone need this file? Or can test it out for me? Lol.

Scourge1024 said:
Thanks! Anyway, at least I ripped the modem partition using "dd if=/dev/block/mmcblk0p1 of=modem.img" before I bricked it... I managed to do the Fido update the first time around. I think that's where I went wrong... I was going to try testing this on another stock KitKat image (which I needed to OTA upgrade to). That's when it died.
I've been waiting forever for this Rogers/Fido KitKat modem file. Never been able to find another stock image to give me the same speeds. Problem is, it's stuck on my SD card. Anyone need this file? Or can test it out for me? Lol.
Click to expand...
Click to collapse
Sherwood Park? I'm in Spruce Grove. Small world. Follow the thread links, there seems to be a lot of XT925 folks soft-bricking (in some case, hard-bricking) their devices. You should hopefully be able to get back on track.

since you are a FIDO dude, give that gpt , tz a try

Well, successful flashing of the partition and tz so far... Things are looking up!!!
UPDATE: rsd-lite is currently at flashing the system partition... Almost just a few more steps... Thanks very much!!!
I'm also linking your file again. It might be redundant but, it could help someone else!
http://forum.xda-developers.com/showpost.php?p=57178291&postcount=15
C:\Android\XT925>..\tools\fastboot.exe flash partition gpt.bin
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'partition' (32 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
OKAY [ 1.343s]
finished. total time: 1.374s
C:\Android\XT925>..\tools\fastboot.exe flash tz tz.mbn
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'tz' (210 KB)...
OKAY [ 0.016s]
writing 'tz'...
OKAY [ 0.519s]
finished. total time: 0.550s
Click to expand...
Click to collapse

you've got it Boss!!!!!!!!!!!!!!!!!!!!!!!!!
p.s credit KABALDAN for pointing to the solution , wihtout him I would have spent few more hours trying to troubleshoot the isht lol, and thanks to the good fellows here like Bwen dior, Coincoin, CWGSM3VO...and few others
we may nee a thread stickied with all the OTA we can catch,or just the tz/gpt from them , that may be the solution to the few bricks happening

CWGSM3VO said:
Sherwood Park? I'm in Spruce Grove. Small world. Follow the thread links, there seems to be a lot of XT925 folks soft-bricking (in some case, hard-bricking) their devices. You should hopefully be able to get back on track.
Click to expand...
Click to collapse
Yeah, I work on 170st in Edmonton though. Selling car parts of all things (yet have a firm grasp of Linux). Luckily it's dead enough here that I was able to fix my phone. Not a lot of demand for performance car parts in winter.

Scourge1024 said:
Yeah, I work on 170st in Edmonton though. Selling car parts of all things (yet have a firm grasp of Linux). Luckily it's dead enough here that I was able to fix my phone. Not a lot of demand for performance car parts in winter.
Click to expand...
Click to collapse
JB Power Centre?
I'm a TELUS wog myself.
Good stuff in getting your phone fixed. A lot of folks bricking XT925's lately.

CWGSM3VO said:
JB Power Centre?
I'm a TELUS wog myself.
Good stuff in getting your phone fixed. A lot of folks bricking XT925's lately.
Click to expand...
Click to collapse
Actually Mopac. Close guess though! I'm one of the lucky bastards with a desk.

Scourge1024 said:
Actually Mopac. Close guess though! I'm one of the lucky bastards with a desk.
Click to expand...
Click to collapse
Me too I'm a Lab Engineer in the Optik TV Lab. Allows me a lot of flexibility.

I was just about to trash my phone or buy another motherboard but hbenz2008 saved my day (and a lot of cash!)
THANKS! flashing the tz and partition revived my phone in a snap! Just flash it and reboot!
(I feel absolutely newbie right now)

Really really hard soft-bricked my Mate MT-TL10. Need help!

Hi guys. I really need your help.
Sometimes I am so stupid and doing really stupid things. Now I killed my MATE MT-TL10. and I think it is dead forever But I still have a hope someone can help me. So here is the story.
I was trying different ROMs to find a good one so I am satisfied with it. So all was good and I was putting it one after another trying(I never put Lolipop though), but then I put a Cinise version B122SP06. Seeing a lot of chinese apps I decided I do not need it and wanted to go back to international or europeaan version but it seemed I was not able to do it. Every time I put a new ROM in dload on my sd and restart on stock recovery it won't fatch it I was making some reaearch and found this like semi-solution http://forum.xda-developers.com/showthread.php?t=2955415 wich was manually flash some images with fastboot. I did that and nice I had a clean european version! But then I digged into settings and found out that 'Motion Control' section is Empty! So apparently the solution from the mentioned thread was not perfect also my PC was seeing the phone as JAZZ which means it thinks it was still Chinise version. And then all of a sudden some stupid thing came into my mind and that was really-really-really STUPID! Never try it!
So I decided to make an experiment. In this tool which I used to unpack the ROM there is also a function 'Repack to update.zip', so I was hoping to repack it to a zip and then just flash it with a CWM recovery. Well I did it and after i selected 'Reboot system now' the phone restarted and just stayed at the Huawei Logo. That's it! and now I do not know how to recover my phone. I tried to go into recovery but no luck I just can't boot into recovery anymore. I was able to plugin the phone in the fastboot mode and try to re-flash everything again, like with 'fastboot flash boot boot.img', 'fastboot flash recovery recovery.img' and even some others but no luck so far. I still can't get into recovery. I do Up+Down+power and when it suppose to start recovery the screen just appears black and indicator is blinking green and red and then just turns off.
Sorry about my bad English and for the long strory but here how the whole thing has happened to me I really really hope I did not kill it complitely and I hope there is a guy who can really point me out to the solution. So, please, please
Here is a copy of text which was in the /META-INF/com/google/androidupdater-script of the repack.zip file which I have created
ui_print("Flashing 10.boot.img ...");
package_extract_file("10.boot.img", "/dev/block/mmcblk0p13");
ui_print("Flashing 11.recovery.img ...");
package_extract_file("11.recovery.img", "/dev/block/mmcblk0p14");
ui_print("Flashing 12.sensorhub.img ...");
package_extract_file("12.sensorhub.img", "/dev/block/mmcblk0p17");
ui_print("Flashing 17.dts.img ...");
package_extract_file("17.dts.img", "/dev/block/mmcblk0p20");
ui_print("Flashing 18.modemnvm_update.img ...");
package_extract_file("18.modemnvm_update.img", "/dev/block/mmcblk0p29");
ui_print("Flashing 20.modem_dsp.img ...");
package_extract_file("20.modem_dsp.img", "/dev/block/mmcblk0p27");
ui_print("Flashing 21.3rdmodem.img ...");
package_extract_file("21.3rdmodem.img", "/dev/block/mmcblk0p31");
ui_print("Flashing 13.cust.img ...");
package_extract_file("13.cust.img", "/dev/block/mmcblk0p37");
ui_print("Flashing 14.system.img ...");
package_extract_file("14.system.img", "/dev/block/mmcblk0p38");
ui_print("Flashing 15.cache.img ...");
package_extract_file("15.cache.img", "/dev/block/mmcblk0p39");
ui_print("Flashing 16.userdata.img ...");
package_extract_file("16.userdata.img", "/dev/block/mmcblk0p40");
There was also some META-INF/com/google/android/update-binary file which I do net really know what it is for.
My thought are this 'repack' made some mess up with the paratitions on my device and even though I am able to flash the RECOVERY the system just does not see it. Or perhaps it did even something worth ;-(
Please guys, help :crying:

Addition
At least say me if it is recoverable or I can just throw it away. Thank's GOD I did not sell my old Galaxy S3 yet.

Without having proper instructions, but as long as you are having fastboot access your device should be recoverable.
What i find strange is that flashing a Rom should never touch your recovery... I would Start with wiping through fastboot, redownloading a recovery and reflashing it.
Sent from my HUAWEI MT7-L09 using XDA Free mobile app

Just remembered, after flashing my weird home-made update.zip and before selecting 'reboot system now' from CWM recovery I think I saw a message 'Canno't mout /recovery' among logs in the CWM recovery window. I'm afraid I screwed up a part of my phone which is responsible of mounting partitions. So what is this part and is there a way to refresh/reflash it with fastboot somehow or in some other way?

Can't erase
domsch1988 said:
Without having proper instructions, but as long as you are having fastboot access your device should be recoverable.
What i find strange is that flashing a Rom should never touch your recovery... I would Start with wiping through fastboot, redownloading a recovery and reflashing it.
Sent from my HUAWEI MT7-L09 using XDA Free mobile app
Click to expand...
Click to collapse
fastboot erase system
erasing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 0.001s
Seems like I can't erase anything, it always says FAILED (remote: Command not allowed)

guest73 said:
fastboot erase system
erasing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 0.001s
Seems like I can't erase anything, it always says FAILED (remote: Command not allowed)
Click to expand...
Click to collapse
Is your Bootloader unlocked? Normally "command not allowed" indicates a locked boot loader...

domsch1988 said:
Is your Bootloader unlocked? Normally "command not allowed" indicates a locked boot loader...
Click to expand...
Click to collapse
Well I requested the unlock code from Huawei and they have provided it to me. Then I unlocked the phone following instructions on some resource, at least it's what it says in the FASTBOOT&RESCUE MODE, there is a red text saying 'PHONE Unlocked'. Also I am able to run commands like 'fastboot flash recovery', 'fastboot flash cust' and it works but on the other hand commands like 'fastboot flash modem', 'fastboot erase cache', 'fastboot erase cust' etc. do not seem to work always giving me 'Command not allowed' Looks like it is semi-unlocked I'm really stuck. Maybe try to lock/unlock it again. I doubt it would make any difference.
Thank you for trying to help btw.

I remember that from the HTC one x. HTC provided the unlock but intentionally didn't allow certain Operations. That was called s-on/s-off back than...
What ever, this means that you wouldn't really be able to brick this device. Since i only have this thing for two days i think i'm not really able to help you more... Sorry mate...
Sent from my HUAWEI MT7-L09 using XDA Free mobile app

It seems your bootloader is not properly unlocked...

tuddu said:
It seems your bootloader is not properly unlocked...
Click to expand...
Click to collapse
And how to unlock it properly? With a different procedure or with a different code? Isn't this code unique to the phone? I got mine from Huawei by sending a request.

Shoul be. Somewher else I posted the link where to find instructions regarding unlocking bootloader. I try to find it for you and re-post here.
Inviato dal mio HUAWEI MT7-L09 utilizzando Tapatalk
---------- Post added at 08:37 AM ---------- Previous post was at 08:03 AM ----------
Ok, try this: http://mate7.net/ascend-mate7-bootloader-unlock/
Time ago B120 firmware worked perfectly for me. Should be still fine for you as well.

Ok
tuddu said:
Shoul be. Somewher else I posted the link where to find instructions regarding unlocking bootloader. I try to find it for you and re-post here.
Inviato dal mio HUAWEI MT7-L09 utilizzando Tapatalk
---------- Post added at 08:37 AM ---------- Previous post was at 08:03 AM ----------
Ok, try this: http://mate7.net/ascend-mate7-bootloader-unlock/
Time ago B120 firmware worked perfectly for me. Should be still fine for you as well.
Click to expand...
Click to collapse
Thanks man but it seems like their official Huawei bootloader unlocker cite is not working anymore, giving Forbidden request. But it won't help anyway, device is unlocked so... I will bring it to service center so they can do re-flash with some hardware tool by connecting it to a special port on motherboard, at least that's how my friend explained to me how it can be done. I expect it to cost arount 15-20$. Compared to the phone's price it is not so much. And of course it would be a lesson for me to not make experiments

This is the end, Huawei sucks!
Well I've got my device from the service center. They was not able to repair it.
I did some googling and well there is a wonderful solution, something with RIFF/Jtag involved. BUT it's NOT applicable to this stupid phone as it has this custom Kirin chipset. So cool! you have a physically workable device but you can't fix it's software in any possible way. Great job Huawei. I think this was my last huawei device ever. So guys, think twice when you wanna buy something with a 'homemade' chip as you may get into big trouble if anything ever happens to it.
Ok, what's left is to fully replace a motherboard and it's so expensive! For Huawei P8 it costs around 196$, but the problem is I can't find the mainboard for MT7 anywhere on the Internet. That's really sucks! I wrote to huawei if I can order mainboard from them but no response so far. I am waiting a couple of more days. If I not find the motherboard I will have to sell the device for spare parts and say Good Bye huawei forever! Also would be nice if anyone will help me to find it. Thanks.

More sucks
I contacted another Service asked if they can order the mainboard for me. The good news is Yes they can, and bad news - it will cost around 280$ total(mainboard+repearing). Hell no!!! I am selling this sh*t out!

same problem here
I am also not able to install a bootloader

Posting just for informational purposes.
I have sold the device. The guy who bought it said that he has an idea how to recover it. So he would unsolder the memory chip and solder it to another phone(he deal with some other guy about it, have no idea what that other phone is, probably some Huawei device) then he will do some flashing-restoring on that other phone and than solder the chip back to original device. Sounds very interesting and promising but I am not sure it would work. Well good luck to the guy . The only thing I am really sure about is that I watched on youtube how to disassemble MT7 and it is very very hard process but it's not my headache anymore

suicide squad

ItS 2019 and no solution , i have the same problem. My mate just been laying in error 12 Func_Load_IOM3 (rescue mode).
Anybody found solution?
i hear Dc phoenix works

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.

LG ARISTO [LG M210 T mobile]

Hey guys! How ya doing?
Im pretty straightforward so I'll make this fast.(like myself in bed with a 10/10)
I need some help on my LG Aristo (T-Mobile).
The problem is I rooted it via fastboot with twrp and everything went great for the first few days until it started to flash gray and wanted to become an alien.
I wasn't worrying cause im a thug.
So I attempted a re-flash & I erased the recovery then re-flashed it.
Until the blinky gray alien screen started happening again.
For a few days I tried everything and the gray flashing screen wouldn't go away.
So I did the following fastboot commands and it went away.
Fastboot erase cache
Fastboot erase userdata
Fastboot erase system
Fastboot erase recovery
Satisfied that the gray flashing finally went away I reflashed it with the twrp recovery.
Only this time when I booted into twrp to install No-verity and SU all I seen was
Failed to mount :/system
Failed to mount :/userdata
Failed to mount :/recovery
And the phone did a reboot and was acting funny.
I then re-flashed the boot, recovery and the modem imgs that I extracted from the KDZ myself. And it actually booted but stays stuck at the LG Logo.
I couldn't flash the system img as I kept getting a "max target size download of 190840823 bytes" error.
I looked into it and a friend mentioned to forget it and to just flash the KDZ File with a LG flash tool.
I tried this only every flash tool I used did not pick up my device model. (yes I had all correct LG Drivers installed)
Aftering searching online I also tried to replace the fastboot exe with mfastboot. But it did not work as I keep getting the same error but it said target -max-download size of: 250mb and my system.img is about 2GB+..
Also, the mfastboot was made for moto devices (I found a XDA thread that linked it) and not lg. But it didn't work anyway.
I really think everything will be solved once I flash my system img but I keep getting errors about the size limit. (If you know of a way to fix this let me know.)
:good:I've already tried the following so please don't bring them up::good:
*Erasing everything via fastboot ( doesn't do anything)
*Putting phone into DL mode to flash KDZ and TOT file with phone dll via LG flash tools.(2014 and 2016) ( kept getting a (s) failed to load error)
*Re-flashed stock imgs (done it all but system img. I don't know why It keeps giving errors, yes I put it in android sdk platform tools folder)
* Put phone in dl mode and use LGUP/uppercut method. ( Kept getting "No handsets connected" errors". Phone wasn't recognized no matter what drivers I used.)
*Try different ports on pc and latest drivers. ( Yeah, I spent a week searching for all drivers and my pc isnt a virgin anymore as I stuck in the usb in all her holes)
*Relentlessly search XDA and other forums for solutions to no prevail. (This phone is irrelevant and no one cares about it)
:good:What I haven't tried::good:
*Breaking the mother****er and just buying a s5.
Greatly appreciate any help and also can XDA add the LG Aristo to the "my devices"? I had to pick a s8 so I didn't look broke.:silly:
I didn't seen an LG Aristo and There is NO forums for this problem or even for this phone in that matter.

Confxsed said:
I really think everything will be solved once I flash my system img but I keep getting errors about the size limit. (If you know of a way to fix this let me know.)
Click to expand...
Click to collapse
No one has a fix for this?

Dayuuum
Fuuu, that's hardcore.

Where is the dang lg m210 developers section? It's a very popular device and there is a ton of interest in rooting it. I can't seem to find the device thread here on XDA. ..
Sent from my SM-N910T using XDA-Developers Legacy app

Are you trying to root it? I can give you the twrp for the device and such and a rooting method. I rooted mine successfully its just I think I messed it up by stepping on it lmao

how did u root it

1118niranjan said:
how did u root it
Click to expand...
Click to collapse
I would post a link but I cant. Just google it and look for the getandroidtips website. I rooted it by working with friends on android forums. But that website getandroidtips has a better understanding.

Confxsed said:
I would post a link but I cant. Just google it and look for the getandroidtips website. I rooted it by working with friends on android forums. But that website getandroidtips has a better understanding.
Click to expand...
Click to collapse
pm then

Need some to dump the firmware of LG M210.
Now i have LG UP tool to dump all partitions from LG M210, But i need to find a working LG M210 phone.
Also, if anyone who need to bypass LG M210 Goolge FRP can PM me, Let me try the Chip erase feature on LG UP
---------- Post added at 12:04 PM ---------- Previous post was at 12:02 PM ----------
Confxsed said:
No one has a fix for this?
Click to expand...
Click to collapse
I think the chip erase feature on LG UP can fix the issue you mentioned, after erase the chip, flash kdz firmware with LG UP tool.
But the chip erase feature do erase IMEI information too..
---------- Post added at 12:04 PM ---------- Previous post was at 12:04 PM ----------
Confxsed said:
No one has a fix for this?
Click to expand...
Click to collapse
I think the chip erase feature on LG UP can fix the issue you mentioned, after erase the chip, flash kdz firmware with LG UP tool.
But the chip erase feature do erase IMEI information too..
if you like to try, PM me and let us works together on teamviewer to fix it.

Confxsed said:
Are you trying to root it? I can give you the twrp for the device and such and a rooting method. I rooted mine successfully its just I think I messed it up by stepping on it lmao
Click to expand...
Click to collapse
Think I could get a copy of rhythm twrp not root method

frp lock
i bought this phone from a pawn shop for cheap but i find out im frp locked out.. how can i get passed this?

Use Uppercut with MS210 Firmware Typically, if you can't get LG Bridge to recognize device you should pull the battery out with the cable disconnected, reinstall the batter and then hold the Volume Up button and then plug the USB cable in while it's connected to yuor PC. Welcome to the miserable world of LG

Any solution for frp lg ms210?

Has anyone had any luck unlocking this phone?I would like to switch from T-mobile to Freedompop.

Confxsed said:
Hey guys! How ya doing?
Im pretty straightforward so I'll make this fast.(like myself in bed with a 10/10)
I need some help on my LG Aristo (T-Mobile).
The problem is I rooted it via fastboot with twrp and everything went great for the first few days until it started to flash gray and wanted to become an alien.
I wasn't worrying cause im a thug.
So I attempted a re-flash & I erased the recovery then re-flashed it.
Until the blinky gray alien screen started happening again.
For a few days I tried everything and the gray flashing screen wouldn't go away.
So I did the following fastboot commands and it went away.
Fastboot erase cache
Fastboot erase userdata
Fastboot erase system
Fastboot erase recovery
Satisfied that the gray flashing finally went away I reflashed it with the twrp recovery.
Only this time when I booted into twrp to install No-verity and SU all I seen was
Failed to mount :/system
Failed to mount :/userdata
Failed to mount :/recovery
And the phone did a reboot and was acting funny.
I then re-flashed the boot, recovery and the modem imgs that I extracted from the KDZ myself. And it actually booted but stays stuck at the LG Logo.
I couldn't flash the system img as I kept getting a "max target size download of 190840823 bytes" error.
I looked into it and a friend mentioned to forget it and to just flash the KDZ File with a LG flash tool.
I tried this only every flash tool I used did not pick up my device model. (yes I had all correct LG Drivers installed)
Aftering searching online I also tried to replace the fastboot exe with mfastboot. But it did not work as I keep getting the same error but it said target -max-download size of: 250mb and my system.img is about 2GB+..
Also, the mfastboot was made for moto devices (I found a XDA thread that linked it) and not lg. But it didn't work anyway.
I really think everything will be solved once I flash my system img but I keep getting errors about the size limit. (If you know of a way to fix this let me know.)
:good:I've already tried the following so please don't bring them up::good:
*Erasing everything via fastboot ( doesn't do anything)
*Putting phone into DL mode to flash KDZ and TOT file with phone dll via LG flash tools.(2014 and 2016) ( kept getting a (s) failed to load error)
*Re-flashed stock imgs (done it all but system img. I don't know why It keeps giving errors, yes I put it in android sdk platform tools folder)
* Put phone in dl mode and use LGUP/uppercut method. ( Kept getting "No handsets connected" errors". Phone wasn't recognized no matter what drivers I used.)
*Try different ports on pc and latest drivers. ( Yeah, I spent a week searching for all drivers and my pc isnt a virgin anymore as I stuck in the usb in all her holes)
*Relentlessly search XDA and other forums for solutions to no prevail. (This phone is irrelevant and no one cares about it)
:good:What I haven't tried::good:
*Breaking the mother****er and just buying a s5.
Greatly appreciate any help and also can XDA add the LG Aristo to the "my devices"? I had to pick a s8 so I didn't look broke.:silly:
I didn't seen an LG Aristo and There is NO forums for this problem or even for this phone in that matter.
https://www.youtube.com/watch?v=
Click to expand...
Click to collapse
Upssss, may be too late but... Did you find a solution for your issue?

I'm going to break this M*****F*****
can someone make a damn video guide to firmware rebooting this damn phone I'm going through hell Z.Z

DarkKingKiyo said:
can someone make a damn video guide to firmware rebooting this damn phone I'm going through hell Z.Z
Click to expand...
Click to collapse
What is the exact issue?
What did you do that cause the trouble?
What have you already test to fix this problem?

can plzz share how you root the lgm210..really some help rooting my device
can plzz share how you root the lgm210..really some help rooting my device

Shatrel said:
can plzz share how you root the lgm210..really some help rooting my device
Click to expand...
Click to collapse
https://messi2050.blogspot.com/2017/02/root-twrp-v3-for-lg-aristo-metropc-t.html?m=1
Pretty sure applies to Tmo and Metro

wamz100 said:
Think I could get a copy of rhythm twrp not root method
Click to expand...
Click to collapse
I need a twrp backup .zip file for this phone. I accidentally wiped my system

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