XiaomiTool [WIN] [UNIX} - Xiaomi Mi 4

Xiaomi Tool
XiaomiTool is an OpenSource project that has the goal to create a safe, fast and noob-friendly interface to manage your Xiaomi Device.
Click to expand...
Click to collapse
Supported Device status
MTK devices aren't / won't be supported
Xiaomi Mi1(puls) : Not supported
Xiaomi Mi2(s) : Fully supported
Xiaomi Mi2A : Support coming soon
Xiaomi Mi3W : Fully supported
Xiaomi Mi4W : Fully supported
Xiaomi Red Rice : Not supported
Xiaomi RedMi 1S : Fully supported
Xiaomi RedMi Note W : Not supported
Xiaomi RedMi Note LTE : May be supported
Xiaomi MiPad : May be supported
Click to expand...
Click to collapse
Features
GUI (linux and windows)
Backup & Restore
Import Photos
Root
Install apps
Adb Shell
Push and Pull files
Switch to Dalvik
Switch to ART
Record Screen
Install a custom Recovery
Wipe data
Flash Zip files
Install custom recovery
Click to expand...
Click to collapse
Requirements
Windows: Adb and Fastboot (placed on %PATH%)
Unix / Linux: Adb and Fastboot, need to execute some commands with SUDO, so an user-password is needed, do not execute as root
Click to expand...
Click to collapse
Downloads
Windows: https://github.com/linuxxxxx/XiaomiTool/blob/releases/windows/windows.zip
Linux: https://github.com/linuxxxxx/XiaomiTool/blob/releases/linux/linux.zip?raw=true
Unix: https://github.com/linuxxxxx/XiaomiTool/blob/releases/unix/unix.zip?raw=true
Click to expand...
Click to collapse
Installation
Windows
Download the Zip file
Extract the folder
Make sure ADB and Fastboot are working well on your device and they're both on a %PATH% (C:WindowsSystem32 for example) folder
Run XiaomiTool.exe and enjoy
Click to expand...
Click to collapse
Linux
Download the zip file
Extract everything in a folder
chmod +x XiaomiTool or run sh XiaomiTool (The one on the main dir)
Insert your password when asked (see here why it's needed)
Click to expand...
Click to collapse
Unix
Download the zip file
Extract the folder
chmod +x Start.sh
Execute Start ( ./Start.sh )
>> If something goes wrong make sure you can execute adb and fastboot without root access, if not run sudo ./Start
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Which one should I choose?
> Windows : it works on all windows-powered Pcs and on Wine, it only needs adb and fastboot
> Linux : if you're running a debian-based distro
> Unix : (mac) os X, *bsd and it may also be good on other linux distros where the linux one does not work (well)
Click to expand...
Click to collapse
Links
Issue Tracker: https://github.com/linuxxxxx/XiaomiTool/issues
Click to expand...
Click to collapse
XDA:DevDB Information
XiaomiTool, Tool/Utility for the Xiaomi Mi 3
Contributors
linuxxxx
Version Information
Status: Beta
Created 2014-08-13
Last Updated 2014-09-08

i just purchased the xiaomi mi4 downloaded this toolkit but i'm unable to find the option for mi4 ??

afer eric said:
i just purchased the xiaomi mi4 downloaded this toolkit but i'm unable to find the option for mi4 ??
Click to expand...
Click to collapse
Use option 4 for Mi4

Hi, I am trying to connect my Mi4 to linux (ubuntu) but only thing I can do is set the phone in PTP mode and it will just mount the camera directory.
You got any hint?
Thanks

New link for win pls

This github is gone. Any new links ?

Links are dead. Can you upload them again?

link dead re-upload pls

Confirm dead link

All links are DEAD !!!

Page not found. (Windows)

page are not found for Mi 4 windows please fix

Looks like project abandoned and removed from github.

lol

re-upload please

Related

Native linux on i9105 [UBUNTU]

Native linux for Samsung GT-i9105 Galaxy S II Plus
After all this u will loose your external sdcard data
We need:
I. SDcard with at least 4 GB
II. Samsung GT-i9105 Galaxy S II Plus
1. Download and put to the root of your internal sdcard ubuntu-i9105_by-sssemil.tar.gz (910,96 Mb)
2. Now type in terminal emulator:
Code:
su
mke2fs /dev/block/mmcblk1p1
mount -o rw -t ext2 /dev/block/mmcblk1p1 /root
cd /root
tar -xzvf /storage/sdcard0/ubuntu-i9105_by-sssemil.tar.gz
Wait....
3. Now type:
Code:
sync
cat /root/deb_ext2_swa_k1p1.img > /dev/block/mmcblk0p6
sync
4. Done! Now to reboot to ubuntu type:
Code:
su -c reboot recovery
And to reboot to android just reboot ubuntu.
If ubuntu is not booting just remove sdcard and boot without it!
Working:
Wi-Fi
Partly sound
Touchscreen
etc.
Not working:
Camera
Ril stuff
...
suleymanovemil8 said:
Native linux for Samsung GT-i9105 Galaxy S II Plus
After all this u will loose your external sdcard data
We need:
I. SDcard with at least 4 GB
II. Samsung GT-i9105 Galaxy S II Plus
1. Download and put to the root of your internal sdcard ubuntu-i9105_by-sssemil.tar.gz (910,96 Mb)
2. Now type in terminal emulator:
Code:
su
mke2fs /dev/block/mmcblk1p1
mount -o rw -t ext2 /dev/block/mmcblk1p1 /root
cd /root
tar -xzvf /storage/sdcard0/ubuntu-i9105_by-sssemil.tar.gz
Wait....
3. Now type:
Code:
sync
cat /root/deb_ext2_swa_k1p1.img > /dev/block/mmcblk0p6
sync
4. Done! Now to reboot to ubuntu type:
Code:
su -c reboot recovery
And to reboot to android just reboot ubuntu.
If ubuntu is not booting just remove sdcard and boot without it!
Working:
Wi-Fi
Partly sound
Touchscreen
etc.
Not working:
Camera
Ril stuff
...
Click to expand...
Click to collapse
what happen to ur cm10.1 for i9105 thread? u build ur own or source from skullface's(the bugs are the same)
nickchk said:
what happen to ur cm10.1 for i9105 thread? u build ur own or source from skullface's(the bugs are the same)
Click to expand...
Click to collapse
I used skulface`s device source as base(forgot about credits)
S2 Plus 9015
suleymanovemil8 said:
I used skulface`s device source as base(forgot about credits)
Click to expand...
Click to collapse
Can work on S2 Plus 9105P too?
thanks
haky 86 said:
Can work on S2 Plus 9105P too?
thanks
Click to expand...
Click to collapse
Try that method :
1. Flash Custom Recovery(CWM/TWRT) for 9105
2. Flash this ubuntu build
3. Wipe cache,data and dalvik(optional)
4. Reboot system
what about bugs ?
Can you Post Screen Shot and Video ! and what about Bugs ?
Oh man, if some1 can confirm this with screenshots or even just a few words that it is working on GT-i9105P, I would love to try it out even if RIL doesn't work!
SethPDA said:
Oh man, if some1 can confirm this with screenshots or even just a few words that it is working on GT-i9105P, I would love to try it out even if RIL doesn't work!
Click to expand...
Click to collapse
You can see if it's working by simply flashing custom recovery for 9105 and then flash this build through it
OK
I can try it on my phone but is still new only 2 days of life and i have to say is a good phone however can i reflash stock firmware without losing warranty? thanks
:good:
haky 86 said:
I can try it on my phone but is still new only 2 days of life and i have to say is a good phone however can i reflash stock firmware without losing warranty? thanks
:good:
Click to expand...
Click to collapse
Yes :good:
You can flash stock roms via ODIN
DenisRonaldo798 said:
Yes :good:
You can flash stock roms via ODIN
Click to expand...
Click to collapse
if iam wrong is a native system not ubuntu touch?
haky 86 said:
if iam wrong is a native system not ubuntu touch?
Click to expand...
Click to collapse
I didn't try it.I'm not interesting in this rom.I'm using CM11 and everything is nice
About the warranty you should reset the countery bin(using triangle away*100%safe and working app*) and then flash the stock rom
Can some1 please upload this somewhere else? Downloading from turbobit is very very slow.
Maybe mega.co.nz please?
hi
the diffrence between original rom and costum rom ?
pretfish said:
the diffrence between original rom and costum rom ?
Click to expand...
Click to collapse
You can use google for that....but ok i'll give you some examples with galaxy s2+:
More Free RAM than the stock roms which are using TouchWiz
Faster and smoother than the stock.You can easily find the differences if you try custom rom
Higher benchmark score
They are pre-rooted
And custom roms gives you the possibility to have the latest Android version if your phone doesn't have official one which is the best reason to have custom rom
Custom roms can be customized a lot and easy+they have a lot of features which stocks doesn't have
Some of the customs are better for gaming(if you are using your phone for gaming)
Some custom roms have the possibility to control the minimum and maximum CPU frequency(overcloack) but in others you will need a custom kernel.
I think that these are the main reasons to try a custom rom or custom kernel(optional)
The choise is yours
Is that ubuntu phone?
Not sure
lukypuie said:
Is that ubuntu phone?
Click to expand...
Click to collapse
I am not sure this one is an ubuntu touch however i'll upload the file into another file hosting like google drive because i still downloading (2 hours and finish)
haky 86 said:
I am not sure this one is an ubuntu touch however i'll upload the file into another file hosting like google drive because i still downloading (2 hours and finish)
Click to expand...
Click to collapse
Mega is the best.
Anyway, sorry, I meant Ubuntu Touch instead of Ubuntu phone *
So, it's Ubuntu touch?
Not Sure
lukypuie said:
Mega is the best.
Anyway, sorry, I meant Ubuntu Touch instead of Ubuntu phone *
So, it's Ubuntu touch?
Click to expand...
Click to collapse
I don't so this rom is Ubuntu Touch btw, i try to install it on i9105P i guess is same way for i9105 too i rename the archive into u.tar.gz to be short, any one can help me, thanks.
Ok, i've searched around the web and i've found the "original" thread (in a russian forum) and there was two videos about this "rom"
And no, is Debian, not ubuntu touch
https://www.youtube.com/watch?v=FsAYdFTfuqA
https://www.youtube.com/watch?v=LJ0FmwhdnDU

Super ADB Tool - No more command lines!

Super ADB Tool​
Reborn released, please go to this post: Super ADB Tool Reborn
I've cleaned here, because of two reasons. Primary is that i don't have the Source of this version anymore, and things such as bug requests cannot be resolved here. Second, I just released my new tool. Even better and stabler.
Thanks :3
XDA:DevDB Information
Super ADB Tool, Tool/Utility for the Android General
Contributors
Fusseldieb
Version Information
Status: Beta
Created 2014-03-29
Last Updated 2015-10-10
Very useful tool
Thanq so much for sharing
Sent from my Lenovo P780_ROW using XDA Premium 4 mobile app
bump
bump :/
I believe that someone should make a post about this in the portal
Vagelis1608 said:
I believe that someone should make a post about this in the portal
Click to expand...
Click to collapse
That's a good ideia
Bump
bump :c
Anyone?
This tool is looking good, very nice job OP, will try it at home (not behind my computer at the moment)!
Verstuurd vanaf mijn Nexus 7 met Tapatalk
Will try this on Windows 7
TecknoFreak said:
Will try this on Windows 7
Click to expand...
Click to collapse
It was made on Windows 7
Fusseldieb said:
Bump
Click to expand...
Click to collapse
very thanks you so ^^, :victory::victory::victory::victory:
I needn't make a *.zip to flash in reovery or find the hard button to join recovery or bootloader. :good:
But when I try to install an app (SwiftKey ~17mb), it takes me 4 minutes. Can you make it quickly? :good:
blessedsword said:
very thanks you so ^^, :victory::victory::victory::victory:
I needn't make a *.zip to flash in reovery or find the hard button to join recovery or bootloader. :good:
But when I try to install an app (SwiftKey ~17mb), it takes me 4 minutes. Can you make it quickly? :good:
Click to expand...
Click to collapse
I will release this weekend version "0.4 Beta", and I will try to solution your problem
Thaks for report
Which option would I use to install a custom recovery?
tarroyo said:
Which option would I use to install a custom recovery?
Click to expand...
Click to collapse
You would use the option "Sideload" on the PC and in your recovery, choose a zip file and then confirm.
Version "0.4 Beta" will include a option "Upload & Reboot", in case, if your recovery doesn't have the "Sideload" feature
Xiaomi mi2s dont working
Does not find device
mopss said:
Does not find device
Click to expand...
Click to collapse
This tool is based on ADB, if your device are not recognized in the command line, it will neither appear in my tool
Please check if you have the correct drivers installed and restart your computer.
If you have already tried this, make sure that in the "adb_usb.ini" is the correct vendor ID written.
EDIT: Ah, and make sure you have USB Debugging enabled xD
Hope i could help you
Fusseldieb said:
This tool is based on ADB, if your device are not recognized in the command line, it will neither appear in my tool
Please check if you have the correct drivers installed and restart your computer.
If you have already tried this, make sure that in the "adb_usb.ini" is the correct vendor ID written.
EDIT: Ah, and make sure you have USB Debugging enabled xD
Hope i could help you
Click to expand...
Click to collapse
I have all-inclusive and all drivers are.
Most likely I did not support the kernel
Here is my adb_usb.ini
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
mopss said:
I have all-inclusive and all drivers are.
Most likely I did not support the kernel
Here is my adb_usb.ini
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
Click to expand...
Click to collapse
Hmmm.... Try putting the vendor ID from your device under these lines, save and try again
v5 :x

[rom][treble]phh aosp 8.1[lm-g710em]

HI Guys , its me again so after a long working night of disabling encryptions and verifications i finaly was able to boot a AOSP Generic System Image on my LG G7 (EUROPEAN VARIANT ONLY) and now im here to show you how to install​
How to install ?​​
Download the GSI from PHH AOSP thread , take a/b ones with ot without gapps as you like
Download my SecuretyOff-Vendor-image and my Permissive boot.img
Reboot to fastboot and unlock your bootloader if you havent done it yet (you can find tutorials online, same method as on g6 and previous)
flash the magisk enabled securetyoff permissive kernel with the command "fastboot flash boot_a pathtoimghere"
Reboot your G7 to LG Stock os and install magisk manager and TerminalEmulator from PlayStore
Now copy the Downloaded Vendor file to your internal sdcard and rename it to vendor.img
Open TerminalEmulator (adb shell works aswell) and type su, hit enter, then type "dd if=/sdcard/vendor.img of=/dev/block/bootdevice/by-name/vendor_a" , hit enter m this will take some time pls be patient
Once youre done with flashing the new vendor reboot to fastboot again and flash the GSI with the following command "fastboot flash system_a pathtoimghere"
One last step before you can enjoy AOSP type "fastboot -w" and then "fastboot reboot"
Whats Working ?​
So for me everyting works so far i just noticed 2 small bugs till now
1. the Notification LED wont stop blinking (im on that already)
2.sometimes the display turns black for about 0,5secs
3. if your headphone jack doesn't work open up a root shell and enter "setprop persist.sys.overlay.devinputjack true"​
Credits​
Me for testing and patching the **** out of that boot.img and vendor.img
AutoPrime for his G7 system Dump
Phhuson for his brilliant work on GSI's
Zefie for recommending me the right tool to repack kernel without bootloops (xD)
SGMarkus for providing ideas and additional Help
reserved
reserved 2
Update , Ressurection Remix Gsi and LineageOS Gsi work too , also i was able to fix the blinking led , but it doesnt work at all anymore (lights hal doesnt load will investiagte tomorrow) but RR or Los doesnt have gapps packed with them so you will need to wait for twrp to be ready (i think i will finish it in next few days)
J0SH1X said:
HI Guys , its me again so after a long working night of disabling encryptions and verifications i finaly was able to boot a AOSP Generic System Image on my LG G7 (EUROPEAN VARIANT ONLY) and now im here to show you how to install
How to install ?
Download the GSI from PHH AOSP thread , take a/b ones with ot without gapps as you like
Download my SecuretyOff-Vendor-image and my Permissive boot.img
Reboot to fastboot and unlock your bootloader if you havent done it yet (you can find tutorials online, same method as on g6 and previous)
flash the magisk enabled securetyoff permissive kernel with the command "fastboot flash boot_a pathtoimghere"
Reboot your G7 to LG Stock os and install magisk manager and TerminalEmulator from PlayStore
Now copy the Downloaded Vendor file to your internal sdcard and rename it to vendor.img
Open TerminalEmulator (adb shell works aswell) and type su, hit enter, then type "dd if=/sdcard/vendor.img of=/dev/block/bootdevice/by-name/vendor_a" , hit enter m this will take some time pls be patient
Once youre done with flashing the new vendor reboot to fastboot again and flash the GSI with the following command "fastboot flash system_a pathtoimghere"
One last step before you can enjoy AOSP type "fastboot -w" and then "fastboot reboot"
Whats Working ?
So for me everyting works so far i just noticed 2 small bugs till now
1. the Notification LED wont stop blinking (im on that already)
2.sometimes the display turns black for about 0,5secs
Credits
Me for testing and patching the **** out of that boot.img and vendor.img
AutoPrime for his G7 system Dump
Phhuson for his brilliant work on GSI's
Zefie for recommending me the right tool to repack kernel without bootloops (xD)
SGMarkus for providing ideas and additional Help
Click to expand...
Click to collapse
Amazing work friend
What about the rom with the DAC? I can change this in the settings of the sound more precise. So not like the lg rom, the preset sound profiles?
Look forward to this! Many thanks +++
what about the dac? sound does not work over jack connection.
Hi.
Does the wide camera work with this rom?
And does the radio fm work?
Where can I find the last release?
Thanks.
Sent from my LM-G710 using Tapatalk
ricxgp said:
Hi.
Does the wide camera work with this rom?
And does the radio fm work?
Where can I find the last release?
Thanks.
Sent from my LM-G710 using Tapatalk
Click to expand...
Click to collapse
wide angle works on aosp rom , fm radio idk but try , you can find the latest release in treble enabled device section of xda
Any word on AOSP 9? As far as I know it requires vndk 8.1 but the g7 launched with Android 8. Do we have to wait for Android 8.1/9 from LG for AOSP 9?
https://highonandroid.com/android-r...oject-treble-unlocked-bootloader-twrp-method/
I saw a video on youtube by max lee i do believe he said you could install this as long as you had twrp recover
I have the sprint verison so i cant try but if anyone with twrp can try and comment
LameMonster82 said:
Any word on AOSP 9? As far as I know it requires vndk 8.1 but the g7 launched with Android 8. Do we have to wait for Android 8.1/9 from LG for AOSP 9?
Click to expand...
Click to collapse
does not work will maybe never work
Guys, can anyone pls do this in adb (or if you have root with terminal app):
echo 0 > /proc/sys/kernel/kptr_restrict
cat /proc/kallsyms >/sdcard/kallsyms.txt
UltraM8 said:
Guys, can anyone pls do this in adb (or if you have root with terminal app):
echo 0 > /proc/sys/kernel/kptr_restrict
cat /proc/kallsyms >/sdcard/kallsyms.txt
Click to expand...
Click to collapse
With the stock ROM or with aosp?
LameMonster82 said:
With the stock ROM or with aosp?
Click to expand...
Click to collapse
Doesn't really matter
so the headphone jack is now fixed open up a root shell and type setprop persist.sys.overlay.devinputjack true then reboot and it will work
UltraM8 said:
Guys, can anyone pls do this in adb (or if you have root with terminal app):
echo 0 > /proc/sys/kernel/kptr_restrict
cat /proc/kallsyms >/sdcard/kallsyms.txt
Click to expand...
Click to collapse
Hello, sorry for being so late but i finaly got the files that youre looking for. "Kptr_restrict" is attached in the post but "kallsyms" is too big so i uploaded it to my google drive. The link is:
https://drive.google.com/file/d/1Mn9jeS7n681dbRWvZqlundCuTAvNF4FJ/view?usp=drivesdk
LameMonster82 said:
Hello, sorry for being so late but i finaly got the files that youre looking for. "Kptr_restrict" is attached in the post but "kallsyms" is too big so i uploaded it to my google drive. The link is:
https://drive.google.com/file/d/1Mn9jeS7n681dbRWvZqlundCuTAvNF4FJ/view?usp=drivesdk
Click to expand...
Click to collapse
thx man!
LameMonster82 said:
Hello, sorry for being so late but i finaly got the files that youre looking for. "Kptr_restrict" is attached in the post but "kallsyms" is too big so i uploaded it to my google drive. The link is:
https://drive.google.com/file/d/1Mn9jeS7n681dbRWvZqlundCuTAvNF4FJ/view?usp=drivesdk
Click to expand...
Click to collapse
I've checked kallsyms, how did you get it? via terminal app, or adb (or even twrp maybe if it's possible on g7)? The prob is that functions addresses are zeros, that's not good.

