TWRP Recovery 2.8.6.0 for LG L7II
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or any other damage made to your device. Please
* do some research if you have any concerns about features included in this
* RECOVERY before flashing it! YOU are choosing to make these modifications,
* and if you point the finger at me for messing up your device,
* I will laugh at you.
*/
In this thread you can find:
Post#1:
1. Presentation
2. Changelog
3. Known bugs + fixes
Post#2:
1. Flashing instruction
2. Thanks
3. Donator Hall of Fame
4. Download links
Post#3:
1. Tutorial on how to make ADB work on windows (with or without MTP)
2. Images of the recovery
1. Presentation:
TeamWin Recovery Project – or TWRP for short – is a fully touch-based custom recovery that was initially developed for Nexus devices, but has since been made available for countless other smartphones and tablets as well, in form of both official and third-party builds.
2. Changelog:
Code:
[U]07.08.2015 - Twrp 2.8.7.0[/U]
Updated to latest Twrp
Added IMEI back-up
[U]12.06.2015 - Twrp 2.8.6.0[/U]
Settings storage is by default External SD
Ext-sd will not be wiped on factory reset (even if the text says so; ignore it)
You have all 3 partitions (internal, external, ext-sd) in MTP now
Updated to latest TWRP 2.8.6.0 source
[U]06.01.2015 - Stable2[/U]
improved code a little
disabled things that are not used
reduced maximum brightness
added Qcom time fix
NEW: added support for sd-ext (2nd partition on sdcard)
[U]02.01.2015 - Working Internal[/U]
Read the warnings (in RED) in the 2nd post.
Internal storage is working now xD
[U]25.12.2014 - Updated to latest TWRP 2.8.3.0[/U]
[U]19.11.2014 - Final release[/U]
- bugs: none
Aroma Fm inverted is not because of recovery.
Not mounting internal is not because of recovery and will not be added because you can mess up your data partition losing all data (our internal is in data/media)
We have full working brightness and screen timeout
[U]10.11.2014 - Beta 1[/U]
- bugs:
after entering screen timeout mode the led backlight won't turn on again
- fixed bugs:
messed up display
flipped screen
unresponsive touch screen
partition problems
[U]09.11.2014 - Closed Alpha 2 - No public download[/U]
- bugs:
flipped screen
unresponsive touch screen
partition problems
after entering screen timeout mode the led backlight won't turn on again
- fixed bugs:
messed up display
[U]05.11.2014 - Closed Alpha 1 - No public download[/U]
- first release
- bugs:
messed up display
flipped screen
unresponsive touch screen
partition problems
after entering screen timeout mode the led backlight won't turn on again
3. Known bugs:
NONE!
1. Flashing instruction:
METHOD 1:
*OUTDATED: Just open the zip from last version and copy that recovery.img if you want to use this.
Copy the "recovery.img" from download to the root of the SD card.
Code:
1. With terminal emulator or using adb do this:
2. adb shell
3. su
4. dd if=/storage/external_SD/recovery.img of=/dev/block/mmcblk0p17
METHOD 2:
Download the version you like (the zip) and flash it in any recovery.
VERY IMPORTANT: EVERYTIME YOU FLASH TWRP AGAIN GO TO SETTINGS AND RESET DEFAULTS.
THE DEFAULT STORAGE MIGHT BE INTERNAL STORAGE PRESS ON THE PLACE THAT SAYS STORAGE: INTERNAL STORAGE AND CHANGE TO EXTERNAL STORAGE IF YOU WANT TO USE THAT (TWRP will remember the choice).
IF WINDOWS RECOGNIZES THE INTERNAL STORAGE IT WILL TRY TO FORMAT IT TO USE IT (this is because of the ext4 extention). DO NOT FORMAT OR YOU LOSE YOUR INTERNAL STORAGE DATA. LINUX DOESN'T HAVE ANY PROBLEM.
2. Thanks:
All Omni and TWRP team.
@Dees_Troy
The IRC channel for TWRP.
3. Donator Hall of Fame:
@vlmaxx - huge thank you man! ^.^
4. Download link:
TWRP_2.8.7.0_L7II.zip
Old:
TWRP_2.8.6.0_L7II.zip
Any kind of mirroring, repacking, uploading this files or files that come from this files on other websites/forums is not allowed. If you want guys on other forums to get this, give them the link to this. Thanks. Please respect my work and do not reupload this files.
How to make ADB to work on Windows:
adb-setup-1.4.2.exe: http://tinyurl.com/qca8abd
LG Drivers: http://tinyurl.com/l3mgf49
1. Delete all LG Drivers you have and all related to LG (Pc suite or anything else) and restart PC.
2. Install the LG Drivers from the rar and also the installer for ADB answering Y, Y, Y and follow the on screen driver installer.
3. Get in recovery and go under Mount and disable MTP if it is enabled. Connect USB. You will get this. Open device manager and you will find that our pictures are alike.
{
"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"
}
4. Right click the yellow triangle icon and right-click it choosing Update Driver Software. You get this.
5. Click the down option. You get this.
6. Click the Let me pick from a list option. You get this.
7. Select ADB Interface and press Next. You get this.
8. Scroll down selecting the LGE Mobile Adb. Press Next. You get this.
9. Press Yes and then Close and you are done.
Proof working recognized with MTP off in Recovery and Sideload and last picture with MTP on (recognizing the sdcard).
Hit thanks please if this helped you. Have a nice day.
Good job I will test this in the night
P.S. I can install this on cwm??
sirion123 said:
Good job I will test this in the night
P.S. I can install this on cwm??
Click to expand...
Click to collapse
Hmm maybe if i make a flashable zip though I have seen ppl prefere to flash it via fastboot. We don't have fastboot so just flash it like i said. It's easy ^.^..
EDIT: NVM made the cwm flashable zip.
Ok. Maybe I'll wait for the others and then install
sirion123 said:
Ok. Maybe I'll wait for the others and then install
Click to expand...
Click to collapse
Just flash that with CWM it's safe it won't destroy your data or system will catch on fire it is tried on my own device.
I install this and this is very good work! But when I reboot to system screen flipped at the moment. I found this one bug
sirion123 said:
I install this and this is very good work! But when I reboot to system screen flipped at the moment. I found this one bug
Click to expand...
Click to collapse
If you like it press the THANKS BUTTON that is in the bottom right of the post. I know about this bug it is normal and it's not really a bug blame lg ^.^. badly mounted screen for this models. This bug won't interfere with anything ^.^ You can see it just when you close the recovery.
Excellent job! It's works on P713 KK CIS!
Themes are applied successfully!
The option "Disable MTP" disables ADB mode too. - SOLVED!
UMS mode for external SD is not supported.
AROMA FM still inverted.
We are waiting for the final version and fixes! Good luck!
Thx, sir. Its work on my LG P713 (4.1.2)
the_vanya1 said:
Thx, sir. Its work on my LG P713 (4.1.2)
Click to expand...
Click to collapse
You are very welcome my friend. Giving back the work haha. Respect to you when i was on 4.1.2 I used your custom rom. EPIC. Respect.
And recovery is perfectly compatible with nandroid manager...
maxx_hr said:
And recovery is perfectly compatible with nandroid manager...
Click to expand...
Click to collapse
Thanks for letting people know.
TWRP Recovery
christi9503 said:
Thanks for letting people know.
Click to expand...
Click to collapse
Please tell me whether it is possible to install on the LG P715 Dual.
vlmaxx said:
Please tell me whether it is possible to install on the LG P715 Dual.
Click to expand...
Click to collapse
Not tested on P715 but it should work. 99,9% it will work my friend. Also no chance you will manage to hard brick it just by flashing. I did not include preloader and bootloader partitions. At most a soft brick but not even that. Just flash it.
EDIT: @vlmaxx Report after flashing please. But for sure it will boot.
TWRP
christi9503 said:
Not tested on P715 but it should work. 99,9% it will work my friend. Also no chance you will manage to hard brick it just by flashing. I did not include preloader and bootloader partitions. At most a soft brick but not even that. Just flash it.
EDIT: @vlmaxx Report after flashing please. But for sure it will boot.
Click to expand...
Click to collapse
Ok. I will try tomorrow to try. Then I will unsubscribe.
TWRP
christi9503 said:
Not tested on P715 but it should work. 99,9% it will work my friend. Also no chance you will manage to hard brick it just by flashing. I did not include preloader and bootloader partitions. At most a soft brick but not even that. Just flash it.
EDIT: @vlmaxx Report after flashing please. But for sure it will boot.
Click to expand...
Click to collapse
Sorry, I'm not good at English. Lost your message, so I answer here.
Sew through CWM Recovery. Starts but tach screen almost does not work or is not adequate. Reacts only INSTALL and offers mount, and then nothing can be done. Rollback on old CWM.
Forgot to specify: I have 4.1.2. Maybe that's why is not working?
vlmaxx said:
Sorry, I'm not good at English. Lost your message, so I answer here.
Sew through CWM Recovery. Starts but tach screen almost does not work or is not adequate. Reacts only INSTALL and offers mount, and then nothing can be done. Rollback on old CWM.
Forgot to specify: I have 4.1.2. Maybe that's why is not working?
Click to expand...
Click to collapse
Nope that is not the case. Think it's the touch drivers can be different or smth. Please make a video place on youtube. I'll make a different build with p715 kernel.
TWRP
christi9503 said:
Nope that is not the case. Think it's the touch drivers can be different or smth. Please make a video place on youtube. I'll make a different build with p715 kernel.
Click to expand...
Click to collapse
Sorry, but it's all too complicated for me. Years and brains are not the same .... unfortunately. In any case, thank you very much for your help.
Related
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
{
"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"
}
Introduction:
Team Win Recovery Project 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.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Decryption of /data
Easy selection of internal/external storage
Portal Link: http://www.xda-developers.com/android/twrp-recovery-now-available-for-the-xperia-u-p-go-and-sola/
Click to expand...
Click to collapse
Installation:
since our device developers are constantly trying to fix bugs, they are always changing something in init.*.rc files for testing. For this reason I can't post a regular boot.img file because it won't work. For now, I've created a script that will take all init.*.rc files from current rom's boot.img and then compile new boot.img with TWRP inside it.
Note : For Rooted & Unlocked Bootloader Only
Note : For 4.4 ROM (should work on older version of android upto 4.1). I don't own XP. So please provide feedback
1) Download the latest zip file.
2) Extract it in a folder and place your current rom's boot.img inside that folder. (it must be named boot.img)
3) Connect your phone with PC. (adb must be working)
4) Open your command line and cd to that folder
5) For linux users, type
Code:
chmod 755 run_me.sh
./run_me.sh
For windows users, type
Code:
run_me.bat
new boot.img file will be created in the current directory named new_boot.img. Power off your phone and flash the boot image.
Code:
fastboot flash boot new_boot.img
Theming:
Information on TWRP 2 Theming - http://teamw.in/project/twrp2themers
To ROM makers
if you include it in your ROM, please give proper credits cause I've spent almost a month trying to port this.Thanks.
Download
recovery_install_XP.zip - 6.43 MB
Source
TWRP source -> https://github.com/omnirom/android_bootable_recovery
Credits
all teamwin members, especially @Dees_Troy for giving me constant advice
@munjeni for his support and answering all my questions
@percy_g2 for providing gyroscope fix in touch
Changelog 21/03/2014
booted
full touch working
adb working
usb mass storage working
fixed show battery capacity & charging status (+ icon next to percentage)
reboot to bootloader/recovery working (from twrp menu)
reboot to bootloader/recovery working (from rom)
battery led to indicate battery status
brightness slider working (under settings=>screen in twrp)
F.A.Q
1) Are CWM backups compatible with TWRP ?
Ans: CWM backups are not compatible - please make a fresh backup in TWRP as soon as you have flashed it.
edit: kernel not supported, stock rom, anyway thanks bro, good job!
miui
MIUI 5 (4.2.2) works +++
Confirmed working on SlimKat 4.4.2 by @DroidModderXtreme. Really good job man!
Sent from my Xperia P using XDA Premium 4 mobile app
kosmos-2011 said:
MIUI 5 (4.2.2) works +++
Click to expand...
Click to collapse
kopter36 said:
Confirmed working on SlimKat 4.4.2 by @DroidModderXtreme. Really good job man!
Sent from my Xperia P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Pls confirm if everything is working according to changelog. Thanks
Well, noob Coder Here's It
booted
full touch working
adb : I dont know how to check
usb mass storage: working super fine
battery percentage is showing... as it is showing in my phone 14%+(guess thatz it)
reboot to bootloader/recovery working (from twrp menu) = working well
reboot to bootloader/recovery working (from rom) =working
battery led to indicate battery status=working
brightness slider working well
Buddy, itz cool to see someone from my country helping here. Thnx for your effort.
MIUI 4.2.2
booted yes
full touch working yes
adb working ? yes
usb mass storage working ? yes
fixed show battery capacity & charging status (+ icon next to percentage) yes
reboot to bootloader/recovery working (from twrp menu) ? yes
reboot to bootloader/recovery working (from rom) ?
battery led to indicate battery status ? yes
brightness slider working (under settings=>screen in twrp) ? yes
Who can make zip for recovery for CM11?
Sent from my Xperia P using xda premium
Xperia_Fans said:
edit: kernel not supported, stock rom, anyway thanks bro, good job!
Click to expand...
Click to collapse
you're on locked BL ? If not, it should work. Did you try it?
kaziupal said:
Buddy, itz cool to see someone from my country helping here. Thnx for your effort.
Click to expand...
Click to collapse
anytime
after flashing this kernel root doesnt seem to be working on miui 4.2.2
work parfectly in stock rom based ( dark) with nemsis v6.3 as original karnel
i thinks that is better than cmw
thanks a lot
Using it on latest carbon but fix permission failed will provide logcat later
Sent from my Xperia P using Tapatalk
ibudanov said:
Who can make zip for recovery for CM11?
Sent from my Xperia P using xda premium
Click to expand...
Click to collapse
Not sure it's possible, since the boot.img is compiled a script that runs on the device.
I suppose it would be possible to do it by running the script on an XP with CM11 installed then using the compiled boot.img to create a flashable ZIP.
I'm going to try do this once I get to my computer.
Are you using Percy's CM11?
not working
i have an XP with the stock rom .100, the stock kernel and Unlocked Bootloader. I followed the instructions but it failed.
here's a screenshot of cmd and if you see something wrong in it tell me plz.
Thanks for your great work !!
big-A said:
i have an XP with the stock rom .100, the stock kernel and Unlocked Bootloader. I followed the instructions but it failed.
here's a screenshot of cmd and if you see something wrong in it tell me plz.
Thanks for your great work !!
Click to expand...
Click to collapse
check your folder, you must have a new file: "new_boot.img" and after fastboot it via flashtool
no
dastane said:
check your folder, you must have a new file: "new_boot.img" and after fastboot it via flashtool
Click to expand...
Click to collapse
there's no new_boot.img in the folder it's clear in the cmd screenshot that the process failed...
did you copied your curent karnel file in this folder and rename it into " boot.img" as its said in the OP??
djkk16 said:
after flashing this kernel root doesnt seem to be working on miui 4.2.2
Click to expand...
Click to collapse
+1
no root acces
now i'm using Liquid smooth based 4.4.2
the probleme is from the original karnel not from this recovry; waiting for karnel fix and i will re flash twrp
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
Unlocking Bootloader (Required)
* Because unlocking the bootloader? *
Bootloader bootloader is present on any Linux (Android) and Windows system.
Every manufacturer makes its locked bootloader to "not let any user device end his".
The LG , besides the bootloader lock, removes the command to unlock and still does not tell how to unlock the bootloader, then the only way is to burn an edited bootloader, that being the case.
Via App - thanks @ElDainosor and @vuminhduc_1998
Follow instructions in topic.
Support: All LG Optimus L3 II Variants
How to get into recovery via buttons:
Turn off your cell phone and do so, press the "Volume -" + "Power", after a second tight press "Home" and when vibrate loose and everyone quickly and repeatedly press the "Home". Will need a few tries until you get the delicacy, because that's the base.
Next Update:
TWRP with support to sd-ext (by @Cobmaster)
TWRP 2.8.6.0 -> TWRP 2.8.7.0
The CWMA and TWRP when I choose install zip from sdcard it displays the folder "/sdcard/0/" instead of "/sdcard/"
Sorry for my english I hope you understand what I mean xd
This is not bug
This folder is the default location, the CWMA you can change the location in recovery settings
thanks... It works on E425g????
now im trying to build something like that, im just learning so its hard even so i know about linux and building but it a little difernt...
Has not yet been tested, but I suppose that works.
It's hard but if you insist you can
TWRP works, but i cant install some packages like cyclone kernel, there is a problem in updater-script.
obrigado!!!
ensarman said:
TWRP works, but i cant install some packages like cyclone kernel, there is a problem in updater-script.
obrigado!!!
Click to expand...
Click to collapse
But you only tested the TWRP?
Test the CWM Advanced
Caio99BR said:
But you only tested the TWRP?
Test the CWM Advanced
Click to expand...
Click to collapse
lol, ok i will, but later, when i go home
Caio99BR said:
But you only tested the TWRP?
Test the CWM Advanced
Click to expand...
Click to collapse
olá
I have tested the CWM touch and it works perfectly until now I do not test everything buy it works well..
besides I have written a tutorial en spanish at my blog, if you want to check it: I will leave the link:
http://supranet.org/sistemas-operativos/twrp-y-cwm-touch-recovery-y-para-lg-optimus-l3-ii/
thanks
E430 Test
Caio99BR said:
Hello people, today I came to bring the main Recovery's ported and tested by me
TWRP - TeamWinRecoveryProject (by TeamWin) - Touch
CWM - ClockworkMod (by Koush) - Non-Touch
CWM Advanced Edition - 6 PhilZ Touch Recovery (by Phil3759) - Touch
Unlocking Bootloader (Required)
* Because unlocking the bootloader? *
Bootloader bootloader is present on any Linux (Android) and Windows system.
Scheme android bootloader.
{
"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"
}
Every manufacturer makes its locked bootloader to "not let any user device end his" meaningless thing to say.
The LG miserable, besides the bootloader lock, removes the command to unlock and still does not tell how to unlock the bootloader (already tried to communicate how to unlock), then the only way is to burn an edited bootloader, that being the case.
Unlocking the bootloader
Unzip emmc_appsboot.rar and place the file on the SD card
Code:
adb pull emmc_appsboot.bin /sdcard/
Give permissions Super User
Code:
su
Command for Flash
Code:
dd if=/sdcard/emmc_appsboot.bin of=/dev/block/mmcblk0p5
Commands to install the CWM:
Put the file on the sdcard
Code:
adb push cwm.img /sdcard/
Give permissions Super User
Code:
su
Command for Flash
Code:
dd if=/sdcard/cwm.img of=/dev/block/mmcblk0p17
Restart in Recovery
Code:
reboot recovery
Commands to install the TWRP:
Put the file on the sdcard
Code:
adb push twrp.img /sdcard/
Give permissions Super User
Code:
su
Command for Flash
Code:
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p17
Restart in Recovery
Code:
reboot recovery
Commands to install CWM Advanced Edition:
Put the file on the sdcard
Code:
adb push cwma.img /sdcard/
Give permissions Super User
Code:
su
Command for Flash
Code:
dd if=/sdcard/cwma.img of=/dev/block/mmcblk0p17
Restart in Recovery
Code:
reboot recovery
Note:
Tested only on E435 - Lg Optimus L3 Dual II
If someone on the other testing L3 II, leave feedback
How to get into recovery via buttons:
Turn off your cell phone and do so, press the "Volume -" + "Power", after a second tight press "Home" and when vibrate loose and everyone quickly and repeatedly press the "Home". Will need a few tries until you get the delicacy, because that's the base.
Downloads:
ADB - AndroidFileHost - (For PC)
Terminal Emulator - Play - (For Mobile)
Bootloader - AndroidFileHost - (Unlock the Bootloader)
TWRP (01/10/2014) - AndroidFileHost - (twrp.img)
CWM (10/01/2014) - AndroidFileHost - (cwm.img)
PhilZ CWM (01/10/2014) - AndroidFileHost- (cwma.img)
Credits:
IGGYVIP - For unlocked BootLoader :good:
hugo.gabriel999 - For Inspiration
TeamWin - For TWRP
Koush - For CWM
Phil3759 - For A Best And Advanced CWM
Click to expand...
Click to collapse
Hi, I tested PhilZ Touch and TWRP on LG E430 they work very well
Mikk123 said:
Hi, I tested PhilZ Touch and TWRP on LG E430 they work very well
Click to expand...
Click to collapse
Thanks!
Cayo what is the cwms???
ensarman said:
Cayo what is the cwms???
Click to expand...
Click to collapse
It is the CWM however you can use the touch to do the movements, it's good because you stop using the physical buttons.
Besides being easier.
Ok i will tr it, it works with the. New edify syntax like set metadata instead of set permission?
ensarman said:
Ok i will tr it, it works with the. New edify syntax like set metadata instead of set permission?
Click to expand...
Click to collapse
Yes, I have implemented SELinux support that adds support to new syntax.
All these recoverys made by me already have this support. There were already implemented in the second build, because in the first gave installation error (CM 11 test builds) due to lack of SELinux support.
Caio99BR said:
Yes, I have implemented SELinux support that adds support to new syntax.
All these recoverys made by me already have this support. There were already implemented in the second build, because in the first gave installation error (CM 11 test builds) due to lack of SELinux support.
Click to expand...
Click to collapse
great!!! thanks man
These recoverys are ready for CM11!
And who knows
I will delete the CWM and leave only the CWMS because it is better and simpler
Status
Updated CWM and CWM PhilZ Edition, now they are compatible with the CyanogenMod 11 (which will be released soon), for those who want to test will be necessary to update the recovery to the latest version.
I did not update the TWRP because it gave an error in which I could not solve.
https://www.paypalobjects.com/en_US/i/btn/btn_donateCC_LG.gif
{
"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"
}
After 2 months of work this is finally booting on our device @AnBro-ID can confirm it (he is the first to try it, congratz). No device atm so I am just getting thread ready for when my device will come from warranty.
And oh I forgot after this is bug free. We are getting Philz Touch also for the party to be complete. Please support me. Thanks to you all. You are amazing.
CWM Touch Recovery 6.0.5.1 for LG L7_2
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or any other damage made to your device. Please
* do some research if you have any concerns about features included in this
* RECOVERY before flashing it! YOU are choosing to make these modifications,
* and if you point the finger at me for messing up your device,
* I will laugh at you.
*/
In this thread you can find:
Post#1:
1. Presentation
2. Changelog
3. Known bugs + fixes
Post#2:
1. Flashing instruction
2. Thanks
3. Donator Hall of Fame
4. Download links
1. Presentation
What is ClockworkMod? ClockworkMod Recovery (CWM) is a replacement recovery option for Android devices, made by Koushik "Koush" Dutta.
2. Changelog
Code:
[B]04-01-2015 - Initial release (closed alpha)[/B]
bugs that are mentioned in bug section
Code:
[B]04-01-2015 - Beta 1[/B]
fixed all bugs in the bug section but adb sideload
sometimes device will reset or screen will flash during start-up if you reboot to system (from recovery)
Code:
[B]12-01-2015 - Release 1[/B]
fixed adb sideload
forced another offset in memory to solve the rebooting problem (screen might flash a little though)
3. Known bugs
- image is inverted (need to do an 180 degree rotation in the framebuffer) fixed, HELL YEAH!
- image jumps when you press buttons (need to investigate when I get my device)
- external_sd is not mounted
- image too small (not really a bug but I need a device to see what can I do)
- adb is not working
- power button is recognized as home button -> well not a bug this is how buttons are mapped, at first I understood power button is switched but no, both buttons can cofirm, all good.
- adb sideload not working
Not really bugs (I will still mention them for you to not worry):
I had to force offsets into memory for recovery to boot and also I had to mess with the framebuffer bitmap (the thing that makes image into memory). If you reboot from recovery to system or if you boot in recovery etc you might experience screen flashing for some seconds. Ignore it. It won't do harm or do any damage just some offsets that are conflicting (for example recovery with kernel).
The bugs written up are the ones that I am aware of. Do not say that the things mentioned are not working since I will just ignore it (I know it and will fix when I have time/motivation and so on, if it can be fixed).
Feel free and I encourage you to report bugs that I am not aware of. Please give a detailed view of the bug. Not just not working and similar things. Post screens/logs all taht can be useful.
Project state: STABLE
If you have any bugs submit them here, in this forum. And don't say hey it's not working or things like that. Give a detailed review of the problem.
I worked a lot for this recovery to work. If you can afford to get me a coffee I would love it. Donation link is at my avatar ^.^. Thanks. Also remember to hit the Thanks button please.
Get my coffee right here, right now <3:
Created 04-01-2015
Last Updated 12-01-2015
1. Flashing instruction
Method 1:
*OUTDATED: Just open the zip from last version and copy that recovery.img if you want to use this.
Copy the "recovery.img" from download to the root of the SD card.
Code:
1. With terminal emulator or using adb do this:
2. adb shell
3. su
4. dd if=/storage/external_SD/recovery.img of=/dev/block/mmcblk0p17
Method 2:
Download the version you like (the zip) and flash it in any recovery.
On Windows your device might get detected as Unknown. You need to set the driver from device manager manually. Choose LGE adb interface ot adb interface.
2. Thanks
ClockWorkMod
@Koush
3. Donator Hall of Fame
4. Download links
Newest:
CWM_6.0.5.1_P710_Release1
Older:
CWM_6.0.5.1_P710_Beta1
If you find this useful really PRESS THE THANKS! BUTTON! It take literally 1 second. Why wouldn't you press it?
Any kind of mirroring, repacking, uploading this files or files that come from this files on other websites/forums is not allowed. If you want guys on other forums to get this, give them the link to this. Thanks. Please respect my work and do not reupload this files.
You can take this as #3 reserved if I need more space. @AnBro-ID is helping me to debug. He is really patient. Fixing bug after bug. You will get the first release when I am managing to rotate the screen. That is the only graphical problem that's let. I fixed the jumping when touching the screen. Have a great night.
EDIT: it will take a while because I need to reverse buffer (for reversed image). Managed to make code for it but only half of screen is inverted... Bleah.
Well yeah just to keep you updated. After a hell of a work (around 20 builds) and a lot of testing by @maxx_hr and @AnBro-ID (which I want to thank a lot) screen is finally rotated (well it was in 5 pieces and 2 colors) haha. That is fixed now. Release is very soon. Buy me the cookies. <3.
christi9503 said:
Well yeah just to keep you updated. After a hell of a work (around 20 builds) and a lot of testing by @maxx_hr and @AnBro-ID (which I want to thank a lot) screen is finally rotated (well it was in 5 pieces and 2 colors) haha. That is fixed now. Release is very soon. Buy me the cookies. <3.
Click to expand...
Click to collapse
Guys, please enable cookies in your browsers...
Digdis said:
Guys, please enable cookies in your browsers...
Click to expand...
Click to collapse
Yeah but cookies are good with coffee. Just joking. Serious things.
Screen fixed (fully working), same for swipe
Adb working
External_sd and extended partition on sd are now mounting.
All issues but the power recognized as menu key are working (the bugs I know of). Don't say heey that's not working it will piss me off. I know and I need to create a custom recovery keymapping. In a later release. Tomorrow evening this is going with full power here haha. Join the party !!! Good night for now.
As I promised. It's uploaded. Take care. Good night and keep it safe!
christi9503 said:
As I promised. It's uploaded. Take care. Good night and keep it safe!
Click to expand...
Click to collapse
Downloaded & tested, working nice and smooth, just awesome!
Great job, keep it up for CM!!!
work on 715?
Does it have the Fix root option? Thats the only reason I returned from TWRP to riskey CWM.
bullika said:
work on 715?
Click to expand...
Click to collapse
Read the title my friend. Of course it will work (but sure better ask, way safer<3). This should work on any L7_2 model. That means p710 p712 p715 etc.
KWG V2 said:
Does it have the Fix root option? Thats the only reason I returned from TWRP to riskey CWM.
Click to expand...
Click to collapse
I don't know why would you need a fix root option. TWRP itself has an option to fix root on your phone. TWRP is way better than normal CWM imo. I don't have a device I didn't test myself. If the source code (so CWM source) has this option it should be present. Try it yourself.
Solved adb sideload in RELEASE 1 (updated in the second post). Also solved the problem where the device might restart after restarting to system from recovery. This is the last release of CWM most likely. Cya.
christi9503 said:
Solved adb sideload in RELEASE 1 (updated in the second post). Also solved the problem where the device might restart after restarting to system from recovery. This is the last release of CWM most likely. Cya.
Click to expand...
Click to collapse
Cheers for your efforts mate. AFAIK, CWM development has stopped, right?
Since this version is kind of a fully working one with all necessary and possible features going well, it is stopped. I'm also very grateful for this CWM.
99 Downloads and 13 Thanks. It is so damn nice to work your ass off and see how people are thankful for your hard work *sarcasm, a lot*
Guys i can't find Mount USB Storage. How can i do that ?!!
christi9503 said:
99 Downloads and 13 Thanks. It is so damn nice to work your ass off and see how people are thankful for your hard work *sarcasm, a lot*
Click to expand...
Click to collapse
Try to ignore. Probably most people so arranged: Set it and forget it worked.
Thanks . Runs up nicely ; )
Paweeloss0707 said:
Thanks . Runs up nicely ; )
Click to expand...
Click to collapse
You are very welcome. Enjoy.
End of support for this and also end of development (already the latest version). This is getting closed. PEACE OUT!
*** Disclaimer
Code:
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Please do some research if you have any concerns about the instructions or the linked things before doing anything!
YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you and I promise, I will!
Introduction
I decided I wanted a more up-to-date CM11 build, so here it is, a new build of LineageOS 11, for D605!
Images
{
"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"
}
Features
* Quite default LineageOS 11 but with USB OTG and offline charging
Installation instructions
* Under construction
Changelog
* Creating once finished
Downloads
Checksums:
* Uploading once finished
Download
* Uploading once finished
Sources
* https://github.com/Avamander/android_device_lge_d605
* https://github.com/Avamander/android_kernel_lge_d605
FAQ
* Under construction
Thanks To/Credits
Code:
* Varcain
* Puresoul_CZ
So, let me know if you're even interested.
XDA:DevDB Information
LineageOS 11 for D605, ROM for all devices (see above for details)
Contributors
Avamander, Varcain, Puresoul_CZ
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: LineageOS
Version Information
Status: Abandoned
Created 2017-09-25
Last Updated 2020-07-04
Planned:
* Fix to reallow XPosed
Thanks Avamander! I'll test your ROM asap! Thank you again for your efforts!
ps: is the new build including the WiFi CRAK fix?
ps2: do you have any resource where to find any guide to compile it?
thePanz said:
Thanks Avamander! I'll test your ROM asap! Thank you again for your efforts!
ps: is the new build including the WiFi CRAK fix?
ps2: do you have any resource where to find any guide to compile it?
Click to expand...
Click to collapse
About CRACK, haven't checked, not sure a patch has been released for LOS11, if it has after the build date, let me know and I'll rebuild it.
I used the this https://wiki.lineageos.org/devices/d855/build but replaced d855 in commands with d605 and manually downloaded the sources to the according folders.
@Avamander: I tried to install your LineageOS ROM on top of a CM11 (by Varchain, the v11 release), but I get a "Status 7" error.
The error reports "set_metadata_recursive: some changes failed"
Checked the MD5 of the ZIP file and it is correct, both on my PC and on the SD.
Can you help me with the installation?
thePanz said:
@Avamander: I tried to install your LineageOS ROM on top of a CM11 (by Varchain, the v11 release), but I get a "Status 7" error.
The error reports "set_metadata_recursive: some changes failed"
Checked the MD5 of the ZIP file and it is correct, both on my PC and on the SD.
Can you help me with the installation?
Click to expand...
Click to collapse
Did you wipe /system (and /cache) and are you using TWRP v2.6.3.0 (that's what I use)?
Avamander said:
Did you wipe /system (and /cache) and are you using TWRP v2.6.3.0 (that's what I use)?
Click to expand...
Click to collapse
I was using a CWM version 2, and I had to update to the latest v3 (from Varchain, :
https://mega.nz/#!QXZUnbwQ!BRI3ENa-53StAjr2Tq1R-hmyIJ9ZDERWIAxXpx9Hye4) and it is now installing. Or do you suggest to update to TWRP?
I'll test it now.
thePanz said:
I was using a CWM version 2, and I had to update to the latest v3 (from Varchain, :
https://mega.nz/#!QXZUnbwQ!BRI3ENa-53StAjr2Tq1R-hmyIJ9ZDERWIAxXpx9Hye4) and it is now installing. Or do you suggest to update to TWRP?
I'll test it now.
Click to expand...
Click to collapse
Let me know if the latest works. If it doesn't, let me know if TWRP works
Avamander said:
Let me know if the latest works. If it doesn't, let me know if TWRP works
Click to expand...
Click to collapse
Ok, CWM v3 installed and Lineage-v11 installed, too.
The install went OK. Few issues encountered so far:
1. looks like the phone WiFi is configured for US area (thus, only channels 1-11 are working, but not mine, as it was configured on channel 13. I had to use https://forum.xda-developers.com/showthread.php?t=1982149 to properly fix it. Would be great if the ROM comes with the 1-13 set of channels.
2. Installing TitaniumBackup: install ok, but it did not run, ADB reported "libtitanium.so not found". Looks like the v8.1.0 is not able to extract the ARM library. I had to extract it from the APK (found here https://www.androidapksfree.com/apk/titanium-backup-apk-latest-version-download/download/) and manually push the library with "adb push libtitanium.so /data/data/com.keramidas.TitaniumBackup/files/"
Couldn't find anywhere else why those errors are caused. Do you have the same behaviour?
btw: thanks for your effort in keeping the D605 alive
thePanz said:
Ok, CWM v3 installed and Lineage-v11 installed, too.
The install went OK. Few issues encountered so far:
1. looks like the phone WiFi is configured for US area (thus, only channels 1-11 are working, but not mine, as it was configured on channel 13. I had to use https://forum.xda-developers.com/showthread.php?t=1982149 to properly fix it. Would be great if the ROM comes with the 1-13 set of channels.
2. Installing TitaniumBackup: install ok, but it did not run, ADB reported "libtitanium.so not found". Looks like the v8.1.0 is not able to extract the ARM library. I had to extract it from the APK (found here https://www.androidapksfree.com/apk/titanium-backup-apk-latest-version-download/download/) and manually push the library with "adb push libtitanium.so /data/data/com.keramidas.TitaniumBackup/files/"
Couldn't find anywhere else why those errors are caused. Do you have the same behaviour?
btw: thanks for your effort in keeping the D605 alive
Click to expand...
Click to collapse
I will investigate the WiFi issue... The TiBu issue, sounds weird, though a lot of old exploits have been patched and some apps might be expecting they exist. Though in my case I could install TiBu without issues from Google Play. I updated the planned task list.
Avamander said:
I will investigate the WiFi issue... The TiBu issue, sounds weird, though a lot of old exploits have been patched and some apps might be expecting they exist. Though in my case I could install TiBu without issues from Google Play. I updated the planned task list.
Click to expand...
Click to collapse
Thank you!
As a side note: CWM v3 is also able to lokify the ROM after flashing Varchain added it "because I am lazy" (cit.)
thePanz said:
Thank you!
As a side note: CWM v3 is also able to lokify the ROM after flashing Varchain added it "because I am lazy" (cit.)
Click to expand...
Click to collapse
That means it would still break the signature if I would release a signed image.
Quick update: the offline-charging is not working.
Switching off the phone and connecting the charger will boot up the phone in the default mode, not "only charging".
I know this might be a minor bug but auto brightness doesn't work.
DJ-SMOKE_300 said:
I know this might be a minor bug but auto brightness doesn't work.
Click to expand...
Click to collapse
Never has, never will, there's no brightness sensor hardware.
Avamander said:
Never has, never will, there's no brightness sensor hardware.
Click to expand...
Click to collapse
Oh. Thanks for clearing that up. All in all its mostly stable. :good:
Another thing i noticed is that some system processes crash at random times. And if I have my own wallpaper set if that happens and I reboot the device it resets.
DJ-SMOKE_300 said:
Another thing i noticed is that some system processes crash at random times. And if I have my own wallpaper set if that happens and I reboot the device it resets.
Click to expand...
Click to collapse
Seen that happen a few times, but without logs of the crash I can't help you.
1. Please remove the space character from the link to md5 for ROM.zip. I think it is easier to place a checksum instead of a link.
2. Last edited by Avamander; 26-12-2017 at 23:23. Reason: New build revert.
Has the file changed on the server, has it been refreshed or something else?
---------- Post added at 23:26 ---------- Previous post was at 23:11 ----------
Avamander said:
(...)
Installation instructions
* Use TWRP, wipe everything, (...)
Click to expand...
Click to collapse
Is there really a reason to clean Internal storage and sdcard?
> 1. Please remove the space character from the link to md5 for ROM.zip. I think it is easier to place a checksum instead of a link.
It's more work to create the file for the recovery to verify it. The space is part of the link.
> 2. Last edited by Avamander; 26-12-2017 at 23:23. Reason: New build revert.
Has the file changed on the server, has it been refreshed or something else?[
Nope
> Is there really a reason to clean Internal storage and sdcard?
Internal storage? If you mean /data, yes, but /sdcard doesn't need to be wiped.
As a sidenote, I've been rebuilding the entire system today, will see if that brings back the WiFi.
{
"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"
}
Team Win Recovery Project 3.x, or twrp3 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.
Code:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
Supported Models:
Galaxy S23 Ultra S918B/S918N/S9180.
Download & Guide:
1. Unlock your bootloader.
2. Downloads for S23 Ultra: AFH: dm3q twrp
3. Reboot to download mode
4. Uncheck auto reboot in Odin and flash TWRP in AP slot and vbmeta_disabled_R.tar in USERDATA slot.
5. Hold volume down and power until the screen goes black then immediately switch to holding volume up and power to reboot into TWRP.
6. Go to wipe, format data, and type "yes" to confirm.
7. Reboot to TWRP
8. Flash boot_repack.zip (To fix stock recovery restoration)
9. Flash magisk canary (Optional)
10. Reboot to system, Enjoy.
Support:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Telegram group
Bugs:
- Decryption will only work if no password/PIN/pattern is set in Android.
- No erofs r/w support yet.
Thanks:
TWRP team
@BlackMesa123 for helping me to add encryption support
@dr.ketan for supporting meDonators
Sources:
Kernel tree
Device tree
Changelog:
GitHub History
mine
afaneh92 said:
Bugs:
- Encryption not fully working.
- No erofs r/w support yet.
Click to expand...
Click to collapse
Data decrypt support should be mandatory for this device expecially with the newer A13 EROFS partitions, please consider adding it.
BlackMesa123 said:
Data decrypt support should be mandatory for this device expecially with the newer A13 EROFS partitions, please consider adding it.
Click to expand...
Click to collapse
I tried on S20+ and S22 ultra it was harder than A series. But will try again when the device delivered, I may ask for your help. Thanks.
afaneh92 said:
I tried on S20+ and S22 ultra it was harder than A series. But will try again when the device delivered, I may ask for your help. Thanks.
Click to expand...
Click to collapse
Implementing crypto support is not that hard as it seems, in the S23 family it should even be easier since you can just implement the official TeamWin QSEE scripts in your device tree. I imagine the big deal on S20/S22 is due to those device having an Exynos SoC with TEEgris TZ, but even in that case it should be easy to handle. What I'm more afraid of is that this device probably has Knox SDP in vold so decrypt with PIN/password set won't work, but it's better than nothing atm.
BlackMesa123 said:
Implementing crypto support is not that hard as it seems, in the S23 family it should even be easier since you can just implement the official TeamWin QSEE scripts in your device tree. I imagine the big deal on S20/S22 is due to those device having an Exynos SoC with TEEgris TZ, but even in that case it should be easy to handle. What I'm more afraid of is that this device probably has Knox SDP in vold so decrypt with PIN/password set won't work, but it's better than nothing atm.
Click to expand...
Click to collapse
I was referring to snapdragon, and never worked. I used your implementation and device wasn't able to decrypt data. S22 was harder since data wasn't able to mount. I will wait for device, thanks again.
afaneh92 said:
I was referring to snapdragon, and never worked. I used your implementation and device wasn't able to decrypt data. S22 was harder since data wasn't able to mount. I will wait for device, thanks again.
Click to expand...
Click to collapse
We can surely work it out to fix it
@afaneh92 it looks like S23 vold has no crap A11 code leftovers which does break decrypt with PIN/password on TWRP, I compared the vold bin with my A52s' one and certain stuff is clearly missing. So it might just work out of the box once support for it gets added
BlackMesa123 said:
@afaneh92 it looks like S23 vold has no crap A11 code leftovers which does break decrypt with PIN/password on TWRP, I compared the vold bin with my A52s' one and certain stuff is clearly missing. So it might just work out of the box once support for it gets added
Click to expand...
Click to collapse
I hope so.
Nice work!
I followed the steps above, and when trying to reboot to system I get back to to twrp. Help please?
I just want to ask if anyone has tried installing viper4android yet and does it work? If it's like the s22 ultra and doesn't work. I might sound crazy but I wouldn't buy it. Music is more important to me then spen and camera although admittedly they are good to. It's mind blowing to think 1200 dollar won't sound as good as my Poco f3 or even my lg tribute 10 years ago.
lcd047 said:
I followed the steps above, and when trying to reboot to system I get back to to twrp. Help please?
Click to expand...
Click to collapse
I have exactly the same:
- after following all steps one by one there is only a reboot into TWRP itself possible
I compared the steps from this thread with the steps which are successfully working on my Galaxy Tab S8 Ultra ( https://forum.xda-developers.com/t/...-for-galaxy-tab-s8-series-snapdragon.4455491/ ) and I see a difference at step 7:
7. Flash custom kernel and magisk apk in twrp.
Click to expand...
Click to collapse
I do not see any "custom kernel" to download in this thread (at least for now) so I think this is the missing part. Or it only works correct in combination with "dr.ketans rom" (which I do not want to use for now).
@afaneh92: Thank you very much for your work (on "root" and also with "twrp")!
Edit: I just read the installation pdf from "dr. ketans rom". There is written in red letters:
DON'T run multidisabler from TWRP termial/zip or any system-rw script after flashing ROM else device won't boot.
Click to expand...
Click to collapse
So maybe the not booting system is related to the work which the "multidisabler" should do.
I will be happy if there will be some light regarding the non booting system after flashing TWRP.
Maybe I will give "dr. ketans rom" a try and have an eye on this thread how the things go on.
________________________________________
@Techguy777: This is very offtopic but I am with you that "Viper4Android" is a very important part also of my daily used tools. I just have found a (for me) good running workaround.
Search the fDroid store for the app "RootlessJamesDSP". Depending on which parts of "Viper4Android" you care about, the app is an extremely good working replacement. In my example, the "Convolver" with the impulse response files are important and that works wonderfully with the players I use.
hurray said:
I will go back for now to (rooted) stock ROM and Recovery and will have a look how this thread will go on.
Click to expand...
Click to collapse
Sadly flashing "dr.ketans rom" (or the "unroot" one, for that matter) doesn't fix the problem for me. Ironically everything was working fine with "dr.ketans rom" alone, but I just had to try disabling encryption. Well I suppose better is the enemy of good.
lcd047 said:
Sadly flashing "dr.ketans rom" (or the "unroot" one, for that matter) doesn't fix the problem for me. Ironically everything was working fine with "dr.ketans rom" alone, but I just had to try disabling encryption. Well I suppose better is the enemy of good.
Click to expand...
Click to collapse
I just flashed the orginal FW from samfw.com and my S23 Ultra is booting correctly into the system. Now I will try the current "S918B_WA6_DrKetan_ROM_T02". It seems that TWRP is build in into the ROM. If this works I will try a backup & restore of user data (this is the most important part from TWRP for me).
hurray said:
I just flashed the orginal FW from samfw.com and my S23 Ultra is booting correctly into the system. Now I will try the current "S918B_WA6_DrKetan_ROM_T02". It seems that TWRP is build in into the ROM. If this works I will try a backup & restore of user data (this is the most important part from TWRP for me).
Click to expand...
Click to collapse
After flashing my ROM + Format dara (Read changelog) TWRP backup/restore data should work as expected. And for that purpose mentioned in OP
dr.ketan said:
After flashing my ROM + Format dara (Read changelog) TWRP backup/restore data should work as expected. And for that purpose mentioned in OP
Click to expand...
Click to collapse
Yup, flashing the full ROM works. Many thanks, and keep up the amazing work!
dr.ketan said:
After flashing my ROM + Format dara (Read changelog) TWRP backup/restore data should work as expected. And for that purpose mentioned in OP
Click to expand...
Click to collapse
You have convinced me of your ROM. After flashing I had to reformat "data" but afterwards the system booted correctly.
The ROM works very well so far and the additional functions via "ROM Tools S23" are also good (especially that they can be selectively enabled and disabled).
Backup and recovery of user data has also worked flawlessly.
So now I can start with the actual setup of all apps.
Thanks a lot for your work!
hurray said:
You have convinced me of your ROM. After flashing I had to reformat "data" but afterwards the system booted correctly.
The ROM works very well so far and the additional functions via "ROM Tools S23" are also good (especially that they can be selectively enabled and disabled).
Backup and recovery of user data has also worked flawlessly.
So now I can start with the actual setup of all apps.
Thanks a lot for your work!
Click to expand...
Click to collapse
I have seen many users don't want "custom" roms, but my ROM will have complete stock look + single click all critical fix. It won't force users to use customised look. Also it have more options to make modifications in ui but everything will be by user's will.