[H918 / T-mo] [1.3b3] EasyRecowvery - TWRP and Root Installer - LG V20 ROMs, Kernels, Recoveries, & Other Developm

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!.

Related

[TOOL] HTC Evo 4G LTE All-In-One Toolkit V2.0 [1-18-2013] [PERM ROOT][Noob-Proof]

Post 1 - Information
Post 2 - Downloads and Release / Change Information
Post 3 - Bugs, Future Additions to the GUI, FAQ
I would like to add for those that like my toolkit, PLEASE DO NOT POST IT ELSEWHERE WITHOUT MY PERMISSION!
I have seen multiple sites who copy and paste my work to their site! If I do not approve of it, then do not do it! it will discourage me from adding updates since it is being used for their own benefits!
tl;dr.
If you post my work without permission, don't expect updates!​
I created an easy to use GUI program for the HTC Amaze and I decided to make one for the HTC Evo 4G LTE. I spent a good over 10+ hours to learn how to script, watch videos on how to do it, working on it during school when I should have been listening lol and all that fun stuff. I am going to fix it and up and add more updates to it. You CAN place requests and I will try to fulfill it!
If this helped you out, Please press the thanks button and if you want, you can always donate!​
FEATURES​
- Install HTC Drivers
- Enter Bootloader (after it enters into bootloader, press the power button to enter Fastboot) REMOVED. No longer necessary.
- Get Token ID. Register at HTCDev, login to the site and submit the Token ID here. Buttons have been replaced and include links.
- Unlock Bootloader (Must place Unlock_code.bin in the folder)
- Install Recoveries
TWRP 2.3.3.0
User Provided Recovery
-Flash Kernels provided
User Provided Kernel
- Link to this thread
- Link to PM me if you need a phone unlocked
- Link to the Evo 4G LTE Development thread
- Boot Into Recovery
- Boot into Bootloader
- Relock Bootloader (must be in fastboot)
- APK Batch Installer (Credits to hamsteyr)
- Donate to me (Hasoon2000) -> Donating to yours truly for putting time into this! (A great motivator for me to continue updating for the Evo 4G LTE!)
Here is a screenshot.
{
"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"
}
How To Use. THIS IS FOR THE PC ONLY. No plans ever for Mac or Linux. Sorry.
1. Download the toolkit DO NOT RENAME THE FOLDER
2. Download Winrar from here. Install it after you download it
3. Extract the folder anywhere.
4. Run the program.
Credits
- The guys at the AutoIT help forum that helped me learn how to make the script!
- Mods of the forum!
- Devs for making us ROMS!
- The community for being awesome!
- HTC for making us the phone so we can be a community!
- To everyone else I may have forgotten!
*DISCLAIMER*​
I take no responsibility for any fault or damage caused by any procedures within this guide. No warranties of any kind are given.
DONATIONS​​
You can show your appreciation by donating to me via PayPal by clicking THIS. It helps me continue going to school and gives me a motivator to update the toolkit for the Evo 4G LTE!
- michael.stollaire
Click to expand...
Click to collapse
Downloads
Mod edit: Download links removed
Changes
V1.0 Released! 6-24-2012
- Initial Release
V1.1 7-25-2012
- Updated TWRP to 2.2.0
- Updated SuperSU to 0.94
- Fixed script for Flashing your own recovery
v2.0 Released! 1-18-2013
- Major Overhaul
- Updated TWRP 2.3.3.0
- Users can now select their own recovery, kernel and unlock_code.bin. You no longer need to place it in a the data folder. Just browse for it
- Removed a lot of .bat scripts and integrated it in the program
- Updated SuperSU to 0.99
- Added a few links
- Added ADB sideload
Bugs
- Directory has to have one word.
Ex:
Will Work. This will solve any issues if the buttons don't work when you press them.
C:\Users\John\Dropbox\Phones\Amaze_All-In-One_Kit_V2.4
C:\Users\John_Smith\Dropbox\Phones\Amaze_All-In-One_Kit_V2.4
Will NOT work. Your directory will look something like this and buttons won't work when you press it.
C:\Users\John Smith\Dropbox\Phones\Amaze_All-In-One_Kit_V2.4
If you have 2 words, put the folder in Drive C:
Ex. This will solve any issues if the buttons don't work when you press them.
C:\Amaze_All-In-One_Kit_V2.4
Click to expand...
Click to collapse
Looking to add in the future
- Kernels
- More recoveries
- Makes Requests!!!
FAQs
Q - Why Did you make this?
A - To make life easier
Q - You are limited on features. Why?
A- You can always make a request!
Q - Will this work on other devices?
A - Only the fastboot commands, HTC Dev unlock (device specific) and the HTC drivers. Toolkit is made for the specific device.
Q - Will you support more devices in the future?
A - If people REALLY want, I can make it happen. I just don't want to make anything that nobody would use.
Q - Awesome! Can I make a donation?
A - Of course! Do not feel obligated though. If you would like to make a donation, you can click the button on my toolkit or under my username.
Toolkit is uploaded! I close my threads when I am uploading so I don't get "Where is the link" comments lol
Number one yes sir
Sent from my htc_jewel using Tapatalk 2
This is awesome, thanks for sharing
JT man said:
Number one yes sir
Sent from my htc_jewel using Tapatalk 2
Click to expand...
Click to collapse
Actually, you are second. I'm the first one
Would you like help fixing the "One Word in Path" Bug? Should be a simple fix. Also, the flash "Your Own Recovery" option points to a bat that doesn't exist in the data folder.
regaw_leinad said:
Would you like help fixing the "One Word in Path" Bug? Should be a simple fix. Also, the flash "Your Own Recovery" option points to a bat that doesn't exist in the data folder.
Click to expand...
Click to collapse
The bug from what I know is due to the batch scripts not liking spaces lol
You need a recovery.iMG in the recovery folder . When the command is executed, it'll see the recovery.img and flash it. I'm positive it is linked. If not, ill take a look in the morning
Sent from my Amazon Kindle Fire using Tapatalk 2
hasoon2000 said:
The bug from what I know is due to the batch scripts not liking spaces lol
You need a recovery.iMG in the recovery folder . When the command is executed, it'll see the recovery.img and flash it. I'm positive it is linked. If not, ill take a look in the morning
Sent from my Amazon Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
There's a way to allow spaces in paths in batch files, pm me if you want to work on that. Also, the flash your own thing is looking for \data\FlashStock.bat, and it doesn't exist. But that should be an easy fix.
regaw_leinad said:
There's a way to allow spaces in paths in batch files, pm me if you want to work on that. Also, the flash your own thing is looking for \data\FlashStock.bat, and it doesn't exist. But that should be an easy fix.
Click to expand...
Click to collapse
I guess I gotta check it in the morning. Doing homework and working on it was not a good idea.. lol
I'll PM you on the spaces. Thanks again
Sent from my HTC_Amaze_4G using Tapatalk 2
thanks for this!
There is NO need to belittle or talk down any member or their work here in a public thread. If you have a complaint then you likely should keep it to your self, but if you can't at most PM them.
Since Regaw has already posted his comments and offered his help to the OP I see ZERO need for the three troll posts in here that I deleted...last warning guys....maybe you should take up building your own toolkit/mod instead of talking down/bad about someone elses that they have provided for free...
Its not about who's toolkit/mod is better here, and never will be, so dont make it that. The more development the better.
sgt. slaughter said:
There is NO need to belittle or talk down any member or their work here in a public thread. If you have a complaint then you likely should keep it to your self, but if you can't at most PM them.
Since Regaw has already posted his comments and offered his help to the OP I see ZERO need for the three troll posts in here that I deleted...last warning guys....maybe you should take up building your own toolkit/mod instead of talking down/bad about someone elses that they have provided for free...
Its not about who's toolkit/mod is better here, and never will be, so dont make it that. The more development the better.
Click to expand...
Click to collapse
Very well said sgt. slaughter.
HTC dev site doesnt support EVO LTE... Am I missing something here?
Sent from APX325C on CKT Network
djisia87 said:
HTC dev site doesnt support EVO LTE... Am I missing something here?
Sent from APX325C on CKT Network
Click to expand...
Click to collapse
Choose "other supported devices"
Sent From My HTC Amaze 4G Via Someone's Room
SWEET !!!!!!
Thanks man that look awesome,
FIRST :angel:
hasoon2000 said:
Post 1 - Information
Post 2 - Downloads and Release / Change Information
Post 3 - Bugs, Future Additions to the GUI, FAQ
I would like to add for those that like my toolkit, PLEASE DO NOT POST IT ELSEWHERE WITHOUT MY PERMISSION!
I have seen multiple sites who copy and paste my work to their site! If I do not approve of it, then do not do it! it will discourage me from adding updates since it is being used for their own benefits!
tl;dr.
If you post my work without permission, don't expect updates!​
I created an easy to use GUI program for the HTC Amaze and I decided to make one for the HTC Evo 4G LTE. I spent a good over 10+ hours to learn how to script, watch videos on how to do it, working on it during school when I should have been listening lol and all that fun stuff. I am going to fix it and up and add more updates to it. You CAN place requests and I will try to fulfill it!
If this helped you out, Please press the thanks button and if you want, you can always donate!​
FEATURES​
- Install HTC Drivers
- Enter Bootloader (after it enters into bootloader, press the power button to enter Fastboot) REMOVED. No longer necessary.
- Get Token ID. Register at HTCDev, login to the site and submit the Token ID here. Buttons have been replaced and include links.
- Unlock Bootloader (Must place Unlock_code.bin in the folder)
- Install Recoveries
TWRP 2.1.8
User Provided Recovery
-Flash Kernels provided
User Provided Kernel
- Link to this thread (Android-Dev / XDA)
- Link to PM me if you need a phone unlocked (Android-Dev / XDA)
- Link to the One X Development thread (Android-Dev / XDA)
- Boot Into Recovery
- Boot into Bootloader
- Relock Bootloader (must be in fastboot)
- APK Batch Installer (Credits to hamsteyr)
- Donate to me (Hasoon2000) -> Donating to yours truly for putting time into this! (A great motivator for me to continue updating for the Evo 4G LTE!)
Here is a screenshot.
How To Use. THIS IS FOR THE PC ONLY. No plans ever for Mac or Linux. Sorry.
1. Download the toolkit DO NOT RENAME THE FOLDER
2. Download Winrar from here. Install it after you download it
3. Extract the folder anywhere.
4. Run the program.
Credits
- The guys at the AutoIT help forum that helped me learn how to make the script!
- Mods of the forum!
- Devs for making us ROMS!
- The community for being awesome!
- HTC for making us the phone so we can be a community!
- To everyone else I may have forgotten!
*DISCLAIMER*​
I take no responsibility for any fault or damage caused by any procedures within this guide. No warranties of any kind are given.
DONATIONS​​
You can show your appreciation by donating to me via PayPal by clicking THIS. It helps me continue going to school and gives me a motivator to update the toolkit for the Evo 4G LTE!
Click to expand...
Click to collapse
Great tool and utilities. Soooo helpful. love, Love, LOVE IT! :good:
Put a game-like slick interface on your UI, and you've got a sellable item that will make you some serious coin in the Google Play Store.
PS: Donation on the way!
michael.stollaire said:
Great tool and utilities. Soooo helpful. love, Love, LOVE IT! :good:
Put a game-like slick interface on your UI, and you've got a sellable item that will make you some serious coin in the Google Play Store.
PS: Donation on the way!
Click to expand...
Click to collapse
Haha. That would be awesome! Glad you like and PM me when you send the donation so I add you to the list!
V1.1 7-25-2012
- Updated TWRP to 2.2.0
- Updated SuperSU to 0.94
- Fixed script for Flashing your own recovery
Download is in Post 2.

