Database Info

[Q] Nexus S 4G won't boot past Google Screen!!

I tried rooting my phone, but when I flashed CWM my Nexus S stopped booting... it freezes on the Google screen in the intro. I can boot into Fastboot, and cwm, but I cant connect the Internal memory to the computer without it booting like it is supposed to. Does anybody know of anything I can do to fix my phone and bring it back to stock??

There are guides for returning to stock stickied in the Nexus S 4G Android Development forum.
Before you do that though, try flashing a different recovery, like the one linked to here or here.
Btw, which guide did you use? You're not the first person to have this problem, and it's really bugging me (though probably not as much as it's bugging you :-o).

Maximilian Mary: I tried to post the link, but since I'm a new member I have to wait 8 posts before I can post a URL.... :/
I will try a different recovery, but how would I flash a rom if I can connect my phone via usb mount?

deadzunehd said:
Maximilian Mary: I tried to post the link, but since I'm a new member I have to wait 8 posts before I can post a URL.... :/
Click to expand...
Click to collapse
What's the title of the thread?
.
I will try a different recovery, but how would I flash a rom if I can connect my phone via usb mount?
Click to expand...
Click to collapse
I'm a little out of my depth here, but I think it's
fastboot flash system system.img.
You don't need to put the rom image on the sdcard. Just put it in the same folder as fastboot.

It was titled "How to Root Nexus S!"
And I will try to flash recovery and try that rom command, thank you )

deadzunehd said:
It was titled "How to Root Nexus S!"
And I will try to flash recovery and try that rom command, thank you )
Click to expand...
Click to collapse
Hmmm. I can't find that exact title. Could you pm me the link?

deadzunehd said:
thank you )
Click to expand...
Click to collapse
There's a button for that.

I got the link. Thanks. I looks like you flashed a boot image that is incompatible with your phone. That guide was for the T-Mobile Nexus S. (Why they're screwing with the boot.img to begin with, I really don't understand.)
Download the attached file, and unzip it to the same folder as fastboot. The md5 sum is d4a9508f9321eb25df3383f00f571e8b. Then
Code:
fastboot flash boot boot.img
You'll probably also want to use one of the recoveries listed above to
Code:
fastboot flash recovery recovery.img
, but leave system alone for now. Flash that only as a last resort.

deadzunehd said:
I tried rooting my phone, but when I flashed CWM my Nexus S stopped booting... it freezes on the Google screen in the intro. I can boot into Fastboot, and cwm, but I cant connect the Internal memory to the computer without it booting like it is supposed to. Does anybody know of anything I can do to fix my phone and bring it back to stock??
Click to expand...
Click to collapse
I had this problem after flashing the wrong ROM onto my phone. I got the phone back to stock using ODIN.
My thread can be found here
http://forum.xda-developers.com/showthread.php?p=14172335#post14172335
hope it helps

Acnescar said:
I had this problem after flashing the wrong ROM onto my phone. I got the phone back to stock using ODIN.
My thread can be found here
http://forum.xda-developers.com/showthread.php?p=14172335#post14172335
hope it helps
Click to expand...
Click to collapse
OMG!! im having the same issue. could you please post the link for ODIN so i can return to stock and take it from there please? I rely on my phone so much and i need it asap thank you.

same problem with me.
but in my case, the phone not only freeze after the google logo before boot. I tried several times to pull the battery and start the phone again, it took several times until the phone can boot normally again.
After that, my nexus s can work as usual. but it only takes 3-4 hour until it freeze/hangs or reboot automatically and show image of green robot lay down with red alert triangle...
sometimes I noticed all application force closed like gmail, gtalk, etc. (its a basic apps instead of 3rd party app)
History :
- root GB 2.37 using superoneclick
- upgrade OTA to ICS 4.04
- problem happens
- root using guide : nexusshacks.com
- unroot using guide : nexusshacks.com
- back to factory setting on GB 2.34
- upgrade OTA to ICS 4.04
- Still got that problem.....
I'm using Nexus S 4G Sprint, pls help me guys...

