Hello guys. I write another post because I found what is the real problem on my phone.
Here is my old post : https://forum.xda-developers.com/redmi-note-3/help/kenzo-black-screen-red-dot-blinking-t3891141.
So, my phone is stuck on bootloop when I try to boot it. It doesn't stop rebooting forever.
Here is a video showing the bootloop http://youtu.be/pi2-fnSNGGA.
What I've already done :
Deep cable to unbrick my phone and it was successful (phone now detected as Qualcomm HS-USB QDLoader 9008)
Flash stable or dev rom in EDL mode with MiFlash (I tried a lot of version...)
Flashing a TWRP rom in EDL mode with MiFlash
eveything
fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.029s]
finished. total time: 0.031s
Click to expand...
Click to collapse
I really need help guys... :crying: I've no phone anymore for the moment xD
Are you flashed lazy flasher??
ketan7731 said:
Are you flashed lazy flasher??
Click to expand...
Click to collapse
I used lazy flasher before to get my phone rooted but i didn't used it when i bricked my phone
There is something weird in my phone, i can't boot with power button anymore... I'm forced to boot with USB cable.
Here is a video showing my problem : https://youtu.be/3uZceq1mqys
Rtxx said:
There is something weird in my phone, i can't boot with power button anymore... I'm forced to boot with USB cable.
Here is a video showing my problem :
Click to expand...
Click to collapse
Did u try unofficial unlock again?
https://forum.xda-developers.com/redmi-note-3/how-to/guide-rn3-pro-se-t3565172
I've done this one and now my phone is unlocked but still in bootloop
fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.013s]
finished. total time: 0.014s
Click to expand...
Click to collapse
I have tried to flash in fastboot TWRP official but i cant access to recovery after the flash.
fastboot flash recovery twrp-3.2.3-0-kenzo.img
target reported max download size of 536870912 bytes
sending 'recovery' (18580 KB)...
OKAY [ 0.597s]
writing 'recovery'...
OKAY [ 0.131s]
finished. total time: 0.734s
Click to expand...
Click to collapse
Rtxx said:
https://forum.xda-developers.com/redmi-note-3/how-to/guide-rn3-pro-se-t3565172
I've done this one and now my phone is unlocked but still in bootloop
I have tried to flash in fastboot TWRP official but i cant access to recovery after the flash.
Click to expand...
Click to collapse
U e official unlocked. But u cant boot into recovery .
Connect phone to pc in fastboot mode.
And use command.
fastboot reboot recovery
I have similar problem with my kate and locked bootloader. It started when my phone needed about 10-15 seconds to turn on and it started freeze. After freeze it rebooted itself. After rebooted it worked normal about 1 hour and again freezed. Untill the moment when it didin't start. I couldn't go into fastboot mode or edl mode (vol + and power). But I found solution to switch into edl mode by disconnect the buttery. And it worked. So i had in device manager qualcomm hs-usb qdloader 9008. I flashed phone with miui 10 and it was successful. But now I have black screen, no fastboot mode only red light blinking. And now I have strange situation. When I connect phone to computer, in device manager I see 900E device. When I disconnect phone from computer and disconnect battery for a moment and connect again to computer, in device manager I have 9008 device. When I try flash I have error ping target failed XiaoMiFlas.code.bl.SerialPortDevice.ping(). I also made and used deep flash cable but it didin't help. Only thing I didin't try is test point but i think it's doing the same as deep flash cable. What am I doing wrong? Or maybe it is hardware issue? (broken emmc or something)
Related
Hi, I have tryed everything I could find in this forum now but nothing worked.
I'm installing TWRP on a Oneplus X via Fastboot as I did with an other OPX before without problems.
Now when I flash TWRP via Fastboot and reboot (holding power + volume down) TWRP doesn't boot.
The phone is stuck at the OP logo with the "powered by android" logo. I can restart it by holding down the power button for a while but then TWRP gets obviously overwritten by stock recovery.
The only thing I recognized is the output of
Code:
fastboot oem device-info
is different from the device I flashed before:
Code:
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.017s]
finished. total time: 0.018s
Shouldn't the tempered flag be on true? Could this be the problem?
I really would appreciate your help! Thank you!
obermeier said:
Hi, I have tryed everything I could find in this forum now but nothing worked.
I'm installing TWRP on a Oneplus X via Fastboot as I did with an other OPX before without problems.
Now when I flash TWRP via Fastboot and reboot (holding power + volume down) TWRP doesn't boot.
The phone is stuck at the OP logo with the "powered by android" logo. I can restart it by holding down the power button for a while but then TWRP gets obviously overwritten by stock recovery.
The only thing I recognized is the output of
Code:
fastboot oem device-info
is different from the device I flashed before:
Code:
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.017s]
finished. total time: 0.018s
Shouldn't the tempered flag be on true? Could this be the problem?
I really would appreciate your help! Thank you!
Click to expand...
Click to collapse
But u still able to boot into stock recovery right? If u r on oos 3.1.3 flashing official twrp will not work, u need to use oos3 twrp... After flashing it by fast boot, boot into it directly by giving cmd "fastboot boot nameofrecovery.img"
Thank you for your reply!
Just in this second I made a TWRP boot on my phone. I took the one from blu_spark. I guess this is kind of a oos3 twrp.
For people looking for it in the future: I took the twrp file from here: http://forum.xda-developers.com/devdb/project/?id=12587#downloads
Is there an official oos3 twrp? Because I took the most recent from the twrp.me download site and it didn't worked...
obermeier said:
Thank you for your reply!
Just in this second I made a TWRP boot on my phone. I took the one from blu_spark. I guess this is kind of a oos3 twrp.
For people looking for it in the future: I took the twrp file from here: http://forum.xda-developers.com/devdb/project/?id=12587#downloads
Is there an official oos3 twrp? Because I took the most recent from the twrp.me download site and it didn't worked...
Click to expand...
Click to collapse
Till now der is no official twrp for mm bootloader.. But dis one is unofficial like bluespark https://www.androidfilehost.com/?fid=529152257862676606 by NachiketNamjoshi
Hi,
This morning i had the very bad idea of changing my recovery, and now I'm stuck!
I'm running CM13 and i wanted to update to the latest release, but I got errors, so I said "well, maybe they need their recovery and TWRP is not good anymore for some reasons.
I downloaded the new recovery from CM website (yes, it is the correct version of the phone) and installed it. Well, i don't know what happened, but now I'm stuck into the bootloader (fastboot mode detects my device in cmd)
I decided to flash TWRP again, but now my bootloader is locked (for some mysterious reason, as it was unlock by both the dev option toggle and by a previous OEM unlock command).
I've been trying to unlock it again, but nothing. I lunch
Code:
fastboot oem unlock
and all it does is coming up with this message:
Code:
OKAY [ 0.015s]
finished. total time: 0.016s
The phone reboots and it's stuck as I have access to neither recovery or OS. It just stays there and i have to go back into the bootloader.
the device info from fastboot is:
Code:
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.010s]
finished. total time: 0.010s
I also tried with
Code:
fastboot flashing unlock
but it stays stuck with the 3 dots without doing anything.
Is there anything i can do or i have to trough my device into the bin?
thanks
nickimola said:
Hi,
This morning i had the very bad idea of changing my recovery, and now I'm stuck!
I'm running CM13 and i wanted to update to the latest release, but I got errors, so I said "well, maybe they need their recovery and TWRP is not good anymore for some reasons.
I downloaded the new recovery from CM website (yes, it is the correct version of the phone) and installed it. Well, i don't know what happened, but now I'm stuck into the bootloader (fastboot mode detects my device in cmd)
I decided to flash TWRP again, but now my bootloader is locked (for some mysterious reason, as it was unlock by both the dev option toggle and by a previous OEM unlock command).
I've been trying to unlock it again, but nothing. I lunch and all it does is coming up with this message:
The phone reboots and it's stuck as I have access to neither recovery or OS. It just stays there and i have to go back into the bootloader.
the device info from fastboot is:
I also tried with but it stays stuck with the 3 dots without doing anything.
Is there anything i can do or i have to trough my device into the bin?
thanks
Click to expand...
Click to collapse
Try this
http://forum.xda-developers.com/one...ga-unbrick-guide-hard-bricked-t3272108/page18
shravanv3 said:
Try this
http://forum.xda-developers.com/one...ga-unbrick-guide-hard-bricked-t3272108/page18
Click to expand...
Click to collapse
Yes, this worked!
Thanks a lot.
Good day,
I would like to ask for an advice. One friend of mine has redmi 3 phone and sudenly the phone stuck in fastboot. I tried every possible combinations with power to bring it up. I got Mi logo (it looks like phone like to start) but then black screen and fastboot again. If I connect usb cable to the phone and pc/charger, fastboot keeps rebooting. Phone is locked. No twrp no other attempts to unlock. Any advice how the phone bring to life again? If I turn phone off, then turn on into fastboot and connect it to pc, i have few seconds to send a command (fastboot/adb). Then phone reboot into fastboot again, but cant send any commands at all. Until I disconnect it, turn phone off and on into fastboot again. I tried fastboot reboot command, command accepted, but system wont boot and then again into fastboot. Also I tried to turn it into download mode, it shows up for few seconds in mi flash, but then vibrate and restart to fastboot.
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.007s]
finished. total time: 0.008s
Thanks for any advice.
a bit similer with this case
my friend bought it 20 days ago and he unlock it
but he cant flash twrp as like guides
he had no expirience before this
so i get tablet and tried to solve the problem but
fastboot doesnt work properly
fastboot devices/reboot/device-info works
but
fastboot flash recovery twrp.img/ flash boot boot.img(guide on carbon rom)/boot twrp.img/and etc that for flashing or change any system
does not work
massage like failed(long link/bigger than max allowed)
changing everytime i try
i though there might some issues when my friend unlock the bootloader
so i 'fastboot oem lock' and try to unlock again
but from then fastboot not work properly
can be boot or 'adb reboot fastboot' to fastboot
but it become unknown device on windows device manager
fastboot command not work
when mi flash try to detect device, fastboot mode end and 'press any key to power off' screen came out
some times it working for few seconds so i try unlock with official xiaomi tool but tool said 'already unlocked'
right after i locked bootloader i used 'fastboot oem device-info' and checked bootloader is locked
i can switch oem unlock on/off in developer option but it doesnt change anything
i searched as i can and edl mode looks last
but few things to consider
1. its official chinese rom and working now
2. i dont know broken fastboot can be restored with flashing rom with edl (i flash rom with update app in settings but not solved)
3. adb reboot edl doesnt work it just rebooted(should teardown it but i dont know what pin to short)
the reason why i trying to install custom rom(or eu rom) is my friend and i not live in native english country
hope i get some help
thx
Ryzen CPU?
thE_29 said:
Ryzen CPU?
Click to expand...
Click to collapse
ryzen 1, 2, intel sandy etc
tried all i got
Im almost sure flashing stock rom with MiFlashTool should solve this problem as it does flash partritions as recovery and fastboot too. Have you tried this one?
KrakmanCz said:
Im almost sure flashing stock rom with MiFlashTool should solve this problem as it does flash partritions as recovery and fastboot too. Have you tried this one?
Click to expand...
Click to collapse
nope
cant go into edl mode until i teardown it
miflash 2018 doesnt connect with pad on fastboot mode
miflash should connect to mi devices when in fastboot mode. I would consider checking drivers for the device, try to install MiSuite, it should install all drivers needed for those actions. Also, in the fastboot mode you are trying some commands, are you using Windows 10 Powershell or basic cmd?
chocodesk said:
ryzen 1, 2, intel sandy etc
tried all i got
Click to expand...
Click to collapse
Ok, when you also tried Intel.. But Ryzen CPUs have major problems with the flash tool and the tablet. Would not do anything on Ryzen PCs.
KrakmanCz said:
miflash should connect to mi devices when in fastboot mode. I would consider checking drivers for the device, try to install MiSuite, it should install all drivers needed for those actions. Also, in the fastboot mode you are trying some commands, are you using Windows 10 Powershell or basic cmd?
Click to expand...
Click to collapse
on basic
with was detected as fastboot before
but know its unknown on device manager
update driver doesnt work
Try using a usb 2.0 port? If you ever need to, hard reset is holding all buttons at once for 30 seconds.
Dannyboy3210 said:
Try using a usb 2.0 port? If you ever need to, hard reset is holding all buttons at once for 30 seconds.
Click to expand...
Click to collapse
i tried 2.0 and 3.0
not work
tablet owner decide to use it on stock chinese rom
not in my hand now
$ adb reboot bootloader
List devices on fastboot :
$ fastboot devices
XXXXXX fastboot
Check if bootloader is unlocked :
$ fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
OKAY [ 0.001s]
Finished. Total time: 0.003s
Flash TWRP recovery :
$ fastboot flash recovery recovery.img
Sending 'recovery' (54400 KB) OKAY [ 1.540s]
Writing 'recovery' OKAY [ 0.410s]
Finished. Total time: 1.952s
Reboot your device
$ fastboot reboot
Rebooting
Finished. Total time: 0.000s
I installed TWRP on MIUI 10 using this description. On the end , after TWRP installed - I rebooted again to TWRP and installed stock rom at once . I not tested , but theory says , MIUI will reflash recovery if it will be booted in this situation .
Sorry to piggy-back off this post, but I'm having a similar issue with my Mi Pad I just received:
I can boot it into Fastboot mode no problem, even see it listed when I use the "Fastboot devices" command. When I run the OEM info everything comes back true for unlocked.
However, when I try to flash anything I get the max size error or just a "FAILED" and it kicks the Mi Pad to a black screen with the white text "Press any key to shut down".
Any ideas?
*edit*
I've continued testing, and I'm really at a loss here. See the response I'm getting using fastboot:
\minimal_adb_fastboot_1.4.3_portable>fastboot flash boot kernel.img
target didn't report max-download-size
sending 'boot' (15060 KB)...
FAILED (command write failed (No error))
finished. total time: 0.003s
I can transfer files in windows no problem... I can use adb commands no problem... fastboot just doesnt seem to work.
I figured out my issue. You cannot use USB 3 ports to connect and run fastboot commands. I bought a cheap USB 2 hub, ran the cable from that and had no problems at all.
I have been trying for the past few days to try to recover my CMR-W09(C00) device with no luck.
What it looks like now?
At the moment there is nothing showing on the screen regardless of what button combinations I've tried (Vol Up+Vol Down+Pwr/Vol Up + Pwr/Vol Down + Pwr, and each with USB power cable plugged in and without). The phone is able to get into fastboot mode (detected by running fastboot devices) automatically, fastboot reboot would get it to fastboot again (i.e., doesn't go to any other mode). The screen is completely dark with nothing at all.
From fastboot I can even see the current firmware version is 195. (CMR-W09C00B195 (8.0.0.195))
What did I do?
Flashed the 160 (CMR-W09C00E160R1P160B160 (9.0.1.160)) firmware which I found on firmware finder, and used EMUI Flasher to flash the firmware. (Found here: https://forum.xda-developers.com/mate-20-pro/how-to/guide-manual-updating-firmware-t3893171) Flash seems to have worked and at 100% it said something along the line of checksum failed, rebooted, and never came back to life again.
What I have tried?
1. No eRecovery (that would be easy)
2. Use HiSuite to repair devices, received unsupported device error.
3. Flashed recovery-ramdis, recovery-vbmeta and recovery-vendor and ramdisk that were extracted from 195 OTA (http://update.hicloud.com:8180/TDS/data/files/p3/s15/G3776/g1699/v225819/f1/full/update.zip) and 160 OTA(http://update.hicloud.com:8180/TDS/data/files/p3/s15/G3776/g1699/v234512/f1/full/update.zip). Nothing happened. In Fastboot I can flash these three partitions and system, anything else would return command not allowed.
4. Tried DC Unlocker, when flashing xloader I got command not allowed error, in the end DC Unlocker refunded me.
5. Tried dload method with UPDATE.APP in dload folder only as well as the entire contents (META-INF/tags files and mbn files together with UPDATE.APP) in dload file, reboot using three button combo
6. In desperation I even tried to buy some "factory flash" image which was supposedly to be used by Huawei repair centres internally (with two zip files) to extract to dload folder. Again didn't do anything.
7. Tried to contacted FH to see if they support unbricking this and didn't hear a response.
8. Went to local Huawei authorized repair centre and they don't seem to have seen this device. They told me they can only fix devices bought locally.
9. Tried to flash in TWRP by flash the recovery_ramdisk partition.
All of above leads to nothing (i.e., it goes back to the blank screen with fastboot, however I can hear the USB connected and disconnected sound and HiSuite popped up again which tells me the reboot actually took place).
Some output from fastboot command:
E:\Android\M5>fastboot devices
HYY6R189********** fastboot
E:\Android\M5>fastboot oem get-product-model
...
(bootloader) CMR-W09
OKAY [ 0.013s]
finished. total time: 0.013s
E:\Android\M5>fastboot getvar vendorcountry
vendorcountry: all/cn
finished. total time: 0.013s
E:\Android\M5>fastboot oem get-build-number
...
(bootloader) :CMR-W09 8.0.0.195(C00)
OKAY [ 0.014s]
finished. total time: 0.015s
E:\Android\M5>fastboot getvar rescue_enter_recovery
getvar:rescue_enter_recovery FAILED (remote: FAIL:need all image flashed!)
finished. total time: 0.027s
E:\Android\M5>fastboot oem oeminforead-SYSTEM_VERSION
...
(bootloader) :CMR-W09 8.0.0.195(C00)
OKAY [ 0.015s]
finished. total time: 0.016s
Click to expand...
Click to collapse
I think I am pretty much out of options right now, but if there is anything
Just wondering if there is anything else I haven't tried that I should?
I think "command not allowed" indicates that your bootloader is locked. If I am right about that, you will need to unlock your bootloader again before you flash anything via fastboot.
Download ONLY the Chinese hisuite, it support CMR-W09C00 as i have already checked
consumer.huawei.com/cn/support/hisuite/
Then reconnect the device with your pc, go to system recovery and follow the instructions
The global hisuite support only few devices
Plz report back to me if it worked
This happened to me once in my CMR-W09C432 i stucked in fastboot mode ( black screen) while i was trying to install the emui 9 beta, but i sent it to huawei service centre, they replaced the whole motherboard and i had to unlock the bootloader again.
But first of all do what i wrote above (the chinese hisuite)
Regards
thref23 said:
I think "command not allowed" indicates that your bootloader is locked. If I am right about that, you will need to unlock your bootloader again before you flash anything via fastboot.
Click to expand...
Click to collapse
Thanks for your input, I am able to write to recovery_ramdisk, recovery_vbmeta and recovery_vendor, as well as system partitions, however XLOADER and ERECOVERY* and FASTBOOT partitions seems to be out of touch.
Here are some more output from fastboot:
fastboot oem check-rootinfo
...
(bootloader) status : RISK
(bootloader) version : v1.1
(bootloader) current status: SAFE
(bootloader) old status : SAFE
(bootloader) change_time : 0
(bootloader) item: root-prop, status: SAFE, credible: Y
(bootloader) item: setids, status: SAFE, credible: Y
(bootloader) item: verifyboot, status: SAFE, credible: N
(bootloader) item: verity-enable, status: SAFE, credible: Y
(bootloader) item: fblock, status: locked, credible: Y
(bootloader) item: userlock, status: unlocked, credible: Y
OKAY [ 0.031s]
finished. total time: 0.032s
fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.008s]
finished. total time: 0.009s
Click to expand...
Click to collapse
Are there multiple lock? What is the fblock? Would unlock that allow me to write to the XLOADER partition?
THE MAXIMUM POWER said:
Download ONLY the Chinese hisuite, it support CMR-W09C00 as i have already checked
consumer.huawei.com/cn/support/hisuite/
Then reconnect the device with your pc, go to system recovery and follow the instructions
The global hisuite support only few devices
Plz report back to me if it worked
This happened to me once in my CMR-W09C432 i stucked in fastboot mode ( black screen) while i was trying to install the emui 9 beta, but i sent it to huawei service centre, they replaced the whole motherboard and i had to unlock the bootloader again.
But first of all do what i wrote above (the chinese hisuite)
Regards
Click to expand...
Click to collapse
Thanks for your response, I've tried that and unfortunately it failed at 99% at the step Writing Recovery. (Simply said failed to repair with no other error).
zhuanyi said:
Thanks for your response, I've tried that and unfortunately it failed at 99% at the step Writing Recovery. (Simply said failed to repair with no other error).
Click to expand...
Click to collapse
Im sorry about that, try to send it to china huawei service as they might repair it their for free because yours is C00