Related
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 .
Can we use version of twrp for the other versions of this phone? I am trying to install android revolution HD, which as sprint support in the 4.3 version, but it requires the newer TWRP (or it will once it gets updated to 4.4 for us). Someone over there said it should be fine, but I just wanted to make sure.
well, i tried it. I got:
FAILED (remote: not allowed)
is that just because it's not for our device, or is it something I did wrong and can get around
TriBeard said:
well, i tried it. I got:
FAILED (remote: not allowed)
is that just because it's not for our device, or is it something I did wrong and can get around
Click to expand...
Click to collapse
The latest TWRP for m7wls (m7spr) is 2.6.3.0.
raptoro07 said:
The latest TWRP for m7wls (m7spr) is 2.6.3.0.
Click to expand...
Click to collapse
Yeah, I get that same error when I try to flash that as well.
Im running ARHD right now and you dont need 2.6.3.3 to install it, thats only for kit kat, which isnt supported as of now for us. Just use 2.6.3.0 and flash 31.6
EmSeeMAC said:
Im running ARHD right now and you dont need 2.6.3.3 to install it, thats only for kit kat, which isnt supported as of now for us. Just use 2.6.3.0 and flash 31.6
Click to expand...
Click to collapse
I can't even get that version to install. I get that same error with either one. I have CWM installed and I just used that and it seems to be doing ok, but I still would like to figure out why TWRP won't install cause the way it handles backups seems way easier.
Any idea when....
2.6.3.3 will be available for Sprint?
JoJoLanny said:
2.6.3.3 will be available for Sprint?
Click to expand...
Click to collapse
Not available yet, but not needed either.
Ok
Twrp is kind of broken on the Sprint HTC One. Use with caution guys
Sent from my HTCONE using XDA Premium 4 mobile app
Kraizk said:
Twrp is kind of broken on the Sprint HTC One. Use with caution guys
Sent from my HTCONE using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Twrp isn't broken. I use 2.6.3.0 everyday with no problems.
Sent from my HTCONE using Tapatalk
raptoro07 said:
Twrp isn't broken. I use 2.6.3.0 everyday with no problems.
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
Really because I know the 3 following issues have been confirmed by the developer:
1) When screen "sleeps" the device becomes unresponsive. back and home buttons vibrate but screen fails to wake
2) When in TWRP and a charger is connected after launching the charging percentage never updates to indicate it is plugged in (+ sign is never shown). If device is launched to recovery while plugged in + sign shows but percentage never updates.
3) USB OTG storage is not read
2 and 3 are kind of big deals. 2 means it is possible the device will not charge while off/dead and 3 limits backup abilities due to the lack of an SD card.
Kraizk said:
Really because I know the 3 following issues have been confirmed by the developer:
1) When screen "sleeps" the device becomes unresponsive. back and home buttons vibrate but screen fails to wake
2) When in TWRP and a charger is connected after launching the charging percentage never updates to indicate it is plugged in (+ sign is never shown). If device is launched to recovery while plugged in + sign shows but percentage never updates.
3) USB OTG storage is not read
2 and 3 are kind of big deals. 2 means it is possible the device will not charge while off/dead and 3 limits backup abilities due to the lack of an SD card.
Click to expand...
Click to collapse
Yes I can confirm those. I think it doesn't charge while in recovery.
Add another bug. The clock doesn't show the correct time
Sent from my HTCONE using Tapatalk
elvisypi said:
Yes I can confirm those. I think it doesn't charge while in recovery.
Add another bug. The clock doesn't show the correct time
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
Ive had one person claim their battery died and they got it to charge enough to boot it just took hours and a bit of luck. Again I am not bashing this recovery, it is just cautionary advice.
Kraizk said:
Ive had one person claim their battery died and they got it to charge enough to boot it just took hours and a bit of luck. Again I am not bashing this recovery, it is just cautionary advice.
Click to expand...
Click to collapse
If somebody is interested to be a beta tester for TWRP sign here http://teamw.in/get-involved
I just did and I also sent a message requesting the update and I listed the bugs
Sent from my HTCONE using Tapatalk
---------- Post added at 11:31 PM ---------- Previous post was at 11:20 PM ----------
Is there anyone willing to start porting the 2.6.3.3 from the international One? I found a guide http://forum.xda-developers.com/showthread.php?t=1943625
Unfortunately I'm no dev and have little knowledge...
Sent from my HTCONE using Tapatalk
My suggestion: for day to day, load PhilZ because all these things are not issues in that recovery (everything works).
In that rare instance that a ROM has a (poorly conceived, imho) dependency on TWRP, flash TWRP for loading the ROM, then flash back to PhilZ to get backups on OTG, proper battery handling, proper screen handling, etc.
It's a free world, no need to keep something loaded that bugs you. Load when needed, stay safe otherwise.
The issues with ROMs with different recoveries, if any, almost always end up an error properly checking device properties in the installer script. Easy fix, just have to let the dev know what's up.
I use standard CWM and it works perfect
tdhite said:
My suggestion: for day to day, load PhilZ because all these things are not issues in that recovery (everything works).
In that rare instance that a ROM has a (poorly conceived, imho) dependency on TWRP, flash TWRP for loading the ROM, then flash back to PhilZ to get backups on OTG, proper battery handling, proper screen handling, etc.
It's a free world, no need to keep something loaded that bugs you. Load when needed, stay safe otherwise.
The issues with ROMs with different recoveries, if any, almost always end up an error properly checking device properties in the installer script. Easy fix, just have to let the dev know what's up.
Click to expand...
Click to collapse
hey, you seem to know your way around android quite well. I too am a fan of philz. I was wondering if you have tried renovate rom? I read a few posts in its thread that people with philz cannot flash rom successfully. I also could not get past aroma(aroma was unresponsive to touch). I asked in thread and although fisha21 was considerate, did not get an answer due to most using twrp. I realize I can switch to flash, wondering what you thought might cause such issues? thx
also it was renovate milestone 7
jblaze10 said:
hey, you seem to know your way around android quite well. I too am a fan of philz. I was wondering if you have tried renovate rom? I read a few posts in its thread that people with philz cannot flash rom successfully. I also could not get past aroma(aroma was unresponsive to touch). I asked in thread and although fisha21 was considerate, did not get an answer due to most using twrp. I realize I can switch to flash, wondering what you thought might cause such issues? thx
also it was renovate milestone 7
Click to expand...
Click to collapse
Never ran renovate, actually don't plan to. I'm on @hawknest's EclipticONE 4.4.2 -- excellent kitkit/sense setup based on @baadnewz InsertCoin 7.x builds.
Anyway -- the issue with touch is not PhilZ, CWM, or TWRP -- it's a known Aroma bug and frankly the developers of Renovate are the best place to work with to work around that bug (note that InsertCoin, ViperONE, and a host of other Aroma users all work fine).
With that said -- touch is not required, at least if the install script was written correctly *not* to assume touch availability. Your vol up/down should work for navigation, and power for select. Note, btw, that if you install the Aroma file manager in PhilZ, half the time the touch doesn't work, but the buttons do (again, an Aroma bug -- not PhilZ, CWM or TWRP issue if touch blows it).
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
WARNING...
VERY IMPORTANT:
Some people were having SOUND ISSUES since flashing the new touch recovery mentioned later below. If you do not want to risk having what MAY BE PERMANENT sound issues it is better to not flash this.
Here is an updated philz touch advanced recovery 6.59.0/6.0.5.1 (fully working with touch afaik,no longer officially supported)
Possible past sound issues hopefully unrelated. Here is an updated philz touch advanced recovery 6.59.0/6.0.5.1 (fully working with touch afaik,no longer officially supported)
WARNING:
Possible past sound issues.
Seems to be unrelated.
Sound is ok here.
Read the thread. Decide for yourself.
https://www.dropbox.com/s/6n91kqmwzwe7wdw/philz_touch_recovery.img?dl=0
Thanks to all who helped.
USE AT YOUR OWN RISK.
To reboot into bootloader:
adb reboot-bootloader
To try the recovery before flashing:
fastboot boot recovery.img
To permanently flash the recovery:
fastboot flash recovery recovery.img
Thanks goes to Phil3759. pershoot
https://www.dropbox.com/s/6n91kqmwzwe7wdw/philz_touch_recovery.img?dl=0
Thanks a lot! Every feature work correctly. I needed custom restore, and in this recovery it to be!
I really want to get f2fs support with touch
I would settle for ANY recovery with touch support
Sent from my K00C using Tapatalk
berndblb said:
I would settle for ANY recovery with touch support
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
Me Too...i have CWM/Philz with touch on my Note 8.0 and it is very cool but with all the extra features it would be a little tedious to navigate.
Nicely done!!!
Sent from my SGH-T889 using XDA Premium 4 mobile app
Here is working version of touch recovery. Thanks to Bogdacutu and his project rm-wrapper: https://github.com/Bogdacutu/RM-Wrapper
Trel725 said:
Here is working version of touch recovery. Thanks to Bogdacutu and his project rm-wrapper: https://github.com/Bogdacutu/RM-Wrapper
Click to expand...
Click to collapse
Very interesting and the holy grail of the 701! :laugh:
sbdags said:
Very interesting and the holy grail of the 701! :laugh:
Click to expand...
Click to collapse
Just flashed it Thats absolutely fantastic! And they said it couldn't be done!
YayYouFixedIt said:
Just flashed it Thats absolutely fantastic! And they said it couldn't be done!
Click to expand...
Click to collapse
I am SO psyched about this! Can we now get a TWRP for our tablet? We should be able to integrate touch drivers using the same principle into TWRP!
michaave said:
I am SO psyched about this! Can we now get a TWRP for our tablet? We should be able to integrate touch drivers using the same principle into TWRP!
Click to expand...
Click to collapse
It may happen
Trel725 said:
Here is working version of touch recovery. Thanks to Bogdacutu and his project rm-wrapper: https://github.com/Bogdacutu/RM-Wrapper
Click to expand...
Click to collapse
What a relief! THANKS! :victory:
Sigh.
To good to be true?
I did some tests on the Philz recovery, did a nandroid then a factory reset followed by a restore and ended up with pretty distorted speaker sounds. Now, this COULD be unrelated, but I wonder....
Decided to dirty flash CROMi-X 7.0.3 and Aroma completely froze halfway through the installation screens....
I'm back on CWM.... :crying:
berndblb said:
Sigh.
To good to be true?
I did some tests on the Philz recovery, did a nandroid then a factory reset followed by a restore and ended up with pretty distorted speaker sounds. Now, this COULD be unrelated, but I wonder....
Decided to dirty flash CROMi-X 7.0.3 and Aroma completely froze halfway through the installation screens....
I'm back on CWM.... :crying:
Click to expand...
Click to collapse
Sound seems to be pretty good here. Might be unrelated. Maybe Give noozxoide a try to see if that helps belt it out. Tested with speakers, line out, netflix and music
http://forum.xda-developers.com/showthread.php?t=2039716
That is not a root app. Just seems to make the sound clearer and open it up a little.
My recovery is just a demo! I don't have enough knowledge in android recoveries, so I just include rm-wrapper and necessary libs (in /touch_libs). Also /system/bin/linker needed for correct works. Be careful now, and maybe someone else will make really good recovery.
Trel725 said:
My recovery is just a demo! I don't have enough knowledge in android recoveries, so I just include rm-wrapper and necessary libs (in /touch_libs). Also /system/bin/linker needed for correct works. Be careful now, and maybe someone else will make really good recovery.
Click to expand...
Click to collapse
Proof of concept is all we really needed to take off on this! Thank you!
I'm unfamiliar with /touch_libs... Where is that?
Also, which other libs ended up being required?
Maybe the touch recovery is affecting the sound eventually. You wouldn't think but to be safe maybe hold off til the problem is found. Could it be something else. Find out a bit later if it is something else like maybe it is one of the ROMs or a setting. My sound is good afaik.
michaave said:
Proof of concept is all we really needed to take off on this! Thank you!
I'm unfamiliar with /touch_libs... Where is that?
Also, which other libs ended up being required?
Click to expand...
Click to collapse
It is in recovery's root. Extract recovery.img by abootimg and then initrd.img by cpio.
I reinstalled CROMi-X 7.0.3 totally clean, formatted everything but /boot and ext-sd (data/media/ needed a cleanup anyway, he, he), still the same. The speaker seems to be shot. But how installing or using Philz would cause this is beyond me. It's gotta be unrelated....
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.
My fellow Android users & developers,
I've been out of the game for a while now (since the HTC incredible). I recently purchased an LG G2 when my upgrade came up. I'm moving back from an iPhone. The one thing that I am trying to do with this phone is some how set up tethering. Previously with my incredible I had to root the phone and then install a ROM. I have been searching around google and the site and all I am finding are horror stories of people bricking their phones. There are a million threads here. Can someone point me in the direction of what I need to enable tethering or how to properly root my device so I can install ROMs from the site? Any tips or links would be greatly appreciated!
My Device:
LG G2 VS98039A (Verizon)
Build: LRX22G
Kernel: 3.4.0-perf-ga038154
Thanks,
Scyth3
Just picked up a used G2 that should be arriving tomorrow so doing some homework today on this device. This is what I am planning to do when mine arrives, best of luck to you
root = http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
hotspot (see post 339) = http://forum.xda-developers.com/showthread.php?t=2456338&page=34
First of all, do you have warranty?
If you do, check if your GPS is working, only GPS sensors. There are a lot of reports with LG G2 gps broken, not working, etc.
If its broken, go and replace it. If its works and you are stock 39A, root your phone with root method that @someguyatx recommended and then, install recovery with this link:
http://forum.xda-developers.com/verizon-g2/development/tool-freedom-tool-vs980-39a-twrp-t3053134
When done, do a full nandroid backup prior doing anything. After that, I can recommend xddadeb version of Lollipop, its great and removes a lot of bloatware.
Anything, just ask
Thank you both for the replies. My warrenty should be gone at this point. I have had the phone for more than a little while I should have mentioned. How would I go about checking the GPS to ensure it is functioning? I have never had any trouble with using google maps or anything of that nature. Also on the link to the rooting page I noticed below the first post is a "one-click root". Should I manually do the instructions at the top or just use the one-click root?
Thanks again!
I am planning to follow the one click procedure link tomorrow to root as soon as I verify my phone works. Check out the video in the one click link from qbking77, his stuff is always good.
If your maps have been working properly then your GPS should be good to go.
I didn't even scroll down far enough to see the video originally haha. Thank you so much for your help. I'm in the process of rooting it now! I'll update the post once I am finished! :good:
Hope it went well, my phone just came in today so I will be rooting it tonight. Looks like I need to update first since its still on android 4.4.2
Sent from my XT1080 using Tapatalk
Just an advice: lollipop uses more battery so its not mandatory to update to that versio, its your choice.
Enviado desde mi VS980 4G mediante Tapatalk
I'm updated to lollipop, GPS is working great and I rooted after a few tries with the one click and a driver reinstall. Its refreshing to still have devices that root this easy. IJust need to add recovery and flash the hotspot zip. Thanks Deathsync3 for starting the thread and neondunker. Loving the G2 so far, much snappier than the Droid Maxx
Sent from my VS980 4G using Tapatalk
Remember to do a full nandroid backup of your stock rom, including EFS and those stuff.
Everything went smoothly. I did have some initial trouble though. To anyone using this method it does work BUT, when you get to the point after you have installed the drivers for the device and unzipped the .exe. Plug your phone in and click start root. when you get the prompts on the phone DO NOT check the box that says, "always allow". I REPEAT DO NOT CHECK the box. Simple click "ok" on the prompts and the root will complete sucessfully. I am now onto installing backup , a ROM, and hotspot. @neondunker can you link me to the ROM that you were talking about in the post? Also can you explain a little more in depth or provide a link in regards to what needs to be backed up? Is it still like the HTC Incredible where I had to go in and clear the cache, delvik cache, etc? Thanks again everyone!
Well the idea is to perform a full nandroid backup before leaving stock just in case. Then you can leave that backup on a pendrive or computer.
About the rom, is the xdadeb one in android devolpment. You wont miss it since itsa always in the first page. Just follow the instructions, dumb proof hehehehe.
Enviado desde mi VS980 4G mediante Tapatalk
@neondunker One last thing. How do I enter back into recovery mode now that TWIN is installed? Thanks for all of your other help man!
Two ways
One through adb and the other is to power off the cellphone. Then power up while pressing power + down volume. As soon as the lg logo appears release the buttons and hold again volume down.
Enviado desde mi VS980 4G mediante Tapatalk
neondunker said:
Two ways
One through adb and the other is to power off the cellphone. Then power up while pressing power + down volume. As soon as the lg logo appears release the buttons and hold again volume down.
Enviado desde mi VS980 4G mediante Tapatalk
Click to expand...
Click to collapse
What is ADB? annd when I power off then power and hold down the power and volume button it puts the phone into safe mode....I just did some searching outside the fourm. It seems this is the way to get into TWRP.
Try holding volume down + power
Immediately when LG appears let go of both and ONLY hold onto power, should boot into option to factory reset
Hit power button 3 times to continue, then it will load twrp
Even though it highlights factory reset it will NOT erase your data and should open up to TWRP.
Quote:
Thank you illyfilly and bodom_hc. Bodom_hc's method worked. I know others must be having this same issue/maybe someone should post it up somewhere. I really apprecaite the time you both took out to reply to me. Now I can flash rom's like I have for every other device. Much appreciated, thank you!
Quote:
Thank you for this! I was having the same problem. I have to admit, I panicked a little when it said it was proceeding with the factory hard reset, but then the recovery screen came up. Phew!
Thanks again.
Can anyone quadruple confirm that doing this does NOT erase all user data/settings and factory reset the G2? I'm honestly too scared to do this as I can't do a nandroid backup without TWRP... Thank so much!
Click to expand...
Click to collapse
This all being said, can you confirm this is the way that you go about entering TWRP?
Deathscyth3 said:
What is ADB? annd when I power off then power and hold down the power and volume button it puts the phone into safe mode....I just did some searching outside the fourm. It seems this is the way to get into TWRP.
This all being said, can you confirm this is the way that you go about entering TWRP?
Click to expand...
Click to collapse
Took a Leap of faith. I can confirm this is the method of how to access TWRP on the Verizon LG G2 once rooted and installed. Now onto the ROM and hotspot!:good:
Deathscyth3 said:
Took a Leap of faith. I can confirm this is the method of how to access TWRP on the Verizon LG G2 once rooted and installed. Now onto the ROM and hotspot!:good:
Click to expand...
Click to collapse
So what do you have to do exactly? I have been using the quick boot app for years to go into recovery but its helpful to know the hardware key combo.
someguyatx said:
So what do you have to do exactly? I have been using the quick boot app for years to go into recovery but its helpful to know the hardware key combo.
Click to expand...
Click to collapse
@someguyatx In order to access TWRP using the phones buttons:
****PLEASE NOTE this is for the VERIZON LG G2****
1. Power down your phone
2.HOLD the following buttons: POWER button and the DOWN volume button
3. Once the LG logo pops up let go of the buttons
4. Once the LG logo disappears hold both the POWER and DOWN volume button again
5. This will take you to the factory data reset screen
6.You will see some text that says, "Erase all user & restore default settings --> your selections will be yes or no. Select YES ( just trust me)
7. It will prompt you again ---> select YES, but this time press the power button 3 times ( so YES, YES, YES.)
8. The phone will go back to the LG screen and then the TEAMWIN logo will pop up and take you into recovery.
@someguyatx and @neondunker and @amcleod1995 have a question for both of you though.....This version of TWRP seems to be behind in regards to some of the ROMs I've looked at our is 5.x.x.x they use 6.x.x.x. I saw that some of the boot stacks include the "updated version" but how do you flash a boot stack? My brother started another thread asking the question as we have both reasearched quite a bit to avoid bricking out LGs.
Brother's thread ----> http://forum.xda-developers.com/lg-g2/help/how-to-flash-bootstack-t3139847
I flashed xdabbeb 3.1.2 Rom this morning and just followed the directions, first I flashed the 39a bootstack then rebooted to recovery wiped the stuff it said and flashed the Rom. So far it's running great.
Yes, its a great rom and the multitasking apps have improved over the 4.4 version. The only drawback is the battery life.