Database Users

[Q] Trying to get back to stock

I rooted as soon as I got my N7 because I wanted to be able to use USB OTG to watch movies during my long flights a few weeks ago. Now I'm using mskip's tool kit to get back to stock (sending it to Asus because of the screen flicker and touchscreen issues).
I tried to download, extract and flash the stock rom and then re-lock the bootloader. After doing this, it wouldn't load. I can get to the bootloader, and managed to unlock it again, but I can't get it to flash the stock rom and thus it won't boot. When I select "Start", it says "booting failed". It also won't let me flash any of the recovery images included in the utility. I'm not exactly well versed in rooting and now I'm stuck.
Please help if you can. Thank you.

If You Have SuperUser Or SuperSU I believe, you could easily unroot it from the settings. As to locking the bootloader, there is a toolkit program and the link is: http://forum.xda-developers.com/showthread.php?t=1766475 With this you could go back to stock if you wish. You could also use a SDK Command prompt thing to lock the bootloader.
EDIT: I forgot you can't boot up. But you could still use the Toolkit program.

Ryan35310 said:
If You Have SuperUser Or SuperSU I believe, you could easily unroot it from the settings. As to locking the bootloader, there is a toolkit program and the link is: http://forum.xda-developers.com/showthread.php?t=1766475 With this you could go back to stock if you wish. You could also use a SDK Command prompt thing to lock the bootloader.
EDIT: I forgot you can't boot up. But you could still use the Toolkit program.
Click to expand...
Click to collapse
I tried that toolkit several times, but it doesn't work. Everytime I try to flash stock+ unroot I get this message:
"md5sum.exe- System Error
The program can't start because libintl3.dll is missing from your computer. Try reinstalling the program to fix this problem."
No idea what that means.

Use wugfreshs toolkit much better. IMO and i don't use toolkits normally but it was a snap. Also for locking the boot loader its fastboot OEM lock.
Sent From My Toro+ via White Tapatalk

ÜBER™ said:
Use wugfreshs toolkit much better. IMO and i don't use toolkits normally but it was a snap. Also for locking the boot loader its fastboot OEM lock.
Sent From My Toro+ via White Tapatalk
Click to expand...
Click to collapse
I was able to get Wugfresh's toolkit working after re-downloading it for the 3rd time and it is able to flash the bootloader but the next lines of text say:
EOCD not found, not zip error..... and then a bunch of nonsensical symbols.

Tried again this morning... still stuck at the same point. Any ideas guys?

Did you install the drivers for it? Did you try using the PDAnet drivers? Can you post a screenshot or picture of the error? Also are you making sure the device is on with USB Debugging enabled? I never got any errors try following this Video.

He can't go to USB Debugging because he can't boot up I think.

Ryan35310 said:
He can't go to USB Debugging because he can't boot up I think.
Click to expand...
Click to collapse
That is correct. I've attached a screenshot of what I was describing earlier. It looks like what I would imagine Transformer language in written form to look like.

Great googly moogly I got it to work! I had to download the stock image directly from Google... again and select the file manually along with inputting the MD5 checksum. So if you're having issues like I was, try this!
Thank you to everyone that tried to troubleshoot my problems and a big Thank You to WugFresh for his toolkit :good:

[Q] Bricked phone, any way to fix it?

I installed deodexed 4.2.2 stock when i was running deodexed 4.2.1 stock. i felt that it was buggy, so i went into cwrecovery and wiped it and i was about to begin reinstalling deodexed 4.2.2 again when i noticed i forgot to put it onto my phone. then i tried to use my phone, and it would be stuck at "unfortunately, system ui has stopped". it never leaves that popup, so i can't enable usb debugging. i can't use recovery mode, because when i do, the android with a triangle caution sign is there, but no options to select from. i can enter fastboot mode, but that's about it.

