Database Develop

[TOOL] Android commander. ADB App/file manager/installer for windows

NOT TO BE CONFUSED WITH ANDROID CONTROL ON THE PORTAL TODAY
Check out this awesome tool!
install and adb/sqlite/apksigning files at bottom put together by me for you!
http://androidcommander.com/
http://forum.xda-developers.com/showthread.php?t=597098
Program Features:
Explore files:
- copy multiple files/dirs between Phone and PC
- copy multiple files/dirs between Phone folders
- delete multiple files/dirs from Phone
- new dir and rename options
- drag&drop multiple files/dirs in to progrm
- drag&drop files/dirs between program tabs
- partitions size info
- bookmarks
Manage apps:
- windows integration WINDOWS WILL "know" apk files! double click to install to phone!!!!!
- backup multiple apps to any dir on Phone/PC
- batch/single apps install
- install as private
- install on SD (Froyo+ only)
- update app
- batch/single uinstall apps
- uninstall with option to keep data or not
Console:
- type any shell command
- run sh script from PC
and more...
- flashing zip and img files
- options to reboot, reboot to recovery, reboot to bootloader, power off device
- device screenshots (beta)
- signing apk/zip files
{
"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"
}

Looks like just what I needed, huge THANKS!

Looks awesome. I wish that my PC (or my brain) wasn't broken.
I haven't been able to get ADB (of any kind, from any source) to run on my win7 64 bit machine...ever. I've had the SDK installed for a while now and have tried several times to get ADB working- today is no different.

Try the adb setup link in my sig!
But you don't need to know how to use adb to use this program

Edit: I got it. The link in your sig is what saved me. Checking this out now. Thanks!!

Well it work with windows xp?
Sent from my GT-I9000 using XDA Premium App

leezrd said:
Well it work with windows xp?
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
well the site only says you need " Windows "
so probably.. no harm in trying...

TRusselo said:
well the site only says you need " Windows "
so probably.. no harm in trying...
Click to expand...
Click to collapse
Ok well thanx for helping with this wether works or not
Sent from my GT-I9000 using XDA Premium App

sorry but i dont have xp to try it and the authors website quoted in first post only says windows, im sure if there was more of a requirement he would have said so.
it runs on my win7 64x and that is usually the last supported windows so i would think xp is ok...

Doesn't recognize my phone. Droid Explorer does but this didn't. I already have adb installed on my win 7 64bit laptop.

did you point the program to where adb is installed?

TRusselo said:
did you point the program to where adb is installed?
Click to expand...
Click to collapse
Yes I did. Not sure why it won't recognize my phone.

Trouble getting hard adb root on Captivate GB 2.3.5 ROM
Android Commander 0.7.9.9 at http://androidcommander.com/ xda link http://forum.xda-developers.com/showthread.php?t=597098
I have a Samsung Captivate running a modified stock leaked GB 2.3.5 One flash ROM that has been Fugu rooted. TiBU, Rom Toolbox and other Super User apps all work.
So this program by PanPiotr looks like just what the noob in me is after, and I'm sure a few others out there too.
Once installed the program seems to be fine. I have one problem that I can't seem to overcome. That is getting a hard or adb root on the phone. I have tried to follow the instructions of PanPiotr but I don't have a boot.img file in my nandroid BU as outlined in his FAQs. Only cache.img, data.img, sd-ext.img and system.img I can use unyaffs-windows to extract the files in these but the default.prop appears to be calling to be loaded from ro.com.google.clientidbase=android-samsung, which I can't seem to find.
I can modify the default.prop ro.debuggable=0 to =1 with root explorer but just doing it in the root doesn't help. I can't seem to find out which IMG file in my nandroid BU has or how to modify the default.prop file loader to get the ro.debuggable=1 to take or stay.
Consequently the Root Access indicator always says Root Access:NO
Any help would be appreciated.
TYIA
Bud

May have this worked out.
So I flashed a custom rom and kernel. Connected Android commander to phone and I have Root access:OK. Program works great. Thanks PanPiotr.
On the brighter side of all this while in recovery mode of the new kernel (CornKernel_UCKJ3_v403) I found a way of switching the toggle for debugging enabled to on if that kernel works with the rom I was on then that will work. It should so I'll give that a try and let you know.
EDIT:
So I just finished and this worked brilliantly. Hope it helps someone else.
Bud

WOW nice tool very needed
+1
please add option for screen shots for more resolutions
Or to manually edit screen size CUSTOM.
I am using this on my sensation and image is captured but due to wrong resolution rows are shifted
Nice app bro.

Open Source CM10.1 for Dell Streak 7 continuation, and some helpful setup info.

