Develop Bugs

Help required with bricked Oneplus 3

Hi,
I have installed MIUI in my OP3 this morning, which was working fine. There was an OTA update, after installing it, device rebooted and entered into recovery mode and it was hanging there for more than an hour. Whrn I tried to reboot, it was off and never came up. Tried unbrick using MSM Download Tool and then I am able to get into boot loader screen. From there I have tried to flash TWRP, but if I reboot, I am getting this message only. Currently I have access to bootloader, if I flash TWRP and choose to boot from recovery (from pc), I have access to OTG also. But even after flashing a ROM, If I reboot, I am getting attached screen only.
I have access to TWRP, only when I chiose to reboot from All in one tool from PC.
Please help me.

you have to use method 2of unbrick not method1.it will flash whole stock rom , then reboot enable developer options etc then flash twrp recovery then go ahead.

Use Method 2. Make sure to follow all steps. Please do quote me otherwise i do not know if you need any further help.

You flashed oficial beta update on mui rom and you have a mess.
Download official OP 4.1.6 rom and try to flash it.
if its not fixed the try wipe everythng (system data ect) and then flash the rom

Puddi_Puddin said:
Use Method 2. Make sure to follow all steps. Please do quote me otherwise i do not know if you need any further help.
Click to expand...
Click to collapse
Hi,
I am following method 2 now. I have switched off the phone and connecting to laptop, as soon as I connect to laptop, it is getting into bootloop (without pressing any button). Phone is not detected in laptop.

colossus_r said:
You flashed oficial beta update on mui rom and you have a mess.
Download official OP 4.1.6 rom and try to flash it.
if its not fixed the try wipe everythng (system data ect) and then flash the rom
Click to expand...
Click to collapse
I have tried to by wiping everything and tried to restore from OTG pendrive. Tried to flash Firmware + Modem, tried to flash different ROM. Nothing helped.
I am in travel now, having limited internet connectivity. I will reach home and then try to download official OP as you suggested.
I do not have data in phone, all the data is already copied to laptop.

colossus_r said:
You flashed oficial beta update on mui rom and you have a mess.
Download official OP 4.1.6 rom and try to flash it.
if its not fixed the try wipe everythng (system data ect) and then flash the rom
Click to expand...
Click to collapse
Finally, method 2 worked. Thanks a lot.

nagurvidyasagar said:
Finally, method 2 worked. Thanks a lot.
Click to expand...
Click to collapse
I was having the same problem like you how did you solve it ?

Bootloop after Magisk img flash trying to root device.

Hello! So I have rooted a few devices before while looking at guides on this website. This time it did not work out very well. I am using a Moto Z2 Force from T-Mobile. When I followed this guide: https://forum.xda-developers.com/z2-force/how-to/how-to-root-moto-z2-force-t-mobile-t3672933 , I ended up locking up my phone in bootloop with the Tmobile logo. I have tried flashing back the backup I made and using a few different roms I found on this site. Some of the guides I tried to use to fix my phone were:
https://forum.xda-developers.com/z2-force/how-to/to-stock-roms-t3672859
https://forum.xda-developers.com/z2...m-stock-november-hybrid-rom-t-mobile-t3712795
https://forum.xda-developers.com/z2-force/development/how-to-install-oreo-ota-t3726932
None of them are working.
Bootloader is unlocked. After using the flashall from these links I had to unlock it again or I was stuck on a screen telling me "Your device is corrupt. It can't be trusted and will not boot". When it is locked it just goes between that quoted black screen and reboots itself every 10 or so seconds back into that screen. Once I unlock the bootloader, It quickly shows the white T-Mobile screen. Goes to a black screen that says "Your devices software can't be checked for corruption. Please lock the bootloader". It will let me pause on the screen if I click the power button or it will continue to the T-Mobile screen. On that screen it will vibrate for a half second and then after 5 seconds or so will restart.
At this current moment I have gotten it so I can get into the recovery mode screen. At some points in my adventure today that option would have a bootloop as well. I have tried "Wipe data/factory reset". But that puts me in a even shorter bootloop that does not even vibrate on the T-Mobile screen. It is just a quick flash of white, black, then white again.
Not sure what other information I can give. I am going to leave the phone where it is until someone replies to this.

