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

LG Optimus Chic (e720) Custom Recovery + Kernel (overclock)!

This Custom Recovery and this Custom Kernel were created by drellisdee! All credits goes to him! I just created this post to show this great news at all LG Optimus Chic's owner. Special thanks by all of us to drellisdee.
After thanking drellisdee and have assigned all the merits of his work, we start with the guide.Remember that this recovery is still in beta, I do not assume any responsibility in case of brick or malfunction.
1) Root your device with z4root or SuperOneClick
2) Download this recovery and unzip it into the root of your sdcard.
Recovery Drellisdee (password is "gnmtest", without the " ")
3) Download flash_image.zip and unzip into the root of your sdcard.
Flash_Image.zip
4)And now give these commands through the terminal or adb shell.
Code:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 0755 /system/bin/flash_image
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak (notice this file install-recovery.sh may not be on your device if it gives an error or file not found move on)
flash_image recovery /sdcard/recovery-alessi-gnm.img
sync
Then power off device and boot holding most likely vol-dn + vol-up + power button. You will see the custom recovery. To move into the recovery: Vol Up and Vol Down to go up and down. Back to go back and Menù to give enter.
The message E: bad boot message is normal disregard it.
For debugging use the move recovery-log to sd option under other and please upload it with feedback.
And nooooooow... The Custom Kernel!
Custom Kernel (for overclocking)
(password is "keepout", without the " ")
Put this kernel (not extract!!!!!) into the root of your sdcard.
Then flash it with this newest Custom Recovery!
Personally, I was able to step up the cpu to 729mhz ... This kernel is still a "beta", drellisdee said that soon it will improve and make it more stable.
Links works again!
Thanks again drellisdee!

Tested... Works 100%

Thanks for sharing this useful tweaks. it work pretty well on my e720, but my stock launcher always crash recently, don't know if this problem relate to this custom recovery.
sorry for my bad english.

Updated my recovery thread is here 2.2.1
Updated to 3.06 http://androidforums.com/getitnowmarketing/330813-all-one-recovery-thread.html

Thank U very much！It's too late to find this post；I'm a chinese， please forgive my terrible english。Thank u very much

Oh It's a good kernel..
I need a your help
Could you give a mcs6000.c (touchbug fixed) to me?
I made a kernel for korean chic
I made a oc kernel for korean chic but I can't fix touchbug....
please help me for korean chic.....
my e-mail address is '[email protected]'
I sorry to my bad english

Awesome share. It works, and I flashed mine with AndMelk rom. Now, my chic is running smooth... Thanks.

Updated recovery http://androidforums.com/getitnowmarketing/330813-all-one-recovery-thread.html
Andreoid said:
This Custom Recovery and this Custom Kernel were created by drellisdee! All credits goes to him! I just created this post to show this great news at all LG Optimus Chic's owner. Special thanks by all of us to drellisdee.
After thanking drellisdee and have assigned all the merits of his work, we start with the guide.Remember that this recovery is still in beta, I do not assume any responsibility in case of brick or malfunction.
1) Root your device with z4root or SuperOneClick
2) Download this recovery and unzip it into the root of your sdcard.
Recovery Drellisdee (password is "gnmtest", without the " ")
3) Download flash_image.zip and unzip into the root of your sdcard.
Flash_Image.zip
4)And now give these commands through the terminal or adb shell.
Code:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 0755 /system/bin/flash_image
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak (notice this file install-recovery.sh may not be on your device if it gives an error or file not found move on)
flash_image recovery /sdcard/recovery-alessi-gnm.img
sync
Then power off device and boot holding most likely vol-dn + vol-up + power button. You will see the custom recovery. To move into the recovery: Vol Up and Vol Down to go up and down. Back to go back and Menù to give enter.
The message E: bad boot message is normal disregard it.
For debugging use the move recovery-log to sd option under other and please upload it with feedback.
And nooooooow... The Custom Kernel!
Custom Kernel (for overclocking)
(password is "keepout", without the " ")
Put this kernel (not extract!!!!!) into the root of your sdcard.
Then flash it with this newest Custom Recovery!
Personally, I was able to step up the cpu to 729mhz ... This kernel is still a "beta", drellisdee said that soon it will improve and make it more stable.
Links works again!
Thanks again drellisdee!
Click to expand...
Click to collapse

[GUIDE] Mini guide to root Gnex manually