[Q] Please link for ZTE K3DX-V5G firmware.

Please link for ZTE K3DX-V5G firmware.
ZTE K3DX-V5G firmware
Why do you need ZTE K3DX-V5G firmware?
Is there something wrong with your device?
Do you recommend buying the ZTE K3DX-V5G?
The brand name is V5 or ZTE or Guan or Mango.
It is the same device, manufatured by V5 and sold by ZTE, Guan and Mango.
Guan K3DX-V5G
https://deviceatlas.com/device-data/devices/guan/k3dx-v5g/28213760
BangGearWatch | ZTE V5G-K3DX
https://www.banggearwatch.com/pricetracker/zte-v5g-k3dx-5-5-inch-3gb-1369255/
The price was €64 at BangGood, for a short time.
The price was €70 at MyeFOX.
V5 K3DX-V5G 3GB RAM 32GB ROM Qualcomm Snapdragon 617 1.5GHz Octa Core FHD Display 5.5 inches Android 5.1 4G LTE Smartphone
https://www.myefox.fr/telephones/v5...a-core-fhd-ecran-55-pouces-android-5-g-223880
K3DX-V5G supports naked-eye 3D and eye-tracking.
It has a K3DX display with column interlaced mode.
Therefore is fully compatible with PhereoRol3D app.
https://github.com/JackDesBwa/PhereoRoll3D
Get the latest release here
https://github.com/JackDesBwa/PhereoRoll3D/releases
Have you tried PhereoRol3D ?
BootStomp and DR.CHECKER
Your phone has a locked bootloader.
You need to run these two tools: DR.CHECKER and BootStomp.
DR.CHECKER : A Soundy Vulnerability Detection Tool for Linux Kernel Drivers.
It is a single script!
This repo contains all the sources, including setup scripts. Now with an Amazing UI to view the warnings along with corresponding source files.
https://github.com/ucsb-seclab/dr_checker
BootStomp
https://seclab.cs.ucsb.edu/academic/publishing/#bootstomp-security-bootloaders-mobile-devices-2017
Did you manage to root ZTE K3DX-V5G ?
Partitions table
Get an excellent partitions table of ZTE K3DX-V5G
This format is ideal for recovery.
Device Info HW
https://play.google.com/store/apps/details?id=ru.andr7e.deviceinfohw&hl=en_US
NOTE - Find attached the partitions table of SuperD D1 (SuperD C1001). It is another device with Naked-eye 3D and eye-tracking.
Do you own a ZTE K3DX-V5G ?
You do not own a ZTE K3DX-V5G, do you?
V5 K3DX V5G Smartphone Unboxing (3D Video Camera)
https://www.youtube.com/watch?v=KkQhQszdSYs
Mango K3DX-V5G
https://v.youku.com/v_show/id_XMjgxMDI4OTcyOA==.html
3D Dongdong APP: Over 10,000 3D movies provided
http://en.k3dx.com/prolist/7/17.html
Thank you for many information about it.
I did not own it now due to it heat up too much compare with SD 625 / 636 phone.
Discussion V5 K3DX-V5G at russian 4pda forum
Discussion V5 K3DX-V5G
http://4pda.ru/forum/index.php?showtopic=944204
There is new firmware available from chinese versions (latest 1.3)
Firmware in China
http://www.shuajibao.com/rom/Zte/23777
Version 1.3 is not official. It is a custom ROM by this russian guy... Sidorovvitalik.
But development has already stopped because he is selling his ZTE V5 K3DX-V5G.
K3DX V5G stockrom
Please can someone upload the stockrom.
After scouring the internet for hours, I stumbled upon this post:
https://4pda.ru/forum/index.php?showtopic=944204&st=220
And guess what, I found the firmware for the device! Eventually, I was able to fix my bricked K3DX V5G, and here it is:
https://yadi.sk/d/TSjrTYbKBV4KWA
What I did was:
1. Decompressing the file
2. Flashing it with fastboot
3. Device resurrected!
Fastboot commands:
Code:
fastboot flash:raw boot boot.img
fastboot flash system system.img
edit: found out that it is a clone of ZTE v5 pro N940SC
Ma'am/Sir. Can i ask what usb driver did you use to detect your k3dx-v5g? Because mine is not detecting. Thanks in advance.
Ma'am/Sir. Can i ask what usb driver did you use to detect your k3dx-v5g? Because mine is not detecting. Thanks in advance.
asce16 said:
Ma'am/Sir. Can i ask what usb driver did you use to detect your k3dx-v5g? Because mine is not detecting. Thanks in advance.
Click to expand...
Click to collapse
Are you on Linux or Windows?
Ma'am/Sir. What usb driver did you use to detect your k3dx v5g phone? I cant find compatible to mine, my pc cant detect my k3dx v5g phone. Plsss. Send link. Thanks in advance.
B83C said:
Are you on Linux or Windows?
Click to expand...
Click to collapse
Window.
B83C said:
Are you on Linux or Windows?
Click to expand...
Click to collapse
Also ma'am/sir. can i ask a little favor? Can you send me full guide how to flash this file. Plssss
asce16 said:
Also ma'am/sir. can i ask a little favor? Can you send me full guide how to flash this file. Plssss
Click to expand...
Click to collapse
Hmm well, have u tried peeking at the device manager when you phone is connected to your PC in fastboot mode?
If there's an entry showing your device you will need grab a fastboot binary to flash the firmware.
Here's a link to the tool called minimal ADB and Fastboot: here
You will also need to extract the firmware to somewhere in your drive.
Having done all the extraction and installation,
and since you're on Windows, you should do:
Bash:
\path\to\fastboot flash:raw boot \path\to\boot.img
\path\to\fastboot flash system \path\to\system.img
where \path\to\fastboot points to the path where you have extracted/installed the tool (or if you have added its path to the PATH environment variable, you can avoid the hassle to write the full path), and \path\to\boot.img and system.img points to absolute path of the extracted firmware.
Then, you are good to go!
B83C said:
Hmm well, have u tried peeking at the device manager when you phone is connected to your PC in fastboot mode?
If there's an entry showing your device you will need grab a fastboot binary to flash the firmware.
Here's a link to the tool called minimal ADB and Fastboot: here
You will also need to extract the firmware to somewhere in your drive.
Having done all the extraction and installation,
and since you're on Windows, you should do:
Bash:
\path\to\fastboot flash:raw boot \path\to\boot.img
\path\to\fastboot flash system \path\to\system.img
where \path\to\fastboot points to the path where you have extracted/installed the tool (or if you have added its path to the PATH environment variable, you can avoid the hassle to write the full path), and \path\to\boot.img and system.img points to absolute path of the extracted firmware.
Then, you are good to go!
Click to expand...
Click to collapse
Ma'am/sir. Thanks, it's fix now. Thanks for the help. Godbless and stay safe.
Hello, in case you are looking for a twrp image for the device, here's one I have ported myself:
TWRP_N940Sc_V3
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
B83C said:
Hello, in case you are looking for a twrp image for the device, here's one I have ported myself:
https://www.mediafire.com/file/0547s4g8hdojctq/TWRP_N940Sc_V3.img/fileTh
Click to expand...
Click to collapse
Thankyou! Uhm is there any custom rom? Can you please port a custom rom or upload please i really need it[/url]
John072021 said:
Thankyou! Uhm is there any custom rom? Can you please port a custom rom or upload please i really need it[/url]
Click to expand...
Click to collapse
I regret to tell you that, no. Currently I have been using the phone as a debian server, since the LCD has been inadvertently broken ( I exerted too much force on it ). Moreover, the device doesn't recognize its battery, which suggests that I might have broken some part of it. Therefore, I have kinda lost any hopes for it. Plus, my linux machine is not powerful enough to build an android OS ( what do you expect much from an intel celeron? ).
PS: I might do it once I get my hands on a much powerful one, or maybe a powerful enough VPS? I am not quite sure but currently I am still in high school, meaning that I may or may not have time....
Best regards,
B83C