Go into bootloader. Let us know the bootloader version. It should have a message in bootloader with the end looking like a date, that is what we need to know. It seems you're on Oreo by your symptoms. If so, flash the flash all in development section thread on "update to Oreo [T-Mobile]" nougat flash all's will not work if you're on the Oreo bootloader.
edit: https://drive.google.com/open?id=1CAFz1yIdnqE13ATSoYJKp2R17Q3bVo6A

Thank you so much. That flashall worked. I tried another one from Oreo but it did not work. Glad this one did.

Uzephi said:
Go into bootloader. Let us know the bootloader version. It should have a message in bootloader with the end looking like a date, that is what we need to know. It seems you're on Oreo by your symptoms. If so, flash the flash all in development section thread on "update to Oreo [T-Mobile]" nougat flash all's will not work if you're on the Oreo bootloader.
edit: https://drive.google.com/open?id=1CAFz1yIdnqE13ATSoYJKp2R17Q3bVo6A
Click to expand...
Click to collapse
I wasn't to know if the Oreo flash all skips the need for the magisk manager apk that nougat required.
And is twrp for Oreo like any other twrp from the past can you boot it from fastboot menu or power button combo and works ok? Not exactly getting the current working status of twrp for this device hence why I haven't flashed any recovery
Sent from my [device_name] using XDA-Developers Legacy app

androidddaaron said:
I wasn't to know if the Oreo flash all skips the need for the magisk manager apk that nougat required.
And is twrp for Oreo like any other twrp from the past can you boot it from fastboot menu or power button combo and works ok? Not exactly getting the current working status of twrp for this device hence why I haven't flashed any recovery
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
For Root, Magisk Manager will always be required. You need an app to manage root access to apps or things would be terribly insecure. After you update to Oreo, use the below TWRP, it works flawlessly. Credits to @joemossjr and @invisiblek for it.
https://drive.google.com/file/d/1nEp8EWDye3BE7p0yjugUWRw0-OkePCRz/view?usp=sharing

Uzephi said:
For Root, Magisk Manager will always be required. You need an app to manage root access to apps or things would be terribly insecure. After you update to Oreo, use the below TWRP, it works flawlessly. Credits to @joemossjr and @invisiblek for it.
https://drive.google.com/file/d/1nEp8EWDye3BE7p0yjugUWRw0-OkePCRz/view?usp=sharing
Click to expand...
Click to collapse
Link to the magisk manager needed by chance ? ... Or is it the same one from the nougat root thread?
And can you possibly be the 2nd one to confirm/acknowledge we indeed can edit build prop to enable MHL Mirracast on the z2 force ? So I heard ... I'm trying to mirror my z2 to my pioneer touch screen and it's got to be done via mhl adapter.
Some say Moto and Lenovo just blocked this but it still exists with simply editing a value in build prop ?
Sent from my [device_name] using XDA-Developers Legacy app

https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 for more information on magisk. Do not flash anything from the nougat thread. Oreo is different. download the 15.3.zip and flash it in TWRP. download Magisk Manager apk from the official thread and you'll be good to go.
Yes, a build.prop edit should make it work

Uzephi said:
For Root, Magisk Manager will always be required. You need an app to manage root access to apps or things would be terribly insecure. After you update to Oreo, use the below TWRP, it works flawlessly. Credits to @joemossjr and @invisiblek for it.
https://drive.google.com/file/d/1nEp8EWDye3BE7p0yjugUWRw0-OkePCRz/view?usp=sharing
Click to expand...
Click to collapse
Is this TWRP image bootable only or is it safe to flash/replace stock recovery?

Shiro12 said:
Is this TWRP image bootable only or is it safe to flash/replace stock recovery?
Click to expand...
Click to collapse
It is flashable

flashing Twrp V6 moto z2 force is this 100% functional
Uzephi said:
It is flashable
Click to expand...
Click to collapse
so OreoV6 twrp is 100% functional can flash it permanently and boot from fastboot recovery at any point? any other steps or flashing ? decryption neccesary after flashing twrp or is that an optional?

androidddaaron said:
so OreoV6 twrp is 100% functional can flash it permanently and boot from fastboot recovery at any point? any other steps or flashing ? decryption neccesary after flashing twrp or is that an optional?
Click to expand...
Click to collapse
Encryption works thanks to @invisiblek. Just "fastboot flash boot path/to/twrp" and you're golden.