[RECOVERY][CWM] CWM 6.0.5.1 for LG L7_2

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!

[TOOL][PIXEL 3] TOOL ALL IN ONE (Drivers|Unlock|TWRP|Factory Image|Stock Recovery)

This is the Pixel 3's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN ONE
{
"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"
}
ADVANCED OPTIONS
FUNCTIONS
Install Drivers
Install Drivers
Unlock Bootloader
Lock Bootloader (use carefully)
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Automatic ROOT
Install APKs
Uninstall APKs
Take a Screenshot
Take a Screen Reocrd
Flash Partitions
Erase All Data (This function can decrypt the phone)
Reboot Phone
Update the Tool to latest version
Update Adb and Fastboot to latest version
Set Adb and Fastboot priviliges in system wide
Install Zip directly from PC (Required TWRP on phone)(These functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect TWRP on my phone)
Flash Fastboot ROM
Delete downloaded files
ADB File Manager
DEVICE LIST
If you want you can send a request to add a new device here:
New Device Request Form
Device List
DOWNLOAD
Original Thread
DONATE LINK
If you want to support the project please consider making a donation, thanks.
​
Thank you for this!
drocny87 said:
Thank you for this!
Click to expand...
Click to collapse
Actually i have not uploaded the twrps, because i don't know which one is working and which one is not working. In all cases manual mode is available
Source code?
You can't honestly expect people to download a random zip containing an executable right?
Although your intentions may not be nefarious you can't trust anyone.
dontcrash said:
Source code?
You can't honestly expect people to download a random zip containing an executable right?
Although your intentions may not be nefarious you can't trust anyone.
Click to expand...
Click to collapse
This tool is not open source.
Nobody obliges someone to use it, if you want you can, if you don't want, don't use it.
I want to specify that this tool have more of 200k of downloads.
mauronofrio said:
This tool is not open source.
Nobody obliges someone to use it, if you want you can, if you don't want, don't use it.
I want to specify that this tool have more of 200k of downloads.
Click to expand...
Click to collapse
I don't want to discourage anyone from trying this tool, I'm simply stating people should be cautious, just because it's been downloaded a heap of times doesn't automatically make it safe. Think back to when Lenovo was found having over 750,000 laptops spying on users.
I would trust the XDA community and their giving him a 3214 thanks meter.
sliding_billy said:
I would trust the XDA community and their giving him a 3214 thanks meter.
Click to expand...
Click to collapse
I'm sure millions trusted Lenovo also.
OP didn't obfuscate, will be looking over the whole source.
Also OP, please name your forms/buttons/labels please, it hurts my head seeing Button1, Button2, Button33, Button7583, Form38748354
dontcrash said:
I'm sure millions trusted Lenovo also.
OP didn't obfuscate, will be looking over the whole source.
Also OP, please name your forms/buttons/labels please, it hurts my head seeing this.
Click to expand...
Click to collapse
Ahahahah, As i said this is not an open source project so please don't share the source code.
mauronofrio said:
Ahahahah, As i said this is not an open source project
Click to expand...
Click to collapse
Anyway, don't want to discourage users, just want to keep everyone safe, will report my findings back here soon.
dontcrash said:
Anyway, don't want to discourage users, just want to keep everyone safe, will report my findings back here soon.
Click to expand...
Click to collapse
Already told you don't share the code, and please remove the code you already shared
mauronofrio said:
Already told you don't share the code, and please remove the code you already shared
Click to expand...
Click to collapse
Done.
Finished looking over 40+ Forms worth of code, nothing evil is going on here, I feel happy recommending people here to download now.
dontcrash said:
Done.
Finished looking over 40+ Forms worth of code, nothing evil is going on here, I feel happy recommending people here to download now.
Click to expand...
Click to collapse
I would have no reason to include something malevolent in such a complex app...
mauronofrio said:
I would have no reason to include something malevolent in such a complex app...
Click to expand...
Click to collapse
I'm not sure how the complexity of software would correlate to the likeliness of malware.
dontcrash said:
Done.
Finished looking over 40+ Forms worth of code, nothing evil is going on here, I feel happy recommending people here to download now.
Click to expand...
Click to collapse
The irony of you recommending this tool after "looking over" the code is just funny. FWIW, I have never used this tool or any other like it and have no interest in it other than someone trying to help others.
sliding_billy said:
The irony of you recommending this tool after "looking over" the code is just funny. FWIW, I have never used this tool or any other like it and have no interest in it other than someone trying to help others.
Click to expand...
Click to collapse
I decompiled the executable and went over every line of code, nothing dodgy is happening, it just has a heap of calls to cmd passing parameters and also the adb and fastboot tool etc.
dontcrash said:
I decompiled the executable and went over every line of code, nothing dodgy is happening, it just has a heap of calls to cmd passing parameters and also the adb and fastboot tool etc.
Click to expand...
Click to collapse
You might be missing my point. Your decision that is not malicious vs his original contention that it wasn't don't provide any more proof to anyone who didn't either review the code or write the code. All we have to go in is the XDA forum reputation. He is a developer on a developer site with a good one, and you have next to none. I don't think either of you are out to mislead anyone, and I certainly would not be the first to try a tool like this (if not for malicious code reasons, for "I don't feel like unbricking my phone" reasons). I wish you both well.
sliding_billy said:
You might be missing my point. Your decision that is not malicious vs his original contention that it wasn't don't provide any more proof to anyone who didn't either review the code or write the code. All we have to go in is the XDA forum reputation. He is a developer on a developer site with a good one, and you have next to none. I don't think either of you are out to mislead anyone, and I certainly would not be the first to try a tool like this (if not for malicious code reasons, for "I don't feel like unbricking my phone" reasons). I wish you both well.
Click to expand...
Click to collapse
Fair point, I would encourage anyone interested to decompile and verify for themselves, I dislike closed source software.
dontcrash said:
Fair point, I would encourage anyone interested to decompile and verify for themselves, I dislike closed source software.
Click to expand...
Click to collapse
If you dislike closed source software is a your problem, please stop spam with your thoughts and convictions.
mauronofrio said:
If you dislike closed source software is a your problem, please stop spam with your thoughts and convictions.
Click to expand...
Click to collapse
Mad respect to this.

