yashsingh1/xdaforums huggingface dataset:
[G Pad 8.3 Original Android Development] Deltadroid:
Updated CWM to 20141120 sources.

sr: Fix vsync logic

* Use CLOCK_MONOTONIC to insulate from system clock changes.

* Normalize all timespec calculations to avoid overflow/underflow.

* Don't signal vsync if poll() fails.

Change-Id: If284ebf581309953c51b2f8d33d7d5800c636be5

sr: Fix screen flashing during wipe operations

* Clear buffer in draw_progress_locked() and always call this in

update_progress_locked(). This is necessary to ensure that all

backing frames in the graphics implementation get updated because

we aren't guaranteed to have any particular number of backing

frames.

* Remove dialogs on wipe operations since we are using the progress

animation now.

* Set progress indicator after showing "Formatting" text to avoid

momentary flicker.

Change-Id: I240d3b8e5c741c9f3ea4e5e17c1b9593e053888a

sr: Only use 4 items on wipe confirmation screens

* Large fonts in Touch UI prevent more than about 7 menu lines.

Change-Id: If523a85d67460c0ac4e012727d946eadb9c68436
[G Pad 8.3 Original Android Development] Deltadroid:
Added guide to OP for first time custom recovery installation.

Edit: Updated guide to use loki_tool from github.
[G Pad 8.3 Original Android Development] Wingchundub:
Hi,

I have tried this method and get an "unable to find" error as regard loki, seen in this picture i took.

I have placed both recovery.img and loki_tool as from your download links in data/local/tmp folder on lg

Where am i going wrong?

Thank you
[G Pad 8.3 Original Android Development] Deltadroid:
When you type "adb shell" to open a connection, wait for the shell to open before typing "su". You will then notice that the terminal says "root" as the user. Make sure you have "dd" installed (this comes with installing Busybox). You can tell if dd is installed by typing "which dd" in the shell. If it returns with a path to dd, then it's there. I also noticed that you tried to chmod loki_tool before you have typed su to gain root. You only need to type su one time to get root permissions in the shell. You can tell it is using root because it shows you as the root user at the command prompt.
[G Pad 8.3 Original Android Development] Wingchundub:
I am sorry for my dumbness, but i am new to this and not a clue what you are talking about lol.

I never typed su as i followed this procedure on youtube and copy and pasted your text.

I am trying to understand this adb method, but a noob tut is not available, thus trying anyway to get it to work obviously without success lol

https://www.youtube.com/watch?v=MVXX-YdhRU0

Best wishes
[G Pad 8.3 Original Android Development] Tsjoklat:
ADB needs root access in developer options. Attached screenshot.
[G Pad 8.3 Original Android Development] Deltadroid:
You are getting an unable to find error because you typed the name incorrectly (it is loki_tool not loki_tooldd). Be very careful that everything is exactly the same as the guide.

Edit: Also, when you type a command in ADB shell, wait for the command to finish before you type the next command. You can enter the next command in ADB when the prompt comes back.

Edit 2: After typing "adb shell", you only need to type "su" one time as long as you don't close the window.
[G Pad 8.3 Original Android Development] Zeljko1234:
Does it support f2fs?
[G Pad 8.3 Original Android Development] Deltadroid:
I think f2fs support is not default for stock CM kernel. There aren't any customizations on this. This is from Jenkins.
[G Pad 8.3 Original Android Development] Zeljko1234:
Currently I'm using LP AOSP. Afaik, only LP available. On my Razr HD f2fs and CM12 works just great. Definitely noticeable faster with f2fs.
[G Pad 8.3 Original Android Development] Wingchundub:
I have just noticed the loki-tooldd, i am positive i did not type that i,.e the dd on the end.

But i will again tomorrow, test this and come back with any results.

I am also never once typing SU, i assume the program is doing it automatically.

I will test and post pics also.