Okay if you do some work to make your Dell Streak 7 work right with the AOKP 4.2.2 here.
Everything you needed is linked in this post to get you up and running with 4.2.2.
Now for the stuff you need to do to make your 7 run big apps like this Rich! Free Casino Slots okay.
First once you have setup you install of 4.2.2 goto system settings. from there goto Developer options.
Once there goto Force GPU rendering and check that.
Now go get Memory Manager from the play store.
Now once you have that running set it's presets to Aggressive.
Once that is done check the Apply at boot.
Now head over to get Trickster MOD Kernel Settings from the store.
Now that you have that start it up and goto General tab.
In there set the I/O Control Scheduler to noop.
Then goto in the same tab, CPU Governor Control and set the Governor to smartassV2.
Now you can try playing around with overclocking the CPU, but I have found most of the 7's don't like anything over 1 GHz top end due to voltages.
But try at your own rick.
Anyway once you have those set then click the first app setting in the upper right and of the app.
Once in there set all of the On Boot setting to on i.e. check them all.
Now you can play with the delays but I have found if they are set to 0 it works better, don't ask why.
Now that we are done with that app the next app to get is Zram Settings Free.
Now once you have that installed.
open it up and check all the check marks you can. DON'T REBOOT THE SYSTEM YET.
Now close that out.
Now get Root Browser.
The reason for this app over others is because this one when it opens and edits files or makes new files or folders will make them so that Android will like them.
Because the next part is only for the brave of hart and mind. LOL
Okay open up Root Browser and get it setup.
Next head to /etc/sysctl.conf file. Open it up and add this to the last of the file.
vm.swappiness = 90
Click to expand...
Click to collapse
or what ever you like from 1 - 100. I set it to 90 so that my system will load most big apps. With out to much lag.
Now that is done and the file saved.
here come the real fun part.
Next head over to Terminal and open it up.
Now in here we put.
su
mount -o rw,remount /dev/block/platform/sdhici-tegra.3/by-name/APP /system
TARG=/system/.swapfile
dd if=/dev/zero of=$TARG bs=$((1024*1024)) count=400
Click to expand...
Click to collapse
The count=400 part is the size of the swap file we are setting up in the /system folder. So if you want something bigger then that put it in as a MB at the count part.
mkswap $TARG
chmod 600 $TARG
Click to expand...
Click to collapse
The last part sets the new swap file to root only keeps it from being deleted.
swapon $TARG
free -m
Click to expand...
Click to collapse
The last two things do this.
1: it tells Android to use the new file as swap.
2: should show you a 400MB size swap file being used.
Now to get this all to restore it's self after a reboot we are going to need to do a bit more, but it's fast should be the end of this.
Okay before we try a reboot head back over to the Play Store one more time and get yourself.
Script Manager - SManager
Now once you get this app setup we are going to make a .sh file.
A .sh file is a shell script file for *inux based systems. Yes that's OS X no matter what apple wants you to think other wise.
Okay to make this file open SManager
Then hit the menu key, then tap new script.
Name it what ever you would like. I called mine swap.sh
Next use the TB editor.
It should have this in the window to start with if not put it in.
#!/system/bin/sh
Click to expand...
Click to collapse
Now the next part to make this all work right.
TARG2=/system/.swapfile
mount -o rw,remount /dev/block/platform/sdhci-tegra.3/APP /system
swapon $TARG2
Click to expand...
Click to collapse
Now once that is saved in your internal SDCard then tap it and then tap the root icon and the boot icon.
Now when you reset the tab it can take up to 2 minutes to fully load out but now swap will be running and the tab will be fast and big apps like games and Netflix should load and work. Now I have only tested this on game like Hit It Rich or Fast 6. I have yet to try it with Netflix so don't blame me if it still don't work.

Can you show your swap output, I cannot remember if I even enabled that option in the kernel.

giveen said:
Can you show your swap output, I cannot remember if I even enabled that option in the kernel.
Click to expand...
Click to collapse
Here is the Terminal output as you asked. As you can see it's working with a swap file.
I have been unable to get it to work with a swap portion be it on the main internal SD Card or on an Ext SD Card.
I'm thinking that it may have something to do with the way Dell did there mounting system, but I have never really been a kernel guy.
{
"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"
}
Here is reading from ZRam Setting app.
And here is some more info for you to look at.
Now I only put the file in the system folder because when it was on the SD Cards it would do things to the system that was not good.
That and I kept losing data on the cards.
So I put the swap file in system folder and the script I put in /data/scripts/. The scripts folder I made.
That way when I did my Nandroid backups I would always have the file and scripts.
Any help you could give me to get my script to run at boot with indit.d would be great as I know android don't really have cron in any working form.

