Database Develop

[Recovery/Bootstrap][5-sep-2012] CWM Touch recovery v6.0.1.1

Touch enabled ClockWorkMod for LG Optimus 4X HD 4.0.3 ONLY
NOT COMPATIBLE WITH LG EARLY BETA v20a WITH Android OS 4.1.2
ClockWorkMod recovery based on http://builder.clockworkmod.com but of course not using a boot.img here, but a raw ramdisk copy of it.​
Todo's
A bootup check function, on external sdcard, for a _boot direct to recovery_ in case you
cannot get regular apps opened, this might be a way to boot recovery in bootloop cases.
HOWTO install
UPDATES: if you are installing an update , remember to press install recovery again, so the changes take effect.
Get your o4x root'd, follow this guide here
make sure busybox is installed correctly and all commands are available in /system/xbin (normally part of rooting installation)
Download the attached zip to this post
extract the apk from inside the downloaded zip file.
install the LG-Optimus-4XHD-Recovery apk on your mobile
after installation reboot mobile once (if you do not, the app might fail installing recovery)
start the LG 4X Recovery app
press - Install recovery - grant superuser access when prompted
wait for success OK, if it fails, something is wrong or SU is not properly installed or denied su access. you should set permissions to granted for this app
after successfull installation, you can press boot recovery and boot into the clockworkmod recovery and make your backups or install custom roms
when you do a backup, remember that CWM v6.0.1.1 got a bug, so you need to specifically chose backup to external sdcard for now.
ChangeLog
05-sep-2012
- uses latest boot base from v10f (OPEN edition), but not much changed
-Found issue with unmount of /system and other filesystems during start of clockworkMod, making it hard to restore backup.
all filesystems are now properly unmounted and services stopped which could use it.
- for adb users, unplug usb cable once, to re-activate adb connection when cwm starts.​
current issues
backup to internal sdcard location is not working , use backup to EXTERNAL sdcard (problem is the link in / which point to /mnt/sdcard)
(FIXED in v1.1) factory reset/restore backup - if you restore a backup or factory reset, it will also wipe your internal storage/sdcard location. as LG have chosen to use part of internal store on same partition.
so where possible, always copy your internal storage files to a safe location
(Koush removed this option in v6.0.1.1)external sdcard - mount usb - currently shares only external sdcard storage to pc.​general notes
It is to assume, that anything restored from a backup, will include any 4X clockwork recovery, as this is located on your system partition.
so its always good to install the newest apk, after a restore of your backup.​
snapshots of recovery running on LG Optimus 4X HD
{
"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"
}
​information on the technical solution used
The bootstrap solution used to run ClockWorkMod is based on the 2nd-init function , which has been around for some time now.
Additional functions are used here, based on services started and building small changes into the unsecure ramdisk, so we get the full functionality of our device.
For those technical users, wanting to use my work, just remember to mention where you got it, and i have no problems with others using scripts.
It's also important when booted into recovery, that you restart adb (adb usb) to get full root access.
as this recovery is not started from a clean bootup, some cleanup jobs are required for those, that MIGHT do a custom rom.
i have seen with my works in progress, that jellybean and htc roms use different services and those needs to be included in the bootmeny/bootrecovery script to stop and cleanup what ever service started originally. so when/if someone makes a different rom, remember to update the bootmenu scripts, which i guess you know how to change if you do customroms.

reserved for future

Nice job

Just like my old milestone
Bootloader is locked so restore from recovery is the only method of using custom roms...

Awesome work. Cant wait for a release!

Good Job!!!!!!
Now,I just have to wait for a cleaner root method from you,
that make install busybox from forced to option XDDD

Great news, thanks for your hard work!!!
Gesendet von meinem LG-P880 mit Tapatalk 2

i am working on how to get recovery started and it ain't that easy.
as you know security meassures taken by LG was quite high, so even key chord triggers from boot is disabled in the kernel, so we cannot activate by any keys for now.

great job so now just waiting to work with recovery.
:thumbup:
Inviato dal mio LG-P880 con Tapatalk 2

Ok,
i am almost ready with the complete package for recovery install (NO root install or similar)
requirements will be that you got o4x root'd to run this installer properly.
Since we got no key detect function in bootup(missing in kernel) available or binary app to extract a keypress, this app will need to run to activate recovery at next boot. thats the solution for now.
ill return with the app installer soon

Dexter_nlb said:
Ok,
i am almost ready with the complete package for recovery install (NO root install or similar)
requirements will be that you got o4x root'd to run this installer properly.
Since we got no key detect function in bootup(missing in kernel) available or binary app to extract a keypress, this app will need to run to activate recovery at next boot. thats the solution for now.
ill return with the app installer soon
Click to expand...
Click to collapse
Thanks Dexter,you're GREAT:good:

OTOGY2002 said:
Thanks Dexter,you're GREAT:good:
Click to expand...
Click to collapse
thx also, great done

testing backup/restore function now.
had some issues mounting /sdcard correctly.
i am close to releasing it now. but want to make sure you do not mess up your mobile using it, so i sacrifice my own before going alpha public with it.

First ALPHA-BETA release in post #1
First release is now attached in post #1 .
do note, this can be experimental based on how users get root'd their mobile, if they did not follow guides or experimented.
but generally it should be ok,
i have tested backup/restore and all looks good for now.
its VERY important, you do not just factory reset or restore a backup, since internal storage is mapped to /data/media location, and you will loose all your stored files here. so backup those files before you start restoring or a factory reset as both functions will format data partition.

Thanks man! Works great