Thank you
[G Pad 8.3 Original Android Development] Deltadroid:
I dont think ADB is working correctly for you because you are not getting the correct responses when you enter commands. It seems like your system is "hanging" when you enter commands in the adb shell.

Maybe you should try these commands in a Terminal Emulator shell instead of using an ADB shell. You will just need to install an extra root reboot application from Play Store so that you can easily reboot into the new recovery when you are finished.
[G Pad 8.3 Original Android Development] Wingchundub:
Thank you for you advice.

With terminal, I tried and copied the text provided, again gave same me errors and also the su and dd were there without me typing them.

It is coming to the point where i am giving up now as taking too much of my time.

Both are rooted and at least i can remove bloatware with root explorer etc and put my own stuff in, but would be nice to get this done and use custom roms, but simply not happening. [MENTION=2478576]Tsjoklat[/MENTION], i do not see that option in developer options fella, checked 4 times to be sure.

Thank you loads fella, your a star and very helpful
[G Pad 8.3 Original Android Development] Jansxel:
Will You Do CWM Touch?
[G Pad 8.3 Original Android Development] Deltadroid:
This version of CWM uses "swipe" gestures, but it isn't full touch. These versions of CWM are the official nightly builds. I was able to download the artifacts before they were removed for the next build in queue. Although, I plan on setting up a private build system pretty soon.
[G Pad 8.3 Original Android Development] leardinet:
where am I wrong ???

C:\Fastboot>adb devices
List of devices attached
07e7df499159c818 device

C:\Fastboot>adb shell
shell@awifi:/ $ su
su
root@awifi:/ # adb push recovery.img /data/local/tmp
adb push recovery.img /data/local/tmp
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|root@awifi:/ #
[G Pad 8.3 Original Android Development] Deltadroid:
It's out of order. First use adb to push the files, then use adb to open the shell.
[G Pad 8.3 Original Android Development] leardinet:
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

C:\Program Files (x86)\Minimal ADB and Fastboot>
C:\Program Files (x86)\Minimal ADB and Fastboot>adb push loki_tool /data/local/t
mp
cannot stat 'loki_tool': No such file or directory

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

su

chmod 755 /data/local/tmp/loki_tool
su

shell@awifi:/ $
shell@awifi:/ $ su

the files recovery.img and loki_tool copied in the data/local/tmp/ with ES File explorer

busybox installed
[G Pad 8.3 Original Android Development] Deltadroid:
Your log says that you first typed "adb shell" and then you tried to use "adb push" inside the shell. Commands that begin with "adb" do not work when you are inside the "Adb shell".

Type "exit" inside the shell to close it and then "adb push" commands will work.
[G Pad 8.3 Original Android Development] leardinet:
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
[G Pad 8.3 Original Android Development] 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.
[G Pad 8.3 Original Android Development] 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?????:confused::confused::confused:
[G Pad 8.3 Original Android Development] Deltadroid:
adb push recovery.img /data/local/tmp

There are no spaces between "/data/local/tmp"
[G Pad 8.3 Original Android Development] Zeljko1234:
Do you have recovery.img in the same folder where's adb? If not copy it there or type path to it.
[G Pad 8.3 Original Android Development] leardinet:
yes, no spaces

I misspelled
[G Pad 8.3 Original Android Development] 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".
[G Pad 8.3 Original Android Development] Zeljko1234:
He's using windows, don't confuse him even more with "ls". Type dir instead ;)
[G Pad 8.3 Original Android Development] Deltadroid:
Sorry,I forgot this was Windows. I meant "dir". The other command is for Linux.
[G Pad 8.3 Original Android Development] 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
shell@awifi:/ $ su
su
root@awifi:/ # chmod 755 /data/local/tmp/loki_tool
chmod 755 /data/local/tmp/loki_tool
root@awifi:/ # 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)
root@awifi:/ # /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
root@awifi:/ # /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!
root@awifi:/ # exit
exit
shell@awifi:/ $ 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 .
[G Pad 8.3 Original Android Development] 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 :)
[G Pad 8.3 Original Android Development] 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 ???
[G Pad 8.3 Original Android Development] Deltadroid:
Yes, that is fine. Just make sure that the recovery.img is built for v500.
[G Pad 8.3 Original Android Development] leardinet:
ok works with 2.6.3.0 but you see everything dark , why ???