michaelcrossland said:
Here is the Terminal output as you asked. As you can see it's working with a swap file.
I have been unable to get it to work with a swap portion be it on the main internal SD Card or on an Ext SD Card.
I'm thinking that it may have something to do with the way Dell did there mounting system, but I have never really been a kernel guy.
View attachment 2901112
Here is reading from ZRam Setting app.
View attachment 2901113
View attachment 2901114
And here is some more info for you to look at.
View attachment 2901115
View attachment 2901116
View attachment 2901117
Now I only put the file in the system folder because when it was on the SD Cards it would do things to the system that was not good.
That and I kept losing data on the cards.
So I put the swap file in system folder and the script I put in /data/scripts/. The scripts folder I made.
That way when I did my Nandroid backups I would always have the file and scripts.
Any help you could give me to get my script to run at boot with indit.d would be great as I know android don't really have cron in any working form.
Click to expand...
Click to collapse
Tutorial [Guide] [Dec.15] How to Tweak and Mod Android Using Init.d Scripts
and, in the jb defconfig,
CONFIG_SWAP=y

Thanks for that link. But it don't help with showing how to make the script do anything that would need SU rights to do.
My script need to be ran as root. But thanks for the info.
And as far as your 2nd part. That's great for that info but what *.conf file does that setting need to be put into?
Sent from my Streak 7 using XDA Premium HD app

michaelcrossland said:
Thanks for that link. But it don't help with showing how to make the script do anything that would need SU rights to do.
My script need to be ran as root. But thanks for the info.
And as far as your 2nd part. That's great for that info but what *.conf file does that setting need to be put into?
Sent from my Streak 7 using XDA Premium HD app
Click to expand...
Click to collapse
I though all init.d scripts ran as root. Why not try it and see?
the second part, is from giveen's github kernel source, and unless the one built into your ROM uses another defconfig, you do have swap enabled.
in terminal, as su, zcat /proc/config.gz > /sdcard/config.txt
then you can look for SWAP in the text file and see what it's currently set to. You can't change whether swap is enabled or not without rebuilding the kernel.

This is after attempting to flash the test kernel.

ElfinJNoty said:
This is after attempting to flash the test kernel.
Click to expand...
Click to collapse
My kernel already has it on, no need to flash any other kernel
https://github.com/giveen/kernel_dell_streak7/blob/cm10.1/arch/arm/configs/streak7_jb_defconfig

giveen said:
My kernel already has it on, no need to flash any other kernel
https://github.com/giveen/kernel_dell_streak7/blob/cm10.1/arch/arm/configs/streak7_jb_defconfig
Click to expand...
Click to collapse
Has what on?
As far as I know, with @bigsupersquid helping, the kernel is missing some things
Like proper modules for logging
If swap is on already, that's good to know...
bigsupersquid was trying to help me make a new kernel, blindly. But could never compile it correctly to be a flashable zip or fastboot the IMG.
@giveen, think we tried to reach out to you via pm

giveen said:
My kernel already has it on, no need to flash any other kernel
https://github.com/giveen/kernel_dell_streak7/blob/cm10.1/arch/arm/configs/streak7_jb_defconfig
Click to expand...
Click to collapse
ElfinJNoty said:
Has what on?
As far as I know, with @bigsupersquid helping, the kernel is missing some things
Like proper modules for logging
If swap is on already, that's good to know...
bigsupersquid was trying to help me make a new kernel, blindly. But could never compile it correctly to be a flashable zip or fastboot the IMG.
@giveen, think we tried to reach out to you via pm
Click to expand...
Click to collapse
I built from that repo with that defconfig.
Not surprising that's what's in the ROM already.
Just couldn't recombine the boot.img in a way that the streak would accept.

You need more than the kernel to build a boot.img that the DS7 will take.
Steps:
1. Download CM10 (or CM10.1 or CM10.2)
2. Download the device tree AND the kernel tree from github
3. Place device tree in source/device/dell/streak7
4. Place kernel in source/kernel/dell/streak7
5. Run "make boot"
6. Fix any compile issues that come up
.....
10. Profit.

giveen said:
You need more than the kernel to build a boot.img that the DS7 will take.
Steps:
1. Download CM10 (or CM10.1 or CM10.2)
2. Download the device tree AND the kernel tree from github
3. Place device tree in source/device/dell/streak7
4. Place kernel in source/kernel/dell/streak7
5. Run "make boot"
6. Fix any compile issues that come up
.....
10. Profit.
Click to expand...
Click to collapse
I was trying instead to split and recombine the cm10.2 boot.img.
Got a readable ramdisk out of it, but when recombined with the new kernel with abootimg (or perl tools, or mkbootimg) I ended up sending off unbootable images. They stuck at the logo I believe.
I don't have a cm10 tree... just cm11. running out of hard drive space, too. But I appreciate the specific info on how to fix the problem. Thanks.

bigsupersquid said:
I was trying instead to split and recombine the cm10.2 boot.img.
Got a readable ramdisk out of it, but when recombined with the new kernel with abootimg (or perl tools, or mkbootimg) I ended up sending off unbootable images. They stuck at the logo I believe.
I don't have a cm10 tree... just cm11. running out of hard drive space, too. But I appreciate the specific info on how to fix the problem. Thanks.
Click to expand...
Click to collapse
I just put my streak on the charger.... Just in case