I've inattentively read the instructions and do not reboot before install recovery and now have bootloop
Code:
E/ThermalDaemon( 162): waiting for boot complete
E/ThermalDaemon( 162): waiting for boot complete
E/NetdConnector( 258): Communications error
E/NetdConnector( 258): java.io.IOException: No such file or directory
E/NetdConnector( 258): at android.net.LocalSocketImpl.connectLocal(Native Method)
E/NetdConnector( 258): at android.net.LocalSocketImpl.connect(LocalSocketImpl.java:238)
E/NetdConnector( 258): at android.net.LocalSocket.connect(LocalSocket.java:98)
E/NetdConnector( 258): at com.android.server.NativeDaemonConnector.listenToSocket(NativeDaemonConnector.java:119)
E/NetdConnector( 258): at com.android.server.NativeDaemonConnector.run(NativeDaemonConnector.java:88)
E/NetdConnector( 258): at java.lang.Thread.run(Thread.java:856)
E/NetdConnector( 258): Error in NativeDaemonConnector
E/NetdConnector( 258): java.io.IOException: No such file or directory
E/NetdConnector( 258): at android.net.LocalSocketImpl.connectLocal(Native Method)
E/NetdConnector( 258): at android.net.LocalSocketImpl.connect(LocalSocketImpl.java:238)
E/NetdConnector( 258): at android.net.LocalSocket.connect(LocalSocket.java:98)
E/NetdConnector( 258): at com.android.server.NativeDaemonConnector.listenToSocket(NativeDaemonConnector.java:119)
E/NetdConnector( 258): at com.android.server.NativeDaemonConnector.run(NativeDaemonConnector.java:88)
E/NetdConnector( 258): at java.lang.Thread.run(Thread.java:856)
E/ThermalDaemon( 162): waiting for boot complete
Can i fix it without reflashing?

m0b said:
I've inattentively read the instructions and do not reboot before install recovery and now have bootloop
?
Click to expand...
Click to collapse
yes.
if you can "su -" it will be ok.
then
0. su -
1. mount -orw,remount /system
2 mv /system/bin/netd.bin /system/bin/netd
thats the problem. netd is not ok.
Can i fix it without reflashing

Recovery on system partition, that's brilliant.
I'm new with 2nd init, try to read about it so may be I can help somehow.

atipon said:
Recovery on system partition, that's brilliant.
I'm new with 2nd init, try to read about it so may be I can help somehow.
Click to expand...
Click to collapse
any help is appreciated, its not easy to test and get around all the stupid things LG invented here. they more we resolve, less of it will be added if they find it worthless to do (nahh, but sounds good)

Now i cant start it again

[RECOVERY][ks01lte] TWRP 3.1.0-0 touch recovery with F2FS support [CLOSED UPDATES]

