Develop Bugs

Swift 2 Plus won't boot, stuck with locked bootloader

Please don't ask why (the answer will be: "because I'm stupid"), but I relocked my bootloader and now my Swift 2 Plus won't boot anymore. When turning it on, it vibrates and the Wileyfox logo flashes for less than a second. After that the screen stays black and nothing happens. Same thing when I try to boot into recovery. I can only boot into the bootloader but I can't flash any images or unlock it again ("FAILED (remote: oem unlock is not allowed)").
Is there any way I can revive my phone or is it lost?

I think your only way is to flash twrp again with fastboot install method :
//twrp.me/devices/wileyfoxswift2.html
And then flash the stock rom :
//cyngn.com/support
hope it will helps you!
---------- Post added at 02:07 PM ---------- Previous post was at 02:05 PM ----------
Sorry, I'm a new user so I can't post link, you've just have to ad "https" at the beginning of the line.

Thanks for answering, but I can't do that, because the bootloader is locked and protected from unlocking. I guess the only thing I can do is ask the support if they can provide the mbn and xml files that are needed for unbricking with QFIL (I can boot into edl mode as I recently found out). They probably won't but it's worth a shot.

If you use the signed zip ( not the fastboot image) the default recovery should be able to install it.

It doesn't boot to recovery. Only fastboot and edl mode work.

You could try flashing fastboot image from http://cyngn.com/support
Sent from my Swift 2 using XDA-Developers mobile app

Thanks, but that doesn't work with a locked bootloader (already tried).

It seems like the only way to revive it is with QFIL, but for doing that it needs the matching mbn and xml files that aren't included in the factory images. Wileyfox support wasn't helpful, either.

xrmnx said:
Thanks, but that doesn't work with a locked bootloader (already tried).
Click to expand...
Click to collapse
Can't we put the dirty cow bug to a use now? It should work on the phone unless it has the latest security patches, right? And with root privileges you should be able to flash a new recovery or reset the phone.:fingers-crossed:

I'm actually not sure, if I still have root privileges. It could be that I turned it off inside the SuperSU app.
I tried to flash the stock rom and that didn't work, though. Do I have to do something different than usually to flash with root privileges?