bigsupersquid said:
I was trying instead to split and recombine the cm10.2 boot.img.
Got a readable ramdisk out of it, but when recombined with the new kernel with abootimg (or perl tools, or mkbootimg) I ended up sending off unbootable images. They stuck at the logo I believe.
I don't have a cm10 tree... just cm11. running out of hard drive space, too. But I appreciate the specific info on how to fix the problem. Thanks.
Click to expand...
Click to collapse
CM11 is a whole 'nother animal, as CM changed a lot of things with the bootup files and how the disks are partitioned/mounted.

DJ Steve and I have an updated kernel for the cm10.1(really an aokp 10.1) ROM by Giveen that is optimized and increases available memory by about 70mb. Amazing how much improvement off of more available ram. Continuing to test and implement changes and add in features. Also working to convert for bootable lollipop ROM.... Stay tuned:
http://forum.xda-developers.com/showthread.php?t=3330564

I think its awesome that you guys are progressing so quickly! Picking up the torch and finishing the race!

How to dual boot on me176cx part 1

This is only first part. In this part, I will NOT mention any OSes. I will teach you how to run rEFInd on this device.
In other parts, I will edit rEFInd's config file to make it really "work". BUT, after this tutorial, you may fell happy that dual boot will most likely work on the device you just hod in your hands.
This guide is for me176cx only. Steps for other devices may be similar, only try to do this on other devices if you are sure you know where the differences are and how to change the commands!
So let's begin!
My tablet before doing anything
{
"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"
}
on http://www.rodsbooks.com/refind/getting.html , click on get binary zip file
Extract the downloaded zip
look for the folder "refind" inside the extracted folder
////////////////////////////////////////////////////////////////////////////
Now, we need to move it to Efi System Partition.
Istall busybox. Then, install Android Terminal Emulator.
Using some file browser with root rights, make a folder in the root of your device's memory called "esp"
Then, mount Efi System Partition on it:
Run the Android Terminal Emulator, type su, and confirm the SuperUser dialog.
Then, type: busybox mount /dev/block/mmcblk0p3 /esp
it should have no output.
Then, copy the "refind" folder to file system root.
Then (using terminal emulator) copy the refind folder to the ESP.
Then, make sure it is really there
Then write: busybox umount /esp
///////////////////////////////////////////////////////////////////////
Now, add rEFInd's binary to bootorder and set the bootorder to !!!NOT!!! boot it first, becouse you have to test it first (and you do not want to run and buy the first powered hub to be able to get back in android some complicated way)
Download this file and move it to some location where you will execute it from:
http://forum.xda-developers.com/showpost.php?p=62429430&postcount=2740
(Thanks to social-design-concepts for compiling this to work on android)
Issue this command (the paste function does not work in terminal emulator so you have to rewrite it by hand)
Then, make sure the path is set well:
Then, set the boot order to boot Android first by ./efibootmgr64 -o 0001,0000
Then, set the next boot (only next boot) to rEFInd
////////////////////////////////////////////////////////////////////
Now, just power off the tablet, (do not restart) and power it on again. You will see rEFInd, but you cannot do much without powered hub.
So if you have one, look around with keyboard. If you do not have one (like me), just power off the tablet by holding the power button, power it on again and wait for the next part of this tutorial
EDIT:
tuxic001 edited rEFInd binary so you can select what to boot.
http://forum.xda-developers.com/showpost.php?p=62463032&postcount=60
\\\_///
P.S If you use nandroid backup to update, you only update kernel and ROM (or recovery, fastboot, esp partition and whatever the other partitions are), depends on what you backup. And I don't think UEFI is stored on EMMC, so if UEFI update (or bootloader, recovery, etc. update) is present, you are totally ignoring it. On the other hand, UEFI update is a risk of not being able to access it..

Is refind working with touch or volume\power keys?

A powered hub is non-optional. OTG power is super finicky on this tablet, especially if you're adding a flash drive on top of mouse and KB

t68kv said:
Is refind working with touch or volume\power keys?
Click to expand...
Click to collapse
Voume keys work, but power key doesn't. But tuxic001 is working on editing the source code so it will. Maybe tomorrow this time it will work

Good And Bad news
Which you want to hear first?
Look fo EDIT in the main post.

I also got my tablet down, it boots only to UEFI as there's no efi bootloader to load anymore.... I'll run and get a powered usb hub to try to use the UEFI, cause the vol keys don't cut it.

Awesome guide @Mis012. I got it working on my Lenovo Tab S8-50F.
Did you have a chance to try dual booting anything yet?
EDIT: Making progress

Shump said:
Awesome guide @Mis012. I got it working on my Lenovo Tab S8-50F.
Did you have a chance to try dual booting anything yet?
EDIT: Making progress
Click to expand...
Click to collapse
Yeah I have run grub 2, it was nice. I got stuck somewhere in kali linux booting process, and then ubuntu-based dostros said bad kernel magic number blah blah. So I tried abother grub. First I found was nice, but still not working with ubuntu. So I tried to use ununtu's grub. It didn't show up in rEFInd. Now I can't find the good grub again What about your progress? Did you need to use powered OTG cable?
EDIT: found working grub again, kali linux stuck at this error: http://unix.stackexchange.com/quest...o-find-a-medium-containing-a-live-file-system