solved with the TWRP_2.7.1.0
[G Pad 8.3 Original Android Development] android404:
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?
[G Pad 8.3 Original Android Development] 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://xdaforums.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
[G Pad 8.3 Original Android Development] android404:
Great. Everything worked and I'm ready to flash away. Thanks again.
[G Pad 8.3 Original Android Development] 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.
[G Pad 8.3 Original Android Development] 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 .
[G Pad 8.3 Original Android Development] HTC Tytn user 188:
I red this tread: http://xdaforums.com/lg-g-pad-83/general/guide-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://xdaforums.com/showthread.php?t=2797190

When i have downloaded and installed firmware my version should be V50020a and then i can install http://xdaforums.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?
[G Pad 8.3 Original Android Development] Deltadroid:
Check post #36 in this thread.
[G Pad 8.3 Original Android Development] HTC Tytn user 188:
Actually i red it but how do i know is that linked firmware right to my device? Do i have understanded right that after i have done that downgrade i follow the TWRP guide and install it and update my firmware back to newest version D back?
[G Pad 8.3 Original Android Development] Deltadroid:
You downgrade first, then install a custom recovery like CWM, then install a custom Rom. That kdz file should work fine to downgrade your device because it's for all v500 devices. They all have the same hardware.

Most cm based ROMS work best with the 4.2.2 base that you get by downgrading with the kdz file I just gave you a link to.
[G Pad 8.3 Original Android Development] HTC Tytn user 188:
Ok, im downloading everything needed now. I will edit this post about how everything goes.

EDIT: I did it! Now my Device have V50010A firmware.

---------- Post added at 01:25 PM ---------- Previous post was at 12:26 PM ----------

I did it. Now my device have CWM-Based Recovery v6.0.5.1 installed. Now its asking

"ROM may flash stock recovery on boot. Fix?

THIS CAN NOT BE UNDONE.

- No

- Yes disable recovery flash

Should i choose Yes disable recovery flash? EDIT: I tried to go back and it done something. Propably accept that disable recovery flash.
[G Pad 8.3 Original Android Development] Deltadroid:
You probably don't want to overwrite the recovery you just installed. It depends on what you are trying to flash. Don't install anything that will overwrite your new aboot partition.

If you install CM, then it wouldn't ask that.
[G Pad 8.3 Original Android Development] HTC Tytn user 188:
I didint install anything. I booted to recovery as installation said. Now im trying to find some good rom to install. There seems to be no CM rom stable.

Do you have any suggestions for fast and stable rom? Allmost every rom seems to be nightly builds stage. Mahdi seems to be allmost only complete and im going to test it first.
[G Pad 8.3 Original Android Development] Deltadroid:
The official nightly cm 11 is very stable to me.
[G Pad 8.3 Original Android Development] HTC Tytn user 188:
Where can you download it? I Cant find any information about anywhere?
[G Pad 8.3 Original Android Development] Deltadroid:
https://download.cyanogenmod.org/?device=v500
[G Pad 8.3 Original Android Development] Deltadroid:
Updated CWM link in OP

Updated CWM to 2014-12-13 sources.

Revert "adbd: switch to su domain when running as root"

This reverts commit c52c5b8e3d690201b2ae009a2d396d1899033e3d.

* This breaks the adb recovery banner, and root_seclabel is not

a valid option on cm11.

Change-Id: I0dede5d38b53b00936ad901e61d65f6119e62ff5

cwm: Allow device-specific recovery modules

Provide a means to include device-specific recovery modules that need to

