[recovery] cwm 5.0.2.7 + cwm touch **no vibration** - LG Optimus 2x

Hello!
After some time of searching in many forums all over the web, I FINALLY found a solution for all the users that experience vibration issues when going into recovery.
I must say this is not my work at all. Credits go to the developers at this forum, to trungkho for finding this forum and to Rusty!, for recompiling and changing the files to match our P990 O2x (this was originally made for the SU660).
It's been tested by me and some other members of XDA, and so far, so good.
Internal SD and external SD are recognized and mountable.
Needs testing for flashing various ROMS, so feedback is appreciated.
Enjoy!
CWM 5.0.2.7: http://www.mediafire.com/?8iqokc1xg73xe89
CWM Touch: http://www.mediafire.com/?y07ehwijm6kjg4h

Cool will download and test tomorrow...
Sent from my Optimus 2X using XDA

This is awesome! Finally i can flash a rom without annoying people around me and stop damaging my phone!

Hope you enjoy it and hope it works!

For anyone waiting for someone to post back about this, I would like to confirm I have installed this, and the vibration has indeed gone!
I'm going to do some flashing to make sure I don't get errors, but first impressions look good.
Thanks for solving this problem!
Charles

I have already made a backup and restored and installed a couple of roms. So for me it works.
Sent from my LG-P990 using Tapatalk 2

Thanks for this recovery. Now i wont hear the "zzzzzz" thing on my desk while doing backup

Well, Rusty did it again, this time recompiling CWM Touch version from the SU660 to the P990. Here is the download link for testing.

Good . One problem though... I like the way the buzzy recovery scares the hell outta you
Sent from my Asus Transformer TF201 Prime using XDA Premium HD app

Trolling level: 9000
Sent from my LG-P990 using XDA

