[Recovery] [v500] CWM 6.0.5.1

[leardinet]

Your log says that you first typed "adb shell" and then you tried to use "adb push" inside the shell. The push command does not work when you are inside the "Adb shell".

Type "exit" inside the shell to close it and then "adb push" commands will work.

i first typed

adb push recovery.img /data/local/tmp

and......

C:\Program Files (x86)\Minimal ADB and Fastboot>adb push recovery.img /data/loca
l/tmp
cannot stat 'recovery.img': No such file or directory

I can write the steps , step by step

 

[Deltadroid]

You have to download the two files I mentioned in the previous step, extract the zip files, and copy the two files I mention into the directory you are going to execute the adb push commands.

 

[leardinet]

is exactly what I do :
- Extract files
- I copy them in the folder
- I open cmd
- I type adb push recovery.img / data / local / tmp
- The eventually find it : cannot stat 'recovery.img': No such file or directory

why?????

 

[Deltadroid]

adb push recovery.img /data/local/tmp

There are no spaces between "/data/local/tmp"

 

[Zeljko1234]

Do you have recovery.img in the same folder where's adb? If not copy it there or type path to it.

 

[leardinet]

adb push recovery.img /data/local/tmp

There are no spaces between "/data/local/tmp"

yes, no spaces

I misspelled

 

[Deltadroid]

Type "ls" first to make sure the files are all there before doing "adb push" commands.

You should see recovery.img and loki_tool when you type "ls".

 

[Zeljko1234]

Type "ls" first to make sure the files are all there before doing "adb push" commands.

You should see recovery.img and loki_tool when you type "ls".

He's using windows, don't confuse him even more with "ls". Type dir instead

 

[Deltadroid]

Sorry,I forgot this was Windows. I meant "dir". The other command is for Linux.

 

[leardinet]

C:\Program Files (x86)\Minimal ADB and Fastboot>adb push recovery.img /data/loca
l/tmp
4477 KB/s (10514432 bytes in 2.293s)

C:\Program Files (x86)\Minimal ADB and Fastboot>adb push loki_tool /data/local/t
mp
5935 KB/s (379276 bytes in 0.062s)

C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
[email protected]:/ $ su
su
[email protected]:/ # chmod 755 /data/local/tmp/loki_tool
chmod 755 /data/local/tmp/loki_tool
[email protected]:/ # dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local
/tmp/aboot.img
cc.1/by-name/aboot of=/data/local/tmp/aboot.img                               <
1024+0 records in
1024+0 records out
524288 bytes transferred in 0.066 secs (7943757 bytes/sec)
[email protected]:/ # /data/local/tmp/loki_tool patch recovery /data/local/tmp/aboot.im
g /data/local/tmp/recovery.img /data/local/tmp/recovery.lok
a/local/tmp/recovery.img /data/local/tmp/recovery.lok                         <
Loki tool v2.1
[+] Detected target International LG G Pad 8.3 build V50010a
[+] Original kernel address: 80208000
[+] Original ramdisk address: 82200000
[+] Output file written to /data/local/tmp/recovery.lok
[email protected]:/ # /data/local/tmp/loki_tool flash recovery /data/local/tmp/recovery
.lok
recovery /data/local/tmp/recovery.lok                                         <
Loki tool v2.1
[+] Loki validation passed, flashing image.
[+] Loki flashing complete!
[email protected]:/ # exit
exit
[email protected]:/ $ exit
exit

C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot recovey

C:\Program Files (x86)\Minimal ADB and Fastboot>

practically comado adb push only serves to copy the files directory , and the files must be in the folder where it would not otherwise copy resides adb.exe
I succeeded , thanks
I finally figured out where wrong .

 

[Zeljko1234]

We told you that Actually you can type something like adb push c:\recovery_folder\recovery.img /data/local/tmp but it's just easier if you put everything in the same folder.

I'm glad that you succeeded and learned something

 

[leardinet]

Now my question is this : if I replace the file recovery.img ( .cmw ) file with recovery.img ( TWRP ) and do the same process works ???

 

[Deltadroid]

Now my question is this : if I replace the file recovery.img ( .cmw ) file with recovery.img ( TWRP ) and do the same process works ???

Yes, that is fine. Just make sure that the recovery.img is built for v500.

 

[leardinet]

Yes, that is fine. Just make sure that the recovery.img is built for v500.

ok works with 2.6.3.0 but you see everything dark , why ???

solved with the TWRP_2.7.1.0

 

[android404]

must be started over again from the beginning after flashing a loki exploitable aboot.img to the device (downgrading firmware should help).

I flashed twrp half a year ago and cannot boot into recovery since. Now I tried your method which fails because of an unsupported aboot.img and I don't know where to find the proper one and how to flash it. Could you point me into the right direction?

 

[Deltadroid]

The new versions of LG Tool won't let you downgrade because the program checks for the latest firmware version to install. There is another version of LG Tool that does allow for downgrading firmware here:
http://forum.xda-developers.com/showthread.php?t=2797190

Now you just need to get the kdz file to install here:

https://www.androidfilehost.com/?w=files&flid=13296

 

[android404]

The new versions of LG Tool won't let you downgrade because the program checks for the latest firmware version to install. There is another version of LG Tool that does allow for downgrading firmware here:
http://forum.xda-developers.com/showthread.php?t=2797190

Now you just need to get the kdz file to install here:

https://www.androidfilehost.com/?w=files&flid=13296

Great. Everything worked and I'm ready to flash away. Thanks again.

 

[HTC Tytn user 188]

I got this LG G Pad 8.3 4.4.2 V500 (rooted and busybox installed) this week. My device informations are KOT49I.V50020d because this is d versio there seems to be some problems with these custom recoverys. Im not yet sure which rom i will go. Pacman and Slim are looking good so possibly some of them.

Question is which i should install CWM or TWRP? And please give complete guide how to do it because both treads seems to be full of diffrent answers about that.

 

[Deltadroid]

In order to install a custom recovery, you still need to downgrade your firmware (see links above) and root over again. The OP here should give you all the details for a manual installation of the recovery for first time installers. This process can be done with CWM or TWRP. I prefer CWM for stock CM because it is automatically upgraded with the CM Installer .

 

[HTC Tytn user 188]

I red this tread: http://forum.xda-developers.com/lg-...e-root-twrp-customrom-kot49i-v50020d-t2894277

There seems to be two ways to do that. Follow the first post of thread or download firmware from here: http://lg-phone-firmware.com/index.php?id_mod=39 (Which firmware i need? Im from Finland and there is not firmware from Finland.) After that i need to use this program to downgrade my firmware: http://forum.xda-developers.com/showthread.php?t=2797190

When i have downloaded and installed firmware my version should be V50020a and then i can install http://forum.xda-developers.com/showthread.php?t=2551499 or this CWM directly following guide if im right? I might go with TWRP. When this is done do i need to upgrade my pad to newest firmware so it comes back to KOT49I.V50020D?