nexus s won't boot
I had the same problem and read elsewhere that heating the phone with a hairdryer solves the problem.
I must say, indeed it did.
I removed the battery and the SIM card, then heated up the phone (so it really feels warm) put back the battery and sim and simsalebim the phone started again. and is still working since (now already a few day's)
It seems that a component in the phone is heat sensitive, the question in my mind is when will this show again and do I need to consider buying a new phone.
But sofar it works
PS I also tried hard reset factory reset the lot, but in the end only heating up helped.
Good luck, David

I fixed this problem! but I had to wipe all user data by rooting it using nexusrootICS. It finally boots up and the phone works now... that's all I need.

[Q] Checking before Upgrading

I was checking to see if everything is working ok with fastboot before upgrading to 4.4.4, I need to confirm with XDA whether everything is ok. I open a command prompt in my platform tools folder and I type in adb devices and it shows my Nexus 5. When I type in Fastboot it does nothing. If I type in fastboot fastboot devices it says "waiting for device." When I boot into the bootloader and type in the command, it shows the device serial. Am I ok to proceed first of all?
Second, I thought you could run fastboot devices inside the command prompt while the Nexus is not in the recovery? Is this incorrect?

Matthewlawson3 said:
I was checking to see if everything is working ok with fastboot before upgrading to 4.4.4, I need to confirm with XDA whether everything is ok. I open a command prompt in my platform tools folder and I type in adb devices and it shows my Nexus 5. When I type in Fastboot it does nothing. If I type in fastboot fastboot devices it says "waiting for device." When I boot into the bootloader and type in the command, it shows the device serial. Am I ok to proceed first of all?
Second, I thought you could run fastboot devices inside the command prompt while the Nexus is not in the recovery? Is this incorrect?
Click to expand...
Click to collapse
adb and fastboot are 2 completely different things, you cant fastboot in adb. fastboot is used ONLY while in the bootloader.

So if I'm seeing the serial when I type "abd devices" in devices and when I type "fastboot devices" in recovery, I should be fine?

Matthewlawson3 said:
So if I'm seeing the serial when I type "abd devices" in devices and when I type "fastboot devices" in recovery, I should be fine?
Click to expand...
Click to collapse
fastboot doesnt work in recovery.

Sorry I meant fastboot devices in the fastboot mode in the bootloader. I should be ok?

Matthewlawson3 said:
Sorry I meant fastboot devices in the fastboot mode in the bootloader. I should be ok?
Click to expand...
Click to collapse
yup

So here is my approach to upgrading to 4.4.4. I did this 4.4.3 and it worked fine for me without me losing data. I am going to extract from the factory .TGZ image.
1. Extract the radio image to platform-tools folder
2. Rename the radio image to radio.img
3. Move the boot.img and system.img to platform-tools folder
4. Open Command Prompt inside platform-tools folder
5.Put phone in fastboot mode
6 Connect phone via USB
7. Type command fastboot flash radio radio.img and press enter
8 Type command fastboot flash boot boot.img and press enter
9. Type command fastboot flash system system.img and press enter.
10. Reboot
Does this sound like an ok process for me to upgrade without losing data?

Matthewlawson3 said:
So here is my approach to upgrading to 4.4.4. I did this 4.4.3 and it worked fine for me without me losing data. I am going to extract from the factory .TGZ image.
1. Extract the radio image to platform-tools folder
2. Rename the radio image to radio.img
3. Move the boot.img and system.img to platform-tools folder
4. Open Command Prompt inside platform-tools folder
5.Put phone in fastboot mode
6 Connect phone via USB
7. Type command fastboot flash radio radio.img and press enter
8 Type command fastboot flash boot boot.img and press enter
9. Type command fastboot flash system system.img and press enter.
10. Reboot
Does this sound like an ok process for me to upgrade without losing data?
Click to expand...
Click to collapse
sure, should be fine. but im a bit lazier when it comes to these things. im assuming that you are running a stock rooted rom? all i would do, personally, would be to find a stock rooted rom in the n4 android development section, and dirty flash it over what i have, dirty meaning no wiping a thing. that way you upgrade and dont lose anything. i actually did that. i was running rastakat(a aosp rom) and dirty flashed stock 443 over it. later on, when it was ready, i dirty flashed rastakat 443 over stock(then 444). rastakat and stock are similar, so i had no issues dirty flashing

simms22 said:
sure, should be fine. but im a bit lazier when it comes to these things. im assuming that you are running a stock rooted rom? all i would do, personally, would be to find a stock rooted rom in the n4 android development section, and dirty flash it over what i have, dirty meaning no wiping a thing. that way you upgrade and dont lose anything. i actually did that. i was running rastakat(a aosp rom) and dirty flashed stock 443 over it. later on, when it was ready, i dirty flashed rastakat 443 over stock(then 444). rastakat and stock are similar, so i had no issues dirty flashing
Click to expand...
Click to collapse
n4 ROMs eh?
Just teasing. ??

KJ said:
n4 ROMs eh?
Just teasing. ??
Click to expand...
Click to collapse
n5 as well. except i skipped the stock step, as i was waiting to start development on the trinity 443/444 kernel(im part of trinity kernel). when we were ready to start development of it, rastakat updated the rom. so it was just a dirty custom rom flash over the same rom

I've never tried Trinity....its a performance leaning kernel right? I've seen your impressive benchmarks. Lol
Its the only one I'm ascared to try....cause I'm a mega battery life buff.

KJ said:
I've never tried Trinity....its a performance leaning kernel right? I've seen your impressive benchmarks. Lol
Its the only one I'm ascared to try....cause I'm a mega battery life buff.
Click to expand...
Click to collapse
its actually a pro user experience kernel, just happens that performance is part of it

simms22 said:
its actually a pro user experience kernel, just happens that performance is part of it
Click to expand...
Click to collapse
I'm not a pro. Lol
---------- Post added at 08:06 PM ---------- Previous post was at 08:05 PM ----------
4 cores running. If I can't get 24 plus hours and 6 hours SoT....on out. Lol
Obviously a great choice for gamers and heavy multi taskers. ?
---------- Post added at 08:07 PM ---------- Previous post was at 08:06 PM ----------
Sorry for the off topic BTW. Lol. ?

KJ said:
I'm not a pro. Lol
---------- Post added at 08:06 PM ---------- Previous post was at 08:05 PM ----------
4 cores running. If I can't get 24 plus hours and 6 hours SoT....on out. Lol
Obviously a great choice for gamers and heavy multi taskers. ?
Click to expand...
Click to collapse
pro as meaning for
i get 4.5-5.5 hours sot at 2265mhz/300mhz, and dont do anything to get better battery. granted, my signal quality here in nyc is exceptional(which plays a role in battery life). the using all 4 cores constantly is deceptive. really, the only difference is whether it hotplugs or not. normally it does, trinity doesnt. when hotplugging, the cores are constantly being turned off and on, constantly. trinity doesnt waste the time turning them on and off constantly. this saving time is also saving little bits of battery. everything else works the same, itll only use 2 cores if it wants to, like normally. it just wont turn off the other 2. this also has a side affect of added snappiness

simms22 said:
pro as meaning for
i get 4.5-5.5 hours sot at 2265mhz/300mhz, and dont do anything to get better battery. granted, my signal quality here in nyc is exceptional(which plays a role in battery life). the using all 4 cores constantly is deceptive. really, the only difference is whether it hotplugs or not. normally it does, trinity doesnt. when hotplugging, the cores are constantly being turned off and on, constantly. trinity doesnt waste the time turning them on and off constantly. this saving time is also saving little bits of battery. everything else works the same, itll only use 2 cores if it wants to, like normally. it just wont turn off the other 2. this also has a side affect of added snappiness
Click to expand...
Click to collapse
Well, I always say I'll get similar fantastic battery times on any rom or kernel out there. (When I hear "what's the best rom or kernel for battery" I cringe....Lol)
I'll give trinity a whack and see how it goes. Like I said, I've never tried it. And I like to try everything!
I'll give it a good few days, see how it feels.
Thanks my friend! ?

KJ said:
Well, I always say I'll get similar fantastic battery times on any rom or kernel out there. (When I hear "what's the best rom or kernel for battery" I cringe....Lol)
I'll give trinity a whack and see how it goes. Like I said, I've never tried it. And I like to try everything!
I'll give it a good few days, see how it feels.
Thanks my friend! ?
Click to expand...
Click to collapse
omg, me too. i get the exact same battery life on every kernel ive tried. and i tell people all the time, kernels make little difference, unless its a terribly coded kernel. but, as you know most of the average users dont know, and are on the constant search for the magic pill. i admit, once a bit back, i was one on the search as well(but learned). but it doesnt exist. most of the "magic pill" really depends on them themselves or the quality of the data/phone connection around them.
and on another part, i dont push trinity kernel onto people. i used to, not anymore. because it doesn't matter. people should always use whats they enjoy most and what their phones like best. thats whats important. trinity(like rastakat) is made for us and our friends to enjoy. just happens that we enjoy sharing it as well. if someone wants to use it, they are more than welcome. if not, that's cool as well

simms22 said:
omg, me too. i get the exact same battery life on every kernel ive tried. and i tell people all the time, kernels make little difference, unless its a terribly coded kernel. but, as you know most of the average users dont know, and are on the constant search for the magic pill. i admit, once a bit back, i was one on the search as well(but learned). but it doesnt exist. most of the "magic pill" really depends on them themselves or the quality of the data/phone connection around them.
and on another part, i dont push trinity kernel onto people. i used to, not anymore. because it doesn't matter. people should always use whats they enjoy most and what their phones like best. thats whats important. trinity(like rastakat) is made for us and our friends to enjoy. just happens that we enjoy sharing it as well. if someone wants to use it, they are more than welcome. if not, that's cool as well
Click to expand...
Click to collapse
Completely agree with first paragraph. Exactly!!
And if you get good battery life on anything, trinity included....then I've had the wrong idea about it. Gonna flash it when I get a chance.

[Q] How to root this device without deleting any data?

Is it possible to root one plus one, without deleting any data and apps from it? I just want root access but don't want any custom rom.

yes, of course..
root doesn't delete any of your data

senaferdy79 said:
yes, of course..
root doesn't delete any of your data
Click to expand...
Click to collapse
Thanks for that. How can I do that?
#newtorooting

senaferdy79 said:
yes, of course..
root doesn't delete any of your data
Click to expand...
Click to collapse
That isn't technically true. In order to get root you must have a custom recovery installed. In order to install a custom recovery you must unlock the bootloader. Unlocking the bootloader wipes the device.
---------- Post added at 08:13 PM ---------- Previous post was at 08:10 PM ----------
sourabhkejriwal said:
Thanks for that. How can I do that?
#newtorooting
Click to expand...
Click to collapse
Sorry you got your hopes up, but the other poster isn't right. As per my reply to him you need to unlock your bootloader first, which is going to wipe your device. I'd suggest backing up any files that you have that are important to you. As for your apps and settings, you'll have to set them up again afterwards. Go to my guide thread here:
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
You need to follow (in order) sections 1, 2, 3, and 4. This will give you root access on your stock ROM. You should also follow section 10, it's very important that you make a backup of your EFS partition.

timmaaa said:
That isn't technically true. In order to get root you must have a custom recovery installed. In order to install a custom recovery you must unlock the bootloader. Unlocking the bootloader wipes the device.[
Click to expand...
Click to collapse
So are you saying all the many how to's that tell you that you can skip installing recover are wrong? Apparently, I don't have enough posts yet to create a link but I've seen posts here on XDA that say other wise and the one I have in front of me at the moment is from ibtimes . com titled "how-root-oneplus-one-install-twrp-recovery-1450708"
Their "Step-7" reads
Step-7: If you want to root the phone without installing TWRP recovery, type the following command
fastboot boot twrp.img
Click to expand...
Click to collapse
I guess the real question being, why would you need a custom recovery?

pdhx said:
So are you saying all the many how to's that tell you that you can skip installing recover are wrong? Apparently, I don't have enough posts yet to create a link but I've seen posts here on XDA that say other wise and the one I have in front of me at the moment is from ibtimes . com titled "how-root-oneplus-one-install-twrp-recovery-1450708"
Their "Step-7" reads
I guess the real question being, why would you need a custom recovery?
Click to expand...
Click to collapse
You're looking at outdated information. They used to be correct, but now they are wrong. This is because you can no longer use the fastboot boot recovery.img command with a locked bootloader. In fact, that functionality was removed quite some time ago.
You need a custom recovery because that's how you flash SuperSU to get root. There's no way around it.
Transmitted via Bacon

The default recovery will only flash cm signed zip, which is another reason for needing a custom recovery. That method you mention at ibtimes meant that it would allow you to, for one boot cycle, do a "live boot" of twrp
Sent From Lollipopified Bacon Goodness!

But how is anything going to be written to the system partition if it is locked ?

timmaaa said:
You're looking at outdated information. They used to be correct, but now they are wrong. This is because you can no longer use the fastboot boot recovery.img command with a locked bootloader. In fact, that functionality was removed quite some time ago.
You need a custom recovery because that's how you flash SuperSU to get root. There's no way around it.
Click to expand...
Click to collapse
Ugh, was afraid of that, you might want to add a comment to that effect to your guide....
Would have been nice to just add a setting to the default recovery to allow you to toggle whether you need a signed zip or not. Sucks that I could root my SGS III (which is far less hacker friendly than the One) without wiping it but I can't do that for the One, all i want is root for the moment. However, after playing around some more I'm getting stick before I even get that far; I can get ADB to find the device but when I adb reboot bootloader I cannot get fastboot to find the device. I've tried multiple drivers, different USB ports. When my One goes into fastboot the screen seems awfully dim, almost like it hasn't completely initialized, is that normal? And if so, any suggestions on why I can get adb to work but not fastboot?

pdhx said:
Ugh, was afraid of that, you might want to add a comment to that effect to your guide....
Would have been nice to just add a setting to the default recovery to allow you to toggle whether you need a signed zip or not. Sucks that I could root my SGS III (which is far less hacker friendly than the One) without wiping it but I can't do that for the One, all i want is root for the moment. However, after playing around some more I'm getting stick before I even get that far; I can get ADB to find the device but when I adb reboot bootloader I cannot get fastboot to find the device. I've tried multiple drivers, different USB ports. When my One goes into fastboot the screen seems awfully dim, almost like it hasn't completely initialized, is that normal? And if so, any suggestions on why I can get adb to work but not fastboot?
Click to expand...
Click to collapse
The one's bootloader is not like a nexus one where you can at least reboot recovery etc, once it boots thats it
what do get when you type fastboot devices ?

bombadier said:
The one's bootloader is not like a nexus one where you can at least reboot recovery etc, once it boots thats it
Click to expand...
Click to collapse
Which seems to be somewhat limiting for such an otherwise developer friendly device?
bombadier said:
what do get when you type fastboot devices ?
Click to expand...
Click to collapse
Nada, nothing, nil. however, "adb devices" works fine... WTF?

pdhx said:
Which seems to be somewhat limiting for such an otherwise developer friendly device?
Nada, nothing, nil. however, "adb devices" works fine... WTF?
Click to expand...
Click to collapse
Point one was just to say there is not anything really you can do in the bootloader, being able to reboot to recovery etc is actually a handy feature
Try a different fastboot.exe ? if you say that adb works perfectly then there has to be something wrong with your fastboot binary
I have attached my one,download and change the name back to .exe and see what happens
Going to need more info in order to help

bombadier said:
Point one was just to say there is not anything really you can do in the bootloader, being able to reboot to recovery etc is actually a handy feature
Try a different fastboot.exe ? if you say that adb works perfectly then there has to be something wrong with your fastboot binary
I have attached my one,download and change the name back to .exe and see what happens
Going to need more info in order to help
Click to expand...
Click to collapse
Fair point about bootloader, what I don't get is why they forced you to have to do the unlock to root? All I started out wanting to do was install Titanium and run a Nandroid or two. Guess if I'm going to have to wipe I guess I may end up installing a Lollipop ROM. However, I still can't get there. The fast boot you supplied gives the same problem. I was running the latest fastboot from the Android SDK and your's appears to be the same (though I haven't done a binary compare). As far as I can tell that leaves the device drivers, the laptop, or the phone itself. I'm running Win 7 SP 1 64 bit and I've tried various drivers including the Samsung the Google generic and they make no difference. Not sure how they would since adb works but I've seen some suggestions that drivers can be finicky in this regard.
What else can I tell you that might help?
Seems since I can get into the recovery that comes with the phone I could maybe get a works around somehow?

pdhx said:
Fair point about bootloader, what I don't get is why they forced you to have to do the unlock to root? All I started out wanting to do was install Titanium and run a Nandroid or two. Guess if I'm going to have to wipe I guess I may end up installing a Lollipop ROM. However, I still can't get there. The fast boot you supplied gives the same problem. I was running the latest fastboot from the Android SDK and your's appears to be the same (though I haven't done a binary compare). As far as I can tell that leaves the device drivers, the laptop, or the phone itself. I'm running Win 7 SP 1 64 bit and I've tried various drivers including the Samsung the Google generic and they make no difference. Not sure how they would since adb works but I've seen some suggestions that drivers can be finicky in this regard.
What else can I tell you that might help?
Seems since I can get into the recovery that comes with the phone I could maybe get a works around somehow?
Click to expand...
Click to collapse
They're "forcing" you to unlock the bootloader in order to root the device because that's the universally accepted standard (unlock bootloader, install custom recovery, flash root). Some devices have super secure bootloaders and that's why you end up needing to use hacks to get those devices rooted, but that isn't the normal way to go about it. Anyway, there's no advantage to leaving the bootloader at all. There's also no disadvantage to unlocking the bootloader at all. You might say that the fact that the device is wiped during the unlocking process is a disadvantage, but that fact is very well documented both here, on the OnePlus forums, and pretty much any other reputable tech site that mentions unlocking the bootloader on this phone. The point to that last sentence? It pays to research a device thoroughly before buying it, or before using it, the wiping of the device is no issue at all if you do it when you receive the phone (prior to using it), like many people have. But in your situation you're just going to have to backup any important media from the phone prior to unlocking.
Anyway, on to your fastboot issue. Exactly which drivers do you have installed on your PC? Do you have any other phone drivers or software installed on the PC? And do you have access to another PC in case the one you're using is the source of the issue?

Got it, 27th try (give or take) is the charm.... Had to use USBdeview and uninstall the Google and the Qualcomm drivers. Reinstalled the Google drivers (after a reboot) and got it to work. Guess I could have figured that out from dev manager by watching what drivers got activated while fastboot was active but nothing ever jumped out at me as an obvious culprit.
Interesting to note that TWRP now automatically prompts you to install SuperSU if you reboot after installing it. Maybe it found the zip but either way, nice touch!
Now to go and decide what ROM to install....
Thanks for your help!

I would suggest temasek unofficial cm12 ROM. Been using it pretty much as a daily driver since version 1.something of the ROM and no problems. At this point it's been almost a month of not having to boot into my cm11s ROM lol. I use it with AK kernel, seems like a good match cuz both devs are working together looks like. Flash AK ukm special edition after flashing his kernel and install synapse from play store if you want to play around with settings of the kernel
Sent From Lollipopified Bacon Goodness!

zenix23456 said:
I have been using AnyRooter for months and it is quite good to root OnePlus phones.
Click to expand...
Click to collapse
Except the Oneplus One.

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

[RECOVERY] TWRP for Samsung Galaxy A41 [SM-A415F] [BINARY 1 & 2]

TWRP Recovery Project for the Samsung Galaxy A41 [Only for Android 11 Devices, will be upgraded soon.]
Team Win Recovery Project or TWRP for short. Its a fully touch driven user interface, completely theme-able & you can change just about every aspect of the look and feel.
Now ported to the SM-A415F.​
I am not responsible for any bricked imei, when flashing TWRP backup the EFS & NVRAM partitions to be safe, do not root until having an actually good working backup, if you signal goes restore your backup, if you didn't have a previous backup I got a fix for you , flash your firmware as always but on the CP slot in Odin Flash Tool get the CP slot from a CUD4 firmware corresponding your CSC code.
Click to expand...
Click to collapse
A mantainer is required for this device, I just revived the project but someone with the device needs to mantain it.
Download - You'll always find the latest release in here: https://github.com/Galaxy-MT6768/android_device_samsung_a41xx/releases​Known Issues / Report Issues - https://github.com/Galaxy-MT6768/android_device_samsung_a31nsxx/issues​Telegram support group - http://t.me/a31nsxx​
How to install​
[Boot Into Download mode by inserting an usb cable while holding both volume buttons]
Flash the latest .tar release from releases.
Hold the recovery combination (Volume Up + Power) while the .tar is flashing via the odin tool.
When booted up into TWRP go Flash and flash this zip, then go to Wipe > Format Data, all your data will be lost.
You can now boot into your system and do whatever you want.
Click to expand...
Click to collapse
​Flashing Disabled vbmeta (To boot a modified system)​
Extract the vbmeta.img.lz4 from the AP slot in your firmware.
Remove it's lz4 compression [for Windows use lz4]:
Code:
sudo apt-get install lz4 -y
lz4 vbmeta.img.lz4
Click to expand...
Click to collapse
Reboot into fastboot from TWRP flash vbmeta using this command line:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
​Sources​
TWRP Source - https://github.com/minimal-manifest-twrp/platform_manifest_twrp_aosp/tree/twrp-11
Device Tree - https://github.com/Galaxy-MT6768/android_device_samsung_a41xx
Note: The device tree should be compatible with SHRP too
Click to expand...
Click to collapse
Special thanks to:​
TeamWin for the Recovery Project.
Akhil1999 for his kernel.
Zillion for re-doing Akhil's lost device tree.
Click to expand...
Click to collapse
Actual TWRP status: Bugfixing; Try at your own risk and only if you know what you're doing.

I have One question: of everything gone wrong. Can i go in download mode and let Odin fix all?

Catoplepas said:
I have One question: of everything gone wrong. Can i go in download mode and let Odin fix all?
Click to expand...
Click to collapse
Yeah, just reflash stock firmware via Odin.
Also I should update this build, the latest isn't actually the latest.

Wait until v1.2.0 gets released

Hi guys, i have a question.
It would be possible to flash a gsi rom in this phone. and if so, how can it be done?
Because when I try to install the rom the phone goes into bootloop

LolUnis said:
Hi guys, i have a question.
It would be possible to flash a gsi rom in this phone. and if so, how can it be done?
Because when I try to install the rom the phone goes into bootloop
Click to expand...
Click to collapse
The process can easily be done via fastboot.
https://source.android.com/docs/setup/build/gsi#flashing-gsis

Zillion said:
The process can easily be done via fastboot.
https://source.android.com/docs/setup/build/gsi#flashing-gsis
Click to expand...
Click to collapse
Doesn't work the phone still goes into bootloop

LolUnis said:
Doesn't work the phone still goes into bootloop
Click to expand...
Click to collapse
Maybe you got the wrong GSI, as far as I know on a31 GSIs work fine.
Join the A31 Telegram group if you can.

Zillion said:
Maybe you got the wrong GSI, as far as I know on a31 GSIs work fine.
Join the A31 Telegram group if you can.
Click to expand...
Click to collapse
Where can I find the link of the Telegram group?

LolUnis said:
Where can I find the link of the Telegram group?
Click to expand...
Click to collapse
It's a public group

Hi everyone. I have this device but I'm facing a problem. After over 2 years of use, it fell on the ground a few days ago, and the screen is all black. I am trying to retrieve the files from it, I have some stuff that I need. The problem is, the device is fingerprint and password locked, so when I connect it to my PC, it doesn't let me see inside the storage until I unlock it. I've trying to place my fingers on the on-screen sensor, but to no avail. I've also tried blindly writing the password but again no success. I am guessing; besides the screen, the touch sensor is also not working. I've found many solutions (various data recovery apps for PC, screen mirroring, ADB commands), but, all require usb debugging enabled, but that is not the case on my A41. My last resort is this, but I need to ask something before I do it.
1. Does flashing it automatically factory reset my phone
2. If not, does this recovery work with volume button controls (because TWRP has a UI unlike CWM which I used like a decade ago) so I can blindly locate the right options?
3. Is it possible to boot without factory reseting?
4. If not, can I just connect my device while in recovery and copy the files from there, before factory reseting it?
I don't want to fix the screen because it's like a hundred euros, and the phone is not worth that much, let alone the screen. I'll be getting a new phone next month and until them I'm using an old phone I have laying around.
Any help is appreciated.

bestnugnification said:
Hi everyone. I have this device but I'm facing a problem. After over 2 years of use, it fell on the ground a few days ago, and the screen is all black. I am trying to retrieve the files from it, I have some stuff that I need. The problem is, the device is fingerprint and password locked, so when I connect it to my PC, it doesn't let me see inside the storage until I unlock it. I've trying to place my fingers on the on-screen sensor, but to no avail. I've also tried blindly writing the password but again no success. I am guessing; besides the screen, the touch sensor is also not working. I've found many solutions (various data recovery apps for PC, screen mirroring, ADB commands), but, all require usb debugging enabled, but that is not the case on my A41. My last resort is this, but I need to ask something before I do it.
1. Does flashing it automatically factory reset my phone
2. If not, does this recovery work with volume button controls (because TWRP has a UI unlike CWM which I used like a decade ago) so I can blindly locate the right options?
3. Is it possible to boot without factory reseting?
4. If not, can I just connect my device while in recovery and copy the files from there, before factory reseting it?
I don't want to fix the screen because it's like a hundred euros, and the phone is not worth that much, let alone the screen. I'll be getting a new phone next month and until them I'm using an old phone I have laying around.
Any help is appreciated.
Click to expand...
Click to collapse
There's nothing you can do, maybe some repair centre could temporally replace the screen just to save the data from it.

Zillion said:
There's nothing you can do, maybe some repair centre could temporally replace the screen just to save the data from it.
Click to expand...
Click to collapse
I guess I'll just repair the screen even if It's not actually worth it. Thanks though.

Hi Guys, is the latest version of this TWRP compatible with Android 12, or it is only working for Android 11? thanks for your kind reply.

abcuky said:
Hi Guys, is the latest version of this TWRP compatible with Android 12, or it is only working for Android 11? thanks for your kind reply.
Click to expand...
Click to collapse
The latest version works on both Android versions