Develop Bugs

Superuser+su+busybox for i9000 [26.06.2010]

I found that some of the new user they dont know from where they can bring the tools to flash roms or kernels so i will help them by uploading all files they need to do that...
1- android-sdk-windows
2- i9000_Kernel_LK9_01b9.tar
3- i9000_Kernel_Original.tar
4- Kies_1.5.0.10052_28.exe
5- Odin3_v1.0.exe
6- s1_odin_20100513.pit
7- Superuser.apk
8- su
9- Superuser_v1_CSC.tar
10-update.zip
http://www.mediafire.com/?yqzebmymnn2
and to download any oem roms go to this website and make registration and download any rom you want
http://samsung-firmware.webs.com/WEBPROTECT-samsungi9000.htm
-WARNING: THIS METHOD CAN BE DANGEROUSE. DO NOTHING IF YOU DO NOT KNOW WHAT YOU DO.
I CAN'T BE RESPONSIBLE IF YOU TRANSFORM YOUR I9000 LIKE A BRICK
Tested on JF2 and JFB
First method:
If you have adb and you know how to use it!
1. Download: update.zip
2. Put update.zip to SD card
3. Enter
Code:
adb reboot recovery
4. In Recovery menu select 'apply sdcard:update.zip' (use vol_down + home)
Phone will reboot
and you have
1. su+Superuser
2. busybox (/system/xbin/busybox)
Second method:
If you have Odin3 and you know how to use it!
Your data and programs will be deleted!!!!
1. Download: Superuser_v1_CSC.7z
2. Unpack
3. Flash this file as CSC file with Odin3
How to install busybox utils
in terminal enter
Code:
su
busybox --install -s /system/xbin
i get it from here
http://forum.samdroid.net/f49/superuser-su-busybox-i9000-26-06-2010-a-1355/

ADB cant find phone, I had adb set up for my G1, what do I need to use adb on my SGS?

go to settings>applications>development>usb debugging and mark it
after that connect your usb it will work
note make sure you install all drivers will

Many thanks...thought it was something simple i had forgoten!
edit: SGS now rooted!!

Nice One Thanks will this work with an out of the box galaxy s or does it need to have something else done to it??? thanks
EDIT: Im suprised theres not so many people like amazed cuz this is great
EDIT2: Thought i put the links on to this forum might help to put them in 1st post update.zip and Superuser_v1_CSC.7z
EDIT3 lol : Do we need to mod the kernal to overclock or canwe now jus over clock it if so to what sppeds ??

yes...just out the box, I used
http://forum.samdroid.net/f49/superuser-su-busybox-i9000-26-06-2010-a-1355/ (same as above!)
its SOO easy just to get superuser and SU, I was so happy to get titanium backup working again..

kirandeep said:
yes...just out the box, I used
http://forum.samdroid.net/f49/superuser-su-busybox-i9000-26-06-2010-a-1355/
its SOO easy just to get superuser and SU, I was so happy to get titanium backup working again..
Click to expand...
Click to collapse
Thank-You that is good isnt it then and much easier realy than my hero

no problems...theres no recovery yet, just SU i think..im no expert but i could follow those instructions once i got ADB working.

Qustion,
If i rooted my phone and want to go back to the original FW or i missed something and never worked and want to reflash my phone again with the untouched FW, Is it okay? or my phone will be bricked as a result of bad rooting?!
need to know that.

Thank you!

Please help me
I am ok with computers but very n00b to smartphones.
I downloaded SDK, enabled USB debugging, in CMD my serial came up so that was all ok.
I put the update.zip on the sd card of the phone and turned on the phone with vol down + home key expecting it to let me choose the update.zip but I got a yellow android triangle screen with the android bot icon using a spade and underneath it says
"downloading.....
Do not turn off target!!!"
What have I missed?
Thanks in advance