Themes / Apps / Mods [DEV] Kernel Flasher

{
"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"
}
Kernel Flasher is an Android app to flash, backup, and restore kernels.
Features
Flash partition images and AK3 kernel zips
Backup and Restore kernel partitions
Mount, Map, and Resize vendor_dlkm
Save dmesg, logcat, and ramoops
Check for kernel updates
Notes
When making a backup of the active slot, to save time, it is assumed that the kernel on disk is the same as the running kernel. The Check Kernel Version button can retrieve it from disk prior to backup.
Depending on the method used, the updated contents of vendor_dlkm may not be immediately available for backup after flash or restore. This can be resolved by unmounting, unmapping, then remapping it.
AK3 helper modules are not backed up.
Credits
@osm0sis for AK3, feedback, and general guidance
@eng.stk & @Freak07 for feedback, advice, and encouragement
@phhusson for lptools
@topjohnwu for Magisk and libsu
Latest Update
2023-02-20 v1.0.0-alpha13
Hi, great app!
Can you please leave the kernel installation log opened after the process ends with an error? Currently it's impossible to see what went wrong since the log disappears instantly and is being replaced by an error screen.
Nezorflame said:
Can you please leave the kernel installation log opened after the process ends with an error? Currently it's impossible to see what went wrong since the log disappears instantly and is being replaced by an error screen.
Click to expand...
Click to collapse
That is already done in my own personal test version of the app, but I haven't had a chance to clean it up and get it released. I'll make an effort to get that done this evening.
I've got several other enhancements planned, but most of my focus has been on Hashtree Patcher lately, though I think that is nearly wrapped up. I'll try to get the installation log issue fixed asap, then I'll work on the rest over the next few days.
I pushed a new build that resolves the installation log issue. Here is the full changelog:
added option to backup AK3 zips
disabled flash and restore on inactive slot
added save ramoops button
added stderr to AK3 logs
added .log file extension to log files
filtered ui_print and progress in AK3 logs
sorted backups
Click to expand...
Click to collapse
I also added a list of planned and potential features to the OP. If you've got some interest in seeing any of them or anything I may have missed in a future build, feel free to note it here. If the list gets to be too big of a pain to maintain here, I may request that they go to the issue tracker, instead. Note that I don't currently plan to add kernel tweaks to the app.
Edit: There was a bug in the v1.0.0-alpha03 build that caused it to crash frequently. This has been fixed in v1.0.0-alpha04.
Alpha 4 seems like a bad upload? I have downloaded it a couple times but Android just reports "There was a problem parsing the package"
osm0sis said:
Alpha 4 seems like a bad upload? I have downloaded it a couple times but Android just reports "There was a problem parsing the package"
Click to expand...
Click to collapse
Hum installed fine on mine, maybe github acting up?
md5:
KernelFlasher-v1.0.0-alpha04.apk 94a1b66b29e95e23c918b054b9b3b1d6
eng.stk said:
Hum installed fine on mine, maybe github acting up?
md5:
KernelFlasher-v1.0.0-alpha04.apk 94a1b66b29e95e23c918b054b9b3b1d6
Click to expand...
Click to collapse
I have that checksum too but it's not working, maybe it's minimum Android 12?
Edit: Yep! Can the minimum API be lowered to support Android 11?
osm0sis said:
Alpha 4 seems like a bad upload? I have downloaded it a couple times but Android just reports "There was a problem parsing the package"
Click to expand...
Click to collapse
osm0sis said:
I have that checksum too but it's not working, maybe it's minimum Android 12?
Click to expand...
Click to collapse
Yes, I was playing with the new Splashscreen API, which requires Android 12, and I don't have an Android 11 device to test on, so I just set minSdk to 31. I'll see if I can get it to build against something lower.
I pushed a new build that will hopefully work on Android 11. Here are the changes:
lowered minSdk to 30
added vbmeta to raw partition backups
fixed vendor_dlkm map and mount
Click to expand...
Click to collapse
Note: With verity enabled, you may have to unmap vendor_dlkm twice, once for the verity device and again for the actual partition. The partition is remounted without verity, though I'm not sure there's a scenario where it's necessary to remount it at all.
capntrips said:
I pushed a new build that will hopefully work on Android 11. Here are the changes:
Note: With verity enabled, you may have to unmap vendor_dlkm twice, once for the verity device and again for the actual partition. The partition is remounted without verity, though I'm not sure there's a scenario where it's necessary to remount it at all.
Click to expand...
Click to collapse
Thanks! Crashes after the splash screen on my OP8T on OOS11, not seeing anything in the logcat however..
osm0sis said:
Thanks! Crashes after the splash screen on my OP8T on OOS11, not seeing anything in the logcat however..
Click to expand...
Click to collapse
I pushed a new build that hopefully fixes the issue. It now makes it to the point where it requires root to continue on an Android 11 AVD. I assume if it makes it to that point, the rest will work as expected. Anything beyond that, and I'll have to root the AVD to test it (though I did see an article about that a few weeks back, and it seemed simple enough).
Now works on lineage 18.1 Sony xz2 slot a/b device
A few random thoughts/ideas while testing on my 8T :
Got some errors trying to backup on my 8T since there's no vendor_boot, so I guess some logic will be needed for whether they exist.
Probably the feature should be like "backup slot" and save init_boot, boot, vendor_boot, dtbo, recovery, vendor_dlkm and vbmeta from the chosen slot if any of them exist.
If vendor_dlkm doesn't exist on an older device it doesn't make sense to show "Not Found" all over the place, nor offer to allow me to map it, it should hide those messages/buttons and just only show boot or whatever other partitions exist on the device.
If the reboot button had a ... to reveal an advanced reboot menu (menu items like the Magisk app) that would be excellent!
Magisk/RebootEvent.kt at master · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
Magisk/XSU.kt at master · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
Overall looking really good! Exciting to see a well written free alternative.
osm0sis said:
A few random thoughts/ideas while testing on my 8T
Click to expand...
Click to collapse
All good ideas. Probably good enough to check by path for the existence of a partition, rather than finding and parsing fstab. My next two weeks are brutal, but I'll see if I find some time to fiddle with it in there.
When you have time to work on the next update, would it be possible to make boot image flashing possible (External ones, not just saved backups), as well as zips?
shoey63 said:
When you have time to work on the next update, would it be possible to make boot image flashing possible (External ones, not just saved backups), as well as zips?
Click to expand...
Click to collapse
The backup format is very basic. You could easily drop the image you want into the backup folder and create the properties file. I'll take a look at adding something to simplify direct flashing in the next few revisions. I'm out of pocket through the weekend and will probably need a few days of catch-up when I get back.
----- posted in error ------
can I flash an uncompressed boot.img file with this app? the github only mentions flashing an AK3 zip file, so I was curious
sorry, I see the other reply. I'm hoping this app gets this feature in a future update soon. making a video about this app right now
Doesn't open up on Pixel 6. Anyone has a similar problem?
radekmazur said:
Doesn't open up on Pixel 6. Anyone has a similar problem?
Click to expand...
Click to collapse
Does it throw an error message? If not, is there anything in the logcat?