Any new?? This tutorial works on Lollipop?? If do this tutorial exist any risk for example brick??
Can you do a tutorial and upload to youtube??
or someone explain me the process?
Thanks in advance.:good:

I get invalid argument on the first command lenovo tab s8

Somewhat more wrong the error invalid argument to execute the first command and at least a thousand times but nothing works I have root and I do everything to the letter I tried on the asus tablet of the same model and my Lenovo Yoga Tab 3 and same error

jet_98 said:
Somewhat more wrong the error invalid argument to execute the first command and at least a thousand times but nothing works I have root and I do everything to the letter I tried on the asus tablet of the same model and my Lenovo Yoga Tab 3 and same error
Click to expand...
Click to collapse
have you installed busybox? as simple as that.

Windows ARM64 on fajita

{
"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"
}
oneplus 6/6t 都可用
警告！不当操作可能会导致手机变砖！
-
20210822 updata
-
project address : https://github.com/edk2-porting
and
Tool download :https://drive.google.com/drive/folders/1GrX9JTVpKwo3WNshqIljPRc9Q6dPJDJJ?usp=sharing
boot download : https://github.com/edk2-porting/edk2-sdm845/releases/tag/v1.0.2
drives download : https://github.com/edk2-porting/WOA-Drivers/archive/refs/heads/main.zip
-
Installation tutorial
new tutorial!(English) https://forum.renegade-project.org/t/faq/95
-
article(Chinese) : https://forum.renegade-project.org/t/6-windows/194
-
Device support status
Renegade Project
Renegade Project
renegade-project.org
-
The drive is gradually improving
有问题我会不定期来看的，欢迎提问。
Questions are welcome

How are you doing with the driver ports. Nice work tho!

Keno_I said:
How are you doing with the driver ports. Nice work tho!
Click to expand...
Click to collapse
The driver is currently only basic
Such as wifi, GPU, battery, etc. are all unavailable
But this will gradually improve in the future!
-
驱动目前只有基础的
比如wifi,GPU,电池等都是不可用的
但这会在之后慢慢完善！

Nice. Good work on that, I'm assuming this port will be easier when windows arm devices get more widespread and supported

Good work. This is really great.
Will try that out the next days.
One thing I am just wondering.
How is it handled to boot Windows and Android?
So when you boot up the phone will it boot to Windows or to Android?
Or will it boot to Android and to boot to Windows you will need to fastboot the boot-fajita.img again?
Thanks!

Given it a go, it's not going bad is it? Very nice.
It took a while to set up so I wrote some scripts to partition and boot to recovery, along with scripts within recovery to deal with bootloader config. The only thing that wasn't automatic at this point was running DISM++
Good work. This is really great.
Wishmasterflo said:
Will try that out the next days.
One thing I am just wondering.
How is it handled to boot Windows and Android?
So when you boot up the phone will it boot to Windows or to Android?
Or will it boot to Android and to boot to Windows you will need to fastboot the boot-fajita.img again?
Thanks!
Click to expand...
Click to collapse
By default it will boot Android, unless you flash the windows bootloader img to boot.
I cannot recommend flashing the windows bootloader img at the moment- it worked and windows boots by default but from this point on I was unable to start TWRP, even via fastboot boot, so I'll have to MSM tool it to restore, which *does* wipe windows.
Other thoughts: This is almost usable, however, battery drain is through the roof and the touch screen driver is misconfigured for the display, so touch events are in the wrong place.
Keep going guys!

damiensturdy said:
Given it a go, it's not going bad is it? Very nice.
It took a while to set up so I wrote some scripts to partition and boot to recovery, along with scripts within recovery to deal with bootloader config. The only thing that wasn't automatic at this point was running DISM++
Good work. This is really great.
By default it will boot Android, unless you flash the windows bootloader img to boot.
I cannot recommend flashing the windows bootloader img at the moment- it worked and windows boots by default but from this point on I was unable to start TWRP, even via fastboot boot, so I'll have to MSM tool it to restore, which *does* wipe windows.
Other thoughts: This is almost usable, however, battery drain is through the roof and the touch screen driver is misconfigured for the display, so touch events are in the wrong place.
Keep going guys!
Click to expand...
Click to collapse
Great. Thanks for the answers. I will try that out as well.
I saw in the Tools folder there is a file "TouchScreen.reg" . Does that not fix the touchscreen issues or what does that do?

Wishmasterflo said:
Great. Thanks for the answers. I will try that out as well.
I saw in the Tools folder there is a file "TouchScreen.reg" . Does that not fix the touchscreen issues or what does that do?
Click to expand...
Click to collapse
Actually, the last time I did it I didn't have any touchscreen issues- I must have skipped the reg file!