korgndm said:
Well, Rusty did it again, this time recompiling CWM Touch version from the SU660 to the P990. Here is the download link for testing.
Click to expand...
Click to collapse
I've tried this. Vibration is gone ( finally ! ) and the recovery loads fine, but the touchscreen doesn't work at all... It's frozen. If I try the volume buttons they work, but as soon as I do that, recovery restarts. Grrr. So close.
Edit : Just tried 5.0.2.7 and that works perfectly ! Pity about the touch version, but the vibration on this phone was driving me crazy when flashing ! DONE WITH IT ! Thank you !
♪ヽ(´▽`)ノ

Does the touch recovery works good? I thought we werent suppose to use it.

punyategar said:
Does the touch recovery works good? I thought we werent suppose to use it.
Click to expand...
Click to collapse
Touch recovery always worked well for me, never a problem. That said, many people have had problems with it, so it is recommended to play safe and stay with the previous, non-touch version.

C:\shttps\nvflash>install-cwm-su660-windows.bat
1967 KB/s (4904960 bytes in 2.435s)
/dev/block/mmcblk0p7: cannot open for write: Permission denied
what am I doing wrong?
edit: replaced the script line with one found on the internet, and it worked (dont know why it doesn't work off hand)
adb-windows shell "/system/xbin/su -c 'dd if=/data/local/cwm-su660.img of=/dev/block/mmcblk0p7'"
edit 2: it no longer vibrates!!! FINALLY!!! HUGE THANKS!!

Ultramanoid said:
Touch recovery always worked well for me, never a problem. That said, many people have had problems with it, so it is recommended to play safe and stay with the previous, non-touch version.
Click to expand...
Click to collapse
I always prefered the "standard" version. The touch version's graphic interface is kind of lousy, and it's not as practical as the normal version. But every person is different, and might prefer other things...

Is this "better" compared to the past version 5.0.2.8 (which is i am currently using)? Its kinda annoying that your phone is vibrating when flashing something.

The past version was made for the 2X, but many people like myself had problems because when you entered recovery mode, the phone would turn into a dildo. The version posted in this thread was recompiled based on the SU660, which doesn't appear to have any issues among users. Even though it's 5.0.2.7, sometimes older is better...
So, to answer your question, if 5.0.2.8 makes your phone vibrate, but 5.0.2.7 doesn't, and they both do the same thing with no problems, then 5.0.2.7 is the way to go.
I don't know if Rusty is willing to make an updated version of this recovery. But, to me, and at this point, it doesn't really make a difference.

I'm still using 5.0.2.0, you shouldn't have a problem with 2.7
Sent from my LG-P990 using XDA

mrQQ said:
C:\shttps\nvflash>install-cwm-su660-windows.bat
1967 KB/s (4904960 bytes in 2.435s)
/dev/block/mmcblk0p7: cannot open for write: Permission denied
what am I doing wrong?
edit: replaced the script line with one found on the internet, and it worked (dont know why it doesn't work off hand)
adb-windows shell "/system/xbin/su -c 'dd if=/data/local/cwm-su660.img of=/dev/block/mmcblk0p7'"
edit 2: it no longer vibrates!!! FINALLY!!! HUGE THANKS!!
Click to expand...
Click to collapse
I had the same problem, permission denied. I don't use Windows. I put the recovery in the SD card and from a terminal in the device used dd to copy/install it.
Code:
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p17
As indicated by Paul from MoDaCo, Rusty! etc.

I've used 5.0.2.7 since release and can confirm it have worked on all my flashes...

Related

[Q] Unable to root OB

I recently updated my OB to the v10c software version. I'm not sure what region it is but I believe it is the europe open v10c? After I installed Gingerbreak 1.20, I tried to root my phone. It just displays the 'running exploit' message & this goes on for more than 20 minutes. I believe this means I am unable to root my OB? Is there an alternative solution to this?
more and more people are asking same things, why don't you research ?
http://forum.xda-developers.com/showthread.php?t=1111771
Well, I did what you told me to but I still wasn't able to root my phone. I tried using all versions of SuperOneClick available but always failed at the step where I entered "adb push superuser,apk \tmp\" in the CMD.EXE. When I enter this line, I get an error message 'Protocol failure' and my phone reboots. I know a couple of users has the same problem as I do & a few of them has a solution. But it's pretty complicated for me to understand and to do..Is there a clearer solution to this?
Did you try all the solutions shared ?
Sent from my Optimus Black using xda premium
I read in another thread to try using different versions of SuperOneClick e.g. 1.7, 1.9.5, 2.1 etc. So i tried all of it but it just rebooted my phone at "adb push superuser.apk \tmp\.
I believe there was another solution suggested but it was a bit complicated for me to try out. So I didn't try it as I wasn't confident about it :/
Did you try as example "my method" ? It's simple.
Sent from my Optimus Black using xda premium
dude even i have the exact problem of protocol failure. even i updated my firmware from v10d to v10e europe open but still the same prob. actually my phone got wet so lg service replaced me a new phone udated already to v10d, is that the prob does new OB has some new security or something. damn i am y totaly pissed of by this rooting issue i am so eager to install cm7 or NOVA, pls for god sake somebody help us.
Hey guys just a quick update. I managed to root my OB with llko's upgrade kit
It took less than 10 minutes for me to root my phone, so many thanks to llko.
dpockets, I had the same problem as you, the 'protocal failure' error message. Try llko's upgrade kit from the 'android development' section. Use the SuperOneClick and SRP. It should root your phone in no time. Read the txt files inside for instructions to Root & install CWM.
p.s. Just for your information, I had to use the SRP(reset) application in order for the files to be pushed to my OB successfully, so yeah, in case the SRP application doesn't work, try the SRP(reset) application. Most importantly, READ THE INSTRUCTIONS FILE GIVEN. Follow the steps closely
Once again, thanks a million llko!
Thanks to you too
I made an update so now it's even more easier and should work for all version (need feedbacks)
Black jack root worked for me like charm
Sent from my LG-P970 using Tapatalk
dpockets said:
Black jack root worked for me like charm
Click to expand...
Click to collapse
I also confirmed Blackjack. I've root V10A, V10D, V11B, and V11C.
hmm so it seems working very well, honnestly better than expected
easy life is cool right ?
Ilko said:
hmm so it seems working very well, honnestly better than expected
easy life is cool right ?
Click to expand...
Click to collapse
Ilko, do u think about making an .apk (like Ginerbreak) so we don't need to use a PC?
It would be great to have an easy .apk to root.
hmm this may be doable, but my knowledge is limited to windows and NSIS and some of graph basics (script/dev related) I didn't really developped, all things I've made here was to assembly what I found. I know making packages (setups), rest of credits go to internet

CWM 5.0.2.8 Issues (Vibrate)

Hello everyone!
I know this issue has been discussed many times in many forums, but no-one can find a final solution to this problem.
I have a LG P990 bought in Portugal, and I installed CWM 5.0.2.8 with internal and external SD support.
My problem is everytime I want to flash something on my phone, I reboot into recovery mode, and when I enter CWM, my phone vibrates like a dildo. I tried several versions of CWM, and the problem persists.
You might say "you can always use Paul's version from Modaco"... yeah, I could. But since I use an external SD card, that is not a viable solution to my problem.
The strange thing is, this doesn't happen on all P990 devices...
I'm not sure about the vibration issue you're having...
but other CWMs should be able to access external SD as well. AFAIK, older versions of CWM couldn't access internal SD, but all could access external SD.
And for what it's worth, I use 5.0.2.7 and it can access both internal and external.
aragorn7 said:
I'm not sure about the vibration issue you're having...
but other CWMs should be able to access external SD as well. AFAIK, older versions of CWM couldn't access internal SD, but all could access external SD.
Click to expand...
Click to collapse
Right, Paul's @Modaco version (4.0.0.5) can only access one of them... If you don't have an external SD, CWM will mount the internal one, but if you have an external SD, CWM wouldn't recognize the internal.
That's the version I use, and the only one that won't make my phone vibrate like a dildo.
No matter how I install CWM, either using ROM Manager, or NVflash or whatever, the result is always the same... The phone vibrates...
I may be wrong, but it seems that temasek is the one who compiled the first p990-compatible CWM 5.0.2.8 back in January.
http://forum.cyanogenmod.com/topic/22319-cm7-discussion-of-nightlies/page__st__1720#entry289942
Is that the same one you are using? If not, try his. If yes, maybe you can ask him?
Or maybe Rusty
http://forum.xda-developers.com/showpost.php?p=27176594&postcount=695
I'll try temasek's version. I had the vibration problems with Rusty's compilation. I'll take a look and get back to you.
korgndm said:
I'll try temasek's version. I had the vibration problems with Rusty's compilation. I'll take a look and get back to you.
Click to expand...
Click to collapse
Tried temasek's version of CWM. Has the same vibrating issue... reverting back to Paul's version.
korgndm said:
Tried temasek's version of CWM. Has the same vibrating issue... reverting back to Paul's version.
Click to expand...
Click to collapse
Sorry to hear that. This is real strange.
You do have a p990 o2x and not a su660 o2x, right? The only thing else I can think of is the slight difference in hardware between phones...
Or one other thing we could try is looking at the command lines for Paul's cwm and compare to temasek/rusty's. Can you send me a link for paul's?
EDIT: Never mind. I found it. I'll let you know if I see anything....
I'm pretty sure it's a O2x, which goes by the name LG Maximo 2x.
Here's Paul's version of CWM:
http://www.modaco.com/topic/335479-29-jun-4005-clockworkmod-recovery-for-the-lg-optimus-2x/
sorry korgndm, but I dont' have any good news.
I had trouble unpacking the .img files. I tried to use bsdiff to see what might be different between the two cwms (apart from the internal/external support) but was not successful.
Logically, if it worked without vibration with paul's, then it's not hardware issue. it's just a matter of coding/compiling the recovery img properly. but now, it's beyond my abilities...
I also considered that it could be a baseband issue. I'm using V20Q with stock rom, and never used anything else.
I'm planning on flashing my phone today with another BB, maybe 20s or 21y, then installing CWM again using the bat files, not using ROM Manager, and see what happens.
ok. kindly report back with how it goes when you get a chance, because i remember reading somewhere that changing BB/RIL didn't help with this. But wish you better luck with your phone!
aragorn7 said:
ok. kindly report back with how it goes when you get a chance, because i remember reading somewhere that changing BB/RIL didn't help with this. But wish you better luck with your phone!
Click to expand...
Click to collapse
All hope is lost
No luck flashing with another BB, or another version of CWM. The "dildo sindrome" persists... S**T!
EDIT: Found a solution to the problem:
http://forum.xda-developers.com/showthread.php?t=1508824
Congrats on finding the solution! So your o2x is su660 after all?
Do you have four or three buttons in the bottom?
If it is three, you have a su660 and that's what I was asking before.
Sent from my LG-SU660 using xda premium
I definitely have four buttons on the bottom. I double checked the label under the battery and it says "LG P990 Made in Korea".
I DO have a small problem with this CWM version, though... It won't mount the internal storage, neither will it mount USB. In another words, it will only recognize my external SD (which, BTW, is a piece of crap!), and if I want to copy a file to it, I have to either boot the phone normally and use a file manager, or remove the SD card and pop it in my laptop.
Any suggestions?
Have you tried adb while in Recovery mode?
If you can connect that way, maybe you can manually mount through shell.
Sent from my LG-SU660 using xda premium
I must confess I'm new to this "world", and I really don't have many computing or programming skills, but I suppose you're talking about using a terminal / terminal emulator... If you could kindly explain the procedure, I would appreciate it.
Yes I was talking about using the terminal. I will have to look for the instructions, written by much smarter and more knowledgeable people than me.
In the mean time, this excellent post with guides may be helpful.
http://forum.xda-developers.com/showthread.php?t=1037751
And if usb connection doesnt work for whatever reason and all you want to do is copy files to the phone, perhaps this tip from xda TV might help too :
http://youtu.be/UI70UYug_zQ
The example in the video is with a Ubuntu machine, but you can follow the same steps for using PC with Putty and WinSCP.
Edit: link updated
Sent from my LG-SU660 using xda premium
aragorn7 said:
In the mean time, this excellent post with guides may be helpful.
http://forum.xda-developers.com/showthread.php?p=7546
Click to expand...
Click to collapse
"No thread specified. If you followed a valid link, please notify the administrator"
Sorry for the wrong link. It's updated.
And for guide on ADB, check this out:
http://www.xda-developers.com/android/adb-easy-tutorial/

[L5] **** Guide for running CM10.1/CM10.2/CM11 on the Canadian E617G ****

The LG L5 E617G variant can certainly be rooted, have an unlocked bootloader, as well as run CyanogenMod. The Bell variant can use a custom kernel.
Firstly:
- Root the device using the guide in this thread.
- Verify that you have a SuperUser app installed, and you're able to achieve root status. The best way to check is by downloading SuperSU, and updating the binaries.
Secondly:
- Unlock the bootloader by downloading emmc_appsboot_617_truncated.zip in this thread. (Thanks Skellums!)
- Turn on USB Debugging in Developer Options, (if you can't see Developer Options in the settings menu, continuously tap on Build Number in About in Settings).
- When you plug in your device, if you have an SDCard, you should see two storage spaces within the LG L5 MTP. Place the bootloader file in root of the phone storage (which the devices sees as the SDCard). The actual SDCard is the external SDCard which ADB has trouble seeing on occasion.
- Plug in your device to the PC, and make sure its loaded into Android.
- Download the fastboot/adb files here, and extract them to C:/fastboot/. Open the command prompt in windows, and type:
Code:
cd C:/fastboot
then...
Code:
adb devices
...and make sure you see your device, then...
Code:
adb shell
su
dd if=/dev/block/mmcblk0p5 of=/sdcard/emmc_appsboot-backup.bin
dd if=/sdcard/emmc_appsboot_617_truncated.bin of=/dev/block/mmcblk0p5
reboot
- Now, you should have an unlocked bootloader. If you get any "file not found errors", you placed the emmc file in the wrong directory
Thirdly:
- You now need a recovery, so let your phone reboot, and when its back to the main screen, make sure the device is plugged in, open the command prompt, and follow the instructions here.
Fourthly:
- Any CyanogenMod works very nicely on the L5 E617G. You can get CM10.1 along with gapps here or CM10.2 here or the amazing CM11 here. Before heading back to recovery, you will need the CM10.1 ROM, GAPPS, v20 BaseBand, and WakeWithHomeAndPower_signed.zip (Optional) and v10 Baseband (For restore purposes if something goes wrong).
- Copy all those zips to the root of your external SD, and then run the command:
Code:
adb reboot recovery
- Before anything, create a NANDROID BACKUP! Make sure to backup to the external SD, as you probably would have more space to work with.
- Then, factory reset your device in recovery. You can now flash CM10.1, by choosing "install zip from external sd card". Flash the v20 baseband, then the ROM, then gapps, then the wake with home fix.
Done!
- Upon reboot, you should have CM working very well on your LG L5 E617G!
Note: You can also get to recovery with the L5 but holding down Vol Down and Home, while pressing the power button for 2 seconds.
Disclaimer: I wrote this article because I, myself, had quite the experience in getting CM10.1 running on this L5 variant, and I wanted to show that it's certainly possible, thanks to the hard work by all the devs here! Good luck!
Thank you, good sir! I have now installed CM10.1!
I ended up running the recovery twice - after the first time, during the reboot, it just hung at the LG logo so I turned it off and back on and then repeated the recovery install steps and it was fine after the second time (now that I think about it I should've just tried issuing the "adb reboot recovery" command again instead).
Phone definitely much snappier and I haven't had any problems so far! Thank you again!
It's been a couple of days now and all seems to be running smoothly!
The only issue I have with CM on my L5 is that the video seems to cause issues - it'll work the first time but then hangs afterwards and subsequent attempts just give an error. Rebooting is the only cure. Not a huge deal for me though.
The rest of the phone runs great, definitely smoother and snappier than stock.
Now my camera/video recording is working just fine today. Go figure.
Loving the speed vs the stock stuff!
koimr said:
Now my camera/video recording is working just fine today. Go figure.
Loving the speed vs the stock stuff!
Click to expand...
Click to collapse
I've noticed the same thing. Once and a while, the video camera will freeze, and then force close. Reopening it causes "Gallery has stopped.". It's really finicky, but a reboot usually does the trick. Not sure if it's a ROM issue or a E617G issue, but you're not alone!
Pictures seem fine, I would suggest staying away from the video recording for now.
BuffMcBigHuge said:
I've noticed the same thing. Once and a while, the video camera will freeze, and then force close. Reopening it causes "Gallery has stopped.". It's really finicky, but a reboot usually does the trick. Not sure if it's a ROM issue or a E617G issue, but you're not alone!
Pictures seem fine, I would suggest staying away from the video recording for now.
Click to expand...
Click to collapse
I seem to recall having these issues a long time ago with the stock ROM too, now that I think about it. Not a big deal for me, easier to just avoid using the video camera.
I've even gone and flashed the latest (as of today) beta 5 of CM 10.1 as well - works just great as well!
koimr said:
I seem to recall having these issues a long time ago with the stock ROM too, now that I think about it. Not a big deal for me, easier to just avoid using the video camera.
I've even gone and flashed the latest (as of today) beta 5 of CM 10.1 as well - works just great as well!
Click to expand...
Click to collapse
Great! I'm going to try the kernel that was also posted and attempt to overclock.
Sent from my HTC One using Tapatalk 4
BuffMcBigHuge said:
Great! I'm going to try the kernel that was also posted and attempt to overclock.
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
Oh wow! Post your results if it all works out!
koimr said:
Oh wow! Post your results if it all works out!
Click to expand...
Click to collapse
I have successfully flashed lge-e610-v3.4.0-13-08-2013_20-59.zip and overclocked the device to 1000Mhz!
BuffMcBigHuge said:
I have successfully flashed lge-e610-v3.4.0-13-08-2013_20-59.zip and overclocked the device to 1000Mhz!
Click to expand...
Click to collapse
Same here now! Whoohoo!!
Thank you, good sir! I have now installed CM10.1
I've installed beta 6 and now the video is working just fine (no hangs!).
I did find that I wasn't able to boot into recovery - I had to reflash recovery from ROM Manager.
I then tried to flash the custom OC kernel and that resulted in a blank screen, so back into recovery and reflash beta 6 again.
So I've lost the overclock but meh, I'm ok with waiting for an updated kernel.
New kernel was posted, I've flashed and it works - OC is back! :good:
fastboot adb files
Hey is it possible to re up the fastboot adb files i get a "file not found" ....or is it just the general adb install for android, if so i already have it from when i did my atrix. but if i need certain files then it would be great if someone could tell me, thx bunches
spuzzum said:
Hey is it possible to re up the fastboot adb files i get a "file not found" ....or is it just the general adb install for android, if so i already have it from when i did my atrix. but if i need certain files then it would be great if someone could tell me, thx bunches
Click to expand...
Click to collapse
A quick Google search usually gets what you need.
http://d-h.st/5Xy
Thx , searched the forums to see if there were special files or if it was just adb.I found nothing concrete and I already had adb installed so I just ran it and it worked so I know now.
sorry about getting back late to edit the post.
Does this Unlock Network?
My phone is LG E617G It's Canadian phone which locked to Bell Mobility.
Does this ROM work on that model? and does it unlock the network(sim)?
altltkrk said:
My phone is LG E617G It's Canadian phone which locked to Bell Mobility.
Does this ROM work on that model? and does it unlock the network(sim)?
Click to expand...
Click to collapse
It does not unlock the SIM, however, you can get your SIM unlocked by using a service such as this: http://dollarunlock.com/lg-e617g-optimus-l5-unlock-code.html
Good
Inviato dal mio LG-E610 con Tapatalk 2
Thank you, for this how to.
I've been searching everywhere for this info.
--------------------------------------------------------------------
I've installed CM and it seem to be working well, but there's a problem with the gapps install.
com.google.process.location
recherche google
picasa uplauder
google play store
All keep crashing on launch and do not work at all. SO I can't do any search on the phone and google play store isn't working at all.
Is this a know problem or did I do something wrong with the install?
Is there a way to fix this? I've tried to redoanload de gapps and do a factory restor but for now no changes.

[RECOVERY][8-24-13]Unofficial OUDHS Recovery 1.0.3.6 for Nvidia Shield

Unofficial OUDHS Recovery version 1.0.3.6 for the Nvidia Shield
Testers Greatly Appreciated! To test you can boot it rather then flashing it through fastboot with the command: "fastboot boot thor-oudhs-1.0.3.6-unofficial.img"​
Downloads
Unofficial OUDHS Recovery 1.0.3.6 Nvidia Shield
MD5 Checksum: BE931987CBA9976E2754BD887C93E68E
Unofficial OUDHS Recovery 1.0.3.6 Nvidia Shield Version 2
MD5 Checksum: 9e7e6df23d5ac0614bce4b63b98b9727
Click to expand...
Click to collapse
Flashing Instructions
1. Download the above file.
2. Move the downloaded recovery file into the directory where you have ADB and Fastboot setup on your computer.
3. Navigate into the directory where you have ADB and Fastboot setup on your computer and run the following commands from the command prompt on your computer:
Code:
adb reboot bootloader
fastboot flash recovery thor-oudhs-1.0.3.6-unofficial.img
Congratulations you now have OUDHS Recovery version 1.0.3.6 running on the Nvidia Shield.
Credits: shabbypenguin for developing the OUDHS source code and for being an excellent mentor!
Sweet! Thanks for this. I'm going to unlock my shield next week, and I'm going to be making several tutorial videos on it.
I just got 3 years of SquareTrade warranty, with Accidental Drop Protection. So if I root it and I break it, I can still get it replaced.
I'm curious... Never seen this recovery before. What does it offer that CWM doesn't? Or is it just a different recovery?
agrabren said:
I'm curious... Never seen this recovery before. What does it offer that CWM doesn't? Or is it just a different recovery?
Click to expand...
Click to collapse
OUDHS Recovery is based on CWMR sources and the full source code can be found here. It has some mortification for user interface and also it has a unique way of handling it's touch driven interface that's designed to make it compatible across a wide range of devices.
shimp208 said:
OUDHS Recovery is based on CWMR sources and the full source code can be found here. It has some mortification for user interface and also it has a unique way of handling it's touch driven interface that's designed to make it compatible across a wide range of devices.
Click to expand...
Click to collapse
Ok, cool. Just trying to decide if I should switch from my current CWM recovery over to this. Doesn't sounds like there's much of a difference.
agrabren said:
Ok, cool. Just trying to decide if I should switch from my current CWM recovery over to this. Doesn't sounds like there's much of a difference.
Click to expand...
Click to collapse
I haven't fully analyzed the OUDHS source code for all the changes that were made (It's on my to do list :good the main difference between your CWMR (Nice job on that by the way) and this is the touch interface that's really the main difference between them.
shimp208 said:
I haven't fully analyzed the OUDHS source code for all the changes that were made (It's on my to do list :good the main difference between your CWMR (Nice job on that by the way) and this is the touch interface that's really the main difference between them.
Click to expand...
Click to collapse
None of the touch is working on my device. And navigation is a real pain with only one of the two buttons working (home acts as up). Have you tested this at all?
agrabren said:
None of the touch is working on my device. And navigation is a real pain with only one of the two buttons working (home acts as up). Have you tested this at all?
Click to expand...
Click to collapse
For the touch issue I think I have ran into the same issue you were having with getting touch working on TWRP for the Shield. The unit I was going to test this on (Which is actually my friends who is still on vacation) I don't unfortunately have access to currently.
shimp208 said:
For the touch issue I think I have ran into the same issue you were having with getting touch working on TWRP for the Shield. The unit I was going to test this on (Which is actually my friends who is still on vacation) I don't unfortunately have access to currently.
Click to expand...
Click to collapse
Issues found while using it:
No touch support
No controller navigation
Screen is rotated 90 degrees
I didn't try anything else, since I'm not really willing to risk my device to test backup/restore.
agrabren said:
Issues found while using it:
No touch support
No controller navigation
Screen is rotated 90 degrees
I didn't try anything else, since I'm not really willing to risk my device to test backup/restore.
Click to expand...
Click to collapse
Thanks for letting me know about these issues I will see what I can do about these and hopefully issue more test builds shortly :good:.
Neither the touch nor the D-Pad on the controller is functional.
Only 2 buttons, Home to scroll up & Shield button : functioning as OK.
The said gestures are not working.
As Agraben said.
chaind said:
Neither the touch nor the D-Pad on the controller is functional.
Only 2 buttons, Home to scroll up & Shield button : functioning as OK.
The said gestures are not working.
As Agraben said.
Click to expand...
Click to collapse
Always glad to have multiple people confirm what is and isn't working I intend to get more test builds out as soon as I can .
Will be glad to help you with the testing!...
Install from SD didn't work.. I did not have SD card in the shield but it did not let me access internal memory of shield either.
Sent from my DROID RAZR HD using Tapatalk 2
thanks:laugh:
Do you think I could use this on my evga tegra note???? Sorry to bother just can't seem to find info in English about this device thanks....
Ksehwail said:
Do you think I could use this on my evga tegra note???? Sorry to bother just can't seem to find info in English about this device thanks....
Click to expand...
Click to collapse
This is meant for the Nvidia Shield only. However if you can provide me with your devices stock recovery.img or a link to where I can find it I can try and compile recovery for your device.
Sent from my SCH-I535 using XDA Premium 4 mobile app
shimp208 said:
This is meant for the Nvidia Shield only. However if you can provide me with your devices stock recovery.img or a link to where I can find it I can try and compile recovery for your device.
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the quick response I will try to find the recovery ima before the day ends... Thanks for taking the time to help... I should be able to find the recov.IMG... I have the Evga note do you think the recovery.IMG for the superfly one tegra note would suffice??
Sorry for the noob question but is there a way to pull the recovery.IMG from my device?? Thanks in advance
Ksehwail said:
Thanks for the quick response I will try to find the recovery ima before the day ends... Thanks for taking the time to help... I should be able to find the recov.IMG... I have the Evga note do you think the recovery.IMG for the superfly one tegra note would suffice??
Click to expand...
Click to collapse
Is the superfly one just a re-branded regular Tegra Note 7? What you can do is fastboot boot (NOT FLASH) the superfly image to see if it works. I saw your other question thread if you can get root access on your Evga Tegra Note 7 then you can pull it's recovery.img.
Ksehwail said:
Sorry for the noob question but is there a way to pull the recovery.IMG from my device?? Thanks in advance
Click to expand...
Click to collapse
Yes there is a way to pull your devices recovery.img, but it requires root access (Make sure you have root access on your device first. First reboot your device into recovery mode and wipe your devices cache then reboot the device into the Android OS. Then from terminal emulator or ADB shell please run the following command and upload the result of the following command:
Code:
su
cat /cache/recovery/log
This will allow me to determine which partition on your device is the recovery partition that you need to dump. As always if you have any questions let me know I'll be happy to help you out .

A PhilZ Touch recovery for the Galaxy S5 Plus (G901F) Lollipop

Starting with a nice script by @Phil3759, I compiled a PhilZ Touch recovery for the Galaxy S5 Plus as this phone, by now, is widely spread over Europe. I took also some parts of the cwm from @Chenglu (Xiaolu). I didn't test all functionnalities, but, normally, this shouln't be very different from what is existing for Lollipop. A file is attached. Use ODIN or dd.
All credits are for these two guys, specially for @Phil3759 and many thanks to them.
Enjoy !
NEW VERSION V2.3 : [Chttp://cdn1.xda-developers.com/images/2015/editor/color.pngOLOR="Lime"] extSdCard [/COLOR](mount/unmount, save/restore...) WORKING !
adb (under Ubuntu or equivalent. For Windows, use Koush's UniversalAdbDriver) WORKING !
exfat (mount, umount,format) WORKING [/COLOR]
Flashing this recovery will trip the knox counter (knox=0x1) !
Please look at a new release including F2FS and NTFS supports - it is version 2.3 + F2FS + NTFS - :
forum.xda-developers.com/showthread.php?t=3112384 (thank you @ad0dh67)
think you forgot the file
I uploaded the file for the second time. As I am very new on this forum, I don't know exactly what to do in case of a failure. I hope It will be fine.
OBSOLETE ! SEE V 2.2 at the beginning of the thread.
xdamc2010 said:
I uploaded the file for the second time. As I am very new on this forum, I don't know exactly what to do in case of a failure. I hope It will be fine.
Click to expand...
Click to collapse
just flashed the recovery and congrats :thumbup: its working well and looking good. i sugest make topic in dev section. Good job!
Edited. Recovery does not see ext sdcard!
xdamc2010 said:
I uploaded the file for the second time. As I am very new on this forum, I don't know exactly what to do in case of a failure. I hope It will be fine.
Click to expand...
Click to collapse
Great work
xdamc2010 said:
Starting with a nice script by @Phil3759, I compiled a PhilZ Touch recovery for the Galaxy S5 Plus as this phone, by now, is widely spread over Europe. I took also some parts of the cwm from @Chenglu (Xiaolu). I didn't test all functionnalities, but, normally, this shouln't be very different from what is existing for Lollipop. A file is attached. Use ODIN or dd.
All credits are for theses two guys, specially for @Phil3759 and many thanks to them.
Enjoy !
Click to expand...
Click to collapse
You did it!! well done mate :good:
ad0dh67 said:
just flashed the recovery and congrats :thumbup: its working well and looking good. i sugest make topic in dev section. Good job!
Edited. Recovery does not see ext sdcard!
Click to expand...
Click to collapse
You are right.
it is a first step and only a strict compilation of @Phil3759 sources. Before adding other properties, I need test reports upon what is working and what is not. Then the first job will consist in making recovery seeing the extSdCard. Moreover, if I compiled this recovery, it is mainly to try to add f2fs formatting in order to replace the ext4 filesystem.
good work, when you get the ext sdcard working I will start using it.
Is this able to use backups made by the older CWM we been using?
ad0dh67 said:
just flashed the recovery and congrats :thumbup: its working well and looking good. i sugest make topic in dev section. Good job!
Edited. Recovery does not see ext sdcard!
Click to expand...
Click to collapse
Have a look to version V2
javilonas said:
Great work
Click to expand...
Click to collapse
HI,
Have a look to version v2 : extSdCard is now recognized
chrcol said:
good work, when you get the ext sdcard working I will start using it.
Is this able to use backups made by the older CWM we been using?
Click to expand...
Click to collapse
Have a look to version v2.2
xdamc2010 said:
Have a look to version v2
Click to expand...
Click to collapse
just downloaded, flashed, and yes external sd works now! congrats man, you just made a recovery, which is ready for use on our phone :thumbup: thank you
xdamc2010 said:
Have a look to version V2
Click to expand...
Click to collapse
Hello, it works great
I tested to do a backup.
I don't try to restore for the moment.
xdamc2010 said:
Have a look to version V2
Click to expand...
Click to collapse
thanks for your efforts
v2 works perfectly here, formatted and flashed a rom from extsdcard perfectly! great work mate :good:
I just noticed it says lollipop, does this mean this recovery wont work with kitkat roms?
issues I found
with touch interface enabled and pressing the circle button, I often by mistake do 2 actions, it seems it repeats even if the repeat key option is disabled.
date/time is completely wrong. time zone is set correct but the time displayed is completely wrong, my local time is 16:37 4 may and its displaying 8:14 5 may.
setting brightness has no effect, always same brightness.
dim screen delay also doesnt work (screen never dims)
ok for now I having to revert to the basic cwm as my extsdcard is exfat.
chrcol said:
I just noticed it says lollipop, does this mean this recovery wont work with kitkat roms?
issues I found
with touch interface enabled and pressing the circle button, I often by mistake do 2 actions, it seems it repeats even if the repeat key option is disabled.
date/time is completely wrong. time zone is set correct but the time displayed is completely wrong, my local time is 16:37 4 may and its displaying 8:14 5 may.
setting brightness has no effect, always same brightness.
dim screen delay also doesnt work (screen never dims)
ok for now I having to revert to the basic cwm as my extsdcard is exfat.
Click to expand...
Click to collapse
I didn't try kitkat roms as I don't need them anymore. If bootloaders are not different it could work.
Touch interface is very sensitive. Try to lower the Scroll Sensitivity.
Time appears foolish. Just tick the Qualcomm Time Daemon and you get the right time
exfat is a real problem and I try to solve this question.
xdamc2010 said:
I didn't try kitkat roms as I don't need them anymore. If bootloaders are not different it could work.
Touch interface is very sensitive. Try to lower the Scroll Sensitivity.
Time appears foolish. Just tick the Qualcomm Time Daemon and you get the right time
exfat is a real problem and I try to solve this question.
Click to expand...
Click to collapse
bootloader kitkat and lollipop are different
so what issues does different bootloader cause?
I was able to access the recovery fine with a kitkat rom installed.
chrcol said:
so what issues does different bootloader cause?
I was able to access the recovery fine with a kitkat rom installed.
Click to expand...
Click to collapse
Good news !
issues with bootloaders : mainly bootloops or phone freezes.

Categories

Resources