be built (i.e. not pre-built). A list of recovery modules can be

specified by a device with:

TARGET_RECOVERY_DEVICE_MODULES := rec_mod_one rec_mod_two

Change-Id: Id28a41185b332a074cd15bd5c63e26bf284663d5
[G Pad 8.3 Original Android Development] Schrotty35:
I use 20b and the manuell install not work here on my V500. After i have reboot i see the stock recovery and not the new recovery.

Microsoft Windows [Version 6.3.9600]

(c) 2013 Microsoft Corporation. Alle Rechte vorbehalten.

F:\Software_Tools\Multimedia\Handy-Taplet\LG Pad 8.3\Recovery-Kernel\ADB + Fastb

oot>adb push recovery.img /data/local/tmp

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

3782 KB/s (11819008 bytes in 3.051s)

F:\Software_Tools\Multimedia\Handy-Taplet\LG Pad 8.3\Recovery-Kernel\ADB + Fastb

oot>adb push loki_tool /data/local/tmp

3312 KB/s (379276 bytes in 0.111s)

F:\Software_Tools\Multimedia\Handy-Taplet\LG Pad 8.3\Recovery-Kernel\ADB + Fastb

oot>adb shell

shell@awifi:/ $ su

su

root@awifi:/ # chmod 755 /data/local/tmp/loki_tool

chmod 755 /data/local/tmp/loki_tool

root@awifi:/ # dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local

/tmp/aboot.img

/data/local/tmp/loki_tool patch recovery /data/local/tmp/aboot.img /data/local/t

mp/recovery.img /data/local/tmp/recovery.lokdd if=/dev/block/platform/msm_sdcc.1

cc.1/by-name/aboot of=/data/local/tmp/aboot.img <

1024+0 records in

1024+0 records out

524288 bytes transferred in 0.028 secs (18724571 bytes/sec)

root@awifi:/ #

root@awifi:/ # /data/local/tmp/loki_tool flash recovery /data/local/tmp/recovery

.lok

flash recovery /data/local/tmp/recovery.lok <

Loki tool v2.1

Usage

> Patch partition file image:

/data/local/tmp/loki_tool [patch] [boot|recovery] [aboot.img] [in.img] [out.lok]

> Flash loki image to boot|recovery:

/data/local/tmp/loki_tool [flash] [boot|recovery] [in.lok]

> Find offset from aboot image:

/data/local/tmp/loki_tool [find] [aboot.img]

> Revert Loki patching:

/data/local/tmp/loki_tool [unlok] [in.lok] [out.img]

1|root@awifi:/ # exit

exit

1|shell@awifi:/ $ exit

exit

F:\Software_Tools\Multimedia\Handy-Taplet\LG Pad 8.3\Recovery-Kernel\ADB + Fastb

oot>adb reboot recovery

F:\Software_Tools\Multimedia\Handy-Taplet\LG Pad 8.3\Recovery-Kernel\ADB + Fastb

oot>

---------- Post added at 04:19 PM ---------- Previous post was at 04:01 PM ----------

I install now 10b and i hope i can flash this ****ing twrp. On 20d and 20b are not working. Its better you write on first post in big font this not work on any 20 rom!!!!!!
[G Pad 8.3 Original Android Development] Deltadroid:
There is a link here for 10a (on post #36) and I know it works with that image. It should also work fine for 10b.
[G Pad 8.3 Original Android Development] cobra698:
Where i find loki aboot.img supported?
[G Pad 8.3 Original Android Development] Deltadroid:
You have to downgrade your firmware. I have posted a link to an image on post #36 in this thread.
[G Pad 8.3 Original Android Development] cobra698:
i have the version V50020d.i can flash with flash tool the version V50010a!and then return ROM V50020d whit castom recovery?
[G Pad 8.3 Original Android Development] Deltadroid:
Yes, once you have a custom recovery installed, then you can flash the other firmware bases and custom ROMS.

You must use lg flash tool 2014 in order to downgrade.
[G Pad 8.3 Original Android Development] HTC Tytn user 188:
I have this on my tablet. Does this handle android 5.x roms without problems?
[G Pad 8.3 Original Android Development] Deltadroid:
Yes, this works with android 5.x.
[G Pad 8.3 Original Android Development] Schrotty35:
Any Update to latest cource for cm?
[G Pad 8.3 Original Android Development] Deltadroid:
There is nothing new yet. This is the latest code available.
[G Pad 8.3 Original Android Development] Deltadroid:
Today I have been testing out the new Cyanogen Recovery (formerly known as ClockWorkMod) from the lollipop branch. I was going to create a new thread but there are still a few show stoppers.

1) can not disable signature verification so nothing can be flashed except official cm packages.