I just bought a USB-c HUB to connect Mouse, keyboard, USB stick to my phone when setting this up.
So if I see this correct now and the boot file can only be booted via Fastboot and flashing it to boot is not recommended due to issues to boot TWRP afterwards there is no way now to boot that without having the phone connected to a Computer or?
OK I gave that a try now. I could boot to the EFI environment and tried to apply the Windows 11 arm64 image in Dism++.
After done the steps to select the ISO file and target C: it starts to copy files and after like 1 minute I get an error Message but all the text in the message is in Chinese letters so I dont know what the error means.
How can I set the language in Dism++ to english?
Thanks!

Wishmasterflo said:
我刚买了一个 Usb - c Hub 来连接鼠标， 键盘， Usb 粘在我的手机上， 当设置这个。
因此，如果我现在看到这个正确的启动文件，并且引导文件只能通过 Fastboot 启动，并且由于启动 TWRP 的问题而不建议将其闪烁到启动，那么现在没有办法启动该启动，而没有将手机连接到计算机或？
好吧， 我现在试了一下。我可以启动到 EFI 环境，并试图应用 Windows 11 手臂 64 图像在 Dism+.
完成选择 ISO 文件和目标 C 的步骤后：它开始复制文件，1 分钟后我收到一条错误消息，但邮件中的所有文本都以中文字母表示，因此我不知道错误是什么意思。
如何将 Dism+中的语言设置为英语？
谢谢！
Click to expand...
Click to collapse
Sorry for taking so long to reply you But this software seems to be only in Chinese

hehedi233 said:
View attachment 5390973Sorry for taking so long to reply you But this software seems to be only in Chinese
Click to expand...
Click to collapse
Thanks for the reply.
I guess Dism++ is taking the language settings from the Windows PE or boot.img and therefor it is set to Chinese.
I see when booting up the img file that that is set to Chinese. So if that can be changed to English I guess the Dism tool will be english aa well.

Wishmasterflo said:
Thanks for the reply.
I guess Dism++ is taking the language settings from the Windows PE or boot.img and therefor it is set to Chinese.
I see when booting up the img file that that is set to Chinese. So if that can be changed to English I guess the Dism tool will be english aa well.
Click to expand...
Click to collapse
you can go online to find the English version of Dism++, and then pass it in via USB disk

hehedi233 said:
you can go online to find the English version of Dism++, and then pass it in via USB disk
Click to expand...
Click to collapse
I already did that but it is in Chinese as well after launching it when booted the boot.img file therefor I guess it it fetching the language setting from the booted IMG or WinPE already.

Wishmasterflo said:
I already did that but it is in Chinese as well after launching it when booted the boot.img file therefor I guess it it fetching the language setting from the booted IMG or WinPE already.
Click to expand...
Click to collapse
If you downloaded the windows that I uploaded, it is the Chinese version, you can go to uupdump to download the corresponding version of windows. Note that it is arm64

hehedi233 said:
If you downloaded the windows that I uploaded, it is the Chinese version, you can go to uupdump to download the corresponding version of windows. Note that it is arm64
Click to expand...
Click to collapse
Yes that I already did. Its more the WinPE which is in Chinese causing that Dism++ is launching in Chinese as well.
So I assume when I push the English WinPE files/Version to my phone I will have everything in english then and Dism++ will launch in English as well.
Can you provide WinPE in english?

Wishmasterflo said:
Yes that I already did. Its more the WinPE which is in Chinese causing that Dism++ is launching in Chinese as well.
So I assume when I push the English WinPE files/Version to my phone I will have everything in english then and Dism++ will launch in English as well.
Can you provide WinPE in english?
Click to expand...
Click to collapse
winpe-EN.7z
drive.google.com

I laughed when I saw the BSOD
---
当我看到死亡的蓝屏时，我笑了。

[INFO] EDK2 port to Redmi Note 7 to boot Windows

Donate a coffee to support development:
Donate via PayPal to serdeliuk
_______________________________
[UPDATE 22 Jan 2022]
- partial fix for ACPI tables which allow to boot windows
- added startup.nsh to automatically run in shell
-----
Hello,
I started to port EDK2 to my Lavender, Xiaomi Redmi Note 7 in order to bring Windows to this device.
So far i was able to fix ClockDxe that makes, for the first time, the eMMC working on a EDK2 port.
The device is able to boot Windows PE from eMMC
I am still working to fix USB for boot, mouse and keyboard in the first phase.
Anyone interested can download my buttons and clocks patches and build his own EDK2 port from my GitHub repo at https://github.com/serdeliuk/edk2-lavender
Best regards,
Marc
{
"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"
}

Enable Debug

hello, I tried to compile, all look normal but on the end this happend
I do not know what is wrong, please can you help me.