[ROM] [Unofficial] [Stable] GrapheneOS 10 Pre-Rooted

**** Disclaimer: I'm not responsible if you destroy your device. Use at your own risk!!! ****
GrapheneOS is an open source privacy and security focused mobile OS with Android app compatibility. It's focused on the research and development of privacy and security technology including substantial improvements to sandboxing, exploit mitigations and the permission model. Currently it is based on AOSP.
Link: (Mod Edit: Link removed)
Important information:
1. This ROM does NOT include Gapps or Google Play Service and hasn't Signature Spoofing Support. If you rely on the mentioned things this Rom isn't for you.
2. I take the official releases, modify the install script and include a pre-patched Magisk boot image. I'm not in contact with the GrapheneOS dev which is the reason why i mark this ROM as Unofficial.
3. Due of point two: Please don't ask questions on the official channels as reddit. Leave comments etc here on this thread.
4. You need a unlocked bootloader to flash this rom and must have adb+fastboot installed on your computer. If this is not the case download it from here: https://developer.android.com/studio/releases/platform-tools
I plan to make unofficial releases when new official builds are available.
Features:
AOSP 10
Built-in Firewall
Built-in local backup function (it's not working on all Apps; some doesn't support it)
Improved MAC Randomization
Hardened Kernel
Expanded Permissions (sensors)
Force calls to 4G only
Bugs
- Receiving text over verizon sim doesn't work reliable. Thx @wolfu11 for reporting.
Download: (Mod Edit: Link removed)
Installation:
Notice 1: The First-time installation will wipe your data. Backup first (i recommend this too when you follow the update instructions to be safe)
Notice 2: I recommend to have the newest stock firmware before the First-time installation
First-time installation:
1. Download the zip from the linked download page and unzip it on your computer
2. Copy the following files into the plattform-tools folder:
-> coral zip
-> bootloader img
-> radio img
-> flash-all_first_install.bat for Windows or flash-all_first_install.sh for Linux
3. Boot your phone into fastboot mode and verify that the phone is recognized from your computer
4. In Terminal (Linux) or Powershell (Windows): Run the appropriate script
5. Install the Magisk Manager App
10. Be happy with a rooted GrapheneOS
Update:
Notice: I assume that fastboot+adb is still installed on your computer.
1. Download the newest zip from the linked download page and unzip it on your computer
2. Copy the following files into the plattform-tools folder:
-> coral zip
-> bootloader img
-> radio img
-> flash-all.bat for Windows or flash-all.sh for Linux
If your computer asks you to overwrite the current files in the plattform-tools folder, confirm it.
3. Boot your phone into fastboot mode and verify that the phone is recognized from your computer
4. In Terminal (Linux) or Powershell (Windows): Run the appropriate script
5. Start the system once. This need a few more time than the first installation cause the data partition remains. Be patient.
6. Install the Magisk Manager App
7. Be happy with a rooted GrapheneOS
Sources:
https://github.com/GrapheneOS
https://grapheneos.org/releases
https://github.com/GrapheneOS/kernel_google_coral
https://github.com/GrapheneOS/device_google_coral-kernel
All Credits go to:
- The GrapheneOS team
- wolfu11 for reporting the verizon bug and testing the windows scripts
- and topjohnwu for his amazing Magisk
Created: 09.08.2020
Based on: Android 10
Updated: 21.08.2020
Current Version: 2020.08.07.01
Changelog from 09.08.2020
New Release: 2020.08.03.22
SHA3-512 Hash for Complete zip:
Code:
773c67b8571927c6f884a98ee67a10f96c3a759e34f925f7a8aaab7c19a4ca6b1ff53bb6dc500b4fe7c306b73853189a1c559889df6d9b4f2e8a90258d3d26c9
SHA3-512 Hash for Unpatched boot.img:
Code:
9b584f6941d37f60a7ed17ec4108b7bf484c3cbf1b63f2be6af1e59f452ed1d06e1b64704785d6ca3b38a3c09c8f29657f88c757bda993df509ef001d9842f00
Changes:
full 2020-08-01 security patch level
full 2020-08-05 security patch level
rebased onto QQ3A.200805.001 release
fix secondary stack hardening when a non-page-size multiple stack size is specified
fix picking up previous build date when doing incremental builds
Vanadium: update Chromium base to 84.0.4147.89
Vanadium: update Chromium base to 84.0.4147.105
Vanadium: update Chromium base to 84.0.4147.111
Vanadium: remove Chromium logo in chrome://version
kernel (Pixel 4, Pixel 4 XL): read-only data expansion
Changelog from 11.08.2020:
Updated the OP with some more informations
Rewrite the instruction cause i believe that they were not fully correct.
Reupload the 2020.08.03.22 unofficial release with new structure. I patched the boot.img which come with GrapheneOS in the zip with Magisk and then replaced the original GrapheneOS boot.img in the zip with the patched version.
Hi good evening to all,
Can somebody try to install this Rom with the updated instructions? I think they should work now (at least on Linux) but i would appreciate a confirmation to be safe.
dhacke said:
Changelog from 11.08.2020:
Updated the OP with some more informations
Rewrite the instruction cause i believe that they were not fully correct.
Reupload the 2020.08.03.22 unofficial release with new structure. It isn't needed anymore to flash Magisk separately from the zip. I replaced the stock boot.img in the zip with the pre-patched one.
Click to expand...
Click to collapse
Just a heads up - you really aren't meant to pre-patch a boot image for Coral/Flame, as you are only meant to patch the boot image from your own individual device, as per the man topjohnwu himself
See: https://twitter.com/topjohnwu/status/1272136975022084097?s=19
Can you supply the unpatched boot img?
Thank you
wolfu11 said:
Can you supply the unpatched boot img?
Thank you
Click to expand...
Click to collapse
Done. Look here: (Mod Edit: Link removed)
I added an SHA3-512 Hash for file checking,too (see changelog from 11.08.2020).
Changelog from 15.08.2020
New Release: 2020.08.07.01
SHA3-512 Hash for Complete zip:
Code:
f3a2b088e0ec503296d5a2527a3766951cb2a3ccd1955ced14d304222e76ed3f341dd9d84b6e186a534eddac335065b756c1fdc89d0f1db3985314424e7f9eea
SHA3-512 Hash for unpatched boot image:
Code:
11abb901511ce8e39911bc951be4b1a349158c5d8389e74766942159c0f83aa9730ed39d8c8ae6c3cc66be559e3c165b5d4f35e0962d20a7be0b1532673a0287
Changes:
SELinux policy: fix executing apk libraries as executables for third party applications
Installation Notices:
From 2020.08.03.22 => No wipe needed. Just take the update scripts and let the right one running (see OP).
From Stock Rom => Use the install_first scripts. Be aware: This will wipe your data
Apart from that i recommend to make a backup first always (to be safe).
Wireguard Kernel integration
dhacke said:
Hi good evening to all,
Can somebody try to install this Rom with the updated instructions? I think they should work now (at least on Linux) but i would appreciate a confirmation to be safe.
Click to expand...
Click to collapse
Hi, great work!! It was exactly what I was looking for, GrapheneOS with root. Are you able to integrate wireguard into the kernel?
[email protected] said:
Hi, great work!! It was exactly what I was looking for, GrapheneOS with root. Are you able to integrate wireguard into the kernel?
Click to expand...
Click to collapse
Hi Cryptt33,
first thx for your praise.
Regarding wireguard integration:
You should be able to use Wireguard independently from the kernel if i understand the description from the wireguard f-droid app right (https://f-droid.org/en/packages/com.wireguard.android/).
Then Wireguard runs in a userspace version. Apart from that i have found a xda thread already regarding wireguard integration. I guess i will at least try it and mayby i will be successful with the help of the thread. But i can't give a eta. I built roms from sources in the past but i until now i didn't try to modify them before the compiling step.
Best regards
dhacke
dhacke said:
Hi Cryptt33,
first thx for your praise.
Regarding wireguard integration:
You should be able to use Wireguard independently from the kernel if i understand the description from the wireguard f-droid app right (https://f-droid.org/en/packages/com.wireguard.android/).
Then Wireguard runs in a userspace version. Apart from that i have found a xda thread already regarding wireguard integration. I guess i will at least try it and mayby i will be successful with the help of the thread. But i can't give a eta. I built roms from sources in the past but i until now i didn't try to modify them before the compiling step.
Best regards
dhacke
Click to expand...
Click to collapse
Just need to add this to local_manifest for WG support
If unfamiliar with local_manifest, it's located in /.repo/local_manifests/ - it'll be the only file in that dir, often it's called room service.xml but it could be something like graphene_manifest.xml. Either way, it'll be the only file there and it'll be an XML - add those lines above to it and sync and you should have WireGuard support.
<remote name="zx2c4" fetch=https://git.zx2c4.com/>
<project remote="zx2c4" name="android_kernel_wireguard" path="kernel/wireguard" revision="master" sync-s="true" />
dhacke said:
Hi good evening to all,
Can somebody try to install this Rom with the updated instructions? I think they should work now (at least on Linux) but i would appreciate a confirmation to be safe.
Click to expand...
Click to collapse
I've tried this several time with a windows computer with no luck the shell opens briefly with red writing on the top and closes.
i must be doing something wrong but can't put my finger on it..... i run windows ltsb but i don't have any issues up and downgrading my p4 xl on it i am running the latest platform tools but get this message:
C:\Users\Wolf's laptop\Desktop\platform-tools_r30.0.4-windows\platform-tools>flash-all_first_install
fastboot : The term 'fastboot' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:10
+ $version=fastboot --version; try { $verNum = $version[0].substring(17 ...
+ ~~~~~~~~
+ CategoryInfo : ObjectNotFound: (fastboot:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
fastboot too old; please download the latest version at https............
wolfu11 said:
I've tried this several time with a windows computer with no luck the shell opens briefly with red writing on the top and closes.
i must be doing something wrong but can't put my finger on it..... i run windows ltsb but i don't have any issues up and downgrading my p4 xl on it i am running the latest platform tools but get this message:
C:\Users\Wolf's laptop\Desktop\platform-tools_r30.0.4-windows\platform-tools>flash-all_first_install
fastboot : The term 'fastboot' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:10
+ $version=fastboot --version; try { $verNum = $version[0].substring(17 ...
+ ~~~~~~~~
+ CategoryInfo : ObjectNotFound: (fastboot:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
fastboot too old; please download the latest version at https............
Click to expand...
Click to collapse
Hi wolfu11,
i know this message in similar way on Linux. To fix it on linux i need to run all fastboot commands and scripts with './' before.
So for example:
./fastboot devices instead of fastboot devices or ./flash-all.sh instead of flash-all.sh.
I done this in the scripts for linux already cause i know it is needed there but didn't thought that it is needed on windows, too.
So please go into the script and make this before all fastboot commands:
./
Save it and execute it in the plattform-tools folder with ./ again in the shell. Hopefully it runs then.
If this fixes your issue, i will update the windows scripts.
dhacke said:
Hi wolfu11,
i know this message in similar way on Linux. To fix it on linux i need to run all fastboot commands and scripts with './' before.
So for example:
./fastboot devices instead of fastboot devices or ./flash-all.sh instead of flash-all.sh.
I done this in the scripts for linux already cause i know it is needed there but didn't thought that it is needed on windows, too.
So please go into the script and make this before all fastboot commands:
./
Save it and execute it in the plattform-tools folder with ./ again in the shell. Hopefully it runs then.
If this fixes your issue, i will update the windows scripts.
Click to expand...
Click to collapse
I will try it when I get home today thank you
wolfu11 said:
I will try it when I get home today thank you
Click to expand...
Click to collapse
that didn't work either i downloaded the latest platform tools so im at a loss about the fastboot issue.
I'm going keep trying
Update: I was able to get the official Graphene to work via putting the image into a working stock update platform tools folder and renaming it to the stock image. it wouldn't work per instruction on the website very strange.
wolfu11 said:
that didn't work either i downloaded the latest platform tools so im at a loss about the fastboot issue.
I'm going keep trying
Update: I was able to get the official Graphene to work via putting the image into a working stock update platform tools folder and renaming it to the stock image. it wouldn't work per instruction on the website very strange.
Click to expand...
Click to collapse
Well it was worth a shot texts don't work on verizon so i guess i'll just give up.
thank you
wolfu11 said:
Well it was worth a shot texts don't work on verizon so i guess i'll just give up.
thank you
Click to expand...
Click to collapse
Hi wolfu11,
i tested the bat script (more precisely flash-all.bat) with './' on my dedicated gaming machine with win 10 2004 education, too. First i got the same problem as you: It didn't run whether i made './' before all fastboot commands in the scripts.
Then i removed all the './' before all fastboot command except at this line:
Code:
$version= fastboot --version; ^
So the line looks now:
Code:
$version=./fastboot --version; ^
And hurray the script worked without problems on my machine (see attached screenshots).
Only as reminder: The bat scripts are from the 2020.08.07.01 unofficial release so you need the radio, bootloader and image files from that release.
i attached the new scripts with my mentioned modification, too. Xda doesn't allow bat files so i made them into a zip file. Please test once more. Thx in advance.
dhacke said:
Hi wolfu11,
i tested the bat script (more precisely flash-all.bat) with './' on my dedicated gaming machine with win 10 2004 education, too. First i got the same problem as you: It didn't run whether i made './' before all fastboot commands in the scripts.
Then i removed all the './' before all fastboot command except at this line:
Code:
$version= fastboot --version; ^
So the line looks now:
Code:
$version=./fastboot --version; ^
And hurray the script worked without problems on my machine (see attached screenshots).
Only as reminder: The bat scripts are from the 2020.08.07.01 unofficial release so you need the radio, bootloader and image files from that release.
i attached the new scripts with my mentioned modification, too. Xda doesn't allow bat files so i made them into a zip file. Please test once more. Thx in advance.
Click to expand...
Click to collapse
That script worked thanks
wolfu11 said:
That script worked thanks
Click to expand...
Click to collapse
Yeah finally. I'm happy to read that. Then i will update the OP & scripts in the next days and take you on the credit section. Thx very much for your windows testing.
Now the next on the to-do list is the building of this rom from source and adding Wireguard support into the kernel
dhacke said:
Yeah finally. I'm happy to read that. Then i will update the OP & scripts in the next days and take you on the credit section. Thx very much for your windows testing.
Now the next on the to-do list is the building of this rom from source and adding Wireguard support into the kernel
Click to expand...
Click to collapse
No problem i'm happy to test. unfortunately the still is an issue with texting on verizon which is what i use this phone on. the texts send but receiving them is not reliable. I tested on an att sim and it didn't have an issue so it's something on verizon's end.

Categories

Resources