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.
Related
[Q] WiFi/BT broken, stuck at "Starting Services" in ALL ROMs and Stock? Help please!
Hello! After a misadventure I managed to get CM 10.2 to run on my Photon Q, and it was fantastic! Wifi and BT work great. However, accidentally flashing the wrong kernel, I got stuck at the bootloader unlocked screen forever.
So, I reinstalled CM 10.2 and all seemed to be well. (I did this from CWM using a ZIP.) However, I quickly discovered WiFi and BT are both broken! If I hit ON, it goes gray for a second and tries to enable, and goes back to OFF with no error or other response. If I open the WiFi or BT menu and hit ON or SCAN, same result or it just does nothing.
So, I tried to downgrade to something older, something with ICS and not JB, which is what I prefer anyway. TwistedAsanti gets stuck forever at "Starting Services..." and the home screen never comes up, even if left overnight. I get a message that no cell networks were found asking if I want to switch to GSM. It's covered by STARTING SERVICES ... so I can't hit "No", but either way I don't have a carrier, so that's no issue. I use WiFi only. I can pull down the notification bar and go into settings. While there, I see the same problem with WiFi and BT, both are broken. I can't run any apps or get to the homescreen, still.
So, I tried to install 10.1, same result. Then MIUI, Carbon and SlimBean. Same result! I installed TWRP and flashed a backup of Stock JB from WIN files I found here on the forum. It boots up, but this time it's stuck at "Starting Services..." just like TwistedAsanti was. Notification bar works, settings menu works, homescreen won't appear, Starting services never goes away, can't run any apps. Wifi and BT still broken in the same manner.
Now downloading a backup of ICS Stock to see if that works any better, but I'm not holding my breath.
Has anyone ever experienced this? Thanks for any advice. I attached some photos that might help. I had to use my Tracfone because now that is the best camera I have access to, so sorry for the blurriness. I hope it gives you the general idea of what is going on.
EDIT: For each flash, I am wiping data, cache and dalvik cache. I also wiped modem and pds by mistake, could that be the problem? If so, how would I restore those? Thanks
Again, thanks for your time!
Jeez, how many threads do you need to post in? I have responded to all your posts in all of the various threads, INCLUDING your PM's.
Let's focus here, if you want custom we can do that. If you want stock we can do that. Please focus, what do you want.
If you want custom, perhaps you're not wiping everything properly... So boot recovery. Wipe system. Factory reset - wipe data, cache, dalvik-cache, sd-ext. Best to do the actual "factory reset" option than wiping all of those by hand, because wiping /data will wipe /data/media (internal SD) while factory reset will preserve /data/media.
Next, flash ROM of your choice. Twisted Asanti is kinda outdated, hasn't had any attention in a loooong time. Let's try something stable, CM10.1. Flash it. Flash gapps. Boot, do you still have the same issues?
Probably the wrong kernel is still flashed, you need to flash the stock kernel.
Wiping modem and pds could be the problem.
The first I would do in your position is to flash with RSD the stock ROM. This Thread -> http://forum.xda-developers.com/showthread.php?t=2095536
edit: If you post in several threads and try different things "in" different threads we won't be able to help you.
EVERYTHING in one thread and we may see what you have done and where you have had problems.
You should keep it simple and give all information in one good structured post so we don't have to read pages to see what you did.
Loader009 said:
Probably the wrong kernel is still flashed, you need to flash the stock kernel.
Wiping modem and pds could be the problem.
The first I would do in your position is to flash with RSD the stock ROM. This Thread -> http://forum.xda-developers.com/showthread.php?t=2095536
edit: If you post in several threads and try different things "in" different threads we won't be able to help you.
EVERYTHING in one thread and we may see what you have done and where you have had problems.
You should keep it simple and give all information in one good structured post so we don't have to read pages to see what you did.
Click to expand...
Click to collapse
Sorry about that. I'll keep it in one place. Thanks Still trying to get RSD to work, but it won't detect the phone for some reason. Well, on one PC it will, but then it fails to flash saying there was a Remote error (FAIL). On another PC, it won't detect. In BOTH cases, fastboot devices successfully shows the phone. I can even format partitions and flash files. I have successfully flashed TWRP this way.
trying to flash the system image doesn't work with the error "invalid sparse file format at header magi", then fastboot crashes. (What?) So, RSD doesn't work and fastboot kinda works, but not for all the images.
I got a copy of all the kernels I could find .. arrrghhh's for every FW I can think of. Searching out a stock kernel now. It says on the Peas and Q's post that it's just a stock FW with a new name, so I grabbed that too, might be worth a shot...
got CM 10.1, I guess I'll try installing that, and then what do I want, the STOCK kernel? or just use the one that it came with? (How confusing.)
To be more clear, either Stock or Custom is fine. I'm happy with either so long as it boots properly and WiFi works again. Root would be nice but I can worry about that later.
You don't have to quote whole posts (just press "QUICK REPLY").
The most important thing is to get RSD to work.
I'm not the guy where you get information about RSD and kind of. I know where to look for and show the right direction.
In the thread I posted you might get help for RSD and you could get help there.
Ask there for help as the more experienced users are reading only the "important" threads and not the "smaller" ones.
(I know this, I do this most time, but I'm not the "know-everything" guy )
As I never needed those FXZ method, I never used it and my RSD Lite experience is rather small.
You might need to install motorola drivers to get it to work but I'm not sure, you should ask in that thread.
PS: If Stock will work again, Custom will work too.
To avoid problems it might be needed to wipe data/cache/dalvik before and after flashing a ROM.
Loader009 said:
You don't have to quote whole posts (just press "QUICK REPLY").
The most important thing is to get RSD to work.
Click to expand...
Click to collapse
I got RSD to see the phone using a different PC. When I try to flash "asanti_c-user-4.0.4-7.7.1Q-6_SPR-89_ASA-36-42-release-keys-Sprint-US.xml" it gets all the way up to flashing "system", which is one of the last steps, then it says the device reported FAIL. This is the same file I couldn't get to flash with fastboot when I was trying to do it manually. But in that case, fastboot crashed entirely.
Not sure what to try now ...
Did you read the following?
Skrilax_CZ said:
NOTES
- use at least RSD Lite 6.1.5 (maybe 6.1.x will work too) or you get an error on flashing system.img.ext4
- you may have to open the zip and edit the xml, and delete the 2 lines "<step operation="getvar" var="max-download-size" />" if you get unknown command fastboot getvar max-download-size
- do not flash Sprint firmware to phone from Cellular US and vice versa unless you know what are you doing!!!
Click to expand...
Click to collapse
As I said, I never tried the FXZ method and I have no experience on error which could appear.
Ask in that FXZ thread and you may get it work soon.
Epicenter714 said:
I got RSD to see the phone using a different PC. When I try to flash "asanti_c-user-4.0.4-7.7.1Q-6_SPR-89_ASA-36-42-release-keys-Sprint-US.xml" it gets all the way up to flashing "system", which is one of the last steps, then it says the device reported FAIL. This is the same file I couldn't get to flash with fastboot when I was trying to do it manually. But in that case, fastboot crashed entirely.
Not sure what to try now ...
Click to expand...
Click to collapse
Try a different port? Different cable? Different computer? Are you using the stock cable?
Perhaps something else is broken... I'm not sure at this point. Do you have any screenshots of the failure? Any specific output from the software?
Did you edit the XML file properly? I think you did, but you said you were downgrading too - are you always trying ICS or have you tried the FXZ file for JB as well?
Useless thread bump.
Another fellow had the same issue, and was using an old version of RSD Lite. What version are you using?
I faced same problem.
Just use latest veersion of RSD lite, 6.0 is ok
and do not forget to remove two getvar commands from xml file.
I tried same and now my phone is alive. But now.IMEI/MEID is gone (zero)
WIFI and bluetooth is now connecting but not receiving any data (useless).
I tried many cdma tool to recover MEID but failed.
I thing we lost EFS partition.
Please look at my thread
http://forum.xda-developers.com/showthread.php?t=2429609
i also need help on that
If any one have EFS backup or something?
lovepreet39 said:
I faced same problem.
Just use latest veersion of RSD lite, 6.0 is ok
and do not forget to remove two getvar commands from xml file.
i also need help on that
If any one have EFS backup or something?
Click to expand...
Click to collapse
The problem WAS RSD's version! Thanks to everyone for your help. I had 5.6.4 running before and it would always die at System.img.ext4 and one other partition later on. That's on the WinXP system that would see the phone in RSD. The Win8 machine wouldn't see it at all, even in XP compatibility mode with admin rights. Go figure. I'll take this as another excuse to not be fond of Win8.
I checked and my phone has boot, system, recovery, data, pds and modem, but no EFS. I'm not familiar with that .. Isn't EFS a filesystem type, not a partition? Like EXTFS?
Epicenter714 said:
I checked and my phone has boot, system, recovery, data, pds and modem, but no EFS. I'm not familiar with that .. Isn't EFS a filesystem type, not a partition? Like EXTFS?
Click to expand...
Click to collapse
I don't understand, are you still having issues? Why are you asking about EFS?
arrrghhh said:
I don't understand, are you still having issues? Why are you asking about EFS?
Click to expand...
Click to collapse
I was replying to lovepreet39 about the EFS thing.
Epicenter714 said:
I was replying to lovepreet39 about the EFS thing.
Click to expand...
Click to collapse
EFS is a partition which contain your IMEI/MEID and Mac address information.
Please check in your settings is your IMEI/MEID there.
I gone from same problem and now IMEI/MEIS is zero.
---------- Post added at 03:54 PM ---------- Previous post was at 03:46 PM ----------
@arrrghhh
Please look at my thread, i also need help
Epicenter714 said:
I was replying to lovepreet39 about the EFS thing.
Click to expand...
Click to collapse
Yes, but he is having an issue with EFS. You, on the other hand, are not... correct?
You post seems to indicate that despite getting RSD to work, you are still having issues. I want to make sure that is not the case...
lovepreet39 said:
EFS is a partition which contain your IMEI/MEID and Mac address information.
Please check in your settings is your IMEI/MEID there.
I gone from same problem and now IMEI/MEIS is zero.
---------- Post added at 03:54 PM ---------- Previous post was at 03:46 PM ----------
@arrrghhh
Please look at my thread, i also need help
Click to expand...
Click to collapse
Hey buddy, I would love to help but that is way above my pay grade. I used my Q on Sprint, never liked mucking with that stuff personally.
@arrrghhh
Dear sir
Problem is that i wasted approx $250 on this device.
I am indian and $1 = Rs65 and $250 = Salary of one month.
I am here on XDA to save my $250.
There is no support on this phone in indian market,
If there any solution please help.
You can post here or PM me.
Or there is only by which i can only get my IMEI back, then i will apply GSM addon on it,
I do not care much about CDMA.
I know IMEI/MEID repair is illegal in USA.
For proof I can provide you original images of phone showing Zero Imei/meid
I do not want to change, only i want to restore original one.
Hey guys,
I decided to share my horrible experience - as title says - with lost IMEI.
Some of you may remember that couple of months ago there were some posts here regarding lost IMEI and possible solutions and questions how is it possible to loose IMEI in the first place.
I remember at least three guys managed to do that by running "fastboot erase all".
What was my story?
Yesterday I decided to flash a new recovery (last two months I haven´t flashed anything and wasn´t active on the forum because of lack of time and I started to show signs of withdrawal syndrome ). My first mistake was that I flashed non-gpe recovery to my device with GPE rom, obviously that couldn´t work because of incompatibility in file systems. Nevermind, that happened before and it´s easy to go back to a proper recovery. But not this time. Tried hundred times, but flashing with fastboot always ended up by "OKAY" but the old recovery remained in place for some reason unknown to me. And also the system wouldn´t boot. Out of desperation I ran "fastboot erase recovery", that wouldn´t help either. In the end I got out of the situation by booting (not flashing) to a proper recovery (fastboot boot recovery recovery.img) and restoring system from a nandroid backup. All seemed fine. ROM booted OK and then I realized I had no service and IMEI: unknown.
The only reason for that was obviously this unfortunate move: fastboot erase recovery. Anything else I did was pretty much "normal".
Here comes the second part of the story.
I downloaded my cloud-stored pds.img backup (lucky me I have it I thought to myself) but that didn´t prove to be of any use.
When running
Code:
adb shell
su
dd if=/sdcard/pds.img of=/dev/block/platform/msm_sdcc.1/by-name/pds
as seen on
http://forum.xda-developers.com/showthread.php?t=2537119
nothing happened. Dd ran too fast, just a fraction of a second and after reboot still IMEI: unknown.
To cut the long story short, after hours of searching for a possible solution (and thinking what would be my next phone) I finally came across this post:
http://forum.xda-developers.com/showpost.php?p=45881991&postcount=86
and tried that very easy method and it worked!
Takeaway messages:
1. don´t use fastboot erase "all" or "recovery" (other partitions may be erased without problems)
2. pds partition backup and restore method didn´t work for me
3. working solution (at least for me):
Remove sim, flash stock firmware using standard methods, boot to home screen, power off, insert sim, reboot and your IMEI should be back!
drfr said:
Hey guys,
I decided to share my horrible experience - as title says - with lost IMEI.
Some of you may remember that couple of months ago there were some posts here regarding lost IMEI and possible solutions and questions how is it possible to loose IMEI in the first place.
I remember at least three guys managed to do that by running "fastboot erase all".
What was my story?
Yesterday I decided to flash a new recovery (last two months I haven´t flashed anything and wasn´t active on the forum because of lack of time and I started to show signs of withdrawal syndrome ). My first mistake was that I flashed non-gpe recovery to my device with GPE rom, obviously that couldn´t work because of incompatibility in file systems. Nevermind, that happend before and it´s easy to go back to a proper recovery. But not this time. Tried hundred times, but flashing with fastboot always ended up by "OKAY" but the old recovery remained in place for some reason unknown to me. And also the system wouldn´t boot. Out of desperation I ran "fastboot erase recovery", that wouldn´t help either. In the end I got out of the situation by booting (not flashing) to a proper recovery (fastboot boot recovery recovery.img) and restoring system from a nandroid backup. All seemed fine. ROM booted OK and then I realised I have no service and IMEI: unknown.
The only reason for that was obviously this unfortunate move: fastboot erase recovery. Anything else I did was pretty much "normal".
Here comes the second part of the story.
I downloaded my cloud-stored pds.img backup (lucky me I have it I thought to myself) but that didn´t prove to be of any use.
When running
Code:
adb shell
su
dd if=/sdcard/pds.img of=/dev/block/platform/msm_sdcc.1/by-name/pds
as seen on
http://forum.xda-developers.com/showthread.php?t=2537119
nothing happend. Dd ran too fast, just a fraction of a second and after reboot still IMEI: unknown.
To cut the long story short, after hours of searching for a possible solution (and thinking what would be my next phone) I finally came across this post:
http://forum.xda-developers.com/showpost.php?p=45881991&postcount=86
and tried that very easy method and it worked!
Takeaway messsages:
1. don´t use fastboot erase "all" or "recovery" (other partitions may be erased without problems)
2. pds partition backup and restore method didn´t work for me
3. working solution (at least for me):
Remove sim, flash stock firmware using standard methods, boot to home screen, power off, insert sim, reboot and you´re IMEI should be back!
Click to expand...
Click to collapse
Is it possible?
Probably your pds partition was never corrupted! IMEI was there the whole time and ROM had some problems?
deej_roamer said:
Is it possible?
Probably your pds partition was never corrupted! IMEI was there the whole time and ROM had some problems?
Click to expand...
Click to collapse
Well, we don´t know what is happening exactly but we do know that a couple of people including me ran into problems after running fastboot erase all or fastboot erase recovery. I ´m describing here a method that could help the other guys or somebody else in the future.
drfr said:
Well, we don´t know what is happening exactly but we do know that a couple of people including me ran into problems after running fastboot erase all or fastboot erase recovery. I ´m describing here a method that could help the other guys or somebody else in the future.
Click to expand...
Click to collapse
Oh I am not criticising your work, I encourage it! I just pointed my point of view!
Added to FAQ (in the lost IMEI section), i also think that contrary to an erase all, the IMEI was not exactly lost but not readable by system (file system issue? misread cluster reading frame ? no idea) and that would explain the recover fail in the first place.
this is cool you could recover it by flashing stock, so i added your story to FAQ in case it happens again to anyone
Good to know.
matmutant said:
... i also think that contrary to an erase all, the IMEI was not exactly lost but not readable by system (file system issue? misread cluster reading frame ? no idea) and that would explain the recover fail in the first place.
Click to expand...
Click to collapse
Just adding some more information after searching through old threads.
I can see there were some little differences between my situation (loosing IMEI after fastboot erase recovery) and the situation of those guys who ran fastboot erase all.
In my case, I was getting IMEI unknown, they were getting IMEI 0. My baseband was also unknown, but their showed some number, but a wrong one.
There was one thing which we had in common though. We were able to see our correct IMEIs through fastboot getvar all, but not inside the ROM.
So Mat, you are obviously right in supposing that the IMEI was still stored SOMEWHERE only the system couldn´t read it, but not only in my case.
Hopefully the other guys will be able to find this thread and try my method.
drfr said:
Just adding some more information after searching through old threads.
I can see there were some little differences between my situation (loosing IMEI after fastboot erase recovery) and the situation of those guys who ran fastboot erase all.
In my case, I was getting IMEI unknown, they were getting IMEI 0. My baseband was also unknown, but their showed some number, but a wrong one.
There was one thing which we had in common though. We were able to see our correct IMEIs through fastboot getvar all, but not inside the ROM.
So Mat, you are obviously right in supposing that the IMEI was still stored SOMEWHERE only the system couldn´t read it, but not only in my case.
Hopefully the other guys will be able to find this thread and try my method.
Click to expand...
Click to collapse
Gonna try this if I can find some time, even if I don't realy got any hope left after flashing the hell out of this phone..
Didn't work. I used erase all back in the days..
RestlessScreams said:
Didn't work. I used erase all back in the days..
Click to expand...
Click to collapse
Same here, tried with 4.3 and 4.4 german (my phone is)
used erase all back in the days still can see imei on fastboot getvar, imei 0 on mobile.
Sorry guys, I don´t know of any other method yet, but if you can see IMEI through fastboot getvar there SHOULD be a chance.
What about this?
http://forum.xda-developers.com/showthread.php?t=1827089
drfr said:
Sorry guys, I don´t know of any other method yet, but if you can see IMEI through fastboot getvar there SHOULD be a chance.
What about this?
http://forum.xda-developers.com/showthread.php?t=1827089
Click to expand...
Click to collapse
thanks mate for your effort!
Sadly fastboot oem writeimei is unsupported in moto g
---------- Post added at 11:26 AM ---------- Previous post was at 11:12 AM ----------
drfr said:
Sorry guys, I don´t know of any other method yet, but if you can see IMEI through fastboot getvar there SHOULD be a chance.
What about this?
http://forum.xda-developers.com/showthread.php?t=1827089
Click to expand...
Click to collapse
about where is SHOULD be, when u do fastboot erase all it deletes those:
modemst1
modemst2
hob
dhob
fsg
fsc
clogo
I have the same problem here... do the comannd of the hell... erase all . IMEI is "0" if anyone solved that share please u.u
Lost IMEI
japoina92 said:
I have the same problem here... do the comannd of the hell... erase all . IMEI is "0" if anyone solved that share please u.u
Click to expand...
Click to collapse
The same situation... Can somebody share the pds folder? I assume that it contains imei.
ol_st said:
The same situation... Can somebody share the pds folder? I assume that it contains imei.
Click to expand...
Click to collapse
i've tried edit the pds.img file from other Moto G XT1032, edit with hex workshop, find the line for imei number and edit with my imei ( back in battery ) flash the pds.img with flashable zip in respective partition and no good news... the imei remain in IMEI = 0 :S
recover imei moto g
japoina92 said:
i've tried edit the pds.img file from other Moto G XT1032, edit with hex workshop, find the line for imei number and edit with my imei ( back in battery ) flash the pds.img with flashable zip in respective partition and no good news... the imei remain in IMEI = 0 :S
Click to expand...
Click to collapse
Hi friend, how did you get flash pds.img into a .zip file, please guide me about the way, thanks in advance
BUMP: any news on this guys?
Nothing..
killerBRs said:
Nothing..
Click to expand...
Click to collapse
japoina92 said:
i've tried edit the pds.img file from other Moto G XT1032, edit with hex workshop, find the line for imei number and edit with my imei ( back in battery ) flash the pds.img with flashable zip in respective partition and no good news... the imei remain in IMEI = 0 :S
Click to expand...
Click to collapse
Younboy69 said:
Hi friend, how did you get flash pds.img into a .zip file, please guide me about the way, thanks in advance
Click to expand...
Click to collapse
tehygav said:
BUMP: any news on this guys?
Click to expand...
Click to collapse
What if we try @japoina92 method, having a new pds.img and restoring it via adb?
@japoina92 can you explain me how to use the hex workshop?
moto
sebastiandg7 said:
What if we try @japoina92 method, having a new pds.img and restoring it via adb?
@japoina92 can you explain me how to use the hex workshop?
Click to expand...
Click to collapse
tengo un moto g hay alguna forma de restaurar imei alguna box que se dedique al cambio de imei?
So the usual things has happened.. I have looked many different places, forums, and posts and the closest thing I have found was this thread.
http://forum.xda-developers.com/showthread.php?t=2423716
However it didnt help me at all so now I am posting this to see if there is an angel out there that can help me.
He is the problem.
1. It will show this if I plug it in to my PC but I cant turn on the device by its self.
"AP Fastboot Flash Mode (S)
10.9B(*) (sha-1e9f557, 2013-09-25 16:26:59)
eMMC Info: Size 16GB
Device is LOCKED. Status Code: 0
Battery Low
Transfer Mode:
USB Connected
Fastboot Reason: Flash Failure"
2. It doesnt charge.. I dont think
3. When I hold the Vol- and PWR for 10 ten then add the Vol+ it sometimes will go to the bootloader and then it will boot.
Can I fix this to not show this message every time?
Thanks for your time
-Avethepizzaman
You'll need to get it charged first, before you do anything.
Sent from my HTC6525LVW using Tapatalk
RikRong said:
You'll need to get it charged first, before you do anything.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
K I have it charged..
Avethepizzaman said:
K I have it charged..
Click to expand...
Click to collapse
per my post in the thread you quoted,
did you download your firmware version and flash one of the files with fastboot?
any flash normally fixed this error.
bweN diorD said:
per my post in the thread you quoted,
did you download your firmware version and flash one of the files with fastboot?
any flash normally fixed this error.
Click to expand...
Click to collapse
I think so. I tried to flash this firmware using RSD Lite v6.16..
VZW_XT907_4.4.2-KDA20.62-10.1_CFC_1FF.xml
But when i go to fastboot and start to flash that firmware it gives me two errors the first one is on the phone stating.
Also does the fact the my phone in running on 4.4.2 verison 182.46.15 matter at all?
"downgraded security version
update gpt_main version failed
preflash validation failed for GPT"
and the second one is RSD starting
"Failed flashing process. 3/21 flash partition "gpt.bin" -> Phone returned FAIL."
Then I simply hold all three of my buttons on the phone and boot normally and it works.. I just need to get rid of that message.
Thanks for helping
Avethepizzaman said:
I think so. I tried to flash this firmware using RSD Lite v6.16..
VZW_XT907_4.4.2-KDA20.62-10.1_CFC_1FF.xml
But when i go to fastboot and start to flash that firmware it gives me two errors the first one is on the phone stating.
Also does the fact the my phone in running on 4.4.2 verison 182.46.15 matter at all?
"downgraded security version
update gpt_main version failed
preflash validation failed for GPT"
and the second one is RSD starting
"Failed flashing process. 3/21 flash partition "gpt.bin" -> Phone returned FAIL."
Then I simply hold all three of my buttons on the phone and boot normally and it works.. I just need to get rid of that message.
Thanks for helping
Click to expand...
Click to collapse
edit the xml file in the firmware and completely remove the line containing "gpt".
im assuming you already removed the "getvar" line because it didnt throw an error, if you didnt remove those too.
you can also remove the "erase userdata" line so it wont wipe all your data off.
after editing, save and run rsd again.
fyi, fastboot is not the same as rsd, but rsd should solve the problem just the same.
bweN diorD said:
edit the xml file in the firmware and completely remove the line containing "gpt".
im assuming you already removed the "getvar" line because it didnt throw an error, if you didnt remove those too.
you can also remove the "erase userdata" line so it wont wipe all your data off.
after editing, save and run rsd again.
fyi, fastboot is not the same as rsd, but rsd should solve the problem just the same.
Click to expand...
Click to collapse
Before I do this I have been reading that if I got the 182.46.15 update that I got on the 9/9 then im strewed and I can do anything.. should I still try what you said? Ha im a noob and kinda scared so I dont want to mess things up!
Avethepizzaman said:
Before I do this I have been reading that if I got the 182.46.15 update that I got on the 9/9 then im strewed and I can do anything.. should I still try what you said? Ha im a noob and kinda scared so I dont want to mess things up!
Click to expand...
Click to collapse
im about to go to bed, but we need to backup a bit.
did i miss where you said you have a xt907?
i just noticed thats the firmware you are trying to flash, but this is a xt925/926 forum.
i can still help you, either way, but you should try to post in the correct forum in the future to avoid confusion and flashing something wrong.
if your phone is locked, you will need the most recent firmware. then you can make the adjustments i suggested and it will work fine.
worst that would have happened by flashing the correct, but older version, is soft brick. annoying but totally fixable.
flashing the wrong phones software is generally not fixable though.
bweN diorD said:
im about to go to bed, but we need to backup a bit.
did i miss where you said you have a xt907?
i just noticed thats the firmware you are trying to flash, but this is a xt925/926 forum.
i can still help you, either way, but you should try to post in the correct forum in the future to avoid confusion and flashing something wrong.
if your phone is locked, you will need the most recent firmware. then you can make the adjustments i suggested and it will work fine.
worst that would have happened by flashing the correct, but older version, is soft brick. annoying but totally fixable.
flashing the wrong phones software is generally not fixable though.
Click to expand...
Click to collapse
Again I want to thank you for your help because its really.. helpful? Ha.
Anyway things are making sense now. I know I have the xt926 and its running 182.46.15 and its 4.4.2. So instead of flashing the wrong phone I flashed this firmware
VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml
which it the firmware for 182.46.10. I then did what you told me to do earlier on getting rid of the line containing "gpt" and the line "getvar". Now im getting new errors starting.
On RSD:
"6/19 flash tz "tz.mbn"
On PHONE:
"downgraded security version
update tz version failed
preflash validation failed for tz"
So yea... New problems.
Thanks Avethepizzaman
Avethepizzaman said:
Again I want to thank you for your help because its really.. helpful? Ha.
Anyway things are making sense now. I know I have the xt926 and its running 182.46.15 and its 4.4.2. So instead of flashing the wrong phone I flashed this firmware
VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml
which it the firmware for 182.46.10. I then did what you told me to do earlier on getting rid of the line containing "gpt" and the line "getvar". Now im getting new errors starting.
On RSD:
"6/19 flash tz "tz.mbn"
On PHONE:
"downgraded security version
update tz version failed
preflash validation failed for tz"
So yea... New problems.
Thanks Avethepizzaman
Click to expand...
Click to collapse
That's a lower version. Unless you unlocked your bootloader, which it appears you haven't, you cannot downgrade from 182.46.15. If you didn't unlock your bootloader (which I'm assuming because in your first post, you showed that the status said "locked" in fastboot mode), then you have no way to root, unlock the bootloader nor downgrade. You can only reflash the latest which is 182.46.15.
Avethepizzaman said:
Again I want to thank you for your help because its really.. helpful? Ha.
Anyway things are making sense now. I know I have the xt926 and its running 182.46.15 and its 4.4.2. So instead of flashing the wrong phone I flashed this firmware
VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml
which it the firmware for 182.46.10. I then did what you told me to do earlier on getting rid of the line containing "gpt" and the line "getvar". Now im getting new errors starting.
On RSD:
"6/19 flash tz "tz.mbn"
On PHONE:
"downgraded security version
update tz version failed
preflash validation failed for tz"
So yea... New problems.
Thanks Avethepizzaman
Click to expand...
Click to collapse
ok, i was tired and forgot about the "tz".
to avoid any further confusion, download the firmware from here and replace the xml file with this one. i already edited it. then flash again.
now that we have all the facts straight, and files in line, it should go fine this time.
Wow! thank you for making it super easy for me! Alrightly so everything flashed perfectly and it passed this time! I understand that since the new update 182.46.15 with a locked bootloader that I cannot root or unlock the bootloader. However every time I boot my phone up, it still keeps giving my warnings in the bootloader. After doing the flash I have a new bootloader failure that gives the error of.
"Fastboot Reason: Sticky bit flash_failure."
So I guess my new goal is to get rid of these bootloader errors.. Is this even possible? Thanks Again!
Avethepizzaman said:
Wow! thank you for making it super easy for me! Alrightly so everything flashed perfectly and it passed this time! I understand that since the new update 182.46.15 with a locked bootloader that I cannot root or unlock the bootloader. However every time I boot my phone up, it still keeps giving my warnings in the bootloader. After doing the flash I have a new bootloader failure that gives the error of.
"Fastboot Reason: Sticky bit flash_failure."
So I guess my new goal is to get rid of these bootloader errors.. Is this even possible? Thanks Again!
Click to expand...
Click to collapse
wow, your phone is being a pita lol
follow the instructions here to fix that.
Everything worked! I am back to normal! Thank you for everything because there was a lot of stuff that I didnt even know about! Thank you for making XDA awesome!
Avethepizzaman said:
Everything worked! I am back to normal! Thank you for everything because there was a lot of stuff that I didnt even know about! Thank you for making XDA awesome!
Click to expand...
Click to collapse
np! happy to help
Hello,
so... yep, I did "fastboot erase all" :cyclops:.
But if I boot into bootloader I can still get my imei with "fastboot getvar imei", though the rom doesn't recognize it. Nope, not even that anymore.
Is it just corrupted or something? Can I still "unbrick" my phone?
(I'll try to flash the stock firmware, but it'll take a while to download) did not work so far.
Stuff I tried:
-Flashing stock firmware
-Edit #550(IMEI) with QPST
Thanks in advance!
Ralmo said:
Hello,
so... yep, I did "fastboot erase all" :cyclops:.
But if I boot into bootloader I can still get my imei with "fastboot getvar imei", though the rom doesn't recognize it. Nope, not even that anymore.
Is it just corrupted or something? Can I still "unbrick" my phone?
(I'll try to flash the stock firmware, but it'll take a while to download) did not work so far.
Thanks in advance!
Click to expand...
Click to collapse
If your imei displayed in fastboot mode then you might have a chance to reflash pure stock including recovery and reflash the bootloader. If that doesn't work I am sorry my friend, at this point in time it cannot be recovered.
skyguy126 said:
If your imei displayed in fastboot mode then you might have a chance to reflash pure stock including recovery and reflash the bootloader. If that doesn't work I am sorry my friend, at this point in time it cannot be recovered.
Click to expand...
Click to collapse
It was displayed... then i flashed stock firmware and did other stuff (didn't get it to work). Now it is not displayed in fastboot. I do get a signal occasionally, so that's "good" i guess.
I'll buy a new one and use this one for testing and might try to fix it when somebody has come up with something. It's not that expensive afterall and I was actually planning on buying a 2. Gen or a 2014 version :3
Ralmo said:
It was displayed... then i flashed stock firmware and did other stuff (didn't get it to work). Now it is not displayed in fastboot. I do get a signal occasionally, so that's "good" i guess.
I'll buy a new one and use this one for testing and might try to fix it when somebody has come up with something. It's not that expensive afterall and I was actually planning on buying a 2. Gen or a 2014 version :3
Click to expand...
Click to collapse
If you are going to use the old one for testing would you mind giving this a try: http://forum.xda-developers.com/showthread.php?p=57054884
[MOD][SCRIPT] Get More Storage by Reloacting Dalvik Cache!
sure
skyguy126 said:
If you are going to use the old one for testing would you mind giving this a try: http://forum.xda-developers.com/showthread.php?p=57054884
[MOD][SCRIPT] Get More Storage by Reloacting Dalvik Cache!
Click to expand...
Click to collapse
Sure, why not? Well, I'll try it in a few days since I'm quite busy (school/work).
Ralmo said:
Sure, why not? Well, I'll try it in a few days since I'm quite busy (school/work).
Click to expand...
Click to collapse
Thanks!
I don't have a computer here in front of me, but if I remember correctly it should be possible to restore/set your IMEI using CDMA workshop if you are able to get your MSL
elrod16 said:
I don't have a computer here in front of me, but if I remember correctly it should be possible to restore/set your IMEI using CDMA workshop if you are able to get your MSL
Click to expand...
Click to collapse
I already ordered a 2. Gen Moto, but I could return it. Would be nice if you could show me how to do that (I already tried a bit with qpst, but it didn't work and i lost my motivation ^^). Link maybe?
The problem is that I can't really mess with my phone, I need it and I'd rather know how to fix it than try for hours and hours and not be able to use it :/ That's why I just gave up
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