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!
Related
Please post all non-dev questions and discussions here:
http://forum.xda-developers.com/showthread.php?t=2392703
Click to expand...
Click to collapse
CyanogenMod 10.2 is a free, community built, aftermarket firmware distribution of Android 4.3 (Jellybean), which is designed to increase performance and reliability over stock Android for your device.
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.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
Download:
alpha #1
Click to expand...
Click to collapse
Requirements:
Unlocked bootloader
CWM recovery installed
Install:
Download the rom
Extract the boot.img
Copy the rom to your sdcard
Go to recovery and flash the rom
Wipe data
Reboot to bootloader/fastboot
Install boot.img with fastboot ---> fastboot flash boot boot.img
Reboot and enjoy!
Sources:
I share the source code, but i have some requests:
Please don't use my work without my permission.
If you have some fixes, don't open a new thread. Just make pull request, write me PM, or share it in this thread.
All sources avaliable here: https://github.com/ProtouProject
Use this for init the repo: "repo init -u git://github.com/ProtouProject/android.git -b cm-10.2"
Credits:
@sakindia123
Working:
Touchscreen
Lights
GSM & data
Camera
Sensors
Not working:
SD card
Bluetooth
Wifi
Audio
Changelog:
alpha 1.0:
First release
Support:
If you would like to support me and the development, you can donate to me here:
Donators: (Thank you guys )
@vogonpoetlaureate
@simaka
@eagle_vis
@RuudM
@azraelcelt
Ok guys,i managed somehow to turn on the Bluetooth and connect it to my moms Nokia. But then i tried to replicate it and now it won't turn on.
Here is the logcat and you can see on the bottom that it connected. http://pastebin.com/PaDuCZiB
Camera crashes on start and Focal is working but crashes when i take a picture. That is probbably because of the SD problem.
No sound,no wifi,i didn't test the gps. Rom is fast,but some animations are laging.
@atis112 i see in the source that you did some changes to BT did you fix it ?
EDIT 3,i think. xD
#define BTM_DEF_LOCAL_NAME in bdroid_buildcfg.h is set as "HTC Explorer A310e" , i mean it's not really a bugfix but i think that BT deservs the name of our device.
EDIT 4 :
So i checked the bt_vendor.conf and there was a file in /system/etc/firmware/ named BCM4330B1_002.001.003.0221.0228.hcd but when i checked on the phone it was named something like BCM4330B1_002.001.003.08xx.08xx.hcd,can't remember correctly. So i renamed it and when i rebooted the bt was on. But when i turn it off it won't turn on again unless i reboot the phone.
{
"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"
}
@nightwalkerkg Congrats.. we are on the same stage in cm10.1
@atis112 did u make changes to protou.fstab to support sdcard mounting? I have heard that there are new changes in 4.3 and vold.fstab is removed.. One more thing, where did u get that ramdisk from? it seems little buggy to me...
prototype-U said:
@nightwalkerkg Congrats.. we are on the same stage in cm10.1
@atis112 did u make changes to protou.fstab to support sdcard mounting? I have heard that there are new changes in 4.3 and vold.fstab is removed.. One more thing, where did u get that ramdisk from? it seems little buggy to me...
Click to expand...
Click to collapse
I am not really a dev,i am just trying to help. I tried to find some help on cm irc channel,but they were to busy trying to help some guy with his S3. -.-' I'll se what i can do,so far i know that sd card can be acessed fully in file manager but only when you enable root access,other then that there is only a download folder. Also when charging the green led turns on as soon as the phone battery lvl reaches 92-93%. Sound works in phone calls,i did two phone calls and some messages and everything was ok. Are there any gapps,i would like to test some other things ?
nightwalkerkg said:
Ok guys,i managed somehow to turn on the Bluetooth and connect it to my moms Nokia. But then i tried to replicate it and now it won't turn on.
Here is the logcat and you can see on the bottom that it connected. http://pastebin.com/PaDuCZiB
Camera crashes on start and Focal is working but crashes when i take a picture. That is probbably because of the SD problem.
No sound,no wifi,i didn't test the gps. Rom is fast,but some animations are laging.
@atis112 i see in the source that you did some changes to BT did you fix it ?
EDIT 3,i think. xD
#define BTM_DEF_LOCAL_NAME in bdroid_buildcfg.h is set as "HTC Explorer A310e" , i mean it's not really a bugfix but i think that BT deservs the name of our device.
EDIT 4 :
So i checked the bt_vendor.conf and there was a file in /system/etc/firmware/ named BCM4330B1_002.001.003.0221.0228.hcd but when i checked on the phone it was named something like BCM4330B1_002.001.003.08xx.08xx.hcd,can't remember correctly. So i renamed it and when i rebooted the bt was on. But when i turn it off it won't turn on again unless i reboot the phone.
Click to expand...
Click to collapse
Yes, I know about this, but i don't work with bt or wifi, while sdcard not working.
prototype-U said:
@nightwalkerkg Congrats.. we are on the same stage in cm10.1
@atis112 did u make changes to protou.fstab to support sdcard mounting? I have heard that there are new changes in 4.3 and vold.fstab is removed.. One more thing, where did u get that ramdisk from? it seems little buggy to me...
Click to expand...
Click to collapse
Yes, i added it: https://github.com/ProtouProject/android_device_htc_protou/blob/cm-10.2/ramdisk/fstab.protou#L6
The sdcard problem is because of prebuilt init. But with CM init, the ril don't work and the rom have random reboots.. and I don't know why.
I think that the sdcard is mounted as read-only or idle.
I read on some disscussion that fsck -f /dev/store/media this would help fix it.
Also is it possible to switch internal and external storage ?
There is a hashtag in /ramdisk/init.protou.rc on line 12,should it be there and on line 148 there is just # wifi-- ? I am just asking this because they don't seem like they should be there,but that is just me.
What is the diff. bettwen eth0 and wlan0 ?
EDIT:
Here are the gapps if you need them.
http://forum.xda-developers.com/showthread.php?t=2387878
nightwalkerkg said:
I think that the sdcard is mounted as read-only or idle.
I read on some disscussion that fsck -f /dev/store/media this would help fix it.
Also is it possible to switch internal and external storage ?
There is a hashtag in /ramdisk/init.protou.rc on line 12,should it be there and on line 148 there is just # wifi-- ? I am just asking this because they don't seem like they should be there,but that is just me.
What is the diff. bettwen eth0 and wlan0 ?
EDIT:
Here are the gapps if you need them.
http://forum.xda-developers.com/showthread.php?t=2387878
Click to expand...
Click to collapse
Appreciate your efforts @nightwalkerkg,
Might i suggest a better method? make a git account and make pull requests. That way, atis112 will have an easier time looking at exactly what you mean.
Regards
Yasir
---------- Post added at 11:49 PM ---------- Previous post was at 10:57 PM ----------
@atis112
Why does pico use NO "init" file??
That means they use CM init?
neXus PRIME said:
Appreciate your efforts @nightwalkerkg,
Might i suggest a better method? make a git account and make pull requests. That way, atis112 will have an easier time looking at exactly what you mean.
Regards
Yasir
---------- Post added at 11:49 PM ---------- Previous post was at 10:57 PM ----------
@atis112
Why does pico use NO "init" file??
That means they use CM init?
Click to expand...
Click to collapse
Yes, they use the source-built CM init.
I did adb shell dmesg and this popped out http://pastebin.com/vZdvYpB6 .
There are tons of <3>[ 1761.106391] C0 init: cannot find '/system/bin/fusermount', disabling 'fuse rmount' errors.
nightwalkerkg said:
I did adb shell dmesg and this popped out http://pastebin.com/vZdvYpB6 .
There are tons of <3>[ 1761.106391] C0 init: cannot find '/system/bin/fusermount', disabling 'fuse rmount' errors.
Click to expand...
Click to collapse
We just need to delete it: https://github.com/ProtouProject/android_device_htc_protou/blob/cm-10.2/ramdisk/init.rc#L641
Our ramdisk is not really clean
atis112 said:
We just need to delete it: https://github.com/ProtouProject/android_device_htc_protou/blob/cm-10.2/ramdisk/init.rc#L641
Our ramdisk is not really clean
Click to expand...
Click to collapse
Haha,yeah.
I'll do some resizing for mySense5 rom,i am much better at graphics,sorry. But after that i'll try to help as much as i can.
Also the logcat is reporting tons of errors,mostly about some files missing. As you can see here : http://pastebin.com/mi96kzyR .
mahra said:
it would be nice, if you finish 4.2.2 first, jumping from project to another project is a bit lame.
i have asked you something on PM, but u didn't replied me. why ?
Click to expand...
Click to collapse
Why would he, 4.2.2 to 4.3 isnt a big jump. And most of the work done on 4.2.2 can be transferred to 4.3. Besides, I dont see it as a new project, but as an upgrade of the current. Its still a jelly bean. He cant help it either that cm gave it an other build number. Its positive in my eyes he moved on to 4.3 instead of sticking to an older android build. Isnt that what we all want? The latest and greatest? So, its not about what you or anyone else wants, but about what he wants. We just have to follow, like it or not.
Edit:
And an other thing: just noticed the thread title, can you please ask questions like this in the q&a thread, this is for development only. You can find the link in the OP.
Sent from my HTC Desire X with Tapatalk Red
Computers are like air-conditioners. They can't work properly if you open windows.
source released !
The jelly bean source ( 4.1.1) has been released for our phone finally !! :good:
http://www.htcdev.com/devcenter/downloads
hopefully this will help with development
Cleaned up fully half the posts here. There's a discussion thread for all non-dev related posts. Thread closed at OP request.
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.
I don't always follow a new device during the troubled early days of root...
...but when I do, I'm utterly scarred by the chaos and confusion.
Since I've watched the current V20 root exploit evolve from "maybe DirtyCow would work here" into a full-blown war on Nougat's sepolicy, and finally into the emergent "Recowvery"; I thought it might be fun to get my own hands a little dirty and write some wrappers to automate the rooting process with ample error-checking along the way.
>> Please take a moment to check out @jcadduono's Recowvery thread at http://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594 for more information, to say "thanks," and to donate if you can afford it. <<
WARNING: ATTEMPT AT YOUR OWN RISK! THIS PACKAGE IS RELEASED AS-IS AND WITHOUT ANY WARRANTY, IMPLIED OR EXPRESSED
THIS PACKAGE MAY MAKE YOUR LIFE EASIER (or harder) BUT NOTHING CAN FULLY PROTECT YOU FROM TROUBLE WHEN ROOTING A DEVICE!
IT IS NOT MY RESPONSIBILITY IF YOU END UP WITH A BRICK IN YOUR POCKET AFTER ATTEMPTING ROOT
{
"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"
}
Current, Planned, and Not Guaranteed Features:
- Windows support, including a truly die-hard adb check
- Push, exploit, and flash all in one step
- Optional automated SuperSU installation
- Bundled adb for more predictable results
- More error checking than you think you'd need
- Auto-disable dm-verity and forced encryption
- Optional selinux permissive mode
- Restore boot and recovery to stock
- Spawn a root shell for exploration and such
- Grab any recovery.img you'd like to use from /sdcard
- Linux support (needs to be reworked )
- Ability to download latest exploit and recovery at runtime
- Extra helper commands for stuff like trying to break out of bootloops or quickly grab logs
- Basic GUI for Windows
Download:
Latest version: 1.3b3
Grab the latest zip: https://github.com/bziemek/EasyRecowvery/releases
Or browse the source: https://github.com/bziemek/EasyRecowvery
--
TWRP for the H918: in jcadduono's thread, Step 3
no-verity-opt-encrypt: also in jcadduono's thread, Step 3
SuperSU: in Chainfire's beta thread
Instructions:
https://github.com/bziemek/EasyRecowvery/blob/master/README.md
Greetz:
Huge shout out to @jcadduono for running with the DirtyCow idea and making this root possible (read more and THANK HIM HERE), Chainfire for taking some time off to do a test install of the latest SuperSU hours before we had a working TWRP, @Darriousx and @slayerh4x for all their hard work testing, and #twrp on Freenode for generally putting up with the lot of us!
Donations:
IF you feel so inclined, PayPal some coffee and beer money to [email protected], or BTC to 1bu5MMgagtbN7QVeciyWfAzRbfk8vmynM
Many thanks to @Pjs187, who furnished the first donation I've received here at XDA!
Frequently Asked Questions
Why isn't it working?
First: update your ADB. If you don't have ADB, then you'll want to fix that before you spend another second at XDA. I personally only use official releases from Google, so I might not be much help if you're using something you found at random at XDA or elsewhere on the Internet. You can download Google's latest release of their tools from the very bottom of this page. (I recommend installing or extract them to C:\Android for easy access.) Using the "SDK Manager" included in that download, choose to install "Android Platform-tools" and "Google USB drivers", and remember to run it again once in a blue moon for updates.
If ADB isn't the problem, I'm happy to offer what assistance I can. Please describe what you were trying to do and how, then attach any .log files the script created.
Where is TWRP?
The link to the latest version is linked in this thread under Step 3.
Rename the downloaded file to recovery.img and put it on your internal storage.
Does Data need to be wiped?
For everything to work properly, YES. If you don't have an inherent understanding of what will happen if you don't run a Format Data, then please do so the first time you enter TWRP. This will erase Internal Storage and remove the default encryption so that TWRP can function to the fullest. BACK UP YOUR STUFF FIRST!
Is no-verity-opt-encrypt necessary?
YES, but not totally. This ZIP makes it possible to allow system modifications, and prevents a couple easy ways to end up with corrupt data or bootloops.
Download that from Step 3 in the thread above, and put it in the folder named zips next to EasyRecowvery.
If you're going to install SuperSU right away, you shouldn't really need it.
What is selinux?
selinux is a major security feature, and also a major pain in the butt depending on who you ask.
If you don't know if you need it in "permissive" mode, just leave it be. You can always reflash later.
Why isn't TWRP showing Internal Storage?
These phones use encryption out of the box. In order for TWRP to function properly, you will need to use the Wipe Data feature after installation.
This will blow away everything on your Internal Storage, so make sure you don't have anything important in there!
Changelog
1.3b3
Add more sanity checks
Add note about formatting data
Separate log for ZIP flashing
Rename bundled adb.exe to adb-recowvery.exe (maybe)
Older Versions
1.3b
Bundle adb.exe (can be toggled in Extras menu)
Improve and fix adb and device checks
1.2b
Add experimental support for auto-rooting.
Add an extra mode to flash no-verity-opt-encrypt.
Add an extra mode just to reboot into recovery.
1.1b-hotfix
Add the "zips" folder needed by the new version.
1.1b
Skip several versions and change versioning style.
Redesign the menu system.
Auto-flash no-verity-opt-encrypt.
Update Recowvery to latest version.
Tweak prompts, formatting, and fix typos.
More aggressive connection handling.
Fix the restore feature.
Allow disabling integrity verification (untested).
Increase logging verbosity.
Fix line endings in EasyRecowvery.cmd
beta5
Take a nap.
Fix some issues with various prompts.
Adjust some formatting.
More testing.
beta4
Improve adb checking code.
Reluctantly accept that we should try recovery.img.img.
Misc. tweaks to prompts.
beta3
Fix several parentheses that might be causing trouble.
beta2
Fix a bug causing EasyRecowvery to fail when run from another directory.
beta1
Initial release.
WOW! This is what i've been waiting for. Thanks man!
Thanks for this. Will help a lot of users who are Leary about the cureent manual process
Awesome...
Awesome man, so cool to watch all this develop. Glad I could be part of it.
definitely looking forward to this. sweetness!!!!
It has been amazing watch all this develop in the past weeks. I have been flashing and rooting for about 10 years and this is the first time I've seen it all from the beginning. It is really amazing what a few of these guys are capable of...but this time for me I was left speechless. Gentlemen, (and ladies?) Thank you for all of your free time and dedication for making this possible for the average end user like me. We all don't show enough gratitude and I'm sure I'm not the only one amazed my all of your capabilities. Keep up the unbelievable work, and a nice donation is coming to everyone who contributed if I can find a way to donate to you all. Point me in the direction, and the cash flow will be on its way. Thank you again.
Sincerely,
dmoney4eal
@bezeek you might want to add the "I am not responsib...." disclaimer. One for your protection but mostly so people are aware of the possible consequences.
If only I had the T-Mobile variant I would of already wrote this and put it in this thread lol, anyone want to donate? :c
whowatchlist said:
@bezeek you might want to add the "I am not responsib...." disclaimer. One for your protection but mostly so people are aware of the possible consequences.
Click to expand...
Click to collapse
There will be some big ol' red letters in here before I attach any files - you can bet on that
pro_granade said:
If only I had the T-Mobile variant I would of already wrote this and put it in this thread lol, anyone want to donate? :c
Click to expand...
Click to collapse
If you think you can beat me to it, there are H918 owners in #twrp on Freenode who would be happy to help you test as you go
bezeek said:
If you think you can beat me to it, there are H918 owners in #twrp on Freenode who would be happy to help you test as you go
Click to expand...
Click to collapse
I could write it in batch and convert to exe.
pro_granade said:
I could write it in batch and convert to exe.
Click to expand...
Click to collapse
I'm game for a friendly race. I've got lots else going on today, so it's coming together bit by bit.
(I might be putting up a rough build in the AM depending on what sort of sleep I get tonight.)
bezeek said:
I'm game for a friendly race. I've got lots else going on today, so it's coming together bit by bit.
(I might be putting up a rough build in the AM depending on what sort of sleep I get tonight.)
Click to expand...
Click to collapse
It'd be a lot quicker if I actually had the device. I'll probably let you go for it lmao
Race, race, race!
The winner gets the most thanks??
poczynek said:
Race, race, race!
The winner gets the most thanks??
Click to expand...
Click to collapse
How about some money lol
Is this still a WIP? I don't see anything updated by the OP. I'm waiting to root and something like this would be great as I am leery of going through the regular method with ADB as I'm coming from a Samsung device.
I pledge $20!.
*** 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.