2) can not make backups yet.

I will keep close watch on the code and open a thread as soon as it is ready for prime time. In the mean time, attached is a screenshot of what is to come...
[G Pad 8.3 Original Android Development] HTC Tytn user 188:
Im selling my Device which now have this recovery installed and LiquidSmooth v4.0 Android 5.0.1 rom. I would like to flash device back to Stock so the Custom recovery etc. will go away and device would be completely stock.

Do i just need to download LG MOBILE SUPPORT TOOL from here: http://www.lg.com/uk/support-mobile/lg-LGV500 and it will delete all or what do i need to do?
[G Pad 8.3 Original Android Development] Deltadroid:
Yes, the LG tool will put it back to stock when it downloads the latest image. It will overwrite the recovery and make that stock too.
[G Pad 8.3 Original Android Development] HTC Tytn user 188:
I cant get my downgrade tool work. It wont find the device. All guides says device must be on LG mode but i cant have it because im on custom rom. I tried to flash official rom on CWM but it did not work. Can you give link or guide how can i flash official back. I want to get rid of this CWM and back to stock and i need to do it fast.
[G Pad 8.3 Original Android Development] Deltadroid:
Just reboot your tablet into download mode and connect to your pc. Then flash the tablet using the latest official lg tool program. You must not be using the correct options in the lg tool program to completely reset. But, you need to use the lg tool with the tablet connected to the pc when it's in download mode.

Edit: you may need to manually download the image to flash.
[G Pad 8.3 Original Android Development] HTC Tytn user 188:
EDIT: My bad got it work. Thanks
[G Pad 8.3 Original Android Development] lmendoza23:
when i try adb push recovery.img /data/local/tmp it says device not found
[G Pad 8.3 Original Android Development] Deltadroid:
Type this command first to verify if your device is connected to adb:

adb devices
[G Pad 8.3 Original Android Development] lmendoza23:
It shows that there are no devices and I am using terminal emulator
[G Pad 8.3 Original Android Development] Deltadroid:
Oh, when using terminal emulator, you must copy the files using a different method, such as root explorer. The example on the op is using the adb method with the tablet connected to a computer with a usb cable.

If you don't have adb setup on a computer, you can also flash the recovery.img with a program called Flashify found on Google Play. This requires root also.
[G Pad 8.3 Original Android Development] lmendoza23:
I used es file explorer

So i could just use the app and not worry about the adb stuff
[G Pad 8.3 Original Android Development] Deltadroid:
Yes, you can just use Flashify and forget the rest as long as you have root and an aboot.img from 4.2.2 (10a).
[G Pad 8.3 Original Android Development] auleu:
latest cwm version is 6.0.4.7 , where does the 6.0.5.1 come from?
[G Pad 8.3 Original Android Development] Deltadroid:
6.0.5.1 is the latest version from the nightly cm11 build.

Tonight,I will make a new bumped version of cwm 6.0.5.1 and I will bump the last cm11 nightly build so the stock kernel will be bumped also.
[G Pad 8.3 Original Android Development] auleu:
thx. is the newer cyanogen recovery better?