Uzephi said:
Go into bootloader. Let us know the bootloader version. It should have a message in bootloader with the end looking like a date, that is what we need to know. It seems you're on Oreo by your symptoms. If so, flash the flash all in development section thread on "update to Oreo [T-Mobile]" nougat flash all's will not work if you're on the Oreo bootloader.
Click to expand...
Click to collapse
Same as Moto people did on old Griffin (Moto Z) with MM -》N...
Does Oreo works fine on Nougat BL?
(On Griffin you could use fine N on MM BL...)

I too got a bootloop after unlocking the bootloader, installing TWRP, and then Magisk from the TWRP forum. I got it back working after formatting data again luckily. I am on 3.1 right now, do I need to update to 3.2 before flashing Magisk? I'm on 7.1 now, BL: MBM-3.0-nash_tmo-e7b4c60-171017
Thanks for any help, its been many years since I had an upgrade, been stuck on the S6 for a while and glad to get back in the game

guys i tried blank flash oreo on mine bricked tmobile moto z2 force and it isnt working, any help would be great on this , thanks.. and also i have tried many blank flashes some for even other moto phone models none worked so far.. one or two of them got really close the oreo one did but failed at last part... tried about hundred times and yes i even tried holding down power and volume button with no success it didnt work it did though recognize the phone but still failed trying to boot or flash it though... seems to me it needs either up to date or just different blank flash it seems, but i dont know that for sure...

Did the new flashall 27.1.3 work if not I may can help

"Fingerprint Hardware Not Available" and missing WiFi

Yesterday I updated my Magisk to 15.3 and also decided that I wanted to flash a new Kernel too, so I did with The Flash. Once everything booted back up, when I try to unlock my phone I get the message at the bottom of my screen saying "Fingerprint Hardware Not Available" and then once I just unlock with my pattern, WiFi won't turn on, I can click and click and it just stays greyed out. I read somewhere that flashing to the Stock+Safetynet Kernel that it could fix those problem, but it didn't for me. Would anyone know of any other solutions other than Factory reset? Thanks in advance.

absoluthamm said:
Yesterday I updated my Magisk to 15.3 and also decided that I wanted to flash a new Kernel too, so I did with The Flash. Once everything booted back up, when I try to unlock my phone I get the message at the bottom of my screen saying "Fingerprint Hardware Not Available" and then once I just unlock with my pattern, WiFi won't turn on, I can click and click and it just stays greyed out. I read somewhere that flashing to the Stock+Safetynet Kernel that it could fix those problem, but it didn't for me. Would anyone know of any other solutions other than Factory reset? Thanks in advance.
Click to expand...
Click to collapse
Fastboot the stock boot.img and see if it boots up normally without the warning. That's pretty strange behavior after flashing the Flash kernel. Kindly post your installation method when you can :good:

Badger50 said:
Fastboot the stock boot.img and see if it boots up normally without the warning. That's pretty strange behavior after flashing the Flash kernel. Kindly post your installation method when you can :good:
Click to expand...
Click to collapse
When I get a chance I'll download the stock image and try fastbooting it.
As far as my install method, I flashed the kernel via TWRP, then flashed Magisk, then rebooted.
Thanks!

absoluthamm said:
When I get a chance I'll download the stock image and try fastbooting it.
As far as my install method, I flashed the kernel via TWRP, then flashed Magisk, then rebooted.
Thanks!
Click to expand...
Click to collapse
Just for the heck of it, if you want to try, go back to TWRP and flash...
Flash kernel
The twrp.zip
Then reboot back into TWRP and flash the magisk zip. Then we'll see if that fixes it.

Badger50 said:
Just for the heck of it, if you want to try, go back to TWRP and flash...
Flash kernel
The twrp.zip
Then reboot back into TWRP and flash the magisk zip. Then we'll see if that fixes it.
Click to expand...
Click to collapse
Haven't had a chance to download the stock boot.img yet, but I did try your suggestion here and the same result happens, no fingerprint, no wifi.

absoluthamm said:
Haven't had a chance to download the stock boot.img yet, but I did try your suggestion here and the same result happens, no fingerprint, no wifi.
Click to expand...
Click to collapse
Darn! Oh well, if your still having trouble after you fastboot the stock boot.img, you may have to dirty flash the factory image. If that doesn't work, then a factory reset or a clean flash of the factory image might be needed. If that doesn't work, then you may have to run it in safe mode for a while. Finally, if that doesn't work, your hardware/software may be hosed and RMA here you come. Lets hope it's not that serious