1. Download and install Samsung_USB_Driver_for_Moblie_Phones_v1_4_6_0.exe
Link to download: http://www.multiupload.co.uk/YXE6FWLFAR
2. Download and install Android SDK (http://dl.google.com/android/android-sdk_r16-windows.zip)
3. With the phone turned OFF, hold VOLUME UP + VOLUME DOWN and power the phone on. This will put you in bootloader mode
4. Using windows/cmd go to the folder where Android SDK was installed (make sure that the folder android-sdk/platform-tools/ contains fastboot.exe and adb.exe etc....
5. using windows/cmd go to the folder /android-sdk/platform-tools
From this folder try the command "fastboot devices" (do not include ") which should list the device connected to your PC.
6. First we have to unlock bootloader,
use this command to unlock bootloader > fastboot oem unlock
(warning.. you will loose all data)
After the bootloader is unlocked the device will reboot normally.
7. Once normally booted from the command prompt issue the commands given below (after each command press enter button)
Note: you need su and superuse.apk (which can be downloaded from here: https://rapidshare.com/files/1319181583/su.zip)
unzip the downloaded file in the same folder where fastboot.exe exist i.e /android-sdk/platform-tools/
adb root
adb remount
adb push su /system/bin
adb push Superuser.apk /system/app
adb shell chmod 06755 /system/bin/su
adb shell chmod 06755 /system/app/Superuser.apk
adb reboot
Done!... your device is now rooted.

it would be good to note that many people have issues with the initial android driver installation.
if you install the drivers, but the phone doesn't show up after a period of time, open control panel -> system -> device manager and look for any devices that have a yellow triangle error (no driver). right click and open properties, and manually select the driver, not auto! the next screen will give you an option to 'select from a list', do this, and find SAMSUNG, then select the latest drivers.
after this, it can still take a minute or two the first time for drivers to install properly, you usually can see the status of this in the usb system tray icon.
if you rebooted to the bootloader (power vol(+) vol(-)), from the command line, if you type "fastboot devices" it should list a device and serial number. if not, you need to go check your drivers, something is missing. also, don't forget how magical a windows reboot can be at times : )

cancerouspete said:
it would be good to note that many people have issues with the initial android driver installation.
if you install the drivers, but the phone doesn't show up after a period of time, open control panel -> system -> device manager and look for any devices that have a yellow triangle error (no driver). right click and open properties, and manually select the driver, not auto! the next screen will give you an option to 'select from a list', do this, and find SAMSUNG, then select the latest drivers.
after this, it can still take a minute or two the first time for drivers to install properly, you usually can see the status of this in the usb system tray icon.
if you rebooted to the bootloader (power vol(+) vol(-)), from the command line, if you type "fastboot devices" it should list a device and serial number. if not, you need to go check your drivers, something is missing. also, don't forget how magical a windows reboot can be at times : )
Click to expand...
Click to collapse
Hi
Thanks for this note which would help many users.

Hi, noob here.
First of all, thanks for the guide.
I have already unlocked the bootloader about a month ago (up to step 6), but would like to root.
Will my phone lose all data again if I root the phone now? I'm not even sure what this actually does, but would like to learn and mess around with it.

You will not loose data. Rooting gets access your system folders by pushing su and superuser through adb.
Hope it helps.
Sent from my Galaxy Nexus using xda premium

smohanv said:
Note: you need su and superuse.apk (which can be downloaded from here: https://rapidshare.com/files/1319181583/su.zip)
unzip the downloaded file in the same folder where fastboot.exe exist i.e /android-sdk/platform-tools/
adb root
adb remount
adb push su /system/bin
adb push Superuser.apk /system/app
adb shell chmod 06755 /system/bin/su
adb shell chmod 06755 /system/app/Superuser.apk
adb reboot
Done!... your device is now rooted.
Click to expand...
Click to collapse
Did you actually test that with a stock rom?
Because adb root will not work with ITL41F at least.
Code:
./adb root
adbd cannot run as root in production builds
Furthermore the chmod for Superuser.apk is totally bogus. No need to mess with it's permissions.
i think a better way is get su and SuperUser.apk from the developers (ChainsDD) site and install it with a temporary boot CWM to install it.
(these instructions are also from memory And i rooted my one from source, but that's a bit involved)
this would mean instead of step 7 do.
7. Download CWM into the same directory as fastboot
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.5.0.4-toro.img (Verizon)
or
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.5.0.2-maguro.img (GSM)
Make sure to get the right version for your device.
8. download http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip
onto the internal storage of the phone( "sdcard" )
9. With the phone turned OFF, hold VOLUME UP + VOLUME DOWN and power the phone on. This will put you in bootloader mode
10. again using windows/cmd go to the folder /android-sdk/platform-tools
From this folder try the command "fastboot devices" (do not include ") which should list the device connected to your PC.
11. Start CWM (without installing it)
fastboot boot recovery-clockwork-XXX-XXX.img
(use the right filename from step 7)
12. choose install update and select the zip from step 8.
You need to use volume up/down to navigate and power to select.

[RECOVERY][ TWRP Recovery 2.6.3.3 | ONLY For Android JB ] [Update 18/02/2014]

Hello !!!
Team Win Recovery Project !​
Permanent Recovery TWRP 2.6.3.3
​ - for -​
Huawei Ascend P6​
Team Win Recovery Project 2.6, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
This is a permanent & fully functionally TWRP Recovery for Huawei Ascend P6 !
​
New Release TWRP 2.6.3.3 : 18/02/2014
Release R03.1 : 05/01/2014 .
Release R03 : 07/12/2013 .
About :
English edition !
builded from the last update TWRP 2.6.3.0 source !
this recovery will rewrite your /recovery partition, warning : install at your own risk !
enter on twrp recovery by pressing volume + & volume - & power button at the same time , when Huawei logo is displayed please release the buttons ! ( or using "adb" commands : > adb reboot recovery )
Change log :
What's new in 2.6.3.0 !
TWRP 2.6.3.3 :
added offmode charging !
added battery percentage display on StatusBar !
allow battery charging ( if the USB cable or a charger is connected ) !
Downloads :
New Update : twrp_2_6_3_3_recovery.img
TWRP_R03.1.zip
TWRP_Recovery_R03.1.zip
TWRP_R03.zip
Installation :
Install the last update TWRP 2.6.3.3 only by this method : ( fastboot flash recovery twrp_2_6_3_3_recovery.img )
make sure your device was already Unlocked !
no need to root your device , TWRP has the ability to root your device !!!
put your device in fastboot mode ( > adb reboot bootloader )
extract recovery_twrp.img from archive TWRP_R03.1 !
fastboot flash recovery recovery_twrp.img ;
fastboot reboot ;
or download TWRP_Recovery_R03.1.zip and install on TWRP like in a usuale way !!!
enjoy with permanent recovery !!!
getting root access !
Revert to stock recovery ( B118 ) :
put your device in fastboot mode ( > adb reboot bootloader )
extract recovery.img from archive Stock_Recovery_B118.zip !
fastboot flash recovery recovery.img ;
fastboot reboot ;
now your device has stock recovery !!!
Credit :
TeamWin !
[NUT]
Source :
GitHub !
>>> Warning <<< ​
Being a total functional recovery, take care what custom rom are you going to flash with it !
A wrong rewrite only one of the partitions (boot, modemimage, recovery, xloader, oeminfo and . ...) can easily ruin your device permanently !
Use this utility at your own risk , I am not responsible for damage your device by using this utility incorrect !
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
regards,
Surdu Petru

TWRP Recovery for locked firmware HAP6 & HAM !!!
<< TWRP RECOVERY >>
​
*** Working on Huawei Ascend P6 & HAM locked Firmware ***
​
About :
English edition !
builded from the last update TWRP 2.6.3.0 source !
this recovery will NOT rewrite your /recovery partition !!!
enter on twrp recovery : power off your device , now briefly press the power button & wait to see the green led lights up - at this time you should quickly and repeatedly pressing volume down or volume up button ( about ~ 5 sec. ) - you will see very soon the led red lights up and your device will be in recovery way !!!!
the latest version is R02.1 & was fixed all issue ( including Internal Storage bug from R02 ! )
TWRP Recovery R02.1 : 05/01/2014 !
TWRP Recovery R02 : 30/11/2013 !
Downloads :
TWRP_R02.1.zip MD5 Sum: 11bb1a5818d9c616fbc3687169b7ba1d
TWRP_R02.zip - 3.55 MB MD5 Sum: 27dbc47a55a695b62f6c6c4f682777c5
TWRP_R02.zip MD5 Sum: 27dbc47a55a695b62f6c6c4f682777c5
Installation :
First you need to have the device rooted !!!
copy archive TWRP_R02.1 on your external or internal sdcard ( storage ) [ > adb push TWRP_R02.1.zip sdcard/ or storage/sdcard1/ ];
you must have already installed an older recovery ( TWRP or CWM ) !
boot your device in your custom recovery - that was already installed on your device ;
choose update from external/internal storage ;
install ;
reboot your device !
by installing this recovery , all previous recoveries will be wiped !!!
TWRP Recovery R01 : 20/11/2013 !
Downloads :
TWRP_R01.zip MD5 Sum : 5348a968f831a4095fda4fac20d6a0d2
TWRP_R01.zip - 3.55 MB MD5 Sum: 5348a968f831a4095fda4fac20d6a0d2
TWRP_SHELL.zip MD5 Sum : c8203f82486f697810444c9be9b8f4cd
Installation :
First you need to have the device rooted !!!
1° using CWM recovery :
copy archive TWRP_R01 on your external sdcard ( storage ) ;
boot your device in CWM recovery ;
choose update from external sdcard ;
install ;
reboot your device !
2° using "adb shell" commands :
unzip archive TWRP_SHELL.zip in TWRP_SHELL directory ;
connect your USB cable and check on Settings -> Developer options -> USB debugging ;
enter on TWRP_SHELL directory and open cmd command ;
> adb push recovery.sh /data/local/tmp
> adb push recovery.cpio.lzma /data/local/tmp
> adb push install-recovery.sh /data/local/tmp
> adb push busybox /data/local/tmp
> adb shell
$ su
# mount -o remount,rw /system
# cp -r /data/local/tmp/busybox /system/xbin/busybox
# chown 0.0 /system/xbin/busybox
# chmod 04755 /system/xbin/busybox
# /system/xbin/busybox --install -s /system/xbin
# cp -r /data/local/tmp/install-recovery.sh /system/etc/install-recovery.sh
# chown 0.0 /system/etc/install-recovery.sh
# chmod 0755 /system/etc/install-recovery.sh
# cp -r /data/local/tmp/recovery.sh /system/bin/recovery.sh
# chown 0.0 /system/bin/recovery.sh
# chmod 0755 /system/bin/recovery.sh
# cp -r /data/local/tmp/recovery.cpio.lzma /system/bin/recovery.cpio.lzma
# chown 0.0 /system/bin/recovery.cpio.lzma
# chmod 0644 /system/bin/recovery.cpio.lzma
# reboot
enjoy ...
3° remove old recovery :
use TWRP Recovery to install Remove_old_recovery.zip - 241.31 KB !
TWRP 2.6.3.0 Screenshots on Device Huawei Ascend P6 :
Screenshots:

Ah, can't wait...
And this Recovery work full wipe and backup/restore?
Sent from my HUAWEI P6-U06 using Tapatalk 4

you are just the TOP :good::good: simply :laugh:

I keep refreshing the thread every 10 minutes I'm so anxious, but take all the time you need surdu_petru!
Sent from my HUAWEI P6-U06 using Tapatalk

surdu_petru said:
I will keep Press Volume UP to enter on CyanogenMod , if I will be able to port !
Click to expand...
Click to collapse
Dual boot? Is the integrated sdcard much slower than the device rom disk itself or are they both on 1 chip but partitioned?

Pressing the thanks button isn't enough, so this is to thank you for your hard work! This will be the start of great things for our P6 :good:

Hi!
I'll be at home in about two hours and I'll update OP !

mikesa said:
Ah, can't wait...
And this Recovery work full wipe and backup/restore?
Sent from my HUAWEI P6-U06 using Tapatalk 4
Click to expand...
Click to collapse
Yes, wipe , factory reset and backup/restore is fully working !
frdan said:
you are just the TOP :good::good: simply :laugh:
Click to expand...
Click to collapse
Thanks ...
tauio111 said:
Dual boot? Is the integrated sdcard much slower than the device rom disk itself or are they both on 1 chip but partitioned?
Click to expand...
Click to collapse
The both recovery can be installed and boot on device ( no need external sdcard ) without partitioned internal sdcard !
miz_pimp said:
Pressing the thanks button isn't enough, so this is to thank you for your hard work! This will be the start of great things for our P6 :good:
Click to expand...
Click to collapse
Thanks ...

Can't get it to boot into twrp :/ I start pressing as soon as I see the green light but the phone just boots, no red light :/
Edit: GOT IT! Didn't realize I had to press it repeatedly, I was just holding it working great, thanks surdu_petru!
Sent from my HUAWEI P6-U06 using Tapatalk

Ottomaani0 said:
Can't get it to boot into twrp :/ I start pressing as soon as I see the green light but the phone just boots, no red light :/
Edit: GOT IT! Didn't realize I had to press it repeatedly, I was just holding it working great, thanks surdu_petru!
Sent from my HUAWEI P6-U06 using Tapatalk
Click to expand...
Click to collapse
Thanks, I'll check right now , it's seem that busybox was not installed on your device !
Also, please can you send me a zip including this two files :
/cache/HuaweiP6/HuaweiP6.log and HuaweiP6.log.old ?

surdu_petru said:
Thanks, I'll check right now , it's seem that busybox was not installed on your device !
Also, please can you send me a zip including this two files :
/cache/HuaweiP6/HuaweiP6.log and HuaweiP6.log.old ?
Click to expand...
Click to collapse
Edited my post. Got it working
Sent from my HUAWEI P6-U06 using Tapatalk

Nice thanks a lot... Really appreciate it..
Sent from my HUAWEI P6-U06 using xda app-developers app

The first link for downloading doesn't work.

Dmitry Budnikov said:
The first link for downloading doesn't work.
Click to expand...
Click to collapse
Working great here
Sent from my HUAWEI P6-U06 using Tapatalk

Ottomaani0 said:
Working great here
Sent from my HUAWEI P6-U06 using Tapatalk
Click to expand...
Click to collapse
Don't know why but I can't download with IE11. I could download after installing Google Chrome...

Dmitry Budnikov said:
The first link for downloading doesn't work.
Click to expand...
Click to collapse
Thanks, I'll re upload on mirror soon !

Why I don't see a green light while rebooting? I have root and busybox... Where is the problem?

Dmitry Budnikov said:
Why I don't see a green light while rebooting? I have root and busybox...
Click to expand...
Click to collapse
In what way you tried to install TWRP recovery, 1° or 2° ?

surdu_petru said:
In what way you tried to install TWRP recovery, 1° or 2° ?
Click to expand...
Click to collapse
First.

[ROOT]How to Root KVT49L.D85110r and Install TWRP. My experience

I am not sure if this is the correct forum for this. Moderators, Please feel free to remove it or relocate it
First of all thanks to all amazing people on this forum ( thecubed,777jon,Dees_Troy, chainfire, supernoman, crashfocus, etc)
This is not my work . It is a compilation of what it worked for me from the work made by others. It is directly toward newbie users.
Instructions
1- Make sure you install LG G3 drivers in your computer( you can get them attached on this thread). Connect phone to the PC using USB cable. Make sure the phone is recognized when you plug it in with the usb cable
Also phone shall be connected as Media device (MTP), if it is in Charge Phone change it to MTP.
Scroll down this post. You will find the correct usb drivers attached. Install them in your pc.
2- Enable Developer options in your phone on Setting > General> About phone > Software information > and click seven times Build number until it enables it
3- Enable USB debugging on your LG G3 from your phones Settings > Developer options > tick ‘USB debugging’ check box. A window should pop up in your phone display to allow USB debugging. Select Allways Allow from This Computer and hit OK.
It will also be convenient to Enable installation of apps from Unknown Sources: Open phone’s Settings » select Security » Tick the “Unknown sources” check box (under Device administration section)
4- Download and unzip
- Pupledrake-Lite at http://downloads.codefi.re/thecubed/lg_g3/purpledrake/PurpleDrake-Lite_R03.tar.gz Thanks to Codefi.re
- Download and unzip the attached ADB LOCAL READY with TWRP recovery.img
Thanks to @Dees_Troy & TeamWin - for TWRP Touch recovery
ATTACHMENT IS HERE- JUST CLICK HERE
5- Download -Latest SuperSu at http://download.chainfire.eu/641/SuperSU/UPDATE-SuperSU-v2.40.zip Thanks to Chainfire
6- Transfer UPDATE-SuperSU-v2.40.zip to the internal sdcard
7- Open Purpledrake-Lite and Run purpledrake_windows.bat. It should detect your devices if it is not, you need to check if the drivers were installed properly and unplug-plug back your phone.
Hit Enter as instructed on the computer screen until it gains temporary root.
IMPORTANT : READ AND DO NOT CONTINUE TO PERMANENT ROOT INSTRUCTIONS DISPLAYED. FOLLOW INSTRUCTIONS TO CONTINUE WITH ADB INSTEAD.
Hit Ctrl+C to exit to use adb.
This process takes a few seconds and The phone start on download mode and it will stay on it.
8- Open ADB LOCAL READY folder you downloaded and hit Start Here.bat
Type "adb devices" to ensure that your phone is connected and it accept adb commands . On list of devices attached it should show LGD851........
Unplug it and plug it back if it is not .
NOTE: SOME PEEPS HAVE REPORTED PROBLEM WITH ADB NOT WORKING PROPERLY ON USB 3.0 PORTS. PLEASE USE USB 2.0 PORTS
9- Type "adb push recovery.img /temp"
You will see that it pushes the data. it should take a few seconds
Note: you may need to push it a few times if you do not find the recovery file on the /temp folder when you do step 12.
Some members stated that they need to push it ..5 times.
rubbamade tip
" This does work. If after you do the "adb push....", Hit the up key on your keyboard. What you just typed " adb push...." will appear again. Hit enter. It will "push" again. Hit up again. Hit enter. Do this at least 5 times. Now proceed with next step "adb shell"..... Should work now"
For some reason others user needed to push it more than 5 times, i assume that it is due to the file size of the image and your operating system and pc settings(i used win7). It is recommended to verify if it was pushed on step 12.
10- Type "adb shell" and it should go to shell command $
11- Then type "/temp/fakesu". This will put you in a superuser shell on your device. It should show su command line # .
12- Type "ls /temp" to make sure that recovery.img and fakesu are in /temp folder . If it is not, then you did not complete correctly the above instructions..repeat it
13- Type "dd if=/temp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery". it will take a few seconds to complete and install TWRP recovery.
14- Type type "reboot recovery" It should boot onto TWRP Touch recovery. it could take a few but it should
15- Once in TWRP, select install,go to the SD card directory, select UPDATE-SuperSU-v2.40.zip and install it. Reboot the phone once complete. Do not panic, it should take a while to cook and update applications, but it will, be patient.
16- Your device is rooted and with TWRP custom recovery. IF you do not see SuperSu in your application drawer, do not panic, just install it from the Play Store.
17- Now you are ready to install custom Roms, any application that requires root, or enjoy root features.
Quick References
How to Boot into TWRP(Recovery Mode)
1.Turn off your phone
2.Now, press and hold Power and Volume down buttons at the same time.
3.When the LG logo appears, release the keys.
4.Immediately press Power and Volume Down buttons again until the Hard Reset menu will be displayed.
5.Press volume down to Select "YES" on reset data. Do not panic, it will not . Select "yes" again . It will boot into TWRP recovery mode.
If you do not like hardware method you can use Quickboot or TWRP Manager applications from the Play store
How to Boot LG G3 Download Mode
-Disconnect your phone from PC.
-Power off your G3 and wait 4-5 seconds after lights go off.
-Hold the Volume Up button on phone, and while holding it, connect the phone to PC using a USB cable
If you get the "Windows cannot find '.\assets\windows\bin\mintty.exe'." error..on purpledrake temproot step 7.
Try just double-clicking on the .bat instead of running as admin.
Also make sure the script is extracted properly first before running
Disclaimer: It worked for me, but I am not responsible for any damages to your phone.

Your experience is very interesting vcurbel!
I was under the impression there was no way to root untouched stock 10R.
It would appear you have found a way! :good: Thanks for your contribution.
I am curious if anyone else has replicated this?

thank you so much had a little trouble but successfully rooted my device

Where was this guide yesterday?
Last week I just thought rooting build R was impossible as of yet, got fed up, and 5 minutes ago ran the LG Update tool to revert my phone back to stock/ Build C and root that way.

vcurbel said:
I am not sure if this is the correct forum for this. Moderators, Please feel free to remove it or relocate it
13- Type "dd if=/temp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery". it will take a few seconds to complete and install TWRP recovery.
Click to expand...
Click to collapse
dd if=/temp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
This command doesn't work for me. It shows, "cannot open for read: no such file or directory".
Can you help?
Edit: Nevermind, had to repush recovery. Didn't go through properly the first time. Thank you
Everything worked great. Thank you for the guide! Rooted on 10r!

NO GO
- Type "ls /temp" to make sure that recovery.img and fakesu are in /temp folder . If it is not, then you did not complete correctly the above instructions..repeat it
AT THIS POINT I AM GETTING "NOT FOUND". DID THE STEPS ABOVE SEVERAL TIMES.
I saw 8xxxkb data pushed after 'push'
==========================================================================================
C:\Users\nick\Downloads\ADB LOCAL READY>c:\windows\system32\cmd.exe
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\nick\Downloads\ADB LOCAL READY>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
LGD851xxxxxxxx recovery
C:\Users\nick\Downloads\ADB LOCAL READY>adb push recovery.img /temp
9716 KB/s (11245568 bytes in 1.130s)
C:\Users\nick\Downloads\ADB LOCAL READY>adb shell
[email protected]:/ $ /temp/fakesu
/temp/fakesu
# Is /temp
Is /temp
/temp/fakesu: Is: not found
#
=========================================================================================

sharkoparko said:
- Type "ls /temp" to make sure that recovery.img and fakesu are in /temp folder . If it is not, then you did not complete correctly the above instructions..repeat it
/temp/fakesu: Is: not found
#
=========================================================================================
Click to expand...
Click to collapse
try to redo step number 7. But, you are getting into su command line which is #
after you do the ls/temp on su #, you should get the list of files in your temp folder.....check if recovery and fakesu are there
then continue to step 13

vcurbel said:
try to redo step number 7. But, you are getting into su command line which is #
after you do the ls/temp on su #, you should get the list of files in your temp folder.....check if recovery and fakesu are there
then continue to step 13
Click to expand...
Click to collapse
Thanks. I did it several times, I did number 7 also. Phone is found, it says creating permaroot....Once I click CTRL C screen disappears then I go to ADB file and follow procedures. IT STILL DOES NOT WORK
===================================================================================
Welcome to PurpleDrake!
Please ensure your phone is connected, powered on, and USB debugging is properly enabled.
Your phone should be showing your homescreen with no other apps open. This is to ensure a clean state.
When you're ready, press [enter]...
Press [enter] to continue...
Waiting for device... Found device!
Your phone is a [ LG-D851 ] on [ TMO ] running SW version [ V10r ] ...
Alright. We're ready to go. We're going to temproot your phone first. Press enter when you're ready!
Press [enter] to continue...
Rebooting phone...
Waiting for device... .... Found device!
Found device, checking if vulnerable...
Yep, performing temproot...
Waiting for system to settle...
Temproot worked, all done here. Moving on...
Alright, now that you're temprooted, you can press CTRL-C here and get
a temproot prompt through 'adb shell /temp/fakesu' if you're so inclined...
However, if you'd like to permaroot, let's continue.
Press [enter] to continue...
===============================================================================================
DO I NEED TO RE-ROOT?

sharkoparko said:
Thanks. I did it several times, I did number 7 also. Phone is found, it says creating permaroot....
DO I NEED TO RE-ROOT?
Click to expand...
Click to collapse
Here is the problem. You pressed to continue (enter) to create permanent root after temporary root was created
You need to press CTRL C instead , then it will exit......then continue to next step with ADB LOCAL READY.
Ill clarify this better on step 7.
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app

vcurbel said:
Here is the problem. You pressed to continue (enter) to create permanent root after temporary root was created
You need to press CTRL C instead , then it will exit......then continue to next step with ADB LOCAL READY.
Ill clarify this better on step 7.
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app
Click to expand...
Click to collapse
Once I click CTRL C screen disappears then I go to ADB file and follow procedures. IT STILL DOES NOT WORK
That's what I do. I clicked enter first time rooting following purple instructions. Then I realized it does not work with January update. I run purple drake again (after I found this "fix") and, as I said, I DO NOT PROCEED WITH ENTER. I use CTRL C. The window closes and I open ADB, then click start hereand follow the rest of the procedures. So YES I did click enter once initially (because purple drake post is not updated that it does not work with JAN 15 update).

sharkoparko said:
Once I click CTRL C screen disappears then I go to ADB file and follow procedures. IT STILL DOES NOT WORK
That's what I do. I clicked enter first time rooting following purple instructions. Then I realized it does not work with January update. I run purple drake again (after I found this "fix") and, as I said, I DO NOT PROCEED WITH ENTER. I use CTRL C. The window closes and I open ADB, then click start hereand follow the rest of the procedures. So YES I did click enter once initially (because purple drake post is not updated that it does not work with JAN 15 update).
Click to expand...
Click to collapse
Ok....lets do it one at a time
Once you open and run ADB LOCAL READY. When you type adb devices, is it show your device?
Let me know on which step you got stuck.
Ill try to help you
Sent from my LG-D851 using XDA Free mobile app

Just got home with a Craigslist buy.
rooted in 15min thanks vcurbel !
now to find CM12 for this baby

hi sorry for the newbiness but for some reason i donload everything i need, basically preperation is done to the T, but as soon as i click on purpledrake_windows.bat it goes into dos window and complety exits out in less then a second, so fast that i can barely read whats on that lil black screen, im pretty sure i can make out "command not found" at the end of it..any help would be greatly appreciated

tomez206 said:
hi sorry for the newbiness but for some reason i donload everything i need, basically preperation is done to the T, but as soon as i click on purpledrake_windows.bat it goes into dos window and complety exits out in less then a second, so fast that i can barely read whats on that lil black screen, im pretty sure i can make out "command not found" at the end of it..any help would be greatly appreciated
Click to expand...
Click to collapse
Did you run it as Administrator?
Did you install LG drivers and the device is being recognized as Media device?
Sent from my LG-D851 using XDA Free mobile app

all drivers are installed, the device is recognized, and nothing, when i do run it as administrater i get a whole different error msg
vcurbel said:
Did you run it as Administrator?
Did you install LG drivers and the device is being recognized as Media device?
Sent from my LG-D851 using XDA Free mobile app
Click to expand...
Click to collapse
---------- Post added at 08:43 AM ---------- Previous post was at 08:38 AM ----------
windows cannot find '.\assets\windows\bin\mintty.exe'. Make sure you type the name correctly and try again...thats the error i get when trying to run as administrator

tomez206 said:
all drivers are installed, the device is recognized, and nothing, when i do run it as administrater i get a whole different error msg
---------- Post added at 08:43 AM ---------- Previous post was at 08:38 AM ----------
windows cannot find '.\assets\windows\bin\mintty.exe'. Make sure you type the name correctly and try again...thats the error i get when trying to run as administrator
Click to expand...
Click to collapse
It seems your windows os is missing the default mintty.exe terminal...
Google it and you will find a solution to manually install it.
Or use other pc
Sent from my LG-D851 using XDA Free mobile app

tomez206 said:
hi sorry for the newbiness but for some reason i donload everything i need, basically preperation is done to the T, but as soon as i click on purpledrake_windows.bat it goes into dos window and complety exits out in less then a second, so fast that i can barely read whats on that lil black screen, im pretty sure i can make out "command not found" at the end of it..any help would be greatly appreciated
Click to expand...
Click to collapse
If I recall if the PD batch file/script is closing on you or giving you trouble, then you can run the script manually.
See link below to thecubed PD lite thread and read the 5th grey portion down of the OP, it is titled:
"But, what if I don't want to run your script to root?"
If you must use command line because the PD batch file/script is closing immediately just be sure to STOP after gaining temporary root!
From OP step 7:
IMPORTANT : READ AND DO NOT CONTINUE TO PERMANENT ROOT INSTRUCTIONS DISPLAYED. FOLLOW INSTRUCTIONS TO CONTINUE WITH ADB INSTEAD. [/FONT]

lagvoid said:
dd if=/temp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
This command doesn't work for me. It shows, "cannot open for read: no such file or directory".
Can you help?
Edit: Nevermind, had to repush recovery. Didn't go through properly the first time. Thank you
Everything worked great. Thank you for the guide! Rooted on 10r!
Click to expand...
Click to collapse
Hello,
I am also having the same issue. I tried the above steps a couple times and am not sure if I am doing something wrong (more than likely I am). What did you mean by repush recovery?

Try step 9 again
9- Type "adb push recovery.img /temp"
You will see that it pushes the data. it should take a few seconds

vcurbel said:
Ok....lets do it one at a time
Once you open and run ADB LOCAL READY. When you type adb devices, is it show your device?
Let me know on which step you got stuck.
Ill try to help you
Sent from my LG-D851 using XDA Free mobile app
Click to expand...
Click to collapse
-------------------------------------------------------------------------------------------------------------------------------------
C:\Users\nick\Downloads\ADB LOCAL READY>c:\windows\system32\cmd.exe
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\nick\Downloads\ADB LOCAL READY>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
LGD851xxxxxxxx recovery
C:\Users\nick\Downloads\ADB LOCAL READY>adb push recovery.img /temp
9682 KB/s (11245568 bytes in 1.134s)
C:\Users\nick\Downloads\ADB LOCAL READY>adb shell
[email protected]:/ $ /temp/fakesu
/temp/fakesu
# Is /temp
Is /temp
/temp/fakesu: Is: not found
# dd if=/temp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/temp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
/temp/recovery.img: cannot open for read: No such file or directory
#
--------------------------------------------------------------------------------
Yes, The phone is recognized and the file as you see was pushed (see script above). I think there is some issue with this method, as other people are reporting problems following the procedure in post #1??!! I guess it work for some and it does not for others.