CM9onmyMoPho said:
I installed deodexed 4.2.2 stock when i was running deodexed 4.2.1 stock. i felt that it was buggy, so i went into cwrecovery and wiped it and i was about to begin reinstalling deodexed 4.2.2 again when i noticed i forgot to put it onto my phone. then i tried to use my phone, and it would be stuck at "unfortunately, system ui has stopped". it never leaves that popup, so i can't enable usb debugging. i can't use recovery mode, because when i do, the android with a triangle caution sign is there, but no options to select from. i can enter fastboot mode, but that's about it.
Click to expand...
Click to collapse
Reflash a factory image in fastboot, flash CWM/TWRP in fastboot, reroot and reflash the dedexed rom. Your phone isn`t even a bit bricked fortunately.

gee2012 said:
Reflash a factory image in fastboot, flash CWM/TWRP in fastboot, reroot and reflash the dedexed rom. Your phone isn`t even a bit bricked fortunately.
Click to expand...
Click to collapse
How can I reflash the factory image? and where can i find instructions? where can i find the link to download the factory image? thanks

CM9onmyMoPho said:
How can I reflash the factory image? and where can i find instructions? where can i find the link to download the factory image? thanks
Click to expand...
Click to collapse
Look in my signature line 2 and 3.

gee2012 said:
Look in my signature line 2 and 3.
Click to expand...
Click to collapse
thanks. will i lose any personal things such as photos?

CM9onmyMoPho said:
thanks. will i lose any personal things such as photos?
Click to expand...
Click to collapse
Everything will be lost. Considering your phone is bricked there is no way to pull the pictures from your device.
Edit: you might not have to flash full stock, just the system.img that will allow you to overwrite the current system and maintain your sdcard.

