I see that XDA is filled with threads that leave a lot of loose ends. I did not see anyone post this yet, but there is an MSM unbrick tool for this model, hidden in plain sight (I will be testing it some time tonight):
Index of /list/Unbrick_Tools
You'll also need the Quantum drivers, duh...
https://drive.google.com/uc?id=1zKPFtcc2X_Nf70mcvn9TBu60bHl6Q3cP&export=download
I miss the good ol' days when we could flash a K20 Plus without having to do backflips. These new devices are awful. Anyway, once I unbrick this piece of junk I may get adventurous enough to try and install Lineage, again. I suspect that trying to install it when 12 was already on had something to do with it. Will try to use MSM to put 11 back on (it is softbricked in a loop but I can at least get into fastboot, so we'll see).
I'm soft bricked but got into fastboot by pressing all three buttons simultaneously to turn the phone on.
I would LOVE to have a vintage android version on here, back when things were fast and simple. I'm not yet talented enough to make that happen. My only real experience is with Mr. Travis Holt's K20 roms back in the day. They worked so well that I'm considering just buying an old K20 again and being done with all this new stuff. It's quite a disappointment.
Gonna get back to unbricking, flashing and ripping my hair out. Wish me luck.
averyboringusername said:
I suspect that trying to install it when 12 was already on had something to do with it.
Click to expand...
Click to collapse
Yes absolutely. The lineage install page warns that you must be on android 11 https://wiki.lineageos.org/devices/dre/install
Warning: Before following these instructions please ensure that the device is currently using Android 11 firmware.
Click to expand...
Click to collapse
They even make you click a button to acknowledge that you've read the warnings before they show the install instructions.
There is also a thread in this forum warning people
Downgrade US OEM (DE2117) Android 12 firmware to Android 11 BEFORE installing Lineage!
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img If you are updated to Android 12 firmware and want to install Lineage, you MUST downgrade first to: DE2117 OEM...
forum.xda-developers.com
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img
Click to expand...
Click to collapse
I'm sorry, but how many more warnings do you want?
Search the forum on how to recover the softbrick.
Related
I have the Huawei Ascend Mate 2 MT2L03
Build number is currently MT2-L03C00B322
Android 5.1
EMUI 3.1
I don't have it rooted, and have never flashed anything to it.
Everything running on it is stock, which I don't mind. But I was thinking it'd be nice to step up to android 7.0 or so.
I have read around some and see that a dev SHM is working on it?
Also my bootloader is still locked, but I found out how to get the unlock code.
Just wondering... should I bother with upgrading to something newer, rooting it and all that? Or is 5.1 still fine?
the closest youll get is a cm 13.1 nightly or snapshot. i think its worth the switch.
I'm using SHMs CandySix 6.0.1 and it was definitely worth it for me to unlock and root to use custom ROMs.
Since you have never flashed before, allow lots of time to read the instructions and don't be in a hurry when you do it.
Check out the HAM2 index (link in my signature). Should be very helpful. The only problem is I don't know what the latest method is for getting the bootloader unlock code. Can you tell me what it is now so I can update the index and the starter pack?
As for SHM's 7.0, he's not working on it anymore. However our phone is officially supported by CyanogenMod, so I think we'll be getting CM14? Not sure though.
CandySix is a good choice. I've been running it for several months now and it's been great.
Latest bootloader unlock method from Huawei Website
ScoobSTi said:
Check out the HAM2 index (link in my signature). Should be very helpful. The only problem is I don't know what the latest method is for getting the bootloader unlock code. Can you tell me what it is now so I can update the index and the starter pack?
As for SHM's 7.0, he's not working on it anymore. However our phone is officially supported by CyanogenMod, so I think we'll be getting CM14? Not sure though.
Click to expand...
Click to collapse
I made a post in another topic, maybe this will help you!? http://forum.xda-developers.com/showpost.php?p=69309478&postcount=463
Forgive me, but what android version is cm 13.1 nightly or snapshot or CandySix running? I currently use android 5.1, and everything is stock.
I don't mind the EMUI interface. I also don't have any application that I'm wishing to uninstall.
I want to upgrade to a newer version because I feel maybe it'd be faster? But I have just also considered getting the LG G5, or maybe the pixel?
So would using a newer android version make my phone faster? I know the HAM2 only has 2gb of ram, and for internal storage it says I have total: 11.69gb but 2.94gb free. But that's not bad considering the amount of apps I have. I also have a 32gb microsd card.
If I flashed a different android version would I still have the radio and the EMUI? Sorry if my terminology is off, still new
Security is the key?
that1guyyep101 said:
I have the Huawei Ascend Mate 2 MT2L03
Build number is currently MT2-L03C00B322
Android 5.1
EMUI 3.1
I don't have it rooted, and have never flashed anything to it.
Everything running on it is stock, which I don't mind. But I was thinking it'd be nice to step up to android 7.0 or so.
I have read around some and see that a dev SHM is working on it?
Also my bootloader is still locked, but I found out how to get the unlock code.
Just wondering... should I bother with upgrading to something newer, rooting it and all that? Or is 5.1 still fine?
Click to expand...
Click to collapse
I use the HAM2 as a mini tablet/media player now to save battery life on my Nexus 6p. Currently on Android 5.1 with EMUI 3.1 and have just unlocked the bootlock and now seeking to figure out how to proceed with rooting and flashing to CM 14 or later. My concern is with all the security holes on 5.1 Official version from Huawei since it has known security holes and is not getting moved forward or patched. While I like the features on the 6P and the improved security the battery life sucks compared to the HAM2 (true for most phones).
I will watch this thread and will keep searching for tips to make this first round of rooting and flashing to CM on my own a learning experience. I would strongly recommend anyone on older versions of Android seek to get more current due to the massive security issues. Hate leaving behind old equipment that I can keep in some use with rooting and upgrading on the software.
To the OP, you can try out CM14.1 now thanks to mdmower.
As for learning how to root and flash, check out the HAM2 index thread for some useful goodies and the starter pack I made. They should be helpful. If not, you can ask us of course.
Unlocked bootlocker, HiSuite and ADB present, can't load twrp
ScoobSTi said:
To the OP, you can try out CM14.1 now thanks to mdmower.
As for learning how to root and flash, check out the HAM2 index thread for some useful goodies and the starter pack I made. They should be helpful. If not, you can ask us of course.
Click to expand...
Click to collapse
Thanks for the great information package ScoobSTi.
Have HAM2 MT2L03 with Android 5.1 stock, EMUI 3.1, attempting to root then flash from a Windows 10 PC. Bootlocker unlocked, HiSuite 5.0.1.300_OVE and ADB loaded and appear to be working as both phone and SD card files are accessible from PC. Have placed TWRP version in the ADB folder and renamed to TWRP.img, placed SuperSu_v2.79....... in root of SD card.
Getting no devices listed when run adb devices from ADB on pc although drivers show good in device manager and files on device are accessible.. When run c:\adb>fastboot flash recovery c:/adb/twrp.img get response error: cannot load 'c:/adb/twrp.img' after I reboot HAM2 into recovery.
What am I missing?
Have reviewed many threads and posts and am too dim to get what I am doing wrong.
Need to turn off phone and go to bootloader the cmds won't reboot the phone,it needs to manually put in too bootloader and then run the cmds
Sent from my Ascend Mate 2 using Tapatalk
Fastboot looking for HiSuite only
hopkins31 said:
Need to turn off phone and go to bootloader the cmds won't reboot the phone,it needs to manually put in too bootloader and then run the cmds
Sent from my Ascend Mate 2 using Tapatalk
Click to expand...
Click to collapse
When I manually reboot into recovery the HAM2 goes into Fastboot & Rescue Mode but does not root with TWRP as noted. The HAM2 Fastboot screen does show the device as "PHONE: Unlocked". New here so cannot post a pic of the boot screen or screenshots of the adb responses in the command prompt. Issue seems to be with the HAM2 not showing up on the adb devices listing.
Good afternoon everyone.
I got interested in putting a custom rom on my Galaxy Note 8 I have laying around (Current Daily driver has been upgraded to a Note 20 Ultra so I have no hurry to fix this issue.)
I followed the steps from one of the forum guides and installed TWRP, the first thing I noticed was that my Note 8 had 2 System directories while this is supossed to be a A only model. (Which struck me as odd.) After installing a android 11 Rom (A Only) I was stuck on the boot screen not loading any further. I found this logical as Android 11 is not really supported as of yet on this model.
I then decided to grab Havoc OS seeing as that was a stable version that should run properly i've seen people on Youtube install it on their S8's without a hitch. After installing this the way the guide told me I got stuck in a boot loop. (Also used an A only ROM) My final attempt will be downloading an A/B ROM and see if that works (Which i genuinly doubt.) but will update this post when that's finished.
On the post I also have added a screenshot of what I see when trying to install an Image. My question to you guys is, does this phone have a A/B configuration after all or am I doing something wrong?
Edit: AB was also not the solution.
After rummaging around a bit more with the phone I found out that i was using an extremely out of date version of the Pie Vendor. I looked at download by Version number instead of by date. Reinstalled Havoc, installed pie vendor.
Now the phone reboots into downloading mode. It's been this way around 10 minutes now will post an update in about an hour or so of leaving it in that state.
QuirkyTechGuy said:
After rummaging around a bit more with the phone I found out that i was using an extremely out of date version of the Pie Vendor. I looked at download by Version number instead of by date. Reinstalled Havoc, installed pie vendor.
Now the phone reboots into downloading mode. It's been this way around 10 minutes now will post an update in about an hour or so of leaving it in that state.
Click to expand...
Click to collapse
Odd. Truly. It could be due to the first install of GSI version. Here's what I suggest.
I hope u have a back up of your old rom, if so, flash it back. If not, check your twrp version. Update it to latest. Flash a non gsi rom. Boot the phone. If it boots and you have it running, then flash a gsi rom .
maxed4901 said:
Odd. Truly. It could be due to the first install of GSI version. Here's what I suggest.
I hope u have a back up of your old rom, if so, flash it back. If not, check your twrp version. Update it to latest. Flash a non gsi rom. Boot the phone. If it boots and you have it running, then flash a gsi rom .
Click to expand...
Click to collapse
I sadly forgot to make a back up of the rom which in hindsight is stupid of me. I did check and have the latest TWRP version, and managed to get LineAge OS 17.1 working without it being Treblized .
Should i now go on with the procedure of trying to flash a GSI rom with the Treble Convert?
QuirkyTechGuy said:
I sadly forgot to make a back up of the rom which in hindsight is stupid of me. I did check and have the latest TWRP version, and managed to get LineAge OS 17.1 working without it being Treblized .
Should i now go on with the procedure of trying to flash a GSI rom with the Treble Convert?
Click to expand...
Click to collapse
Let's take a back up first and then try. Which tutorial are u following.
Install Android 11 (R) On Any Treble Device ( Detailed Guide)
This way you can install Android 11 On any device without the need of waiting for your manufacturer to push the latest update.
xtremedroid.com
And try Google or aosp gsi from here https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Here's @corsicanu thread for instructions.
But it's for android 9? M not sure though
[AOSP][Treble][G95*F/FD] hadesTreble [03.09.2019]
Disclaimer I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it...
forum.xda-developers.com
So I have a moto g power (2021) and the model is XT2117-1 and I've been searching for a clear way to install Android 11 and one way I saw I needed root so I decided to try too root my phone and spent hours just trying to get twrp to work and obviously to no avail and I was going to try a GSI but now I'm even more confused since I need twrp again so help me please I just want to try Android 11 idc if it sucks since I can always go back
COWLORD2000 said:
So I have a moto g power (2021) and the model is XT2117-1 and I've been searching for a clear way to install Android 11 and one way I saw I needed root so I decided to try too root my phone and spent hours just trying to get twrp to work and obviously to no avail and I was going to try a GSI but now I'm even more confused since I need twrp again so help me please I just want to try Android 11 idc if it sucks since I can always go back
Click to expand...
Click to collapse
You can use twrp from an adb shell nowadays. That's how I use our twrp since I don't have a mouse.
TWRP Commandline Guide
</style>CLIENT SIDE/SCRIPTinstall FILENAME : install FILENAME zip file.
twrp.me
BUT You don't need twrp to install a GSI ROM.
You can fastboot flash it to System after wiping System. These guys came a long way on this phone in this thread. It has a lot of details. Take special note of what to do if it says partitions full or whatever. That's very important. And be prepared before you start to flash back to stock if it fails for any reason.
Anyone try any GSI ROMs on the G Power 2021?
It's pretty standard hardware as far as phones go. No weird under display fingerprint reader or anything. Anyone try a GSI ROM? It might "just work" or "almost just work but you need to run a few commands to fix something".
forum.xda-developers.com
I may flash the Resurrection Remix Q GSI tonight to try it out, but I expect to flash back to stock because, from what I've read, it's very likely not everything will work in a GSI and I need most things to work.
I've been running Lineage OS with Micro G for years. I just update to each version using the built-in updater. Never had any issues.
Well, recently I tried to update to the latest 12/17 release, but now it dumps me straight to the Fastboot screen and won't boot up. I've tried the "recovery" "bootloader" and "start" options and they just leave me at the fastboot mode.
Where do I go from here?
Why not ask in the thread of the LOS version you're on/tried to update to?
If all else fails you can MSM back to stock and start over, but you WILL lose all your files/data on the device.
Nimueh said:
Why not ask in the thread of the LOS version you're on/tried to update to?
If all else fails you can MSM back to stock and start over, but you WILL lose all your files/data on the device.
Click to expand...
Click to collapse
I didn't ask mostly because I didn't know there was one. I see it now; didn't realize there was a 5 / 5T cross development forum. I'll ask there, thanks.
Hopefully not all is lost. But my phone did have an excellent run.
Hi
Quite bored of Oneplus updates for my Nord 2 5G that transforms more and more the phone in publicity support for OnePlus CEO messages, and adding features I don't care at all, I'm looking to flash it with an alternative ROM.
What is most stable and operational ROM for that device currently ? The version of the device I have is DN2103 (bought in Switzerland).
Thanks for your advices,
Vincèn
Tried them all. Evolution X is the most often updated and works the best for me.
Hey there!
I also need some much needed insight in how to continue with this device (DN2103 bought in NL, Europe; just updated from 11.A.14 to 11.A.21). I suspect I will probably need the same answer as OP is looking for.
This is my second OnePlus, I was using a OnePlus X before running my first and only ROM, Lineage OS, to be able to move on to Android 10. Then screen broke for the second time after I had already fixed up the whole phone myself before that using brand new parts (Screen, frame, backplate) except for the motherboard still original. So I decided it was time for a new device.
Really love the DN2103 itself, except for the whole rooting / OTA update process, although it was a good training in getting to know all the technicalities. I had been running rooted 11.A.14 since it came out till yesterday, because I was avoiding dealing with the whole process again.
Anyway I kicked myself under my butt and got myself to 11.A.21 now. I was planning to just continue updating OOS till the latest 11.C.10 / 11.C.13, because after all this effort, I'm too curious to not check out the new Android.
But I just happened to read some thread where people were saying that somewhere after 11.C.4 it's not possible anymore to get into fastboot / BROM mode and thus no means to get TWRP?? That sounds horrible, one mistake rooting and it would be a big mess, having to downgrade to OOS 11 again and bla bla bla, why the f...?
So, I just need to hear this from someone, is this correct? I'm too tired to investigate now myself after a 20h OTA/rooting session behind me and just 3h sleep.
And how is everyone dealing with it that wants root? Has everyone moved on to other ROMs for Android 12 / 13, because of this?
In the update process yesterday for some reason my phone did a complete wipe without asking / warning. So I really need to get to a stage in this update process where I can restore all my ****. I've been at this for 24h right now and was happy to do so as I was making steps. but now I suddenly got hit in the face by this news.
tl;dr PLEASE confirm/deny this news (underlined part above) and help me decide if the only comfortable way is to ditch OOS for a custom ROM to get Android 12 / 13 with root & TWRP. I've thrown 24 hours into OTA updating OOS 11, now got to 11.A.21, but phone somehow got wiped in process, so now I really need to finish upgrading and restore data, because I'm without all the apps / accounts etc. I depend on for daily life.
I do really enjoy the road but now I HATE being lost along the way. Show me the light and, if ROM, same question as OP
Sorry if a bit off-topic + long post...
Yes, you need to have android 11 to enter fastboot. I had 12 and had to downgrade. Trust me, this is the most fuked up thing.
wuttehhell said:
Yes, you need to have android 11 to enter fastboot. I had 12 and had to downgrade. Trust me, this is the most fuked up thing.
Click to expand...
Click to collapse
Stop waiting for oneplus. There are great roms on android 13 that work very nice. What i am using is Evolution X. Tried them all and this is the one i stick to. Found no bugs, very consistent updates and the team as i see work very fast on every bug people find.
Btw, u dont need root to change rom, only if you want. I personally dont use root and works great.
wuttehhell said:
Tried them all. Evolution X is the most often updated and works the best for me.
Click to expand...
Click to collapse
Thanks for the info, and noticed too in forum that it looks to be the most up-to-date and maintained ROM for DN2103 and it looks to have no more any blocking bugs such as Wifi or Bluetooth not working, or random reboots/crashes. I'm running right now version DN2103_11_C.12 with Android 12. Is it ok to upgrade to Evolution X straight ? as I see people speaking about downgrade first to Android 11 :/
wuttehhell said:
Stop waiting for oneplus. There are great roms on android 13 that work very nice. What i am using is Evolution X. Tried them all and this is the one i stick to. Found no bugs, very consistent updates and the team as i see work very fast on every bug people find.
Click to expand...
Click to collapse
Thanks a lot for confirming! I'd already read the thread and indeed Evolution looks like the best option, so that's decided then. Wish me luck flashing the ROM
And about root, I really have some essential mods that need root. For example Advanced Charge Controller (I use it with the GUI app ACCA for convenience, else it's only terminal). I limit my charging by default to 80%, which translates in about a 4x increase in lifetime of the battery. On normal days I don't need any more than that, and it always has the option to charge to 100% if you know you're gonna have a long day without charging capabilities.
vincebay said:
Thanks for the info, and noticed too in forum that it looks to be the most up-to-date and maintained ROM for DN2103 and it looks to have no more any blocking bugs such as Wifi or Bluetooth not working, or random reboots/crashes. I'm running right now version DN2103_11_C.12 with Android 12. Is it ok to upgrade to Evolution X straight ? as I see people speaking about downgrade first to Android 11 :/
Click to expand...
Click to collapse
As I understand, and as @wuttehhell just confirmed in this thread, once you update OxygenOS beyond Android 11, fastboot and BROM mode don't work anymore. This means you can't install a custom recovery like TWRP to flash a new ROM, neither can you flash it using fastboot.
This means you have to rollback to Android 11 first. Fortunately OnePlus has official rollback packages, which is just a .ZIP archive like any other update, except it will downgrade to a previous version. Warning: a rollback package will WIPE ALL DATA. So make sure to backup anything you need to keep before downgrading. The upside is you can do a clean flash of the ROM (flashing method where device gets wiped), which is the most stable method and gives you a fresh OS that will use less battery and such.
I think the process of downgrading itself is very simple though. If you get stuck let us know, there's many knowledgeable people here lucky for us so keep a positive attitude and with a little luck we'll both be running Evolution X in the coming days!
Releece said:
As I understand, and as @wuttehhell just confirmed in this thread, once you update OxygenOS beyond Android 11, fastboot and BROM mode don't work anymore. This means you can't install a custom recovery like TWRP to flash a new ROM, neither can you flash it using fastboot.
This means you have to rollback to Android 11 first. Fortunately OnePlus has official rollback packages, which is just a .ZIP archive like any other update, except it will downgrade to a previous version. Warning: a rollback package will WIPE ALL DATA. So make sure to backup anything you need to keep before downgrading. The upside is you can do a clean flash of the ROM (flashing method where device gets wiped), which is the most stable method and gives you a fresh OS that will use less battery and such.
I think the process of downgrading itself is very simple though. If you get stuck let us know, there's many knowledgeable people here lucky for us so keep a positive attitude and with a little luck we'll both be running Evolution X in the coming days!
Click to expand...
Click to collapse
@Releece thanks for the details and so if I have well understood the whole process:
backup datas
Downgrade to Android 11 using the OTA downgrade package and procedure from oneplus (which implies a full reset of device)
Reboot at least one tine in Android 11
Flash TWRP
Reboot in TWRP (be careful not to boot Android or I'll have to reflash TWRP)
Flash Evolution X zip
Boot normally and enjoy Evolution X
Am I correct ? I have seen also that the phone has the same annoying double "bank" when you flash it that I had on previous OnePlus phones. Does it imply I have to do each flashing process on both banks ?
Thanks
vincebay said:
@Releece thanks for the details and so if I have well understood the whole process:
backup datas
Downgrade to Android 11 using the OTA downgrade package and procedure from oneplus (which implies a full reset of device)
Reboot at least one tine in Android 11
Flash TWRP
Reboot in TWRP (be careful not to boot Android or I'll have to reflash TWRP)
Flash Evolution X zip
Boot normally and enjoy Evolution X
Am I correct ? I have seen also that the phone has the same annoying double "bank" when you flash it that I had on previous OnePlus phones. Does it imply I have to do each flashing process on both banks ?
Thanks
Click to expand...
Click to collapse
Yep that should do it, looks like you did your research and understand the process.
I had the same question earlier. Strangely I found that the Nord 2 does not have A / B partitioning. I can only detect an A-partition with apps designed to test it. I didn't have to do anything extra / another way while rooting with Magisk, OTA updates or flashing ROM. I thought A/B was enforced on all phones since Android 10 or sth, but apparently not all.
I would add one extra step, after you reboot into TWRP (before flashing the ROM) make a backup of all the individual partitions one by one (so you can restore any single partition in the future), even the tiniest ones.
Some contain calibration data for e.g. Bluetooth and fingerprint sensor that are specific to your device. Now this whole process should leave them untouched, but if anything ever happens to them, the only way to get your phone working again is to send your phone to a service centre, so it's a good idea to have everything backed up.
They will be stored in the TWRP folder in /sdcard/, which is the folder you can see on your PC. So after backing them all up, you can just copy them to your PC.
I successfully flashed Evolution yesterday, and all went well Initially the new Android 13 UI was a bit of a shock from what I was used to, but I'm starting to like it already, especially after going over the settings. And it works smooooth like butter. The only thing that annoyed me was the haptic feedback, which feels very mushy instead of snappy. But putting vibration strength to low helps a lot. Maybe I can find a way to modify it later.
I had one little hickup: Evolution install instructions say this for TWRP before flashing ROM:
"3. Tap [Wipe] , then [Format data]. type "yes" and Enter"
But when I did this, it removed the media folder at /data/media/ instead of just emptying it. I remember it gave me a pop-up saying something like, for /data/media/ to get populated I would probably need to boot to system. But if I would've done that stock would overwrite recovery.
I don't have a lot of knowledge about this, but this folder gets mounted to /sdcard/ and is where your internal storage is mounted to. So after the wipe I wanted to copy the ROM .zip to my phone using the file manager. Windows did recognize my phone as having internal storage, and I could open it, but it didn't see any file/folder/free space and I couldn't copy anything to it.
I solved it by renaming ROM to sth simple like evolution.zip, placing it inside platform-tools folder, and then using ADB push command, so it looked like:
ADB push C:/platform-tools/evolution.zip /data/
It doesn't give any feedback while copying and I didn't even see much disk usage on Windows task manager, so I was about to get nervous and close the terminal, but then it suddenly completed successfully and I could see the evolution.zip in TWRP file manager. After that flashing took just a few minutes and everything went perfect.
Now I don't know if it's maybe a typo in the instructions or if TWRP had a bug, but I don't think so as it specifically gave me a prompt about it. I think it's better to just tap [Wipe] and then do the usual factory reset slider, with data, dalvik and cache selected. Think I'll make a post later in the Evolution thread to ask.
Good luck!
Hi, I don´t like the colors on Oxygen OS. I don't know if it's cause by our screen or is something related with the ROM. In Samsung or Xiaomi colors are more brilliant and saturated. In Evolution ROM, can you modify this issue?
So I have been able to dowgrade my DN2103 to 11_A20 running Android 11 but I'm stuck there !
Each time I try to flash twrp or load it in device I get that:
[email protected]:~/Bureau$ fastboot boot twrp.img
Sending 'boot.img' (131072 KB) OKAY [ 3.310s]
Booting FAILED (remote: 'not allowed in locked state')
fastboot: error: Command failed
[email protected]:~/Bureau$ fastboot flash recovery twrp.img
Sending 'recovery' (131072 KB) OKAY [ 3.371s]
Writing 'recovery' FAILED (remote: 'not allowed in locked state')
fastboot: error: Command failed
I have unlocked OEM protection into it and allow USB debug. Any ideas what's the problem ?
damn was a long time I had not done Android flashing so was a little more complicated but made it (well it looks to be so far Will see if it boots after initial setup and now hanging on the Phone initial preparation but should go very soon I think
Thanks