Samuel Ladziansky said:
hello, I tried to compile, all look normal but on the end this happend
View attachment 5469915
I do not know what is wrong, please can you help me.
Click to expand...
Click to collapse
Hi,
You may need to edit edk2-lavender/RedmiNote7Pkg/RedmiNote7Pkg.dsc
and uncomment the line below that contain RegisterFilterLib
Code:
[LibraryClasses]
# RegisterFilterLib|MdePkg/Library/RegisterFilterLibNull/RegisterFilterLibNull.inf
VariablePolicyHelperLib|MdeModulePkg/Library/VariablePolicyHelperLib/VariablePolicyHelperLib.inf

serdeliuk said:
Hi,
You may need to edit edk2-lavender/RedmiNote7Pkg/RedmiNote7Pkg.dsc
and uncomment the line below that contain RegisterFilterLib
Code:
[LibraryClasses]
# RegisterFilterLib|MdePkg/Library/RegisterFilterLibNull/RegisterFilterLibNull.inf
VariablePolicyHelperLib|MdeModulePkg/Library/VariablePolicyHelperLib/VariablePolicyHelperLib.inf
Click to expand...
Click to collapse
Thanks I go to try it

Now it compiled and I tried to boot via "fastboot boot uefi.img" but nothing shows, after that I flashed it to boot partition and still nothing, I need put some operating system on some partition because it tries booting something? Or is something other wrong.
Thanks for reply.
Now works I use wrong (older) version of xbl.

Samuel Ladziansky said:
Now it compiled and I tried to boot via "fastboot boot uefi.img" but nothing shows, after that I flashed it to boot partition and still nothing, I need put some operating system on some partition because it tries booting something? Or is something other wrong.
Thanks for reply.
Click to expand...
Click to collapse
I suppose that you have xiaomi redmi note 7 (lavender) right? If so, the uefi.img should properly boot to uefi shell, if you have a fat32 efi partition on your device with windows will try to load that windows, but the actual state of acpi tables freezes windows during boot.
You may need to enable serialframebuffer and properly set the edk2 debug level to see what is going on.

Yes, I have redmi note 7 (lavender), I tried boot windows and what you said happened, windows freze at boot.
And I do not know where I enable serialframebuffer or set that debug level. I gonna try to find it.

Samuel Ladziansky said:
Yes, I have redmi note 7 (lavender), I tried boot windows and what you said happened, windows freze at boot.
And I do not know where I enable serialframebuffer or set that debug level. I gonna try to find it.
Click to expand...
Click to collapse
good, then you need to replace acpi tables from RedmiNote7Pkg/AcpiTables with the ones from msm8998 then modify the edk2- lavender/RedmiNote7Pkg/RedmiNote7Pkg.fdf accordingly, yo ucan take whole acpitable section from msm8998 edk2 port, right now i am not yet done with my acpitable, but that one should work

1. Install dependencies
```
# On Ubuntu 18.04
sudo apt install -y build-essential uuid-dev iasl git nasm python3-distutils gcc-aarch64-linux-gnu abootimg bspatch p7zip-full zip python-pip
```
```
# On Debian 11
sudo apt install -y build-essential uuid-dev iasl git nasm python3-distutils gcc-aarch64-linux-gnu abootimg bspatch p7zip-full zip pip
```
```
sudo pip install uefi_firmware
```
2. Clone edk2 and edk2-platforms repositories
```
git clone https://github.com/tianocore/edk2.git --recursive
git clone https://github.com/tianocore/edk2-platforms.git
```
3. Download Released File and Unzip
```
wget https://github.com/serdeliuk/edk2-lavender/releases/download/2/edk2-lavender.0.0.2.zip
unzip edk2-lavender.0.0.2.zip
```
4. Edit ` edk2-lavender/RedmiNote7Pkg/RedmiNote7Pkg.dsc`. uncomment the line below that contain RegisterFilterLib
```
[LibraryClasses]
# RegisterFilterLib|MdePkg/Library/RegisterFilterLibNull/RegisterFilterLibNull.inf
```
```
[LibraryClasses]
RegisterFilterLib|MdePkg/Library/RegisterFilterLibNull/RegisterFilterLibNull.inf
```
5. Place your `xbl.elf` extracted from a firmware update in xbl folder
6. Run `bash xbl-extract.sh` inside xbl folder
7. Run `bash xbl-extract.sh` inside xbl folder
8. Run ` make -C your_path/edk2-lavender/../edk2/BaseTools/Source/C `
9. Run ` bash build.sh `
10. Run ` fastboot flash boot uefi.img `

Samuel Ladziansky said:
Yes, I have redmi note 7 (lavender), I tried boot windows and what you said happened, windows freze at boot.
And I do not know where I enable serialframebuffer or set that debug level. I gonna try to find it.
Click to expand...
Click to collapse
Acpi is broken in this port. So you can use this port: https://github.com/XRedCubeX/edk2-jasmine
Delete jasmine_sprout.dtb, copy lavender.dtb from edk2-lavender to edk2-jasmine and rename lavender.dtb as jasmine_sprout.dtb. Then compile. Windows should boot.

