Has anyone successfully gotten to TWRP Recovery to install for their Omate?
I have tried to do it using GooManager, but it says it cant find it.
I have also attempted to do the alternate methods but cant find a scatter file for it ?
Is there any tutorial on this that has worked for anyone?
fibroman said:
Has anyone successfully gotten to TWRP Recovery to install for their Omate?
I have tried to do it using GooManager, but it says it cant find it.
I have also attempted to do the alternate methods but cant find a scatter file for it ?
Is there any tutorial on this that has worked for anyone?
Click to expand...
Click to collapse
I installed TWRP on my TrueSmart this morning via adb while booted to Android. Rename the file that you download to twrp.img and then do the following:
adb push twrp.img /sdcard/twrp.img
adb shell dd if=/sdcard/twrp.img of=/dev/recovery
Done.
Dees_Troy said:
I installed TWRP on my TrueSmart this morning via adb while booted to Android. Rename the file that you download to twrp.img and then do the following:
adb push twrp.img /sdcard/twrp.img
adb shell dd if=/sdcard/twrp.img of=/dev/recovery
Done.
Click to expand...
Click to collapse
Thanks for the info. I now have it installed.
But when trying to do a backup it says( Failed )
Updating Partition details...
Kernel does not have support for running this application.
I was having the same issue. Did exactly what Dees_Troy suggested and it worked like a charm.
Thanks!
Now to wait for roms, because the stock one blows so far.
mortis2600 said:
I was having the same issue. Did exactly what Dees_Troy suggested and it worked like a charm.
Thanks!
Now to wait for roms, because the stock one blows so far.
Click to expand...
Click to collapse
Ouch!!! I can always take Operative and instead of a 100MB file make it +600MB file and call it a "ROM" if it will help.
fibroman said:
Thanks for the info. I now have it installed.
But when trying to do a backup it says( Failed )
Updating Partition details...
Kernel does not have support for running this application.
Click to expand...
Click to collapse
Try running the backup again. If you get an error, adb pull /tmp/recovery.log without rebooting and attach or paste the log to a paste site.
Lokifish Marz said:
Ouch!!! I can always take Operative and instead of a 100MB file make it +600MB file and call it a "ROM" if it will help.
Click to expand...
Click to collapse
Sorry, I have a fairly high standard of roms at this point.
Dont want to go too far off topic, but I've had some issues with bluetooth (pairs, doesn't stay connected, thus making the companion app useless), battery life, etc.
I may have to run tasker scripts to emulate some of the things I want it to do with notifications and turning the screen on. Finally, if I install a new launcher, it'd be wonderful if it didn't cover up the notifications bar.
mortis2600 said:
Sorry, I have a fairly high standard of roms at this point.
Dont want to go too far off topic, but I've had some issues with bluetooth (pairs, doesn't stay connected, thus making the companion app useless), battery life, etc.
I may have to run tasker scripts to emulate some of the things I want it to do with notifications and turning the screen on. Finally, if I install a new launcher, it'd be wonderful if it didn't cover up the notifications bar.
Click to expand...
Click to collapse
I quit anyways so no biggie
mortis2600 said:
Sorry, I have a fairly high standard of roms at this point.
Click to expand...
Click to collapse
Then.... build.... your.... own?
Be a part of the solution.
Sent from my Galaxy Nexus using Tapatalk 2
Lokifish Marz said:
I quit anyways so no biggie
Click to expand...
Click to collapse
Did you build the stock rom? If so, I meant no offense.
mortis2600 said:
Did you build the stock rom? If so, I meant no offense.
Click to expand...
Click to collapse
It was built from broken, crappy Umeox firmware so better battery life, memory management and pretty much every fix or improvement came form me. Like I said I'm done so no offense taken.
Lokifish Marz said:
It was built from broken, crappy Umeox firmware so better battery life, memory management and pretty much every fix or improvement came form me. Like I said I'm done so no offense taken.
Click to expand...
Click to collapse
I don't have yours installed. Mine is just running completely stock firmware right now.
And it sucks that you're quitting. Your build looked to be the one thing that might make the OS on this thing worth using.
---------- Post added at 08:09 PM ---------- Previous post was at 07:42 PM ----------
kuronosan said:
Then.... build.... your.... own?
Be a part of the solution.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
If I had the expertise to do so, I would be inclined to do so. Sadly, I'll just have to settle for reporting bugs and making feature requests and being happy to have my device at all.
[SOLVED] backup failed on TWRP
fibroman said:
Thanks for the info. I now have it installed.
But when trying to do a backup it says( Failed )
Updating Partition details...
Kernel does not have support for running this application.
Click to expand...
Click to collapse
If you are getting 'Unable to create folder' error, then rename the backup name and it should work :good:
nbarm2 said:
If you are getting 'Unable to create folder' error, then rename the backup name and it should work :good:
Click to expand...
Click to collapse
That did the trick!!! Renaming the backup. Thanks.
One final question here: I have been using apps like goomanager to reboot into recovery, but how can you enter TWRP straight from turning the watch on.
Is there a key combo that needs to be held when turning the watch on to get right into TWRP? I tried holding down the bottom right key and that did not work.
Hold both keys for 10 seconds then toggle to recovery
Sent from my Galaxy Nexus using Tapatalk 2
kuronosan said:
Hold both keys for 10 seconds then toggle to recovery
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
This, but your battery pretty much has to be fully charged or else it will just flash the Omate logo on the screen for a couple seconds and then shut off.
Related
anyone have a mod for optical sensor button ? i saw some post for other device and i tested on my phone and it went into a boot loop. this will be a nice mod since the power button is on the top right side of the phone and is kinda hard to press.
http://forum.xda-developers.com/showpost.php?p=7292981&postcount=12
mattbollenbach said:
http://forum.xda-developers.com/showpost.php?p=7292981&postcount=12
Click to expand...
Click to collapse
thank for link
mattbollenbach said:
http://forum.xda-developers.com/showpost.php?p=7292981&postcount=12
Click to expand...
Click to collapse
That doesn't work for everyone, so a more permanent solution will have to be devised.
craig.cabrey said:
That doesn't work for everyone, so a more permanent solution will have to be devised.
Click to expand...
Click to collapse
i've done this mod that exact same way on my aria with 4 different roms with no issues at all every time.
you really just need to save the qwerty.kl file and push it to the phone. reboot into recovery, go to the partitions menu, mount the system partition, push the file via adb, reboot your phone and voila.
jaex said:
anyone have a mod for optical sensor button ? i saw some post for other device and i tested on my phone and it went into a boot loop. this will be a nice mod since the power button is on the top right side of the phone and is kinda hard to press.
Click to expand...
Click to collapse
SEARCH...!
Please take a moment to review the forum rules with regards to searching existing threads prior to creating a new one, and also regarding the proper sections to post in. Moving to General as this is not a Development thread.
you really just need to save the qwerty.kl file and push it to the phone. reboot into recovery, go to the partitions menu, mount the system partition, push the file via adb, reboot your phone and voila.
Click to expand...
Click to collapse
oh my gosh that seems painfully complicated considering the simplicity of the issue. that's kinda funny really
mattbollenbach said:
i've done this mod that exact same way on my aria with 4 different roms with no issues at all every time.
you really just need to save the qwerty.kl file and push it to the phone. reboot into recovery, go to the partitions menu, mount the system partition, push the file via adb, reboot your phone and voila.
Click to expand...
Click to collapse
I've done that. The qwerty.kl method just simply isn't working for some people.
This worked for me
Couldn't figure out how to add attachments to this post, and it won't let me add an external link since it's a new forum account. google ojwake-signed.zip or something.
Steps: Load file to SD card, boot in to recovery mode, install zip, locate this zip on flash card, reboot.
(ojwake-signed.zip)
Don't remember where i got this, but kudos to that guy!
Neverwhere10
HTC Aria Liberated B005.
gdeadfan said:
oh my gosh that seems painfully complicated considering the simplicity of the issue. that's kinda funny really
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=7292981&postcount=12
Just to make it even easier on you
EDIT-Short Version...Download file from link above
-:Have Clockwork Recovery Installed and know how to use ADB:-
-DOWNLOAD ATTACHED to linked post qwerty.kl (may need 7zip to extract file from archive...)
-BOOT into CLOCKWORK recovery with NO USB PLUGGED INto phone!!!
-PARTITIONS>MOUNT /SYSTEM
-adb push qwerty.kl /system/usr/keylayout|adb reboot
As far as I know, this ridiculously simply method of pushing qwerty.kl has worked for everyone except the few that didn't boot into clockwork correctly, once they booted into clockwork correctly it then worked for them.
I updated the instructions to be crystal clear for all you noobs. If pushing a file to your android device is too painfully complicated for you, I suggest you read/search more and figure out what you are actually doing.
Neverwhere10's steps are just as painfully complicated, but at least he is providing some constructive input.
Thanks!
Worthless thread is worthless.
jaex said:
anyone have a mod for optical sensor button ? i saw some post for other device and i tested on my phone and it went into a boot loop. this will be a nice mod since the power button is on the top right side of the phone and is kinda hard to press.
Click to expand...
Click to collapse
Thanks for asking this question when you did...
mattbollenbach said:
http://forum.xda-developers.com/showpost.php?p=7292981&postcount=12
Click to expand...
Click to collapse
Thank you so much for the link... this is great.. love it... like jeezy
This mod is built into the CM6 rom.
Sent from my Liberty using XDA App
There is also a setting in one of the menus if you are using any of attn1's cm roms for this same thing. I currently have my aria set this way and I am using cm008 as of right now.
Sent from my Liberty using XDA App
If you have not already seen it, or if an application is an acceptable solution, widgetlocker is a nifty program.
jaex said:
anyone have a mod for optical sensor button ? i saw some post for other device and i tested on my phone and it went into a boot loop. this will be a nice mod since the power button is on the top right side of the phone and is kinda hard to press.
Click to expand...
Click to collapse
Sent from my HTC Liberty using XDA App
This is an interesting question, maybe we should take a test to see, and I want to ask and optical sensor is the same?
Hello! Here's another one of my donations to the Slide community - it's AmonRA in an update.zip. There are a few bugs since this is just a quick port and I haven't tested functionality (I'll leave that up to you ).
Notes:
YOU MUST HAVE ROOT AND "ENG" RECOVERY INSTALLED. (Just like the Clockwork method).
Please make sure to use your OPTICAL pad to scroll through menu items - pressing the optical pad is the replacement for pressing Power (aka Enter).
DOWNLOAD: [removed - too broken]
Enjoy!
THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU
Haha, I've wanted to run Amon_Ra's recovery since I found out it has a built in terminal. Thanks a bunch man.
Sent from my T-Mobile myTouch 3G Slide using XDA App
how is AmonRA's recovery different/better than clockwork? or it doesn't really matter o_o
daniel60104 said:
how is AmonRA's recovery different/better than clockwork? or it doesn't really matter o_o
Click to expand...
Click to collapse
it has a built-in console, and it uses the right a2sd directory...clockwork uses /sd-ext/, but we use /system/sd/...
migueltherocker said:
THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU
Click to expand...
Click to collapse
I second that! Thanks!!!
edit: Im sure its nothing, but im getting this message when entering recovery:
Code:
Build: not set
E: Invalid command argument
-BMFC
The console doesn't work, just a headsup.
But thank you nb! and RA, obviously
edit: USB is broken, too. Don't enable it.
r0man said:
The console doesn't work, just a headsup.
But thank you nb! and RA, obviously
edit: USB is broken, too. Don't enable it.
Click to expand...
Click to collapse
that makes me wanna do the thing you said not to do...lol
ive found if you sit there and stare at it for about 30 seconds without doing anything, it freaks out! It shows the progress message from installing the update.zip to get into Amon-Ra from the stock recovery, then if i press optical pad it reboots...
any thoughts/confirmation?
-BMFC
bmfc187 said:
ive found if you sit there and stare at it for about 30 seconds without doing anything, it freaks out! It shows the progress message from installing the update.zip to get into Amon-Ra from the stock recovery, then if i press optical pad it reboots...
any thoughts/confirmation?
Click to expand...
Click to collapse
I'm not sure yet - I'm at work at the moment and we're too busy for me to focus on fixing it at the moment. I'll take a look at it tomorrow or this week.
Thanks!
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
Much appreciated! Big fan of this recovery.
FYI: Tried a Nand backup including my ext partition ... did not work. Perhaps something I did wrong, not sure.
neither did bart backup...
This recovery image is pretty much entirely broken. It needs a lot of work, but I'm hoping that AmonRA can work on it if I can manage to get his contact info.
Great job! I like it!
nbetcher said:
This recovery image is pretty much entirely broken. It needs a lot of work, but I'm hoping that AmonRA can work on it if I can manage to get his contact info.
Click to expand...
Click to collapse
so... what happened with this? are you waiting until we have S-OFF or...
etu_aty said:
so... what happened with this? are you waiting until we have S-OFF or...
Click to expand...
Click to collapse
I'm not really sure how to get a hold of the (real) AmonRA, to be honest.
nbetcher said:
I'm not really sure how to get a hold of the (real) AmonRA, to be honest.
Click to expand...
Click to collapse
Twitter would be a good way: http://twitter.com/#!/Amon_RA
OP : Could you please change the name of this recovery? I'm getting PM's with issues logged on this recovery while I didn't make it
Amon_RA said:
OP : Could you please change the name of this recovery? I'm getting PM's with issues logged on this recovery while I didn't make it
Click to expand...
Click to collapse
Do you plan to create an official version of your recovery for the Slide? I personally would be very interested in this . It was a lifesaver for my Dream. Keep up the good work!
When we have full root (S-OFF), we "might" have a Amon RA recovery. It's wishful thinking on my part, but I really hope so.
Amon_RA said:
OP : Could you please change the name of this recovery? I'm getting PM's with issues logged on this recovery while I didn't make it
Click to expand...
Click to collapse
Err, I can, but what should I name it? It came from you a long time ago, albeit unofficially.
I don't think it should be renamed... just put a huge red disclaimer in the op with "Do not contact Amon Ra, this is an unsupported project. No support will be provided by the author or myself"
Sent from my T-Mobile myTouch 3G Slide using XDA App
I just got this in the mail today. Does anyone have any insights on how to unlock the bootloader and inject root? I had assumed 'fastboot' would work, but this has ODIN. I'm sure I could follow the steps on the original S4, but I don't know what the downstream effects will be.
Thanks!
----------------------------------------------------------------------------------
Edit: Please see this post: http://forum.xda-developers.com/showpost.php?p=44322019&postcount=70
Ok, just got done rooting my gs4 vzw dev edition. It was really pretty simple.
Steps from my win8 laptop were...
Install samsung drivers,
get adb working (android sdk doesn't seem to work on win8.. but just the adb files are all you need, google adb platform-tools or just use win7)
dl and push your superuser zip to the sdcard or external sdcard
dl odin 3.07 and extract to pc
dl and make tar.md5 of your favorite recovery. ( i personally like cwm )
Then all I did was... reboot phone in to odin mode... while phone is powered off, hold vol down + power
Start odin.exe
uncheck auto-reboot
click pda button, select the recovery file.md5
press start and let it finish, only takes a few secs...
once done.. reboot in to recovery, and flash the superuser.zip u pushed over to it.
Vol up + power to boot in to recovery. for me i just booted the phone normally... used "adb reboot recovery" then flashed superuser.zip.
reboot your phone and done.
good idea to make a backup while ur in recovery
If someone has hosting, i can send the files needed.
-r4ph
Click to expand...
Click to collapse
Okay, so I couldn't wait!
I followed the steps here: http://forum.xda-developers.com/showthread.php?t=2290798 and was able to gain root access.
I have yet to take the plunge on a custom recovery, but I'm sure I'll do that soon.
Additionally, the boot screen now has a picture of an "unlocked" lock, and the words "Samsung" "Custom". I guess they know that this has been flashed.
How did you order this prior to it being available on the Samsung Web site?
Sent from my DROID RAZR using Tapatalk 2
equake said:
How did you order this prior to it being available on the Samsung Web site?
Sent from my DROID RAZR using Tapatalk 2
Click to expand...
Click to collapse
It became available yesterday, and I got overnight shipping.
tithefug said:
It became available yesterday, and I got overnight shipping.
Click to expand...
Click to collapse
Is it full of VW blot ware?
rcb929 said:
Is it full of VW blot ware?
Click to expand...
Click to collapse
Yes. The only difference is that this has an unlocked bootloader by default.
tithefug said:
Okay, so I couldn't wait!
I followed the steps here: http://forum.xda-developers.com/showthread.php?t=2290798 and was able to gain root access.
I have yet to take the plunge on a custom recovery, but I'm sure I'll do that soon.
Additionally, the boot screen now has a picture of an "unlocked" lock, and the words "Samsung" "Custom". I guess they know that this has been flashed.
Click to expand...
Click to collapse
Mine comes tomorrow or Monday. So, despite it being unlocked, you still had to go thru that kernel replacement root method? Hmmm. I would have thought there would have been an easier way, no?
markwebb said:
Mine comes tomorrow or Monday. So, despite it being unlocked, you still had to go thru that kernel replacement root method? Hmmm. I would have thought there would have been an easier way, no?
Click to expand...
Click to collapse
Probably. But, I knew that would work.
tithefug said:
Probably. But, I knew that would work.
Click to expand...
Click to collapse
Couldn't you have just skipped the kernel replacement steps and just run motochopper step in that tutorial?
I think we need more insight from our all powerful devs on the best/easiest way to root a Dev Edition phone.
markwebb said:
Couldn't you have just skipped the kernel replacement steps and just run motochopper step in that tutorial?
I think we need more insight from our all powerful devs on the best/easiest way to root a Dev Edition phone.
Click to expand...
Click to collapse
Maybe. Either way it worked for me.
That being said, when I flashed the latest CM10.1-Nightly, the screen went blank (no boot animation). I restored my backup, so I still have a working device.
tithefug said:
Okay, so I couldn't wait!
I followed the steps here: http://forum.xda-developers.com/showthread.php?t=2290798 and was able to gain root access.
I have yet to take the plunge on a custom recovery, but I'm sure I'll do that soon.
Additionally, the boot screen now has a picture of an "unlocked" lock, and the words "Samsung" "Custom". I guess they know that this has been flashed.
Click to expand...
Click to collapse
I ended up doing the same as you and had to do all the steps too in order for it to work. Now I keep getting a warning message "this device has detected an unauthorized attempt..." trying to get me to reboot though. Can the master devs find something for the developer edition phones to have an easier time rooting?
And I also bought my phone and ordered it for next day shipping, so worth it!
tithefug said:
Okay, so I couldn't wait!
I followed the steps here: http://forum.xda-developers.com/showthread.php?t=2290798 and was able to gain root access.
I have yet to take the plunge on a custom recovery, but I'm sure I'll do that soon.
Additionally, the boot screen now has a picture of an "unlocked" lock, and the words "Samsung" "Custom". I guess they know that this has been flashed.
Click to expand...
Click to collapse
The boot message you see when you power on your device means your device is rooted. I have the same exact thing when I rooted mine. I got mine from a Verizon store.
Sent from my SCH-I545 using xda app-developers app
tithefug said:
Maybe. Either way it worked for me.
That being said, when I flashed the latest CM10.1-Nightly, the screen went blank (no boot animation). I restored my backup, so I still have a working device.
Click to expand...
Click to collapse
What backup method are you using: CWM or TWRP?
cmmelton2 said:
I ended up doing the same as you and had to do all the steps too in order for it to work. Now I keep getting a warning message "this device has detected an unauthorized attempt..." trying to get me to reboot though. Can the master devs find something for the developer edition phones to have an easier time rooting?
And I also bought my phone and ordered it for next day shipping, so worth it!
Click to expand...
Click to collapse
Search for the phrase used in the notification. It had to so with SEAndroid. You have to delete/rename KNOXAgent.apk, KNOXAgent.odex from /system and com.sec.knox.seandroid from /data/data
Have fun!
markwebb said:
What backup method are you using: CWM or TWRP?
Click to expand...
Click to collapse
TWRP. I installed it using the GooManager app.
tithefug said:
TWRP. I installed it using the GooManager app.
Click to expand...
Click to collapse
OK, thanks. I am just noticing a thread on TWRP issues and am nervous about it. However, you were able to back up the stock out of the box ROM and then restore it w/o a hitch?
markwebb said:
OK, thanks. I am just noticing a thread on TWRP issues and am nervous about it. However, you were able to back up the stock out of the box ROM and then restore it w/o a hitch?
Click to expand...
Click to collapse
Yep. I'm going to try CM again in a little while. Now that the official camera/gallery is out, I have less reasons to. But the ridiculousness that is the notification pane might just send me over the edge.
tithefug said:
Yep. I'm going to try CM again in a little while. Now that the official camera/gallery is out, I have less reasons to. But the ridiculousness that is the notification pane might just send me over the edge.
Click to expand...
Click to collapse
Was just wondering if you tried CM yet?
markwebb said:
I think we need more insight from our all powerful devs on the best/easiest way to root a Dev Edition phone.
Click to expand...
Click to collapse
I would also like to see the best/correct way to root the Developer Edition.
markwebb said:
Was just wondering if you tried CM yet?
Click to expand...
Click to collapse
Not yet. It's going to have to wait until tomorrow. Sorry.
Help! I was using Carlos' unlocking the bootloader guide against my will, because I love stock. And turns out karma has gotten me. For some reason my recovery wasn't installing on V20B, so I flashed back to V20F, factory reset, re-rooted, installed busybox, flashed the artas recovery... And yet my recovery STILL isn't showing up. The boot animation is inverted and the touch screen is still "messed up." I have a backup on my external SD card that I can use if I somehow get recovery functional. It's just the stupid recovery won't work and I need it to work lol. Any help? Please?! By the way, I've done an emergency flash using LG Mobile Support Tool and that didn't work, so I'm still open to suggestions.
I've been very helpful to everyone who's asked me for help, I'd like for others to be the same to me. Thanks to whoever tries
go back into recovery then make a backup in tar format then reboot into recovery and check for your files.
Sent from my LG-P769(20F) using the xda-developers app. If I helped you please hit the "thanks" button.
Nathan.7118391 said:
go back into recovery then make a backup in tar format then reboot into recovery and check for your files.
Sent from my LG-P769(20F) using the xda-developers app. If I helped you please hit the "thanks" button.
Click to expand...
Click to collapse
I don't have recovery. It won't flash. I have stock V20F without anything but a messed up screen.
Have you tried installing recovery using the L9 recovery installer app?
Also, for the wonky touch screen, it would help a lot if you enabled "Show touches" in the developers options tab~
Creta said:
Have you tried installing recovery using the L9 recovery installer app?
Also, for the wonky touch screen, it would help a lot if you enabled "Show touches" in the developers options tab~
Click to expand...
Click to collapse
That's what I'm using. Full busybox install and it still isn't installing.
You needed to be rooted to get recovery.
Sent from my LG-P769(20F) using the xda-developers app. If I helped you please hit the "thanks" button.
Ilxaot said:
That's what I'm using. Full busybox install and it still isn't installing.
Click to expand...
Click to collapse
you need this busybox
https://play.google.com/store/apps/details?id=com.bitcubate.root.busybox.complete&hl=en
I never had a problem with the other, but others have, but this one has worked for everyone.
If you have root, just fix the wonky touch screen the old way (through adb)
kuma82 said:
you need this busybox
https://play.google.com/store/apps/details?id=com.bitcubate.root.busybox.complete&hl=en
I never had a problem with the other, but others have, but this one has worked for everyone.
If you have root, just fix the wonky touch screen the old way (through adb)
Click to expand...
Click to collapse
Can you upload the apk for that? I can't type due to my phone's screen. And how do I do it through ADB? I don't even know how to use ADB, as embarrassing as it sounds. I could never get it to work. But I'm willing to do anything now.
Ilxaot said:
Can you upload the apk for that? I can't type due to my phone's screen. And how do I do it through ADB? I don't even know how to use ADB, as embarrassing as it sounds. I could never get it to work. But I'm willing to do anything now.
Click to expand...
Click to collapse
First fix the touch screen, hold up I'll send you all the info,
Another thing, I hope you already have adb debugging enabled
Wait a min, you have everything you need if you tried to unlock your device
Inside the root lelus folder is the adb
You know, if you go to link for robert busybox on your pc (and sign in) it will send it to your phone, to download
1. Go to the root lelus folder (should be on your c: drive) and open the "stuff" folder
now, hold down the shift key and right click with your mouse, you should see an option, to "open command window here"
This should open a cmd up where the adb is at.
2. Open the cwm_ts_fix_p769.zip and go into the system folder and copy the v6.bin to your external sd
3.now type
adb devices (in the command window)
you should get a number with online status. If you don't it's because adb debugging is not enabled
4. next type
adb shell
su
your phone will ask to enable it, good luck on enabling on the wonky touch screen
okay, type
cat /storage/external_SD/v6.bin > /sys/devices/virtual/input/lge_touch/firmware
note if you put it on the internal storage, type
cat /sdcard/external_SD/v6.bin > /sys/devices/virtual/input/lge_touch/firmware
this will cause the shell to freeze.
so open up a new cmd (hold shift key & and right click inside the stuff folder) and type
adb reboot
hope this helps, if you need a better guide, lol just ask, it will take me awhile though
kuma82 said:
First fix the touch screen, hold up I'll send you all the info,
you have root right?
Click to expand...
Click to collapse
I'll root again right now, I've reflashed so many times lol.
EDIT: I already have root aha. But nothing else.
kuma82 said:
First fix the touch screen, hold up I'll send you all the info,
you have root right?
Another thing, I hope you already have adb debugging enabled
Wait a min, you have everything you need if you tried to unlock your device
Inside the root lelus folder is the adb
You know, if you go to link for robert busybox on your pc (and sign in) it will send it to your phone, to download
Click to expand...
Click to collapse
Sign in as to your Google account and go to the play store.
Sent from my LG-P769 using Tapatalk 4 Beta
kuma82 said:
First fix the touch screen, hold up I'll send you all the info,
you have root right?
Another thing, I hope you already have adb debugging enabled
Wait a min, you have everything you need if you tried to unlock your device
Inside the root lelus folder is the adb
You know, if you go to link for robert busybox on your pc (and sign in) it will send it to your phone, to download
Click to expand...
Click to collapse
I don't have internet connection on my phone lol. We have FIOS and the router password is a WPA and it's like 14 characters long, with like 4 Q's (Near impossible to hit with mirrored touch screen. Trust me. It's a science of its own) I just need the apk, I couldn't find it anywhere. And okay, for the adb, how do i fix it?
Ilxaot said:
I don't have internet connection on my phone lol. We have FIOS and the router password is a WPA and it's like 14 characters long, with like 4 Q's (Near impossible to hit with mirrored touch screen. Trust me. It's a science of its own) I just need the apk, I couldn't find it anywhere. And okay, for the adb, how do i fix it?
Click to expand...
Click to collapse
Here's a direct link to busybox.apk if you still need it.
OMG I don't have internet my WiFi password is too long to type. Is it THAT hard to get an apk?
Creta said:
Here's a direct link to busybox.apk if you still need it.
Click to expand...
Click to collapse
THANK YOU. Now I can try it. I'll keep you updated, thanks for listening and not telling me methods I can't use.
Creta said:
Here's a direct link to busybox.apk if you still need it.
Click to expand...
Click to collapse
Bummer. This isn't the one I needed. NEVER MIND CWM IS WORKING THANK YOU SO MUCH OMG. THANKS TO YOU! Albeit it was really simple, THANKS YOU! God bless your soul, have a great life.
Ilxaot said:
Bummer. This isn't the one I needed. NEVER MIND CWM IS WORKING THANK YOU SO MUCH OMG. THANKS TO YOU! Albeit it was really simple, THANKS YOU! God bless your soul, have a great life.
Click to expand...
Click to collapse
No problem, I just unlocked my boot loader 2 days ago... took me a while cause carlo's video was missing out a lot of things...
Creta said:
No problem, I just unlocked my boot loader 2 days ago... took me a while cause carlo's video was missing out a lot of things...
Click to expand...
Click to collapse
I've got my backup back, but my screen is still mirrored. I'm flashing the touchscreen fix for now, but if this doesn't work I'm at a loss.
EDIT: Yeah, it didn't work. Things are still mirrored.
Ilxaot said:
I've got my backup back, but my screen is still mirrored. I'm flashing the touchscreen fix for now, but if this doesn't work I'm at a loss.
Click to expand...
Click to collapse
TS fix is for the wonky touchscreen, for mirrored, I think you gotta go back to 20D for P769
Creta said:
TS fix is for the wonky touchscreen, for mirrored, I think you gotta go back to 20D for P769
Click to expand...
Click to collapse
So I have to flash again?
Download
Mega
Installing
You can't flash this yet (I'm working on that, I promise) but you can boot from it!
NOTE: THIS IS A WIP. Not a lot has been really tested yet and this is posted merely for your enjoyment atm.
I don't suggest flashing anything yet, not that there is anything to flash heh.
Also, I take no responsibility if you break your watch, yada, yada.
To do this, make sure you have Android's tools (for fastboot), an unlocked bootloader, and the watch connected to your computer in Debug mode.
> adb reboot bootloader
<wait for the reboot to happen>
> fastboot boot /path/to/recovery.img
Click to expand...
Click to collapse
Enjoy!
Did u push the tree to github?
1st built for me was a no go
wouldn't twrp make more sense since its touch based?
D-FUSE said:
Did u push the tree to github?
1st built for me was a no go
Click to expand...
Click to collapse
Nope, though I'll try to get to it tomorrow after work! If you want, I can give you an overview of what I did:
1. Pull the source for CM11.
2. Dump boot and recovery images using dd.
3. Ran makevender.sh using lge and dory.
4. lunch'd it up.
5. Replaced the recovery.fstab with the fstab from the recovery ramdisk.
6. Ran makerecovery.sh.
7. fastboot boot'd the recovery.img
This is all off the top of my head and missing some random files you had to hack around with, of course. Hope you get it working and more progress is made because I can't get to it for another day!
ptesmoke said:
wouldn't twrp make more sense since its touch based?
Click to expand...
Click to collapse
I explained in the post that I thought CWM had touch built-in and have since switched over to Philz.
Smith7018 said:
Nope, though I'll try to get to it tomorrow after work! If you want, I can give you an overview of what I did:
1. Pull the source for CM11.
2. Dump boot and recovery images using dd.
3. Ran makevender.sh using lge and dory.
4. lunch'd it up.
5. Replaced the recovery.fstab with the fstab from the recovery ramdisk.
6. Ran makerecovery.sh.
7. fastboot boot'd the recovery.img
This is all off the top of my head and missing some random files you had to hack around with, of course. Hope you get it working and more progress is made because I can't get to it for another day!
I explained in the post that I thought CWM had touch built-in and have since switched over to Philz.
Click to expand...
Click to collapse
I wasn't trying to shoot you down just suggesting if it would be easier to iron out since its built to be touch based...that's all
ptesmoke said:
I wasn't trying to shoot you down just suggesting if it would be easier to iron out since its built to be touch based...that's all
Click to expand...
Click to collapse
Heh, don't worry, you didn't seem like you were shooting me down at all! Anyway, I tried TWRP but it wouldn't boot for some reason (it's extremely hard to debug at the bootloader level). So, I went back to CWM and got swipe control working! Here's a build of the recovery image
NOTE: To boot this do NOT flash it; you need to "fastboot boot" it. Also, don't blame me if your watch breaks, yadda, yadda.
As per the source, I'll tell you the truth, it's pretty ugly and I'm deathly afraid of git so give me a few days until I get around to uploading it.
Download: https://mega.co.nz/#!ctMGgb4T!1g3m2PxsXH3LEoF0GuCaxFcfvrUBHc1_IW3nXDdGQbA
Smith7018 said:
Nope, though I'll try to get to it tomorrow after work! If you want, I can give you an overview of what I did:
1. Pull the source for CM11.
2. Dump boot and recovery images using dd.
3. Ran makevender.sh using lge and dory.
4. lunch'd it up.
5. Replaced the recovery.fstab with the fstab from the recovery ramdisk.
6. Ran makerecovery.sh.
7. fastboot boot'd the recovery.img
This is all off the top of my head and missing some random files you had to hack around with, of course. Hope you get it working and more progress is made because I can't get to it for another day!
I explained in the post that I thought CWM had touch built-in and have since switched over to Philz.
Click to expand...
Click to collapse
Interesting.
I was/am working on TWRP, but my first build wouldn't boot.
EDIT: Where did you get that strap? I really like it.
Smith7018 said:
Heh, don't worry, you didn't seem like you were shooting me down at all! Anyway, I tried TWRP but it wouldn't boot for some reason (it's extremely hard to debug at the bootloader level). So, I went back to CWM and got swipe control working! Here's a build of the recovery image
NOTE: To boot this do NOT flash it; you need to "fastboot boot" it. Also, don't blame me if your watch breaks, yadda, yadda.
As per the source, I'll tell you the truth, it's pretty ugly and I'm deathly afraid of git so give me a few days until I get around to uploading it.
Download: https://mega.co.nz/#!ctMGgb4T!1g3m2PxsXH3LEoF0GuCaxFcfvrUBHc1_IW3nXDdGQbA
Click to expand...
Click to collapse
Thanks man. Got it to boot up and backup worked. Guess that's about all u can do for now
Sent from my Nexus 5 using XDA Premium 4 mobile app
dude1981 said:
Thanks man. Got it to boot up and backup worked. Guess that's about all u can do for now
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Awesome! You can technically flash mods; I flashed the iOS emoji mod so now my hangout messages don't have the ugly Google ones :victory:
jamcar said:
Interesting.
I was/am working on TWRP, but my first build wouldn't boot.
EDIT: Where did you get that strap? I really like it.
Click to expand...
Click to collapse
Same, and I gave up; TWRP's UI won't really work out too well at 280x280, IMO, and CWM swipe is already working heh. I got the watch strap from eBay. It was super cheap and easy to adjust!
Why just booting it via fastboot instead of flashing it?
and have you push your device tree to github??
Smith7018 said:
Heh, don't worry, you didn't seem like you were shooting me down at all! Anyway, I tried TWRP but it wouldn't boot for some reason (it's extremely hard to debug at the bootloader level). So, I went back to CWM and got swipe control working! Here's a build of the recovery image
NOTE: To boot this do NOT flash it; you need to "fastboot boot" it. Also, don't blame me if your watch breaks, yadda, yadda.
As per the source, I'll tell you the truth, it's pretty ugly and I'm deathly afraid of git so give me a few days until I get around to uploading it.
Download: https://mega.co.nz/#!ctMGgb4T!1g3m2PxsXH3LEoF0GuCaxFcfvrUBHc1_IW3nXDdGQbA
Click to expand...
Click to collapse
just zipping your device tree and uploading it would work too.
And how you build a recovery and git look skeery?? lol
Smith7018 said:
Awesome! You can technically flash mods; I flashed the iOS emoji mod so now my hangout messages don't have the ugly Google ones :victory:
Same, and I gave up; TWRP's UI won't really work out too well at 280x280, IMO, and CWM swipe is already working heh. I got the watch strap from eBay. It was super cheap and easy to adjust!
Click to expand...
Click to collapse
Good deal. Do u happen have any links to mods or did u create them yourself?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Smith7018 said:
Awesome! You can technically flash mods; I flashed the iOS emoji mod so now my hangout messages don't have the ugly Google ones :victory:
Click to expand...
Click to collapse
This is exactly why I've rooted my watch! Well, that and the Gohma ROM.
The issue I'm having is pushing the .zip file to the sdcard. Getting an error saying it's read-only. Can't do it via adb because the second I boot into CWM my laptop forgets it's connected to anything.
PlayfulGod said:
Why just booting it via fastboot instead of flashing it?
and have you push your device tree to github??
Click to expand...
Click to collapse
It's only booting because it doesn't work when flashed to recovery. The file size is around 8 mb whereas the legitimate recovery is 23 mb, which I'm sure is an issue. Is it possible that I'm only creating a ramdisk that gets paired with the watch's kernel and I need to make an image with both of them? Sorry, this whole uBoot stuff confuses me a bit.
PlayfulGod said:
just zipping your device tree and uploading it would work too.
And how you build a recovery and git look skeery?? lol
Click to expand...
Click to collapse
Heh, I'm not actually afraid of git, I guess, I'm afraid of the whole "making a device-specific git repo that can be easily pulled while building CM." I guess I just don't have the time atm to set it up properly, but dw, I'll get to it this weekend! :fingers-crossed:
dude1981 said:
Good deal. Do u happen have any links to mods or did u create them yourself?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well, the iOS mod is something I downloaded awhile ago for my N5. I'm afraid I don't have the link anymore. Sorry, man.
Pepski said:
This is exactly why I've rooted my watch! Well, that and the Gohma ROM.
The issue I'm having is pushing the .zip file to the sdcard. Getting an error saying it's read-only. Can't do it via adb because the second I boot into CWM my laptop forgets it's connected to anything.
Click to expand...
Click to collapse
Try pushing the zip to the sd card while it's normally booted and then restart. I think that's what I did, IIRC.
Smith7018 said:
Try pushing the zip to the sd card while it's normally booted and then restart. I think that's what I did, IIRC.
Click to expand...
Click to collapse
Getting:
Code:
C:\fastboot>adb push emoji.zip \sdcard
failed to copy 'emoji.zip' to '\sdcard': Read-only file system
This was just done while the watch is booted normally and plugged in via USB. It almost seems as though the root permission hasn't worked. I'm at a loss.
Pepski said:
Getting:
Code:
C:\fastboot>adb push emoji.zip \sdcard
failed to copy 'emoji.zip' to '\sdcard': Read-only file system
This was just done while the watch is booted normally and plugged in via USB. It almost seems as though the root permission hasn't worked. I'm at a loss.
Click to expand...
Click to collapse
Weird... I don't even think you need root to push to /sdcard/ but I could be wrong. I'd suggest trying /sdcard/emoji.zip so it knows where to resolve. Also, I don't use Windows, but does the backslash work on adb as a file separator?
what happened to development on this?