dan 6a said:
Please help me
I am ok with computers but very n00b to smartphones.
I downloaded SDK, enabled USB debugging, in CMD my serial came up so that was all ok.
I put the update.zip on the sd card of the phone and turned on the phone with vol down + home key expecting it to let me choose the update.zip but I got a yellow android triangle screen with the android bot icon using a spade and underneath it says
"downloading.....
Do not turn off target!!!"
What have I missed?
Thanks in advance
Click to expand...
Click to collapse
Did you enable USB debugging on the S? It's off the Settings|Applications|Development menu.
In the CMD shell, did you go to the android-sdk-windows\tools directory and run 'adb reboot recovery' with the USB lead connected?

Thankyou
I did it, I didn't put in the command shell, I rebooted it thinking the vol down + home would bring me into the recovery screen
How do I confirm it worked? It looked like it was doing stuff.. *edit I found the superuser app*

Wow sounds great! Custom recovery anyone!? Just got back from romania, nice little treat!
-------------------------------------
Sent via the XDA Tapatalk App

Hi,
i'm new to this..I have a I9000 and maybe I wan't to root it.
But I have some questions first and i I hope anybody can help me.
1) Can you go back to the stock settings ?
2) Do you still have your warranty?
3) Can you put a costum ROM on it? Example: Can you use the ROM they use on a nexus one?
4) What can you do more when u are a superuser?
Thnx

worked perfectly (first method) fast and simple
I have root now
can't wait for custom recovery.

the busybox in here was not very good had to let titanium backup update to its version of busy box.

If you want the full featured busybox, why not taking this one?

removing apps..
can someone help me out please, i cant seem to find a way to remove apps that are already installed from samsung...

Do you have already root? Then you should open your command line where your adb binary lies in and type the following:
Code:
adb shell
su
cd /system/app
ls
and identify the packages which you don't need and remove them by typing:
Code:
rm PACKAGENAME.apk
rm PACKAGENAME.odex

Xoom WiFi (MZ604) Root!!

This is it guys... HUGE props to bigrushdog (his kernel made this possible!), MADindustries and modplan!
Download the Motorola WiFi Xoom Root Zip file and unzip it. (MediaFire) - Contains Tiamat 1.3.1
You need the Moto Drivers - Read this thread to START you - http://forum.xda-developers.com/showthread.php?t=981578
You'll need fastboot - get it here http://developer.htc.com/adp.html
Make sure you have the latest SDK - adb and fastboot should be in /platform-tools - http://developer.android.com/sdk/index.html
Place the files in the SDK Tools folder.
If rebooting works... - This will wipe your phone by the way!!
adb reboot bootloader
fastboot oem unlock
adb reboot bootloader
If stuck at "Dual Core Technology"
Hold VolUp and power to restart Xoom
Hold VolDown will booting unit for fastboot mode
fastboot flash boot boot.img
fastboot reboot
adb shell
mkdir /data/media/sdcard2
exit
(physically put in microSD card if you are planning to use)
adb reboot
adb remount
adb push bcm4329.ko /system/lib/modules/bcm4329.ko
adb push cifs.ko /system/lib/modules/cifs.ko
adb push tun.ko /system/lib/modules/tun.ko
adb push scsi_wait_scan.ko /system/lib/modules/scsi_wait_scan.ko
adb push su /system/bin
adb shell ln -s /system/bin/su /system/xbin/su
adb shell chmod 4755 /system/bin/su
adb push Superuser.apk /system/app
adb push vold.fstab /system/etc/vold.fstab
adb reboot
adb shell
WE HAZ ROOT!!
Check out this video for basic Windows walkthrough from Buddhahb - http://www.youtube.com/watch?v=ZsVpY0PDwtQ
Check out this video for basic Mac walkthrough from sleeplessninjas - http://www.youtube.com/watch?v=zC6J-hV6SM4
Update: 3/27/2011 12:04pm CST Added cifs.ko, tun.ko, and scsi_wait_scan.ko
Update: 3/27/2011 12:22pm CST Added vold.fstab file for USB mounting & MegaUpload
Update: 4/13/2011 10:07am CST Updated to Tiamat's 1.3.1 kernel for SD card support & Gallery support.