This happened to me on the Pixel 2 when updating to the January image, I had do a full image wipe in order to fix it.

bro i am worried i wiped data cache vendor and flashed RR rom now the sim is not inserting and wifi bluetooth fingerprint music everything is not working ..what should i do

[solved] help!!!

I installed Lineage OS 17.1 and when I turn on my phone he asks me for a password but I've never had

FranGAMER321 said:
I installed Lineage OS 17.1 and when I turn on my phone he asks me for a password but I've never had
Click to expand...
Click to collapse
Funny, i had the same problem yesterday, was told i should wipe the decryption on the phone in twrp, i lost my IMEI and can't flash roms anymore, be carefull.

maserati2011 said:
Funny, i had the same problem yesterday, was told i should wipe the decryption on the phone in twrp, i lost my IMEI and can't flash roms anymore, be carefull.
Click to expand...
Click to collapse
In TWRP to skip the password requirement I touched cancel and touched wipe (without a custom wipe), and after doing so I made an error, but after trying a couple of hours later the same thing came out, until I tried 3 more times in a row and he left me, after that I could finally use LineageOS 17.1

maserati2011 said:
Funny, i had the same problem yesterday, was told i should wipe the decryption on the phone in twrp, i lost my IMEI and can't flash roms anymore, be carefull.
Click to expand...
Click to collapse
Your loss of imei had nothing to do with formatting data and more to do with flashing rom
Make sure you're on oero firmware & reflash that firmware fully via fastboot
Flash a custom rom that gives you imei (you will have to try them - try the oero twrp flashable stock rom too) and then back up efs so you can restore it if problem happens again
---------- Post added at 02:05 PM ---------- Previous post was at 02:03 PM ----------
FranGAMER321 said:
I installed Lineage OS 17.1 and when I turn on my phone he asks me for a password but I've never had
Click to expand...
Click to collapse
You need to format data
TWRP - wipe - format data (option on the right)
Reboot to recovery & flash rom again
Or in fastboot do
fastboot erase userdata
Either way backup anything on internal storage (pics docs music etc) first as this will be deleted

TheFixItMan said:
Your loss of imei had nothing to do with formatting data and more to do with flashing rom
Make sure you're on oero firmware & reflash that firmware fully via fastboot
Flash a custom rom that gives you imei (you will have to try them - try the oero twrp flashable stock rom too) and then back up efs so you can restore it if problem happens again
Click to expand...
Click to collapse
would you be kind enough to help me through it on messenger?

TheFixItMan said:
Your loss of imei had nothing to do with formatting data and more to do with flashing rom
Make sure you're on oero firmware & reflash that firmware fully via fastboot
Flash a custom rom that gives you imei (you will have to try them - try the oero twrp flashable stock rom too) and then back up efs so you can restore it if problem happens again
Click to expand...
Click to collapse
I managed to re flash the stock Oreo 8.1 firmware through Lenovo Moto Smart Assistant hoping to get the IMEI back and automatically re-lock the boot-loader but neither happened, still no IMEI and Boot-loader is still unlocked, what to do now?

maserati2011 said:
I managed to re flash the stock Oreo 8.1 firmware through Lenovo Moto Smart Assistant hoping to get the IMEI back and automatically re-lock the boot-loader but neither happened, still no IMEI and Boot-loader is still unlocked, what to do now?
Click to expand...
Click to collapse
If running
fastboot erase modemst1
fastboot erase modemst2
Doesn't bring your imei back like I said - try different custom roms (especially the last where imei worked)
Else you will need a motherboard replacement if you can't work out a way to restore it
And never re-lock the bootloader 'if you hard brick your device again due to ota update because the firmware you flashed was wrong you will never be able to re-flash the device

TheFixItMan said:
If running
fastboot erase modemst1
fastboot erase modemst2
Doesn't bring your imei back like I said - try different custom roms (especially the last where imei worked)
Else you will need a motherboard replacement if you can't work out a way to restore it
And never re-lock the bootloader 'if you hard brick your device again due to ota update because the firmware you flashed was wrong you will never be able to re-flash the device
Click to expand...
Click to collapse
So basically your advice is to find a stable custom rom where the IMEI shows and just stick with it correct?