i do not know if this is the best place to post this considering i am brand new (i hope so) but i have a soft bricked nexus s 4g that i am trying to fix.
it was loaded with the helly bean 4.2.2 custom rom from nexus hacks (sorry no links) after the reboot it went to a black screen.
what ive tried:
odin: flashing a new rom, this resulted in odin not finding the device (usb debugging is not on and i cant turn it on)
fastboot: (i have all the files but i cant seem to get it set up, i type in adb or fastboot (no device recognized)
nexus root toolkit: (wouldnt find the device and found no options to help with usb debugging)
dfs: (couldnt read the device)
plugging in the phone to the computer: it makes the noise that it is plugged in, comes up as f drive but it is greyed out and i cant click on it (says insert disc)
clock work recovery: i did a full data wipe and required wipes cache and delvik or something along those lines: it reboots into the rom and nothing has changed.. my guess is because there is no back up of the original rom and the cfw is trash, it just wipes the bad rom back to factory and that is still a problem.
pda net: wont recognize the device
galaxy nexus toolkit: nothing useful since the usb debugging is not enabled.
ive worked for 6 hours as of last night to figure this out. i have spent most of those hours in forums and delving further into this phone then id imagined (its not mine) so if there is anyone out there that can suggest anything id appreciate it. this has got me stumped and amazed how such easy fix can really be this complicated.. i will thank any and all answers given to me

theblackrose666 said:
i do not know if this is the best place to post this considering i am brand new (i hope so) but i have a soft bricked nexus s 4g that i am trying to fix.
it was loaded with the helly bean 4.2.2 custom rom from nexus hacks (sorry no links) after the reboot it went to a black screen.
what ive tried:
odin: flashing a new rom, this resulted in odin not finding the device (usb debugging is not on and i cant turn it on)
fastboot: (i have all the files but i cant seem to get it set up, i type in adb or fastboot (no device recognized)
nexus root toolkit: (wouldnt find the device and found no options to help with usb debugging)
dfs: (couldnt read the device)
plugging in the phone to the computer: it makes the noise that it is plugged in, comes up as f drive but it is greyed out and i cant click on it (says insert disc)
clock work recovery: i did a full data wipe and required wipes cache and delvik or something along those lines: it reboots into the rom and nothing has changed.. my guess is because there is no back up of the original rom and the cfw is trash, it just wipes the bad rom back to factory and that is still a problem.
pda net: wont recognize the device
galaxy nexus toolkit: nothing useful since the usb debugging is not enabled.
ive worked for 6 hours as of last night to figure this out. i have spent most of those hours in forums and delving further into this phone then id imagined (its not mine) so if there is anyone out there that can suggest anything id appreciate it. this has got me stumped and amazed how such easy fix can really be this complicated.. i will thank any and all answers given to me
Click to expand...
Click to collapse
You need to be in the bootloader for fastboot to work. Reboot to bootloader and try flashing a recovery.img using this command.
fasboot flash recovery recovery.img

It blows my mind when a user gets all this great help and hasn't given any thanks to the helpers.
Sent from my iPad 4

mitchdickson said:
It blows my mind when a user gets all this great help and hasn't given any thanks to the helpers.
Sent from my iPad 4
Click to expand...
Click to collapse
Happens all the time. I'd have 1000 extra thanks if people new how to use the button or were remotely grateful.

estallings15 said:
Happens all the time. I'd have 1000 extra thanks if people new how to use the button or were remotely grateful.
Click to expand...
Click to collapse
i am sorry i was getting sdk tools set up watching an online tut. i am very greatful for your help my problem was that i had not installed java. so if anyone finds that sdk tools is not coming up. install java and it will work like it is supposed to. i will give a thank you just like i have promised. you guys on this site are the best techs hands down
---------- Post added at 05:13 PM ---------- Previous post was at 05:05 PM ----------
is there a thread on here about adb shell and pushing a new rom onto a nexus s 4g? basically the commands?

theblackrose666 said:
i am sorry i was getting sdk tools set up watching an online tut. i am very greatful for your help my problem was that i had not installed java. so if anyone finds that sdk tools is not coming up. install java and it will work like it is supposed to. i will give a thank you just like i have promised. you guys on this site are the best techs hands down
---------- Post added at 05:13 PM ---------- Previous post was at 05:05 PM ----------
is there a thread on here about adb shell and pushing a new rom onto a nexus s 4g? basically the commands?
Click to expand...
Click to collapse
adb push nameofrom.zip /sdcard/
Sent from my Nexus 4 using xda premium

ran sdk tools tried adb shell and nothing it wont read the device. we tried to push the .tar files to the phone using samsung galaxy nexus tool kit. it didnt work so hes going to take it to a repair but i think the device is toast on the account that usb debugging mode is no where in sight. if it does get fixed ill be sure to report how it got fixed. so anyone else who runs into the problem can get this fixed without a 20 dollar repair bill.

heat361 said:
Everything will be lost. Considering your phone is bricked there is no way to pull the pictures from your device.
Edit: you might not have to flash full stock, just the system.img that will allow you to overwrite the current system and maintain your sdcard.
Click to expand...
Click to collapse
will my computer even detect my phone? usb debugging is off and i can't see the phone's storage from my pc.

[Q][Answered] Have I screwed up? (Fastboot not seeing the Tablet)

Okay, I bought a Nexus 10 off someone, and they had already rooted the device. Bootloader is unlocked and whatnot. That's where my problems start. I can not for the life of me get fastboot or adb to see this thing.
Here's my info:
Google Nexus 10 (Samsung)
ClockworkMod Recovery 6.0.4.3
Bootloader Version: MANTALJ12a
Windows 8.1 Pro x64
Full Android SDK
Samsung drivers installed (I rooted my Galaxy Nexus without issue).
USB has a direct connection
Before I decided to format and try to install a stock .zip, I could access the tablet as a media (That's how I got the .zip on the device).
Steps to how I got here:
Flashed Cyanogenmod 10.2 or whatever. Didn't want JB, wanted Lollipop.
Pushed the (what I thought was correct) .zip to /sdcard
Booted into recovery
Formatted /system, /cache, /data, /factory
Reflashed the .zip
Failed. Miserably.
I named the .zip as something simple and just overwrote it. I wouldn't have this issue if it wasn't for that. I know I did a bad there.
But still, nothing I can do will get fastboot/adb to see the device. It makes the sounds that it's connected when I plug it in. I'm using an elevated prompt as well, but it will not pull the device. How do I get myself out of this hole? If I could push a new .zip to somewhere on /sdcard I could at least use the recovery to reflash.

Wrong device ? [emoji14]

Khaon said:
Wrong device ? [emoji14]
Click to expand...
Click to collapse
No, I was going to put it in the general help thread, may be better here since this may not be a simple question (Please prove me wrong).

Some additional things I've tried:
The NExus Root Toolkit. Removing all drivers etc. Still getting to fastboot by PWR+ VOL+ + VOL-.
Still nothing. Should I go to my wife's computer and try it there? I might do that anyways.

gothmog1065 said:
Some additional things I've tried:
The NExus Root Toolkit. Removing all drivers etc. Still getting to fastboot by PWR+ VOL+ + VOL-.
Still nothing. Should I go to my wife's computer and try it there? I might do that anyways.
Click to expand...
Click to collapse
You don't have access to have os then? How did you push your zip if you don't have access to adb?
I have seen people who couldn't get adb and fastboot working on their windows and switching to another computer solved the issues.
Ok, make sure to make a full clean of your drivers. Wug toolkit explain how to. Then install proper samsung driver and this
If it is not a hardware's problem, you should have access to fastboot & adb. You might try on another computer if possible. A clean one would be the best (i.e. never used any droid devices, etc.).
Another workaround would be to use and otg cable and an usb drive with any zip of your liking.
Another one, I had an issue long time ago, similar, I had to flash through odin in downloading mode to fix my problems.
BUT did you really deleted /factory partition? It contains various proprietary files needed for the device to work. Well concerns more devices with imei and stuff to allow 3g connection and co. Might have no incidence tho on your device's behavior.

Khaon said:
You don't have access to have os then? How did you push your zip if you don't have access to adb?
Click to expand...
Click to collapse
Sorry if I wasn't clear on this, I have 100% access to my computer. I have the Android SDK installed, and adb/fastboot commands working in command prompt. They're just not seeing the tablet.
Ok, make sure to make a full clean of your drivers. Wug toolkit explain how to. Then install proper samsung driver and this
Click to expand...
Click to collapse
Yeah, that's one of the steps I did. Followed the Wug toolkit and removed everything. Still not seeing the tablet.
If it is not a hardware's problem, you should have access to fastboot & adb. You might try on another computer if possible. A clean one would be the best (i.e. never used any droid devices, etc.).
Click to expand...
Click to collapse
Yeah, seems to be doing the same on my wife's computer (Win 7 HP, never had my phone/tablet hooked to it). I get adb/fastboot loaded and working in the command prompt, and it registers when I plug in, but neither command will "see" the tablet.
Another workaround would be to use and otg cable and an usb drive with any zip of your liking.
Another one, I had an issue long time ago, similar, I had to flash through odin in downloading mode to fix my problems.
BUT did you really deleted /factory partition? It contains various proprietary files needed for the device to work. Well concerns more devices with imei and stuff to allow 3g connection and co. Might have no incidence tho on your device's behavior.
Click to expand...
Click to collapse
It's a Wifi tablet, no cellular data and IMEI etc.
edit: As a side note, I've been thinking about reformatting my computer, though it'll be a huge pain to get it back to here as I've got to go from 7 - 8.0 - 8.1 on the upgrade paths to get it back here again.

gothmog1065 said:
Sorry if I wasn't clear on this, I have 100% access to my computer. I have the Android SDK installed, and adb/fastboot commands working in command prompt. They're just not seeing the tablet.
Click to expand...
Click to collapse
From my own experience, having similar issue with the windows drivers for adb, but eventually I fixed it. I really doubt you are screwed.
adb version output ? 1.0.32 is latest.
Yeah, that's one of the steps I did. Followed the Wug toolkit and removed everything. Still not seeing the tablet.
Click to expand...
Click to collapse
Installed universal adb drivers? Nothing shows up in the device manager?
Yeah, seems to be doing the same on my wife's computer (Win 7 HP, never had my phone/tablet hooked to it). I get adb/fastboot loaded and working in the command prompt, and it registers when I plug in, but neither command will "see" the tablet.
Click to expand...
Click to collapse
You might try odin.
Usb mtp doesn’t work from recovery?

Khaon said:
From my own experience, having similar issue with the windows drivers for adb, but eventually I fixed it. I really doubt you are screwed.
adb version output ? 1.0.32 is latest.
Installed universal adb drivers? Nothing shows up in the device manager?
?
Click to expand...
Click to collapse
Android Debug Bridge version 1.0.32, yep latest.
I just feel like I'm missing something, maybe something stupid. HOWEVER, I'm now getting my nexus 10 to show up in device manager with a ? on it. Already tried the direct Samsung drivers, the universal drivers in the Wug toolkit.

gothmog1065 said:
Android Debug Bridge version 1.0.32, yep latest.
I just feel like I'm missing something, maybe something stupid. HOWEVER, I'm now getting my nexus 10 to show up in device manager with a ? on it. Already tried the direct Samsung drivers, the universal drivers in the Wug toolkit.
Click to expand...
Click to collapse
Did you deleted all samsung vendor, etc from the usb program, you know what i am talking about?
You can force to install drivers from device maanger, don't remember how, when installing manually, you must do some step , install from floppy or file, get inf files or so, you will get a prompt telling you it might be harmfull and it will force installation. Might be the solution?
The culprit is definitely software-sided.
Does the mount internal storage (mtp) work?

Would this be easier in Linux? I could pop open my Ubuntu VM and do this if it'd be easier?
Beyond that, are you telling me to try and install the drivers from the driver files created by the Samsung vendor .exe?
I have tried to 'mount USB storage' from recovery, but it doesn't seem to do anything. /system /cache /data /factory are all mounted ATM and nothing is showing.

You've already got more advanced advice than I can offer but when I tried to update to 5.0.1 from 4.4.4, I couldn't get my windows computer to see my device. I was trying the adb fastboot but it I couldn't get it to work.
Wug's toolkit got it all straightened out (http://forum.xda-developers.com/showthread.php?t=2015467)[*]. There was an option on his interface that asked whether the device was working properly or not (a!most missed it as a choice). Checked that box and it went through much of the process I had done (installing adb, updating drivers etc). Long story short, it worked.

Where did you see this option? The only thing I see is the Soft Brick/Bootloop option where it will install the factory again. Was it that or somewhere else?
I swear to the Android droid that I tried that before. That seems to be doing what needs to be done, holy crap thanks!
e: I would like to know, however, why fastboot/adp wouldn't work but this would without doing any of the other stuff?

gothmog1065 said:
Where did you see this option? The only thing I see is the Soft Brick/Bootloop option where it will install the factory again. Was it that or somewhere else?
I swear to the Android droid that I tried that before. That seems to be doing what needs to be done, holy crap thanks!
e: I would like to know, however, why fastboot/adp wouldn't work but this would without doing any of the other stuff?
Click to expand...
Click to collapse
You're right. I confused the heading but choosing that option got my computer and my Nexus "talking." After installing the factory image I think you can then push a cusom ROM to you Nexus (http://forums.androidcentral.com/go...acks/264619-wugs-nexus-toolkit-questions.html).

gothmog1065 said:
Where did you see this option? The only thing I see is the Soft Brick/Bootloop option where it will install the factory again. Was it that or somewhere else?
I swear to the Android droid that I tried that before. That seems to be doing what needs to be done, holy crap thanks!
e: I would like to know, however, why fastboot/adp wouldn't work but this would without doing any of the other stuff?
Click to expand...
Click to collapse
Problem solved ? I always had less issues with fastboot and adb on Linux you can install a ppa that install for you adb and fastboot
Hovewer if you are using 2.8.2.0 you will need 1.0.32 and the ppa includes 1.0.31 so only adb sideload fails.
Sent from my nexus 10

Bootloader Unlock issue

EDIT: Well after a few hours of bashing around at it I managed to get the bootloader unlocked. However I am having one wicked time trying to get twrp installed as my recovery, and to S-off my device.
When I got to run : fastboot flash recovery twrp.img I get the error "unable to load twrp.img" Now I know darn good and well it is prob some stupid error on my part, but this is driving me batty and help would be greatly appreciated.
Brad
OK..Maybe I'm dumb...but I'd rather post a question than screw around and brick my phone.
Admittedly it has been a couple years since I had an HTC device. (Just got a Bolt today) Been to HTC Dev unlock to try and unlock my bootloader however I am running into an issue when trying to run oem get_identifier_token. Getting 'fastboot' is not recognized as an internal or external command. operable program or batch file.
Been thru this a couple times before on older HTC Devices (last one was an M8-HK Edition) and not had issues.
I installed everything it said to on the HTC site. But I'm stalled out at step 5 on the HTC Dev site. and can't seem to get any further than that. (and yes phone is in DL mode)
Anyone kind enough to help an old dummy out?

PodCulture said:
EDIT: Well after a few hours of bashing around at it I managed to get the bootloader unlocked. However I am having one wicked time trying to get twrp installed as my recovery, and to S-off my device.
When I got to run : fastboot flash recovery twrp.img I get the error "unable to load twrp.img" Now I know darn good and well it is prob some stupid error on my part, but this is driving me batty and help would be greatly appreciated.
Brad
OK..Maybe I'm dumb...but I'd rather post a question than screw around and brick my phone.
Admittedly it has been a couple years since I had an HTC device. (Just got a Bolt today) Been to HTC Dev unlock to try and unlock my bootloader however I am running into an issue when trying to run oem get_identifier_token. Getting 'fastboot' is not recognized as an internal or external command. operable program or batch file.
Been thru this a couple times before on older HTC Devices (last one was an M8-HK Edition) and not had issues.
I installed everything it said to on the HTC site. But I'm stalled out at step 5 on the HTC Dev site. and can't seem to get any further than that. (and yes phone is in DL mode)
Anyone kind enough to help an old dummy out?
Click to expand...
Click to collapse
1. make sure you're in download mode, not bootloader
2. make sure twrp.img is in your sdktools folder
maybe a bad download of twrp?

The saga continues...
Now Im stuck in this weird loop after S-off getting this screen:
It says "your phone is encrypted" enter your lock screen password. I did and it said correct, but your data is corrupted. You must do a factory reset. I try that process, the phone reboots, comes back up to that same "your phone is encrypted"
PodCulture said:
EDIT: Well after a few hours of bashing around at it I managed to get the bootloader unlocked. However I am having one wicked time trying to get twrp installed as my recovery, and to S-off my device.
When I got to run : fastboot flash recovery twrp.img I get the error "unable to load twrp.img" Now I know darn good and well it is prob some stupid error on my part, but this is driving me batty and help would be greatly appreciated.
Brad
OK..Maybe I'm dumb...but I'd rather post a question than screw around and brick my phone.
Admittedly it has been a couple years since I had an HTC device. (Just got a Bolt today) Been to HTC Dev unlock to try and unlock my bootloader however I am running into an issue when trying to run oem get_identifier_token. Getting 'fastboot' is not recognized as an internal or external command. operable program or batch file.
Been thru this a couple times before on older HTC Devices (last one was an M8-HK Edition) and not had issues.
I installed everything it said to on the HTC site. But I'm stalled out at step 5 on the HTC Dev site. and can't seem to get any further than that. (and yes phone is in DL mode)
Anyone kind enough to help an old dummy out?
Click to expand...
Click to collapse

PodCulture said:
Now Im stuck in this weird loop after S-off getting this screen:
It says "your phone is encrypted" enter your lock screen password. I did and it said correct, but your data is corrupted. You must do a factory reset. I try that process, the phone reboots, comes back up to that same "your phone is encrypted"
Click to expand...
Click to collapse
yes, after s-off u have to format data

OMJ said:
yes, after s-off u have to format data
Click to expand...
Click to collapse
I've no problem doing that, but teh phone isn't letting me do it.

PodCulture said:
I've no problem doing that, but teh phone isn't letting me do it.
Click to expand...
Click to collapse
How are you trying to format data?
Sent from my unknown using XDA Labs

Unlocked needs root and twrp
Honestly...I don't know where I screwed up. (in the various how-to's I read I didn't see a format data step) I took the phone to Sprint and they were kind enough to flash it for me...so I am back up and running. Booted into DL mode and verified that I'm still unlocked and S-off. But where to go from here I don't know. I'd love to flash twrp and SU, but paranoid about semi-bricking it again. I used to know how this crap worked but that was quite awhile ago. (a couple phones and a couple versions of Windows ago)
OMJ said:
How are you trying to format data?
Sent from my unknown using XDA Labs
Click to expand...
Click to collapse

PodCulture said:
Honestly...I don't know where I screwed up. (in the various how-to's I read I didn't see a format data step) I took the phone to Sprint and they were kind enough to flash it for me...so I am back up and running. Booted into DL mode and verified that I'm still unlocked and S-off. But where to go from here I don't know. I'd love to flash twrp and SU, but paranoid about semi-bricking it again. I used to know how this crap worked but that was quite awhile ago. (a couple phones and a couple versions of Windows ago)
Click to expand...
Click to collapse
flashing twrp & SU isn't difficult...since you unlocked bootloader, you should already have the fastboot tools needed.
1. download latest twrp (3.1.1-0 as of now) https://dl.twrp.me/pme/twrp-3.1.1-0-pme.img
2. copy that img to your sdktools/fastboot folder
3. reboot into download mode
4. flash twrp: fastboot flash recovery twrp-3.1.1-0-pme.img
5. reboot to bootloader, then reboot to recovery
6. create a backup if u want
7. flash/install SuperSU https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip

Thanks! Got everything back up and running now. Nice to have a phone I can use the way I want to again. TONS of bloat though.
OMJ said:
flashing twrp & SU isn't difficult...since you unlocked bootloader, you should already have the fastboot tools needed.
1. download latest twrp (3.1.1-0 as of now) https://dl.twrp.me/pme/twrp-3.1.1-0-pme.img
2. copy that img to your sdktools/fastboot folder
3. reboot into download mode
4. flash twrp: fastboot flash recovery twrp-3.1.1-0-pme.img
5. reboot to bootloader, then reboot to recovery
6. create a backup if u want
7. flash/install SuperSU https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip
Click to expand...
Click to collapse

How did u get s off

LG aristo 2 (K8 2018)

Since the majority of the hardware between the devices is gonna be almost exactly the same, I'mma give a shot at rooting it. Picking up tomorrow, so hopefully it goes well

I just got this phone. Let me know how what happens please.

tge101 said:
I just got this phone. Let me know how what happens please.
Click to expand...
Click to collapse
Yeah, I'll keep a heads up. I'm sitting in metro now tryna see what's going on, small argument. Their commercials in Philly don't mention that you need to switch carriers for the rebates.

I'll probably be getting one next week. Says it has 7.1.2 an it weighs less? Cool

attempt
Ok so I tried to root this and everything went well up ubtil I flashed Team win. When i try to open it, the program starts HOWEVER something is up with the touch screen. Im unable to click anything the only power button works. I tried flashing versions 3.0.0, 3.0.1, 3.0.2, 3.0.3. No luck! Is the problem they are old versions? Should i use 3.1.1 which was designed for Nougat supposedly?
Any advice this is my first attempt in to rooting android devices. Forgive me if any of my lingo is incorrect.

tribal1209 said:
Ok so I tried to root this and everything went well up ubtil I flashed Team win. When i try to open it, the program starts HOWEVER something is up with the touch screen. Im unable to click anything the only power button works. I tried flashing versions 3.0.0, 3.0.1, 3.0.2, 3.0.3. No luck! Is the problem they are old versions? Should i use 3.1.1 which was designed for Nougat supposedly?
Any advice this is my first attempt in to rooting android devices. Forgive me if any of my lingo is incorrect.
Click to expand...
Click to collapse
Are you trying to root the aristo or aristo 2?

Aristo 2. Sorry, kind of diving in head first with this whole process. If im doing something obviously wrong go easy on me lol.
---------- Post added at 11:26 PM ---------- Previous post was at 11:25 PM ----------
Aristo 2

Hmm and you flashed the twrp that was for the aristo right?

Well the TWRP files i used were on *How To* forums posts and youtube videos for the original LG Aristo. Everything was going fine but the touch screen while in TWRP does not work. Maybe there os a different version I can try? Do any of you guys have any ideas, my understanding though is that TWRP has to be created for a specific device once released. Is thats whats going wrong?

you unlocked the bootloader and flashed the aristo 1 recovery thats what you did so far right?

The aristo 1 recovery will not work at all.
The screens are of the same build, but different composition.
That's why I wanted to test this myself before posting further on the subject.
I can risk my phone, most of you cant.

I figured as much. Thanks for the info! Just got mine today. Glad the aristo's battery works in the aristo2 as i bought a couple batteries for it. I still do like the aristo though it feels a bit better in my hand.

Well luckily It seems i have not screwed up my phone. Have reset and wiped it multiple times which was annoying, but seems to be ok. It sucks because it looks like the touch screen alone is whats screwing me over. If only i had a way around it. Then again im sure you guys have a better idea of whats going on. Guess ill just be patient until more is posted on subject.

We need a new recovery for this anyway. Since the aristo 2 isn't gonna have multiple versions (besides the Korean base model the 2 is built after), we should be able to build just one recovery using the model number as it's target, we can make it borderline universal if a new version were to pop up.
I decided against going the metro route, buying mine in bulk. So I'll have one to smash when this is all over.

The TWRP method works the same as the Aristo, and the TWRP recovery IS compatible. However the touch screen does not function.. Is there a way to get it to work?

@ninjasinabag @teknoweanie @tribal1209 Hey guys, spent a few hours figuring out how to root. Pretty Simple
1) Enable Developer Options, USB Debugging & OEM Unlock
2) Reboot to Fastboot Mode (Using ADB via PC type: adb reboot bootloader)
3) Add root_boot.img into your adb folder
4) In ADB type: fastboot flash boot root_boot.img
5) After flash successful, type: fastboot reboot
6) Install Magisk Manager App

