Related
Warning this will erase your entire tablet and restore it to the way it was when you first turned it on!I'm NOT responsible if you bork your tablet because you can't follow simple instructions!
INSTRUCTIONS:
1) Download and install Win 7 DRIVERS
2) Download and extract Nexus7_2013_KTU84P_Restore.zip WIFI Flo, or Nexus7_Deb_KOT49H_Restore.zip for LTE version Deb, or Nexus7_Deb_KVT49L_Restore.zip for Verizon LTE Model
3) Turn on your tablet, and connect your tablet to the computer (make sure you have USB Debugging enabled on the tablet)
4) Open up folder where you extracted the Nexus7_2013_KTU84P_Restore.zip WIFI Flo, or Nexus7_Deb_KOT49H_Restore.zip for LTE version Deb, or Nexus7_Deb_KVT49L_Restore.zip for Verizon LTE Model
5) Double Click on the "Recovery_Nexus7.bat" and follow the instructions,,,,it really is that easy! (watch video and follow along)
6) If your tablet will not boot and you need to restore, boot your tablet into fastboot (volume down and power) and click the "Dead_Nexus7.bat" file found in the folder.
For those that couldn't find their azzes if a target was painted on it, here's a link to the video.
http://www.youtube.com/watch?feature=player_embedded&v=hectdvR9Y6c
I'm NOT responsible if you bork your tablet because you can't follow simple instructions!
FAQ:
1) You will have to relock your bootloader after you restore. Tablet in fastboot and connected to pc open up command prompt in the folder where these files reside and type: "fastboot oem lock".
2) You will be unrooted after this procedure
3) Your bootloader must be unlocked before using this utility.
If you can't handle these simple instructions, pickup one of these.
If you want to use pre-rooted images for FLO download this toolkit (will restore your tablet pre-rooted)
Nexus_7_Restore_Flo_Rooted.zip
CHANGE LOG:
06/22/14:
Updated With Images KTU84P Flo Wifi (Android 4.4.4)
06/04/14:
Updated With Images KTU84 Flo Wifi (Android 4.4.3)
12/12/13:
Updated With Images KOT49H Flo/Deb 4.4.2
11/20/13:
Updated With Images KRT16S Flo/Deb 4.4
11/15/13:
Updated With Images KRT16o Flo 4.4
11/14/13:
Updated With Images KRT16o Deb 4.4
10/13/13:
Updated With Images JLS36i Deb 4.3.1
09/19/13:
Updated With Images JSS15R Flo
09/16/13:
Updated With Images for Deb (LTE)
08/23/13:
Updated With Google Factory Images JSS15Q
08/09/13:
Updated With Google Factory Images JSS15J
08/08/13:
Uploaded new version with updated Bat files so they reflect being in "fastboot" before continuing for the few that couldn't follow a simple video
Is that a rooted image that you have linked?
dexgen said:
Is that a rooted image that you have linked?
Click to expand...
Click to collapse
First sentence in the OP:
"Warning this will erase your entire tablet and restore it to the way it was when you first turned it on!"
ATGAdmin said:
First sentence in the OP:
"Warning this will erase your entire tablet and restore it to the way it was when you first turned it on!"
Click to expand...
Click to collapse
So it'll end up relocking your device? I didn't see any OEM lock command in the bat files.
dexgen said:
So it'll end up relocking your device? I didn't see any OEM lock command in the bat files.
Click to expand...
Click to collapse
This is to restore your tablet back to the way it was when you first turned it on...just what is it that you don't understand??
I think you want this:
http://forum.xda-developers.com/showthread.php?t=2380268
ATGAdmin said:
Warning this will erase your entire tablet and restore it to the way it was when you first turned it on!
INSTRUCTIONS:
1) Download and install DRIVERS
2) Download and extract Nexus 7 Restore.zip
3) Turn on your tablet, and connect your tablet to the computer (make sure you have USB Debugging enabled on the tablet)
4) Open up folder where you extracted the Nexus 7 Restore.zip
5) Double Click on the "Recovery_Nexus7.bat" and follow the instructions,,,,it really is that easy! (watch video and follow along)
6) If your tablet will not boot and you need to restore, boot your tablet into fastboot (volume down and power) and click the "Dead_Nexus7.bat" file found in the folder.
Click to expand...
Click to collapse
thank you so much! now I can get a warranty exchange from Best Buy, since I have 2 black dots under the screen :crying:
I guess he is asking will bootloader be locked ?
munchy_cool said:
I guess he is asking will bootloader be locked ?
Click to expand...
Click to collapse
And that was answered in the very first sentence of the OP.
Sent from my Nexus 7 using xda premium
dexgen said:
So it'll end up relocking your device? I didn't see any OEM lock command in the bat files.
Click to expand...
Click to collapse
munchy_cool said:
I guess he is asking will bootloader be locked ?
Click to expand...
Click to collapse
bootloader will not be locked when using this process. but it is easy to lock the bootloader
in fastboot, type this in the command prompt:
Code:
fastboot oem lock
Is this a windows only command or can I run this on a Mac? I have ADB and Fastboot running on the mac which is how I installed TWRP and rooted.
Thanks
androidfr33k said:
Is this a windows only command or can I run this on a Mac? I have ADB and Fastboot running on the mac which is how I installed TWRP and rooted.
Thanks
Click to expand...
Click to collapse
Sorry, PC only.
Sent using XDA premium on my Nexus 7 (2) tablet.
0.0 said:
bootloader will not be locked when using this process. but it is easy to lock the bootloader
in fastboot, type this in the command prompt:
Code:
fastboot oem lock
Click to expand...
Click to collapse
Then technically you can't say the device is restored to "when it was first turn on". I think fresh devices all have the bootloader locked.
You guys are worrying way too much about the bootloader. Its a nexus. It takes one simple command in fastboot to unlock it. Again, it's a nexus. Its meant to be easy to unlock so developers can mess with it.
This isn't some HTC or Samsung on Verizon.
Bootloader is not an issue.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Why in adb it says my device is offline??
Sent from my Nexus 7 using Tapatalk 4 Beta
casonswag said:
Why in adb it says my device is offline??
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
make sure USB debugging is checked.
if you don't know how to turn on USB debugging, go to settings > about tablet> clicked like 7 times on the build number. it should then say you're a developer
go back and into "developer options" and it will be there
0.0 said:
make sure USB debugging is checked.
if you don't know how to turn on USB debugging, go to settings > about tablet> clicked like 7 times on the build number. it should then say you're a developer
go back and into "developer options" and it will be there
Click to expand...
Click to collapse
I have that checked adb sees my device but it says offline for some reason
Sent from my Nexus 7 using Tapatalk 4 Beta
androidfr33k said:
Is this a windows only command or can I run this on a Mac? I have ADB and Fastboot running on the mac which is how I installed TWRP and rooted.
Thanks
Click to expand...
Click to collapse
Mac can use the code
zeroxia said:
Then technically you can't say the device is restored to "when it was first turn on". I think fresh devices all have the bootloader locked.
Click to expand...
Click to collapse
trust me, it isn't hard to unlock and lock the bootloader. it's really, really simple. Idk how to express how simple it is to lock and unlock
---------- Post added at 09:50 PM ---------- Previous post was at 09:49 PM ----------
casonswag said:
I have that checked adb sees my device but it says offline for some reason
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
maybe the cable is bad, or the USB port is bad
I find that using one cable doesn't work and using another one does. so just mess with the cables
0.0 said:
Mac can use the code
trust me, it isn't hard to unlock and lock the bootloader. it's really, really simple. Idk how to express how simple it is to lock and unlock
---------- Post added at 09:50 PM ---------- Previous post was at 09:49 PM ----------
maybe the cable is bad, or the USB port is bad
I find that using one cable doesn't work and using another one does. so just mess with the cables
Click to expand...
Click to collapse
I tries my other cord and other usb port on my laptop but still saying offline this sucks i used the same chord and usb ports on my first gen n7 and it worked fine this weird
Sent from my Nexus 7 using Tapatalk 4 Beta
casonswag said:
I tries my other cord and other usb port on my laptop but still saying offline this sucks i used the same chord and usb ports on my first gen n7 and it worked fine this weird
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
did you update the android SDK and drivers? possibly only the drivers need to be updated
0.0 said:
did you update the android SDK and drivers? possibly only the drivers need to be updated
Click to expand...
Click to collapse
Yessir just downloaded the nexus7 root zip from zedo max which has the latest sdk files but the drivers im not sure how to do that i went through the steps to manually find the android_winusb file but its not letting me install it
Sent from my Nexus 7 using Tapatalk 4 Beta
Ok guys... I accidently deleted everything in my SD card...
Now that I'm in TWRP, how exactly can I put files back on the storage so I can flash something?
I can't seem to mount the storage on to the computer in TWRP
Edit: Using the Toolkit, I flash zip.. Now I'm stuck on Google logo and my computer says "waiting for device..."
Any ideas? D:
go in to twrp click advanced then click ADB side and follow this
1. Reboot into TWRP
2. in TWRP, Hit andvanced and find Sideload
3. Swipe to start Sideload
4. Open a CMD Prompt window and Change Directories to where your adb.exe is
5. type adb devices and it should show your device conntected and say sideload
6. Your ZIP file should already be in your adb folder
7. You are now ready to push the zip.....
8. type adb sideload nameofzip.zip
9. Wait until it says 100% and reboot back into recovery to flash the ROM
10. If hitting power does not make the screen come one, type adb reboot recovery
11. if adb reboot recovery does not work, hold power and volume down until it reboots to fastboot then go to recovery
Cool. Worked!
Thanks.
You do realize you cab recover much of what has been lost with data digger or other such tool. I recovered about 80% of my photos with it.
Sent from my Nexus 5
floepie said:
You do realize you cab recover much of what has been lost with data digger or other such tool. I recovered about 80% of my photos with it.
Sent from my Nexus 5
Click to expand...
Click to collapse
On the nexus 5?
I haven't seen anything that can recover data on FUSE devices yet. Please can you link?
Sent from my Nexus 5 using Tapatalk
rootSU said:
On the nexus 5?
I haven't seen anything that can recover data on FUSE devices yet. Please can you link?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
this seemed to work on the galaxy nexus.... so in theory it should work for the nexus 5
http://forum.xda-developers.com/showthread.php?t=1994705
Zepius said:
this seemed to work on the galaxy nexus.... so in theory it should work for the nexus 5
http://forum.xda-developers.com/showthread.php?t=1994705
Click to expand...
Click to collapse
Yes.
In fact I have a link to that thread in my data recovery thread for nexus 5
http://forum.xda-developers.com/showthread.php?t=2534010
What I really want to know is if datadigger has been used on a n5 successfully because I have never found any app that can retrieve data on FUSE
Sent from my Nexus 5 using Tapatalk
rootSU said:
Yes.
In fact I have a link to that thread in my data recovery thread for nexus 5
http://forum.xda-developers.com/showthread.php?t=2534010
What I really want to know is if datadigger has been used on a n5 successfully because I have never found any app that can retrieve data on FUSE
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
i doubt it. i also have never heard of an app to recovery data on a fused storage system.
rootSU said:
On the nexus 5?
I haven't seen anything that can recover data on FUSE devices yet. Please can you link?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I followed the guide quoted above but I found diskdigger from the app store to be just as good if not better. But be sure to do it sooner than later as you will begin to overwrite your lost data.
Sent from my Nexus 5
floepie said:
I followed the guide quoted above but I found diskdigger from the app store to be just as good if not better. But be sure to do it sooner than later as you will begin to overwrite your lost data.
Sent from my Nexus 5
Click to expand...
Click to collapse
ON the nexus 5?
Please link to the app. The only one I see is about secure data.
If they have honestly become the first company to restore data on fuse, they're onto a goldmine
Sent from my Nexus 5 using Tapatalk
Zepius said:
i doubt it. i also have never heard of an app to recovery data on a fused storage system.
Click to expand...
Click to collapse
Wait. Sorry I had to do this during the last days of my N4 and it worked quite well. Didn't the N4 have the same drive as the N5?
The app is called diskdigger undelete.
Sent from my Nexus 5
o I rooted my nexus 5. No issues. Installed TWRP. Same. Downloaded CM and GA to the phone. Then, very foolishly, wiped everything to prep for the install - SD card included. Now, all I can load is TWRP. No ROM to be found - obviously. Computer won't recognize the phone to load a ROM that way. Would be VERY appreciative of any help. TY!S
you can use the 'adb push' command in recovery to transfer a rom zip to the phone via your computer
meangreenie said:
you can use the 'adb push' command in recovery to transfer a rom zip to the phone via your computer
Click to expand...
Click to collapse
I have TWRP v2.6.3.0 installed. The bootloader option takes me to TWRP. The Recovery option just hangs at the Google splash screen. Can you be more specific pls? Thanks for the help.
bradley.robt said:
I have TWRP v2.6.3.0 installed. The bootloader option takes me to TWRP. The Recovery option just hangs at the Google splash screen. Can you be more specific pls? Thanks for the help.
Click to expand...
Click to collapse
Install adb drivers on your computer then go to TWRP recovery with your phone connected to your computer. Type 'adb devices', to check if your phone is detected, it should display your phone's serial number. Then you can 'adb push file' to transfer the cm/gapps zips from your computer to phone's internal sdcard.
So you have no idea how to use ADB? You're in for a real long night. -__-
Read this
http://forum.xda-developers.com/showthread.php?t=2513701
And this
http://forum.xda-developers.com/showthread.php?t=2507905
aldyu said:
Install adb drivers on your computer then go to TWRP recovery with your phone connected to your computer. Type 'adb devices', to check if your phone is detected, it should display your phone's serial number. Then you can 'adb push file' to transfer the cm/gapps zips from your computer to phone's internal sdcard.
Click to expand...
Click to collapse
Sorry, assume 'adb devices' is in the command prompt, but noob town - which folder in the ADT parent folder?
RoyJ said:
So you have no idea how to use ADB? You're in for a real long night. -__-
Read this
http://forum.xda-developers.com/showthread.php?t=2513701
And this
http://forum.xda-developers.com/showthread.php?t=2507905
Click to expand...
Click to collapse
That's what I figured, but...challenge accepted. Thanks for the links.
RoyJ said:
So you have no idea how to use ADB? You're in for a real long night. -__-
Read this
http://forum.xda-developers.com/showthread.php?t=2513701
And this
http://forum.xda-developers.com/showthread.php?t=2507905
Click to expand...
Click to collapse
RoyJ,
Appreciate the help. TY, all's good.
Happened to me a few times tinkering with the gnex, n4...boneheadedly wiped the internal storage. Easiest fix in my opinion is to just flash factory stock and start back from stretch. If not like they said you're in for a long night trying to get your phone to sync up to push the files via adb if you aren't familiar with the stuff.
Do wish you the best. Been there.
I have not been in that situation but couldn't you use a OTG cable (a Y type one which accepts power as well) and a SD card or stick and then mount it within TWRP to access a ROM to flash...?
EDIT: Also consider the Nexus Toolkit - very useful.
I really think that the faster way is to flash stock firmware back (if you have no experience with ADB commands).
Don't be so scared of adb. Its hard if you don't know Linux but adb is really really copy and paste for first time use. (That's how I learned anyways) You learn it once and it stays current and useful.
Sent from my Nexus 7 using XDA Free mobile app
Just install official images of nexus 5. No need to learn complex stuff where u have no idea even abt adb.
TheLastSidekick said:
Don't be so scared of adb. Its hard if you don't know Linux but adb is really really copy and paste for first time use. (That's how I learned anyways) You learn it once and it stays current and useful.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
It's really not that hard.. You plug it in, open a folder, open the prompt and type a few words.. My advice is to try and learn.
sent from my Nexus 5
Seadra said:
Just install official images of nexus 5. No need to learn complex stuff where u have no idea even abt adb.
Click to expand...
Click to collapse
A bit discouraging friend. I say learn on all about adb it's essential for Android. Knowledge is power.
Sent from my Nexus 7 using Tapatalk
Seadra said:
Just install official images of nexus 5. No need to learn complex stuff where u have no idea even abt adb.
Click to expand...
Click to collapse
You need fastboot/adb to do it anyways. Unless you use toolkits, ew.
Glad you got it sorted.
Letharqy said:
You need fastboot/adb to do it anyways. Unless you use toolkits, ew.
Click to expand...
Click to collapse
Yes, just the adb drivers needs to be installed. And I have never used toolkit ever.
TheLastSidekick said:
A bit discouraging friend. I say learn on all about adb it's essential for Android. Knowledge is power.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
No, you didn;t get my point. I told him to straight away restore by images just because his phone wasn't working at all. He can learn all that stuff later, but atleast he should be with no phone at all.
Seadra said:
Yes, just the adb drivers needs to be installed. And I have never used toolkit ever.
Click to expand...
Click to collapse
How would you flash the .imgs without using adb/fastboot?
Letharqy said:
How would you flash the .imgs without using adb/fastboot?
Click to expand...
Click to collapse
by adb drivers, I mean adb/fastboot or SDK and drivers of the phone that's always included.
Hey guys, I have a problem with my Nexus 5, it's that I cannot boot ANY Android (No android at all, just shows Google logo)
I can get into Recovery mode, but the phone is EMPTY (no rom on it).
Adb (How to push files using ADB without Android SDK The Easy Way - Team Nocturnal <-- go to youtube and paste that, i followed that tutorial) doesn't work unfortunately.
Any suggestions guys ?
Just wrote a thread about adb. Click link in signature then look for section 1
Sent from my Nexus 5 using Tapatalk
spluxor said:
Hey guys, I have a problem with my Nexus 5, it's that I cannot boot ANY Android (No android at all, just shows Google logo)
I can get into Recovery mode, but the phone is EMPTY (no rom on it).
Adb (How to push files using ADB without Android SDK The Easy Way - Team Nocturnal <-- go to youtube and paste that, i followed that tutorial) doesn't work unfortunately.
Any suggestions guys ?
Click to expand...
Click to collapse
Google 15 second adb drivers xda. It's probably in rootSu's guide. That'll set up the adb you need
Sent from my Nexus 5 using XDA Free mobile app
It is indeed
Sent from my Nexus 5 using Tapatalk
I unfortunately cannot pass the 'unwanted things' in How to test adb and fastboot work, since I cannot install the driver.
It shows like AOSP on HammerHead and I cannot install a single driver.
Thanks!
spluxor said:
I unfortunately cannot pass the 'unwanted things' in How to test adb and fastboot work, since I cannot install the driver.
It shows like AOSP on HammerHead and I cannot install a single driver.
Thanks!
Click to expand...
Click to collapse
You need these drivers http://forum.xda-developers.com/showthread.php?t=2386956
If you are using windows 8 or 8.1 then you have to turn off driver signature enforcement
bitdomo said:
You need these drivers http://forum.xda-developers.com/showthread.php?t=2386956
If you are using windows 8 or 8.1 then you have to turn off driver signature enforcement
Click to expand...
Click to collapse
That was already told in my thread.
Sent from my Nexus 5 using Tapatalk
---------- Post added at 06:56 AM ---------- Previous post was at 06:55 AM ----------
spluxor said:
I unfortunately cannot pass the 'unwanted things' in How to test adb and fastboot work, since I cannot install the driver.
It shows like AOSP on HammerHead and I cannot install a single driver.
Thanks!
Click to expand...
Click to collapse
Well, you need to fix that.
If you want help please explain in detail your issue
Sent from my Nexus 5 using Tapatalk
Well the good thing is that I unbricked it, by following How to Unbrick or Unroot the Nexus 5 (incl. Tamper Flag Reset) on YouTube by C4ETech, the bad thing is that I have to install everything again, but okay my fault
Anyways guys thanks for help !
If you can see the Google logo when you turn on your device and can go into recovery, it's not bricked. Bricked means it will not turn on at all. It's essentially just a "brick" with no possible way to recover.
vanessaem said:
If you can see the Google logo when you turn on your device and can go into recovery, it's not bricked. Bricked means it will not turn on at all. It's essentially just a "brick" with no possible way to recover.
Click to expand...
Click to collapse
Completely agree. And by this rule, there is not really such a thing as a software brick either.
That said, I do sometimes use the term "Radio Brick" when a Rdio flash has gone wrong and it cannot be fixed without being sent to the Vendor. Can't think of a better term.
rootSU said:
Completely agree. And by this rule, there is not really such a thing as a software brick either.
That said, I do sometimes use the term "Radio Brick" when a Rdio flash has gone wrong and it cannot be fixed without being sent to the Vendor. Can't think of a better term.
Click to expand...
Click to collapse
By that term, anything nonrecoverable can be considered a brick which is still more accurate than a device being bricked or software bricking a device yet it can still be turned on and/or charged.
Anyway, I say all that to say to the OP and all who think they are bricked, all is not lost if your device functions at all.
Anyone have a link or instructions on how to root, unlock the Bootloader, and install custom recovery on the Metro varient running stock 6.0? Been searching around and can only find 5.1 and down instructions. Cant afford to brick.
from what i am reading, you should be able to use the same method that they used to root the tmobile 6.0 update found here http://androidforums.com/threads/guide-how-to-root-t-mobile-6-0-update.1008880/
i havent tried it myself yet, so if you have the courage please report back and let us know how it goes
edit i couldnt wait anymore...i kdz'd back to stock and im trying to force the ota to come through...will post back with results when i get it and attempt to root
Thank you for this link. This worked beautifully. i was able to get into TWRP and do a full backup and install Super SU. Yes, I'm using MS631 with Android 6.0 and now I can say I'm successfully rooted. This made my day being able to root the Stylo after the upgrade.
Encase you're unsure on how to gain access to a command line through Windows hold down shift key and right click the file. Should see the option to open command line and from then on follow the steps.
czjrli said:
Thank you for this link. This worked beautifully. i was able to get into TWRP and do a full backup and install Super SU. Yes, I'm using MS631 with Android 6.0 and now I can say I'm successfully rooted. This made my day being able to root the Stylo after the upgrade.
Encase you're unsure on how to gain access to a command line through Windows hold down shift key and right click the file. Should see the option to open command line and from then on follow the steps.
Click to expand...
Click to collapse
cool deal glad it worked out for you...im just sitting around waiting to get the update now...hopefully when the phone gets fully charged and check again i will see it
Any way at all possible to accomplish this without a pc?
AP2FTW said:
cool deal glad it worked out for you...im just sitting around waiting to get the update now...hopefully when the phone gets fully charged and check again i will see it
Click to expand...
Click to collapse
If you manually change your time to 11pm local time and then reboot your phone you should see the upgrade message in the system update section
czjrli said:
If you manually change your time to 11pm local time and then reboot your phone you should see the upgrade message in the system update section
Click to expand...
Click to collapse
didnt work
I woke up to the system update message 2 days ago. Yall should see it soon. Now if only i could root without a pc....
Goongydin said:
I woke up to the system update message 2 days ago. Yall should see it soon. Now if only i could root without a pc....
Click to expand...
Click to collapse
I had sucessful root on 6.0 via kingroot. Be sure to go into developer options and enable I am unlock before rebooting.
Sent from my LGMS631 using XDA-Developers mobile app
tokenpoke said:
I had sucessful root on 6.0 via kingroot. Be sure to go into developer options and enable I am unlock before rebooting.
Sent from my LGMS631 using XDA-Developers mobile app
Click to expand...
Click to collapse
I thought you had to fastboot oem unlock the bootloader before rooting?
Revenant Ghost said:
I thought you had to fastboot oem unlock the bootloader before rooting?
Click to expand...
Click to collapse
It doesn't automatically reboot for me. So I don't think it matters as long as you unlock before rebooting.
Sent from my LGMS631 using XDA-Developers mobile app
---------- Post added at 03:32 PM ---------- Previous post was at 03:30 PM ----------
I didn't doo fastboot btw.
Sent from my LGMS631 using XDA-Developers mobile app
Revenant Ghost said:
I thought you had to fastboot oem unlock the bootloader before rooting?
Click to expand...
Click to collapse
Yes i thought so too otherwise you risk a secure boot error correct?
Goongydin said:
Yes i thought so too otherwise you risk a secure boot error correct?
Click to expand...
Click to collapse
That's right. That's what happened to me. The only ways to fix the problem is either by flashing a KDZ (with a computer), or send it to LG for repairs. Better safe than sorry.
Hey guys kinda stuck need root(apps req) no access to a pc that i can install anything on (outta town in a hotel) no way to root with out the pc? Rooted several phones in the past mostly samsungs. Most already had one click root available....
Lgms631 mm6.0
Ok june 6th new king root update works!
Am I the only one having trouble getting into fastboot?
jjswag said:
Am I the only one having trouble getting into fastboot?
Click to expand...
Click to collapse
nope. It happens to me too. I think you have to have Android SDK Tools installed on your PC alongside ADB for it to work, sadly
jjswag said:
Am I the only one having trouble getting into fastboot?
Click to expand...
Click to collapse
shawnster480 said:
nope. It happens to me too. I think you have to have Android SDK Tools installed on your PC alongside ADB for it to work, sadly
Click to expand...
Click to collapse
Did you install ADB and Fastboot?
http://forum.xda-developers.com/showthread.php?t=2317790
tube517 said:
Did you install ADB and Fastboot?
http://forum.xda-developers.com/showthread.php?t=2317790
Click to expand...
Click to collapse
I did, it turns out, I had to install the appropriate drivers fro the Stylo MTP, then I had to install the appropriate ADB Drivers by updating to LGE Mobile ADB Drivers, then after that, I had to do "adb reboot-bootloader" and that booted it straight into the fastboot interface, but to no avail, I couldn't get fastboot to recognise the device, so I went into device manager, and I saw "(something)com bootloader interface", I expanded that, and saw Android Bootloader interface. So I updated the software, hit load from PC, and hit Android Bootloader Interface Version 9.0.0.0 instead of 11, and fastboot saw my phone
message me further if you need any help, if you want me to Teamspeak you so I can show you directly, I'll be glad to help you
Can somebody please help me I'm trying to root my phone when it comes to rooting I'm a virgin to it and I heard it's pretty safe to do using I have a LG Stylo 2 plus Metro model LG ms550 6.0.1 marshmallow but I'm not too dumb lol I know how to load up XBMC put add-ons on their use different builds load up operating systems programs on computers and stuff like that but rooting a phone is totally different to me
Root help lg stylo ms631 metro pcs
I unlocked the bootloader on my phone but i cant root i tried kingroot it just tells me it cant root my device then i tried adb and fastboot everytime i tried to, flash twrp via fastboot then install super su from twrp, i get failed remote: unknown command i used the command, "fastboot flash recovery twrp.img" im on lg stylo ms631 6.0 metro pcs and my computer is windows 10