awesome work guys!

Woooooooooooooooooooooooooot

fantastic work!!
\o/

can you try the cifs.ko module as well? i have a 3g version and am curious

Thanks Xaositek and HUGE props to MADindustries and modplan for coming up with a quick solution.
Is there a rip of the stock "boot.img" in case it doesn't work so that people who soft brick their xoom can return it back to stock? If so can that be posted in the OP's post? I know I am not the only paranoid one that would like to have the stock boot.img before attempting any rooting.
Also just for curiousity, can someone explain the differences between the wifi and wifi+3g boot.img versions and what they had to do to workaround this. Thanks.

We end up replacing the stock boot - We'll probably need to wait for Motorola to toss us a bone there

I just downloaded the "xoomwifiroot.zip" file and realized the files in the "xoomwifiroot.zip" are just tiamat's 1.1.6 files (boot.img and kernel modules) that can be found in tiamat's thread.
I was expecting the files to be something different that was close to the original root method by Koush where there is a "rootboot.img".
Maybe a better question for my understanding is this. Sorry if I am a noob.
Is Koush's file rootboot.img for the original xoom root only good for rooting the system while tiamat's boot.img file not only roots the system but also has code to overclock the xoom?

ericdabbs said:
I just downloaded the "xoomwifiroot.zip" file and realized the files in the "xoomwifiroot.zip" are just tiamat's 1.1.6 files (boot.img and kernel modules) that can be found in tiamat's thread.
Click to expand...
Click to collapse
It also has the su and Superuser.apk but essentially yes...
ericdabbs said:
Is Koush's file rootboot.img for the original xoom root only good for rooting the system while tiamat's boot.img file not only roots the system but also has code to overclock the xoom?
Click to expand...
Click to collapse
Koush's rootboot got us into this mess, Tiamat's boot.img got us out of it. It also allows the critical adb remount to allow the next steps.

Xaositek said:
It also has the su and Superuser.apk but essentially yes...
Koush's rootboot got us into this mess, Tiamat's boot.img got us out of it. It also allows the critical adb remount to allow the next steps.
Click to expand...
Click to collapse
Gotcha. Thanks for all your help.

ericdabbs said:
Gotcha. Thanks for all your help.
Click to expand...
Click to collapse
Grab the latest file from MegaUpload and add the additional modules

glad I could help get this working and glad that it fixed my bricked xoom! One thing that I would suggest is someone pull the stock ko files and save them, after moto releases the stock boot.img files I am sure that there will be some people that want to go back to the stock kernel which will then be as easy as flashing the stock boot.Img and then pushing the stock ko files back on.

Guess I'll run out and grab one now at Best Buy then. Thanks!

modplan said:
glad I could help get this working and glad that it fixed my bricked xoom! One thing that I would suggest is someone pull the stock ko files and save them, after moto releases the stock boot.img files I am sure that there will be some people that want to go back to the stock kernel which will then be as easy as flashing the stock boot.Img and then pushing the stock ko files back on.
Click to expand...
Click to collapse
Is there a way to extract the stock boot.img and wifi ko files before flashing it with tiamat's files? If so, what are the instructions so that people who haven't rooted it yet can give it a try. That way we can give back to the community.

ericdabbs said:
Is there a way to extract the stock boot.img and wifi ko files before flashing it with tiamat's files? If so, what are the instructions so that people who haven't rooted it yet can give it a try. That way we can give back to the community.
Click to expand...
Click to collapse
Pulling the boot image looks like it is rather difficult but pulling the ko files should be as simple as using the adb pull command instead of adb push. For example
Adb pull /system/lib/modules/something.ko c:/something.ko (put the right paths obviously the second path is just where you want to save it on your computer)