General [Kernel][Kali-NetHunter]Pixel 6/Pixel 6Pro Oriole/Raven[Kernel][Kali-NetHunter]

{
"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"
}
With Great power comes great responsibility.
Disclaimer::
Please use this Kernel in accordance with local law and with the privacy of yourself and others in mind. Not responsible for any charges you might accrue, bail money or fines if you choose to use it for unlawful reasons
Warning your warranty is now void. Do this at your own risk. The mad clown is in no way responsible for the chaos, worldwide disease, nuclear destruction, laughing fish, costumed caped crusaders or damage caused to your device by performing the steps involved.
The mad tech clown is back with another Kernel for all of the Kali-linux-nethunter users wanting the portability of kali-nethunter for their Pixel 6 and 6Pro devices codenamed Oriole and Raven .
I now bring you the
Mad-Kali-Maxhunter kernel for raviole
Some of the features include:
-power efficient workqueues
-fsync switch
-boeffla wake lock blocker
-force usb fastcharge
-mm: oom_kill: Reduce some verbose logging
-cpufreq: add cleanslate battery optimizer feature
-/dev/tmp and /dev/tmp/ mount
-full bluetooth support
-Wifi injection
-dvb / sdr support
Plus:
-Everything neeeded to use kali properly on your device plus some systemd stuff
-dns resolver support
-full usb/otg support
See source commits for more
This is not a super fancy pot luck kernel with every allowable feature. This is tuned out quite effeciently and ive found that adding certain features or too many causes heat to rise and we all know thats not good with this device.
Source
GitHub - Biohazardousrom/android_kernel_google_raviole
Contribute to Biohazardousrom/android_kernel_google_raviole development by creating an account on GitHub.
github.com
Download
16.68 GB folder on MEGA
74 files and 20 subfolders
mega.nz
How to Flash:
pre-requisites:
Franco Kernel Manager & root
Download zip to the internal storage of your device.
Open FKM and tap 3 line menu and choose flasher.
Choose manual flash and navigate to the zip file, select it and choose reboot after flash.
Enjoy
For more support
gs101 and gs201 development/support
Pixel 6/pro & 7/pro discussion group for general support and development
t.me
Thanks to
acuicultor
freak07
tbalden
arter97
andip71
for all your development
reserved
Some notes to help you get the Kali-nethunter system set up on your device.
1. Please install the Kali-nethunter magisk modules. These will have the firmwares needed to use the various USB dongles for wifi/bluetooth.
2. Visit this site to download and install the Kali-nethunter store https://store.nethunter.com/en/
3. After installing the store app let it update and then install these 3 apps
-Kali-nethunter installer updater and interface (aka kali-nethunter gui)
-Kali-nethunter terminal
-Kali-nethunter bvnc and kex manager
once installed open the kali gui app and ok any permissions it asks for. it will then force close.
Note:: Since android 12 the gui quit asking for several permissions needed for running scripts in the terminal so you will need to download the attached file kadb.sh to your pc then connect your device to the pc and open a command prompt and run
./kadb.sh
this will grant the missing permissions and allow the gui to open again without it force closing. script was written for linuxed based pc's. if you use windows just open it up and copy and paste the comnands one by one.
or if you have another rooted device you can connect the two via otg and run from the extra rooted device
4. open the gui app once more and navigate to install and start chroot. if you have your own just add the location to the given box when you choose install. for everyone else let the app download it and install from the Kali repository.
Note:: this will take some time please do not exit the app while in the process of downloading or installing
5. to make it easier to enter the kali nethunter terminal app create a custom comnand in the gui. it can be anuthing ls, apt-get update just what ever. then save it to kali and use it when ever you want to use the terminal
Note:: If you want to use the Kex manager/vnc you will need the root password to run programs as root. That password is toor.
Also you can activate wlan0 and wlan1 without a usb dongle. But for some reason it wont allow use of bluetooth without a dongle. i never could find a rhyme or reason for this but i have found when using bluetooth on my pc that kali would not use the built in bluetooth either and i would have to use a dongle. this is probably by design for stealth reasons but dont quote me.
I have found dual wifi and bluetooth adapters in the past and they work simultaneously
This is great! Will it be possible for you to share the kernel build instructions here? I cloned you repo into private/gs-google and ran BUILD_KERNEL=1 ./build_slider.sh -j$(nproc) after that. I do see the kernel files in out/mixed/dist. I flashed them, and it gave me boot loops.
It would be awesome if you could share some build instructions as well.
you can find more info on building kernels here....
Building Kernels | Android Open Source Project
source.android.com
but the steps i took were to initialize and sync the repo listed in the link above. then from there i made my cherry picks. next i went to /arch/arm64/configs and edited the gki_defconfig to match the needed configs i needed for kali linux. after that i ran build/build.sh.
it will error after that because the abi_symbol_allowlist in /android/abi_gki_aarch64_generic file will need updated with the new symbols now compiled in the newly customized kernel.
then after you have corrected all the errors and its built a kernel you will have 4 items to flash..
boot.img
dtbo.img
vendor_boot.img
vendor_dlkm.img
dtbo and boot are flashed in fastboot while vendor_boot and vendor_dlkm are flashed in fastbootd.
but the easiest way to flash is by making an anykernel.zip
also need to point out that some custom roms will not allow you to flash custom kernels so i would hop on tg and ask the maintainer if that rom permits flashing kernels else your gonna have a hard time
thanks for the build @Duhjoker. I managed to flash it on a Pixel 6 and install NetHunter but wifi monitoring mode doesn't work. This is the output from `airmon --debug`
Hey Duhjoker! Thanks for your work on this! Its a dream come true! I just have one question. Is there any chance we will see a pixel 6a version of this kernel with wifi injection? Or is this a pipedream?
evansfromza said:
thanks for the build @Duhjoker. I managed to flash it on a Pixel 6 and install NetHunter but wifi monitoring mode doesn't work. This is the output from `airmon --debug`
View attachment 5705665
Click to expand...
Click to collapse
i am aware of the problem and im looking into it. to be honest i never could get airmon-ng to work on any android.
im thinking monitor mode may need to be enabled first through /sys/ like qualcomm but i could be wrong. this is my first exynos kernel and im having to relearn stuff.
gahndii said:
Hey Duhjoker! Thanks for your work on this! Its a dream come true! I just have one question. Is there any chance we will see a pixel 6a version of this kernel with wifi injection? Or is this a pipedream?
Click to expand...
Click to collapse
I can but i dont own a pixel 6a. The build would have to completely blind but if your willing to test i can try. i did the same for the pixel 3 so it shouldnt be a problem but read next post to see whats up on the current state of building
ok so i dont know whats up with android 13 kernel source but so far none of the builds are booting. ive been at it since release and no go.
but be assured i am working on stuff
Duhjoker said:
I can but i dont own a pixel 6a. The build would have to completely blind but if your willing to test i can try. i did the same for the pixel 3 so it shouldnt be a problem but read next post to see whats up on the current state of building
Click to expand...
Click to collapse
Though I wouldn't mind testing something like that, however would not consider myself a reliable tester. I'm more of a tinkerer honestly. I haven't flashed a rom in 4-5 years haha I gave up years ago on a kernel with wifi packet injection drivers baked in. (for a model I owned) I would not be able to give you solid reliable feedback but id happily try it out for fun. From what ive been reading looks like im staying on Android 12 for a bit longer.
The ramdisk provided by Google for A13 is the issue, you must extract it from vendor_boot and replace it inside prebuilts folder, thanks to freak07 for the solution.
Here's the commit from him.
acuicultor said:
The ramdisk provided by Google for A13 is the issue, you must extract it from vendor_boot and replace it inside prebuilts folder, thanks to freak07 for the solution.
Here's the commit from him.
Click to expand...
Click to collapse
Thank you so much for that. it was driving me crazy and couldnt understand what the problem was.
so now we have kali coming for a13 in a couple days
ok guys Mad-Kali-MaxHunter-Raviole-T for android 13 is now live and linked in op.
I have been researching the wifi monitor mode and packet injection properties on the wlan and heres the state of the driver from my google searches
The bcm4389 wifi 6e client set of chips was announced in 2020 by broadcom and can be found in the Samsung galaxy s21 and google pixel 6, 6pro and 6a models along with some xiaome phones.
For us that means that the drivers and firmware are so new that theres been very little development for it. i myself was only able to find a bluetooth patch that im sure has already been picked up by the google source kernel devs.
from what i can tell of the other drivers by looking at the nexmon github page and further reading the previous wlan modules needed patched firmware to enable airmon-ng.
im still doing research into how to fix this but if anyone has any clues please speak up.
but for now if you should be able to get by using a usb wifi dongle.
Hi, @Duhjoker I was able to install everything successfuly but it seems like the kernel is missing some features not directly related to Kali but that would be nice to add.
HID attack support from Rucky, and ISO usb host from DriveDroid.
I'm using a Pixel 6 Pro on A13
Thanks for your work
Unfortunately, usb wifi dongles aren't working even if they're supported, even after installing their firmwares. Something's wrong with the kernel.
I have good news. Seems google did the hard work for us on hacking the firmware for monitor mode and it looks like we can now use monitor mode to catch packets "NATIVELY".
please read here for the details.
Get BCM4389 into monitor mode for WIFI sniffing
Hey all, I was trying to watch beacon frames transmitted by my access point, but had no capable hardware in my house to sniff it. Or did I? Turns out, Pixel 6 / Pixel 6 Pro can do it. Here's my howto...
forum.xda-developers.com
i havent tested this fully yet but a friend in my tg chat helped me snag the binaries rc files and best of all the firmware.
i dont currently have a magisk module yet but with root copy the vendor folder in the zip to /data/adb/modules pick any module for example
/data/adb/modules/busybox-ndk/system
reboot and enjoy
edit: you made need to chmod the binaries after placing them
deleted
tried that, it doesn't work.
also, wifi dongles are recognized by lsusb but not mounted (airmon-ng only shows phy0 - internal wlan interfaces)

Categories

Resources