brad2192 said:
@[email protected]@tribal1209 Hey guys, spent a few hours figuring out how to root. Pretty Simple
1) Enable Developer Options, USB Debugging & OEM Unlock
2) Reboot to Fastboot Mode (Using ADB via PC type: adb reboot bootloader)
3) Add root_boot.img into your adb folder
4) In ADB type: fastboot flash boot root_boot.img
5) After flash successful, type: fastboot reboot
6) Install Magisk Manager App
Click to expand...
Click to collapse
Not to sound sceptical but is this the real deal?

spirithandler said:
Not to sound sceptical but is this the real deal?
Click to expand...
Click to collapse
Please someone let me know! I want this phone rooted (Its an awesome phone) but want some verification before I start flashing and downloading random files.

spirithandler said:
Not to sound sceptical but is this the real deal?
Click to expand...
Click to collapse
Yes, it is. What I did was use LG firmware extractor and extracted the boot image, then I proceeded to patch the boot image with magisk manager. Enabling OEM unlock allows me to flash the boot image with the newly-created custom one. Remember though, you should create a backup of your device because enabling OEM unlock will completely erase everything.

brad2192 said:
@ninjasinabag @teknoweanie @tribal1209 Hey guys, spent a few hours figuring out how to root. Pretty Simple
1) Enable Developer Options, USB Debugging & OEM Unlock
2) Reboot to Fastboot Mode (Using ADB via PC type: adb reboot bootloader)
3) Add root_boot.img into your adb folder
4) In ADB type: fastboot flash boot root_boot.img
5) After flash successful, type: fastboot reboot
6) Install Magisk Manager App
Click to expand...
Click to collapse
Supposedly the img you posted is simply a modified version of Magisk you posted. Someone please explain to me (Who is new to this whole process) why this supposed explanation does not involve any recovery program or requiring of wiping/clearing any cache or what have you?