As an FYI. coolbho's ocboot.img does not work on the wi-fi version of the xoom yet. To prevent your headaches I have already flashed and it stays at boot screen. Tiamat's seems the only kernel that is working for wi-fi only

modplan said:
Pulling the boot image looks like it is rather difficult but pulling the ko files should be as simple as using the adb pull command instead of adb push. For example
Adb pull /system/lib/modules/something.ko c:/something.ko (put the right paths obviously the second path is just where you want to save it on your computer)
Click to expand...
Click to collapse
Got it. When I get my wifi xoom, I'll give this a shot.

d3coy3d said:
As an FYI. coolbho's ocboot.img does not work on the wi-fi version of the xoom yet. To prevent your headaches I have already flashed and it stays at boot screen. Tiamat's seems the only kernel that is working for wi-fi only
Click to expand...
Click to collapse
Tiamat's kernel allows for the 1.5ghz OC

When i command to push the first file, I get all the info on android debug.

chaz03 said:
When i command to push the first file, I get all the info on android debug.
Click to expand...
Click to collapse
Revisit the instructions now - you can just copy and paste them all now

[Q] Downgrade from 4.2 to 4.1?

So, I finally decided to ditch HTC Sense try an AOSP rom. I'm glad I did. Though, I originally got this rom:
http://forum.xda-developers.com/showthread.php?t=2013506
I feel that 4.2 has too many bugs and I want to go back to 4.1.
After a good two hours of searching, I noticed that some people with the Nexus 7 had complicated procedure in order to get it back.
So, do I have to do the same? If so, how would I do it? The search is only giving me results for Nexus devices and I'm not sure if they would work for mine...
Thanks in advance!