-- Team Win Recovery Project --​
{
"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"
}
Supported model ONLY ks01lte​
I'm sorry but my i9506 is definitely dead, who wants to use my source code to create new updates this is the guide:
(links below)
device > use branch cm-14.1_twrp
kernel > use branch cm-14.1-rc
android_bootable_recovery repo > rebase with official omni repo or cherry-pick my last two commit on top​
Team Win Recovery Project 3.x, or twrp for short, is a custom recovery built with ease of use and customization in mind. Its 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.
I built this recovery by using my cleaned source code for kernel and OmniRom for twrp.
If you find any bug or problem please reply below this thread or use the dedicated tab page "Bug Reports" over here.
Phone look:
Features:
MTP auto mounting for SD / External SD
Mass storage mounting for External SD
Usb OTG
Full SELinux support
Supported F2FS (system, data, cache partitions)
CPU temperature handled
Thermal control and Performance profiles are active by default
Backup/Restore tested with 4.4.2/5.1 TW original samsung rom and all CyanogenMod
Screen shot capture enabled (Volume (-) + Power) (saved in the "Picture" folder)
Charge-Led
Known problems:
-Samsung HW encryption does not work well, follow this steps to decrypt /data: (thanks Diapolo)
1 - In the initial dialog "Enter Password." press Cancel
2 - "Swipe to Allow Modifications"
3 - Go to "Mount" and select "System" partition
4 - Press "Decrypt Data" and on "Enter Password." dialog press Accept
Changelog:
This is the changelog of my TWRP versions releases, if you want read the original changelog of TWRP versions go to:
http://teamw.in/project/twrp2
CHANGELOG for 3.1.0-0 [04/04/2017]:
-Updated kernel
CHANGELOG for 3.0.3-0 [18/12/2016]:
-Updated kernel
-Fixed twrp screen off timeout problem
CHANGELOG for 3.0.2-0 [20/11/2016]:
-Switched to TWRP android-7.1 branch
-Builded with a new stable kernel for Nougat and CM-14.1
-Added /misc partition on fstab for the recovery commands (Nougat changes)
-Tried to add Samsung HW encryption, it does not seem to work well i think it's incomplete, in our stock rom missing some file
such as keystore.xx.so and firmware files such as keymaster.xxx
CHANGELOG for 3.0.2-0 [08/05/2016]:
-Fixed chargeled service
-Fixed SEANDROIDENFORCE warning at boot, again
-Some changes in the partitions parameters on fstab
CHANGELOG for 3.0.2-0 [07/05/2016]:
-Switched to TWRP android-6.0 branch
-Builded from cm-13.0 repo
-New kernel made by me with latest LP sources
CHANGELOG for 2.8.7.0 [01/08/2015]:
-Switched to TWRP android-5.1 branch
-Builded from cm-12.1 repo
-Updated kernel from cyanogenmod
-Fixed brightness slider
-Fixed SEANDROIDENFORCE warning at boot
CHANGELOG for 2.8.5.0 [15/02/2015]:
-Fixed problem when wiping Data partition in F2FS
CHANGELOG for 2.8.4.0 [07/02/2015]:
-Added rewrite of TWRP settings after a SD wipe (prevent lost settings)
-Fixed mount F2FS or others filesystems to system, data, cache partitions
-Updated with latest changes from source
CHANGELOG for 2.8.4.0 [24/01/2015]:
-Switched to TWRP android-5.0 branch
-Brightness slider still does not work (it's a kernel related problem)
CHANGELOG for 2.8.1.0 [24/01/2015]:
-Updated kernel from cyanogenmod
-Screen blink on boot is not longer present
-Brightness slider no longer work (it's a kernel related problem)
-Added chargeled - adapted for samsung devices
CHANGELOG for 2.8.1.0 [27/11/2014]:
-Enabled mass storage mounting for external sd
-Fixed MTP mounting without external sd
CHANGELOG for 2.8.1.0:
-Initial TWRP release for I9506 (ks01lte)
How to do for install it:
FIRST INSTALL FROM ODIN (v3.07 or higher):
-Download twrp .TAR.MD5 file.
-Go to download mode (Volume down + Home + Power)
-Open Odin and check AutoReboot and F.Reset Time checkboxes are selected, also Re-Partition it NOT selected.
-Click on AP (PDA) and select the downloaded twrp recovery tar.md5 file.
-Check if all options are corrects, and press Start.
-Once the installation process complete, your phone will restart and soon you will see a PASS message with green background in the left-most box at the very top of the Odin. You can now unplug the USB cable to disconnect it from the computer.
-Some users has found problems with previous procedure: in this unlucky situation, when phone reboot and the logo (i9506 Samsung S4 Galaxy) appear, pull out the battery. Don't panic, the logo is there for several seconds. The installation process should be finalized now. There will be no PASS status in Odin. Put back the battery in the phone and try to boot straight to recovery.
UPGRADE YOUR TWRP:
-Download twrp .ZIP file.
-Copy the recovery zip file in the internal SD or external SD.
-Go to recovery mode (Volume up + Home + Power)
-Touch the INSTALL button.
-Select the appropriate SD
-Select the twrp file copied previously and slide to flash.
-Press back some times and reboot.
DOWNLOAD:
You can dowload the current version from this folder, you will find the flashable zip and tar version.
CLICK HERE TO GET DOWNLOAD FOLDER
To download Odin go here: samsungodin.com
SOURCES:
TWRP Source: https://github.com/omnirom/android_bootable_recovery
Kernel Source: https://github.com/CastagnaIT/android_kernel_samsung_ks01lte
Device Source: https://github.com/CastagnaIT/android_device_samsung_ks01lte
Thanks to: CyanogenMod, OmniRom Team, TWRP Team, Dees_Troy, Solk2, DualJoe​
XDA:DevDB Information
TWRP, Tool/Utility for the Samsung Galaxy S4
Contributors
CastagnaIT, smeroni68
Version Information
Status: Stable
Current Stable Version: v3.1.0-0
Stable Release Date: 2017-04-04
Created 2014-11-16
Last Updated 2017-07-15

Thank you! It works great!
Sent from my Galaxy S4 LTE-A [GT-I9506] using Settings app

I've trayed stock recovery version. It doesn't work, there is something wrong with "footer"?
Signature verification failed.
I have the latest stock NEE firmware.
Wysłane z mojego GT-I9506

checking in the next days, probably the stock recovery isn't compatible with the classic signature, for now use odin

Your current filename TWRP_2.8.1.0_ks01lte_20141115.tar.md5 won't get accepted by Odin 3.09. It should be TWRP_2.8.1.0_ks01lte.tar.md5 as generated by md5sum (that includes/binds filename as well). Or just omit md5sum step completely. Its not mandatory.
Edit: Looks like forum database has been set back (and so is your 1st post). One fellow guy is missing again.

working perfectly for me thanks
Sent from my GT-I9506 using XDA Free mobile app

Fixed files updated from CIT... md5 corrected...

When I'm trying to root my I9506 it tells me it failed to verify footer. I have tried keymaster, PhilZ touch and ROOT_E330S_I9506_v2 - it won't root the phone. And since this goes on, I cannot use Odin to flash neither TWRP or CWM (specified for I9506). I really hope for some help for this, as it bugs me really hard.

nydxlil said:
When I'm trying to root my I9506 it tells me it failed to verify footer. I have tried keymaster, PhilZ touch and ROOT_E330S_I9506_v2 - it won't root the phone. And since this goes on, I cannot use Odin to flash neither TWRP or CWM (specified for I9506). I really hope for some help for this, as it bugs me really hard.
Click to expand...
Click to collapse
Du får ikke root ved at flashe recovery... Du skal flashe en version (som svarer til din firmware version) af AutoRoot fra denne tråd http://forum.xda-developers.com/showthread.php?t=2597058

morten82 said:
Du får ikke root ved at flashe recovery... Du skal flashe en version (som svarer til din firmware version) af AutoRoot fra denne tråd http://forum.xda-developers.com/showthread.php?t=2597058
Click to expand...
Click to collapse
Så har jeg åbenbart fuldstændig misforstået de guides der er. Alle de forskellige roots jeg har fundet har ikke været signed så dem har jeg ikke kunne bruge Jeg prøver en af de pre-rooted rom'er og ser om de ikke kan "do the magic" senere i dag, BBL med svar. På forhånd tak

ENGLISH PLEASE!! XDA Rules!! Thanks

Kernel seandroid enforcing?
Hi. I have flasch tvrp recovery and it works perfect.
Only thing is this message on boot screen KERNEL IS SEANDROID ENFORCING
NO WARANTY BIT.
what its this?
Thanks for answers.
Sorry for my bad English

Rado G said:
Hi. I have flasch tvrp recovery and it works perfect.
Only thing is this message on boot screen KERNEL IS SEANDROID ENFORCING
NO WARANTY BIT.
what its this?
Thanks for answers.
Sorry for my bad English
Click to expand...
Click to collapse
Not stock recovery give knox 0x1 broken... the message is reporting this... it is irreversibile... That's the rule...
Inviato dal mio GT-I9505 utilizzando Tapatalk

--new updates--
Only a quick update, the most important i fixed the MTP mount for internal storage when external SD isn't present, that before seemed not work properly.
All the changelog below.
CHANGELOG for 2.8.1.0 [27/11/2014]:
-Enabled mass storage mounting for external sd (CastagnaIT)
-Fixed MTP mounting without external sd (CastagnaIT)
-Various other bugfixes and tweaks by twrp team
Click to expand...
Click to collapse
Bye
CastagnaIT

Thanks for the update.
So far, working fine here.

CastagnaIT said:
Only a quick update, the most important i fixed the MTP mount for internal storage when external SD isn't present, that before seemed not work properly.
All the changelog below.
Bye
CastagnaIT
Click to expand...
Click to collapse
Thank you for the update! [emoji106]

WOW
Super! Works pretty good on I9506 with rooted Stock Rom 4.4.2 NNE ! Big thanks from Germany!:good:

Hey,
Recently bought Galaxy S4 4g+ (i9506) and now trying to flash the latest TWRP (TWRP_2.8.1.0_ks01lte_20141127.tar.md5) with Odin 3.07, but it doesn't seem to work? Odin completes the flash just fine and gives the green "PASS" just fine but when I boot into recovery it's just the default one. Also Knox Warranty flag isn't triggered. What should I do to be able to flash TWRP (or any custom recovery)?
Thanks.
---------- Post added at 06:56 PM ---------- Previous post was at 06:02 PM ----------
enkku said:
Hey,
Recently bought Galaxy S4 4g+ (i9506) and now trying to flash the latest TWRP (TWRP_2.8.1.0_ks01lte_20141127.tar.md5) with Odin 3.07, but it doesn't seem to work? Odin completes the flash just fine and gives the green "PASS" just fine but when I boot into recovery it's just the default one. Also Knox Warranty flag isn't triggered. What should I do to be able to flash TWRP (or any custom recovery)?
Thanks.
Click to expand...
Click to collapse
Nevermind, battery pull trick did it and got it installed now (removed battery on Galaxy S4 logo after it auto reboots after flashing TWRP with Odin).

When trying to flash ROM (CM12 2.4.1 I9506) it seems like it can't install/mount/unmount the /data, which results in the the recovery prompts that OS is not installed.
I've tried both TWRP and PhilZ (in PhilZ i get error: "unmount of /data failed; no such volume").
I'm desperate for a solution! Thanks in advance!

Thanks for this versions. I can instal cm12 lollipop with. Thanks

[ROM] fRomFuture - Genesis (B172) KangVip Mod

Welcome to Genesis
{
"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"
}
Base B172
Busybox
prerootet with Magisk
Viper4Android
Callrecorder
Init.d support
light debloadet
Data usage in notification panel
Parentsmode
VoLTE (if you provider support it)
More clone apps
3D Panorama Camera Mod
And you can remove your FRP Lock! If you have FRP lock [emoji6]
Install from Stock:
Backup your Data
Unlock bootloader
install TWRP (Download)
Backup Stock with TWRP (System,Cust,Version,Product,Vendor)
Wipe System,Cust,Version,Product,Vendor in TWRP
Format Data Partition (type YES)
Copy files to your phone
install Rom
L29C432 User can reboot now
install Data Files for other brands
Reboot and have fun
Install from Custom Rom:
Backup your Data with TWRP
Wipe System,Cust,Version,Product,Vendor in TWRP
Wipe Data for a Clean Flash or try dirty
Copy Rom to your Phone
install Rom and KangVipMod (if you want)
L29C432 User can reboot now
install Data Files and reboot (other brands)
If you installed KangVip Mod at first boot a huawei app asked for root permission . Just grant for a full working rom!
DOWNLOAD B172
Datafiles L09C432
Datafiles L29C636
Datafiles L29C567
Datafiles AL00
KangVip Mod for B172:
Download
For emmc user :
DOWNLOAD B172
KangVip Mod for B172:
Download
Androidfilehost dont have a P10plus Folder yet. So its ok downloading this file
Credits to:
tecalote
tkkg1984
chainfire
guitardedhero
mankindtw
Disclaimer: I will not take any responsibility for anything wrong happen to your device. Do it at your own risk.
Join my Telegram Group for more info, testbuilds or just for fun:
https://t.me/joinchat/BpBgfQ1WyaKBrDxiEzUWjQ
​

Blackball said:
Welcome to Genesis
Base B150
prerootet with SuperSU 2.82
Busybox
Viper4Android
Callrecorder
Init.d support
light debloadet
This is the first build and i think i can add more features in the future.
Install:
Unlock bootloader
install TWRP (Download)
Backup Stock (System,Cust,Version,Product,Vendor)
Wipe System,Cust,Version,Product,Vendor
Format Data Partition (type YES)
Copy Rom to your Phone
install Rom
Reboot and have fun
Its testet with VKY-L29C432B133 and everything is working fine.
If there is any problems you can try to install oeminfo from B133. If that not work debrand to VKY-L29C432B133.
DOWNLOAD
MD577c83b8eccbf1f69d0ebb9daa6190bc1
Androidfilehost dont have a P10plus Folder yet. So its ok downloading this file
Credits to:
tecalote
tkkg1984
chainfire
guitardedhero
Disclaimer: I will not take any responsibility for anything wrong happen to your device. Do it at your own risk.
​
Click to expand...
Click to collapse
Hi,
I have P10 Plus L29C432B123, can I install firmware B150 over it with TWRP without loosing bootloader unlocking and without erasing data (I have already configurated my phone and installed a lot of apps, I wish to keep them...) ?
How I must proceed ?
Thanks for the attention.

The recovery have data partition encription?
For "wipe data" are required, without that probably brick the device...

@anabolic_guy
After install the bootloader is still open but you need to make a full wipe. So you lost all your data but you can make a Backup with the Huawei tool or titanium backup.
@BadWolfYe
The recovery don't have data encryption but its not needed if you patch the kernel. It will not brick your device.!
You can always back to stock with HWOTA method and then your data partition is stock again [emoji6]
Gesendet von meinem VKY-L29 mit Tapatalk

Blackball said:
@anabolic_guy
After install the bootloader is still open but you need to make a full wipe. So you lost all your data but you can make a Backup with the Huawei tool or titanium backup.
@BadWolfYe
The recovery don't have data encryption but its not needed if you patch the kernel. It will not brick your device.!
You can always back to stock with HWOTA method and then your data partition is stock again [emoji6]
Gesendet von meinem VKY-L29 mit Tapatalk
Click to expand...
Click to collapse
Does it work for VTR or could you make it work?

I'm sorry. I don't know. The only way is that you test it.
But I think there are some changes needed but kernel, system partition and twrp are compatible.
Gesendet von meinem VKY-L29 mit Tapatalk

Blackball said:
@anabolic_guy
After install the bootloader is still open but you need to make a full wipe. So you lost all your data but you can make a Backup with the Huawei tool or titanium backup.
@BadWolfYe
The recovery don't have data encryption but its not needed if you patch the kernel. It will not brick your device.!
You can always back to stock with HWOTA method and then your data partition is stock again [emoji6]
Gesendet von meinem VKY-L29 mit Tapatalk
Click to expand...
Click to collapse
Thanks a lot for the answer.

funiewski said:
Does it work for VTR or could you make it work?
Click to expand...
Click to collapse
Blackball said:
I'm sorry. I don't know. The only way is that you test it.
But I think there are some changes needed but kernel, system partition and twrp are compatible.
Click to expand...
Click to collapse
I'd be surprised if it didn't work on both the P10 & P10+. Apart from screen resolution and amount of RAM, both phones are pretty much identical and don't forget the KangVIP rom works on both (if you can get it running, lol!)
So unless @Blackball has seriously messed around with some system files then I think it will be ok, and as he says, you can always go back to stock
@Blackball : Interesting that you format data though, does the kernel have forceencrpytion disabled so we can use an unencyrpted data partition?

colthekid said:
I'd be surprised if it didn't work on both the P10 & P10+. Apart from screen resolution and amount of RAM, both phones are pretty much identical and don't forget the KangVIP rom works on both (if you can get it running, lol!)
So unless @Blackball has seriously messed around with some system files then I think it will be ok, and as he says, you can always go back to stock
@Blackball : Interesting that you format data though, does the kernel have forceencrpytion disabled so we can use an unencyrpted data partition?
Click to expand...
Click to collapse
I was going to test it anyway, but asking does not harm

I need the data partition for the Rom so I decided to format the data partition. And yes we can use the unencrypted now.
Gesendet von meinem VKY-L29 mit Tapatalk

Blackball said:
Welcome to Genesis
Base B150
prerootet with SuperSU 2.82
Busybox
Viper4Android
Callrecorder
Init.d support
light debloadet
This is the first build and i think i can add more features in the future.
Install:
Backup your Data
Unlock bootloader
install TWRP (Download)
Backup Stock (System,Cust,Version,Product,Vendor)
Wipe System,Cust,Version,Product,Vendor
Format Data Partition (type YES)
Copy Rom to your Phone
install Rom
Reboot and have fun
Its testet with VKY-L29C432B133 and everything is working fine.
If there is any problems you can try to install oeminfo from B133. If that not work debrand to VKY-L29C432B133.
DOWNLOAD
MD577c83b8eccbf1f69d0ebb9daa6190bc1
Androidfilehost dont have a P10plus Folder yet. So its ok downloading this file
Credits to:
tecalote
tkkg1984
chainfire
guitardedhero
Disclaimer: I will not take any responsibility for anything wrong happen to your device. Do it at your own risk.
​
Click to expand...
Click to collapse
Hi,
I followed all your instructions but, when I connect the device with usb debug active, the phone doesn't ask me the permission to validate the pc access with the confirmation dialog, so I cannot connect properly.
I also, in developer menu, I clicked on restore the standard settings and this disactivated also the unlock vendor...
Please help me.
Thanks
Cesare.

Hi, pressing on restore standard is not a good idea. I will check how you can get it back.
With PC access do you mean adb?
Gesendet von meinem VKY-L29 mit Tapatalk

Blackball said:
Hi, pressing on restore standard is not a good idea. I will check how you can get it back.
With PC access do you mean adb?
Gesendet von meinem VKY-L29 mit Tapatalk
Click to expand...
Click to collapse
Yeah, adb and hisuite
In addition of this I cant' find neither in developer menu the option: Revoke USB debugging authorization
This appears when I run adb:
C:\adb>adb devices
List of devices attached
BHY7N17322002196 unauthorized
C:\adb>adb reboot fastboot
error: device unauthorized.
This adbd's $ADB_VENDOR_KEYS is not set; try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
But dialog confirmation never appears....

anabolic_guy said:
Yeah, adb and hisuite
In addition of this I cant' find neither in developer menu the option: Revoke USB debugging authorization
This appears when I run adb:
C:\adb>adb devices
List of devices attached
BHY7N17322002196 unauthorized
C:\adb>adb reboot fastboot
error: device unauthorized.
This adbd's $ADB_VENDOR_KEYS is not set; try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
But dialog confirmation never appears....
Click to expand...
Click to collapse
I have flashed the original rom and I have avaiable again (not grayed) the swith to enable oem unlocking, but when I enable it, immediately it returns at the original position (disable).
I don't understand why...
I am desperate...

How did you install the original rom?
Gesendet von meinem VKY-L29 mit Tapatalk

Blackball said:
How did you install the original rom?
Gesendet von meinem VKY-L29 mit Tapatalk
Click to expand...
Click to collapse
With HWOTA_VKY

So when you have now original recovery try to install from firmware finder. Another user had the same problem and fix it.
Gesendet von meinem VKY-L29 mit Tapatalk

Blackball said:
So when you have now original recovery try to install from firmware finder. Another user had the same problem and fix it.
Gesendet von meinem VKY-L29 mit Tapatalk
Click to expand...
Click to collapse
Hi, I have restored the phone and installed again your rom (oem unlock, bootloader unlock): the real probelm is that once installed when I try to connect the device with usb debug active, the phone doesn't ask me the permission to validate the pc access with the confirmation authorization fingerprint dialog, so I cannot connect properly, adb see the phone as unauthorized.
Either the "Revoke USB debugging authorization" menu is disappeared...
Please check carefully.

I will check that and i sent you a pm

Blackball said:
I will check that and i sent you a pm
Click to expand...
Click to collapse
Answered, take a look at ADB message

[ROM][H870][Stock] OPEN EU LG-H870 11I ROM

{
"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"
}
LG-H870 OPEN EU 11I ROM​Hello everyone
LG rolled out a new update to 11I
Changelog from LG:
Code:
[Feature]
- Phone usability and functionality has been further improved
Changelog what I noticed and found:
Code:
*New Security Patch
This zip is created from the original KDZ. I changed the Boot.img, so you do not have to reinstall TWRP. . .
I had made this for users who can not get ota's because they have Custom Recovery / Root installed
Sorry for my bad english i'm out of practice ​
Features​ *Stock build made from official KDZ
*Stock Build.prop
*Unrooted
*Boot.img modified to keep TWRP
*Remove dm-verity
*Remove forceencrypt​Installation​ What you need​ *Unlocked Bootloader [How to do]
*Working TWRP installed [Link to official TWRP]
*When you need Root, Latest SuperSU [Download] or Magisk [Download]
*H870 11I OPEN EU (TWRP).zip [Download]​
How to install​ Reboot to recovery using button combo or reboot app (need root)
Backup Dalvik,ART, Cache, System & Data (include not your internal memory) and Boot
in to your external sd or copy the backup from internal sd to your PC!
For clean install: Wipe Dalvik/ART, Cache, System and Data (Recommend)
You can also keep your data by dirty flashing the zip.
Flash H870 11I OPEN EU (TWRP).zip
Flash SuperSU or Magisk zip when you need root
Reboot System
At the first time you boot to system, it can be TWRP says No OS installed. You can ignore it.
If TWRP asks if you want to install SU, hit no​
Here you can find my other [Downloads.] There are IMG´s, KDZ´z and more!​
Rom Version
Android Version: 7.0
Android security patch level: 2018-01-01
Build date: 2018-01-08
Build number: NRD90U
MD5 SUMS:
Code:
[SIZE="4"][B][COLOR="Black"]boot.img 26ebe54e36a36519d2faf34a69d20205
modem.img fc865d7ac8c318f3148dc86919860c5a
persist.img 02a9745cf73e5fa2382f6d2373270d5b
rct.img 15bc82584049ec3a7c62d921c2897267
system.img a66f0a9eb2245ce17c20ef02b32c0cff
aboot.img 4b30803c97a1e6dd6d3a943534de5aa2
apdp.img 1750792e461d3007acdb2117157de687
cmnlib.img 33b7d2cfcf2343a114458080a072466f
cmnlib64.img f46a7c1d57f82f31894c23921055a3e0
devcfg.img 7c7a00cdb1fc5406d06ae71e25c629f2
factory.img 15bc82584049ec3a7c62d921c2897267
hyp.img 340706b10312615b4e10b993680997a6
keymaster.img 95105995db358581b534eb837b9957d9
laf.img 4a9a633285f98af084c3a755cd6d197a
msadp.img 0e0c19f7a255db4f4130a784a60387ab
pmic.img 8f9bdf5a1c7172e5f8e7a269717f55fb
raw_resources.img 07d187a09cf0cc83cf6d2b3781019204
rpm.img 30648f189a83a0be802852d29510de98
sec.img 628756d1475c7e6ffa2f974c63261bf6
tz.img dfa61ef23f4955b101b1b4159e10b6fb
xbl.img a0464b8e061b94c6b6083a24683fec73[/COLOR][/B][/SIZE]
Credits:
@autoprime
@J0SH1X's
@Chainfire
@topjohnwu
@Me :laugh:
Don´t forget to hit the thanks-button if you like my work! :good:
You want to help me with a [donation?] Feel free to make it.​

Boot.img md5 in your downloads is: d101942135865580b75280b9ece767c1
Is this your modified boot.img and does it include rct free patch?
Thanks

No this is stock boot image and with rtc.

Tnx bro with love and respect for your work

Hey guys I have a problem
tried to update as usual but then when I hit reboot it rebooted into recovery again
tried it several times it always reboots to recovery
also tried to use another zip that worked before but still the same
need help

Tatsuyamoto said:
Hey guys I have a problem
tried to update as usual but then when I hit reboot it rebooted into recovery again
tried it several times it always reboots to recovery
also tried to use another zip that worked before but still the same
need help
Click to expand...
Click to collapse
Du hast bestimmt vorher lineage oder sowas drauf gehabt?
sichere deine daten und dann musst du mit lg up und der kdz flashen.
You've probably had lineage or something on it before?
save your data and then you have to flash with lg up and the kdz.

westwood24 said:
Du hast bestimmt vorher lineage oder sowas drauf gehabt?
sichere deine daten und dann musst du mit lg up und der kdz flashen.
You've probably had lineage or something on it before?
save your data and then you have to flash with lg up and the kdz.
Click to expand...
Click to collapse
jup
heißt ich flashe das wieder per recovery (hoffe das geht) und dann per lg up und der kdz wieder auf stock ??
weil up erkennt das g6 während es in recovery oder im bootloader ist leider nicht
Edit: 0:42
habs grad probiert das nochmal zu flashen aber es bootet trotzdem nur in die recovery :/
und mein Backup hab ich aus versehen gelöscht
was nun ??
Edit2: 1:40
ok habs geschafft *puh*
vol+ und kabel rein bringt einen ja auch in den download-mode wo lgup das g6 erkennt
jz erst mal schlafen
trotzdem danke für deine bemühungen

Works beautifully, though after a while I'm prompted to install an LG OTA update (08/01). Ideas?

admkx said:
Works beautifully, though after a while I'm prompted to install an LG OTA update (08/01). Ideas?
Click to expand...
Click to collapse
Please take a screenshot of your software information
And the ota update screen

westwood24 said:
No this is stock boot image and with rtc.
Click to expand...
Click to collapse
Stock boot image has a different hash (SHA1: 74bd07510017b3e996e580d42b08cb3d1c022f38).
boot.img isn't related to recovery. I flashed the (real) stock boot.img and still have TWRP running. What means "rtc"?

Cloonix said:
Stock boot image has a different hash (SHA1: 74bd07510017b3e996e580d42b08cb3d1c022f38).
boot.img isn't related to recovery. I flashed the (real) stock boot.img and still have TWRP running. What means "rtc"?
Click to expand...
Click to collapse
Boot image in my downloads with (SHA1: 74bd07510017b3e996e580d42b08cb3d1c022f38, MD5: d101942135865580b75280b9ece767c1) is stock without any mods.
Boot image in the zip is modified to keep twrp (read the start post.)
i mean rct sry my bad.

@westwood24
Thank you, I will than just flash boot.img from your zipped rom since I am on stock 11i already to get rid of rct

westwood24 said:
Please take a screenshot of your software information
And the ota update screen
Click to expand...
Click to collapse
I ended up ignoring and it and disabling updates so it will be difficult to reproduce exactly. Basically, I was promoted to download an OTA of several hundred MB, which obviously didn't install due to the custom recovery. I remember the LG OTA being dated 08/01. It's the EU-market model.
Otherwise, the ROM works fantastically though I'm wondering whether to just flash a stock LG ROM and recovery to enable OTAs - unless you/OP plan on releasing new, flashable ZIPs with each official LG update?

westwood24 said:
Boot image in my downloads with (SHA1: 74bd07510017b3e996e580d42b08cb3d1c022f38, MD5: d101942135865580b75280b9ece767c1) is stock without any mods.
Boot image in the zip is modified to keep twrp (read the start post.)
i mean rct sry my bad.
Click to expand...
Click to collapse
Sorry for the confusion. I've downloaded "H87011i+Open+EU+(TWRP).zip" from your androidfilehost-account. I extracted the zip and hashed boot.img. SHA1-result: 28e86d637dceafd4108235392869a4f6195ce1d0
I understand that you modified the boot.img. But why? As i said... TWRP is not touched by flashing the boot.img. I've downloaded the 11i-kdz directly from LG and built my own zip (w/o any modification). So i wonder why my zip differs from yours.

Strange, even after flashing your boot.img from ROM zip file I still have rct enabled, can someone test this on their device and check output?
su
ps | grep rctd

Patch boot.img manually?
How is it possible to patch boot.img manually with twrp? Because sometimes it's not possible to find those ready zips on the internet, so it would be useful to know.

I'm on fulmics 4.2 right now. Can I just flash the zip file after doing the wipes to go back to stock or would it require LG UP ?

Elvenstar said:
I'm on fulmics 4.2 right now. Can I just flash the zip file after doing the wipes to go back to stock or would it require LG UP ?
Click to expand...
Click to collapse
you can just flash but you have to wipe data, system and cache.

Hi,
Im a litte bit new to this so bare with me.
I tried installing twrp and supersu to root my phone but it didnt work so I accidentily erased my OS..
Now im stuck in TWRP.
I tried "adb sideload" the stock zip but it said "cannot read the file". When I googled they suggested to use 64-bit adb instead.
Tried that too but then it just said "transfered 0x0".
What to do?

Solved. Please delete this Post. Thanks...

SIM card is not recognized

Hello
The mobile had the following error "Encryption unscuccessfull"
It was no longer possible to install a ROM.
Only after the in
mount and Storge Menu the partitions have been reformatted.
After that, the modem zip was still installed without success
Rome only runs the sim card is not recognized.
SIM card works in other mobile phone
Hardware error?
S III i9305
ClockworkMod Recovery V6.0.4.7
Rome
lineage-14.1
or
RR-N v5.8.5

@uzzoo If my reply sounds a bit "unstructired" I apologise but I'm not convinced if I completely grasp the whole issue.
In Settings => About phone, is the modem/baseband indicated by its version or does it states "unknown"?
I urgently suggest to replace your current recovery by TWRP 3.0.2-1! And please only use this version; any later one will again make trouble.
You are mentioning "Encryption unscuccessful", Did you try to encrypt your device? If I correctly remember RR (and I believe same applies to LOS) does not support encryption. Maybe @rodman01 can confirm?
Last but not least: The issue "SIM not recognised" was already reported several times in different threads and solutions provided. I assume your consent that I don't conduct the searches for you but I suggest to search these threads:
https://forum.xda-developers.com/ga...m-resurrection-remix-4-4-2-kitkat-v5-t2704828
https://forum.xda-developers.com/ga...resurrection-remix-4-4-2-kitkat-v5-1-t2950817
https://forum.xda-developers.com/ga...m-unofficial-lineageos-14-1-gt-i9305-t3542012

Yes encryption is not working with at least the latest RR versions on our phone.
Not sure whether it had been working on any not samsung stock based custom rom for the i9305. I never tested it or dived deeper in the topic to get it to work, so this might be not a very reliable post .

Have the phone with the error message encrypted.
Official LineageOS 14.1 Samsung Galaxy S III LTE GT-I9305
last version is running
modem / baseband will display "unknown"
Will continue with the following instructions.
1) Install TWRP:
TWRP 3.2.3-0 fails installing .zips here, 3.0.2-1 is fine.
https://dl.twrp.me/i9305/twrp-3.0.2-1-i9305.img.html
- Boot to bootloader (Power, Volume Down, Home)
As I'm running linux on my PC, I'm using heimdall for flashing:
- sudo heimdall flash --no-reboot --RECOVERY twrp-3.0.2-1-i9305.img
2) For a clean start, wipe everything in TWRP first:
- Boot to TWRP (Power, Volume Up, Home)
- Format data
- Mount everything but EFS and MicroSD, including System, not read-only
- Advanced wipe: Wipe everything but MicroSD card
- Reboot to download
3) Install stock ROM:
I found the current stock ROM here:
https://updato.com/firmware-archive-...r=desc&exact=1
At least for my country (Germany, DBT) the appropriate modem file ...UFOA1 is included!
- Boot to bootloader
- sudo heimdall flash --no-reboot --BOOTLOADER sboot.bin --TZSW tz.img --BOOT boot.img --TOMBSTONES tombstones.img --CACHE cache.img --RADIO modem.bin --RECOVERY recovery.img --SYSTEM system.img --HIDDEN hidden.img
4) Boot the stock Android!
Baseband did not work for me as long as I directly continued without booting Android.
So let Android boot until it says welcome (no need to continue with the initial setup).
5) Install TWRP again
- Boot to bootloader
- sudo heimdall flash --no-reboot --RECOVERY twrp-3.0.2-1-i9305.img
6) Install files in TWRP:
- Boot to TWRP
- Copy files to external SD-Card:
LineageOS from http://buildyourownandroid.selfhost..../daily-builds/
Open Gapps from https://opengapps.org/ (ARM, 7.1, pico)
system(sim_support).zip from https://forum.xda-developers.com/sho...&postcount=800
su (arm) 14.1 from https://download.lineageos.org/extras
- Wipe Data, Cache and Dalvik
- Install all the four files in the order given above
The installation runs fine besides two "E:unknown command [log]" messages.
7) Reboot to system, everything is working fine.
Click to expand...
Click to collapse

