Hi, offering $10 PayPal to anyone that helps me fix my phone. (Don't know if this is against the rules, if so, I take it back).
Here's the situation:
Was on stock MIUI Global 9.5.8.0 with RedWolf Recovery.
Did a backup and flashed LineageOS
Wasnt happy with it and flashed back the backup, including the Firmware and EFS partitions, basically every partition
Bootloop, WiFi and BT driver prolly messed up, cant connect and restarts upon trying to connect to WIFI/BT.
Tried flashing other firmware, various combinations of wipes, flashes, MiFlashTool fastboot rom, nothing helped.
Tried flashing with EDL, the newest ROM gives me "Too many lines in XML file", old ROM flashed fine, but then couldn't even get to fastboot.
Now: Can't get to fastboot nor recovery, phone goes to EDL mode w/ red LED blinking when connected to PC.
QFIL gives me "Cannot read packet header, read 0 bytes", same with MiFlash.
What are my options guys? Is this a dead case? Any help is greatly appreciated.
I flashed a wrong TWRP recovery on my Nokia 1 (a one from a Huawei P10 Lite). After that, i rebooted reinserting the battery, it showed android logo + "orange state", 10secs of blackscreen, and bootloop "forever".
I tried to get into bootloader mode via adb at reset
Code:
fastboot reboot bootloader
, but it doesn't work ("waiting for any devices"). Note that i flashed the wrong recovery successfully via adb, and previously i had a correct recovery flashed with adb too.
Flashing the TA 1056 stock rom via OST didn't work either; OST doesn't detect the phone (probably because i can't get into bootloader mode).
I tried with SP Flash Tool too, flashing the TA 1056 MT6737M firmware, but CHIP TYPE NOT match, scatterChipType 143, targetChipType 160. In the scatter file (i don't know why), i changed "platform: MT6752" to "platform MT6737M" and holding down both volume buttons till the end, i could flash the complete firmware.
Then, i reset reinserting the battery and obtain the ethernal bootloop with a blackscreen; the phone vibrates every 10secs until i remove the battery (no logos show up).
I can't do anymore; i can reflash with SP Flash Tool, but it's the same.
Please, help me
*PD: i flashed via SP Flash Tool with "Format All + Download" option; can it be a problem?
Man... I am right now where you were.
Same error. Did you find any way out?
*sigh*
Hey OP, you still looking to troubleshoot? I might be able to help
I have realme 3 pro and my bootloader was unlocked skme days ago i accendenatlly flash some malware application and then my device switch of and bootloop on custom rom logo then i tried to go in fastboot mode but its again bootloop in fastboot logo However i tried to boot in device then i see my network did not show and my wifi also no working then i format my rom amd change roms but its booting but not going in fastboot mode (i go to recovery through adb cammands) then some tell me go to stock rom i flash it through recovery (Remember i cant go to fastboot mode i go to recovery through adb cammands) and i flash the the stock rom after flash stock rom then my device did not setup becouse of network then i pass it out through *#813# now in my device not showing any type of signal expect Bluetooth and did not boot into fastboot and now it have stock revovery and also my imei no and baseband version is null before i am in twrp whenever i flash something then show me a eror "failed to mount presis file" like this but i also visit service centre but they flash Rui 2.0 and i talk him about signal and imei no but they telling its motherboard issue and its cost around 8k Indian rupees now i am fouked so help me to this
did you manage to fix it?
yeah, can anyone check this command in bootloader and paste the output here ? I would be very thankful because my phone is stuck in EDL mode and can't be flashed using Qfil. I need to check the output of this command to hopefully be able to figure something out.
Ask @kofijordan how he accomplished it, we went throught the same scenario with slot_a & slot_b and EDL. I'm thinking you have the wrong QPST/QFIL. Send him a private message or maybe he'll see the mention and let you know what his setup has installed.
&(*) said:
Ask @kofijordan how he accomplished it, we went throught the same scenario with slot_a & slot_b and EDL. I'm thinking you have the wrong QPST/QFIL. Send him a private message or maybe he'll see the mention and let you know what his setup has installed.
Click to expand...
Click to collapse
The thing is, I need to check if there is anything like unlock_a & unlock_b partitions. When I flashed the sn.img it could be the A slot only, and now it has switched to B which bootloader might be locked and preventing user from using Qfil.
That's not your issue with switching the current slot, you didn't clone all your slots and now it doesn't have everything it needs to mount properly back into the bootloader. My bet is you have the wrong software and need the more recent QPST and maybe the vc++ redistributables (both 2010 & 2012 x86).
I'm using Qfil 2.0.3.5 from QPST 2.7.496 (the latest one i could find) and have the qualcomm drivers and vc installed, and it's still the same
Both vc 2010 & 2012? Are you executing QFIL from the QPST path where all the .dll dependencies are?
&(*) said:
Both vc 2010 & 2012? Are you executing QFIL from the QPST path where all the .dll dependencies are?
Click to expand...
Click to collapse
Yup, everything is as should be
Did you previously use QFIL without the issues you are facing currently, meaning the phone in it's present state is the issue?
&(*) said:
Did you previously use QFIL without the issues you are facing currently, meaning the phone in it's present state is the issue?
Click to expand...
Click to collapse
I wrote it in another post already, from the moment i started tinkering with it (it was fully functional back then), there always was this Sahara error happening
I went through a similar process when I first installed QFIL with errors but fixed them after installing vc 2010 & vc 2012 x86 redistributables. In device manager is there a yellow exclamation anywhere when you plug the device in (missing driver)? I remember reading you installed QFIL v2 from lolinet, correct? QPST (.496) comes with it, so my guess is you don't have the right version of QFIL or have replaced it with the other version and now there is a mismatch when it executes. You could also try deleting temp data stored as a hidden folder under (username)/appdata/local/temp, though I don't think that is what's causing the issue. If all else fails delete every reference of data after uninstalling QPST (ProgramData, ProgramFiles(x86), etc) and reinstall it and do not use the other QFIL version supplied from lolinet.
&(*) said:
I went through a similar process when I first installed QFIL with errors but fixed them after installing vc 2010 & vc 2012 x86 redistributables. In device manager is there a yellow exclamation anywhere when you plug the device in (missing driver)? I remember reading you installed QFIL v2 from lolinet, correct? QPST (.496) comes with it, so my guess is you don't have the right version of QFIL or have replaced it with the other version and now there is a mismatch when it executes. You could also try deleting temp data stored as a hidden folder under (username)/appdata/local/temp, though I don't think that is what's causing the issue. If all else fails delete every reference of data after uninstalling QPST (ProgramData, ProgramFiles(x86), etc) and reinstall it and do not use the other QFIL version supplied from lolinet.
Click to expand...
Click to collapse
Every program's version was the most recent and I had everything installed correctly but I decided to check the drivers details under the HS-USB QDLOADER 9008 device and it turned out, my antivirus had installed a usb driver that was superior to the Qualcomm one and was overriding it. Now Qfil loads some things but still shows the error, which now is ERROR: it took x seconds to open port. Which is longer than 3. This indicates your target is not stable.
A little progress; now try with the device fully powered down, hold both volume buttons and power button, screen should flash for a split second then plug it in and flash the build right away.
Can't do that because this phone is constantly in edl mode and there is no way to turn it off. Holding power off or power off + volume for 15 seconds causes Qfil to blink the port for a split second but there is nothing on the device.
I tried to do it for like 30 mins and every time it reports com port timeout at around 10sec instead of 3
SOOOO
it works !!
Turns out i wasted like 20 hours trying to flash it. The first error was caused by a different driver interfering with the appropriate one. The next one - timeout - solved it by using the _lite elf file instead of _ddr. The _lite one should have flashed the Super.img partition as far as i know. Now it boots .062.
That's good news. Would you be willing to try to install the CN Pro 2 version?
If so, flash the bundle and right after it finishes boot into the bootloader and type:
reboot fastboot
(make sure it registers as a fastboot device), then
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
Both vbmeta and vbmeta_system can be found within the CN 12.5.591 bundle.
Downloading cn roms atm. There are some problems after reflashing the global firmware. The baseband has been wiped along with imei info so no network access for now, there should be no radio.img so something entirely different may be causing it. There is abnormal battery drain, ca. 30-40% during the night with wifi turned off and power saving mode enabled, no LEDs nor fan working. Also the front camera isn't calibrated correctly and the motor tries to move it like double the usual distance. Flashing the persist.img didn't help and i have no QCN backup but it's no big deal as i bough it for gaming and tinkering.
&(*) said:
That's good news. Would you be willing to try to install the CN Pro 2 version?
If so, flash the bundle and right after it finishes boot into the bootloader and type:
reboot fastboot
(make sure it registers as a fastboot device), then
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
Both vbmeta and vbmeta_system can be found within the CN 12.5.591 bundle.
Click to expand...
Click to collapse
with or without flashing vbmeta and vbmeta_system all it does is boot up, shows the boot animation with chinese SD888 banner and displays the incorrect firmware warning.
Flashing the CN 12.5.535 via Qfil with boot.img already swapped to TWRP boot.img in the root folder also does not work, the phone is stuck in bootloader just like with global rom and modified boot.img.
Malberd said:
Downloading cn roms atm. There are some problems after reflashing the global firmware. The baseband has been wiped along with imei info so no network access for now, there should be no radio.img so something entirely different may be causing it. There is abnormal battery drain, ca. 30-40% during the night with wifi turned off and power saving mode enabled, no LEDs nor fan working. Also the front camera isn't calibrated correctly and the motor tries to move it like double the usual distance. Flashing the persist.img didn't help and i have no QCN backup but it's no big deal as i bough it for gaming and tinkering.
Click to expand...
Click to collapse
Everything you mention is why QFIL should be used very cautiously and carefully. It's best used for patching or targeting a specific partition. There is a tutorial that has been reported to work for Legion Duels posted here . You might need to request a blank QCN from another Legion Duel 2/Pro 2 owner, or the blank QCN posted within that thread might be modifiable to restore what's missing. The porting from Pro 2 to Duel 2 is turning out to be an unnecessary nightmare and the Lenovo Hong Kong devs need to address it with a solution. The device feels practically abandoned and it shouldn't be.
ok hear me out, I'm a newbie, and I missed up, plz help
I was trying to root my device following this tutorial, I flashed twrp and vbmeta and every thing went alright without errors, I booted the phone into recovery to continue as how the tutorial said, but it gave me the orange state error and it restarted into system but now the device is factory reset, I enabled usb debugging and went on to follow this tutorial, every thing went same as before and I couldn't boot into recovery, so I decided to flash the "orange_state_disabler_MTK Only.zip" with adb and every thing went downhill from there, It won't boot to recovery, bootloader nor system, It just stays at a blank screen after the logo and the orange state message, It is recognized by adb as "recovery" and I can do adb commands but I can't boot to bootloader to flash the stock firmware, I found this thread and tried using the tool mentioned there, Faced an error, solved it and the phone still won't boot to any thing.
so, is there any way I can get out of this situation ?
TLDR / what you should know/ idk ¯\_(ツ)_/¯
- did something wasn't supposed to do
- can't boot to recovery
- can't boot to bootloader
- device recognized by adb but can't do fastboot commands
- device is recognized by MTKAuthBypassToolV25
- can't shutdown nor restart using phone physical buttons
- don't know if the below screenshots would help with any thing, but here goes nothing
You have misunderstanding, Orange State does not cause anything. That is just notification that bootloader is unlocked, nothing more. Therefore the Orange State Disabler cannot fix anything. You don't need this at all.
But it seems it destroyed fastboot. flash lk from SP Flash Tool
aIecxs said:
You have misunderstanding, Orange State does not cause anything. That is just notification that bootloader is unlocked, nothing more. Therefore the Orange State Disabler cannot fix anything. You don't need this at all.
But it seems it destroyed fastboot. flash lk from SP Flash Tool
Click to expand...
Click to collapse
please explain, I don't know what IK is, and if I could flash things with SP flash tools, wouldn't I be able to flash stock firmware?
lk - little kernel. that is the partition where fastboot lives (and was modified by Orange State Disabler).
you need partition image from stock ROM and any flash tool to restore its original state.
i can't do that because i can't boot to bootloader
you don't need bootloader, only preloader or bootrom
ok turns out ima an idiot and misunderstood the entire situation , this is my first dealing with an mtk device so i thought sp flash tool is like odin and you need to be in download mode to flash things so i panicked, and didn't read well how to use the tool.
flashed stock firmware and the phone is up and running again
thanks for your help man really appreciate it and sorry for wasting your time