Hey, I bring to you, Clockworkmod Recovery or commonly known as CWM for your beloved i9505 (S4). Giving your device the ability to flash your favourite custom ROMs, Kernels, Mods in the future. Thankyou to 'as i9000' for giving me the stock recovery. Note: This thread will be moved to the i9505 section once its created.
This has not been tested by me and is still experimental. I hold no responsibility
for any problems caused. YOU! Are trying this at your own risk. Don't blame me that I wasted your $700.
Put a scare in you didn't I?
I have provided the stock recovery if you encounter any issues, you can always flash back. It is Odin flashable.
Downloads:
CWM Experimental #4: http://d-h.st/ZOk
Stock Recovery: http://d-h.st/LqC
Changelog:
Code:
[I][U]Experimental #4[/U][/I]
Display fixes
recovery.fstab fix
[I][U]Experimental #3[/U][/I]
Working (everything) [B]- revert[/B]
[I][U]Experimental #2[/U][/I]
Skipped
[I][U]Experimental #1[/U][/I]
Public release
emwno said:
Hey, I bring to you, Clockworkmod Recovery or commonly known as CWM for your beloved i9505 (S4). Giving your device the ability to flash your favourite custom ROMs, Kernels, Mods in the future. Thankyou to 'as i9000' for giving me the stock recovery. Note: This thread will be moved to the i9505 section once its created.
This has not been tested by me and is still experimental. I hold no responsibility
for any problems caused. YOU! Are trying this at your own risk. Don't blame me that I wasted your $700.
Put a scare in you didn't I?
I have provided the stock recovery if you encounter any issues, you can always flash back. It is Odin flashable.
Downloads:
CWM Experimental #1: http://d-h.st/khT
Stock Recovery: http://d-h.st/LqC
Changelog:
Code:
[I][U]Experimental #1[/U][/I]
Public release
Click to expand...
Click to collapse
It does not work (it doesnt boot)...
samovog said:
It does not work (it doesnt boot)...
Click to expand...
Click to collapse
adb pull /tmp/recovery.log
emwno said:
adb pull /tmp/recovery.log
Click to expand...
Click to collapse
Cannot. Flashed Chainfires root package, now the phone reboots itself...
Does anyone have a link to a stock odin firmware so i can reflash the phone and send you that file ?
samovog said:
Cannot. Flashed Chainfires root package, now the phone reboots itself...
Does anyone have a link to a stock odin firmware so i can reflash the phone and send you that file ?
Click to expand...
Click to collapse
This: http://www.orpheusdroid.com/xda/ credit to vijai2011. Flash that, then my provided stock recovery. (if still not working, ill provide the bootloader and boot.img)
emwno said:
This: http://www.orpheusdroid.com/xda/ credit to vijai2011. Flash that, then my provided stock recovery. (if still not working, ill provide the bootloader and boot.img)
Click to expand...
Click to collapse
It does not let me flash! It says:
Unsupported dev_type
i can flash other files (recovery, ...).
samovog said:
It does not work (it doesnt boot)...
Click to expand...
Click to collapse
do not work
[email protected] said:
do not work
Click to expand...
Click to collapse
adb pull /tmp/recovery.log
I tried to pull the log:
C:\Old stuff\I9300\Odin>adb pull /tmp/recovery.log
remote object '/tmp/recovery.log' does not exist
C:\Old stuff\I9300\Odin>adb shell
[email protected]:/ $ cd /tmp
cd /tmp
/system/bin/sh: cd: /tmp: No such file or directory
2|[email protected]:/ $
Is there another path in which I could look for the log you want?
/primpa
primpa said:
I tried to pull the log:
C:\Old stuff\I9300\Odin>adb pull /tmp/recovery.log
remote object '/tmp/recovery.log' does not exist
C:\Old stuff\I9300\Odin>adb shell
[email protected]:/ $ cd /tmp
cd /tmp
/system/bin/sh: cd: /tmp: No such file or directory
2|[email protected]:/ $
Is there another path in which I could look for the log you want?
/primpa
Click to expand...
Click to collapse
Code:
adb pull /cache/recovery/last_log
Code:
adb pull /cache/recovery/log
I'll be working with ewmno to try and get a working version out. (I'm only tester :highfive: )
Annie the Eagle said:
I'll be working with ewmno to try and get a working version out. (I'm only tester :highfive: )
Click to expand...
Click to collapse
Sweet. Let me know if you guys want me to try something =)
/p
---------- Post added at 11:44 PM ---------- Previous post was at 11:27 PM ----------
emwno said:
Code:
adb pull /cache/recovery/last_log
Code:
adb pull /cache/recovery/log
Click to expand...
Click to collapse
Unfortunately it won't work either:
Code:
[email protected]:/ # cd /cache/
[email protected]:/cache # ls -l
-rwx------ system system 8 2013-04-27 23:43 hidden_volume.txt
drwxrwx--- root root 1970-01-01 01:00 lost+found
[email protected]:/cache #
I guess im gonna have to start fresh, blindly
emwno said:
I guess im gonna have to start fresh, blindly
Click to expand...
Click to collapse
Just let me know if you need me to do something to help you out with this. I'm not a programmer, but I can try stuff =)
/p
I created my own CWM using the fstab.qcom and stock recovery. Here's the last_log file....
The-Kevster said:
I created my own CWM using the fstab.qcom and stock recovery. Here's the last_log file....
Click to expand...
Click to collapse
Whats wrong with it? need to know what im looking for..
Ok. The Samsung screen loads and there's text in the top left saying "loading recovery..." this is normal on stock recovery.
The screen then goes black and the device reboots. Nothing displayed on screen. Either it fails and reboots the device or there's instructions missing so with nothing left to do it reboots.
Sent from my GT-I9505 using Tapatalk 2
The-Kevster said:
Ok. The Samsung screen loads and there's text in the top left saying "loading recovery..." this is normal on stock recovery.
The screen then goes black and the device reboots. Nothing displayed on screen. Either it fails and reboots the device or there's instructions missing so with nothing left to do it reboots.
Sent from my GT-I9505 using Tapatalk 2
Click to expand...
Click to collapse
Check your recovery.fstab and what did you use to compile CWM?
Just builder.clockworkmod. The behavior is the same as your cwm.
Anything else I can do to help?
Sent from my GT-I9505 using Tapatalk 2
The-Kevster said:
Just builder.clockworkmod. The behavior is the same as your cwm.
Anything else I can do to help?
Sent from my GT-I9505 using Tapatalk 2
Click to expand...
Click to collapse
No not yet, still figuring it out. Will post a new version, i got an idea of what may have gone wrong.
Related
UPDATED 7-8-13
WHAT THIS TOOL DOES:
1.ROOTS YOUR GALAXY S4 (motochopper exploit created by djrbliss)
2. PREPS FOR RECOVERY
3. INSTALLS CWM OUDHS 1.0.3.4 (7/8) RECOVERY(credit to shabbypenguin)
4. INSTALLS TWRP 2.6.0.0 (credit to dees_troy)
5. Flash phone back to stock using odin
(Full Version Only)
#FOR AT&T I337 ONLY WARNING MADE#
Heres a pretty amateur video I threw together:
https://www.youtube.com/watch?v=NlK3r81kQPw&feature=youtube_gdata_player
Ive updated this to a 3 way all in one tool. Tool can root device (using motochopper by djrbliss) and install either cwm or twrp. Great tool for all those just getting started. Both CWM OUDHS 1.0.3.5 and TWRP 2.5.0.2 are auto loki. They will apply loki patch to all compatible roms and kernels flashed. You can also flash back to stock via Odin
##EDIT I HAVE RECEIVED VERIFICATION THAT TWRP WILL NOT AUTO PATCH. THIS CAME FROM DEES_TROY HIMSELF. IF YOU USE TWRP BE SURE TO FLASH A LOKI KERNEL AFTER ANY NON LOKI ROM FLASH##
A huge thanks to djrbliss for his genius
And huge thanks to dees_troy and shabbypenguin for the recoveries
Also thanks to mostyle for the script help
Instructions:
1. Download 3way tool zip
2. Unzip on desktop and open tool.
3. Connect I337 via usb with usb
debugging enabled.
4. Click Run_Me.bat select number for option you desire and enjoy!
Use this tool at your own risk. I am not responsible for any level of destruction to your phone blah blah blah
Downloads:
Full Version
https://mega.co.nz/#!o0dXHLoY!BNo2eFNQsuPN2-ivpVGo7Vk_V7ckHorY9WlK0PTqbSM
Slim Version (no odin to stock)
https://mega.co.nz/#!Q9FByZrD!CUK7RTDUzzzrH-n3rXjylhkOyy9B1gx9zHNfaKkbVJg
#EDIT# ADDED PREP FOR RECOVERY OPTION. WILL REMOVE KNOX APKS AND install-recovery.sh FOR YOU.Mirrors are welcome. Have a nice day! Dont forget to hit the THANKS button!
If youd like to buy me a beer:beer: I wont complain
Thanks for the beer:beer:list:
Scanss2k
LSUtigers03
O.K
I like to try it :fingers-crossed:
I installed the OUDHS Recovery yesterday and now either one of these will install.I'd love to have Loki'd TWRP. My phone has the same UCUAMDL
If you use either of these please let me know if it works for you.
Respond to sholsten
You mean Neither will work,
It didn't work on mine.
Ill recheck script when I get home. Worked on test devices prior to posting. Please post error messages here. ^^^^ already have yours
pakxelaos said:
Respond to sholsten
You mean Neither will work,
It didn't work on mine.
Click to expand...
Click to collapse
Neither seemed to have have installed on mine. It has the same one I installed in my above post yesterday.
sholsten said:
Neither seemed to have have installed on mine. It has the same one I installed in my above post yesterday.
Click to expand...
Click to collapse
What message did you get on tool after it ran
pakxelaos said:
Respond to sholsten
You mean Neither will work,
It didn't work on mine.
Click to expand...
Click to collapse
Did uninstall the recovery.sh file?
Fixed
On the line that issues the remount command there occurs 'Permission denied.'
In your batch file change line 25:
adb remount
Click to expand...
Click to collapse
so that it reads:
adb shell su -c "mount -o rw,remount /system"
Click to expand...
Click to collapse
Of course this assumes you are rooted..
EDIT:
Still getting an error 'Failed to open aboot for reading'
I'm investigating.. Hang on.
Will change and repost in a few
You could just install goomanger and install twrp thats been lokified directly from your rooted s4
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
bhp090808 said:
What message did you get on tool after it ran
Click to expand...
Click to collapse
Finished Rebooting into TWRP
Have a nice day!
adb is not recognized as an internal or external command, operable program or batch file.
Press any key to continue
Here's the fixed script..
Just had to su -c all of your commands...
db kill-server
adb start-server
adb shell su -c "mount -o rw,remount /system"
adb wait-for-device
adb push loki_flash /data/local/tmp
adb push openrecovery.lok /data/local/tmp
ECHO.
ECHO Doing the hard stuff.............
ECHO.
adb shell su -c "mount -o rw,remount /system"
adb shell su -c "chmod 755 /data/local/tmp/loki_flash"
adb shell su -c "./data/local/tmp/loki_flash recovery /data/local/tmp/openrecovery.lok"
Click to expand...
Click to collapse
Hope that helps. Tested it here and it works fine..
mostyle said:
Just had to su -c all of your commands...
Hope that helps. Tested it here and it works fine..
Click to expand...
Click to collapse
Will update and repost in a few thx
EDIT
Ok updated script new links are up let me know if its working for you now
MrPlNK said:
You could just install goomanger and install twrp thats been lokified directly from your rooted s4
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
How do you find the correct TWRP?
Just tried this with TWRP worked beautifully, thank you very much!! :good:
djoutrages said:
Just tried this with TWRP worked beautifully, thank you very much!! :good:
Click to expand...
Click to collapse
Make sure to thank mostyle for the script assist. Thanks bro
Tested both on my 32GB S4. Both working with no issues at all. Appreciate the work that went into this.
So if I understand this will allow you to flash a Rom that has not been Loki'd and it will loki it and allow it to boot with either TWRP or CWM?
Hello everyone!
Here's another release thread for y'all!
What is this?
This is a flashable ClockworkMod recovery for the Optimus G Pro.
Special thanks to @djrbliss
You can safely flash this to your phone's recovery and enjoy modding bliss!
How do I use this, and where do I get it?
Good question!
There are two ways to use the files provided here.
To Flash to Recovery:
Download this file to somewhere on your computer https://github.com/djrbliss/loki/raw/master/bin/loki_flash
Download this file http://downloads.codefi.re/thecubed/lgoptimusg_pro/gkatt/recovery/e98010g/gkatt-cwm-e98010g.lok
Run the following:
Code:
adb push loki_flash /data/local/tmp
adb push gkatt-cwm-e98010g.lok /data/local/tmp
abd shell
su
cd /data/local/tmp
chmod 755 loki_flash
./loki_flash recovery gkatt-cwm-e98010g.lok
To boot
Download this file: http://downloads.codefi.re/thecubed/lgoptimusg_pro/gkatt/recovery/e98010g/gkatt-cwm-e98010g.img
Use fastboot boot to boot it
DO NOT FLASH THE .IMG FILE TO YOUR PHONE. It is only meant for fastboot booting.
Where can I find the source you used to build this?
All on my github!
http://github.com/thecubed/
Or, follow my guide here:
http://forum.xda-developers.com/showthread.php?p=43514195
What can I do with this?
Right now, the possibilities are unlimited. Once a security-lax boot.img is released, we can flash that through recovery and let the modding commence.
Please remember though, modding /system with the stock boot.img will result in a security error!
What works, and what doesnt?
I have so far tested making backup images, however I haven't tested restoring them.
I have also not tested external SD cards, since I don't have one with me at work.
Can you show me a video?
Why yes I can!
As usual, please pardon the crappy camera work.
I <3 you so much, how do I show my love?
You are so kind
I most definitely do not expect donations of any kind, however they are appreciated a lot.
I purchased this phone off-contract just to get it unlocked, if you are a kind soul and would like to send me a token of your appreciation I would love you forever.
XDA has a neat "Donate to me" button that should be on the left side of this page under my name. Donations go to purchasing new hardware to work on and other neat stuff, so they're always appreciated.
Special Thanks!
In no particular order, special thanks to all of you guys!
djrbliss
synergy
Shelnutt2
DeamonFish
If I forgot anyone, let me know and I'll add you here!
Alright guys! Let me know if you find any bugs!
Can I flash this threw dd?
Sent from my LG-E980 using xda premium
Gotroot said:
Can I flash this threw dd?
Sent from my LG-E980 using xda premium
Click to expand...
Click to collapse
We could just run Loki flash from terminal and flash that way if no adb as for the second Part we'd need fastboot on our computer
Sent from my LG-E980 using xda premium
This is some serious progress! :thumbup::thumbup:
Sent from my LG-E980 using Tapatalk 2
Btw cube external sd does work !!!
Sent from my LG-E980 using xda premium
Gotroot said:
Can I flash this threw dd?
Sent from my LG-E980 using xda premium
Click to expand...
Click to collapse
Yes you can, just do the following:
Code:
adb push gkatt-cwm-e98010g.lok /data/local/tmp
adb shell
su
dd if=/data/local/tmp/gkatt-cwm-e98010g.lok of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Getting into recovery is as simple as "adb reboot recovery" or holding the proper volume keys.
I just recommend using Dan's excellent loki_flash utility since it checks to make sure you have the right bootloader in place already.
fastboot info
Would be nice to have more info on how to use fastboot with the .img file. I tried all I know with no results. Thanks!
G0bl1n said:
Would be nice to have more info on how to use fastboot with the .img file. I tried all I know with no results. Thanks!
Click to expand...
Click to collapse
Not sure what you're asking. To flash any .img file without any modifications requires our bootloader to be unlocked. What's going on here is everything needs to be "Loki'ed" so our phones are able to flash unsigned code through a custom recovery, bypassing our locked bootloader.
Fastboot is a way of testing unsigned code without having to necessarily flash it to any partitions.
Anyone correct me if I'm wrong, as I'm definitely not a developer. I just read a lot lol
thecubed said:
Hello everyone!
Here's another release thread for y'all!
What is this?
This is a flashable ClockworkMod recovery for the Optimus G Pro.
Special thanks to @djrbliss
You can safely flash this to your phone's recovery and enjoy modding bliss!
How do I use this, and where do I get it?
Good question!
There are two ways to use the files provided here.
To Flash to Recovery:
Download this file to somewhere on your computer https://github.com/djrbliss/loki/raw/master/bin/loki_flash
Download this file http://downloads.codefi.re/thecubed/lgoptimusg_pro/gkatt/recovery/e98010g/gkatt-cwm-e98010g.lok
Run the following:
Code:
adb push loki_flash /data/local/tmp
adb push gkatt-cwm-e98010g.lok /data/local/tmp
abd shell
su
cd /data/local/tmp
chmod 755 loki_flash
./loki_flash recovery gkatt-cwm-e98010g.lok
To boot
Download this file: http://downloads.codefi.re/thecubed/lgoptimusg_pro/gkatt/recovery/e98010g/gkatt-cwm-e98010g.img
Use fastboot boot to boot it
DO NOT FLASH THE .IMG FILE TO YOUR PHONE. It is only meant for fastboot booting.
What can I do with this?
Right now, the possibilities are unlimited. Once a security-lax boot.img is released, we can flash that through recovery and let the modding commence.
Please remember though, modding /system with the stock boot.img will result in a security error!
What works, and what doesnt?
I have so far tested making backup images, however I haven't tested restoring them.
I have also not tested external SD cards, since I don't have one with me at work.
Can you show me a video?
Why yes I can!
As usual, please pardon the crappy camera work.
I <3 you so much, how do I show my love?
You are so kind
I most definitely do not expect donations of any kind, however they are appreciated a lot.
I purchased this phone off-contract just to get it unlocked, if you are a kind soul and would like to send me a token of your appreciation I would love you forever.
XDA has a neat "Donate to me" button that should be on the left side of this page under my name. Donations go to purchasing new hardware to work on and other neat stuff, so they're always appreciated.
Special Thanks!
In no particular order, special thanks to all of you guys!
djrbliss
synergy
Shelnutt2
DeamonFish
If I forgot anyone, let me know and I'll add you here!
Alright guys! Let me know if you find any bugs!
Click to expand...
Click to collapse
If I have the old ClockworkMod, can I still do this or do I have to get rid of it somehow?
Are there any special precautions someone should take if they have this recovery already flashed to our phones?
Flashing with the latest "loki_flash" from dan's repos is segfaulting here and I'm too lazy to run it in gdb. The recovery works just fine with dd after zeroing the recovery partition out. Thanks mucho :good:
Coming from the Note I'm not use to locked bootloader.
Should we all install this if our goal is to eventually flash custom roms?
Yoreo said:
Are there any special precautions someone should take if they have this recovery already flashed to our phones?
Click to expand...
Click to collapse
Had that recovery and I had one of the first cwm Loki recoveries flashed this one just fine no issues
Sent from my LG-E980 using xda premium
acejoker25000 said:
Had that recovery and I had one of the first cwm Loki recoveries flashed this one just fine no issues
Sent from my LG-E980 using xda premium
Click to expand...
Click to collapse
Sounds good. Thanks.
madmack said:
Flashing with the latest "loki_flash" from dan's repos is segfaulting here and I'm too lazy to run it in gdb. The recovery works just fine with dd after zeroing the recovery partition out. Thanks mucho :good:
Click to expand...
Click to collapse
did the gdb backtrace:
Code:
Program received signal SIGSEGV, Segmentation fault.
0x4016ffa0 in memcmp () from /home/madmack/tmp/gdb/libs/libc.so
(gdb) bt
#0 0x4016ffa0 in memcmp () from /home/madmack/tmp/gdb/libs/libc.so
#1 0x00008868 in main ()
(gdb) bt
#0 0x4016ffa0 in memcmp () from /home/madmack/tmp/gdb/libs/libc.so
#1 0x00008868 in main ()
(gdb) quit
One of the memcmp commands is segfaulting. Perhaps @djrbliss can have a look when he gets some free time.
madmack said:
Flashing with the latest "loki_flash" from dan's repos is segfaulting here and I'm too lazy to run it in gdb. The recovery works just fine with dd after zeroing the recovery partition out. Thanks mucho :good:
Click to expand...
Click to collapse
what do you mean?
need zeroing the recovery partition before using dd to flash recovery image?
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/data/local/tmp/gkatt-cwm-e98010g.lok of=/dev/block/platform/msm_sdcc.1/by-name/recovery
GREAT.... I can using this to "adb reboot recovery" with CWM recovery on my E988 HK version ^^
so what is next, how to try boot my custom boot kernel ???
Timisone said:
If I have the old ClockworkMod, can I still do this or do I have to get rid of it somehow?
Click to expand...
Click to collapse
I have a few a questions. When do I run the commands? Command prompt in windows? What mode does my phone need to be in to flash this?
hkfriends said:
what do you mean?
need zeroing the recovery partition before using dd to flash recovery image?
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/gkatt-cwm-e98010g.lok of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Click to expand...
Click to collapse
It's just an extra step I like taking before flashing a partition with data that might be smaller than the original. And yes, that's pretty much what I typed.
madmack said:
It's just an extra step I like taking before flashing a partition with data that might be smaller than the original. And yes, that's pretty much what I typed.
Click to expand...
Click to collapse
another issue:
I am using loki_patch v1.5 to patch my custom build kernel
then I flash this Loki'ed kernel to my E988 (by CWM recovery) and it keep re-boot loop
(with the wording => Cause: Device Unlock, so boot success!!....) ==> it is the same Ok msg with boot to CWM recovery
which I believe if boot image LOKI'ed should be good
PS: I fixed this by re-flash the good boot image by CWM
Here is the output of the patching msg
[email protected]:/usr/android# ./loki_patch-linux-x86_64 boot aboot.img myboot.img myboot.lok
[+] loki_patch v1.5
[+] Detected target AT&T or HK LG Optimus G Pro build E98010g or E98810b
[+] Output file written to myboot.lok
[email protected]:/usr/android#
call me lazy, is there a zip file I could flash to do this from within the 2nd init recovery? :fingers-crossed:
I have never used adb before...
Hello everyone!
Here's another release thread for y'all!
What is this?
This is a flashable TWRP recovery for the Optimus G Pro.
Special thanks to @djrbliss
You can safely flash this to your phone's recovery and enjoy modding bliss!
How do I use this, and where do I get it?
Good question!
There are two ways to use the files provided here.
To Flash to Recovery:
I've created an easy installer for all you Windows folks!
Download this: http://downloads.codefi.re/thecubed/lgoptimusg_pro/gkatt/recovery/e98010g/easy-twrp-e98010g.zip
Extract it to somewhere on your computer.
Enable USB debugging on your phone, if you need the drivers I've included them in the "files/drivers" folder in the zip
Run the 'install.bat' script.
Check for any errors, if it was successful, you can 'adb reboot recovery' or use an app on your phone to get you into TWRP now!
Profit! (and realize that this was pretty easy!)
(thanks to hkfriends for pointing out the errors in my script!)
OR..
Download this file to somewhere on your computer https://github.com/djrbliss/loki/raw/master/bin/loki_flash
Download this file http://downloads.codefi.re/thecubed/lgoptimusg_pro/gkatt/recovery/e98010g/gkatt-twrp-e98010g.lok
Run the following:
Code:
adb push loki_flash /data/local/tmp
adb push gkatt-twrp-e98010g.lok /data/local/tmp
abd shell
su
cd /data/local/tmp
chmod 755 loki_flash
./loki_flash recovery gkatt-twrp-e98010g.lok
To boot
Download this file: http://downloads.codefi.re/thecubed/lgoptimusg_pro/gkatt/recovery/e98010g/gkatt-twrp-e98010g.img
Use fastboot boot to boot it
DO NOT FLASH THE .IMG FILE TO YOUR PHONE. It is only meant for fastboot booting.
Where can I find the source you used to build this?
All on my github!
http://github.com/thecubed/
Or, follow my guide here:
http://forum.xda-developers.com/showthread.php?p=43514195
What can I do with this?
Right now, the possibilities are unlimited. Once a security-lax boot.img is released, we can flash that through recovery and let the modding commence.
Please remember though, modding /system with the stock boot.img will result in a security error!
What works, and what doesnt?
I have not tested external SD cards, since I don't have one with me at work.
I have also not tested backups or restores in TWRP yet.
Can you show me a video?
Why yes I can!
As usual, please pardon the crappy camera work.
I <3 you so much, how do I show my love?
You are so kind
I most definitely do not expect donations of any kind, however they are appreciated a lot.
I purchased this phone off-contract just to get it unlocked, if you are a kind soul and would like to send me a token of your appreciation I would love you forever.
XDA has a neat "Donate to me" button that should be on the left side of this page under my name. Donations go to purchasing new hardware to work on and other neat stuff, so they're always appreciated.
Special Thanks!
In no particular order, special thanks to all of you guys!
djrbliss
hkfriends
synergy
Shelnutt2
DeamonFish
If I forgot anyone, let me know and I'll add you here!
Alright guys! Let me know if you find any bugs!
This is killer, I love twrp. So this will just over flash the cwm currently added earlier of course correct? Awesome work m8:thumbup:
EDIT: Not sure why but the Loki flash file downloads as a. Txt file for me
Sent from my LG-E980 using Tapatalk 2
maybe i am doing something wrong, but when i get into twrp the touch does not work
Very nice work there
testing back up and restore now
rbf351 said:
maybe i am doing something wrong, but when i get into twrp the touch does not work
Click to expand...
Click to collapse
Touch doesn't work? You have the ATT version, right?
That'd be very strange if it didn't work because of something in my kernel... it's pretty much just stock...
sorry for the "newbie" question...but the file to download are getting to the phone right?
thecubed said:
Touch doesn't work? You have the ATT version, right?
That'd be very strange if it didn't work because of something in my kernel... it's pretty much just stock...
Click to expand...
Click to collapse
yup, AT&T version, but it happens when i type in adb reboot recovery
Everything works so far tried backing up restore flashing and external sd... very nice work I will keep playing to see if i find any bugs
rbf351 said:
yup, AT&T version, but it happens when i type in adb reboot recovery
Click to expand...
Click to collapse
That's weird... I've been testing with that exact command and it's not doing it.
Can you possibly pull the kernel logs and pastebin them?
Do this while you're booted in recovery:
Code:
adb shell
dmesg > /sdcard/twrp_kmsg.txt
[press ctrl-c after a few seconds]
adb pull /sdcard/twrp_kmsg.txt
Thanks!
thecubed said:
That's weird... I've been testing with that exact command and it's not doing it.
Can you possibly pull the kernel logs and pastebin them?
Do this while you're booted in recovery:
Code:
adb shell
dmesg > /sdcard/twrp_kmsg.txt
[press ctrl-c after a few seconds]
adb pull /sdcard/twrp_kmsg.txt
Thanks!
Click to expand...
Click to collapse
won't all me to do it, i get the following error
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
error: device not found
rbf351 said:
won't all me to do it, i get the following error
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
error: device not found
Click to expand...
Click to collapse
Can you check to ensure that you have the ADB driver installed for your system? It is possible that your desktop hasn't installed the ADB interface while the phone is in recovery mode.
Start -> devmgmt.msc [enter]
Look to see if you have any unknown devices or "Android Phone" entries with no driver installed. That should do the trick.
thecubed said:
Can you check to ensure that you have the ADB driver installed for your system? It is possible that your desktop hasn't installed the ADB interface while the phone is in recovery mode.
Start -> devmgmt.msc [enter]
Look to see if you have any unknown devices or "Android Phone" entries with no driver installed. That should do the trick.
Click to expand...
Click to collapse
i have the following
ADB Interface
Android Sooner Single ADB Interface
edit, that wasn't while i was in recovery mode
in recovery mode i have
other devices
LG-E980 with an exclamation
I was able to flash and get into recovery without any issues. Excellent work! Thecubed and djrbliss, you guys are awesome!
here is the pastebin
http://pastebin.com/XPYi0v44
rbf351 said:
here is the pastebin
http://pastebin.com/XPYi0v44
Click to expand...
Click to collapse
Here's an interesting question... if you flash CWM instead, and press the softkeys at the bottom of the phone (the normal back and menu buttons) does anything happen? It looks like your touchscreen is being brought up successfully (despite the "[ 8.270257 / 03-05 11:00:29.766] Reflash Completed. Please reboot." line)
If softkeys work in CWM, then it means that something in TWRP isn't registering your touchscreen right. I'll look into that, should be fairly straightforward.
If softkeys don't work in CWM... that means something more strange. That means my kernel (or the boot commands I'm using) aren't compatible with your phone... which is indeed possible, since there are many revisions of each phone. (I hope this isn't the case!)
thecubed said:
Here's an interesting question... if you flash CWM instead, and press the softkeys at the bottom of the phone (the normal back and menu buttons) does anything happen? It looks like your touchscreen is being brought up successfully (despite the "[ 8.270257 / 03-05 11:00:29.766] Reflash Completed. Please reboot." line)
If softkeys work in CWM, then it means that something in TWRP isn't registering your touchscreen right. I'll look into that, should be fairly straightforward.
If softkeys don't work in CWM... that means something more strange. That means my kernel (or the boot commands I'm using) aren't compatible with your phone... which is indeed possible, since there are many revisions of each phone. (I hope this isn't the case!)
Click to expand...
Click to collapse
CWM works perfectly, i can navigate through all the menus using the softkeys
TWRP working perfectly here for me also! thank you for this! :good:
verry nice work........would be nice to have a kind od "how to" when thing get all set.....:good:
Uhmm there is a how to..
Sent from my LG-E980 using xda premium
Gotroot said:
Uhmm there is a how to..
Sent from my LG-E980 using xda premium
Click to expand...
Click to collapse
yeah ...but i have all the file....does i have to put the phone in download mode??
Hello Guys
I'am proud to present you the jackmu95 CWM Recovery auto-installer
In the moment the auto-installer is only available for the AT&T (D800) and the International (D802) LG G2. The Verizon variant will follow when I get the aboot.img for this device.
FEATURES
Multi platform support (Windows / OSX / Linux)
Fully automated recovery installation process
Choice between normal and touch recovery
Device check to avoid flashing on unsupported devices
Reboot into recovery option
REQUIREMENTS
Your phone has to be rooted
Installed LG mobile driver (Windows only)
Downloaded and extracted jackmu95 Recovery auto-installer
Enabled USB-Debugging
Accepted RSA Fingerprint message
INSTALLATION
Just run the install_recovery script and let the magic begin
DOWNLOADS
D800 (AT&T)
D802 (International)
CREDITS
ClockworkMod
CyanogenMod
Heatshiver
djrbliss
AndroidUser00110001
HOW-TO pull aboot.img
Because I only own the international version of LG G2 I need you help to support the other variants as well.
All you need to do is to follow the instructions below and sent me the aboot.img as PN.
HOW-TO pull aboot.img
Code:
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img
chmod 644 /data/local/tmp/aboot.img
exit
exit
adb pull /data/local/tmp/aboot.img
Hey thanks for porting CWM to the G2!
However, im facing errors installing it. My G2 is the international G802 one (even went into settings just to check that) but the installer has been saying it is not compatible with my phone.
Nice!
I have loki enabled recovery images here http://androtransfer.com/?developer=AndroidUser00110001&folder=/recovery/D800/ for the ATT(800) version and Verizon(Vs980) version if you want to use them.
It would be awesome if you could add Telus (d803) to cwm!
https://dl.dropboxusercontent.com/u/68562258/aboot.img
Are you sure you're using the correct property to determine the model #?
I see in your installer the following:
device=`./adb shell getprop ro.product.device`
# Check if device is correct
if [[ "$device" != *d802* ]]; then
And my d802 shows this:
[email protected]:/ $ getprop ro.product.device
g2
[email protected]:/ $ getprop ro.product.model
LG-D802
Sent from my LG-D802 using Tapatalk
fanghan said:
Hey thanks for porting CWM to the G2!
However, im facing errors installing it. My G2 is the international G802 one (even went into settings just to check that) but the installer has been saying it is not compatible with my phone.
Click to expand...
Click to collapse
erraggy said:
Are you sure you're using the correct property to determine the model #?
I see in your installer the following:
device=`./adb shell getprop ro.product.device`
# Check if device is correct
if [[ "$device" != *d802* ]]; then
And my d802 shows this:
[email protected]:/ $ getprop ro.product.device
g2
[email protected]:/ $ getprop ro.product.model
LG-D802
Click to expand...
Click to collapse
Please download the installer again!
I fixed device detection by looking for the device name in the fingerprint instead of the ro.product.device property
d802
i think there is a "bug" when u press wipe cache it freezed or takes too long (more than 10 minutes) to wipe the cache -_- anyway i m gonna try to back my rom so i can test the speed . thanks anyway
---------- Post added at 12:23 AM ---------- Previous post was at 12:13 AM ----------
back seems to me very fast! only 2 min for 3giga back up -_- ! thats awesome ! hope u fix the wipe cache bug now keep up the good work
Also seeing "not compatible with your device".
on 802 int
dukat0s said:
i think there is a "bug" when u press wipe cache it freezed or takes too long (more than 10 minutes) to wipe the cache -_- anyway i m gonna try to back my rom so i can test the speed . thanks anyway
---------- Post added at 12:23 AM ---------- Previous post was at 12:13 AM ----------
back seems to me very fast! only 2 min for 3giga back up -_- ! thats awesome ! hope u fix the wipe cache bug now keep up the good work
Click to expand...
Click to collapse
I just provide the installer for the CWM Recovery and haven't anything to do with the development of the recovery itself
d802
jackmu95 said:
I just provide the installer for the CWM Recovery and haven't anything to do with the development of the recovery itself
Click to expand...
Click to collapse
oO my fault then! thanks , it work like a charm after a reboot ! thanks
MarkyG82 said:
Also seeing "not compatible with your device".
on 802 int
Click to expand...
Click to collapse
Can you please provide me the output of
Code:
adb shell getprop
so I can look into the problem.
shell getprop returns:
error: device offline
and adb devices returns:
List of devices attached
02a03a1bd84c6678 offline
I'm guessing this is the issue.
how can I get it online? running Linux Mint BTW
MarkyG82 said:
shell getprop returns:
error: device offline
and adb devices returns:
List of devices attached
02a03a1bd84c6678 offline
I'm guessing this is the issue.
how can I get it online? running Linux Mint BTW
Click to expand...
Click to collapse
It seems that you haven't accepted the RSA fingerprint message. Do you have a message on your phones screen when you use adb?
nope. all I got is the debug bug, and USB connection selection.
what does the fingerprint message look like? Toast or pop up?
MarkyG82 said:
nope. all I got is the debug bug, and USB connection selection.
what does the fingerprint message look like? Toast or pop up?
Click to expand...
Click to collapse
plug your phone into usb, in shell type adb devices, wake your phone if it is sleeping and you should have a notification to accept the fingerprint message.
So I did what you said and got nothing. For giggles I tried all the connection types and plugged unplugged between each.
never get any pop up or nowt.
MarkyG82 said:
So I did what you said and got nothing. For giggles I tried all the connection types and plugged unplugged between each.
never get any pop up or nowt.
Click to expand...
Click to collapse
But you have USB-Debugging enabled, haven't you?
yep. looked around for other tips and they all give similar advice to what I've tried. Not normally needed for linux but i'm gonna reboot my pc just in case.
@AndroidUser00110001 - If you have the aboot.img for ATT or VZW I can create the CWM recoveries for those models.
I whipped up something quick based of stuff I used to do with the Droid X and what the Sony SP guys did.
This is twrp with a locked bootloader, the recovery partition is untouched, you can still get into that recovery. When the phone is booting, a green light will come on, hit volume up and then phone should vibrate within 3 seconds. If you hit the volume up then it should start loading twrp, otherwise it should continue with booting.
This is untested and I have a feeling the system will either not boot recovery, or not boot the main system.
This needs root.
This installs busybox, i know i should be using toybox
Someone please test, just extract the zip to your computer, plug in your phone, and run the appropriate file.
Do not test, I've tested it and I need to make changes
Sorry I was busy creating a new root method, got it working, almost done
Aaahh said:
I whipped up something quick based of stuff I used to do with the Droid X and what the Sony SP guys did.
This is twrp with a locked bootloader, the recovery partition is untouched, you can still get into that recovery. When the phone is booting, a green light will come on, hit volume up and then phone should vibrate within 3 seconds. If you hit the volume up then it should start loading twrp, otherwise it should continue with booting.
This is untested and I have a feeling the system will either not boot recovery, or not boot the main system.
This needs root.
This installs busybox, i know i should be using toybox
Someone please test, just extract the zip to your computer, plug in your phone, and run the appropriate file.
Click to expand...
Click to collapse
I need root to install it? Because marshmallow its unrootable
ericperez380 said:
I need root to install it? Because marshmallow its unrootable
Click to expand...
Click to collapse
Yup, in the future I might be able to make a marshmallow zip that'll let you run marshmallow with root and twrp. For that I need to relook into kernel modules because the kernel would have to be reloaded.
Aaahh said:
Yup, in the future I might be able to make a marshmallow zip that'll let you run marshmallow with root and twrp. For that I need to relook into kernel modules because the kernel would have to be reloaded.
Click to expand...
Click to collapse
Damn man you're a beast in does things good job doing this TWRP for locked bl, I'll be waiting till some feedback about this working
ericperez380 said:
Damn man you're a beast in does things good job doing this TWRP for locked bl, I'll be waiting till some feedback about this working
Click to expand...
Click to collapse
Yeah this opens the avenue for custom roms too, and multiboot and tons of stuff. Also, do not flash this if you are encrypted.
Aaahh said:
Yeah this opens the avenue for custom roms too, and multiboot and tons of stuff. Also, do not flash this if you are encrypted.
Click to expand...
Click to collapse
What you mean about encrypted, I don't know what's that
ericperez380 said:
What you mean about encrypted, I don't know what's that
Click to expand...
Click to collapse
If you encrypted your device. If you did you know.
Aaahh said:
If you encrypted your device. If you did you know.
Click to expand...
Click to collapse
No I don't encrypted it
Im at work.. Will Try to test it at home.
In between im bit confused how to flash this
Hopefully this will allow for us to write the drivers that would allow us to unlock the band's that are locked. If this allows us to write drivers.
So, just extract and run install.bat? On normal mtp mount?
Aaahh said:
I whipped up something quick based of stuff I used to do with the Droid X and what the Sony SP guys did.
This is twrp with a locked bootloader, the recovery partition is untouched, you can still get into that recovery. When the phone is booting, a green light will come on, hit volume up and then phone should vibrate within 3 seconds. If you hit the volume up then it should start loading twrp, otherwise it should continue with booting.
This is untested and I have a feeling the system will either not boot recovery, or not boot the main system.
This needs root.
This installs busybox, i know i should be using toybox
Someone please test, just extract the zip to your computer, plug in your phone, and run the appropriate file.
Click to expand...
Click to collapse
does it work with (vs986) version model
I'm interested to see if this works for the Canadian model (H812). Will keep watching this thread so good luck!
So the hope here is that we could downgrade to L, root, and then run this to get TWRP and install custom roms all without touching the recovery partition?
Has anyone had a chance to test this? I have a VS986 but it's the only phone I have with me right now so I'm hesitant to try myself
recharged20 said:
So, just extract and run install.bat? On normal mtp mount?
Click to expand...
Click to collapse
Yeah uses adb
ANDROID2468 said:
does it work with (vs986) version model
Click to expand...
Click to collapse
It should work with all G4s, exception might be T-Mobile
ReeS86 said:
I'm interested to see if this works for the Canadian model (H812). Will keep watching this thread so good luck!
Click to expand...
Click to collapse
Yeah it should, in fact it may work on yours but not the Verizon because I used the twrp from the international. Easy fix tho if that's the caw
Wumbonaut said:
So the hope here is that we could downgrade to L, root, and then run this to get TWRP and install custom roms all without touching the recovery partition?
Has anyone had a chance to test this? I have a VS986 but it's the only phone I have with me right now so I'm hesitant to try myself
Click to expand...
Click to collapse
Yeah I'm in the same predicament.
coolguy71261 said:
Hopefully this will allow for us to write the drivers that would allow us to unlock the band's that are locked. If this allows us to write drivers.
Click to expand...
Click to collapse
No that probably won't be as the drivers are probably locked at bootloader level not system
Wait. I'm confused.
Q: does it work with (vs986) version model
A: It should work with all G4s, exception might be T-Mobile
Q: I'm interested to see if this works for the Canadian model (H812). Will keep watching this thread so good luck!
A: Yeah it should, in fact it may work on yours but not the Verizon because....
Soooo - it should work with the verizon G4 or it shouldn't?
Aaahh said:
I whipped up something quick based of stuff I used to do with the Droid X and what the Sony SP guys did.
This is twrp with a locked bootloader, the recovery partition is untouched, you can still get into that recovery. When the phone is booting, a green light will come on, hit volume up and then phone should vibrate within 3 seconds. If you hit the volume up then it should start loading twrp, otherwise it should continue with booting.
This is untested and I have a feeling the system will either not boot recovery, or not boot the main system.
This needs root.
This installs busybox, i know i should be using toybox
Someone please test, just extract the zip to your computer, plug in your phone, and run the appropriate file.
Click to expand...
Click to collapse
I ran this with a Verizon G4 and it doesn't appear to work. I don't get a green light when I boot up nor does pressing the Vol Up button at any point during boot up appear to have any affect. Perhaps I'm missing something in order to get into TWRP but from what I can tell it does not work.
One other note, the batch file for the windows installation needs to be edited: In this section PUSH needs to be changed to INSTALL. Not sure it matters if it doesn't work overall but wanted to let the you know.
USH <------- Should be INSTALL
@ECHO Let's go!
@adb\adb kill-server
@adb\adb wait-for-device
@adb\adb push common\logwrapper /data/local/tmp/
@adb\adb push common\twrp.cpio.gz /data/local/tmp/
@adb\adb push common\busybox /data/local/tmp/
@adb\adb push common\step1.sh /data/local/tmp/
@adb\adb shell chmod 755 /data/local/tmp/step1.sh
@adb\adb shell su -c "mount -o remount,rw /system"
@adb\adb shell su -c /data/local/tmp/step1.sh
@adb\adb shell rm /data/local/tmp/step1.sh
@pause
@goto MENU
shmoode1 said:
I ran this with a Verizon G4 and it doesn't appear to work. I don't get a green light when I boot up nor does pressing the Vol Up button at any point during boot up appear to have any affect. Perhaps I'm missing something in order to get into TWRP but from what I can tell it does not work.
One other note, the batch file for the windows installation needs to be edited: In this section PUSH needs to be changed to INSTALL. Not sure it matters if it doesn't work overall but wanted to let the you know.
USH <------- Should be INSTALL
@ECHO Let's go!
@adb\adb kill-server
@adb\adb wait-for-device
@adb\adb push common\logwrapper /data/local/tmp/
@adb\adb push common\twrp.cpio.gz /data/local/tmp/
@adb\adb push common\busybox /data/local/tmp/
@adb\adb push common\step1.sh /data/local/tmp/
@adb\adb shell chmod 755 /data/local/tmp/step1.sh
@adb\adb shell su -c "mount -o remount,rw /system"
@adb\adb shell su -c /data/local/tmp/step1.sh
@adb\adb shell rm /data/local/tmp/step1.sh
@pause
@goto MENU
Click to expand...
Click to collapse
It should not be install it should be push.
Did you use install or push
Does your phone still boot?
I had to guess the led paths so they may be wrong
It made a log, I'll send you the path of it on your phone so you can send it to me
Aaahh said:
It should not be install it should be push.
Did you use install or push
Does your phone still boot?
I had to guess the led paths so they may be wrong
It made a log, I'll send you the path of it on your phone so you can send it to me
Click to expand...
Click to collapse
I used install, otherwise when I tried to install it, Option 1, the CMD window just closed. When I changed it to Install it ran and showed TWRP Successfully installed.
Yes it still boots.
Let me know the path, I'll send the log file.