Have the phone with the error message encrypted.
Official LineageOS 14.1 Samsung Galaxy S III LTE GT-I9305
last version is running
modem / baseband will display "unknown"
Will continue with the following instructions.
1) Install TWRP:
TWRP 3.2.3-0 fails installing .zips here, 3.0.2-1 is fine.
https://dl.twrp.me/i9305/twrp-3.0.2-1-i9305.img.html
- Boot to bootloader (Power, Volume Down, Home)
As I'm running linux on my PC, I'm using heimdall for flashing:
- sudo heimdall flash --no-reboot --RECOVERY twrp-3.0.2-1-i9305.img
2) For a clean start, wipe everything in TWRP first:
- Boot to TWRP (Power, Volume Up, Home)
- Format data
- Mount everything but EFS and MicroSD, including System, not read-only
- Advanced wipe: Wipe everything but MicroSD card
- Reboot to download
3) Install stock ROM:
I found the current stock ROM here:
https://updato.com/firmware-archive-...r=desc&exact=1
At least for my country (Germany, DBT) the appropriate modem file ...UFOA1 is included!
- Boot to bootloader
- sudo heimdall flash --no-reboot --BOOTLOADER sboot.bin --TZSW tz.img --BOOT boot.img --TOMBSTONES tombstones.img --CACHE cache.img --RADIO modem.bin --RECOVERY recovery.img --SYSTEM system.img --HIDDEN hidden.img
4) Boot the stock Android!
Baseband did not work for me as long as I directly continued without booting Android.
So let Android boot until it says welcome (no need to continue with the initial setup).
5) Install TWRP again
- Boot to bootloader
- sudo heimdall flash --no-reboot --RECOVERY twrp-3.0.2-1-i9305.img
6) Install files in TWRP:
- Boot to TWRP
- Copy files to external SD-Card:
LineageOS from http://buildyourownandroid.selfhost..../daily-builds/
Open Gapps from https://opengapps.org/ (ARM, 7.1, pico)
system(sim_support).zip from https://forum.xda-developers.com/sho...&postcount=800
su (arm) 14.1 from https://download.lineageos.org/extras
- Wipe Data, Cache and Dalvik
- Install all the four files in the order given above
The installation runs fine besides two "E:unknown command [log]" messages.
7) Reboot to system, everything is working fine.
Click to expand...
Click to collapse