I fixed it.
In case you're wondering, here's how I did it:
1. Make backups in case anything goes wrong.
2. boot into fastboot and flash the boot.img of the 4.1 rom you are going to.
3. boot into recovery.
4. restore a backup or flash a .zip
5. while in recovery, plug your phone into your computer and type these commands exactly:
adb shell
cd /sdcard/0/
mv * ../
mv .* ../
cd ..
rmdir 0
(You may get a few errors, but it's ok. You can make sure it worked by using the AROMA file manager)
6. reboot

i did the same and i follow the steps written by ilikejuice and it works

[TUTORIAL]All you need to know to flash a ROM on LG-P350

Hi guys, this is my second tutorial and in this one I will show you every thing you need to do to flash a custom ROM on the LG-P350. So let's get started.
DISCLAIMER: This is tampering with the system itself and if done incorrectly a simple factory reset will not fix it. It is YOU who is doing this on your phone and I am in no way responsible if any damage happens to your device. (tough it shouldn't if you follow these steps carefully) You have been warned!
WHAT WE NEED :
1.An LG-P350 running stock Froyo
2.LG mobile united drivers, get them from here https://docs.google.com/file/d/0B7Faau7Enf-Bc1hhbWRtTkczNEE/edit?usp=sharing
3.A PC running Windows (can be done on linux too but this guide is based on Windows)
4.A microUSB data cable.
5.The official Android SDK obtained from http://developer.android.com/sdk/index.html Make sure you select the version for your OS (32-bit or 64-bit)
6.USB debugging to be on. Go to Settings>Apps>Development>Turn on USB debugging
7.ADB to be properly set up.
8.Patience to read this thread carefully
1. Root
Ok so what is root? Well simply said rooting gives us the permission to modify parts of the Android system itself. Normally when you try to tamper with it it would simply say that either you don't have the privilege to do so or it would fail. When we have root permissions then you can change anything you want.
Note: Be careful tough, removing or modifying some parts of the system can damage the system and prevent it from working/booting. Always make a nandroid backup (will talk about this later) before editing anything in the system.
Now for the rooting itself.
Most versions of the software for the P-350 can be rooted using gingerbreak, which can be found here http://forum.xda-developers.com/showthread.php?t=1044765 Get the newest version, copy it and install it on your phone and follow the instructions on screen.
For those who prefer some other root method you can also use z4root which can be found here http://forum.xda-developers.com/showthread.php?t=833953 or superoneclick which can be obtained here http://forum.xda-developers.com/showthread.php?t=803682 (For superoneclick you need the USB cable and drivers installed)
2.ADB
Ok so what is ADB? ADB is a short term for Android Debug Bridge. It is one the most essential tools in the Android world and is used for a number of things such as sending commands (which can do anything you imagine with the device), getting various log data etc.
To set it up you will have to get the latest version of the official Android SDK (look for the link in the Introduction). Once you've downloaded the sdk you will get a .zip file you need to extract. I extracted mine to C:\Program Files (x86)\Android\ (so this guide is based on that) but it can really be anywhere. If you decide to put a different directory then adapt the guide to it. Once extracted you will get two folders. Here we only use the sdk one, the other one is for the Eclipse plugin used for application development. Open up the cmd from the start menu and then input these codes.
Code:
cd C:\Program Files (x86)\Android\sdk\platform-tools\ (you adapt this to your case if you didn't extract it there)
adb shell
Do this with your device connected otherwise it's pointless.
NOTE1: In order for adb to recognize your device you must have the drivers installed.
NOTE2: If you are too lazy to type all this every time you can make a .bat script. Open up notepad and copy/paste these codes
Code:
cd C:\Program Files (x86)\Android\sdk\platform-tools\ (adapt to your location)
adb shell
pause
After that just click on File and click Save as. In the window that opened, under file type select all files and on the file name save it as adb.bat
Now whenever you want to use adb you can just double click on the script you made and it will open up adb instantly leaving out the hassle of typing in commands every time.
3.Recovery
Now that we have root it's time for the recovery module.
The recovery allows us to modify parts (or even the entire) system by "flashing" (installing) .zip files prepared by our developer. They can be tweaks,fixes, additional features or even a completely new version of Android. There are a couple of ways to do this and the choice is yours.
Before you do this you need to get a recovery image. We have a couple of them for our device:
1. AmonRa-The very first recovery for our phone. It is outdated and generally not recommended for use. If anyone wants it you can get it here http://forum.xda-developers.com/showthread.php?t=1080911
2. CWM (clockwork mod recovery)- One of the most popular recoveries around. It is a well made piece of software which will make flashing simple and fast. We have a couple of versions for our phone and the links are here:
http://forum.xda-developers.com/showthread.php?t=2075797&highlight=recovery ClockWorkMod 6.0.2.7
http://forum.xda-developers.com/showthread.php?t=1768895&highlight=recovery ClockWorkMod 6.0.1.4
You will also need a flash_image file gotten from https://docs.google.com/file/d/0B7Faau7Enf-BTURDQmp1OWIzVGM/edit?usp=sharing
Method 1: cmd
Ok so this tutorial is from a developer who has retired and who made the original recovery our phone. All credits for that go to him.
Also note that it is recommended to reboot the device prior to flashing to increase the RAM.
1.Copy the .img file and copy the flash_image file to the rood directory of your sd card NOT in some folder. If you got your recovery in a .zip then extract the .img file from it and copy it and the flash_image file to the root of the sd card.
2.Using ADB shell copy these commands into the cmd :
Code:
$ su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
# cat /sdcard/flash_image > /system/bin/flash_image
# chmod 755 /system/bin/flash_image
# sync
3.Now flash it:
Code:
$ su
# flash_image recovery /sdcard/*insert image name here*.img Here you should put the name of your .img file without the starts ofc :)
# sync
4.After that if no error occurred you can type this in
Code:
reboot recovery
WARNING: If some sort of error showed up DO NOT type in reboot recovery. This could brick your device. Instead restart the phone and start over.
Method 2: Venkat's toolkit RECOMMENDED
This toolkit does the same from above but it does it automatically without the user having to do anything. You can get it from here http://forum.xda-developers.com/showthread.php?t=1948326 It can also be used for rooting.
It is also recommended to make a nandroid backup of your current system in case you want to go back. Nandroid backup is a complete copy of your system as it is when the backup was made. It backs up EVERYTING not just apps and data, so it is a perfect thing to have if a ROM or a tweak you are trying render the phone unbootable since you can just restore the backup you made and no harm done.
That is recovery. Now you can use it to flash whichever ROM for our device you choose. You can boot to it either by typing in adb/terminal reboot recovery or by pressing the following buttons when the device is turned off: Power + Call + Volume Down. Also don't worry if the touchscreen doesn't work in the recovery. That is normal use the volume up and down buttons to navigate menus and either the menu button(for amon ra) or the call (CWM) to confirm your choice.Use the back/power button to cancel/go back.
4.Flashing
Flashing is a process where we install the entire system or its parts contained in .zip files from the recovery module.
NOTE When you get a flashable .zip package DON'T extract it to the sd card. Copy it as you got it to the root of the sd and then continue.
Now that you've gotten the ROM you desired the process is pretty straight forward. Copy the .zip file you got to the root directory of your sd. Once you've done that, reboot to recovery and make a nandroid backup (if you haven't done so already) and go to the option install zip from sd card. Then choose the .zip you copied and confirm. After it says install complete you can reboot your device.
NOTE 1: Flash only things that are either universal or made for this device. Flashing stuff not made to work on this device could damage it.
NOTE 2: When flashing new ROMs you MUST wipe Dalvik cache,cache and data partitions. It is also recommended to wipe Dalvik cache when flashing kernels.
Those are pretty much all the basics you need to get into the flashing stuff You can find loads of ROMs and other tweaks on the official P-350 forums here on xda http://forum.xda-developers.com/forumdisplay.php?f=1769
You can also find info and development support on our Facebook page https://www.facebook.com/groups/p350development/

Revision 1: Added tutorial for setting up adb, explaining what adb is, as well as an adb script code.

i think this thread need to stick, try to contact mods

A comment on the 'adb' way. Before executing the commands, you might want to cd to where adb.exe is because you will have an error executing the command and the terminal will show 'adb is not a valid command'
Sent from my X8 using xda premium
---------- Post added at 07:09 AM ---------- Previous post was at 07:07 AM ----------
And installing android sdk is optional because there are standalone adb available for download.
Sent from my X8 using xda premium

Ya sticky this thread mods, cuz' i read, Many people stuck at LG Logo or fastboot mode even hard reset when flashing ROM without recovery before..
Sent from my LG-P350 using xda app-developers app

rho57 said:
A comment on the 'adb' way. Before executing the commands, you might want to cd to where adb.exe is because you will have an error executing the command and the terminal will show 'adb is not a valid command'
Sent from my X8 using xda premium
---------- Post added at 07:09 AM ---------- Previous post was at 07:07 AM ----------
And installing android sdk is optional because there are standalone adb available for download.
Sent from my X8 using xda premium
Click to expand...
Click to collapse
It already is set to the adb.exe path that's needed in order for adb to be activated on Windows. That's why we use the cd C:\Program Files (x86)\Android\sdk\platform-tools
And I know but there are a lot of other useful tools as well. And it is most reliable too.

Good job dude

Why complicated more then needed. Just make tut with andking toolkit.

boyan81 said:
Why complicated more then needed. Just make tut with andking toolkit.
Click to expand...
Click to collapse
Not complicated, this is a basic tutorial for those who don't want/can't use his toolkit. It also has some explanations about basic Android terms which you won't find there.

It would be nice if you update the wiki too, as there is an old but yet usable guide which pretty much has the same information written here...
Sent from my GT-S5830M using Tapatalk 2

[Recovery][TWRP][ATT-ONLY!] Flashable TWRP recovery!

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??