I bricked it trying to update cRdroid and now it's got the empty bootloader with 00000 and missing imei. Anyway I looked around and turns out I have to bankflash it then I think I'll rewrite the gpt partition and hope I don't have to reflash the stock rom. The problem is I can't boot in EDL, it boots in fastboot mode. I tried manually installing the 9008 drivers but it doesn't recognize. Do I have to short the 2 pins on the motherboard or is there anything else I could try?
uhh
Related
I tried to install Conceptify ROM. When I was making a partition, I had mistake, instead of typing rm 29, i typed rm 3. Then I came back to recovery and power off telephone. At first time I was able to enter recovery, but then I wasnt. Flashmode and Fastboot arent working, device dont start. On my pc its named like an unknown device or somc, Does anyone can help?:crying:
Hi bro , did have solve your problem yet?? , I've got the same situation as you the same rm 3 if only I added another number , I think that block 3 has files for flashboot that is why it isn't working anymore , I tried with xperia companion but also asked about that flashboot
The only solution is to find a workaround on how to flash the firmware through fastboot , anyone has any idea??
partition 3 is s1sbl (related to bootloader), so you can't restore your device via flashtool, pc companion or emma. it's hard bricked, sorry
it can be recovered if you have any jtag box
Cubbins said:
partition 3 is s1sbl (related to bootloader), so you can't restore your device via flashtool, pc companion or emma. it's hard bricked, sorry
it can be recovered if you have any jtag box
Click to expand...
Click to collapse
thanks for clarifying , So the jtag box used for recover the lost partitions or repartitions the whole device?
do you know any the proccess to recover with jtag?
also when I tried to fix that partition with fastboot or flash bootimg or recovery it's said that my partitions table is not exist
othmane.os said:
thanks for clarifying , So the jtag box used for recover the lost partitions or repartitions the whole device?
do you know any the proccess to recover with jtag?
also when I tried to fix that partition with fastboot or flash bootimg or recovery it's said that my partitions table is not exist
Click to expand...
Click to collapse
please join to our telegram chat then we can discuss about your problem
Any joy in getting your boot partition back. I may have gone the same route with my M4. No flashmode, no LED when connecting to USB, etc.
Links to possible JTAG solutions for this phone?
mannemerak said:
Any joy in getting your boot partition back. I may have gone the same route with my M4. No flashmode, no LED when connecting to USB, etc.
Links to possible JTAG solutions for this phone?
Click to expand...
Click to collapse
which partition have you mistakenly delete? did fastboot still work for you? if so you can flash recovery and restore your OS and somehow you could fix flashmode with usb debugging on
but if you're unlucky like me with locking the bootloader mistakenly then
there's setool box and JTAG box but the question is which one is easier for restoring boot partitions
also I saw some way of restore partitions but that was with emmc replacement
Hello guys!
My Redmi 3 Pro didn't boot into TWRP so I followed the instructions in this post to fix it but I didn't notice that there is a file attached and used TWRP image instead. Now my phone is completely bricked, I can't put it into recovery, fastboot nor edl mode. There is no reaction after plugging charger. But when I connect it to a computer it's visible as Qualcomm HS-USB QDLoader 9008 so I thought it automatically runs into edl somehow and tried to flash using MiFlash but it always fails with "sahara read end error with status 9" even when using deep flash cable. I've never unlocked it's bootloader but was running LineageOS and then xiaomi.eu ROMs so I think it was unlocked inofficially by the seller I bought it from. Is there a way to fix it?
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
So I have this really really frustrating issue where basically WiFi, Bluetooth just won't turn on.
Doing some research I tried flashing persist file through Mi Flash and Miracle Box. Now that I am trying to install a custom ROM, it gets installed without any errors but it won't boot either. I get the screen showing boot animation of the ROM and then Mi logo. Then it just boots up to ROM animation again then Mi logo, just an endless boot loop. I have no idea what's causing this.
I have tried everything I know but still nothing works
Any suggestions?
In which partition did you flash persist using miracle box?
I would recommend you to goto EDL mode and then flash official firmware with QFIL or Miracle box. To goto EDL mode, boot in fastboot mode and enter this command: fastboot oem edl echo > nul 2>&1
Else you may use the test point method to boot to edl.
[Note: this will erase ur imei, mac. ] -> If still problem persists, try to erase all partitions from miracle box and flash the firmware again. Sometimes this solves the problem.
Do you have ur EFS backed up? So that u can flash them back to get ur imei, mac. Else note down your imei, mac, bt mac before trying 2nd method. You have to manually repair imei, mac etc which is not hard though.
If this also fails, maybe ur wifi chip is gone. Get the schematics, hunt down the wifi chip and check voltage at the main capacitor near the wifi chip. if voltage is fine then replace the chip. if voltage is not correct or 0, then it would be hard to find what exactly is causing it.
Does anybody know the pins need to be shorted for me to boot into 9008 Mode (EDL mode)? EDL Cable, DIY EDL Cable, and buttons doesn't work for me. Also, I can't boot to fastboot and recovery.. Thank you!
xXEphie said:
Does anybody know the pins need to be shorted for me to boot into 9008 Mode (EDL mode)? EDL Cable, DIY EDL Cable, and buttons doesn't work for me. Also, I can't boot to fastboot and recovery.. Thank you!
Click to expand...
Click to collapse
how you bricked the phone?as i know this phone partition is a/b so if something went wrong with a software update or u mess with anything related to software it will boot with the old working system
mhammad77 said:
how you bricked the phone?as i know this phone partition is a/b so if something went wrong with a software update or u mess with anything related to software it will boot with the old working system
Click to expand...
Click to collapse
I used "flash ab" command on ADB while installing TWRP then I got stucked on recovery loop (There's a thread on using the right ADB commands to flash TWRP.. but it's too late for me haha). While trying to restore the old recovery, i used a command (I forgot what that command is) to clear recovery ab partition and tried the proper way to install TWRP..
It worked out just fine until I tried to flash latest EU rom , failed on 50%.. cleared all partitions and rebooted to recovery mode then viola! no display but the unit is warm
Anyways, we (me and the tech guy that I contacted to fix hard brick) already located the test points for this unit.. I don't know if there are devs who already posted the test points for this unit on the internet/forum sites.
Fixed from Feb. 16, 2023. That time, only K40 series has the test point on the internet.
P.S. Oh right, I haven't posted it in here (XDA)
P.S.S. Now that I'm reviewing this thread, I remembered that I used A12 version of TWRP.. but I updated to MIUI 14 (A13) before i began installing TWRP...