maserati2011 said:
So basically your advice is to find a stable custom rom where the IMEI shows and just stick with it correct?
Click to expand...
Click to collapse
Please read my past responses carefully
I said once you have found a custom rom that gives you imei you can then back up efs partition using a 64bit twrp to restore it if you loose it in future (or using other roms)

Question POCO F3 bricked

Hey, I just unlocked my bootloader after waiting for the 7 days today I wanted to install the MIUI EU, and i follow the steps that they have on their website, installed and boot into recovery mode TWRP format data, and install the ROM that i downloaded, after that the wipe on the cache. When i rebooted my phone he didn't boot and was stuck on POCO screen. After 1 hour it was stuck on that, I decided to try and flash stock firmware with miflash tool, did the steps and after 604 seconds it shows success on the result but it doesn't boot the same thing stuck on POCO screen.

You need to Format data. Not cache.
Then the phone will boot up just fine.
Go, do it again.

Try to flash it using miflash again.
Then Boot TWRP, then flash it again + ( FORMAT DATA)

laid1995 said:
Boot TWRP, then install it again.
Click to expand...
Click to collapse
I'm facing the issue that I cannot access the internal storage to flash the ROM now or paste it again

Don't freak out. Your phone is fine. As long as you can boot into Fastboot. Then you are fine.

skullgnik said:
I'm facing the issue that I cannot access the internal storage to flash the ROM now or paste it again
Click to expand...
Click to collapse
Try otg.

laid1995 said:
Try otg.
Click to expand...
Click to collapse
otg? sorry, I'm kinda new to this situation. I've flashed many custom ROMs before but have never had an issue. Yes, my phone can boot into Fastboot without a problem. Right now I'm downloading a different version of the stock firmware (IDK i think it could fix the not booting problem after the miflash tool) if it works i will leave it with the stock firmware if not i will try to find a solution to fix the issue of not accessing the internal storage on twrp

skullgnik said:
otg? sorry, I'm kinda new to this situation. I've flashed many custom ROMs before but have never had an issue. Yes, my phone can boot into Fastboot without a problem. Right now I'm downloading a different version of the stock firmware (IDK i think it could fix the not booting problem after the miflash tool) if it works i will leave it with the stock firmware if not i will try to find a solution to fix the issue of not accessing the internal storage on twrp
Click to expand...
Click to collapse
I had the same issue before. Just reflash the stock (be aware, don't select "Wipe data and lock")
When the phone boots up. Flash twrp or just boot it. Then flash Xiaomi EU then FORMAT DATA.
Everything will be just fine.

laid1995 said:
I had the same issue before. Just reflash the stock (be aware, don't select "Wipe data and lock")
When the phone boots up. Flash twrp or just boot it. Then flash Xiaomi EU then FORMAT DATA.
Everything will be just fine.
Click to expand...
Click to collapse
What option should I select then?

skullgnik said:
What option should I select then?
Click to expand...
Click to collapse
Please tell me you didn't select " wipe and lock " before !

i did
laid1995 said:
Please tell me you didn't select " wipe and lock " before
Click to expand...
Click to collapse

skullgnik said:
i did
Click to expand...
Click to collapse
welp...... Try unlocking the bootloader again

Do as he says. Hopefully it gets unlocked.

laid1995 said:
Do as he says. Hopefully it gets unlocked.
Click to expand...
Click to collapse
I already booted with another stock firmware, i just re-downloaded and it worked guess for now i will stick with the stock one. Thank you both for the help!

You're welcome.
As you wish, just try, at least to unlock bootloader since you're still fresh. As to make sure that it can be unlocked.

skullgnik said:
I already booted with another stock firmware, i just re-downloaded and it worked guess for now i will stick with the stock one. Thank you both for the help!
Click to expand...
Click to collapse
you don't have to use memeui, official EvolutionX just released today!

JustAnAverageGuy_19 said:
you don't have to use memeui, official EvolutionX just released today!
Click to expand...
Click to collapse
I will think later this day about installing a custom ROM. but I don't hate miui as much as people usually hate, I find some things extremely useful I just don't like some UI esthetics i prefer the minimalist look of pure android. But some things like the cloning apps are very handy to me. Some bugs that are present atm on custom ROMs for this device like the double-tap to wake up are very negative to me because I have always used that feature since 2014 and I'm extremely used to it.