Hello there!
Long story short:
I'm was successfully running on twrp-3.0.2-0-onyx-20161020-085152.img and cm-13 on my beloved OPX for serveral months now. Got it running, following this guides:
http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
https://wiki.cyanogenmod.org/w/Install_CM_for_onyx
Also, happily updating the nightly builds since then.
But last update went wrong. I OTA updated my device on the go, not paying to much attention that the update will be cm13->cm14. After TWRP installed the update i got stuck on reboot with the OnePlus logo.
I restarted the phone (Powerbutton off/on), 'cause my guts told me that something went wrong. I hoped to reboot to recovery an rollback the update to previous CM version.
But, it won't boot.
This is what happens:
Powerbutton down (Trun on): -> Vibrates -> flashes OP Logo + powerd by Android -> Vibrates -> flashes OP Logo + powerd by Android ->...
I can reach fastboot mode by VolumeUp (w/o pressing powerbutton) but i cannot reach TWRP recovery.
So normally i could totally live with fastboot, flashing reflashing unlocking etc. BUT here my first WTF experience took place:
I can not
Code:
fastboot oem unlock
because oem unlock is locked! I know how to unlock it via DevMode -> unlock oem unlock yadda yadda (who had this "great" idea anyway?!). But since i cannot boot the OS, i cannot enter devmode....
So before going through all the (Mega)unbrick guides, I'm curious:
Is there some way around this dilemma?
What we've got: No OS, no recovery, only fastboot
Code:
$: fastboot devices
...
25bf1e07 fastboot
$ 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
$: fastboot oem unlock
...
FAILED (remote: oem unlock is disabled)
finished. total time: 0.003s
$: fastboot format userdata
Creating filesystem with parameters:
Size: 12611891200
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3079075
Block groups: 94
Reserved block group size: 751
Created filesystem with 11/770048 inodes and 88617/3079075 blocks
target reported max download size of 536870912 bytes
erasing 'userdata'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.000s
Code:
fastboot continue
ends up in same loop.
I cannot adb.
Device is encrypted.
I've no problem to completely wipe or factory reset or stock reset my device, hence i love tinkering with it and have backups of important data.
I sincerely ask for some pointers, links, opinions on how to go on from here? Is there a chance to get my phone back running? Should I stop searching and just follow the unbrick guides?
Are there unbrick guides for Linux users? (Just nice to have! )
Is there some exploit, backdoor, trick, magic to circumvent a disabled 'oem unlock'? (again: who had this 'great' idea anyways? )
Unbrick guide(s):
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-x.417648/
Thank you very much in advance! Have your (virtual) coffee on me!
sem
Hi,
I do have the very same issue.
I can enter fastboot but that's about it. Would be curious to get it running again without the "mega unbrick" stuff...
I found a way to get back.
After i have flashed to CM 14.1 Nightly update it was stuck at the oneplus logo, and i felt the same that something went wrong had no other choice just rebooted the phone and then it started acting wired (Phone vibrates and it shows oneplus logo for every second) and not able to access TWRP. Only i can access is Fast boot but here is the twist the oem was locked and we cannot unlock it any way.
Spent lot of time (2hrs+) searching for the solution and finally found it :angel:
Check this Link
forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-x.417648/
It took me around 4hrs to get back to my Custom Rom
Cheers
i'm suffering the same problem now...today morning tried to update the cm nightly 14 and soft bricked my oneplus X
is the mega unbrick guide really working..? for me device is not recognized when i connect the phone to the pc pressing v up key for 10 secs..
prasannazx said:
i'm suffering the same problem now...today morning tried to update the cm nightly 14 and soft bricked my oneplus X
is the mega unbrick guide really working..? for me device is not recognized when i connect the phone to the pc pressing v up key for 10 secs..
Click to expand...
Click to collapse
Which driver you are using and which windows version 64bit or 32bit?
prasannazx said:
i'm suffering the same problem now...today morning tried to update the cm nightly 14 and soft bricked my oneplus X
is the mega unbrick guide really working..? for me device is not recognized when i connect the phone to the pc pressing v up key for 10 secs..
Click to expand...
Click to collapse
Just flash Arsenic Kernel for Android N. Cyanogen 14 has kernel problem. Flashing custom kernel will fix your bugged boot
Caraparbor said:
Just flash Arsenic Kernel for Android N. Cyanogen 14 has kernel problem. Flashing custom kernel will fix your bugged boot
Click to expand...
Click to collapse
Thnx man!! It helped me not to waste my time doing this mega unbrick process...
Caraparbor said:
Just flash Arsenic Kernel for Android N. Cyanogen 14 has kernel problem. Flashing custom kernel will fix your bugged boot
Click to expand...
Click to collapse
Thank you...? ?
does the clock app and settings for gboard work ????
does the clock app and settings for gboard work ????
Caraparbor said:
Just flash Arsenic Kernel for Android N. Cyanogen 14 has kernel problem. Flashing custom kernel will fix your bugged boot
Click to expand...
Click to collapse
But is flashing a kernel possible w/o oem unlock?
prasannazx said:
i'm suffering the same problem now...today morning tried to update the cm nightly 14 and soft bricked my oneplus X
is the mega unbrick guide really working..? for me device is not recognized when i connect the phone to the pc pressing v up key for 10 secs..
Click to expand...
Click to collapse
Press VolUp until you see something in Devicemanager! It took more than 10s for me too until it showed up in Devicemanager.
Or if you have a Linux at hand, look at dmesg. You should see something like this:
Code:
[ +0,004635] usbcore: registered new interface driver qcserial
[ +0,000049] usbserial: USB Serial support registered for Qualcomm USB modem
[ +0,000103] qcserial 1-4:1.0: Qualcomm USB modem converter detected
[ +0,000325] usb 1-4: Qualcomm USB modem converter now attached to ttyUSB0
[Dec24 02:39] usb 1-4: USB disconnect, device number 6
[ +0,000343] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
Ashok6086 said:
After i have flashed to CM 14.1 Nightly update it was stuck at the oneplus logo, and i felt the same that something went wrong had no other choice just rebooted the phone and then it started acting wired (Phone vibrates and it shows oneplus logo for every second) and not able to access TWRP. Only i can access is Fast boot but here is the twist the oem was locked and we cannot unlock it any way.
Spent lot of time (2hrs+) searching for the solution and finally found it :angel:
Check this Link
forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-x.417648/
It took me around 4hrs to get back to my Custom Rom
Cheers
Click to expand...
Click to collapse
I was stuck on OnePlus logo too, but I solved the situation pushing a different recovery throgh fastboot commands, then I've installed a different ROM. It took me only 5 minutes!
When you restart your bricked device (pressing for 12 seconds the power btn) keep pressed the Volume UP BTn to enter the Fastboot Mode, the follow the procedure to flash a different recovery.
I'm using BlueSpark TWRP Recovery. As ROM, for now, I'm using XperienceRom with Android 7.1 and no bug found.
I tried that too, but no use. it says OEM Locked and we cannot unlock the phone that means we cannot load anything.
Ashok6086 said:
I tried that too, but no use. it says OEM Locked and we cannot unlock the phone that means we cannot load anything.
Click to expand...
Click to collapse
Use megha unbrick guide
http://forum.xda-developers.com/one...ga-unbrick-guide-hard-bricked-t3272108/page20
I had the same problem. Solved it by first flashing latest cm and right after that I flash arsenic kernel and then reboot. I had to do that every time I flash a new nightly build but it works. Hope it helps
Hello.
I've had the exact same problem as semph0re.
Did the Mega Unbrick Guide thing, somehow I got a "Sahara communication failed" during the process, but it still managed to flash the stock recovery (and the old bootloader i guess).
From there I'm able to install and successfully boot OOS 2.3 (or older), old versions of CM13.0 (those based on the old bootloader), and TWRP-3.0.2-0 recovery and therefore unlock the bootloader.
So basically anything compatible with the old bootloader.
And trying to install anything based on the new bootloader, either a stock rom, the OPX_MM_recovery from Oneplus, any custom rom, with or without custom kernel or a custom recovery leave me with a fixed Oneplus logo (and the powered by android disappearing almost immediately)
But I can't manage to update the bootloader.
Either by trying to install OOS3.1.x from OOS 2.x
Nor by following matwaking guidehttps://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Does anyone have face the same issue ? Any idea what could the cause of the problem ?
The only thing I could think of but didn't try is to go through the Mega Unbrick guide again. But I'm on Ubuntu and do not have a Windows machine anywhere near me at the moment.
@GARGZUL you have to use stock recovery from 2.X.X not mm stock.
Exodusche said:
@GARGZUL you have to use stock recovery from 2.X.X not mm stock.
Click to expand...
Click to collapse
@Exodusche
That's what I tried many times.
Trying to install OOS3.x from OOS2.x with either (old)stock recovery or TWRP-3.0.2-0 leave me with a beautiful stuck Oneplus logo when booting system.
And those are the only recovery I can boot on. Any more recent recovery won't boot (fixed Oneplus logo again or 'dtb not found' error when boot from fastboot command) since they require the new BL.
It's like when trying to install OOS3.x or flashing matwaking's BLUpdater.zip the old bootloader is not deleted, effectively preventing any new BL based rom or recovery to boot.
@GARGZUL Use latest twrp and you want to use 2.2.3 before flashing 3.X.X .
Exodusche said:
@GARGZUL your using the wrong twrp use 3.0.3
Click to expand...
Click to collapse
@Exodusche
I would if I could. But when flashing TWRP 3.0.3-0 (either with flashboot or via TWRP 3.0.2-0) my phone won't boot to recovery (Vol down+poweer gives me a stuck oneplus logo, and 'fastboot boot twrp-3.0.3-0-onyx.img' gives me a "dtb not found" error).
Any other idea ?
Related
Hi
I used my Xiaomi Redmi Note 3, 3GB RAM, 32GB new phone first day yesterday.
When I went to sleep it was 92% charged and when I woke up it was stuck on the Xiaomi loading screen. I let it on that screen for about 3 hours before I restarted it.
It's unable to boot into normal mode, and when I try to get into recovery mode it just shows a screen to connect a cable.
When I connect the cable to the computer it shows that the cable is connected but nothing happens after this.
If I boot the phone in fastboot and use Mi PC Suite to try to flash it, it just tells me to reboot in normal mode and try again.
If I hold all 3 buttons I have managed to get into some test mode, but from there I can't do anything.
How can I reset or get into my phone again? Is this normal behaviour after just one day use?
Johanna12221 said:
Hi
I used my Xiaomi Redmi Note 3, 3GB RAM, 32GB new phone first day yesterday.
When I went to sleep it was 92% charged and when I woke up it was stuck on the Xiaomi loading screen. I let it on that screen for about 3 hours before I restarted it.
It's unable to boot into normal mode, and when I try to get into recovery mode it just shows a screen to connect a cable.
When I connect the cable to the computer it shows that the cable is connected but nothing happens after this.
If I boot the phone in fastboot and use Mi PC Suite to try to flash it, it just tells me to reboot in normal mode and try again.
If I hold all 3 buttons I have managed to get into some test mode, but from there I can't do anything.
How can I reset or get into my phone again? Is this normal behaviour after just one day use?
Click to expand...
Click to collapse
Flash aboot it will ok..
Hi and thanks for your reply!
By running fastboot getvar product I found out that I have the "special edition" model, kate.
I have now downloaded this:
kate_global_images_6.9.8_20160805.0000.29_6.0_global_042c784ac4
After unpacking and trying to flash I get this:
Code:
fastboot flash tz C:\kate\kate\images\tz.mbn
target reported max download size of 536870912 bytes
sending 'tz' (637 KB)...
OKAY [ 0.023s]
writing 'tz'...
FAILED [B](remote: Critical partition flashing is not allowed)[/B]
finished. total time: 0.032s
"Flash tz error"
Johanna12221 said:
Hi and thanks for your reply!
By running fastboot getvar product I found out that I have the "special edition" model, kate.
I have now downloaded this:
kate_global_images_6.9.8_20160805.0000.29_6.0_global_042c784ac4
After unpacking and trying to flash I get this:
Code:
fastboot flash tz C:\kate\kate\images\tz.mbn
target reported max download size of 536870912 bytes
sending 'tz' (637 KB)...
OKAY [ 0.023s]
writing 'tz'...
FAILED [B](remote: Critical partition flashing is not allowed)[/B]
finished. total time: 0.032s
"Flash tz error"
Click to expand...
Click to collapse
By looks of it, you have a locked bootloader and hence, are unable to flash fastboot files. The only way for you to make your device usable again is to somehow boot into the 'edl' mode and use MiFlash to falsh the fastboot ROM from there.
Hi! Thanks for your reply.
I didn't do anything to the bootloader, so yeah it should be locked.
I will contact the store I bought it from and try to get it returned.
So sad to have made this purchase. I hope I can find another phone, perhaps one that is not as cheap as this.
Hi again!
I have kept trying to solve this issue further. I'm able to get into edl mode using the modified fastboot that I found here on the forums with "fastboot reboot-edl".
I managed to run MiFlash 2016.04.01 (important, newer version didn't work!)
But it still seems to be stuck in just an endless Android loading screen. Anything else I can try?
Johanna12221 said:
Hi again!
I have kept trying to solve this issue further. I'm able to get into edl mode using the modified fastboot that I found here on the forums with "fastboot reboot-edl".
I managed to run MiFlash 2016.04.01 (important, newer version didn't work!)
But it still seems to be stuck in just an endless Android loading screen. Anything else I can try?
Click to expand...
Click to collapse
I can help you. Talk me in PM.
Hi!
Thanks for offering your help, andersonaragao.
I finally got it to work by doing a "Flash all" of the MIUI 8 package.
So the steps so solve was just this easy:
Boot in fastboot (Volume down + power)
Make sure you have kenzo or kate (fastboot getvar product)
Get correct fastboot rom, depending on kenzo/kate: (http://en.miui.com/a-234.html)
Boot in edl (Fastboot_edl-v2: fastboot reboot-edl)
MiFlash 2016.04.01 (Flash all)
Hi,
I'm new here, so please excuse me if I am posting in the wrong category.
So I tried to root my Doogee F7 (not the pro version) using fastboot and TWRP, and it resulted in a sort of bootloop where it says:
Code:
Orange State
Your device has been unlocked and can't be trusted
Your device will boot in 5 seconds
And then it restarts and gives the same message again. This loop has been going on for some time and I can't stop it because the phone has a non-removable battery and I have tried every possible combination of buttons (i.e. Power + Volume Down + Volume Up).
The process I used in my attempt to root was as following:
1. I used
Code:
adb reboot bootloader
to go into fastboot. (I already set up everything like USB debugging and OEM unlocking in the developer options)
2. I then used
Code:
fastboot oem unlock
and pressed Volume Up to unlock the bootloader. All was successful.
3. I then tried to flash TWRP to recovery and I believe this is where everything went wrong. I flashed it using
Code:
fastboot flash recovery recovery.img
and it was successful, according to the command prompt:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery "C:\Users\momen\Downloads\recovery (1).img"
target reported max download size of 134217728 bytes
sending 'recovery' (12832 KB)...
OKAY [ 0.562s]
writing 'recovery'...
OKAY [ 0.213s]
finished. total time: 0.779s
4. After it finished I used
Code:
fastboot reboot
to reboot the phone and that's when it got stuck.
At the moment I am just letting my battery run out, as I have no other way of turning off the phone, and neither adb nor fastboot is working.
I don't really know if my device was even supported, but I followed the instructions on various websites stating that I should first unlock my bootloader, then flash TWRP, then flash superSU onto it, and my phone would be rooted. I used the latest TWRP image, and I think that was where I went wrong. Is there anything I can do to get my phone to work again?
Hey! i´m sorry for your phone, can you tell me any updates, is it fixed now? what happened? i am about to do the same process to root my Doogee F7 and i´m very worried that my phone gets bricked, so please, i need your recommendations.
I hope everything is alright with your phone.
solartediego said:
Hey! i´m sorry for your phone, can you tell me any updates, is it fixed now? what happened? i am about to do the same process to root my Doogee F7 and i´m very worried that my phone gets bricked, so please, i need your recommendations.
I hope everything is alright with your phone.
Click to expand...
Click to collapse
Ah yes, sorry for not updating. I managed to connect my phone to my PC again using the flash tool and then I could flash the original ROM back onto it. I found the ROM by Googling for a bit tho I dont have a link. Be aware that if you do this, it basically factory resets your phone, locking your bootloader again and all. If you do manage to root your phone please contact me as I still have not managed to do so.
Edit: This process of flashing back your ROM always works as long as your phone powers on, so don't worry too much about bricking your phone. I think I've bricked my phone over 20 times trying to root it, and it worked every single time.
Hello there. I suggest that you use "fastboot boot recovery.img" than using "fastboot flash" if you are not sure if the custom recovery works (or if you just want to test/try it). In this way, you'll just boot the custom recovery temporarily (and your stock recovery is still in tacked).
For rooting your device, first you'll need a working custom recovery for your device (you used TWRP, very first if it works or compatible with your device).
Insyder28 said:
Ah yes, sorry for not updating. I managed to connect my phone to my PC again using the flash tool and then I could flash the original ROM back onto it. I found the ROM by Googling for a bit tho I dont have a link. Be aware that if you do this, it basically factory resets your phone, locking your bootloader again and all. If you do manage to root your phone please contact me as I still have not managed to do so.
Edit: This process of flashing back your ROM always works as long as your phone powers on, so don't worry too much about bricking your phone. I think I've bricked my phone over 20 times trying to root it, and it worked every single time.
Click to expand...
Click to collapse
Hi.How you actually managed to connect your phone to PC using flash tool if you were in a bootloop and had no access to fastboot mode or recovery?
ciubsy2004 said:
Hi.How you actually managed to connect your phone to PC using flash tool if you were in a bootloop and had no access to fastboot mode or recovery?
Click to expand...
Click to collapse
Im interested too in your process to flash TWRP again, as i am in the same boot loop than you with a Doogee S60. I´ve waited till the battery ended, but now flash tool doesn´t recognize my phone. If i charge the battery, i get a boot loop again..
TheBidan said:
Im interested too in your process to flash TWRP again, as i am in the same boot loop than you with a Doogee S60. I´ve waited till the battery ended, but now flash tool doesn´t recognize my phone. If i charge the battery, i get a boot loop again..
Click to expand...
Click to collapse
I have managed to get the flash tool recognizing my phone.Had to keep pressed volume up,if i recall properly(or try volume down) before connecting usb cable to phone with flash tool opened and . It was a while ago though and i can't remember exactly which key was for sure. Hope this helps
When i was updating the twrp i managed to hard brick my phone, it just shows the 1+ logo and "powered by android" when turned on. if i hold the power button and volume up it shows the cyanogenmod logo and "fastboot mod" and stays there. If i hold power button and volume down it just shows the 1+ logo without the "powered by android".
i followed this guide https://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
completed all the steps but the installed program cant recognise my phone when i plug it in.
When its in fastboot mode logo i can see it in device manager under portable devices listed as "ONE E1001" (it has a yellow ! triangle next to it)
When i try to turn the recovery (powerbutton+volume down) where it shows just the 1+ logo with no "powered by android" i can see it in the device manager under android phone as "Android Bootloader Interface"
When i just turn it on where it does display "powered by android" i can see it same as in fastboot mode, as "ONE E1001" under portable devices, (a yellow ! triangle appears after some time too)
i tried a similar guide here: https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
did everything, i have like 5 driver now from all the guides, i think all of them work, i just cant manage to get the programs to realize when the phone is pluged in. Is it possible that something is still wrong with the drivers?
pls help );
PlsHelpMeee said:
When i was updating the twrp i managed to hard brick my phone, it just shows the 1+ logo and "powered by android" when turned on. if i hold the power button and volume up it shows the cyanogenmod logo and "fastboot mod" and stays there. If i hold power button and volume down it just shows the 1+ logo without the "powered by android".
i followed this guide https://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
Click to expand...
Click to collapse
You're talking about Cyanogenmod logo. What was on your phone before? What did you do exactly?
Are you sure you know how to use Fastboot?
"fastboot oem device-info" output?
And then explain precisely at what step you have error.
Kéno40 said:
You're talking about Cyanogenmod logo. What was on your phone before? What did you do exactly?
Are you sure you know how to use Fastboot?
"fastboot oem device-info" output?
And then explain precisely at what step you have error.
Click to expand...
Click to collapse
i had CM12 before i tried to upgrade, i managed to go through the entire first guide now, the CM logo isn't appearing anymore, now its the 1+ logo and below it "fastboot mode" the drivers were a problem after all
now im stuck at the new recovery that is installed and cant install the ROM from it, even my old one that i had before all of this (CM12) that i have on my sd card.
OK, so you flash something incompatible.
After CM13 or so, the bootloader have to be upgraded and then you have to use a version compatible with it.
First look with fastboot command I give if BL still unlocked.
Do you know how to use fastboot commands?
Kéno40 said:
OK, so you flash something incompatible.
After CM13 or so, the bootloader have to be upgraded and then you have to use a version compatible with it.
First look with fastboot command I give if BL still unlocked.
Do you know how to use fastboot commands?
Click to expand...
Click to collapse
kind of, "fastboot oem device-info" output is
(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.010s]
finished. total time: 0.011s
if i could install the twrp from here i could install the ROM too i think, is there a guide to do so while stuck like this?
"fastboot oem unlock" gives me
FAILED (remote: oem unlock is disabled)
finished. total time: 0.009s
i cant use adb commands, in the command prompt my computer doesent even see the device when i type "adb devices", i think its because oem, debuging, isnt turned on but i cant turn it on if i cant install a ROM and check it "on" in the settings of the androis OS.
all i can use are fastboot comands since my computer can see it as a fastboot device while not as a adb device. i have a bricked phone with a locked bootloader i think.
BL is locked so only solution is mega unbrick guide.
I never tried but oos 3.1.4 won't flash either...
Kéno40 said:
BL is locked so only solution is mega unbrick guide.
I never tried but oos 3.1.4 won't flash either...
Click to expand...
Click to collapse
i did the mega unbricked guide, this one ==> https://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
i have the recovery dom the guide installed but it cant install any ROMs or the twrp, im trying to install them over fastboot but it also cant be done because my device is locked and i cant flash anything remotely. I also cant use adb for some reason because the command prompt cant see my phone under "adb devices". is there anything i can install with that recovery? i just stuck, spent so much time and still nothing :crying:
i think adb devices dont show because usb debugging is not turned on, i dont know how it can be turned on without and actual operating system on the phone..
THis guide push you back with OnePlus recovery and OOS.
That's not what you have?
You did something wrong...
At which step does it stop?
A few day ago, one of the file ws missing. Do you have it all?
---------- Post added at 10:43 PM ---------- Previous post was at 10:43 PM ----------
THis guide push you back with OnePlus recovery and OOS.
That's not what you have?
You did something wrong...
At which step does it stop?
A few day ago, one of the file ws missing. Do you have it all?
Kéno40 said:
THis guide push you back with OnePlus recovery and OOS.
That's not what you have?
You did something wrong...
At which step does it stop?
A few day ago, one of the file ws missing. Do you have it all?
---------- Post added at 10:43 PM ---------- Previous post was at 10:43 PM ----------
THis guide push you back with OnePlus recovery and OOS.
That's not what you have?
You did something wrong...
At which step does it stop?
A few day ago, one of the file ws missing. Do you have it all?
Click to expand...
Click to collapse
i did all the steps, all of them work, when the program finished downloading/instaling things on my phone it turned on my phone and it was tuck at the 1+ logo again. when i held the power button+volume down it went to the custom recovery that was installed from the program from the guide. that recovery cant do anything i tried to install a new ROM even the twrp but it always says it failed.
i thought the guide was suposed to install a operating system too but it didnt. now i only have the OnePlus recovery (from the guide) and nothing else. When i try to just turn on the phone (just the power button) its stuck in the 1+ logo. power button+volume up gets the 1+ logo and "fastboot mode" below it
the original recovery tool link doesent work so i downloaded the mini version he posted in the comments, this one ==> https://www.androidfilehost.com/?fid=24269982087019810
maby the OS didnt come with it???
PlsHelpMeee said:
i did all the steps, all of them work, when the program finished downloading/instaling things on my phone it turned on my phone and it was tuck at the 1+ logo again. when i held the power button+volume down it went to the custom recovery that was installed from the program from the guide. that recovery cant do anything i tried to install a new ROM even the twrp but it always says it failed.
i thought the guide was suposed to install a operating system too but it didnt. now i only have the OnePlus recovery (from the guide) and nothing else. When i try to just turn on the phone (just the power button) its stuck in the 1+ logo. power button+volume up gets the 1+ logo and "fastboot mode" below it
the original recovery tool link doesent work so i downloaded the mini version he posted in the comments, this one ==> https://www.androidfilehost.com/?fid=24269982087019810
maby the OS didnt come with it???
Click to expand...
Click to collapse
You have to use the other. This mini tool is from dec 2015.
At last you should have OnePlus recovery + OOS.
Can you retry on an older computer (easier on win 7).
See if it works. At the end, try to fahs the OOS 3.1.4 zip from here :
http://downloads.oneplus.net/oneplus-x/oneplus_x_oxygenos_3.1.4/
Kéno40 said:
You have to use the other. This mini tool is from dec 2015.
At last you should have OnePlus recovery + OOS.
Can you retry on an older computer (easier on win 7).
See if it works. At the end, try to fahs the OOS 3.1.4 zip from here :
http://downloads.oneplus.net/oneplus-x/oneplus_x_oxygenos_3.1.4/
Click to expand...
Click to collapse
I downloaded the oxygen OS form the link, i managed to install it with the 1+ recovery. Everything is working now, thank you for everything!!
Cool if you have done it !
Now unlock bootloader, flash new TWRP and you're good to go to flash all recents customs roms.
My top 3 : Candy 7 // Sultan's LOS // OmniROM
PlsHelpMeee said:
I downloaded the oxygen OS form the link, i managed to install it with the 1+ recovery. Everything is working now, thank you for everything!!
Click to expand...
Click to collapse
Hi, thank you for the information, you made my day! I confirm only the official rom can be flashed. Then I could unlock oem / bootloader and install lineageos on my oneplus x.
Greetings…
W̶i̶l̶l̶ ̶d̶o̶n̶a̶t̶e̶ ̶2̶0̶ ̶U̶S̶D̶ ̶t̶o̶ ̶w̶h̶o̶e̶v̶e̶r̶ ̶c̶a̶n̶ ̶f̶i̶x̶ ̶m̶y̶ ̶p̶h̶o̶n̶e̶ Fixed and contacted both Bordo_Bereli51 and Ante0.
My Huawei Mate 10 got in a bootloop after installing Xposed Framework
It was on Android Oreo 8.0 rooted and bootloader unlocked
Lock state info:
FB LockState: LOCKED
USER LockState: UNLOCKED
Leaving the device to boot normally: HUAWEI logo then reboots.
Vol up+power: eRecovery mode … doesn’t work (wiped data and cache .. tried to download firmware through wifi .. nothing works). ... then tried this method it worked while downloading the firmware .. but after verifying the firmware then installing it when it gets from 0% to 1% it fails and a red exclamation mark appears. :crying:
Vol down + power: fastboot: always get: FAILED (remote: Command not allowed) ). even though the bootloader is supposed to be unlocked. :crying:
Vol up and down: download mode .. on USB: stuck at 5% … without USB connection to computer: nothing happens (a red exclamation mark appears).
The device has an SD card slot: I tried placing the UPDATE.APP in dload folder and pressed both volume buttons but nothing appeared .. did I do something incorrectly?
Here are more info:
product-model: ALP-L29
vendorcountry: hw/meafnaf
build-number: System 8.0.0.38(0310)
fastboot getvar rescue_enter_recovery
getvar:rescue_enter_recovery FAILED (remote: FAIL:need all image flashed!)
fastboot oem oeminforead-SYSTEM_VERSION
...
(bootloader) :ALP-L29 8.0.0.128(C185)
Please help.
thanks in advance
====================
FIXED: Thanks to Bordo_Bereli51 who wrote this post and thanks for Ante0 for recommending DC Pheonix and for taking a lot of his time explaining a lot of things to me privately. contacted both as promised.
How I fixed it (credits to Bordo_Bereli51 for the guide .. I only modified it a bit and added some info from my experience):
1- I purchased a 19 euro -3 days pass for DC Pheonix.
2- Download Firmware Finder and click the "Common Base" tab, then download a FullOTA-MF firmware (all 3 files) which is approved for installation ( I copied the "changelog" link and pasted it in the 6th icon at the top "Firmware Checker" and it returned "Firmware approved for install" I' was not able to repack other non approved firmwares).
3- extract UPDATE.APP from update.zip
4- run DC Phoenix program .. tap the "Standard" button in Update mode .. select "update" and choose the UPDATE.APP you just extracted.
5- let it flash everything successfully then redo step 4 again.
6- Here's the trick before it flashes anything ... as soon as you see "utilizing backdoor" (or something like that) open Task Manager and force close DC Phoenix (it has to be BEFORE flashing anything, otherwise you might get errors like:
"error: exec '/system/bin/sh' failed: No such file or directory"
and AFTER utilizing backdoor (so you can use fastboot commands)
7-Download HWOTA8_Mate10 , place the 3 files you downloaded in step 2 in the "repack" folder, and rename "update_data_full_public.zip" to "update_data_public.zip" and "update_full_*ALP-L29*_hw_*meafnaf*.zip" to "update_all_hw.zip". Then run "repack.bat" and wait for it to finish.
8- run "ota.bat" in "ota" folder.
9- When it flashes the recovery_ramdisk and kernel plug your usb cable out and Reboot to recovery by pressing volume up + power button
10- When the phone is in recovery now ADB works (in case you need to do things manually).
11- When this process also finishes, the command center will tell you to press enter, so it boots to erecovery, which will flash the files.
12- Now your phone is unbricked after the flash.
Do not forget to do factory reset by pressing again at boot: (power + volume up) and selecting (factory reset).
After boot allow (OEM Unlock) under (developer settings) or otherwise the FRP will still be locked but the phone will work.
if someone will fix it can u tell me cause i have the same problem
---------- Post added at 06:58 AM ---------- Previous post was at 06:58 AM ----------
wait do u have twrp?
Dolev234786 said:
if someone will fix it can u tell me cause i have the same problem
---------- Post added at 06:58 AM ---------- Previous post was at 06:58 AM ----------
wait do u have twrp?
Click to expand...
Click to collapse
I have the same problem.
Dolev234786 said:
if someone will fix it can u tell me cause i have the same problem
---------- Post added at 06:58 AM ---------- Previous post was at 06:58 AM ----------
wait do u have twrp?
Click to expand...
Click to collapse
No, I don’t have TWRP.
hero3210 said:
No, I don’t have TWRP.
Click to expand...
Click to collapse
What does fastboot mode say, unlocked on both phone and frp?
ante0 said:
What does fastboot mode say, unlocked on both phone and frp?
Click to expand...
Click to collapse
yes both are unlocked
Dolev234786 said:
yes both are unlocked
Click to expand...
Click to collapse
Post input & output when you try to flash using fastboot
ante0 said:
Post input & output when you try to flash using fastboot
Click to expand...
Click to collapse
My device used to be bootloader unlocked
But I always get "FAILED (remote: Command not allowed)" for any fastboot command
I searched here and a lot of people had the same issue and they fixed it by relocking then re-unlocking the bootloader
I tried that .. relocked successfully but now I cannot unlock it again.
This is the current info from info.bat:
Lock state info:
FB LockState: LOCKED
USER LockState: RELOCKED
in fastboot mode it says:
PHONE Relocked
FRP Lock
=====
Input and output of fastboot:
fastboot flash recovery_ramdisk SYSTEM.img
target reported max download size of 471859200 bytes
sending sparse 'recovery_ramdisk' 1/7 (460797 KB)...
OKAY [ 3.650s]
writing 'recovery_ramdisk' 1/7...
FAILED (remote: Command not allowed)
finished. total time: 3.661s
Thanks for taking time to reply
hero3210 said:
My device used to be bootloader unlocked
But I always get "FAILED (remote: Command not allowed)" for any fastboot command
I searched here and a lot of people had the same issue and they fixed it by relocking then re-unlocking the bootloader
I tried that .. relocked successfully but now I cannot unlock it again.
This is the current info from info.bat:
Lock state info:
FB LockState: LOCKED
USER LockState: RELOCKED
in fastboot mode it says:
PHONE Relocked
FRP Lock
=====
Input and output of fastboot:
fastboot flash recovery_ramdisk SYSTEM.img
target reported max download size of 471859200 bytes
sending sparse 'recovery_ramdisk' 1/7 (460797 KB)...
OKAY [ 3.650s]
writing 'recovery_ramdisk' 1/7...
FAILED (remote: Command not allowed)
finished. total time: 3.661s
Thanks for taking time to reply
Click to expand...
Click to collapse
You need to enable OEM unlock in Settings-developer options. At least frp needs to say unlock else you won't be able to unlock or flash, at least not for free.
But since you can't boot you're pretty much limited to use dc unlocker/dc phoenix
ante0 said:
You need to enable OEM unlock in Settings-developer options. At least frp needs to say unlock else you won't be able to unlock or flash, at least not for free.
But since you can't boot you're pretty much limited to use dc unlocker/dc phoenix
Click to expand...
Click to collapse
Thanks for the reply
Do you recommend that I use dc unlocker or dc pheonix or FunkyHuawei?
do you recommend that I use dc unlocker or dc pheonix or FunkyHuawei?
hero3210 said:
Thanks for the reply
Do you recommend that I use dc unlocker or dc pheonix or FunkyHuawei?
Click to expand...
Click to collapse
Dc phoenix is what you'll need, Mate 10 is not supported in DC Unlocker. (Though DC Unlocker made DC Phoenix)
You'd just want it to flash stock anyway.
And it's cheaper than FunkyHuawei... FH "only" cost 1 credit to flash, but minimum to buy is 5 credits which is $41.
FH is easier though as you'd only need to setup DNS, but it's up to you
HCU/DC Phoenix pass for 3 days is €19, and then you have unlimited usage.
If you need further help you can find me at the telegram group https://t.me/HuaweiMate
as it's easier to do it live than through messages.
There is a "DC Phoenix repair tutorial" if you google it, use Method 1. Basically you just download the firmware update zip you're on now (and hw data zip) from http://pro-teammt.ru/firmware-database/ then extract update.app from it and select it in Phoenix, then extract update.app from hw data zip and select it as customization.
Alternatively you can downgrade to factory build using images from DC Phoenix (the build your phone came with) then update from there when you have a booting phone.
Thank you sooo much man. I really appreciate your help.
What version of Xposed frameworks did you install I have beta 4 working fine on my mate 10 pro.
tokoam said:
What version of Xposed frameworks did you install I have beta 4 working fine on my mate 10 pro.
Click to expand...
Click to collapse
yeah the bootloop was fixed in beta4 (original comment by dev) which wasn't officially released to the channel when I installed it, so I didn't know about it until I got the bootloop.
Anyways, I just managed to fix my issue. I'll post about it now.
ante0 said:
What does fastboot mode say, unlocked on both phone and frp?
Click to expand...
Click to collapse
what would happens if it says unlock on frp? i cant load twrp i have flashed many times but i does not take it.
I bricked my Huawei Mate 10 too
Please help.. I also bricked my Huawei Mate 10 ALP-L29C636...
I installed the EMUI 9.0 on my device using the HWOTA8_Mate10 method which was successful. The EMUI 9.0 ROM was from FirmwareFinder: ROM version ALP-L29C636E2R1P8B108-log (9.0.0.108). I didn't have any issues at all but since Huawei Mate 10's EMUI 9.0 is still in Beta, I decided to switch back to the stable EMUI 8.0.
Here's where the problem started... Since I want to downgrade, I went ahead and downloaded the 3 needed files (update.zip, update_all_hw, update_data_public) from FirmwareFinder: ROM version ALP-L29C636B143 (8.0.0.143). I fired up HWOTA8_Mate10 and started the installation process. The first step was to boot to fast boot and then plug the device, after that, the software asked me to unplug the device and press volume+ and power button but the device won't boot to recovery anymore. The device is now stuck at "Your device is booting now..." I tried rebooting the device but it won't work. Tried to go to eRevovery to wipe cache/factory reset but it will go back to "Your device is booting now..." page. I tried reinstalling the recovery.img via fastboot and tried to boot to recovery mode again but it won't work anymore. I believe my device is now soft bricked . I can still boot to fastboot, I even tried fastboot flash system system.img which was successful but the device still won't boot. Please help how to recover my device. I think I went too far and now I don't know how to fix this issue.
Carnage! said:
Please help.. I also bricked my Huawei Mate 10 ALP-L29C636...
I installed the EMUI 9.0 on my device using the HWOTA8_Mate10 method which was successful. The EMUI 9.0 ROM was from FirmwareFinder: ROM version ALP-L29C636E2R1P8B108-log (9.0.0.108). I didn't have any issues at all but since Huawei Mate 10's EMUI 9.0 is still in Beta, I decided to switch back to the stable EMUI 8.0.
Here's where the problem started... Since I want to downgrade, I went ahead and downloaded the 3 needed files (update.zip, update_all_hw, update_data_public) from FirmwareFinder: ROM version ALP-L29C636B143 (8.0.0.143). I fired up HWOTA8_Mate10 and started the installation process. The first step was to boot to fast boot and then plug the device, after that, the software asked me to unplug the device and press volume+ and power button but the device won't boot to recovery anymore. The device is now stuck at "Your device is booting now..." I tried rebooting the device but it won't work. Tried to go to eRevovery to wipe cache/factory reset but it will go back to "Your device is booting now..." page. I tried reinstalling the recovery.img via fastboot and tried to boot to recovery mode again but it won't work anymore. I believe my device is now soft bricked . I can still boot to fastboot, I even tried fastboot flash system system.img which was successful but the device still won't boot. Please help how to recover my device. I think I went too far and now I don't know how to fix this issue.
Click to expand...
Click to collapse
Spamming every thread won't help you fix your issue.
Pretoriano80 said:
Spamming every thread won't help you fix your issue.
Click to expand...
Click to collapse
I apologize. I panicked since I don't know what to do. I will continue on the thread which I received a response.
Hi, I am using a oneplus 7t pro mclaren edition. I have soft-bricked the device. I tried to change the filesystem in twrp to f2fs when i was in stock rom (I know it was a stupid mistake). Now the boot and recovery partitions are destroyed. I can boot to actual fastboot mode. Tried to use payload dumper but whenever it tries to boot fastbootd it says
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Tried erase everything I got the following error using "fastboot -w"
Erasing 'userdata' OKAY [ 0.229s]
/home/abhijith/Documents/op7t/output/make_f2fs failed with status 1
fastboot: error: Cannot generate image for userdata
I have heard of MSM unbrick tool but as far as i know it only works in windows , before installing VM with windows , I want to know if there is any other way i can recover my device. I have a11 fastboot rom and a12 stock rom. Please help
I have exactly the same problem, same errors etc. if I find any solution I'll post it here. Can't use my phone until then I guess. It all happened after my phone was bricked after trying to install TWRP (previously used LineageOS Recovery).
I followed this guide which resulted in the same errors as for you: https://forum.xda-developers.com/t/...ock-fastboot-roms-for-oneplus-7t-pro.3991189/
Okay, I managed to unbrick my phone, but you won't like the (probably only) solution:
- You NEED Windows (7-10) for this, as the tools are only available on this platform, sadly
- There is this one Indian Guy that will save you:
- Includes how to install all drivers and how to get your phone into COM Mode
- This uses the MSM tool. For 1+ 7T Pro, get it here: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4002909/
- This is going to STOCK RESET you phone 100%, meaning that your bootloader will be locked etc.
- If you get into any Chinese menu after the phone reboots, you can use Google Lens for translation
I can't believe this worked because it just feels so hacky, but trust me, it's a good last resort as you can always put your phone into COM Mode, regardless of how hard you messed up the system [citation needed].
For me even in device manager qualcomm device itself is not showing :0
abhijiths362 said:
For me even in device manager qualcomm device itself is not showing :0
Click to expand...
Click to collapse
Follow the video. When all drivers are installed and you hold both volume buttons while the device is off, it will show up as a COM/serial device for a few seconds before booting.
Important: Only connect the cable while already pressing the buttons or it won't work.
I was able to get to edl mode and msm tool was detecting but now i am facing sahara communication error i dont have official cable so maybe that might be the reason will try that also
@Colin_T Thanks for the help. I was able to install stock rom to my oneplus 7t pro. I really want to install pixel experience, in the instructions it is saying flash oos 12 firmware. But in the official website i am only seeing 11. What to do?