uzzoo said:
Have the phone with the error message encrypted.
Official LineageOS 14.1 Samsung Galaxy S III LTE GT-I9305
last version is running
modem / baseband will display "unknown"
Will continue with the following instructions.
Click to expand...
Click to collapse
Why didn't you accept the advice I already provided here? You are using a TWRP version that most likely leads to problems.

I do not have a twrp version on it
There is still an old ClockworkMod Recovery V6.0.4.7
The mobile phone has been running since 2016 with no problems
Had already tried the twrp on it.
Currently under Win10 / Linux

uzzoo said:
I do not have a twrp version on it
There is still an old ClockworkMod Recovery V6.0.4.7
The mobile phone has been running since 2016 with no problems
Had already tried the twrp on it.
Currently under Win10 / Linux
Click to expand...
Click to collapse
I can offer you to send me your phone with DHL or something. Ulm is not that far away from me, around 120 KM. Other possibility if you want to make a trip into the wonderful Allgäu you can come in for a coffee or 2 and we will have a look at your device. Last: I maybe can arrange a date with my sister who is living also in the near of Ulm. Btw I lived in Neu-Ulm for around 20 years . On Sunday the 4th of August I will visit my sister at their home, so that I can put the mobile from her. Or maybe we find a possibility to meet each other at that day and you pass me your device personally. No promise that I can solve the problem, but maybe it is worth a try.