boa05 said:
Can't we put the dirty cow bug to a use now? It should work on the phone unless it has the latest security patches, right? And with root privileges you should be able to flash a new recovery or reset the phone.:fingers-crossed:
Click to expand...
Click to collapse
I read a little about dirty cow, now (didn't know much about it before), but if I understand it right, I need adb to upload files onto the phone, right? Sadly, adb doesn't work. Only fastboot :/

Hmmm, there is a similar thread for the Nexus 5X. You might want to check it out if you haven't already ( http://forum.xda-developers.com/nexus-5x/help/nexus-5x-permanently-bricked-locked-t3232105/page2 ).
A few of the suggestions were to try with:
Code:
fastboot flashing unlock
or
Code:
fastboot format userdata
fastboot format cache
I don't know if it will be of any help but it is worth a shot.
You could try to flash individual portions of the stock image like the recovery or the userdata but I doubt that it will be successful.
PS: From the thread above, for some reason removing the SIM card allowed them to enter recovery.

Thanks, but none of these solutions works. Already tried all of them a couple of times....

Hmmm, how about you try to trick it then?
Grab the official signed firmware, place it on SD Card and try with:
Code:
fastboot update <path/to/zip>
or this one to try to wipe the device? (dunno if the command is still in use, though)
Code:
fastboot -w
If this doesn't work as well, I guess it will be a waiting game for QFIL files.

Pak0St said:
Hmmm, how about you try to trick it then?
Grab the official signed firmware, place it on SD Card and try with:
or this one to try to wipe the device? (dunno if the command is still in use, though)
If this doesn't work as well, I guess it will be a waiting game for QFIL files.
Click to expand...
Click to collapse
I tried to flash/update every official rom (with and without -w) there is, but I never put it on an SD-card. Does that make a difference? If so, this might be one ofhe stupidest mistakes I ever made :/
I'll try in a few days. Not much time, at the moment...
Yes... Waiting for QFIL files is what I'm prepared for...

The idea with the SDCard is just a random thought. There is a slight chance to trigger the allowed update policies.
Usually you place the update.zip through adb (not possible in this situation) but placing it on the sdcard is possible.
Still, QFIL is the safest bet once someone uploads the files.

Pak0St said:
Still, QFIL is the safest bet once someone uploads the files.
Click to expand...
Click to collapse
That's what I thought. Since I couldn't find any (yet), is there a way to extract the QFIL files from a working phone (I bought another one since I needed a phone)? I don't think so, but I hope I'm wrong...

xrmnx said:
That's what I thought. Since I couldn't find any (yet), is there a way to extract the QFIL files from a working phone (I bought another one since I needed a phone)? I don't think so, but I hope I'm wrong...
Click to expand...
Click to collapse
I'm in the same boat here, same phone and same issue. Did you find a way to fix it? already searched all internet for a fix. Thanks a lot

Sorry, but for some reason I never saw your answer... I never found a solution either, though

how to unlock bootloader
Use fast boot to unlock the bootloader again.
connect your Swift 2 to your PC and in a command prompt type the following "fastboot oem unlock"
When you press enter, check the phone and using the volume keys you need to select yes and then press power to execute.
Your bootloader should then be unlocked again. Good Luck.

[SOLVED] PLEASE HELP - HardBricked my OnePlus 5T

Dear Community,
I just searched the past 2 days for a solution but I've not been lucky
Therefore I'd like to ask for help in this forum and hope there is some additional hint or hack I could try...:
So here's the situation:
OnePlus 5T (8/128) with a non booting or not "useful" OS (see last point what I've tried)
No TWRP or CWM
Stock Recovery present
Bootloader Locked
Allow Bootloader to be unlocked = FALSE
What I've already tried yet:
Flashing TWRP --> Not possible Bootloader Locked
Flashing regarding any other kinds like "update" or "flash all" as provided with TOOL_ALL_IN_ONE
ADB Sideload any available ROMS (Original "full" OP5T / FreedomOS / Omni8) --> ADB stops at 47% in Stock Recovery regardless of size of the ZIP file
Tried different versions of ADB (32 & 64 Bit / older & new / also with the LargeAddressAware approach / and on multiple PC's) --> Always same error (47%)
Stumbled upon the possibility to EmergencyDownload a factory flash due to Qualcomm chipset using the MSM-Download-Tool --> Only OnePlus 5 ROM available (no "T")
Mentioned EDL procedure works and OS is booting BUT neither Touchscreen nor USB OTG (for external mouse support) is working --> So I can't navigate and allow Bootloader to be unlocked again
Unfortunately I'm now stuck and have no more idea how to unbrick my phone again
What would help:
Any source to MSM-Download-Tool packed with a correct ROM for the OnePlus 5T
A Workaround to just flash TWRP via MSM-Download-Tool or Qualcomm's QFIL application in EDL mode
Some "hack" to bypass the locked Bootloader situation
Every appreciated Input you might have that I'm currently not aware of...
So PLEASE let me know of any approach that I could try or if you might have found a link or something else to a solution that might help me out of this disaster...
Many thanks in advance!
Tryouts due to your feedback:
@dreinulldrei - "fastboot boot recovery.img" tried with the original 5T Recovery.img also with blu_spark TWRP --> no luck...
SOLVED SOLUTION:
As the EDL factory flash ROM is currently not (or will never officially be) available public getting in contact with the OnePlus support team is required.
They have such a recovery tool (MSM-Download-Tool) with an appropriate ROM and are able to flash the device during a remote support session conducted via chat.
So by starting a chat on the OnePlus Support page and describing your situation will lead to scheduled time slot where a Level-2 technician will do all required steps remotely.
(All files are password protected and the technician ensures they are deleted at the end of the session so I'm unfortunately not able to provide the sources for DIY purposes...)

Following. I would think there would be some way to flash some sort of signed image via fastboot...

U flashed a 5 os to it, using the msmtool try to extract those files from 5t os, I will do it when I get home and so u can try it, i can't guarantee anything though, would u like me to do that for u

Bradl79 said:
U flashed a 5 os to it, using the msmtool try to extract those files from 5t os, I will do it when I get home and so u can try it, i can't guarantee anything though, would u like me to do that for u
Click to expand...
Click to collapse
Thanks for your input - I'm really not aware of how to generate such *.ops ROM files as this is what the MSM Tool expects...
But if there is a way and you are able to extract and produce a MSM flashable file I would be very happy to try!

I would recommend trying to boot a OP5T recovery, you might have flashed some OP5 rom including OP5 recovery. Just go into fastboot (power on with volume up pressed down), then via cmd:
fastboot boot recovery.img
Since OP does not offer the recovery to be downloaded, it will need to be downloaded from a working device. Lacking the cable right where I am, but I am sure someone else can help out.

crakerjac said:
Following. I would think there would be some way to flash some sort of signed image via fastboot...
Click to expand...
Click to collapse
Thanks for the input - I forgot to mention I also tried the 2 original available OP5T "full" ZIP ROM's (think they should be signed...)
Will add this to the initial Post but I assume also no chance here...

dreinulldrei said:
I would recommend trying to boot a OP5T recovery, you might have flashed some OP5 rom including OP5 recovery. Just go into fastboot (power on with volume up pressed down), then via cmd:
fastboot boot recovery.img
Since OP does not offer the recovery to be downloaded, it will need to be downloaded from a working device. Lacking the cable right where I am, but I am sure someone else can help out.
Click to expand...
Click to collapse
Ohhh good point - I also think there is the "wrong" recovery (from 5) currently on my phone (because also there the touchscreen behaves unexpectedly...)
But unfortunately with your command I get the "Your device is corrupted. It can't be trusted and will not boot" message.
Tried this with the original 5T Recovery.img I managed to obtain and also with the blu_spark TWRP - no luck...

Edit: Ignore, misread previous post.

U may have to make a call to oneplus so they can restore for u

Submit a ticket to One Plus
You are going to have to submit a ticket, they will arrange a time to help you by unbricking the phone remotely.
I just had to do this myself this week, and it got done today.
I do have the 5t unbricking files but I cannot access the archive because it's password protected.

One important this you didn't mention is how this happened.

OnePlus may be able to help with this one, but all root guides explicitly include the phrase "at your own risk."

blackknightavalon said:
OnePlus may be able to help with this one, but all root guides explicitly include the phrase "at your own risk."
Click to expand...
Click to collapse
Bradl79 said:
U may have to make a call to oneplus so they can restore for u
Click to expand...
Click to collapse
WMerkens said:
You are going to have to submit a ticket, they will arrange a time to help you by unbricking the phone remotely.
I just had to do this myself this week, and it got done today.
I do have the 5t unbricking files but I cannot access the archive because it's password protected.
Click to expand...
Click to collapse
Thanks for all your advice - so I will arrange a support chat/ticket as soon as possible and inform about the result in this thread.
Didn't thought that OnePlus Support Team would even care about such bricks (no warranty / own risk / "playing" with root / etc...)
But as indeed they seem to help like @WMerkens experienced I would be very happy to have a working device again

CodeXter said:
Thanks for all your advice - so I will arrange a support chat/ticket as soon as possible and inform about the result in this thread.
Didn't thought that OnePlus Support Team would even care about such bricks (no warranty / own risk / "playing" with root / etc...)
But as indeed they seem to help like @WMerkens experienced I would be very happy to have a working device again
Click to expand...
Click to collapse
don't know why you would think that OP wouldn't help...they have said from day one that unlocking/rooting does not void your warranty. Heck they encourage it. I assume you are the same person on the OP forum w/ this problem. Hopefully after you get this resolved you will have learned to NEVER EVER RELOCK your phone unless you do the whole factory image qualcomm recovery tool bit. and experienced OP folks on this forum know any claims of a "hardbricked" OP phone is ALWAYS not true.

Yeah oneplus used to be good about and does a remote session to restore, this was back in the one plus one days though, but I think they still do it
---------- Post added at 03:25 AM ---------- Previous post was at 02:54 AM ----------
WMerkens said:
You are going to have to submit a ticket, they will arrange a time to help you by unbricking the phone remotely.
I just had to do this myself this week, and it got done today.
I do have the 5t unbricking files but I cannot access the archive because it's password protected.
Click to expand...
Click to collapse
Awwww I wish we could get them, do they use the msmtool too?

How I bricked a 5t
I got the phone and I had installed twrp, that went fine. I was looking at magick systemless rooter when the phone then kicked in with a OTA update, I chose to ignore it the first time. It occurred again a few minutes and in my haste I let it do it's job but it did not complete correctly. I rebooted and the phone complained about corruption to the OS, I got in again but made the dumb mistake of re enabling the OEM lock and because I thought that might be causing the problem. I rebooted again but now I could not boot any more into the OS, it complained I was corrupted and go to google to see what to do.
So I was left with a bricked phone.
I could do bootloader but not recovery and I could not unlock the bootloader.
I could not get in via adb usb debug, So after much research I download the OnePlus 5 unbricking pack and learned a whole lot about qualicom and EDL mode, plus I learned a lot about the QFIL tools and restoring a phone. I did the 5 unbrick but my screen ended up upside down but the touch was right side up, which resulted in a very hard to use phone.
I tried the QFIL method but I was missing a mdb file to be able to talk to the phone.
So I gave up submitted a ticket and after much bad co-ordination on their part got a level 2 tech to debrick the phone remotely.
They do a reverse VPN and connect to your computer, they tell you to have 2 files archive ready in a folder on your desktop (they supply the links). They install the EDL driver and unpack the debrick archive. The archives are password protected, they run the tool and restore the phone
back to factory.
They erase the unpacked archives after they are done.

jerrywmilton said:
don't know why you would think that OP wouldn't help...they have said from day one that unlocking/rooting does not void your warranty. Heck they encourage it. I assume you are the same person on the OP forum w/ this problem. Hopefully after you get this resolved you will have learned to NEVER EVER RELOCK your phone unless you do the whole factory image qualcomm recovery tool bit. and experienced OP folks on this forum know any claims of a "hardbricked" OP phone is ALWAYS not true.
Click to expand...
Click to collapse
Oh yes I've learned my lesson on this :angel: --> Never ever set OEM to be unlocked to NO again
Obviously I do not exactly know what wrong procedure made me stuck in this situation but I just wanted to revert every single step back one by one to see which element brings me back to a valid SafetyNet situation...
I've been with the OnePlus "family" since the OP1 but never needed any direct support from the vendor - so every time there's a first time and so for me now...
Thus I really didn't know OP staff is actively doing remote support for their devices - but thumbs up for that! :good:
(BTW: I'm not the guy from the OP forum)

Bradl79 said:
Yeah oneplus used to be good about and does a remote session to restore, this was back in the one plus one days though, but I think they still do it
---------- Post added at 03:25 AM ---------- Previous post was at 02:54 AM ----------
Awwww I wish we could get them, do they use the msmtool too?
Click to expand...
Click to collapse
Yes basically it's the same archive as the 5 unbrick pack but it's for 5t, OnePlus 5T OxygenOS 4.7.2-171116.zip is the archive and you can look in it and you see the ops file is for dumpling not cheesburger, which is the code name for 5t. I saw the MsmDownloadTool is 4.0.8

Bradl79 said:
Yeah oneplus used to be good about and does a remote session to restore, this was back in the one plus one days though, but I think they still do it
---------- Post added at 03:25 AM ---------- Previous post was at 02:54 AM ----------
Awwww I wish we could get them, do they use the msmtool too?
Click to expand...
Click to collapse
I just had a chat with them before and got mailed a link to the MSMTool incl. ROM for the OP5T (dumpling)
But unfortunatley support files from OnePlus are password protected Nevertheless here the original vendor link:
https://onepluscn-my.sharepoint.com/personal/sheva_liu_oneplus_net/_layouts/15/guestaccess.aspx?docid=0fde9596c72744b4fb9c073ca5d87edbe&authkey=AQPXKRi7pdIzZX-5WH_pwWg&e=1030aa0046da4d1aa9189020027d9c93
So I have to wait for my remote support schedule on Saturday to have the L2 technician entering the password and do the rest.
Would be able to do this myself but OnePlus obviously wants to protect their sources what I have to accept, respect and be patient for...

So, never turn off the OEM Unlocking?

k10 2017 no fastboot

hi I have a LG k10 2017 that has a problem, does not start in fastboot, and even in recovery and then go fastboot, how do I start in fastboot?

XRed_CubeX said:
hi I have a LG k10 2017 that has a problem, does not start in fastboot, and even in recovery and then go fastboot, how do I start in fastboot?
Click to expand...
Click to collapse
I have the same issue with the same phone, I tried everything, I can't root my phone. Looks like LG "blocked" fastboot in some models, unless someone knows a way to remove it, I guess we're stuck.

Klinsk said:
I have the same issue with the same phone, I tried everything, I can't root my phone. Looks like LG "blocked" fastboot in some models, unless someone knows a way to remove it, I guess we're stuck.
Click to expand...
Click to collapse
It is said that to activate the fastboot you must format the partition LAF, you would say: "impossible, there are no methods" but there is an explot called LGLAF, I do not know how to use it, format the partition LAF involves the loss of the Download mode and unlocking the fastboot, one method is to make a backup of the LAF partition, go into fastboot, unlock, do all the things you need to do and then restore the partition. As soon as I know how to use it, maybe I write it in this thread.

Thanks man.

Failed experiment.

XRed_CubeX said:
Failed experiment.
Click to expand...
Click to collapse
https://forum.xda-developers.com/lg-k10/help/nuked-laf-download-mode-fastboot-t3898626 For informations.

XRed_CubeX said:
hi I have a LG k10 2017 that has a problem, does not start in fastboot, and even in recovery and then go fastboot, how do I start in fastboot?
Click to expand...
Click to collapse
I also have the same problem friends and I am very sad.
---------- Post added at 12:20 AM ---------- Previous post was at 12:17 AM ----------
[/COLOR]
XRed_CubeX said:
https://forum.xda-developers.com/lg-k10/help/nuked-laf-download-mode-fastboot-t3898626 For informations.
Click to expand...
Click to collapse
What a sad hand, I sincerely hope that you can resolve this as soon as possible.

Questions about developpement

Hello there !
I got the RN8Pro, last week and i unlocked it today. I naturally started to look how to root/install TWRP. I found numerous threads with instructions on how to do it but i also found a lot of warnings that it may brick the device, and that if that happens i need a special account to be able to unbrick it. It seems that some methods will work for the Chinese version while bricking others and vice versa. I have the Global ROM version 11.0.3.0(PGGEUXM) and the model of my phone is M1906G7G. Do you think it's safe for me to try flashing TWRP or at least root through ADB ?
I have also searched for custom ROMs and did not find any. The phone is relatively new so i wouldn't mind if i had to wait a bit, but i have also read that people just don't want to develop for it because of the Mediatek chip. Everyone says that development is not possible because there is no source code the the Mediatek chip. But here it says that the sources have been released partially here and the rest here. Is there something that's missing from these repos that makes development impossible ?
I also would like to become more than just a user and learn how to make custom roms. I found this thread that compiles some guides but a lot of them seem a bit outdated and I'm lost. Is that a good starting point or i should i go elsewhere ?
Thanks ^^

TheBolshe said:
Hello there !
I got the RN8Pro, last week and i unlocked it today. I naturally started to look how to root/install TWRP. I found numerous threads with instructions on how to do it but i also found a lot of warnings that it may brick the device, and that if that happens i need a special account to be able to unbrick it. It seems that some methods will work for the Chinese version while bricking others and vice versa. I have the Global ROM version 11.0.3.0(PGGEUXM) and the model of my phone is M1906G7G. Do you think it's safe for me to try flashing TWRP or at least root through ADB ?
I have also searched for custom ROMs and did not find any. The phone is relatively new so i wouldn't mind if i had to wait a bit, but i have also read that people just don't want to develop for it because of the Mediatek chip. Everyone says that development is not possible because there is no source code the the Mediatek chip. But here it says that the sources have been released partially here and the rest here. Is there something that's missing from these repos that makes development impossible ?
I also would like to become more than just a user and learn how to make custom roms. I found this thread that compiles some guides but a lot of them seem a bit outdated and I'm lost. Is that a good starting point or i should i go elsewhere ?
Thanks ^^
Click to expand...
Click to collapse
Can't you look at guides section we need Testers for POSP :crying:

girishjangir7 said:
Can't you look at guides section we need Testers for POSP :crying:
Click to expand...
Click to collapse
I did, but what is said there doesn't apply to me. I don't live near a center and I bought it on AliExpress, so I don't tink that I have a guarantee that I could use.

TheBolshe said:
I did, but what is said there doesn't apply to me. I don't live near a center and I bought it on AliExpress, so I don't tink that I have a guarantee that I could use.
Click to expand...
Click to collapse
No problem then wait for someone to test:laugh:

TheBolshe said:
I did, but what is said there doesn't apply to me. I don't live near a center and I bought it on AliExpress, so I don't tink that I have a guarantee that I could use.
Click to expand...
Click to collapse
I would love to help though. But your post is quite cryptic. More details could be nice like what are the risks, what is need to be done, what to do in case of a problem. Plus, it's my only phone ATM and I am poor ^^

It Is Safe As Well As Not Safe.
I Had Bricked My Redmi Note 8 Pro(8GB) And I Had To Visit Mi Service Centre As I Required Xiaomi Authorised Account Which I Don't Have.
Some Peoples Bricked Their Phone After Flashing TWRP And Some After Flashing Wrong Boot.img
I Flashed TWRP Successfully But When I Rooted My Phone, I Faced Bootloop Problem Then To Solve That Problem I Accidently Flashed Wrong Boot.img File( 10.0.4 Boot File Into 11.0.3) Which Resulted Into Bootloop
But If You Follow All The Steps Carefully Then It Is Absolutely Safe.

Hemant Singh Rajput said:
I Had Bricked My Redmi Note 8 Pro(8GB) And I Had To Visit Mi Service Centre As I Required Xiaomi Authorised Account Which I Don't Have.
Some Peoples Bricked Their Phone After Flashing TWRP And Some After Flashing Wrong Boot.img
I Flashed TWRP Successfully But When I Rooted My Phone, I Faced Bootloop Problem Then To Solve That Problem I Accidently Flashed Wrong Boot.img File( 10.0.4 Boot File Into 11.0.3) Which Resulted Into Bootloop
But If You Follow All The Steps Carefully Then It Is Absolutely Safe.
Click to expand...
Click to collapse
Mine has 6gb ram. Which TWRP img did you use?
When it's in bootloop, all I need to do is hold power up to get to fastboot so I can flash boot.img right?

TheBolshe said:
Mine has 6gb ram. Which TWRP img did you use?
When it's in bootloop, all I need to do is hold power up to get to fastboot so I can flash boot.img right?
Click to expand...
Click to collapse
I Flashed This TWRP Through CMD
https://forum.xda-developers.com/re...overy-unofficial-twrp-recovery-redmi-t4002397
You Need To Press&Hold Power+Vol Down Button To Enter Into Fastboot Mode.
When TWRP Flashed Successfully Through CMD You Have To Immediately Disconnect Your Phone From PC Otherwise Your Phone Will Load Stock Recovery.
---------- Post added at 12:45 PM ---------- Previous post was at 12:42 PM ----------
TheBolshe said:
Mine has 6gb ram. Which TWRP img did you use?
When it's in bootloop, all I need to do is hold power up to get to fastboot so I can flash boot.img right?
Click to expand...
Click to collapse
I Think You Shouldn't Take Risk As Your Phone Has No Warranty

Question Fastbook flashing unlock not recognized?

Hi guys, I'm stucked at this weird problem, basically when I type that command, fastboot reply with the list of options, like the command itself doesn't exist. Funny things is, to confirm it should work, I've tried to launch it with the device connected but not in fastboot, and it says "waiting for device" so the command actual exists.
I've tried so far: dl the last adb sdb from the official page
put the phone through fastboot using adb fastboot devices (it works)
launch the command: nothing works
This is hmm my 4th? Oneplus, so isn't like I'm new to unlock bootloaders but now I'm stucked, any ideas?
Of course OEM debug is on and also OEM unlock
ps.: I've also tried the old command but no resuts

here is the proper fastboot stuff you need. https://www.mediafire.com/file/xy5ifa0k1bz7tn4/fastboot.7z/file
with this one, fastboot flashing unlock

MrSteelX said:
here is the proper fastboot stuff you need. https://www.mediafire.com/file/xy5ifa0k1bz7tn4/fastboot.7z/file
with this one, fastboot flashing unlock
Click to expand...
Click to collapse
Ty, I've done it properly but sadly, I'm in the loop now, because following the guide to unlock:
because of the mismatch of the step 3 (which stated correctly I guess, "init_boot", and the pic, I've wrote boot instead of init_boot and flashed the patched magisk file to the boot.
Do you know/have where find the correct boot file to patch it back? My model is the CPH2449 A09 BA (europe) for what I remember...
Or, what guide can I follow withouth worst the situation... For now, I can still enter in the fastboot mode

If you flash init_boot to boot, it will hard brick your device. If you can't access fastboot now, then only way to recover is using MSM tool.

surajpai524 said:
If you flash init_boot to boot, it will hard brick your device. If you can't access fastboot now, then only way to recover is using MSM tool.
Click to expand...
Click to collapse
Yes I've noticed...someone helped me for 20 bucks from telegram so now its working...btw my mistake is due to the guide in the first post, as the pic there SHOWS to flash it to BOOT instead of INIT, please fix the guide and check it 200x times before post it wtf...

takui said:
Yes I've noticed...someone helped me for 20 bucks from telegram so now its working...btw my mistake is due to the guide in the first post, as the pic there SHOWS to flash it to BOOT instead of INIT, please fix the guide and check it 200x times before post it wtf...
Click to expand...
Click to collapse
I know.. That's why I used the other method to root. KernelSU method.
PROPER CPH2451 Root and Update instructions
This is for the CPH2451 Rom, but should also work for other roms. I have returned my device so I will not be updating this with future updates. I have validated these instructions work for CPH2451 NA version so it's your choice to follow it or...
forum.xda-developers.com

surajpai524 said:
I know.. That's why I used the other method to root. KernelSU method.
PROPER CPH2451 Root and Update instructions
This is for the CPH2451 Rom, but should also work for other roms. I have returned my device so I will not be updating this with future updates. I have validated these instructions work for CPH2451 NA version so it's your choice to follow it or...
forum.xda-developers.com
Click to expand...
Click to collapse
oh thanks for the link, ill check it after it finish to copy data from old one...this time it needs 1 hr (before 5 mins...lucky, without reason)... it worked for u then? Ok!

takui said:
oh thanks for the link, ill check it after it finish to copy data from old one...this time it needs 1 hr (before 5 mins...lucky, without reason)... it worked for u then? Ok!
Click to expand...
Click to collapse
Yes.. this method just needs booting and no hard flash. Also unlock bootloader and try setting passcode or patern before you copy data. If you can't set pattern, then relock and unlock bootloader till possible.

surajpai524 said:
Yes.. this method just needs booting and no hard flash. Also unlock bootloader and try setting passcode or patern before you copy data. If you can't set pattern, then relock and unlock bootloader till possible.
Click to expand...
Click to collapse
hey, did you perhaps found a way to fix fingerprint/passwords not working too? I guess that it is broken because I had one before unlocking it...so maybe locking it back, removing old one (if works) and unocking again, could work but...I'm still trying to figure out how to lock it back...maybe with enhanced tools... any ideas? Maybe I'm overthinking?

takui said:
hey, did you perhaps found a way to fix fingerprint/passwords not working too? I guess that it is broken because I had one before unlocking it...so maybe locking it back, removing old one (if works) and unocking again, could work but...I'm still trying to figure out how to lock it back...maybe with enhanced tools... any ideas? Maybe I'm overthinking?
Click to expand...
Click to collapse
Only is to fix phone lock issue is by relocking bootloader and unlocking it till it works. This must be done only if not rooted. No other method was found till now.

I've tried at least 5+ times, nothing. I've read first we need to flash stock then lock again, but idk how to flash stock frankly....now desperately I'm flashing it through enhanced fastboot tool, even if a guide said to avoid cuz some op10R got bricked... let's see....