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.
Related
So my Bootloader is currently locked and I can't boot into recovery, it just shows the OnePlus Logo when I try to boot into it.
So currently, I have ParanoidAndroid w/root, can boot into it, can get to FastBoot, can't get into recovery, Bootloader locked, can't unlock it because the Bootloader Unlock option isn't present in this ROM, since it's not the stock ROM,
How It happened
I had the MultiROM Recovery installed, with the Stock ROM installed as the main ROM. I guess through experimenting with it the Bootloader got relocked somehow.
I eventually installed Paranoid Android, and wanted to switch back to regular TWRP, so I flashed it from recovery, that's when I lost access to it, so I booted into PA, used the TWRP app to flash the recovery, still nothing. finally tired to flash with FastBoot, that's when I found out the Bootloader was locked again.
Did "fastboot oem device-info" got this
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
I tried this Unbrick Guide, didn't work, here's the comment I made over there
Not too sure what to do at this point,
https://forum.xda-developers.com/nexus-5x/help/tp-link-android-phone-adb-device-t3440471 maybe inbox the OP of this thread and see if he found a solution
I figured it out, in the end it's the Mega unbrick guide, but with a step I didn't see mentioned anywhere.
if you can't get your phone to show up as QHUSB_BULK:
Turn off your phone.
Hold Volume Up and plug your phone into you computer,
this will force the phone to show up as QHUSB_BULK.
Then you can use the driver provided in that guide and follow the rest of the steps as stated.
Thanks to this guide I found, https://www.gizmochina.com/2016/07/30/oneplus-series-mega-unbrick-guide-twrp-flashing/
Hi all,
I messed up my onyx pretty good this time. It gets stuck after oneplus powered by android logo, if it is connected to my computer i see about 7 partitions come and go. I can enter fastboot, original oneplus recovery.
In fastboot everything is locked,
[email protected]:/home/ivo# fastboot oem unlock
...
FAILED (remote: oem unlock is disabled)
finished. total time: 0.005s
[email protected]:/home/ivo# fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.006s]
finished. total time: 0.006s
So fastboot isn't working for me.
I tried enter the original recovery, adb sideload original OOS, it says all ok nothing failed, once i reboot nothing changed.
In original recovery my touchscreen isn't responding to touches, with volume up an down and powerbutton i can control it. I wiped everything multiple times.
I tried https://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
With this method i locked my device, and still it doesn't change anything.
What else could i try?
thanks for your help
vanderveen.ivo said:
Hi all,
I messed up my onyx pretty good this time. It gets stuck after oneplus powered by android logo, if it is connected to my computer i see about 7 partitions come and go. I can enter fastboot, original oneplus recovery.
In fastboot everything is locked,
[email protected]:/home/ivo# fastboot oem unlock
...
FAILED (remote: oem unlock is disabled)
finished. total time: 0.005s
[email protected]:/home/ivo# fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.006s]
finished. total time: 0.006s
So fastboot isn't working for me.
I tried enter the original recovery, adb sideload original OOS, it says all ok nothing failed, once i reboot nothing changed.
In original recovery my touchscreen isn't responding to touches, with volume up an down and powerbutton i can control it. I wiped everything multiple times.
I tried https://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
With this method i locked my device, and still it doesn't change anything.
What else could i try?
thanks for your help
Click to expand...
Click to collapse
Does this work:
1. Boot into oxygen recovery.
2. Wipe data and cache.
3. Wipe data and cahce again.
4. Then sideload the latest version of OxygenOS.
5. Then boot.
aryan.arora180 said:
Does this work:
1. Boot into oxygen recovery.
2. Wipe data and cache.
3. Wipe data and cahce again.
4. Then sideload the latest version of OxygenOS.
5. Then boot.
Click to expand...
Click to collapse
I tried it, but noticed my terminal says:
serving: 'OnePlusXOxygen_14_OTA_019_all_201611071506_03f73e21449d4d31.zip' (~94Total xfer: 2.00x
It looks like it stops at 94% and then stopped, while my onyx says download succes.
but is still not booting
vanderveen.ivo said:
I tried it, but noticed my terminal says:
serving: 'OnePlusXOxygen_14_OTA_019_all_201611071506_03f73e21449d4d31.zip' (~94Total xfer: 2.00x
It looks like it stops at 94% and then stopped, while my onyx says download succes.
but is still not booting
Click to expand...
Click to collapse
Use this OOS zip file instead: http://downloads.oneplus.net/oneplus-x/oneplus_x_oxygenos_2.2.3/
The one you're downloading is for OOS 3 which has to use the new bootloader and since the mega unbrick guide will put you on the old bootloader I would try the old OOS first. If it boots immediately open the developer settings and tick off OEM unlock.
---------- Post added at 01:34 AM ---------- Previous post was at 01:27 AM ----------
Also I'll say when mine became locked with a custom rom installed I just had to keep following the guide over and over until it finally worked. A lot of it was just trying to get the device to be recognized and having to download files from other sites.
vanderveen.ivo said:
I tried it, but noticed my terminal says:
serving: 'OnePlusXOxygen_14_OTA_019_all_201611071506_03f73e21449d4d31.zip' (~94Total xfer: 2.00x
It looks like it stops at 94% and then stopped, while my onyx says download succes.
but is still not booting
Click to expand...
Click to collapse
When u say booting, do you mean that it gets stuck at the OnePlus logo along with Powered by Android or do you mean it passes that and shows the bootscreen animation and is stuck there?
---------- Post added at 11:19 AM ---------- Previous post was at 11:17 AM ----------
Tanner1294 said:
Use this OOS zip file instead: http://downloads.oneplus.net/oneplus-x/oneplus_x_oxygenos_2.2.3/
The one you're downloading is for OOS 3 which has to use the new bootloader and since the mega unbrick guide will put you on the old bootloader I would try the old OOS first. If it boots immediately open the developer settings and tick off OEM unlock.
Click to expand...
Click to collapse
If you flash the newer OxygenOS, it will automatically install the newer bootloader so old/new bootloader will not make a difference.
aryan.arora180 said:
When u say booting, do you mean that it gets stuck at the OnePlus logo along with Powered by Android or do you mean it passes that and shows the bootscreen animation and is stuck there?
---------- Post added at 11:19 AM ---------- Previous post was at 11:17 AM ----------
If you flash the newer OxygenOS, it will automatically install the newer bootloader so old/new bootloader will not make a difference.
Click to expand...
Click to collapse
Well, i tried oos 2, it changed my boot behavior. I now tries to boot, gets stuck at OnePlus logo along with Powered by Android and then it disapeers and it tries again. It is new that she wants to try again. And the partitions are not visible anymore. Before oos3 it showed about 7 partitions.
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)
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
FIXED!!!: Solution: Download MiFlash and flash a stable Rom, then install twrp and flash your prefered rom.
LINKS in Comments
Hello,
So basically I'm stuck in FastBoot.
I wanted to install the Pixel Experience ROM and did a big mistake, I wiped Dalvik, Cache, System and Data, then installed the ROM but no system, I rebooted and since then I am stuck in Bootloader.
My phone didn't turn on at first and I thought I broke it, but then it turned on into FastBoot.
Now it is stuck there.
I tried everything I found on the internet, I even went to the XDA Discord Server for help but nothing worked.
I have the Xiaomi Mi 9, I had the GlobeROM installed.
I don't care about the data, I just want my phone to work again.
I tried:
adb:
- Does not find my device because it is in FastBoot
fastboot:
-fastboot flash recovery (then my twrp, yes I tried three different versions and they worked before on my Mi 9)
-fastboot boot (image) --> FAILED (remote: Failed to load/authenticate boot image: Load Error)
I tried rebooting into recovery, no success.
I tried installing twrp with cmd and powershell both without success.
I tried rebooting with power and vol up, no success.
The twrp installs successfully, but I can't boot into it.
my fasboot oem device-info:
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.009s]
finished. total time: 0.010s
I tried to flash a stock (for Android Pie) that I downloaded, but my phone turns off during the process and boots again into FastBoot causing the cmd to close everytime.
Please help me, I feel like my phone is broken now.
Feel free to ask any question, I will answer quick as long as I'm not sleeping, because I will refresh this page every 10 seconds I guess.