uzzoo said:
I do not have a twrp version on it
There is still an old ClockworkMod Recovery V6.0.4.7
The mobile phone has been running since 2016 with no problems
Had already tried the twrp on it.
Currently under Win10 / Linux
Click to expand...
Click to collapse
Adding to @rodman01 generous offer that is most likely the most proper solution due to the vicinity of Ulm to his home, if you have plans to visit the most westerly part of Germany in the near future, I'd also be personal available to assist.
#######
And if you rather prefer to use the German language, just let me know and I'd place the German translation below the English version. You can also use Google Translate; just place the Englisg translation above your German post. Although German is my mother tongue, just wanted to show you how it looks like.
*****
Translated by Google Translate:
Und wenn Sie lieber die deutsche Sprache verwenden möchten, lassen Sie es mich einfach wissen und ich platziere die deutsche Übersetzung unter der englischen Version. Sie können auch Google Translate verwenden. Platzieren Sie einfach die englische Übersetzung über Ihrem deutschen Beitrag. Obwohl Deutsch meine Muttersprache ist, wollte ich Ihnen nur zeigen, wie es aussieht.
rodman01 said:
I can offer you to send me your phone with DHL or something. Ulm is not that far away from me, around 120 KM. Other possibility if you want to make a trip into the wonderful Allgäu you can come in for a coffee or 2 and we will have a look at your device. Last: I maybe can arrange a date with my sister who is living also in the near of Ulm. Btw I lived in Neu-Ulm for around 20 years . On Sunday the 4th of August I will visit my sister at their home, so that I can put the mobile from her. Or maybe we find a possibility to meet each other at that day and you pass me your device personally. No promise that I can solve the problem, but maybe it is worth a try.
Click to expand...
Click to collapse