mark251107 said:
Acpi is broken in this port. So you can use this port: https://github.com/XRedCubeX/edk2-jasmine
Delete jasmine_sprout.dtb, copy lavender.dtb from edk2-lavender to edk2-jasmine and rename lavender.dtb as jasmine_sprout.dtb. Then compile. Windows should boot.
Click to expand...
Click to collapse
Thanks, the ACPI problem was explained in post #9, if you have a fix for ACPI tables, other than to suggest to use different repo for a different device please share with us?

I have published a new release that has a partial fix for ACPI tables which allow to boot windows, also added startup.nsh to automatically run in shell

hello again
I tried to replace those ACPI tables as just the folder where they were, but it still didn't work for me and later I didn't have time to try it again.
But still, even though I compiled this new version, I can't boot windows. I added "UseBootProcessorOnly" to the BCD as Fxsheep wrote on his port on MI6. So far I've been trying to boot from BOOT.WIM but it's stuck on the windows logo, now I'm going to try to extract the wim file into the userdata partition and modify the BCD to boot it. I hope it will run.
theory one:
I think when I tried to boot from wim file once when is loaded in to memory and logo shows up, the memory just gone or lost that files.
theory 2:
Can the windows get stuck on bootlogo beause I have inserted SD Card? I asking because I do not know if windows get access to the device or it have bad information about that.
I come across the fact that whether by chance there is the same effect as when the HDD is damaged on the PC and the BIOS / UEFI will remain chopped on the first screen, if you know what I mean

Samuel Ladziansky said:
hello again
I tried to replace those ACPI tables as just the folder where they were, but it still didn't work for me and later I didn't have time to try it again.
But still, even though I compiled this new version, I can't boot windows. I added "UseBootProcessorOnly" to the BCD as Fxsheep wrote on his port on MI6. So far I've been trying to boot from BOOT.WIM but it's stuck on the windows logo, now I'm going to try to extract the wim file into the userdata partition and modify the BCD to boot it. I hope it will run.
theory one:
I think when I tried to boot from wim file once when is loaded in to memory and logo shows up, the memory just gone or lost that files.
theory 2:
Can the windows get stuck on bootlogo beause I have inserted SD Card? I asking because I do not know if windows get access to the device or it have bad information about that.
I come across the fact that whether by chance there is the same effect as when the HDD is damaged on the PC and the BIOS / UEFI will remain chopped on the first screen, if you know what I mean
Click to expand...
Click to collapse
I just re-tested the edk2-lavender.0.0.3.zip version, should work out of the box, see the image, that windows was just booted now
You must have EFI folder and should be complete, you can find a minimal bootable winPE as the one i used in the attached image to test, i cant recall where i found the minimal winPE iso image.....
Also, you can test the installer itself download win10iso with hXXs://uupdump.net/ then mount the iso, copy EFI folder and all other folders to your fat32 partition the installer should boot

I added an sdcard too, does not matter, windows boot

I have iso from that page and I trying. So you did not change any BCD or other files, and how long time to take boot?
by the way it so cool see Rn7 with windows booted
serdeliuk said:
I just re-tested the edk2-lavender.0.0.3.zip version, should work out of the box, see the image, that windows was just booted now
You must have EFI folder and should be complete, you can find a minimal bootable winPE as the one i used in the attached image to test, i cant recall where i found the minimal winPE iso image.....
Also, you can test the installer itself download win10iso with hXXs://uupdump.net/ then mount the iso, copy EFI folder and all other folders to your fat32 partition the installer should boot
View attachment 5519759
Click to expand...
Click to collapse

I will write when I can boot it.
thanks for help

Samuel Ladziansky said:
I will write when I can boot it.
thanks for help
Click to expand...
Click to collapse
that full desktop from the previous image take approx 80 seconds from phone startup (volUP+power) to complete desktop load (full taskbar)
i tested the windows installer, untouched, should boot, that image (win10desktop) is as ii was downloaded, the winPE image the 200MB one ( the one just with terminal) should boot untouched too, please be sure you use v.0.0.3 and not use files from that version copied to another version, possible i changed a lot in fdf/dsc files

serdeliuk said:
that full desktop from the previous image take approx 80 seconds from phone startup (volUP+power) to complete desktop load (full taskbar)
i tested the windows installer, untouched, should boot, that image (win10desktop) is as ii was downloaded, the winPE image the 200MB one ( the one just with terminal) should boot untouched too, please be sure you use v.0.0.3 and not use files from that version copied to another version, possible i changed a lot in fdf/dsc files
Click to expand...
Click to collapse
Is mater where I flash the uefi.img? I have flashed it in to boot partition, but you say (volUP+power) thats for recovery.
+ I get in to this stage.