I whipped up something quick based of stuff I used to do with the Droid X and what the Sony SP guys did.
This is twrp with a locked bootloader, the recovery partition is untouched, you can still get into that recovery. When the phone is booting, a green light will come on, hit volume up and then phone should vibrate within 3 seconds. If you hit the volume up then it should start loading twrp, otherwise it should continue with booting.
This is untested and I have a feeling the system will either not boot recovery, or not boot the main system.
This needs root.
This installs busybox, i know i should be using toybox
Someone please test, just extract the zip to your computer, plug in your phone, and run the appropriate file.
Do not test, I've tested it and I need to make changes
Sorry I was busy creating a new root method, got it working, almost done
Aaahh said:
I whipped up something quick based of stuff I used to do with the Droid X and what the Sony SP guys did.
This is twrp with a locked bootloader, the recovery partition is untouched, you can still get into that recovery. When the phone is booting, a green light will come on, hit volume up and then phone should vibrate within 3 seconds. If you hit the volume up then it should start loading twrp, otherwise it should continue with booting.
This is untested and I have a feeling the system will either not boot recovery, or not boot the main system.
This needs root.
This installs busybox, i know i should be using toybox
Someone please test, just extract the zip to your computer, plug in your phone, and run the appropriate file.
Click to expand...
Click to collapse
I need root to install it? Because marshmallow its unrootable
ericperez380 said:
I need root to install it? Because marshmallow its unrootable
Click to expand...
Click to collapse
Yup, in the future I might be able to make a marshmallow zip that'll let you run marshmallow with root and twrp. For that I need to relook into kernel modules because the kernel would have to be reloaded.
Aaahh said:
Yup, in the future I might be able to make a marshmallow zip that'll let you run marshmallow with root and twrp. For that I need to relook into kernel modules because the kernel would have to be reloaded.
Click to expand...
Click to collapse
Damn man you're a beast in does things good job doing this TWRP for locked bl, I'll be waiting till some feedback about this working
ericperez380 said:
Damn man you're a beast in does things good job doing this TWRP for locked bl, I'll be waiting till some feedback about this working
Click to expand...
Click to collapse
Yeah this opens the avenue for custom roms too, and multiboot and tons of stuff. Also, do not flash this if you are encrypted.
Aaahh said:
Yeah this opens the avenue for custom roms too, and multiboot and tons of stuff. Also, do not flash this if you are encrypted.
Click to expand...
Click to collapse
What you mean about encrypted, I don't know what's that
ericperez380 said:
What you mean about encrypted, I don't know what's that
Click to expand...
Click to collapse
If you encrypted your device. If you did you know.
Aaahh said:
If you encrypted your device. If you did you know.
Click to expand...
Click to collapse
No I don't encrypted it
Im at work.. Will Try to test it at home.
In between im bit confused how to flash this
Hopefully this will allow for us to write the drivers that would allow us to unlock the band's that are locked. If this allows us to write drivers.
So, just extract and run install.bat? On normal mtp mount?
Aaahh said:
I whipped up something quick based of stuff I used to do with the Droid X and what the Sony SP guys did.
This is twrp with a locked bootloader, the recovery partition is untouched, you can still get into that recovery. When the phone is booting, a green light will come on, hit volume up and then phone should vibrate within 3 seconds. If you hit the volume up then it should start loading twrp, otherwise it should continue with booting.
This is untested and I have a feeling the system will either not boot recovery, or not boot the main system.
This needs root.
This installs busybox, i know i should be using toybox
Someone please test, just extract the zip to your computer, plug in your phone, and run the appropriate file.
Click to expand...
Click to collapse
does it work with (vs986) version model
I'm interested to see if this works for the Canadian model (H812). Will keep watching this thread so good luck!
So the hope here is that we could downgrade to L, root, and then run this to get TWRP and install custom roms all without touching the recovery partition?
Has anyone had a chance to test this? I have a VS986 but it's the only phone I have with me right now so I'm hesitant to try myself
recharged20 said:
So, just extract and run install.bat? On normal mtp mount?
Click to expand...
Click to collapse
Yeah uses adb
ANDROID2468 said:
does it work with (vs986) version model
Click to expand...
Click to collapse
It should work with all G4s, exception might be T-Mobile
ReeS86 said:
I'm interested to see if this works for the Canadian model (H812). Will keep watching this thread so good luck!
Click to expand...
Click to collapse
Yeah it should, in fact it may work on yours but not the Verizon because I used the twrp from the international. Easy fix tho if that's the caw
Wumbonaut said:
So the hope here is that we could downgrade to L, root, and then run this to get TWRP and install custom roms all without touching the recovery partition?
Has anyone had a chance to test this? I have a VS986 but it's the only phone I have with me right now so I'm hesitant to try myself
Click to expand...
Click to collapse
Yeah I'm in the same predicament.
coolguy71261 said:
Hopefully this will allow for us to write the drivers that would allow us to unlock the band's that are locked. If this allows us to write drivers.
Click to expand...
Click to collapse
No that probably won't be as the drivers are probably locked at bootloader level not system
Wait. I'm confused.
Q: does it work with (vs986) version model
A: It should work with all G4s, exception might be T-Mobile
Q: I'm interested to see if this works for the Canadian model (H812). Will keep watching this thread so good luck!
A: Yeah it should, in fact it may work on yours but not the Verizon because....
Soooo - it should work with the verizon G4 or it shouldn't?
Aaahh said:
I whipped up something quick based of stuff I used to do with the Droid X and what the Sony SP guys did.
This is twrp with a locked bootloader, the recovery partition is untouched, you can still get into that recovery. When the phone is booting, a green light will come on, hit volume up and then phone should vibrate within 3 seconds. If you hit the volume up then it should start loading twrp, otherwise it should continue with booting.
This is untested and I have a feeling the system will either not boot recovery, or not boot the main system.
This needs root.
This installs busybox, i know i should be using toybox
Someone please test, just extract the zip to your computer, plug in your phone, and run the appropriate file.
Click to expand...
Click to collapse
I ran this with a Verizon G4 and it doesn't appear to work. I don't get a green light when I boot up nor does pressing the Vol Up button at any point during boot up appear to have any affect. Perhaps I'm missing something in order to get into TWRP but from what I can tell it does not work.
One other note, the batch file for the windows installation needs to be edited: In this section PUSH needs to be changed to INSTALL. Not sure it matters if it doesn't work overall but wanted to let the you know.
USH <------- Should be INSTALL
@ECHO Let's go!
@adb\adb kill-server
@adb\adb wait-for-device
@adb\adb push common\logwrapper /data/local/tmp/
@adb\adb push common\twrp.cpio.gz /data/local/tmp/
@adb\adb push common\busybox /data/local/tmp/
@adb\adb push common\step1.sh /data/local/tmp/
@adb\adb shell chmod 755 /data/local/tmp/step1.sh
@adb\adb shell su -c "mount -o remount,rw /system"
@adb\adb shell su -c /data/local/tmp/step1.sh
@adb\adb shell rm /data/local/tmp/step1.sh
@pause
@goto MENU
shmoode1 said:
I ran this with a Verizon G4 and it doesn't appear to work. I don't get a green light when I boot up nor does pressing the Vol Up button at any point during boot up appear to have any affect. Perhaps I'm missing something in order to get into TWRP but from what I can tell it does not work.
One other note, the batch file for the windows installation needs to be edited: In this section PUSH needs to be changed to INSTALL. Not sure it matters if it doesn't work overall but wanted to let the you know.
USH <------- Should be INSTALL
@ECHO Let's go!
@adb\adb kill-server
@adb\adb wait-for-device
@adb\adb push common\logwrapper /data/local/tmp/
@adb\adb push common\twrp.cpio.gz /data/local/tmp/
@adb\adb push common\busybox /data/local/tmp/
@adb\adb push common\step1.sh /data/local/tmp/
@adb\adb shell chmod 755 /data/local/tmp/step1.sh
@adb\adb shell su -c "mount -o remount,rw /system"
@adb\adb shell su -c /data/local/tmp/step1.sh
@adb\adb shell rm /data/local/tmp/step1.sh
@pause
@goto MENU
Click to expand...
Click to collapse
It should not be install it should be push.
Did you use install or push
Does your phone still boot?
I had to guess the led paths so they may be wrong
It made a log, I'll send you the path of it on your phone so you can send it to me
Aaahh said:
It should not be install it should be push.
Did you use install or push
Does your phone still boot?
I had to guess the led paths so they may be wrong
It made a log, I'll send you the path of it on your phone so you can send it to me
Click to expand...
Click to collapse
I used install, otherwise when I tried to install it, Option 1, the CMD window just closed. When I changed it to Install it ran and showed TWRP Successfully installed.
Yes it still boots.
Let me know the path, I'll send the log file.
Related
This is an exploit, I take NO RESPONSIBILITY if this does ANYTHING bad, your fault not mine, it was only tested on the firmware mentioned below. If you redistribute it, republish, work it into a all in one click, please link back and PROPERLY credit me.
Tested on the
ro.build.date=Mon Jan 30 10:42:53 KST 2012
ro.build.version.incremental=ZV9.479A6632
Update for the VirginMobile LG Optimus V
Your phone needs to be updated to the above build, and potentially needs a factory reset before this works, but it works fine. This will allow you to flash recovery without being root. After flashing recovery, flash this zip http://dl.dropbox.com/u/8699733/rootme.zip to install su, superuser and disable re-flashing of the stock re covery
LinuxMac Script + files:
https://github.com/CunningLogic/GorditaRoot
Flash_image:
https://github.com/CunningLogic/GorditaRoot/blob/master/flash_image
Recovery:
http://www.mediafire.com/?vzc5k8taj9smmll (Credit BobZhome)
Windows users run the commands manually
GNU nano 2.2.2 File: Gordita.sh
Code:
#!/bin/sh
echo "GorditaRoot 1.0 by jcase / TeamAndIRC"
echo "for the VM670 Optimus V"
echo "March 21st 2012"
echo "Follow me! http://www.twitter.com/TeamAndIRC"
echo "Donations are optional http://forum.xda-developers.com/donatetome.php?u=2376614"
echo "-"
echo "Recovery taken from http://forum.xda-developers.com/showthread.php?t=1197991"
echo "-"
echo "Pushing recovery to /data/local/"
adb push VM670NH_recovery.img /data/local/recovery.img
adb push flash_image /data/local/
adb shell "chmod 755 /data/local/flash_image"
echo "Removing old sensor config, setting up symlink attack"
adb shell "rm /data/amit/*"
adb shell "ln -s /dev/mtd/mtd2 /data/amit/AMI304_Config.ini"
adb shell "ln -s /dev/mtd/mtd2 /data/amit/AMI304_Config2.ini"
echo "Rebooting to execute symlink attack, to chmod 666 the recovery block device"
adb reboot
adb wait-for-device
sleep 10
adb shell "rm /data/amit/*"
adb shell "/data/local/flash_image recovery /data/local/recovery.img"
echo "Recovery flashed! Enjoy"
Having trouble identifying whether or not you completed the root process? Quickly test for root access with Root Checker Basic
Confirmed working on a phone donated just for this purpose!
Started with stock firmware, Android 2.2.1, baseband VM670ZV4_60401001, generic android recovery
Flashed the VirginMobile Security Update from their website, became VM670ZV9_60401001 ZV9.479A6632
Manually walked through above script by jcase via gtalk, and using the exploit, was able to flash BobZhome's CWM for the VM670, reboot into it and made a backup.
Flashed the su zip, and all is well in Optimus V land again.
HUGE THANKS TO JCASE FOR TAKING THE TIME TO RE-ROOT THE VM670!!!
I only wish I understood what it all meant--so I could be excited, too!
wilberfan said:
I only wish I understood what it all meant--so I could be excited, too!
Click to expand...
Click to collapse
Means ppl who couldnt root before, now can
wilberfan said:
I only wish I understood what it all meant--so I could be excited, too!
Click to expand...
Click to collapse
i was gonna ask the same thing LOL
Hey! Sorry, I'm a ET4G user, just trying to put ICS on my girl's phone so she stops whining
Anyways, I presume there's an update being pushed to all optimus v's? If so would you happen to know how I could update hers? Or would it be easier to stay on the current version ( i belive v5???) and root a different way??
Also, great work on an exploit so soon after a release! Happy to join (kinda) the Optimus family!
jlear3 said:
Hey! Sorry, I'm a ET4G user, just trying to put ICS on my girl's phone so she stops whining
Anyways, I presume there's an update being pushed to all optimus v's? If so would you happen to know how I could update hers? Or would it be easier to stay on the current version ( i belive v5???) and root a different way??
Also, great work on an exploit so soon after a release! Happy to join (kinda) the Optimus family!
Click to expand...
Click to collapse
The update is not being pushed, because the OTA mechanism doesn't work on the OV. You have to go to the VM website and download the update from the phone FAQ.
The only advantage is a new radio, which give slightly improved performance.
Thank you very much!
I installed the update to my (unmodded) backup phone without thinking about whether or not I'd be able to root the handset after applying it. DOH!
I have just been using this phone as a WiFi device so far. I have run the battery down and recharged it once and installed a few apps on it. So I will run it down, recharge it again and then do a factory reset before I try rooting it just to make sure that I don't hose it.
It's a good idea to check all the steps before you start ...
Finally ran my battery down for the second time. So, I recharged, ran a factory re-set and ran the shell script on my Linux box to root the phone.
Oops!
The file VM670NH_recovery.img downloaded as VM670NH_recovery.bin and the system can't find/stat it! Hit ^C and bailed!
Hoping, hoping, hoping ...
Good! It's not bricked!
Renamed the recovery file, re-ran the script. Success!!
Rebooted into recovery, flashed rootme.zip
==> Did a nandroid backup.
Downloaded root check basic app and confirmed that it has worked.
So, for other modders trying this out:
Check your files and file names before you start! When I looked at Gordita.sh the first time I found that what I had downloaded was an HTML file with the script embedded in it. Copied and pasted from the OP and then checked again to make sure I had the right content.
Of course if you are running the adb commands manually then this won't happen to you.
But, as I noted above, I didn't cross-check that the recovery file that the script would be looking for had the right file name extension (.img, not .bin), so don't be me.
That said, jcase: Thank You Very Much!! Not only for developing this root exploit but also for making one that is robust enough for someone like me to goober it up and still come out unburnt!
After all of this , can you make it a hotspot in quick settings?
The setting dialog is there ..
H0daddy said:
After all of this , can you make it a hotspot in quick settings?
Click to expand...
Click to collapse
Once I rooted my phone I installed a modified ROM. And then another one, and then ...
I saw your question a bit ago and since I no longer had the stock ROM installed (and had never used Quick Settings to enable the hotspot feature before) I didn't know. I still don't. Here is the story on that ...
I just restored the ZV9 ROM from backup today and then installed the Quick Settings app. I can say that the app still has the option to enable the hotspot available and that it tries to set it up. However the phone I am using hasn't been activated yet and the 3G network isn't provisioned on it. So all I get is a message saying the network isn't available.
So, it looks somewhat promising. Maybe someone who has an activated phone with the ZV9 ROM can test it out and let you know.
And if I activate this phone before you get a useful reply I'll test it to see if it works.
So happy to see this
Please assist
Got up to step adb shell "chmod 755 /data/local/flash_image"
But got back "no such file."
CWM
Got up to CWM but it won't let me select install zip from sd card. Any suggestions?
knicks791 said:
Got up to CWM but it won't let me select install zip from sd card. Any suggestions?
Click to expand...
Click to collapse
so you have bobz recovery installed?... i assume youve tried rebooting to recovery form the powered off state via the key combo (HOLD home+vol down+power, RELEASE after the LG logo), and tried instal zip from sd again?...
try:
http://forums.projectopencannibal.net/beta-releases-11/lg-optimus-v-v2-1dev1-(10-09-2012)/
http://forums.projectopencannibal.n...1-universal-installer-for-lg-optimus-devices/
UPDATED 7-8-13
WHAT THIS TOOL DOES:
1.ROOTS YOUR GALAXY S4 (motochopper exploit created by djrbliss)
2. PREPS FOR RECOVERY
3. INSTALLS CWM OUDHS 1.0.3.4 (7/8) RECOVERY(credit to shabbypenguin)
4. INSTALLS TWRP 2.6.0.0 (credit to dees_troy)
5. Flash phone back to stock using odin
(Full Version Only)
#FOR AT&T I337 ONLY WARNING MADE#
Heres a pretty amateur video I threw together:
https://www.youtube.com/watch?v=NlK3r81kQPw&feature=youtube_gdata_player
Ive updated this to a 3 way all in one tool. Tool can root device (using motochopper by djrbliss) and install either cwm or twrp. Great tool for all those just getting started. Both CWM OUDHS 1.0.3.5 and TWRP 2.5.0.2 are auto loki. They will apply loki patch to all compatible roms and kernels flashed. You can also flash back to stock via Odin
##EDIT I HAVE RECEIVED VERIFICATION THAT TWRP WILL NOT AUTO PATCH. THIS CAME FROM DEES_TROY HIMSELF. IF YOU USE TWRP BE SURE TO FLASH A LOKI KERNEL AFTER ANY NON LOKI ROM FLASH##
A huge thanks to djrbliss for his genius
And huge thanks to dees_troy and shabbypenguin for the recoveries
Also thanks to mostyle for the script help
Instructions:
1. Download 3way tool zip
2. Unzip on desktop and open tool.
3. Connect I337 via usb with usb
debugging enabled.
4. Click Run_Me.bat select number for option you desire and enjoy!
Use this tool at your own risk. I am not responsible for any level of destruction to your phone blah blah blah
Downloads:
Full Version
https://mega.co.nz/#!o0dXHLoY!BNo2eFNQsuPN2-ivpVGo7Vk_V7ckHorY9WlK0PTqbSM
Slim Version (no odin to stock)
https://mega.co.nz/#!Q9FByZrD!CUK7RTDUzzzrH-n3rXjylhkOyy9B1gx9zHNfaKkbVJg
#EDIT# ADDED PREP FOR RECOVERY OPTION. WILL REMOVE KNOX APKS AND install-recovery.sh FOR YOU.Mirrors are welcome. Have a nice day! Dont forget to hit the THANKS button!
If youd like to buy me a beer:beer: I wont complain
Thanks for the beer:beer:list:
Scanss2k
LSUtigers03
O.K
I like to try it :fingers-crossed:
I installed the OUDHS Recovery yesterday and now either one of these will install.I'd love to have Loki'd TWRP. My phone has the same UCUAMDL
If you use either of these please let me know if it works for you.
Respond to sholsten
You mean Neither will work,
It didn't work on mine.
Ill recheck script when I get home. Worked on test devices prior to posting. Please post error messages here. ^^^^ already have yours
pakxelaos said:
Respond to sholsten
You mean Neither will work,
It didn't work on mine.
Click to expand...
Click to collapse
Neither seemed to have have installed on mine. It has the same one I installed in my above post yesterday.
sholsten said:
Neither seemed to have have installed on mine. It has the same one I installed in my above post yesterday.
Click to expand...
Click to collapse
What message did you get on tool after it ran
pakxelaos said:
Respond to sholsten
You mean Neither will work,
It didn't work on mine.
Click to expand...
Click to collapse
Did uninstall the recovery.sh file?
Fixed
On the line that issues the remount command there occurs 'Permission denied.'
In your batch file change line 25:
adb remount
Click to expand...
Click to collapse
so that it reads:
adb shell su -c "mount -o rw,remount /system"
Click to expand...
Click to collapse
Of course this assumes you are rooted..
EDIT:
Still getting an error 'Failed to open aboot for reading'
I'm investigating.. Hang on.
Will change and repost in a few
You could just install goomanger and install twrp thats been lokified directly from your rooted s4
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
bhp090808 said:
What message did you get on tool after it ran
Click to expand...
Click to collapse
Finished Rebooting into TWRP
Have a nice day!
adb is not recognized as an internal or external command, operable program or batch file.
Press any key to continue
Here's the fixed script..
Just had to su -c all of your commands...
db kill-server
adb start-server
adb shell su -c "mount -o rw,remount /system"
adb wait-for-device
adb push loki_flash /data/local/tmp
adb push openrecovery.lok /data/local/tmp
ECHO.
ECHO Doing the hard stuff.............
ECHO.
adb shell su -c "mount -o rw,remount /system"
adb shell su -c "chmod 755 /data/local/tmp/loki_flash"
adb shell su -c "./data/local/tmp/loki_flash recovery /data/local/tmp/openrecovery.lok"
Click to expand...
Click to collapse
Hope that helps. Tested it here and it works fine..
mostyle said:
Just had to su -c all of your commands...
Hope that helps. Tested it here and it works fine..
Click to expand...
Click to collapse
Will update and repost in a few thx
EDIT
Ok updated script new links are up let me know if its working for you now
MrPlNK said:
You could just install goomanger and install twrp thats been lokified directly from your rooted s4
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
How do you find the correct TWRP?
Just tried this with TWRP worked beautifully, thank you very much!! :good:
djoutrages said:
Just tried this with TWRP worked beautifully, thank you very much!! :good:
Click to expand...
Click to collapse
Make sure to thank mostyle for the script assist. Thanks bro
Tested both on my 32GB S4. Both working with no issues at all. Appreciate the work that went into this.
So if I understand this will allow you to flash a Rom that has not been Loki'd and it will loki it and allow it to boot with either TWRP or CWM?
Hello everyone!
Here's another release thread for y'all!
What is this?
This is a flashable TWRP recovery for the Optimus G Pro.
Special thanks to @djrbliss
You can safely flash this to your phone's recovery and enjoy modding bliss!
How do I use this, and where do I get it?
Good question!
There are two ways to use the files provided here.
To Flash to Recovery:
I've created an easy installer for all you Windows folks!
Download this: http://downloads.codefi.re/thecubed/lgoptimusg_pro/gkatt/recovery/e98010g/easy-twrp-e98010g.zip
Extract it to somewhere on your computer.
Enable USB debugging on your phone, if you need the drivers I've included them in the "files/drivers" folder in the zip
Run the 'install.bat' script.
Check for any errors, if it was successful, you can 'adb reboot recovery' or use an app on your phone to get you into TWRP now!
Profit! (and realize that this was pretty easy!)
(thanks to hkfriends for pointing out the errors in my script!)
OR..
Download this file to somewhere on your computer https://github.com/djrbliss/loki/raw/master/bin/loki_flash
Download this file http://downloads.codefi.re/thecubed/lgoptimusg_pro/gkatt/recovery/e98010g/gkatt-twrp-e98010g.lok
Run the following:
Code:
adb push loki_flash /data/local/tmp
adb push gkatt-twrp-e98010g.lok /data/local/tmp
abd shell
su
cd /data/local/tmp
chmod 755 loki_flash
./loki_flash recovery gkatt-twrp-e98010g.lok
To boot
Download this file: http://downloads.codefi.re/thecubed/lgoptimusg_pro/gkatt/recovery/e98010g/gkatt-twrp-e98010g.img
Use fastboot boot to boot it
DO NOT FLASH THE .IMG FILE TO YOUR PHONE. It is only meant for fastboot booting.
Where can I find the source you used to build this?
All on my github!
http://github.com/thecubed/
Or, follow my guide here:
http://forum.xda-developers.com/showthread.php?p=43514195
What can I do with this?
Right now, the possibilities are unlimited. Once a security-lax boot.img is released, we can flash that through recovery and let the modding commence.
Please remember though, modding /system with the stock boot.img will result in a security error!
What works, and what doesnt?
I have not tested external SD cards, since I don't have one with me at work.
I have also not tested backups or restores in TWRP yet.
Can you show me a video?
Why yes I can!
As usual, please pardon the crappy camera work.
I <3 you so much, how do I show my love?
You are so kind
I most definitely do not expect donations of any kind, however they are appreciated a lot.
I purchased this phone off-contract just to get it unlocked, if you are a kind soul and would like to send me a token of your appreciation I would love you forever.
XDA has a neat "Donate to me" button that should be on the left side of this page under my name. Donations go to purchasing new hardware to work on and other neat stuff, so they're always appreciated.
Special Thanks!
In no particular order, special thanks to all of you guys!
djrbliss
hkfriends
synergy
Shelnutt2
DeamonFish
If I forgot anyone, let me know and I'll add you here!
Alright guys! Let me know if you find any bugs!
This is killer, I love twrp. So this will just over flash the cwm currently added earlier of course correct? Awesome work m8:thumbup:
EDIT: Not sure why but the Loki flash file downloads as a. Txt file for me
Sent from my LG-E980 using Tapatalk 2
maybe i am doing something wrong, but when i get into twrp the touch does not work
Very nice work there
testing back up and restore now
rbf351 said:
maybe i am doing something wrong, but when i get into twrp the touch does not work
Click to expand...
Click to collapse
Touch doesn't work? You have the ATT version, right?
That'd be very strange if it didn't work because of something in my kernel... it's pretty much just stock...
sorry for the "newbie" question...but the file to download are getting to the phone right?
thecubed said:
Touch doesn't work? You have the ATT version, right?
That'd be very strange if it didn't work because of something in my kernel... it's pretty much just stock...
Click to expand...
Click to collapse
yup, AT&T version, but it happens when i type in adb reboot recovery
Everything works so far tried backing up restore flashing and external sd... very nice work I will keep playing to see if i find any bugs
rbf351 said:
yup, AT&T version, but it happens when i type in adb reboot recovery
Click to expand...
Click to collapse
That's weird... I've been testing with that exact command and it's not doing it.
Can you possibly pull the kernel logs and pastebin them?
Do this while you're booted in recovery:
Code:
adb shell
dmesg > /sdcard/twrp_kmsg.txt
[press ctrl-c after a few seconds]
adb pull /sdcard/twrp_kmsg.txt
Thanks!
thecubed said:
That's weird... I've been testing with that exact command and it's not doing it.
Can you possibly pull the kernel logs and pastebin them?
Do this while you're booted in recovery:
Code:
adb shell
dmesg > /sdcard/twrp_kmsg.txt
[press ctrl-c after a few seconds]
adb pull /sdcard/twrp_kmsg.txt
Thanks!
Click to expand...
Click to collapse
won't all me to do it, i get the following error
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
error: device not found
rbf351 said:
won't all me to do it, i get the following error
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
error: device not found
Click to expand...
Click to collapse
Can you check to ensure that you have the ADB driver installed for your system? It is possible that your desktop hasn't installed the ADB interface while the phone is in recovery mode.
Start -> devmgmt.msc [enter]
Look to see if you have any unknown devices or "Android Phone" entries with no driver installed. That should do the trick.
thecubed said:
Can you check to ensure that you have the ADB driver installed for your system? It is possible that your desktop hasn't installed the ADB interface while the phone is in recovery mode.
Start -> devmgmt.msc [enter]
Look to see if you have any unknown devices or "Android Phone" entries with no driver installed. That should do the trick.
Click to expand...
Click to collapse
i have the following
ADB Interface
Android Sooner Single ADB Interface
edit, that wasn't while i was in recovery mode
in recovery mode i have
other devices
LG-E980 with an exclamation
I was able to flash and get into recovery without any issues. Excellent work! Thecubed and djrbliss, you guys are awesome!
here is the pastebin
http://pastebin.com/XPYi0v44
rbf351 said:
here is the pastebin
http://pastebin.com/XPYi0v44
Click to expand...
Click to collapse
Here's an interesting question... if you flash CWM instead, and press the softkeys at the bottom of the phone (the normal back and menu buttons) does anything happen? It looks like your touchscreen is being brought up successfully (despite the "[ 8.270257 / 03-05 11:00:29.766] Reflash Completed. Please reboot." line)
If softkeys work in CWM, then it means that something in TWRP isn't registering your touchscreen right. I'll look into that, should be fairly straightforward.
If softkeys don't work in CWM... that means something more strange. That means my kernel (or the boot commands I'm using) aren't compatible with your phone... which is indeed possible, since there are many revisions of each phone. (I hope this isn't the case!)
thecubed said:
Here's an interesting question... if you flash CWM instead, and press the softkeys at the bottom of the phone (the normal back and menu buttons) does anything happen? It looks like your touchscreen is being brought up successfully (despite the "[ 8.270257 / 03-05 11:00:29.766] Reflash Completed. Please reboot." line)
If softkeys work in CWM, then it means that something in TWRP isn't registering your touchscreen right. I'll look into that, should be fairly straightforward.
If softkeys don't work in CWM... that means something more strange. That means my kernel (or the boot commands I'm using) aren't compatible with your phone... which is indeed possible, since there are many revisions of each phone. (I hope this isn't the case!)
Click to expand...
Click to collapse
CWM works perfectly, i can navigate through all the menus using the softkeys
TWRP working perfectly here for me also! thank you for this! :good:
verry nice work........would be nice to have a kind od "how to" when thing get all set.....:good:
Uhmm there is a how to..
Sent from my LG-E980 using xda premium
Gotroot said:
Uhmm there is a how to..
Sent from my LG-E980 using xda premium
Click to expand...
Click to collapse
yeah ...but i have all the file....does i have to put the phone in download mode??
http://android.clients.google.com/p...ned-metallica-LWX48P-from-KNX01S.98cdf4ca.zip
to update:
Go into a shell on the watch with su and...
mount -o rw,remount /dev/block/mmcblk0p15 /cache
mv /sdcard/98cdf4ca90c4693edd379d67cdcf86e283058b81.signed-metallica-LWX48P-from-KNX01S.98cdf4ca.zip /cache/98cdf4ca90c4693edd379d67cdcf86e283058b81.signed-metallica-LWX48P-from-KNX01S.98cdf4ca.zip
echo 'boot-recovery ' > /cache/recovery/command
echo '--update_package=/cache/98cdf4ca90c4693edd379d67cdcf86e283058b81.signed-metallica-LWX48P-from-KNX01S.98cdf4ca.zip' >> /cache/recovery/command
echo '--wipe_cache' >> /cache/recovery/command
echo 'reboot' >> /cache/recovery/command
reboot recovery
Nice ty
See above
abuttino said:
See above
Click to expand...
Click to collapse
I was trying to do it thought ADB I'm just new to this and I ended up re posting in the wrong thread.
Im Not new to flashing via recover on phones but on adb through commands I always feel sketchy about it.
I keep getting permission denied
Ive ran root a few times I have the drivers install right for sure not sure what im doing wrong
NUGZZ420 said:
I keep getting permission denied
Ive ran root a few times I have the drivers install right for sure not sure what im doing wrong
Click to expand...
Click to collapse
Throw an "su" command in the shell before anything else. It will only work if you're rooted.
I don't really get it how to connect via shell to my watch. Is it the same as installing apk's over adb bluetooth debugging bridge?
Could you provide further instructions how to install the update manually?
Thanks!
Kamekazegoldi said:
I don't really get it how to connect via shell to my watch. Is it the same as installing apk's over adb bluetooth debugging bridge?
Could you provide further instructions how to install the update manually?
Thanks!
Click to expand...
Click to collapse
Is your watch rooted? If not, you can't do it
No further questions thanks!
abuttino said:
http://android.clients.google.com/p...ned-metallica-LWX48P-from-KNX01S.98cdf4ca.zip
to update:
Go into a shell on the watch with su and...
mount -o rw,remount /dev/block/mmcblk0p15 /cache
mv /sdcard/98cdf4ca90c4693edd379d67cdcf86e283058b81.signed-metallica-LWX48P-from-KNX01S.98cdf4ca.zip /cache/98cdf4ca90c4693edd379d67cdcf86e283058b81.signed-metallica-LWX48P-from-KNX01S.98cdf4ca.zip
echo 'boot-recovery ' > /cache/recovery/command
echo '--update_package=/cache/98cdf4ca90c4693edd379d67cdcf86e283058b81.signed-metallica-LWX48P-from-KNX01S.98cdf4ca.zip' >> /cache/recovery/command
echo '--wipe_cache' >> /cache/recovery/command
echo 'reboot' >> /cache/recovery/command
reboot recovery
Click to expand...
Click to collapse
Worked (almost) perfect! Except, the "mv" command caused it to error out with "Invalid Arguement:Cross-Device Link" (Due to the implementation of blocked cross device linking with the mv command, bypassable by just cp'ing) Just replaced it with "cp" and the problem was solved.
Though this has already been said, the 4.4w1 insecure boot.img no longer roots 5.0.1. Probably due to incompatibilliuies, I'll work up a new rooted boot.img this weekend. Sadly looks like its going to require flashing the boot.img, not just booting it.
How do you go on a shell on your watch?
You have to have the bootloader unlocked and rooted hooked up via Modded USB cable. Then use the super tool script iin the dev section to install drivers for fastboot. Then back out to that folder make sure you not clicked on anything right click anywhere I think but I right click on the fastboot file while holding the SHIFT key and open in command window the type adb devices to make sure you hooked up right and you have accepted it on your phone Witch you must click accept the adb on your phone to accept the computer access. Once you know your hooked up right type adb shell and boom there you go.
having some trouble.
I've got shell, and then su, i've got a prompt with #
Tried the mv command, and like that other guy, got a cross link error. So i tried cp instead of mv, and now get no such file or directory...
I should mention I'm doing this from adb on Windows. Am I missing something??
Prfndhatrdofman said:
having some trouble.
I've got shell, and then su, i've got a prompt with #
Tried the mv command, and like that other guy, got a cross link error. So i tried cp instead of mv, and now get no such file or directory...
I should mention I'm doing this from adb on Windows. Am I missing something??
Click to expand...
Click to collapse
Try this its what worked for me
coming from KNX01S, but I keep running into "Status 7" with the stock recovery and "Error executing updater script" with TWRP. Anybody have any better luck flashing this?
SOLVED!: I removed the get prop lines in the beginning of the update script and sideloaded in TWRP!
If anybody would like the modified package it can be found here: https://dl.dropboxusercontent.com/u/...360/update.zip
This was not my fix only copied and pasted
NUGZZ420 said:
Try this its what worked for me
coming from KNX01S, but I keep running into "Status 7" with the stock recovery and "Error executing updater script" with TWRP. Anybody have any better luck flashing this?
SOLVED!: I removed the get prop lines in the beginning of the update script and sideloaded in TWRP!
If anybody would like the modified package it can be found here: https://dl.dropboxusercontent.com/u/...360/update.zip
This was not my fix only copied and pasted
Click to expand...
Click to collapse
That Dropbox link seems to be down, do you still have that modified TWRP zip?
Found the original post, here's the original link: https://dl.dropboxusercontent.com/u/9407677/Moto 360/update.zip
Looks like the link text got shortened when copying/pasting, but it's all good now! Thanks for sharing!
Prfndhatrdofman said:
having some trouble.
I've got shell, and then su, i've got a prompt with #
Tried the mv command, and like that other guy, got a cross link error. So i tried cp instead of mv, and now get no such file or directory...
I should mention I'm doing this from adb on Windows. Am I missing something??
Click to expand...
Click to collapse
Make sure your using "/cache" instead of "/cache/"
nissanskylinebam said:
That Dropbox link seems to be down, do you still have that modified TWRP zip?
Found the original post, here's the original link: https://dl.dropboxusercontent.com/u/9407677/Moto 360/update.zip
Looks like the link text got shortened when copying/pasting, but it's all good now! Thanks for sharing!
Click to expand...
Click to collapse
Sorry I had been running all day and beat here my own just in case it helps same zip just my own link
5.0.1 update zip Mirror https://www.dropbox.com/s/naliirhnblh6ihg/update.zip?dl=0
npjohnson said:
Worked (almost) perfect! Except, the "mv" command caused it to error out with "Invalid Arguement:Cross-Device Link" (Due to the implementation of blocked cross device linking with the mv command, bypassable by just cp'ing) Just replaced it with "cp" and the problem was solved.
Though this has already been said, the 4.4w1 insecure boot.img no longer roots 5.0.1. Probably due to incompatibilliuies, I'll work up a new rooted boot.img this weekend. Sadly looks like its going to require flashing the boot.img, not just booting it.
Click to expand...
Click to collapse
Look forward to flashing the Rooted boot.img.
Thank you for doing it.
Update Today
In past day i have update to 5.0.1 LWX48P release. Today i have received automatic update on my watch to 5.0.1 LWX48T release. I don't know what is change but in past day I noticed a problem centering of my display; after update now the display is centered
http://shabbypenguin.com/?developer=Tools&folder=Superuser
flash that in TWRP to get root
latest update: https://mega.co.nz/#!dNBnyT7Q!qtPkmgOV-jrajJAAKDLE6cQWVHyDGi3OsEwmTq5jfOU LWX48T-from-LWX48P follow OP's instructions but change teh file names
Anyone have success pushing a system file and having it stick after reboot WITHOUT root? I haven't been successful to have it stick...
808phoneaddict said:
Anyone have success pushing a system file and having it stick after reboot WITHOUT root? I haven't been successful to have it stick...
Click to expand...
Click to collapse
Not sure if it will work, but have you tried it as su in adb?
>adb shell
>su
#
JimSmith94 said:
Not sure if it will work, but have you tried it as su in adb?
>adb shell
>su
#
Click to expand...
Click to collapse
Yeah I tried it didn't recognize su...I'll try again later
808phoneaddict said:
Yeah I tried it didn't recognize su...I'll try again later
Click to expand...
Click to collapse
Sounds like you need to figure out why su isn't working anyway. You might need to update your adb.
JimSmith94 said:
Sounds like you need to figure out why su isn't working anyway. You might need to update your adb.
Click to expand...
Click to collapse
I updated that...hmm otherwise it should be working? Would I need to do command prompt from another window?
If you have root installed and reboot to recovery, then "adb shell" should get you a # prompt.
If it does, then you're already ADB with root.
If you get $ prompt then you don't have root.
I don't think you can push system files without root?
You certainly can't "adb root" without root. That's for sure.
808phoneaddict said:
I updated that...hmm otherwise it should be working? Would I need to do command prompt from another window?
Click to expand...
Click to collapse
I just tried it on my rooted phone and "su" asks for root privileges on the phone, so that won't work, sorry.
JimSmith94 said:
I just tried it on my rooted phone and "su" asks for root privileges on the phone, so that won't work, sorry.
Click to expand...
Click to collapse
You did it in recovery mode? I know u can try to mount as rw in recovery...could U try that and see what happens?
808phoneaddict said:
You did it in recovery mode? I know u can try to mount as rw in recovery...could U try that and see what happens?
Click to expand...
Click to collapse
As I said, my phone is rooted, so of course it would work in recovery for me. Assuming you don't have TWRP already installed, you could try booting into TWRP with "fastboot boot <TWRP img file name>" and see if you can mount system and copy your system file with its file manager.
JimSmith94 said:
As I said, my phone is rooted, so of course it would work in recovery for me. Assuming you don't have TWRP already installed, you could try booting into TWRP with "fastboot boot <TWRP img file name>" and see if you can mount system and copy your system file with its file manager.
Click to expand...
Click to collapse
I actually booted to twrp and change the mount to rw, then I pushed the hosts file successfully (it says 100%) but when I boot up it doesn't work, not sure if I need to prove the old one maybe? Or does having the boot slots make a difference? Am I pushing to the wrong place?
808phoneaddict said:
I actually booted to twrp and change the mount to rw, then I pushed the hosts file successfully (it says 100%) but when I boot up it doesn't work, not sure if I need to prove the old one maybe? Or does having the boot slots make a difference? Am I pushing to the wrong place?
Click to expand...
Click to collapse
Sorry, you'll have to find someone else to help, or just go ahead and root it. You can probably unroot it after you have done your copy, but I don't know why you would bother.
I have always rooted my phones, so I haven't done what you're trying to do. Plus I don't even have my Pixel XL yet, so I don't know anything about the boot slots yet. Over and out!
JimSmith94 said:
Sorry, you'll have to find someone else to help, or just go ahead and root it. You can probably unroot it after you have done your copy, but I don't know why you would bother.
I have always rooted my phones, so I haven't done what you're trying to do. Plus I don't even have my Pixel XL yet, so I don't know anything about the boot slots yet. Over and out!
Click to expand...
Click to collapse
O yeah I rooted, was rooted for a while but I ran into the data drain that others are reporting when there is an OTA update...knowing that December is upon us I was trying to unroot but push modified hosts file so I wouldn't get ads. Honestly, if it wasn't for the ads, I have no problem with a stock pixel xl...there hasn't been much development for it just yet, understandable since it's so new...