Related
So i read thru a lot of the root threads & none of them made anh sense to me.I downloaded ADB,moto drivers, sdk,jdk,etc.But still none of it made any sense. So i tried the 1 click root & soft bricked my xoom. It gets stuck at the Motorola screen. I tried getting into the options & wiping user data,factory reset.But it would still get stuck at the dual core screen. So i tried a suggestion of using 1 click root to undo the root. But it said the xoom would say "done" twice on the screen but it only said "done" once. So then i relocked it hoping it would reboot & work but it didn't. I see 1 guy was able to fix his using a rooting guide.I hope someone here can help me out.
Sent from my DROIDX using XDA App
Arun01 said:
So i read thru a lot of the root threads & none of them made anh sense to me.I downloaded ADB,moto drivers, sdk,jdk,etc.But still none of it made any sense. So i tried the 1 click root & soft bricked my xoom. It gets stuck at the Motorola screen. I tried getting into the options & wiping user data,factory reset.But it would still get stuck at the dual core screen. So i tried a suggestion of using 1 click root to undo the root. But it said the xoom would say "done" twice on the screen but it only said "done" once. So then i relocked it hoping it would reboot & work but it didn't. I see 1 guy was able to fix his using a rooting guide.I hope someone here can help me out.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Motorola published the factory files for Xoom awhile back so if you still have fastboot, you can recover from it.
http://developer.motorola.com/produ...utm_source=supportforums&utm_term=unlockboard
I relocked it using the 1 click root and all it says now is "Failed to boot LNX 0x0004" "Starting RSD mode 2".I'm now trying to use the 1 click root to try to get it back to where it was..I just don't understand all of the rooting methods even after downloading adb,sdk,,etc..It may as well be written in Chinese.I'm sure if i saw someone actually do it i could catch on to it but right now rooting is confusing..hence i went with the 1 click.I had no problem 1 click rooting my droid x with a 1 click root.
Stop using one click crap. If you don't know what you're then you should not be messing with your device.
Sent from my DROIDX using XDA App
I can. Just won't.
Arun01 said:
I relocked it using the 1 click root and all it says now is "Failed to boot LNX 0x0004" "Starting RSD mode 2".I'm now trying to use the 1 click root to try to get it back to where it was..I just don't understand all of the rooting methods even after downloading adb,sdk,,etc..It may as well be written in Chinese.I'm sure if i saw someone actually do it i could catch on to it but right now rooting is confusing..hence i went with the 1 click.I had no problem 1 click rooting my droid x with a 1 click root.
Click to expand...
Click to collapse
Type oem unlock again and then flash the stock images...youll be good to go...also there are really good stickies in here that help..pleasedont forget to search before starting a new thread.
albundy2010 said:
I can. Just won't.
Click to expand...
Click to collapse
And this is rude and uncalled for
The OP stated he read quides etc and none of it made sense to him etc. So instead of asking for help a explanation he tries a one click method. Which is stupid. He than softbricks the device and asked for help here.
Then he is told that moto released the factory images and use fastboot if he still has it to recover the device. He then decides to ignore that entirely and go back and try to unroot/restore with the one click BS again. Then he tries to use it again to go back to where he was. Just flat out stupid. He did something when he had no idea wtf he was doing. Was told what to do. Did not do it. He even said it is like Chinese to him.
So I told him to stop messing with one click crap. Which is correct. I told him to stop messing with the ****ing thing. Which is also correct. He needs to learn/understand wtf he is doing. Instead of basically button mashing/trying crap and hoping it will basically fix itself.
On top of that this posted in the wrong section. Uncalled for my ass. He is the one that was rude when told to not mess with the one click or the device. Now this part is rude. **** his stupid ass.
csseale said:
Type oem unlock again and then flash the stock images...youll be good to go...also there are really good stickies in here that help..pleasedont forget to search before starting a new thread.
Click to expand...
Click to collapse
How do i get to that ..and where do i type it at ..i looked in device manager & does recognize the xoom..it says "Motorola USB Device:Motorola Flash Interface"..In properties under "Driver" it has options for driver details..update driver..disable & uninstall.Can i do anything with them?
I tried opening SDK manager but it never lets me type anything in the box as it's always trying to do some kind of update in another window so when i close the window it closes all of the windows.
Sent from my DROIDX using XDA App
Arun01 said:
So i read thru a lot of the root threads & none of them made anh sense to me.I downloaded ADB,moto drivers, sdk,jdk,etc.But still none of it made any sense. So i tried the 1 click root & soft bricked my xoom. It gets stuck at the Motorola screen. I tried getting into the options & wiping user data,factory reset.But it would still get stuck at the dual core screen. So i tried a suggestion of using 1 click root to undo the root. But it said the xoom would say "done" twice on the screen but it only said "done" once. So then i relocked it hoping it would reboot & work but it didn't. I see 1 guy was able to fix his using a rooting guide.I hope someone here can help me out.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
If they didnt make sense to you in the first place you probably shoud not be attempting to root... U went straight to an old method that even the developer has marked in hs thread can full brick you and should not be used. The xoom costs like 600 bucks... Why wouldnt you do extensive research on how to root? If you did not understand the terms why didn't you research the methods and learn it?
I hope you can flash the factory imagines back through fastboot and adb, but i just do not understand why people attempt this stuff when they have no idea what the terms even mean...
You need to have sdk, hook up to usb on your computer, and follow one of the unlock guides posted on this site... A real one using adb... Then you need to follow a root one...
Sorry that is not more helpful, but half of this experience is that you need to learn what you are doing and the instructions are out there. If they do not make sense at this point im afraid you are stuck. Now the way your device is you have to figure it out...
Arun01 said:
I relocked it using the 1 click root and all it says now is "Failed to boot LNX 0x0004" "Starting RSD mode 2".I'm now trying to use the 1 click root to try to get it back to where it was..I just don't understand all of the rooting methods even after downloading adb,sdk,,etc..It may as well be written in Chinese.I'm sure if i saw someone actually do it i could catch on to it but right now rooting is confusing..hence i went with the 1 click.I had no problem 1 click rooting my droid x with a 1 click root.
Click to expand...
Click to collapse
Please check out this thread.It is called Root heaven for a reason. Just about every viable rooting guide, all the files and explanations you will need are here.
http://forum.xda-developers.com/showthread.php?t=1209341
I urge you to just calm down, read about what is the sdk, what is adb, how to recover from a soft brick and so on. The xda xoom forum is all about learning and teaching. We were all noobies once. The Xoom is a very complex device with many models and vesions and one clicks just don't cut it. There are rooting methods that are relatively simple but you really need to be prepared before you get started.
Good luck and don't despair. You'll get there.
Thanks for the help guys.I'm reading through all of the threads and i see a typo in a post that in the command window would've never let me find the sdk tools on my c drive. But after i retyped it i did it & a bunch of writing came up. Trying to figure out now how to flash the stock images to the xoom.
Sent from my DROIDX using XDA App
Arun01 said:
Thanks for the help guys.I'm reading through all of the threads and i see a typo in a post that in the command window would've never let me find the sdk tools on my c drive. But after i retyped it i did it & a bunch of writing came up. Trying to figure out now how to flash the stock images to the xoom.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
at first, make sure you install android sdk correctly. then go to android sdk-folder in your computer, u will find a folder named platform-tool. Press shift+ right click on it, then choose open command window here. After that, type in "adb devices" or "fastboot devives" to check if your xoom is connected. If yes,you good to go. If no, check your android sdk installed process
After i type in abd devices it says list of devices attached but shows nothing..i did copy the sdk tools folder to the c drive like i was told.
@OP
If you can't do it yourself, getting somebody to help you (in person) is always an option. If you live in a major city, advertise on Craigslist or some equivalent. Offer $50 for debricking + some tutorial.
In order for the device to show up in adb the device needs to actually booted into the os and have USB debugging enabled. Which you can't do.
What you're supposed to do is use fastboot.
Boot the device into fastboot mode.
Use fastboot devices to see if the computer see's it/everything is set up etc.
If bootloader is locked unlock it with fastboot OEM unlock.
Then flash the official images for your exact device. Fastboot flash boot boot.img and so on.
The last command on restoring to stock guides is optional. Fastboot OEM lock. I would not do it. No reason to relock it. If do learn decide to root later you would have to unlock again and loose all data.
albundy2010 said:
In order for the device to show up in adb the device needs to actually booted into the os and have USB debugging enabled. Which you can't do.
What you're supposed to do is use fastboot.
Boot the device into fastboot mode.
Use fastboot devices to see if the computer see's it/everything is set up etc.
If bootloader is locked unlock it with fastboot OEM unlock.
Then flash the official images for your exact device. Fastboot flash boot boot.img and so on.
The last command on restoring to stock guides is optional. Fastboot OEM lock. I would not do it. No reason to relock it. If do learn decide to root later you would have to unlock again and loose all data.
Click to expand...
Click to collapse
That's good advice...no reason to re-lock. But get back to square one so that you're functional and then when you're ready to try again, do it the right way.
Again, good luck!
albundy2010 said:
In order for the device to show up in adb the device needs to actually booted into the os and have USB debugging enabled. Which you can't do.
What you're supposed to do is use fastboot.
Boot the device into fastboot mode.
Use fastboot devices to see if the computer see's it/everything is set up etc.
If bootloader is locked unlock it with fastboot OEM unlock.
Then flash the official images for your exact device. Fastboot flash boot boot.img and so on.
The last command on restoring to stock guides is optional. Fastboot OEM lock. I would not do it. No reason to relock it. If do learn decide to root later you would have to unlock again and loose all data.
Click to expand...
Click to collapse
Thanks a lot.I was able to unlock it then it rebooted & stopped at the Motorola screen then i started the 1st command: fastboot flash boot boot.img & it says waiting on device..but nothing happens so far.Should i move on to the next step or retry?
Isn't there anyone one here who would be willing to make a rom for the ME301t besides the stock ones? If we were willing to donate money to get it done?
krash1256 said:
Isn't there anyone one here who would be willing to make a rom for the ME301t besides the stock ones? If we were willing to donate money to get it done?
Click to expand...
Click to collapse
No offense, but i don't think this is the section for requests. FAQ and general discussion would be more appropriate.
Oops, sorry
DaringDomino3s said:
No offense, but i don't think this is the section for requests. FAQ and general discussion would be more appropriate.
Click to expand...
Click to collapse
Sorry didn't know.
I assumed, that's why i said something as soon as i saw it. I'm new to the posting rules here too, and i have seen that the development section is taken seriously.
Sorry about your device scenario. Im sure something will come along start a thread campaigning in a place where it wont get deleted and you may find more people that know someone wlling.
Cromi-x and Geimlock are already compatible with ME301T... :good::good::victory:
Since the ME301T is so close to the TF300 in terms of specs and because of how easy it was to make the ME301 work on CROMI or GRIMLOCK, its possible that there might only be a few minor things that need to change to make a ME301 work on a CM rom. Since there are no devs who own an ME301T we would needs some help from the community to get it to work.
Mainly we would need for someone with an ME301T to install a CM based rom and see if it will boot. From there you would need to get a logcat and send it to us so we can see if we can fix the issues that are preventing it from working.
hardslog said:
Since the ME301T is so close to the TF300 in terms of specs and because of how easy it was to make the ME301 work on CROMI or GRIMLOCK, its possible that there might only be a few minor things that need to change to make a ME301 work on a CM rom. Since there are no devs who own an ME301T we would needs some help from the community to get it to work.
Mainly we would need for someone with an ME301T to install a CM based rom and see if it will boot. From there you would need to get a logcat and send it to us so we can see if we can fix the issues that are preventing it from working.
Click to expand...
Click to collapse
Someone tried it here. http://forum.xda-developers.com/showthread.php?p=48077047#post48077047
It didn't work for me yet. Maybe you could take a look and see if I'm doing something wrong or if there's something wrong with the file. Am more than willing to help in anyway I can.
krash1256 said:
Someone tried it here. http://forum.xda-developers.com/showthread.php?p=48077047#post48077047
It didn't work for me yet. Maybe you could take a look and see if I'm doing something wrong or if there's something wrong with the file. Am more than willing to help in anyway I can.
Click to expand...
Click to collapse
Sounds like it isn't too far off. What I need is for someone to try and flash a CM rom and send me logs of when it is booting up etc. As a suggestion, I would try this rom: GRIMLOCK_CM_3.0 as it is the rom I am working on. It would be easiest for me to help on that.
hardslog said:
Sounds like it isn't too far off. What I need is for someone to try and flash a CM rom and send me logs of when it is booting up etc. As a suggestion, I would try this rom: GRIMLOCK_CM_3.0 as it is the rom I am working on. It would be easiest for me to help on that.
Click to expand...
Click to collapse
Okay, will do. I'll download and it and give it a shot. I'm not very good with the logcat stuff, lol, but I will do my best.
Well, it boots into the rom and I get a little circle which is a mouse I guess. I can get around and I can get into settings but I can't figure out how to get down to about tablet so I can get to usb debugging. If I try to adb while it's booting up adb just says waiting for device... So I can't do the logcat. Any suggestions on what I'm doing wrong or a way to get adb working?
krash1256 said:
Okay, will do. I'll download and it and give it a shot. I'm not very good with the logcat stuff, lol, but I will do my best.
Well, it boots into the rom and I get a little circle which is a mouse I guess. I can get around and I can get into settings but I can't figure out how to get down to about tablet so I can get to usb debugging. If I try to adb while it's booting up adb just says waiting for device... So I can't do the logcat. Any suggestions on what I'm doing wrong or a way to get adb working?
Click to expand...
Click to collapse
Okay, I messed around and finally got usb debugging turned on. Rebooted and did this logcat. I can't get wifi turned on at all.
BTW: I love this rom without all the google crap on it. I have always hated having to run through all the setup wizard crap too. Thank you for helping with this. I'm very excited about getting this rom for my tablet.
krash1256 said:
Okay, I messed around and finally got usb debugging turned on. Rebooted and did this logcat. I can't get wifi turned on at all.
BTW: I love this rom without all the google crap on it. I have always hated having to run through all the setup wizard crap too. Thank you for helping with this. I'm very excited about getting this rom for my tablet.
Click to expand...
Click to collapse
Try to flash THIS after flashing the rom and see what happens.
hardslog said:
Try to flash THIS after flashing the rom and see what happens.
Click to expand...
Click to collapse
Okay, I wasn't sure if you meant to flash both files one right after the other, so I flashed the rom, then the test. Sticks me at CyanogenMod animation. Then I did a clean flash of just the rom, rebooted and flashed the test, it booted, said Android is updating apps and then gets stuck at starting apps. So then I rebooted just to see if maybe that would do it but that just sticks at CM animation once again.
krash1256 said:
Okay, I wasn't sure if you meant to flash both files one right after the other, so I flashed the rom, then the test. Sticks me at CyanogenMod animation. Then I did a clean flash of just the rom, rebooted and flashed the test, it booted, said Android is updating apps and then gets stuck at starting apps. So then I rebooted just to see if maybe that would do it but that just sticks at CM animation once again.
Click to expand...
Click to collapse
I meant to flash the rom then the test.
Can you get my any logs?
hardslog said:
I meant to flash the rom then the test.
Can you get my any logs?
Click to expand...
Click to collapse
I don't know how to get log during boot. I tried turning on usb debugging first and then flashing the test and then tried to logcat but it just says waiting for device. Is there a specific way to get adb to work during boot?
hardslog said:
I meant to flash the rom then the test.
Can you get my any logs?
Click to expand...
Click to collapse
I wasn't doing adb devices first then the logcat command. Duh. Here's the logcat.
Test # 2
@krash1256
Ok here is another one to try. Again Flash GRIMLOCK_CM first and then try flashing this one. According to the logs its possible that the wifi got fixed but the extra files I put in borked other stuff.
hardslog said:
@krash1256
Ok here is another one to try. Again Flash GRIMLOCK_CM first and then try flashing this one. According to the logs its possible that the wifi got fixed but the extra files I put in borked other stuff.
Click to expand...
Click to collapse
Okay, it now boots into the rom but you still have to use the little circle as a mouse and I can now turn wifi on but it just sticks at turning on wifi.
Turned wifi off and back on now it says To see available networks, turn on wifi.
krash1256 said:
Okay, it now boots into the rom but you still have to use the little circle as a mouse and I can now turn wifi on but it just sticks at turning on wifi.
Turned wifi off and back on now it says To see available networks, turn on wifi.
Click to expand...
Click to collapse
Ok so wifi still doesn't work, but it is a step in the right direction.
I don't really understand what you mean by a little circle as a mouse though?
and again, the more logs the merrier
hardslog said:
Ok so wifi still doesn't work, but it is a step in the right direction.
I don't really understand what you mean by a little circle as a mouse though?
and again, the more logs the merrier
Click to expand...
Click to collapse
Instead of being able to just touch the screen and make choices, this little round circle pops up when you touch the screen and you have to move that little circle around and tap on the circle twice to make choices. It's like using a touch pad for the mouse on a laptop. For instance, if you want to open settings you have to position the little circle on the settings button, tap twice, it opens settings, then you have to position the circle on say wifi and tap the circle again. To scroll, you have to position the little circle at the very bottom of settings, and it's a hit or miss type of thing, tap it and then move it upwards to get to the bottom, like about tablet and tap the little circle again. Does that make since? The rom is basically mouse driven instead of touch driven.
This logcat is while it's booting and also once I'm in the rom.
Bluetooth is definitely working. I connected a bluetooth mouse and I can navigate with that instead of having to navigate with the little circle.
Trying to get my V20 rooted I figured since it's been awhile I'd try and ask hopping not to get my head ripped off about rooting this beast. I would greatly appreciate some help. Tried in the past failed miserably.
ice5192 said:
Trying to get my V20 rooted I figured since it's been awhile I'd try and ask hopping not to get my head ripped off about rooting this beast. I would greatly appreciate some help. Tried in the past failed miserably.
Click to expand...
Click to collapse
I am coming from the Note 7 and Samsung background. I was apart of the Tekhd team. When the note 7 starting exploding and I had to turn it in I got the v10 to test then I prefer ordered the v20.
I just need some pointers on what I need to do the rooting process on this phone is very different from what I have been used to...
how have you failed ? what methods have you used? .. ill help you out as much as i can. i had trouble rooting before so i feel your pain
Just updated to lastest version.
xDEMON87x said:
how have you failed ? what methods have you used? .. ill help you out as much as i can. i had trouble rooting before so i feel your pain
Click to expand...
Click to collapse
Which version should I use? I have the lastest update now.
Hey,
Just follow the Recowvery thread, then install whatever ROM you want after you have TWRP.
https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
I'll try I do have the newest build. December release.
ice5192 said:
I'll try I do have the newest build. December release.
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=fZEL96MPLvY , follow this guide..
xDEMON87x said:
, follow this guide..
Click to expand...
Click to collapse
O tried this but when I got to type the dirtycow commands it simply doesn't find it it says no such file directory exist
egren58 said:
O tried this but when I got to type the dirtycow commands it simply doesn't find it it says no such file directory exist
Click to expand...
Click to collapse
Before copy twrp.img to internal storage, make sure the name is exactly twrp.img (it MUST be all lower case).
SuperSU file must be copied to memory card.
Anyone free this Saturday willing to help me root I have tried every method... I do where I have done wrong
egren58 said:
Anyone free this Saturday willing to help me root I have tried every method... I do where I have done wrong
Click to expand...
Click to collapse
I & a few others used this a few times,the still pics might be better since it gives you time to reread any step. I put some tips in the comment section. It's basically be the manual dirtycow way (thread with the 120+ pages).
http://android.gadgethacks.com/how-to/root-your-t-mobile-lg-v20-using-dirty-cow-0175329/
2muchspl said:
I & a few others used this a few times,the still pics might be better since it gives you time to reread any step. I put some tips in the comment section. It's basically be the manual dirtycow way (thread with the 120+ pages).
http://android.gadgethacks.com/how-to/root-your-t-mobile-lg-v20-using-dirty-cow-0175329/
Click to expand...
Click to collapse
I figured it out. It turns out that I was using the smaller portable version of adb I went ahead and install android sdk n all the files again n it worked perfectly!! ????
egren58 said:
I figured it out. It turns out that I was using the smaller portable version of adb I went ahead and install android sdk n all the files again n it worked perfectly!!
Click to expand...
Click to collapse
Congrats & welcome to the club!!!:good:
Don't forget not to do a factory reset from inside Android,only in TWRP.
2muchspl said:
Congrats & welcome to the club!!!:good:
Don't forget not to do a factory reset from inside Android,only in TWRP.
Click to expand...
Click to collapse
I formated data bia twrp when I first booted. But one thing is.. I cant figure out how to boot into twrp is it power and volume up?
egren58 said:
I formated data bia twrp when I first booted. But one thing is.. I cant figure out how to boot into twrp is it power and volume up?
Click to expand...
Click to collapse
Power and Volume down
2muchspl said:
Power and Volume down
Click to expand...
Click to collapse
Yeah.. Doesn't do anything but take a screenshot than it just sits there.. Wtf
egren58 said:
Yeah.. Doesn't do anything but take a screenshot than it just sits there.. Wtf
Click to expand...
Click to collapse
Sorry should have added this is during the boot up stage..here is a copy & paste I keep handy:
While the device is powered off, press and hold Vol - and Power button. When you see the LG logo quickly release only the power button and re-press and hold the power button (Never let go of the Vol - button) This will boot you into the LG Factory reset screen. ONLY USE THIS METHOD IF YOU HAVE TWRP INSTALLED!!!!! OTHERWISE YOU WILL FACTORY RESET YOUR DEVICE!!!!! Choose yes to both options and you will be rebooted into TWRP. TWRP intercepts this command and ignores the factory reset part.
xDEMON87x said:
https://www.youtube.com/watch?v=fZEL96MPLvY , follow this guide..
Click to expand...
Click to collapse
When you state follow this guide ( i have to say the LG dev community is kinda of rude and does not even explain anything to new comers from other devices...) Do you mean i need to follow every step or some steps this is why i say the LG Dev community is all over the place nothing is set in stone there is not one way to do like most Samsung users are used to. I would hope that you could elaborate a little more if you are offering to help.
I am not trying to be a jerk i'm just use to nicer dev community. I have done dev work... I have not had any other device besides Samsung for the longest time and i and will be switching back once the S8 or note 8 comes out.
To get me but i would like to root this device and i would like more then a point here to do it because you don't have some time to explain what needs to be done....
Again i am not trying to be rude just trying to learn the process on the LG dev side... Do not want to brick my device if i can prevent it.
ice5192 said:
When you state follow this guide ( i have to say the LG dev community is kinda of rude and does not even explain anything to new comers from other devices...) Do you mean i need to follow every step or some steps this is why i say the LG Dev community is all over the place nothing is set in stone there is not one way to do like most Samsung users are used to. I would hope that you could elaborate a little more if you are offering to help.
I am not trying to be a jerk i'm just use to nicer dev community. I have done dev work... I have not had any other device besides Samsung for the longest time and i and will be switching back once the S8 or note 8 comes out.
To get me but i would like to root this device and i would like more then a point here to do it because you don't have some time to explain what needs to be done....
Again i am not trying to be rude just trying to learn the process on the LG dev side... Do not want to brick my device if i can prevent it.
Click to expand...
Click to collapse
Yes every step i am new as well and i got to say this was the most complex toot i have ever done. But every single comand bust be typed.. Ignore the $ sign. Install sdk not the smaller version of adb.
Hi All,
My wife is headed to Italy at the end of the month, and I purchased an unlocked Verizon VS995 V20 off ebay for her.
She is running a stock ROM Galaxy Note 2 (she likes things the way they are on KitKat , but that's another story ).
I've rooted Samsung, HTC and Moto phones in the past, but this is my first LG. From what I can tell, the V20 is a solid phone!
I tried looking online but am not finding clear answers yet, so here's my basic questions:
1. since the phone is supposedly unlocked, is there a specific ADB command I can use to verify it? Or should I go through a root process to be sure?
2. we are on T-Mobile, so I'd like to go to a stock AOSP Android 7 ROM with no carrier bloat. If the phone is unlocked, or if I do root, would there be any issues since this is a Verizon-branded phone?
3. not trying to start any bickering, but any recommendations for a stock vanilla Nougat ROM?
My phone info:
Build # NRD90M
Config ver B26.LGE.VS995.0
Software ver VS99513A
I appreciate any replies and thoughts, and I'm looking forward to seeing what this phone can do!
regards,
motionmonk
First, this post belongs in the Q&A section, hopefully a mod will move it.
Second, what security patch version are you on. It is listed in software info. If it is anything later than Dec 2016, then you can't root (yet).
My apologies to the Mods; I wasn't sure which section this should go in.
The Security Patch Level is dated Dec 1, 2016. Would that still work?
Wrong thread
Yes, you can root. Before you do, find the patched LG UP thread and do a dump of your entire phone. If you ever want to go back to stock, you will have the files. Also, it is good to have a full backup of your phone as it currently is.
I don't have a VS995, but I am willing to offer all the help I can.
-- Brian
runningnak3d said:
Yes, you can root. Before you do, find the patched LG UP thread and do a dump of your entire phone. If you ever want to go back to stock, you will have the files. Also, it is good to have a full backup of your phone as it currently is.
I don't have a VS995, but I am willing to offer all the help I can.
-- Brian
Click to expand...
Click to collapse
Thank you very much for the offer of help. It's sincerely appreciated.
I have some more research to do today, and then I'll reach out with more specifics.
And to all, sorry for posting in the wrong area... it looks like the Mods moved this to the Q&A area overnite.
-motionmonk
Ok, I think I have everything now.
I am using the Dirty Santa setup, and have installed the Terminal Emulator to the V20, loaded the twrp image to my SD card, and have the Required Files from the c20-root.zip loaded on the desktop.
Inside Win7 I installed the minimal package for ADB and Fastboot, and then connected the V20 as a device. Double-clicking on RUNMEFIRST.bat briefly shows a window, but it auto closes itself. I tried running the adb shell and doing "adb devices", but nothing is showing up. Doing adb logcat says it's waiting for devices too.
I feel I've already missed a step...
You enabled USB debugging?
runningnak3d said:
You enabled USB debugging?
Click to expand...
Click to collapse
Interesting... no, it's greyed out. I did the 7x tap to get Developer Options before I started, and thought I had checked it.
I have the phone set for File Transfer when connected to the Computer... but I don't think that would effect this setting.
Any ideas?
motionmonk said:
Interesting... no, it's greyed out. I did the 7x tap to get Developer Options before I started, and thought I had checked it.
I have the phone set for File Transfer when connected to the Computer... but I don't think that would effect this setting.
Any ideas?
Click to expand...
Click to collapse
The USB mode setting has no effect on adb. Also how is it greyed out? Can't say I've ever heard of something like that before.
Thisisabadname said:
The USB mode setting has no effect on adb. Also how is it greyed out? Can't say I've ever heard of something like that before.
Click to expand...
Click to collapse
I certainly can't claim to know much about this process, but I've never seen it before either on any other phone I've rooted.
I'll try and upload a shot of the Developer Option screen to this msg. I haven't done that yet here.
Weird, huh?
motionmonk said:
I certainly can't claim to know much about this process, but I've never seen it before either on any other phone I've rooted.
I'll try and upload a shot of the Developer Option screen to this msg. I haven't done that yet here.
Weird, huh?
Click to expand...
Click to collapse
Did you try unplugging it before trying to turn it on? It might be blocked cause it's currently connected
Thisisabadname said:
Did you try unplugging it before trying to turn it on? It might be blocked cause it's currently connected
Click to expand...
Click to collapse
I think I understand what you are asking...
-disconnect phone from computer
-restart phone
-reboot Windows
-phone is up; check Dev Options-- no joy.
-connect phone to Windows, VS995 is recognized. Type adb devices... nothing listed.
Latest Update
<I messed up this post, so I'd like to take it back>
While booted into the OS, you have to authorize it. Plug in the USB cable, and a prompt will come up.
Can't open /system
Ok, I'm stuck on Step 1 (which is farther than I've been till now; don't laugh)...
Just before the start of Step2.bat instructions, I need to applypatch after checking with Terminal Emulator that I have an untrusted_app.
I copy/pasted the applypatch instructions, and it reports:
elsa:/ # applypatch /system/bin/atd /storage/emulated/0/dirtysanta
could not open /system/bin/atd
This one I can't figure out. Have I missed something?
Install a terminal on your phone. That command goes into a terminal on your phone, not on your PC.
Ack. It even says so
I started Step2, and as a Verizon phone, the vibrator is going off, which is recognized in the instructions.
How long does Step2 take? I've been going for almost an hour.
On Terminal Emulator, it reports:
[1140] Fastboot mode started
Does your PHONE say fastboot? It should not take more than a few minutes.
-- Brian
runningnak3d said:
Does your PHONE say fastboot? It should not take more than a few minutes.
-- Brian
Click to expand...
Click to collapse
I thought I sent a reply but I guess it didn't go through.
-Yes, the Phone screen does say FASTBOOT MODE in Red, then multiple spec lines of Product Name, HW Version, Serial number, then at the end it says [1140] Fastboot mode started.
Back from lunch. Should I pull the battery and restart from Step1? Or can I continue from Step2?
I don't know why the root is so confusing for me. Thank you again for all your help Brian!
UPDATE -- ISSUE RESOLVED
*** New OTA available ***
See links below
Updated zip confirmed working here:
https://plus.google.com/100708818877715770270/posts/dEyVgqmURw2
Android Beta Program:
https://g.co/androidbeta
OTA Download:
NEW (fixes both OTA and sideload failures)
https://ota.googlezip.net/packages/.../1c0e174d9aeefbb176b4dd38b48270a0fd4082d9.zip
pangolin.rollin said:
For those experiencing issues updating to 8.1 on locked n stock f/w there is now a fix!!!
Source and Credit goes to "AC" : [url]https://issuetracker.google.com/issues/68264793[/URL]
See post #64 and #71
FIX SUMMARY
1. Enroll in beta ota
2. Download ota
3. Enable Developer mode
4. When update screen says "Reboot to update" DON'T click it but rather issue "adb reboot recovery"
5. Once in bootloader go to recovery like normal and ensure it says recovery 8.1
6. You may then enable update from adb for sideload.
7. When pixel is in ready to receive update issue "adb sideload <update.zip>"
8. Profit
Android Beta Program:
https://g.co/androidbeta
OTA Download:
[url]https://ota.googlezip.net/packages/ota-api/google_sailfish_sailfish/42c4425cf03125fe7c535e39cbac7d17c1a2f65a.zip[/URL]
Please post your success stories or issues.
I was on OPR3.170623.008 when this was done.
Click to expand...
Click to collapse
Credit goes to @ACastanza ,
Here is the mentioned fix by him/her : https://forum.xda-developers.com/showpost.php?p=74331289&postcount=51
Although i commend you trying to summarize the steps, they are wrong
adb reboot recovery is not a valid command ; i believe what you meant was
Code:
adb reboot bootloader
And i am not sure about this, but i think turning on developer mode is entirely optional.
NoobInToto said:
Credit goes to @ACastanza ,
Here is the mentioned fix by him/her : https://forum.xda-developers.com/showpost.php?p=74331289&postcount=51
...
And i am not sure about this, but i think turning on developer mode is entirely optional.
Click to expand...
Click to collapse
Oops yeah updated to bootloader, hadn't seen the post before or anything on XDA. Been following the normal circles. Can't hurt to spread the news!
The whole reason for suggesting the "optional" part of developer mode is cause if you try just the regular reboot /key press combo and miss it you have to redo the OTA download which is rather annoying. Rather just remove that possibility.
NoobInToto said:
Credit goes to @ACastanza ,
Here is the mentioned fix by him/her : https://forum.xda-developers.com/showpost.php?p=74331289&postcount=51
Although i commend you trying to summarize the steps, they are wrong
adb reboot recovery is not a valid command ; i believe what you meant was
Code:
adb reboot bootloader
And i am not sure about this, but i think turning on developer mode is entirely optional.
Click to expand...
Click to collapse
adb reboot recovery is definitely a valid command (assuming you're running a current version of ADB).
Enabling developer mode was not part of my original post, I don't think it is required, but then I was running it anyway. Entering recovery through a command rather than having to catch it at exactly the right moment with the key command is definitely easier, but I hadn't tested it that way when I did this originally. Glad this works too, it's much easier.
Also, glad people are finding this useful!
pangolin.rollin said:
Oops yeah updated to bootloader, hadn't seen the post before or anything on XDA. Been following the normal circles. Can't hurt to spread the news!
The whole reason for suggesting the "optional" part of developer mode is cause if you try just the regular reboot /key press combo and miss it you have to redo the OTA download which is rather annoying. Rather just remove that possibility.
Click to expand...
Click to collapse
Ah, now I get it. I forgot you needed usb debugging for adb when booted in system.
Anyways, booting in bootloader mode was easy, it is very hard to miss. One has to press power+volume down immediately after first bootloop, when the screen is back, and i was able to get into bootloader mode within 1 second.
---------- Post added at 05:11 AM ---------- Previous post was at 05:09 AM ----------
ACastanza said:
adb reboot recovery is definitely a valid command (assuming you're running a current version of ADB).
Enabling developer mode was not part of my original post, I don't think it is required, but then I was running it anyway. Entering recovery through a command rather than having to catch it at exactly the right moment with the key command is definitely easier, but I hadn't tested it that way when I did this originally. Glad this works too, it's much easier.
Also, glad people are finding this useful!
Click to expand...
Click to collapse
I had checked adb reboot recovery when booted in system. It did not work in 8.0.0.
Woops, I only read the first part of your post. Nevermind.
NoobInToto said:
I had checked adb reboot recovery when booted in system. It did not work in 8.0.0.
Click to expand...
Click to collapse
Your right it doesn't work in 8.0. That's why I specified to do it when it says "reboot to update" because when the system "pre-loads" the OTA it switches the active boot slot for next reboot. That's why doing it this way works as well.
ACastanza said:
Woops, I only read the first part of your post. Nevermind.
Click to expand...
Click to collapse
Huh? lol..
Anyways man didn't mean to steal your thunder. Just glad we're on 8.1.
You're the best! :good:
pangolin.rollin said:
Huh? lol..
Anyways man didn't mean to steal your thunder. Just glad we're on 8.1.
You're the best! :good:
Click to expand...
Click to collapse
No worries! Just glad people are getting updated without needing to factory reset.
(ADB rebot recovery actually does work on 8.0 but you need to have adb debugging enabled and need a new-ish version of the ADB binary).
ACastanza said:
No worries! Just glad people are getting updated without needing to factory reset.
(ADB rebot recovery actually does work on 8.0 but you need to have adb debugging enabled and need a new-ish version of the ADB binary).
Click to expand...
Click to collapse
Oh, yeah, the latest one not only has reboot recovery, but direct reboot to sideload options too....sweet
Btw there is a second workaround. It involves adb sideloading the same build (8.0.0) and then sideloading the Dev preview.
This worked for me. Looked like it was bootlooping again at first, but eventually booted into 8.1.0. Thanks!
invisibro said:
This worked for me. Looked like it was bootlooping again at first, but eventually booted into 8.1.0. Thanks!
Click to expand...
Click to collapse
Yup, strangely enough, that is the expected behavior for this workaround. @pangolin.rollin should include info about it in the OP post.
What am I missing here? I enrolled in the beta (Verizon locked bl) yesterday and within about an hour I had a notification to update to the beta. I clicked download and install and on the reboot I was running 8.1. What's all this about bootlooping, slots, rebooting bootloader? I did none of that and it worked flawlessly.
NoobInToto said:
Yup, strangely enough, that is the expected behavior for this workaround. @pangolin.rollin should include info about it in the OP post.
Click to expand...
Click to collapse
Updated op thanks
** Fixes "parse error -22" and update not installed, while this works first boot looks like it's looping. **
bobby janow said:
What am I missing here? I enrolled in the beta (Verizon locked bl) yesterday and within about an hour I had a notification to update to the beta. I clicked download and install and on the reboot I was running 8.1. What's all this about bootlooping, slots, rebooting bootloader? I did none of that and it worked flawlessly.
Click to expand...
Click to collapse
Your lucky then! Not sure of the official cause of the errors and why some work and some don't. But seems some devices have issues verifying. That's why Google even pulled ota images.
So I presume that the only problems were with sideloading? I never do that on my Pixel since I just like it updating in the background, reboot and done. With a locked bootloader I can't take a chance of doing something wrong. If they send me an image or OTA that bootloops then it's not my problem and they have to either fix it or replace it. Nonetheless, it's working very well and the reboot wasn't long at all. Might be the better way to go.
I did this fix and although it did work, now when I wake the device back up it takes a long time to do so. Double tapping the screen doesn't work at all, and when I hit the power button it takes about 5 seconds before the screen turns on. I'm going to try to sideload the ota again and see if it fixes it.
EDIT: Nope, still having the same issue
cred05 said:
I did this fix and although it did work, now when I wake the device back up it takes a long time to do so. Double tapping the screen doesn't work at all, and when I hit the power button it takes about 5 seconds before the screen turns on. I'm going to try to sideload the ota again and see if it fixes it.
EDIT: Nope, still having the same issue
Click to expand...
Click to collapse
Haven't heard of this problem yet.. were you on stock OPR3 with locked bootloader?
There is a new OTA (for same build, but new working OTA) for 8.1 rolling out.
https://plus.google.com/100708818877715770270/posts/dEyVgqmURw2
Please can someone grab the OTA URL?
Settings > System > Developer Options > Take Bug Report > Full Bug Report, then email it to yourself (or PM it to me) and search for the URL ending with ".zip".
I don't have a sailfish device on me right now to do it myself. Thanks!
Edit: here it is
https://ota.googlezip.net/packages/.../1c0e174d9aeefbb176b4dd38b48270a0fd4082d9.zip
pangolin.rollin said:
Haven't heard of this problem yet.. were you on stock OPR3 with locked bootloader?
Click to expand...
Click to collapse
I was on stock 8.0 OTA, locked bootloader. The issue seemed to have gone away by itself. Very strange