Related
You can hack your PS3 with your evo. Please refer to http://forum.xda-developers.com/showthread.php?t=778202 for the files and informations....
Some points of interest.
1) If you run any rom but fresh, your evo will freeze during the white loading screen, its normal, it will still do the hack. (have not verified myself, I run cyanogen and it freezes on white loading screen, still hacked my ps3)
2) You must have Amon Ra 1.8 or higher or the latest Clockwork Recovery or else you cannot flash the hack to your phone. It will give a digest error.
3) You must have firmware 3.41 installed on your PS3, not 3.15 not 3.42. If you have any other firmware, your ps3 just will not show anything on the screen. If the hack is installed correctly, it will take about 10 seconds, no more.
In order to install firmware 3.41 you can download it from PS3 - Hacks - firmware 3.41 and then visit Playstations Website for installation directions. In order to learn how to update your ps3 WITHOUT doing an auto update which WILL MAKE SURE YOU CANNOT INSTALL THE HACK.
4) Whatever device you load the backup manager package on, will be the only device you can do add backups to. IE: if you load backup manager on your evo in USB storage mode, you will only be able to back up to your evo. I suggest, swallowing 100 bucks and getting an external drive, install device manager to that, then do all your backups to the drive. ORRRRRRRR Buy a 2.5 terabyte drive and install it internally to your ps3.
5) Now instead of a nandrestore there is a disable file you can flash. Check out http://wiki.psfreedom.com/wiki/HTC_EVO
--------------------- Instructions for installing PSfreedom hack with your EVO ---------------------------
1) Bakckup your nandroid then Flash the zip to your evo
2) Reboot your evo (most likely will freeze on reboot, its normal)
3) Make sure you have Firmware 3.41 on your PS3, if not, use an SD card, DVD, or Flash Drive to install the proper firmware.
4) Unplug your power cable to the ps3
5) Plug your EVO into the PS3 via USB cable
6) Plug in your ps3 power cable
7) Press the power buttom immediately followed by the eject button on your ps3 (will beep twice)
8) Wait no longer than 60 seconds for your ps3 to boot, if it does not, refer to the above information about firmwares and files.
9) Once the PS3 boots go to the game menu, and look for install packages.
10) Flash the disable zip file or do a nand restore to your evo.
If you have the option to install packages, its official! You are hacked.
kamitsuna said:
5) Once you have installed Backup Manager to your permanent storage solution, you WILL NOT NEED TO USE YOUR EVO to boot your ps3 anymore. You only need this hack in order to install unsigned code. Once the code is installed, its there permanently. (Have not verified myself).
Definitely NOT true, you will need to have the device plugged in every time.
Click to expand...
Click to collapse
kamitsuna said:
You can hack your PS3 with your evo. Please refer to http://forum.xda-developers.com/showthread.php?t=778202 for the files and informations....
Some points of interest.
1) If you run any rom but fresh, your evo will freeze during the white loading screen, its normal, it will still do the hack. (have not verified myself, I run cyanogen and it freezes on white loading screen, still hacked my ps3)
2) You must have Amon Ra 1.8 or higher or the latest Clockwork Recovery or else you cannot flash the hack to your phone. It will give a digest error.
3) You must have firmware 3.41 installed on your PS3, not 3.15 not 3.42. If you have any other firmware, your ps3 just will not show anything on the screen. If the hack is installed correctly, it will take about 10 seconds, no more.
In order to install firmware 3.41 you can download it from PS3 - Hacks - firmware 3.41 and then visit Playstations Website for installation directions. In order to learn how to update your ps3 WITHOUT doing an auto update which WILL MAKE SURE YOU CANNOT INSTALL THE HACK.
4) Whatever device you load the backup manager package on, will be the only device you can do add backups to. IE: if you load backup manager on your evo in USB storage mode, you will only be able to back up to your evo. I suggest, swallowing 100 bucks and getting an external drive, install device manager to that, then do all your backups to the drive. ORRRRRRRR Buy a 2.5 terabyte drive and install it internally to your ps3.
5) Once you have installed Backup Manager to your permanent storage solution, you WILL NOT NEED TO USE YOUR EVO to boot your ps3 anymore. You only need this hack in order to install unsigned code. Once the code is installed, its there permanently. (Have not verified myself).
6) Now instead of a nandrestore there is a disable file you can flash. Check out http://wiki.psfreedom.com/wiki/HTC_EVO
--------------------- Instructions for installing PSfreedom hack with your EVO ---------------------------
1) Bakckup your nandroid then Flash the zip to your evo
2) Reboot your evo (most likely will freeze on reboot, its normal)
3) Make sure you have Firmware 3.41 on your PS3, if not, use an SD card, DVD, or Flash Drive to install the proper firmware.
4) Unplug your power cable to the ps3
5) Plug your EVO into the PS3 via USB cable
6) Plug in your ps3 power cable
7) Press the power buttom immediately followed by the eject button on your ps3 (will beep twice)
8) Wait no longer than 60 seconds for your ps3 to boot, if it does not, refer to the above information about firmwares and files.
9) Once the PS3 boots go to the game menu, and look for install packages.
10) Flash the disable zip file or do a nand restore to your evo.
If you have the option to install packages, its official! You are hacked.
Click to expand...
Click to collapse
i appreciate your help to the community and i have implemented some of it into my thread but some of the info you posted is wrong such as device manager, i believe you mean back up manager and that is not true that you need to install it on there. Anyway, thanks for the help, i have added it to my post, but i dont think this thread belongs here, more like answers part of forum.
#5 sounds wrong. I doubt the PS3 will ever run your unsigned code without the PSFreedom hack enabled by the Evo at every bootup, even if successfully installed on a previous boot.
WIIWONWON said:
kamitsuna said:
5) Once you have installed Backup Manager to your permanent storage solution, you WILL NOT NEED TO USE YOUR EVO to boot your ps3 anymore. You only need this hack in order to install unsigned code. Once the code is installed, its there permanently. (Have not verified myself).
Definitely NOT true, you will need to have the device plugged in every time.
Click to expand...
Click to collapse
beat me to it as i was typing lol, i added a little bit of his post.
Click to expand...
Click to collapse
That is possible, Backup Manager will remain installed i guess but will no longer function.
Post has been edited to reflect this.
It also makes the evo a fairly useless way to hack your ps3. 15 minutes to turn on your ps3...bleh
In any case, thanx for correcting me guys. Im no developer, i just know all the questions i ran into, and they happen to be the same questions people keep asking. Figured id try to keep it simple.
Good info (seems to be copied and pasted from the PSFREEDOM thread).. I'm sure we will see this skip to QnA tho. Question is even in the title
iitreatedii said:
i appreciate your help to the community and i have implemented some of it into my thread but some of the info you posted is wrong such as device manager, i believe you mean back up manager and that is not true that you need to install it on there. Anyway, thanks for the help, i have added it to my post, but i dont think this thread belongs here, more like answers part of forum.
Click to expand...
Click to collapse
Is it necessary to quote the entire first post?
Sent from my badass, superfast evo; over the fastest, cheapest, best coverage-having network.
So i got the ps3 to come up with the "install package files", so i know i'm hacked, but now what do I do? Do I have to hit install packages or what? Thanks in advance
Edit: Also where can I get backup manager?
barnacles10 said:
Good info (seems to be copied and pasted from the PSFREEDOM thread).. I'm sure we will see this skip to QnA tho. Question is even in the title
Click to expand...
Click to collapse
To clarify, the info in the psfreedom thread, is copy and pasted from here, as stated above.
So i got the ps3 to come up with the "install package files", so i know i'm hacked, but now what do I do? Do I have to hit install packages or what? Thanks in advance
Edit: Also where can I get backup manager?
Click to expand...
Click to collapse
You can now install package files. Google for backup manager.
I see no point on using my phone to play games on the PS3... why not to make it work with old phones (the ones that you just use as a paper weight). I have two PS3's at home and believe me I still see no point on using my evo to play games on the ps3 hehe. Don't get me wrong, I like the idea but, what about if somebody calls you and you are playing.
This will be much more streamlined when a psfreedom AMON_RA is released for our phones. Then you can just open Rom manager, click boot into Recovery, and hack the ps3, then reboot and you phone is normal again.
At that time, Bart will be my hero. (even more)
technically you rent using it to play games youa re using yor phone to put your ps3 in dev mode. while in dev mode you can play games (if you install back up mamager) or use homebrew apps with out the aid of your phone once in dev mode.. Personally i still think it is a hassle and i think Sony will crack down on those they can catch. It is kind of a pain to have to flash your phone start your ps3 and either flash or annd restore your phone back each time you want to power on your ps3 and use it in dev mode (which is needed to play the back ups).
just me. I am sure the kiddies that have nothing better to do and no jobs will love this and wont mind though.
gatorran said:
I see no point on using my phone to play games on the PS3... why not to make it work with old phones (the ones that you just use as a paper weight). I have two PS3's at home and believe me I still see no point on using my evo to play games on the ps3 hehe. Don't get me wrong, I like the idea but, what about if somebody calls you and you are playing.
Click to expand...
Click to collapse
You dont have to leave your phone plugged in. Once the ps3 has booted up you can remove it. takes 10 seconds.
Guys this literally takes 5 minutes.
-flash the enabler
-plug phone into ps3
-unplug ps3
-plug in ps3
-power on then hit eject
-unplug phone and restore from nandroid
Piece of cake.
then you wait 10 minutes while your phone finishes restoring. thats also assuming you are ok with the nand back up you have and havent changed anything since you made it if you have you either have to manually make the changes or make a nand back up first. 5 minutes is now 15-25. and that is EVERY time you turn on the ps3. is it cool that you can do it sure, is it hard to do no it isnt, but if you find this as an optimal solution or even a sustainable one then i don't know what to tell you.
omegasun18 said:
then you wait 10 minutes while your phone finishes restoring. thats also assuming you are ok with the nand back up you have and havent changed anything since you made it if you have you either have to manually make the changes or make a nand back up first. 5 minutes is now 15-25. and that is EVERY time you turn on the ps3. is it cool that you can do it sure, is it hard to do no it isnt, but if you find this as an optimal solution or even a sustainable one then i don't know what to tell you.
Click to expand...
Click to collapse
Im playing tiger woods while my phone restores so I dont pay attention to how long it takes. Im sure there will be a much simpler solution in the future but this one works perfectly fine for me.
how do you install psfreed recovery .img??
I know that it says by fastboot, but are there any step by step instruction? thanks for the help
After much debate I have decided to make my work public as a lot of people seem to want these features!
THIS IS AN ALPHA SOFTWARE! EXPECT BUGS!
THEREFORE IF YOU INSTALL, ITS YOUR CHOICE. I TAKE NO RESPONSIBILITY IF THINGS GO DOWN THE PAN!
To get this working well, I need you guys! The testers - the community!
TFU ROM UPGRADE PACK ALPHA 3
What is it?
This software pack will supply your STOCK UK nook with software 1.2.0 with the following features:
ROOT
BUSYBOX
ADB
A clean nook friendly interface
A custom kernel (Thanks guevor http://forum.xda-developers.com/showthread.php?t=1906507)
Multitouch
Browser, Email, PDF, News Feed, Lots of tools
A custom built video mod to improve multitouch speed, refresh rates, delay and general display performance
MORE (but I cant remember)
Follow this guide to backup your nook and find out everything you need to know about the process. Please do this BEFORE any other tinkering! Make sure you know what you are doing!
http://forum.xda-developers.com/showthread.php?t=1961835
How to Install
Make a CWM SD card:
http://forum.xda-developers.com/showthread.php?t=1360994
Flash my zip:
http://dl.dropbox.com/u/13673492/TFU_ALPHA3.zip
Reboot:
You now have everything you need to get started!
BUGS:
Cant install apps unless you use ADB or drop them into /data/app and install.
If some of the preinstalled apps don't work follow this procedure:
-Open nook color tools and disable/enable allow non-market apps.
-Use file explorer to browse to /data/app and click on and install the broken app.
If you need help with ADB or want a different way to root check out my other post here!
http://forum.xda-developers.com/showthread.php?t=1961835
If you find a bug let me know please!
RESERVED
Hi Loney,
Installed just now and all seems well so far - well done!
John
I'd like to suggest an addition to the backup method that many folks are using - always test your restore, but dont test it (the first time) on your device.
Your backup file should be about 2 gig.
find a 2 gig or larger flash drive or sdcard and restore your backup image to that drive.
when you're done, there should be 8 partitions, as there were on your Nook to begin with.
If you can't get that working - you're not ready to root yet. Until you're sure you can restore, don't start making changes, please.
People turn up all the time having screwed themselves over by restoring a partial backup and not knowing it, or having restored only one partition from a complete backup and having blown out the partition table.
Out of curiosity is this listed as Glow only just because that was all you had to test it on?
I have the non-glow version so was going to test it, is there any reason why this may be a bad idea or has anyone else tried this yet? Thanks
stelph said:
Out of curiosity is this listed as Glow only just because that was all you had to test it on?
I have the non-glow version so was going to test it, is there any reason why this may be a bad idea or has anyone else tried this yet? Thanks
Click to expand...
Click to collapse
You are spot on. I didn't want to cause problems for people. Is your firmware 1.2.0? its firmware differences which are most likely to cause a problem. If you have a good backup, give it a go. If it works great. If not, you could try sending me your framework.jar file and I can try and find out what the differences are. Good luck!
roustabout said:
I'd like to suggest an addition to the backup method that many folks are using - always test your restore, but dont test it (the first time) on your device.
Your backup file should be about 2 gig.
find a 2 gig or larger flash drive or sdcard and restore your backup image to that drive.
when you're done, there should be 8 partitions, as there were on your Nook to begin with.
If you can't get that working - you're not ready to root yet. Until you're sure you can restore, don't start making changes, please.
People turn up all the time having screwed themselves over by restoring a partial backup and not knowing it, or having restored only one partition from a complete backup and having blown out the partition table.
Click to expand...
Click to collapse
Thanks for posting this. Very useful for people who aren't familiar with the nook. I will mention your name and this post when I update my guide with this information.
Also, the US nook touches - both the NST and NSTG - are now going to be running under OS 1.2.0 per BN.
The BN support announcement on this is here:
http://www.barnesandnoble.com/u/Software-Updates-NOOK-Simple-Touch/379003175
Hopefully, we'll wind up with net fewer folks quasi bricking their devices.
roustabout said:
Also, the US nook touches - both the NST and NSTG - are now going to be running under OS 1.2.0 per BN.
The BN support announcement on this is here:
http://www.barnesandnoble.com/u/Software-Updates-NOOK-Simple-Touch/379003175
Hopefully, we'll wind up with net fewer folks quasi bricking their devices.
Click to expand...
Click to collapse
This is great news. Everyone will benefit from some constancy across all devices.
Thanks, yes my nook is 1.2.0 so I've now installed the ROM on my non-glow light and it looks like it works fine! Seems stable and could start using it straight away, the only fault was opera wouldn't load/didint install properly but I followed the guide and re-installed it and it now works
I think the simple layout is really great, although one question, I plan to add the kindle app. Will I be able to add it to the "book" symbol (ie when I press the reading book it'd be nice to get an option of barnes&noble or kindle)? Im sure there is probably a legal reason why it hasnt but i think a kindle app would be good to include as standard, since kindle is one of the most popular ebook services and I bet most people have some books they'd want to access
Great work on the ROM!
stelph said:
Thanks, yes my nook is 1.2.0 so I've now installed the ROM on my non-glow light and it looks like it works fine! Seems stable and could start using it straight away, the only fault was opera wouldn't load/didint install properly but I followed the guide and re-installed it and it now works
I think the simple layout is really great, although one question, I plan to add the kindle app. Will I be able to add it to the "book" symbol (ie when I press the reading book it'd be nice to get an option of barnes&noble or kindle)? Im sure there is probably a legal reason why it hasnt but i think a kindle app would be good to include as standard, since kindle is one of the most popular ebook services and I bet most people have some books they'd want to access
Great work on the ROM!
Click to expand...
Click to collapse
In my next update you will be able to customise the launcher as you like. The fact that you cant is a bug that can be fixed by clearing the launcher data using the included titanium backup program.
Since i'm back from the hell of the "bricked nook", now i can come back to test your mod with more understanding.
It seems that if we change the language to all but english, the installation of the mod is doomed to a blank launcher. (that was the case for registering the nook i have to do it in english).
I reflash my nook after setting it in english and that correctly installs everything (not Opera but that's easy to recover it).
may be a note for foreigners who try to install this mod is to be aware of keeping the nook in shakespeare's mother tongue.
would you mind integrating in your future version the manga reader "perfect viewer"? fastmode.apk is also a request but now i understand that is not so easy.
thanks for your contribution. :highfive:
I'll report my experience using this technique. A few days ago, I purchased a US Nook Simple Touch (non-glow) which came with software v.1.0. I made a backup using the method referenced in the OP. I then upgraded to software v.1.2 via the manual (USB mode) method shown at http://www.barnesandnoble.com/u/Software-Updates-NOOK-Simple-Touch/379003175/ . I made another backup. I verified both backups using the SD card method as suggested by roustabout. Everything looked good.
I followed the OP instructions and was successful in installing TFU_ALPHA3.zip with CWM.
Upon reboot of the NST, I saw a dialog chooser asking me to select either the standard Nook software or Launcher7. I first tried Launcher7 and was greeted with a large gray "n" background. Nothing else. The only button that had functionality was the "n" button which brought up the "home" menu at the bottom of the screen. This got me back to the standard Nook software. So at least the reader still worked.
I rebooted and tried Launcher7 again, just to be sure. Still nothing but the large gray "n" background. No apps.
I restored my v.1.2 backup without any problems, and am now back to a "stock" NST. All good.
So while the TFU_ALPHA3.zip installation proceeded without incident, I didn't see any apps that I could run from Launcher7. I guess I'll have to try a different technique.
it seems like the same problem i said in my previous topic. did you set your language to anything but english?
i had the launcher7 without anything loaded. I had to set the language in english then reinstall the TFUAlpha3 to make it work correctly.
hope it helps.
jjinkou2 said:
it seems like the same problem i said in my previous topic. did you set your language to anything but english?
Click to expand...
Click to collapse
I have the US version of the NST. I couldn't find any way to change the language in the settings.
fastmode is working but we have to set it manually. i read this here http://forum.xda-developers.com/showthread.php?t=1241419, and i tested it.
Code:
adb shell
# cd /sys/class/graphics/fb0/
# echo -n 1 > fmode
# echo -n 0 > pgflip_refresh
since no-refresh and fastmode are autoexclusive i set pgflip_refresh to 0.
values are lost when the nook reboots.
New version coming soon. Lets start a list of requests guys. And if anyone has tested custom graphics settings, what works for you?
Loney,
Things that aren't working for me:
* Launcher 7 settings can't be altered (changes don't "save")
* apk installs are hitty-missy. Sometimes moving an apk into /data/apps and rebooting will work, other times I need to install it again by clicking on it in a file explorer.
* Fast mode app does nothing (but we knew that...)
Other than that, all is cool. I have also installed the patched .jars from the "mod manager" thread and they work alongside your changes.
Well done for your efforts on our behalf. Shout if you want anything specific testing - I'm confident that I can recover from "bricking"!
John
loney01843 said:
New version coming soon. Lets start a list of requests guys.
Click to expand...
Click to collapse
I haven't tried this yet, but when I do I would imagine access to google markets would be needed.
A follow-up on my experience which may (or may not) help getting this to work with the US NST (non-glow). Yesterday, I decided to give GlowNooter (http://forum.xda-developers.com/showthread.php?t=1675706) a try. Suspecting that it wouldn't work out-of-the-box, I deleted /system/framework/framework.jar from the glownooter.zip file. Installation of the .zip succeeded, and I was able to run ADW Launcher. I added my account to YouTube, attempted to sync in GMail, rebooted, and installed the PART-2-END.zip. Then I tried to open up Market, but kept getting connection errors. I also tried the Browser app, but was unable to enter text into Google's search page. So I guess there is stuff in glownooter's framework.jar file that is needed for everything to work. I didn't try too much more.
Anyway, I reverted to the stock NST 1.2 software for now. But I am happy to help with testing new firmware since I'm pretty confident about restoring to stock software.
I have a list of things that I want to do for my flo, and I have no clue where to start.I actually don't even know if this is the correct forum to ask this in, but here goes.
1. I want to be able to use an external WiFi adapter android, and looped Linux images, how can I do this? From everything I've read it seems it starts with including drivers in your kernel for the WiFi adapter. How do I do this? I've read around 10 different tutorials and each are different.
2. I can mount a Linux image inside of android and run it, that's cool, but slow and ineffective. I want to boot into Linux and kiss android goodbye Why do we have to use vnc to connect to the GUI instead of just starting one up? Is it simply because a lack of drivers that connect the GUI to the hardware?. I know that there isn't a version of Linux that will boot on the flo, so why can't I make one? My problem is I don't know where to start. What part of android or Linux has he be coded/compiled differently to work. There are many images that are based on the arm instructions, why is it not possible to just put extract that image and mount it to boot? I believe that a kernel is somewhat of a bridge between the software and firmware, but I don't know what has to change in any of it. I would like to start with a basic non-gui flavor of Linux, then worry about gnome or KDE later.
Any help in the right direction is greatly appreciated. I taught myself JavaScript and HTML back in the 90's just so I could start my own website and say I built it myself. I can learn, I just don't know what I need to learn. Everyone has to start somewhere, I say go big or go home.
Bump
Sent from my Nexus 7 using xda app-developers app
So I have an Optimus G LS970, added a couple apps, but other than that it's pretty basic. I'm wanting to root this device and eventually add a custom rom on it perhaps, but I've very new to this and don't want to accidentally brick my device.
1) I've been looking for stable linux rooting methods, the only one I've found that looks promising is here, but it's 2 years old. Does anyone know anything about it's stability for android 4.1.2, kernel 3.4.0?
2) In order to transfer files (music, pictures, pdfs/ebooks) to/from my device it needs to be mounted, but I haven't been able to mount it for this (or any other) purpose at all. It shows up as connected (command "lsusb" shows "Bus 002 Device 028: ID 1004:631d LG Electronics, Inc.") but it won't mount. Will this be possible once rooted, or is there some other cause to this?
3) Once rooted, I want to get rid of some of the Preinstalled apps but I'm not sure which will lead to instability and which would be fine to remove, does anyone know where I can check this, or would I just need to list all the apps I don't want on my phone and have you all tell me on an app-by-app basis which is safe to remove?
4) Lastly, when it comes to using alternative app markets, I haven't had much luck. I was trying to test using alt stores with f-droid and nothing showed in the lists, so I don't know if that's a thing with f-droid or my device. Is there anything you need to do to use alt app stores aside from enabling it in the system settings, and installing the app store's .. app?
Thanks in advance!
JustAk said:
So I have an Optimus G LS970, added a couple apps, but other than that it's pretty basic. I'm wanting to root this device and eventually add a custom rom on it perhaps, but I've very new to this and don't want to accidentally brick my device.
1) I've been looking for stable linux rooting methods, the only one I've found that looks promising is here, but it's 2 years old. Does anyone know anything about it's stability for android 4.1.2, kernel 3.4.0?
2) In order to transfer files (music, pictures, pdfs/ebooks) to/from my device it needs to be mounted, but I haven't been able to mount it for this (or any other) purpose at all. It shows up as connected (command "lsusb" shows "Bus 002 Device 028: ID 1004:631d LG Electronics, Inc.") but it won't mount. Will this be possible once rooted, or is there some other cause to this?
3) Once rooted, I want to get rid of some of the Preinstalled apps but I'm not sure which will lead to instability and which would be fine to remove, does anyone know where I can check this, or would I just need to list all the apps I don't want on my phone and have you all tell me on an app-by-app basis which is safe to remove?
4) Lastly, when it comes to using alternative app markets, I haven't had much luck. I was trying to test using alt stores with f-droid and nothing showed in the lists, so I don't know if that's a thing with f-droid or my device. Is there anything you need to do to use alt app stores aside from enabling it in the system settings, and installing the app store's .. app?
Thanks in advance!
Click to expand...
Click to collapse
All of your questions are answered here. http://forum.xda-developers.com/showthread.php?t=2050582
And the FAQ.
1. See above
2. Install the LG drivers, link is in that OP, then tick MPT. That should transfer your files. If not, you may need to uninstall, then reinstall them.
3. DO NOT remove any apps unless you unlock! Info is in that link also.
4. I have no idea on that one.
Sent from my LG-LS970 using XDA Premium 4 mobile app
engine95 said:
All of your questions are answered here. http://forum.xda-developers.com/showthread.php?t=2050582
And the FAQ.
1. See above
2. Install the LG drivers, link is in that OP, then tick MPT. That should transfer your files. If not, you may need to uninstall, then reinstall them.
3. DO NOT remove any apps unless you unlock! Info is in that link also.
4. I have no idea on that one.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
1) *EDIT* [Doesn't say anything about linux rooting, how am I supposed to install a windows drive on a linux system?] I overlooked the linux mention. Thanks! Can't find something. How/where do I find adb?
2) Ignore, see 1) [Again, how am I supposed to install the Windows driver in linux?]
3) Thanks for that. I didn't know the importance of unlocking the bootloader.
JustAk said:
1) *EDIT* [Doesn't say anything about linux rooting, how am I supposed to install a windows drive on a linux system?] I overlooked the linux mention. Thanks! Can't find something. How/where do I find adb?
2) Ignore, see 1) [Again, how am I supposed to install the Windows driver in linux?]
3) Thanks for that. I didn't know the importance of unlocking the bootloader.
Click to expand...
Click to collapse
Sorry bout that. Linux drivers are native, so they're anyway installed.
You use either fiddy629 root for Linux, or Framaroot.
Sent from my LG-LS970 using XDA Premium 4 mobile app
---------- Post added at 10:53 PM ---------- Previous post was at 10:51 PM ----------
Edit. You don't have to have ADB, but there's alot of info if you google it.
Sent from my LG-LS970 using XDA Premium 4 mobile app
engine95 said:
Sorry bout that. Linux drivers are native, so they're anyway installed.
You use either fiddy629 root for Linux, or Framaroot.
Sent from my LG-LS970 using XDA Premium 4 mobile app
---------- Post added at 10:53 PM ---------- Previous post was at 10:51 PM ----------
Edit. You don't have to have ADB, but there's alot of info if you google it.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried fiddy619's thing here using the universal linux one. It asked me for ADB. Found that debian has "android-tools-adb" so I installed that, now there's this:
Code:
Using: /usr/bin/adb
Waiting for device... Connect your LGOG via USB in Charge Only Mode
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Device found
Beginning Root Process
Disconnect your phone from USB
Disable USB Debugging
Enable USB Debugging
Press enter to Continue
I can't tell if this is telling me to do these things, or if it's saying it already did them. Any idea?
JustAk said:
I tried fiddy619's thing here using the universal linux one. It asked me for ADB. Found that debian has "android-tools-adb" so I installed that, now there's this:
Code:
Using: /usr/bin/adb
Waiting for device... Connect your LGOG via USB in Charge Only Mode
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Device found
Beginning Root Process
Disconnect your phone from USB
Disable USB Debugging
Enable USB Debugging
Press enter to Continue
I can't tell if this is telling me to do these things, or if it's saying it already did them. Any idea?
Click to expand...
Click to collapse
Nevermind that, I got it working just fine. took o nly a couple seconds and it was done. Now I have "SuperSU" in my apps menu, so I'm guessing it worked.
JustAk said:
Nevermind that, I got it working just fine. took o nly a couple seconds and it was done. Now I have "SuperSU" in my apps menu, so I'm guessing it worked.
Click to expand...
Click to collapse
Awesome, glad to hear it worked! Which if you have SuperSU it should have. I too only use linux(Linux Mint specifically) and while most guides are made for Windows, things are usually easier from the linux terminal because we don't need to download drivers, android uses a modified linux kernel, etc. Welcome to the forums, glad to have you here! All the info you need is here and plenty of people will be glad to help(as engine has already demonstrated). As for the alternative app markets, Ive read plenty and tested a few but really, nothing comes close to the play store. On our phone Banks Gapps is the standard google apps package to install if you are flashing a custom rom. Just make sure you get the correct version of gapps for the version of android your rom is based on.
HPTesla said:
Awesome, glad to hear it worked! Which if you have SuperSU it should have. I too only use linux(Linux Mint specifically) and while most guides are made for Windows, things are usually easier from the linux terminal because we don't need to download drivers, android uses a modified linux kernel, etc. Welcome to the forums, glad to have you here! All the info you need is here and plenty of people will be glad to help(as engine has already demonstrated). As for the alternative app markets, Ive read plenty and tested a few but really, nothing comes close to the play store. On our phone Banks Gapps is the standard google apps package to install if you are flashing a custom rom. Just make sure you get the correct version of gapps for the version of android your rom is based on.
Click to expand...
Click to collapse
Ah. brilliant, thanks!
The only problem I'm now having is getting the phone to connect to my computer so I can transfer music or ebooks or whathaveyou to/from my device. I've gone through the arch wiki for android (even though I'm running debian) and this forum postt but I keep getting an error:
Code:
$ android-connect
Listing raw device(s)
Device 0 (VID=1004 and PID=61f9) is a LG Electronics Inc. V909 G-Slate.
Found 1 device(s):
LG Electronics Inc.: V909 G-Slate (1004:61f9) @ bus 2, dev 8
Attempting to connect device
PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
Android device detected, assigning default bug flags
Error 1: Get Storage information failed.
Error 2: PTP Layer error 02fe: get_handles_recursively(): could not get object handles.
Error 2: (Look this up in ptp.h for an explanation.)
Listing File Information on Device with name: (NULL)
LIBMTP_Get_Storage() failed:-1
I can start a separate thread regarding this issue, but if you have any insight, figured it couldn't hurt to ask real quick.
JustAk said:
Ah. brilliant, thanks!
The only problem I'm now having is getting the phone to connect to my computer so I can transfer music or ebooks or whathaveyou to/from my device. I've gone through the arch wiki for android (even though I'm running debian) and this forum postt but I keep getting an error:
Code:
$ android-connect
Listing raw device(s)
Device 0 (VID=1004 and PID=61f9) is a LG Electronics Inc. V909 G-Slate.
Found 1 device(s):
LG Electronics Inc.: V909 G-Slate (1004:61f9) @ bus 2, dev 8
Attempting to connect device
PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
Android device detected, assigning default bug flags
Error 1: Get Storage information failed.
Error 2: PTP Layer error 02fe: get_handles_recursively(): could not get object handles.
Error 2: (Look this up in ptp.h for an explanation.)
Listing File Information on Device with name: (NULL)
LIBMTP_Get_Storage() failed:-1
I can start a separate thread regarding this issue, but if you have any insight, figured it couldn't hurt to ask real quick.
Click to expand...
Click to collapse
This may or may not help, but when I've had issues with Linux hooking up I've had to format my SD. Something gets stuck in there that Linux just didn't like.
Sent from my LG-LS970 using XDA Premium 4 mobile app
JustAk said:
Ah. brilliant, thanks!
The only problem I'm now having is getting the phone to connect to my computer so I can transfer music or ebooks or whathaveyou to/from my device. I've gone through the arch wiki for android (even though I'm running debian) and this forum postt but I keep getting an error:
Code:
$ android-connect
Listing raw device(s)
Device 0 (VID=1004 and PID=61f9) is a LG Electronics Inc. V909 G-Slate.
Found 1 device(s):
LG Electronics Inc.: V909 G-Slate (1004:61f9) @ bus 2, dev 8
Attempting to connect device
PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
Android device detected, assigning default bug flags
Error 1: Get Storage information failed.
Error 2: PTP Layer error 02fe: get_handles_recursively(): could not get object handles.
Error 2: (Look this up in ptp.h for an explanation.)
Listing File Information on Device with name: (NULL)
LIBMTP_Get_Storage() failed:-1
I can start a separate thread regarding this issue, but if you have any insight, figured it couldn't hurt to ask real quick.
Click to expand...
Click to collapse
Are you doing this with the phone turned on and booted into the os? It gives you a PTP error first, make sure the phone is in MTP. At the bottom you also have a LIBMTP error tho. I don't have much experience with debian but from what I understand it is extremely stable but the downside is that it can be a bit out of date at times. Ubuntu and all ubuntu derivatives had a major mtp flaw awhile back but it has since been fixed. Im not sure if it has been fixed in debian. Yes ubuntu is based off of debian, but just like linux mint will add things to the ubuntu base, ubuntu will do the same to the debian base. So LIBMTP MAY be out of date, Im not sure. I know that I have no problem seeing my phone from either the terminal or file browser. Check this out and see if it helps any.
If not you may have to follow engine's advice and format the sd.
EDIT: Also this might work, it is for linux mint but adding the repository and installing it should work on debian(I think) since they all use .deb files. Before ubuntu officially supported mtp by default this was the most popular work around.
HPTesla said:
Are you doing this with the phone turned on and booted into the os? It gives you a PTP error first, make sure the phone is in MTP. At the bottom you also have a LIBMTP error tho. I don't have much experience with debian but from what I understand it is extremely stable but the downside is that it can be a bit out of date at times. Ubuntu and all ubuntu derivatives had a major mtp flaw awhile back but it has since been fixed. Im not sure if it has been fixed in debian. Yes ubuntu is based off of debian, but just like linux mint will add things to the ubuntu base, ubuntu will do the same to the debian base. So LIBMTP MAY be out of date, Im not sure. I know that I have no problem seeing my phone from either the terminal or file browser. Check this out and see if it helps any.
If not you may have to follow engine's advice and format the sd.
EDIT: Also this might work, it is for linux mint but adding the repository and installing it should work on debian(I think) since they all use .deb files. Before ubuntu officially supported mtp by default this was the most popular work around.
Click to expand...
Click to collapse
The first thing you linked to (steneteg.org or somesuch) was another avenue I went down trying to solve this, but alas it resulted with much the same problems. The second link to the linuxmint forums looked very promising, the only problem with it is the ppa has been dropped by webupd8 so it no longer is available (404s).
I have just discovered earlier today that adb push/pull works for getting things onto/off of my device, but I can't use adb to mount the device to allow it to be seen with a filemanager (thunar in this case). So, that's progress I think.
EDIT : I just saw mention somewhere of androidair, have yyou any experience with this app's reliability/security?
JustAk said:
The first thing you linked to (steneteg.org or somesuch) was another avenue I went down trying to solve this, but alas it resulted with much the same problems. The second link to the linuxmint forums looked very promising, the only problem with it is the ppa has been dropped by webupd8 so it no longer is available (404s).
I have just discovered earlier today that adb push/pull works for getting things onto/off of my device, but I can't use adb to mount the device to allow it to be seen with a filemanager (thunar in this case). So, that's progress I think.
EDIT : I just saw mention somewhere of androidair, have yyou any experience with this app's reliability/security?
Click to expand...
Click to collapse
You can try searching for other places where go-mptfs is located, other ppas where it still might be. The ubuntu forums also has this as a possible solution. I haven't used androidair but I have moved files over wifi using the sshdroid app and an ssh server on my pc with great success. If you have any experience with ssh that could be a possible solution although it is obviously slower than usb. But ssh in general is a simple and great tool, also pretty secure since you are simply connected to your home wifi - as long as your wifi is secure you should be fine.
On my pc I believe its openssh that I use - plenty of tutorials out there for that - and here is the link to sshdroid in the play store. Hope this helps!
EDIT: I will also be at work until 2p.m. EST so may not be able to reply back until then - don't worry, I will as soon as I get home if you have any other issues.
I was going to wait for this device to be added to devdb to make a release thread, but that's being delayed, if it'll ever happen. So, I'm making this thread as a placeholder. No big fancy text, just a known problem list and the release. If you're looking for this, you probably know what to do with it. Everything should work from flashing to backup and restore from all external media. If it doesn't, please report it.
KNOWN PROBLEMS:
1. This is a multirom edition of twrp, but there's no multirom support yet.
2. My wireless keyboard / mouse combo (an old Logitech MX something or another) fails to initialize the mouse on boot. I have to unplug and replug the USB receiver for the mouse to work. My wired mouse doesn't do this. I'm curious if anyone else sees a similar problem or if there's something weird with my hardware.
SOURCE:
device (branch cm-12.1-mrom)
kernel
vendor
CURRENT RELEASE:
For Android M:
twrp-20160222-UNOFFICIAL-foster.img
Known Issue: This release does not work on 4K displays. It boots to a black screen. Please use a 1080p display for TWRP until this is fixed.
For Android L:
twrp-multirom-20151112-UNOFFICIAL-foster.img
OLD RELEASES:
twrp-multirom-20150630-UNOFFICIAL-foster.img
twrp-multirom-20150624-UNOFFICIAL-foster.img
twrp-multirom-20150613-UNOFFICIAL-foster.img
MultiRom will be a must have on this device.
I really appreciate your work, and reading the various thread on xda I found out that you're one of the best developers for Nvidia Shield devices.
Without people like you we would all be locked in a large digital cage.
Compliments
Thanks Steel01!
I'm starting to slowly look at what I can disable in the kernel to shrink it down enough to fit in the recovery partition. Unfortunately, my first two ideas, network and sound, can't be unilaterally removed due to the android USB gadget (used for adb) depending on them. I've got it down to 26 MB, but iI dont know if it still boots. I'll try a few more things and hopefully have something working in the next couple days. I'm also hoping Tasssadar merges the 2.8.7.0 changes soon, the resize functionality will be useful (in testing I somehow shrunk my user data partition to 11 GB and had to reformat it get the full 4?? GB back).
Or it could be quicker than I thought. Todays test was successful. It's small enough to barely fit in the partition and appears to work correct. The link is in the OP. The next update to the multirom TWRP will probably make it too big again and I'll have to rip some more stuff out...
I want to install twrp recovery on my 16gb Shield, but i have no need for multirom. Is there an option to bypass the boot option or should I wait for a standard TWRP?
You didn't take much of a break before going back at it again. Thanks for your dedication!
Well, I'm not going back at it fully yet. Next week and a half will likely be pretty busy. I'm just doing a piece here and there.
This TWRP has multirom support, but does not require it or even set it up by default. In fact, to enable multirom, you have to install a separate zip (which I haven't released because it doesn't work). So no, you won't see any extra boot screens with this.
A standard TWRP build should be simple to make with the sources I've linked in the OP. I haven't released one here (or on any device I support) because I don't want to support it directly (basically, I'm supporting what I use myself). If no one else makes one, I might make a one time build for those that want it.
Hi Steel01, thanks for your efforts. I am a rookie at best at this, however, I managed to get this installed to my 16 gb shield tv, all appears to work fine, except I am unable to pair the shield remote, the shield game controller paired fine, but not the remote, just curious is this is expected, or maybe something wrong on my end. Also, If I wanted to load another rom at some point, is it as simple as booting to the twrp screen and selecting install? Hope that doesn't sound like a dumb question, I'm just a little unsure of that exact process. thanks
Remote controller fix
cdsn99 said:
Hi Steel01, thanks for your efforts. I am a rookie at best at this, however, I managed to get this installed to my 16 gb shield tv, all appears to work fine, except I am unable to pair the shield remote, the shield game controller paired fine, but not the remote, just curious is this is expected, or maybe something wrong on my end. Also, If I wanted to load another rom at some point, is it as simple as booting to the twrp screen and selecting install? Hope that doesn't sound like a dumb question, I'm just a little unsure of that exact process. thanks
Click to expand...
Click to collapse
Do not worry and follow these simple steps to fix your remote controller problem:
This is quite normal after a system reset or wipe.
If the remote did not connect:
If the microphone symbol is not flashing, hold down the back and home buttons at the same time until it flashes (3 seconds).
If the microphone symbol does not flash after holding for 3 seconds, charge the remote and try again.
To charge the remote, connect it to one of the USB ports on the back of your SHIELD with the included USB cable or connect it to another USB power source.
---------- Post added at 06:08 AM ---------- Previous post was at 06:01 AM ----------
cdsn99 said:
Hi Steel01, . Also, If I wanted to load another rom at some point, is it as simple as booting to the twrp screen and selecting install? Hope that doesn't sound like a dumb question, I'm just a little unsure of that exact process. thanks
Click to expand...
Click to collapse
Yes with TWRP it is very easy to flash a new rom, it is also recommended to use the recovery roms for updating your system.
Instead of running the OTO updates because this will undo your Root modification and reinstall the original recovery partition.
Download the correct firmware from this forum from the nvidia developers network, place it on a SD card boot to recovery and flash.
As a final suggestion have a look at the Flashify utllity (not compatible yet) or similar from the appstore, that a simple front end for flashing & backing up boot and recovery partitions. And it will enable you to boot to recovery in one click.
I have TWRP running on my Shield Portable / Shield Tablet without any problems.
Enjoy
Josti-Band said:
Do not worry and follow these simple steps to fix your remote controller problem:
This is quite normal after a system reset or wipe.
If the remote did not connect:
If the microphone symbol is not flashing, hold down the back and home buttons at the same time until it flashes (3 seconds).
If the microphone symbol does not flash after holding for 3 seconds, charge the remote and try again.
To charge the remote, connect it to one of the USB ports on the back of your SHIELD with the included USB cable or connect it to another USB power source.
---------- Post added at 06:08 AM ---------- Previous post was at 06:01 AM ----------
Yes with TWRP it is very easy to flash a new rom, it is also recommended to use the recovery roms for updating your system.
Instead of running the OTO updates because this will undo your Root modification and reinstall the original recovery partition.
Download the correct firmware from this forum from the nvidia developers network, place it on a SD card boot to recovery and flash.
As a final suggestion have a look at the Flashify utllity (not compatible yet) or similar from the appstore, that a simple front end for flashing & backing up boot and recovery partitions. And it will enable you to boot to recovery in one click.
I have TWRP running on my Shield Portable / Shield Tablet without any problems.
Enjoy
Click to expand...
Click to collapse
Thanks Josti-Band , that fixed my remote, I appreciate it greatly. Thanks also for the info on flashing, I'm still have one more question, when I flashed the img file from this thread TWRP, did I change the rom or just the recovery? It seems like the rom is the original that was on the shield tv, If rom was not changed do you or anyone else have a recommendation. Thanks again for the assistance.
cdsn99 said:
Thanks Josti-Band , that fixed my remote, I appreciate it greatly. Thanks also for the info on flashing, I'm still have one more question, when I flashed the img file from this thread TWRP, did I change the rom or just the recovery? It seems like the rom is the original that was on the shield tv, If rom was not changed do you or anyone else have a recommendation. Thanks again for the assistance.
Click to expand...
Click to collapse
No Problem, Your Shield TV has basically 3 partitions (to keep it simple)
1) Boot
2) Recovery
3) OS/Data (Rom)
With the steps you have followed
a) you unlocked your 1) bootloader, to enable the installation of unsigned packages to make this possible your personal data was erased/wiped from the 3) OS/Data partition.
b) Then you applied a new TWRP image to the recovery partition an replacing the old one.
So your 3) OS/Data (Rom) is still the original one you only wiped the personal data clean when unlocking the bootloader, this also the partition you will write your updated recovery images to. And stay updated.
I have TWRP running on my Shield Portable / Shield Tablet without any problems.
Enjoy[/QUOTE]
Josti-Band said:
No Problem, Your Shield TV has basically 3 partitions (to keep it simple)
1) Boot
2) Recovery
3) OS/Data (Rom)
With the steps you have followed
a) you unlocked your 1) bootloader, to enable the installation of unsigned packages to make this possible your personal data was erased/wiped from the 3) OS/Data partition.
b) Then you applied a new TWRP image to the recovery partition an replacing the old one.
So your 3) OS/Data (Rom) is still the original one you only wiped the personal data clean when unlocking the bootloader, this also the partition you will write your updated recovery images to. And stay updated.
Click to expand...
Click to collapse
Thank you, that makes better sense, I will try and load a rom and gapps and see how it goes. thanks again for the assistance
Steel01 said:
2. My wireless keyboard / mouse combo (an old Logitech MX something or another) fails to initialize the mouse on boot. I have to unplug and replug the USB receiver for the mouse to work. My wired mouse doesn't do this. I'm curious if anyone else sees a similar problem or if there's something weird with my hardware.
Hi Steel01 , I have a logitech k400r wireless keyboard and mouse, it seemed to work ok, except was very laggy, had to wait for it a few seconds each time I went to move the mouse, and sometimes mouse would freeze.
Click to expand...
Click to collapse
I have edited and deleted the orginal text from this post,and moved it to it's own thread. I realized I was beginning to hijack steels thread, I couldn't find a way to just delete the whole post, sorry.
Tassadar merged TWRP 2.8.7.0 into his multirom twrp fork today. So I ran new builds for everything I support. Unfortunately, I have not been able to test this device (TV's been busy all night), so YMMV. The other builds came off fine, so I don't see why this one should have any problems the last build didn't. Of interest in this build is the partition resize feature. So if someone does something weird like I did and ends up with an 11 GB data partition on the pro, it'll be *much* easier and quicker to fix now. Build is in the OP.
Steel01 said:
Tassadar merged TWRP 2.8.7.0 into his multirom twrp fork today. So I ran new builds for everything I support. Unfortunately, I have not been able to test this device (TV's been busy all night), so YMMV. The other builds came off fine, so I don't see why this one should have any problems the last build didn't. Of interest in this build is the partition resize feature. So if someone does something weird like I did and ends up with an 11 GB data partition on the pro, it'll be *much* easier and quicker to fix now. Build is in the OP.
Click to expand...
Click to collapse
What about the kexec-hardboot patch ? Do you have already tried it ?
The others binary for multirom execution are the same for all arm64 devices like the nexus 9 or we need a specific build for shield ? I never played with multirom stuff. There are specific problems to solve ? In case i can help you with experiments if you don't have much time.
P.S.
I tried your patch for the framework and all others new Nvidia binary + resigned private apk like blakepairing and others. But this year Nvidia added many others things to the framework. You can see by yourself with dex2jar.
It's a shame that for a stupid controller there are all this bloatware inside the firmware. Very bad behaviour, that a so big company not publish drivers for an hardware that we have bought. Fortunately we can use also better wireless controllers. But this fact really remove 10000 points from Nvidia as good company.
I've worked very little on the multirom side of things. The kernel repo has a mrom branch with a kexec patch, which still boots to stock. However, there's something getting triggered in the multirom init program that is skipping the boot screen. I haven't tried to track that down yet.
The controller part is off-topic, but there isn't really anywhere else to discuss it yet. Maybe I'll open a CM thread for discussion and put not working in bold at the top. Anyways, the framework patches work with the blakepairing shipped with the Shield TV, that's what I ship with my portable and tablet builds. But you have to deodex and stuff the class file back in the apk. Or easier, use the one in my vendor repo and just resign it. That should at least run. On a side note, the underlying technologies are all open source. WiFi Direct, wps, hid, etc. It just a standard USB hid controller with a WiFi chip and USB sound card. It's driven by an xmega (iirc) as well, those are all pretty open. It's obfuscation atm that stops me from completely reimplementing the pairing open source.
Steel01 said:
I've worked very little on the multirom side of things. The kernel repo has a mrom branch with a kexec patch, which still boots to stock. However, there's something getting triggered in the multirom init program that is skipping the boot screen. I haven't tried to track that down yet.
The controller part is off-topic, but there isn't really anywhere else to discuss it yet. Maybe I'll open a CM thread for discussion and put not working in bold at the top. Anyways, the framework patches work with the blakepairing shipped with the Shield TV, that's what I ship with my portable and tablet builds. But you have to deodex and stuff the class file back in the apk. Or easier, use the one in my vendor repo and just resign it. That should at least run. On a side note, the underlying technologies are all open source. WiFi Direct, wps, hid, etc. It just a standard USB hid controller with a WiFi chip and USB sound card. It's driven by an xmega (iirc) as well, those are all pretty open. It's obfuscation atm that stops me from completely reimplementing the pairing open source.
Click to expand...
Click to collapse
Already tried all. deodexed and resigned stock stuff, also used your framework patch and your (resigned) apks . not work in shield console. as i write above in shield console there are others proprietary things in the framework. Tested also with your wpa_supplicant and hostapd but the result does not change.
In any way i will retry
We can discuss in a separate thread. sorry for off-topic. can be useful also for others developers
This is very interesting, please continue with this work! Would be great to get the remote working on other ROMs.
Thanks!
Steel01 said:
I've worked very little on the multirom side of things. The kernel repo has a mrom branch with a kexec patch, which still boots to stock. However, there's something getting triggered in the multirom init program that is skipping the boot screen. I haven't tried to track that down yet.
The controller part is off-topic, but there isn't really anywhere else to discuss it yet. Maybe I'll open a CM thread for discussion and put not working in bold at the top. Anyways, the framework patches work with the blakepairing shipped with the Shield TV, that's what I ship with my portable and tablet builds. But you have to deodex and stuff the class file back in the apk. Or easier, use the one in my vendor repo and just resign it. That should at least run. On a side note, the underlying technologies are all open source. WiFi Direct, wps, hid, etc. It just a standard USB hid controller with a WiFi chip and USB sound card. It's driven by an xmega (iirc) as well, those are all pretty open. It's obfuscation atm that stops me from completely reimplementing the pairing open source.
Click to expand...
Click to collapse
Steel01 said:
I
KNOWN PROBLEMS:
1. This is a multirom edition of twrp, but there's no multirom support yet.
2. My wireless keyboard / mouse combo (an old Logitech MX something or another) fails to initialize the mouse on boot. I have to unplug and replug the USB receiver for the mouse to work. My wired mouse doesn't do this. I'm curious if anyone else sees a similar problem or if there's something weird with my hardware.
Click to expand...
Click to collapse
I have a logitech K830 keyboard with trackpad and have exactly the same issue as you. I have to unplug and replug the usb receiver before it will work with the recovery.
The recovery itself is working great for me. I can access my external usb hd from the file manager, and I did a TWRP backup to the external usb drive last night :good: Ive sideloaded this app to boot straight into the recovery from the TV.. https://play.google.com/store/apps/details?id=gt.reboot.utility