Français :
Bonjour, je vous explique mon problème.
Mon LG G4 H815 (modéle 505) c'est retrouvé en bootloop suite à un mauvais contact du processeur.
J'ai donc décider de flasher un fichier .tot pour désactiver le Bigcore et cela à très bien fonctionner (v10d lollipop)
Mais un seul processeur (num 0) fonctionne, donc j'aimerais un fichier à flasher ou une autre solution pour activer les processeur 1,2,3 (seul le 4 et 5 ont des problème) Le téléphone fonctionne parfaitement quant le 1,2,3 sont actif
Je parle d'une manière définitive c'est a dire que le 0,1,2,3 puisse fonctionner normalement sans avoir à les activer avec kernel audiutor.
Si quelqu'un peut m'aider ou me donner une solution gratuite, je suis sur que sa existe.
Je tient à préciser que je suis prêt à tester n'importe quel solution
Je vous remercie beaucoup
PS : J'ai aperçu la solution ilAPO mais pour 25$ cela m'ennuie
English :
Hello, I explain my problem. :crying: :crying:
My LG G4 H815 (model 505) it is found in bootloop following a bad contact of the processor.
I decided to flash a .tot file to disable the Bigcore and it works very well (v10d lollipop)
But a single processor (num 0) works, so I would like a file to flash or another solution to activate the 1,2,3 processor (only the 4 and 5 have problems)
The phone works perfectly as the 1,2,3 are active
I speak in a definitive way that is to say that the 0,1,2,3 can operate normally without having to activate them with kernel adiutor.
If someone can help me or give me a free solution, I'm sure its exists.
I want to clarify that I am ready to test any solution
Thank you a lot
PS: I saw the solution ilAPO but for $ 25 it annoys me
Unfortunately I can not post screen
there https://forum.xda-developers.com/g4/themes-apps/root-4-cores-activator-t3538175
Levent2101 said:
there https://forum.xda-developers.com/g4/themes-apps/root-4-cores-activator-t3538175
Click to expand...
Click to collapse
How to fix the bootloop in lg g4 stylus?
ThankYou
Levent2101 said:
there https://forum.xda-developers.com/g4/themes-apps/root-4-cores-activator-t3538175
Click to expand...
Click to collapse
Thank you very much, it works but in the same way as adiutor.
The processors turn on when the smartphone starts and finish.
What I would like is a solution to modify some system file to have the 4 cores active directly in the boot (without software)
For information I decompile this application: https://forum.xda-developers.com/g4/development/ilapo-infinite-loop-auto-power-off-fix-t3404421
And this aplication changes this: /system/etc/init.qcom.post_boot.sh
So I think there can be a solution to directly activate the 4 processors at the boot?
Decompiler .class file:
// Decompiled by Jad v1.5.8e. Copyright 2001 Pavel Kouznetsov.
// Jad home page: http://www.geocities.com/kpdus/jad.html
// Decompiler options: packimports(5) braces fieldsfirst noctor nonlb space lnc
package cz.youber.g4ilapo;
import android.app.Activity;
import android.content.Context;
import android.os.AsyncTask;
import android.widget.Button;
import com.a.a.b.d;
import com.a.b.a;
// Referenced classes of package cz.youber.g4ilapo:
// g, MainActivity, h, i
final class f extends AsyncTask {
int a;
String b;
Activity c;
Context d;
f(Activity activity, Context context) {
a = 1;
c = activity;
d = context;
}
private transient Integer a(Integer ainteger[]) {
String as[];
String s;
g g1;
com.a.a.b.a a1;
if (ainteger[0].intValue() == 0) {
b = "mount -o rw,remount /system; sed -i -e 's/g4ilapofix=true/g4ilapofix=false/g' /system/etc/init.qcom.post_boot.sh; echo 0 > /sys/devices/system/cpu/cpu1/online; echo 0 > /sys/devices/system/cpu/cpu2/online; echo 0 > /sys/devices/system/cpu/cpu3/online; $(exit 1)";
} else
if (ainteger[0].intValue() == 1) {
b = "mount -o rw,remount /system; sed -i -e 's/g4ilapofix=false/g4ilapofix=true/g' /system/etc/init.qcom.post_boot.sh; echo 1 > /sys/devices/system/cpu/cpu0/online; echo 1 > /sys/devices/system/cpu/cpu1/online; echo 1 > /sys/devices/system/cpu/cpu2/online; echo 1 > /sys/devices/system/cpu/cpu3/online; $(exit 0)";
} else {
b = "mount -o rw,remount /system; if $(grep -Fq 'g4ilapofix' /system/etc/init.qcom.post_boot.sh); then if $(grep -Fq 'g4ilapofix=true' /system/etc/init.qcom.post_boot.sh); then $(exit 0); else $(exit 1); fi; else sed -i -e '$a\\g4ilapofix=false; if $g4ilapofix; then if $(pm list packages | grep -q 'cz.youber.g4ilapo'); then echo 1 > /sys/devices/system/cpu/cpu0/online; echo 1 > /sys/devices/system/cpu/cpu1/online; echo 1 > /sys/devices/system/cpu/cpu2/online; echo 1 > /sys/devices/system/cpu/cpu3/online; else echo 0 > /sys/devices/system/cpu/cpu1/online; echo 0 > /sys/devices/system/cpu/cpu2/online; echo 0 > /sys/devices/system/cpu/cpu3/online; fi; else echo 0 > /sys/devices/system/cpu/cpu1/online; echo 0 > /sys/devices/system/cpu/cpu2/online; echo 0 > /sys/devices/system/cpu/cpu3/online; fi' /system/etc/init.qcom.post_boot.sh; $(exit 1); fi";
}
as = new String[1];
s = b;
as[0] = s;
g1 = new g(this, as);
a1 = com.a.b.a.b().a(g1);
_L3:
if (!((com.a.a.b.a) (g1)).l) goto _L2; else goto _L1
_L1:
com.a.b.a.a();
_L4:
return Integer.valueOf(a);
_L2:
long l = 50L;
Thread.sleep(l);
goto _L3
Exception exception;
exception;
goto _L4
}
protected final transient Object doInBackground(Object aobj[]) {
Integer ainteger[] = (Integer[])aobj;
return a(ainteger);
}
protected final void onPostExecute(Object obj) {
obj = (Integer)obj;
if (((Integer) (obj)).intValue() != 0) goto _L2; else goto _L1
_L1:
cz.youber.g4ilapo.MainActivity.a().setText("DISABLE 4CORE FIX");
cz.youber.g4ilapo.MainActivity.a().setEnabled(true);
Button button = cz.youber.g4ilapo.MainActivity.a();
h h1 = new h(this);
button.setOnClickListener(h1);
_L4:
return;
_L2:
if (((Integer) (obj)).intValue() == 1) {
cz.youber.g4ilapo.MainActivity.a().setText("ENABLE 4CORE FIX");
cz.youber.g4ilapo.MainActivity.a().setEnabled(true);
Button button1 = cz.youber.g4ilapo.MainActivity.a();
i j = new i(this);
button1.setOnClickListener(j);
}
if (true) goto _L4; else goto _L3
_L3:
}
}
Click to expand...
Click to collapse
@dydy85230
It can't be done by modifying system file. My app, and the one that costs 25 bucks do the same thing. They modify same system file, but it can modify it only after phone boots. It doesn't stick, so on every boot the phone boots on one core. Only way it *might* be possible is some modified custom kernel, but I don't think there is any for G4 that does that...
Sent from my ZTE A2017U using Tapatalk
Levent2101 said:
there https://forum.xda-developers.com/g4/themes-apps/root-4-cores-activator-t3538175
Click to expand...
Click to collapse
stojshic said:
@dydy85230
It can't be done by modifying system file. My app, and the one that costs 25 bucks do the same thing. They modify same system file, but it can modify it only after phone boots. It doesn't stick, so on every boot the phone boots on one core. Only way it *might* be possible is some modified custom kernel, but I don't think there is any for G4 that does that...
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
Ok thank you very much for this clarification.
The application works fine so it's perfect. :good:
However I will experiment with the file "init.qcom.post_boot.sh" while trying to modify it and integrate it with twrp and adb push
***
I would like to know about this post
I thank you very much
I have build Android Pie (9.0.0) successfully for Xperia X Performance f8131from AOSP source.
Instructions:
extract
F8131: android-pie-f8131-160119.zip
F8132: My build was not bootibg!
For another build, please refer to https://forum.xda-developers.com/showpost.php?p=78359565&postcount=67
Connect phone in fastboot mode (vol-up & power)
flash boot, system, userdata
# fastboot flash boot boot.img
# fastboot flash system system.img
# fastboot flash userdata userdata.img
Download SW_BINARIES_FOR_XPERIA_ANDROID_9.0_2.3.2_V4_TONE-1.ZIP/URL]
Unpack SW_BINARIES_FOR_XPERIA_ANDROID_9.0_2.3.2_V4_TONE-1.ZIP to obtain the vendor image.
Connect the device to your computer in Fastboot mode, by pressing volume up while inserting the USB cable. When the device is in Fastboot mode, the LED on the device will be illuminated in blue.
Flash the vendor image by entering the following commands in a terminal window:
# fastboot flash oem SW_binaries_for_Xperia_Android_9.0_2.3.2_V4_tone.img
Works: everything
Bugs:
Build from SE AOSP, kernel sources link: [URL="https://github.com/sonyxperiadev/kernel"]Sony kernel sources
Link for building from AOSP: Building from AOSP
Links:
Android Pie (9.0.0),Software binaries
XDA:DevDB Information
TheExplorer, ROM for the Sony Xperia X Performance
Contributors
NielDK
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: No Longer Updated
Current Beta Version: 9.0.0_r21
Created 2018-10-08
Last Updated 2019-02-06
OpenGAPPS
ROM is without Gapps, you must flash it if you need it.
Since /data is not manageable from TWRP, it cant handle encryption.
You will need to flash arm64 nano version for Android Pie (9.0) from https://opengapps.org/ and push it to device from PC terminal (command promt in Windows). You wont be able to access the file if you simply copy it from PC to device.
1. Boot device in TWRP
2. FORMAT data (not wipe)
3. Reboot recovery (no restart of system!!)
2. In shell/command prompt on PC
adb push open_gapps-arm64-9.0-nano-20181011.zip /sdcard/
3. flash open_gapps-arm64-9.0-nano-20181011.zip from TWRP
4. reboot
You can make /data available by formatting /data from TWRP, but you will loose all data. Remember a backup!
And, you will need to do this every boot!
Releases
R16: November security patches released
R21: December security patches released
Hi, what's about DRM? Have you installed drm fix?
grzegorz.u said:
Hi, what's about DRM? Have you installed drm fix?
Click to expand...
Click to collapse
No, AOSP is different code base (kernel) than stock Sony (Thanks God), so a DRM fix is not needed (not usable)
Hello
Thank you.Will you continue to maintain and fix bugs?Such as fingerprint
Hi
Thank you! I love the new rom.
Is there any way I can install GApps via TWRP? TWRP keeps failing to mount /data, even though it says decryption is successful.
NielDK said:
I have build Android Pie (9.0.0_r10) successfully for Xperia X Performance (f8131) from AOSP source.
Instructions:
extract android-pie-081017.zip ,
Connect phone in fastboot mode (vol-up & power)
flash boot, system, userdata
# fastboot flash boot boot.img
# fastboot flash system system.img
# fastboot flash userdata userdata.img
Download SW_BINARIES_FOR_XPERIA_ANDROID_9.0.6.3_R1_V1_TONE_BETA.ZIP
Unpack SW_BINARIES_FOR_XPERIA_ANDROID_9.0.6.3_R1_V1_TONE_BETA.ZIP to obtain the vendor image.
Connect the device to your computer in Fastboot mode, by pressing volume up while inserting the USB cable. When the device is in Fastboot mode, the LED on the device will be illuminated in blue.
Flash the vendor image by entering the following commands in a terminal window:
# fastboot flash oem SW_binaries_for_Xperia_Android_9.0.6.3_r1_v1_tone_beta.img
Works: everything
Bugs: Adding fingerprint crashes device
Build from SE AOSP, kernel sources link: Sony kernel sources
Link for building from AOSP: Building from AOSP
Links:
Android Pie (9.0.0_r10),Software binaries
XDA:DevDB Information
TheExplorer, ROM for the Sony Xperia X Performance
Contributors
NielDK
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Beta
Current Beta Version: 9.0.0_r10
Created 2018-10-08
Last Updated 2018-10-10
Click to expand...
Click to collapse
dude, do i need to flash gapps too? or this rom allready included gapps? btw thanks for your hard work!
Sdcrad said:
Thank you.Will you continue to maintain and fix bugs?Such as fingerprint
Click to expand...
Click to collapse
Yes, I will keep it updated and investigate any issues
pine5508 said:
Thank you! I love the new rom.
Is there any way I can install GApps via TWRP? TWRP keeps failing to mount /data, even though it says decryption is successful.
Click to expand...
Click to collapse
Yes, you can (and need to, if you want Google apps)
1. Boot device in TWRP
2. In shell/command prompt on PC
adb push open_gapps-arm64-9.0-nano-20181011.zip /sdcard/
3. flash open_gapps-arm64-9.0-nano-20181011.zip from TWRP
4. reboot
What's about rooting this rom? Have you already tried?
grzegorz.u said:
What's about rooting this rom? Have you already tried?
Click to expand...
Click to collapse
Of course, flash Magisk from TWRP
Any chance of a build for F8132
First, thank you for building this! I got inspired by you and tried to do the work myself and build for F8132, but after like 3 hours.. the build failed complaining about this:
Code:
FAILED: out/target/common/obj/JAVA_LIBRARIES/apache-xml_intermediates/dex-hiddenapi/classes.dex
/bin/bash -c "(rm -rf out/target/common/obj/JAVA_LIBRARIES/apache-xml_intermediates/dex-hiddenapi/ ) && (mkdir -p out/target/common/obj/JAVA_LIBRARIES/apache-xml_intermediates/dex-hiddenapi/ ) && (find out/target/common/obj/JAVA_LIBRARIES/apache-xml_intermediates/dex/ -maxdepth 1 -name "classes*.dex" | sort | xargs -I{} cp -f {} out/target/common/obj/JAVA_LIBRARIES/apache-xml_intermediates/dex-hiddenapi/ ) && (find out/target/common/obj/JAVA_LIBRARIES/apache-xml_intermediates/dex-hiddenapi/ -name "classes*.dex" | sort | sed 's/^/--dex=/' | xargs out/host/linux-x86/bin/hiddenapi --light-greylist=out/target/common/obj/PACKAGING/hiddenapi-light-greylist.txt --dark-greylist=out/target/common/obj/PACKAGING/hiddenapi-dark-greylist.txt --blacklist=out/target/common/obj/PACKAGING/hiddenapi-blacklist.txt )"
hiddenapi E 10-15 13:42:46 5124 5124 hiddenapi.cc:47] No DEX files specified
hiddenapi E 10-15 13:42:46 5124 5124 hiddenapi.cc:47] Command: out/host/linux-x86/bin/hiddenapi --light-greylist=out/target/common/obj/PACKAGING/hiddenapi-light-greylist.txt --dark-greylist=out/target/common/obj/PACKAGING/hiddenapi-dark-greylist.txt --blacklist=out/target/common/obj/PACKAGING/hiddenapi-blacklist.txt
hiddenapi E 10-15 13:42:46 5124 5124 hiddenapi.cc:47] Usage: hiddenapi [options]...
hiddenapi E 10-15 13:42:46 5124 5124 hiddenapi.cc:47]
hiddenapi E 10-15 13:42:46 5124 5124 hiddenapi.cc:47] --dex=<filename>: specify dex file whose members' access flags are to be set.
hiddenapi E 10-15 13:42:46 5124 5124 hiddenapi.cc:47] At least one --dex parameter must be specified.
hiddenapi E 10-15 13:42:46 5124 5124 hiddenapi.cc:47]
hiddenapi E 10-15 13:42:46 5124 5124 hiddenapi.cc:47] --light-greylist=<filename>:
hiddenapi E 10-15 13:42:46 5124 5124 hiddenapi.cc:47] --dark-greylist=<filename>:
hiddenapi E 10-15 13:42:46 5124 5124 hiddenapi.cc:47] --blacklist=<filename>: text files with signatures of methods/fields to be marked
hiddenapi E 10-15 13:42:46 5124 5124 hiddenapi.cc:47] greylisted/blacklisted respectively. At least one list must be provided.
hiddenapi E 10-15 13:42:46 5124 5124 hiddenapi.cc:47]
hiddenapi E 10-15 13:42:46 5124 5124 hiddenapi.cc:47] --print-hidden-api: dump a list of marked methods/fields to the standard output.
hiddenapi E 10-15 13:42:46 5124 5124 hiddenapi.cc:47] There is no indication which API category they belong to.
hiddenapi E 10-15 13:42:46 5124 5124 hiddenapi.cc:47]
[ 6% 969/15007] build out/target/product/dora/obj/ETC/sepolicy.recovery_intermediates/sepolicy
out/host/linux-x86/bin/checkpolicy: loading policy configuration from out/target/product/dora/obj/ETC/sepolicy.recovery_intermediates/sepolicy.recovery.conf
out/host/linux-x86/bin/checkpolicy: policy configuration loaded
out/host/linux-x86/bin/checkpolicy: writing binary representation (version 30) to out/target/product/dora/obj/ETC/sepolicy.recovery_intermediates/sepolicy.tmp
[ 6% 971/15007] target C++: statsd <= out/target/product/dora/obj/EXECUTABLES/statsd_intermediates/proto/frameworks/base/cmds/statsd/src/statsd_config.pb.cpp
ninja: build stopped: subcommand failed.
13:42:49 ninja failed with: exit status 1
This goes beyond my skills at the point, I'd appreciate any pointers you might have. Or you have the time, a build for F8132 please
aravindg said:
First, thank you for building this! I got inspired by you and tried to do the work myself and build for F8132, but after like 3 hours.. the build failed complaining about this:
Code:
FAILED: out/target/common/obj/JAVA_LIBRARIES/apache-xml_intermediates/dex-hiddenapi/classes.dex
/bin/bash -c "(rm -rf out/target/common/obj/JAVA_LIBRARIES/apache-xml_intermediates/dex-hiddenapi/ ) && (mkdir -p out/target/common/obj/JAVA_LIBRARIES/apache-xml_intermediates/dex-hiddenapi/ ) && (find out/target/common/obj/JAVA_LIBRARIES/apache-xml_intermediates/dex/ -maxdepth 1 -name "classes*.dex" | sort | xargs -I{} cp -f {} out/target/common/obj/JAVA_LIBRARIES/apache-xml_intermediates/dex-hiddenapi/ ) && (find out/target/common/obj/JAVA_LIBRARIES/apache-xml_intermediates/dex-hiddenapi/ -name "classes*.dex" | sort | sed 's/^/--dex=/' | xargs out/host/linux-x86/bin/hiddenapi --light-greylist=out/target/common/obj/PACKAGING/hiddenapi-light-greylist.txt --dark-greylist=out/target/common/obj/PACKAGING/hiddenapi-dark-greylist.txt --blacklist=out/target/common/obj/PACKAGING/hiddenapi-blacklist.txt )"
hiddenapi E 10-15 13:42:46 5124 5124 hiddenapi.cc:47] No DEX files specified
hiddenapi E 10-15 13:42:46 5124 5124 hiddenapi.cc:47] Command: out/host/linux-x86/bin/hiddenapi --light-greylist=out/target/common/obj/PACKAGING/hiddenapi-light-greylist.txt --dark-greylist=out/target/common/obj/PACKAGING/hiddenapi-dark-greylist.txt --blacklist=out/target/common/obj/PACKAGING/hiddenapi-blacklist.txt
hiddenapi E 10-15 13:42:46 5124 5124 hiddenapi.cc:47] Usage: hiddenapi [options]...
hiddenapi E 10-15 13:42:46 5124 5124 hiddenapi.cc:47]
hiddenapi E 10-15 13:42:46 5124 5124 hiddenapi.cc:47] --dex=<filename>: specify dex file whose members' access flags are to be set.
hiddenapi E 10-15 13:42:46 5124 5124 hiddenapi.cc:47] At least one --dex parameter must be specified.
hiddenapi E 10-15 13:42:46 5124 5124 hiddenapi.cc:47]
hiddenapi E 10-15 13:42:46 5124 5124 hiddenapi.cc:47] --light-greylist=<filename>:
hiddenapi E 10-15 13:42:46 5124 5124 hiddenapi.cc:47] --dark-greylist=<filename>:
hiddenapi E 10-15 13:42:46 5124 5124 hiddenapi.cc:47] --blacklist=<filename>: text files with signatures of methods/fields to be marked
hiddenapi E 10-15 13:42:46 5124 5124 hiddenapi.cc:47] greylisted/blacklisted respectively. At least one list must be provided.
hiddenapi E 10-15 13:42:46 5124 5124 hiddenapi.cc:47]
hiddenapi E 10-15 13:42:46 5124 5124 hiddenapi.cc:47] --print-hidden-api: dump a list of marked methods/fields to the standard output.
hiddenapi E 10-15 13:42:46 5124 5124 hiddenapi.cc:47] There is no indication which API category they belong to.
hiddenapi E 10-15 13:42:46 5124 5124 hiddenapi.cc:47]
[ 6% 969/15007] build out/target/product/dora/obj/ETC/sepolicy.recovery_intermediates/sepolicy
out/host/linux-x86/bin/checkpolicy: loading policy configuration from out/target/product/dora/obj/ETC/sepolicy.recovery_intermediates/sepolicy.recovery.conf
out/host/linux-x86/bin/checkpolicy: policy configuration loaded
out/host/linux-x86/bin/checkpolicy: writing binary representation (version 30) to out/target/product/dora/obj/ETC/sepolicy.recovery_intermediates/sepolicy.tmp
[ 6% 971/15007] target C++: statsd <= out/target/product/dora/obj/EXECUTABLES/statsd_intermediates/proto/frameworks/base/cmds/statsd/src/statsd_config.pb.cpp
ninja: build stopped: subcommand failed.
13:42:49 ninja failed with: exit status 1
This goes beyond my skills at the point, I'd appreciate any pointers you might have. Or you have the time, a build for F8132 please
Click to expand...
Click to collapse
I tried to build it a few times. Every time it took much more time than 3 hours and finally there were some errors. I will not try again.
Please make it for Dual Sim cards (F8132) I think android Pie will save battery. I really want stock, natural android instead of modified one.
Thanks beforehand.
Just to be clear, and answer your question.
Iam not going to make a build for dualsim version. I dont have that device.
good, volte support please
good, volte support please
can it be flashed to a locked bootloader phone?
No, like any other custom ROM, you need unlocked boot loader.
gaki25252 said:
can it be flashed to a locked bootloader phone?
Click to expand...
Click to collapse
I can build for F8132, did you modify the source before you could build successfully?
Hi there,
Afew monts back I installed MIUI 11/HybridOS from the user robin_vilensky_ on my Mi A2 Lite (Daisy), today I thout about trying something new, so I downloaded HavocOS and tried to install it, to be honest I'm pretty sure I did it wrong and ended up on a bootloop, however, I decided to go back to stock using the official firmware provided by Xiaomi and MiFlash, the process finished in 1 second (or less) with a message of success, obviously it was a false positive and the bootloop was still there. I tried different firmwares, methods (except via TWRP because I don't know how), USB wires, versions of MiFlash and more, none of them worked.
Then I tried to go back to MIUI 11 using the same ROM, it worked instantly, then I went back to MiFlash now that the phone was running an OS and I ran into the same result: the process finishes with "success" in one second, nothing happens to the device.
My only clue so far is the log from my MiFlash process, this is the latest one but it's basically the same for the rest of my previous attempts:
Code:
[02:05:27 a. m. de6068120605]:MiFlash 2019.12.6.0
[02:05:27 a. m. de6068120605]:idproduct: 53261 idvendor: 6353
[02:05:27 a. m. de6068120605]:Thread id:11 Thread name:de6068120605
[02:05:27 a. m. de6068120605]:image path:C:\Daisy\daisy_global_images_V10.0.18.0.PDLMIXM_9.0
[02:05:27 a. m. de6068120605]:env android path:"C:\Daisy\MiFlash20191206\MiFlash20191206\Source\ThirdParty\Google\Android"
[02:05:27 a. m. de6068120605]:script :C:\Daisy\daisy_global_images_V10.0.18.0.PDLMIXM_9.0\flash_all.bat
[02:05:27 a. m. de6068120605]:Physical Memory Usage:1658880 Byte
[02:05:27 a. m. de6068120605]:start process id 9108 name cmd
[02:05:27 a. m. de6068120605]:info1:$fastboot -s de6068120605 getvar product 2>&1 | findstr /r /c:"^product: *daisy" ||
[02:05:27 a. m. de6068120605]:info2:"findstr" no se reconoce como un comando interno o externo,
[02:05:27 a. m. de6068120605]:info2:programa o archivo por lotes ejecutable.
[02:05:27 a. m. de6068120605]:flash done
[02:05:27 a. m. de6068120605]:flashSuccess True
[02:05:27 a. m. de6068120605]:isFactory False CheckCPUID False
[02:05:27 a. m. de6068120605]:before:flashSuccess is True set IsUpdate:True set IsDone True
[02:05:27 a. m. de6068120605]:after:flashSuccess is True set IsUpdate:false set IsDone true
[02:05:28 a. m. de6068120605]:No hay ningún proceso asociado a este objeto.
[02:05:28 a. m. de6068120605]:flash done
[02:05:28 a. m. de6068120605]:process exit.
info1 and info2 translate to:
Code:
[02:05:27 a. m. de6068120605]:info2:"findstr" is not recognized as an internal or external command,
[02:05:27 a. m. de6068120605]:info2:program or executable batch file.
Even with this I'm unable to point out what is happenning that prevents me from going back to stock. I ask for your kind help. Thanks.
Solution: Unable to install official firmware after installing MIUI 11 / HybridOS ROM
Apparently this is one of those posts that solve by themselves, after translating the error I decided to search it on the web I stumbbled uppon a StackOverflow post about the same error on a different context, the solution provided there consists on:
Go to System Properties > Enviroment Variables (Bottom right on Advanced Options tab) > Look for the Path variable, select it and click on edit > Click on new and paste/write
Code:
C:\Windows\system32
> Accept the changes and reboot the computer
Note that there is two places to find Path on the same window, I edited both of them for good measure.
There it is, now I'm able to flash the firmware with no problem.
Hello,
I have bought a Xiaomi Mi 10T Pro, "apollo" code name, with MIUI Global 12.0.10.0 (QJDEEUXM) and I want to flash Miui Global 12.0.4.0.QJDIDXM - Indonesia rom (for miui dialer).
On my current ROM after running "fastboot getvar anti" returns 1.
Well, the .bat files from the fastboot 12.0.4.0.QJDIDXM, are a little bit different from other fastboot phones roms versions (see below).
Anyway, the question is more than clear:
Is it safe to flash this rom?
---
::check anti_version
if exist %~dp0images\anti_version.txt (for /f "delims==" %%a in (%~dp0images\anti_version.txt) do (set CURRENT_ANTI_VER=%%a))
if [%CURRENT_ANTI_VER%] EQU [] set CURRENT_ANTI_VER=0
for /f "tokens=2 delims=: " %%i in ('fastboot %* getvar anti 2^>^&1 ^| findstr /r /c:"anti:"') do (set version=%%i)
if [%version%] EQU [] set version=0
set anticheck="antirollback check pass"
if %version% GTR %CURRENT_ANTI_VER% set anticheck="Current device antirollback version is greater than this pakcage"
echo %anticheck% | findstr /r /c:"pass" || @ECHO "Antirollback check error" && exit /B 1
---
Thank you in advance!
have u unlock ur bootloader ?
Yes, of course.
Witajcie Mój problem w Mi9 SE polega na tym ze nie moge wogóle wgrać TWRP i gdy chce MiFlashem Wgrac Na nowo Firmware Fastboot 3 razy Restart i Wisi nie Wgyrwa niczego(Sprawdzałem prze całą Noc) ADB pokazuje mi same Znaki Zapytania Podczas Pomendy Fastboot Devices Jakies Propozycje Macie Bede Dozgonnie Wdzieczny
MOD EDIT: Please post only in English according to the FORUM RULES or at least add an English translation below your foreign language(Google translator for example),translation added below:
Hello.My problem in Mi9 SE is that I can not upload TWRP at all and when I want to MiFlashem Reload Firmware Fastboot 3 times Restart and hangs nothing (I checked all night) ADB shows me the Question Marks During the Fastboot Devices Prompt Any Proposals I will be forever grateful