Develop Bugs

Failed to flash

Hey there,
I want to switch to these htt ps://download .lineageos. org/oneplus2 LOS 14.1 builds as I'm currently using LOS 14.1 by daktak. (Sorry, not allowed to post links right now..)
There haven't been any updates for almost 3 weeks now and I don't think that this will be updated any further.
Well, simply booting into recovery mode and flashing the newest LOS zip doesn't work for me. I guess it's because I'm not wiping my system partition, just data + dalvik cache... I thought I can simply switch/update from an older version of LOS? Do I really need to wipe everything again so I can install the LOS builds I've mentioned above?
Also I don't really understand the difference between signed and unsigned zips. The zip I want to flash is signed. Is this why I get "Failed to flash" as an error message in recovery? Does "signed" mean, I need to root my OP2 again and my current root will be removed?
Current LOS version 14.1-20170213-UNOFFICIAL-oneplus2 by daktak

Yakumichan said:
Hey there,
I want to switch to these htt ps://download .lineageos. org/oneplus2 LOS 14.1 builds as I'm currently using LOS 14.1 by daktak. (Sorry, not allowed to post links right now..)
There haven't been any updates for almost 3 weeks now and I don't think that this will be updated any further.
Well, simply booting into recovery mode and flashing the newest LOS zip doesn't work for me. I guess it's because I'm not wiping my system partition, just data + dalvik cache... I thought I can simply switch/update from an older version of LOS? Do I really need to wipe everything again so I can install the LOS builds I've mentioned above?
Also I don't really understand the difference between signed and unsigned zips. The zip I want to flash is signed. Is this why I get "Failed to flash" as an error message in recovery? Does "signed" mean, I need to root my OP2 again and my current root will be removed?
Current LOS version 14.1-20170213-UNOFFICIAL-oneplus2 by daktak
Click to expand...
Click to collapse
It is all explained here:
http://lineageos.org/Update-and-Build-Prep/

jhedfors said:
It is all explained here:
http://lineageos.org/Update-and-Build-Prep/
Click to expand...
Click to collapse
Thank you for your quick reply! After some issues using adb I could not fix (but I don't need to as I already did this somehow earlier for CM13) I managed to install LOS14.1 HYPE!
Maybe you could help me with my problem?
"No command 'fastboot' found"... But I can find my phone using adb devices.
Screenshot attached...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Yakumichan said:
Thank you for your quick reply! After some issues using adb I could not fix (but I don't need to as I already did dis somehow earlier for CM13) I managed to install LOS14.1 HYPE!
Maybe you could help me with my problem?
"No command 'fastboot' found"... But I can find my phone using adb devices.
Screenshot attached...
Click to expand...
Click to collapse
I am not an expert on adb/fastboot, but is the fastboot binary in the directory? It is also a little difficult to interpret the language in your sceenshot.

jhedfors said:
I am not an expert on adb/fastboot, but is the fastboot binary in the directory? It is also a little difficult to interpret the language in your sceenshot.
Click to expand...
Click to collapse
Right, sorry. It's German and it says that the command "fastboot" either has been written wrong or hasn't been found.
And also: Yes, it is:

I think you need to check your drivers
The device should be connected via adb interface driver or android driver
After that you should be able to see ur device

One plus 5t root issue on new phone that son has buggered up!

Hello, my 17 year old got the new one plus 5t yesterday,
He rooted the phone but then realised he couldn’t use certain apps with it rooted, so he uninstalled magisk
He rebooted the phone but it only went into custom recovery and wouldn’t load an OS
Because that didn’t work, he tried flashing an OTA update.
Now his phone is stuck on an upside down screen and a fuzzy section on it.
I know ZERO about android phones.
Should I wait for the support to open at one plus? Or is there something I can do to fix this?

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
brickedmum said:
Hello, my 17 year old got the new one plus 5t yesterday,
He rooted the phone but then realised he couldn’t use certain apps with it rooted, so he uninstalled magisk
He rebooted the phone but it only went into custom recovery and wouldn’t load an OS
Because that didn’t work, he tried flashing an OTA update.
Now his phone is stuck on an upside down screen and a fuzzy section on it.
I know ZERO about android phones.
Should I wait for the support to open at one plus? Or is there something I can do to fix this?
Click to expand...
Click to collapse

tell him to download this (full firmware)
https://otafsg.h2os.com/patch/amazo...xygen_43_OTA_011_all_1804241056_afd261322.zip
Boot to recovery, copy zip to internal storage, swipe to wipe and flash the zip.
p/s if it cannot boot to custom rec then use this guide
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012

Thanks so much for your reply,
In the end I spoke to one plus and they couldn’t fix it, they said I could exchange it free of charge, so he got a brand new phone yesterday! Thank god. I’m never letting him root it again tho, he only had it 24hours!!!
nguyenlucky said:
tell him to download this (full firmware)
https://otafsg.h2os.com/patch/amazo...xygen_43_OTA_011_all_1804241056_afd261322.zip
Boot to recovery, copy zip to internal storage, swipe to wipe and flash the zip.
p/s if it cannot boot to custom rec then use this guide
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
Click to expand...
Click to collapse

brickedmum said:
Thanks so much for your reply,
In the end I spoke to one plus and they couldn’t fix it, they said I could exchange it free of charge, so he got a brand new phone yesterday! Thank god. I’m never letting him root it again tho, he only had it 24hours!!!
Click to expand...
Click to collapse
You should let him experiment again, this time with some more reading here on the forum before though. He can learn a great deal about how different systems are built and the working parts of them.
And mostly since it's really fun, these days its really hard, close to impossible to mess up the phone bad.

Yes - He should be allowed to root it again - He needs practice

fkofilee said:
Yes - He should be allowed to root it again - He needs practice
Click to expand...
Click to collapse
I'm also in that opinion. He should be allowed to root again.
I may have an idea why this happened: Instead of an Oneplus 5T Firmware, he may have flashed a Oneplus 5 Firmware..
you mentioned an upside down turned Screen... well, the normal oneplus 5 had their Display assembled upside down and oneplus thought it would Fixing it by turn the Display Output by 180° by Software configuration. Your son should be Aware of that Oneplus 5 and 5T are different devices.

First step is using fastboot adb tool to flash some custom recovery first such as twrp,then download the latest oxygen system from oneplus official website(should be about 1.6gb) flash it inside and reboot. U will get a official system with official recovery set everything up. Then flash the custom recovery again and flash custom kernals such as bluespark or franco. goto the google pay or other root blocked app to set up everything.
Now you can flash the magisk to get root and activate magisk hide immediately right after u reboot. Remenber to tick the apps you need to hide the root for.
Wish u success:good:

Beta and Global ROM stuck in MIUI Loading Screen

Hi,
hope someone could help me.
I have a Mi max 3. I was on latest stable ROM (Global) which is miui_MIMAX3Global_V11.0.2.0.QEDMIXM_4eb86f33af_10.0
Then I flashed OrangeFox Recovery and installed Chinese Beta Rom which is miui_MIMAX3_20.6.17_e4a1ec4252_10.0
I reinstalled few times because I noticed some issues with notification and also needed gapps because not included in chinese beta rom. However later I decided to flash back from Chinese Beta Rom to Global Stable Rom again. I got a message to enter password to start Android. Then I did different steps like wipe Data, Format Data, flashed Global Stable, flashed Chinese Beta and so on. Actually it only booted with bootloop while MIUI Loading screen appears. I did some google research and found out I would need to flash these files: I flashed Disable_Dm-Verity_ForceEncrypt_12.27.2019 and no-verity-opt-encrypt-6.0 but after that I couldnt even get into Android loading screen, after restarting device it only would load Recovery and Fastboot mode. So even worse than before. Cant remember right now what I did next but However, currently situation is this:
I have TWRP (Not Orangefox) installed and can boot into it
I can boot into Fastboot
But doesnt matter if Chinese Beta ROM or GLobal Stable ROM is installed, it will load untl MIUI Loading Screen but hangs there (bootloop)
Even if I flash whole official ROM (nitrogen_global_images_V10.2.1.0.PEDMIXM_20190226.0000.00_9.0_global) via Mi Flash Tool I do get an Error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What can I do? I am pretty sure I could get it back to work, I am just frustrated because trying all this whole day already and just cant find the right steps until it wouldl load normally and boot up normally.

Please, isn't there anyone who can help me to get the phon back booting up?

Antirollback?
Try as a temp solution xiaomi.eu ROM

Wywern.pl said:
Antirollback?
Try as a temp solution xiaomi.eu ROM
Click to expand...
Click to collapse
I just check for activated Antirollback but seems it is not enabled on my device
C:\adb>fastboot getvar anti
getvar:anti FAILED (remote: GetVar Variable Not found)
finished. total time: 0.016s
C:\adb>
So that is a good sign at least, ya?
I found a a MIUI 12 based ROM for Mi max 3 on xiaomi.eu:
https://xiaomi.eu/community/threads/20-6-18.56244/
https://androidfilehost.com/?fid=8889791610682873498
But it says antirollback enabled. So should I try to flash it or not? Seems I will have antirollback enabled afterwards?
Unfortunately I cant register with xiaomi.eu, they ban all my registration automatically coz of fraud protection

Wywern.pl said:
Antirollback?
Try as a temp solution xiaomi.eu ROM
Click to expand...
Click to collapse
Hey @Wywern.pl or anyone else, can you hekp me again? =(

A local reapir shop managed it somehow to get the phone back to life. It is now booting up to MIUI 10.2.1.0 Stable - (OEDMIFK)
But unfortunately my WIFI is not working anymore. If I toggle on, it will be turned on for a moment and searching for networks but does not find one, then it switchwes off WIFI automatically. Mac address is someting like 2.000.00.00 and camera and its flash warent working.
Anyone got an idea what this could be?
I am now downloading official OTA Update (via mobile data) to MIUI 11.0.7.0 Stable (PEDMIXM) and hope that update wll bring my WIFI back to work.

Great news
WiFi problem - only thing comes to my mind is baseband
Acc camera - no idea , hope new ROM will work better

luckily update fixed everything, all is working normal again. Thx anyway!

Need help with hardbricked phone

Hi, something went wrong while trying to install pixelExperience on my redmi note 8 pro. It doesn't reach any screen, no fastboot, no recovery, no boot screen. The notification led light up when connected to the PC, but no charging screen.
I was installing pixelExperience 11 with no error, but it never booted up after rebooting.
I'm currently trying to flash rom downloaded from xiaomifirmwareupdater.com with SP flash tool. I'm using the version from UnbrickRN8ProNoAuth, it says it worked, but the phone won't start.
The booloader was unlocked, I tried both the global and the europe version. I don't know what to try now, any suggestion ?
What could be the problem, I was expecting that flashing the official rom would at least get me to the boot screen.
Thanks !

Hello to me, exactly the same thing happened to me when installing pixel experience, you follow all the steps of UnbrickRN8ProNoAuth
to use python, driver, libusb, bypass and finally spflashtool with the dafiles and the authfiles?
I use the version with this method is this:
https://c.mi.com/thread-3612344-1-0.html
With that I was able to start the mobile and the fastboot mode worked again, apparently it is a bug when entering pixel experience if you have firmware 12.5 that sometimes causes the brick, try that version it worked for me. a greeting
ps: especially remember to use the auth_sv5.auth in the program
and MTK_AllInOne_DA_mt6765_mt6785, if everything is correct you should get a green check, I tell you because first the program checks the rom if it is correct, do you connect it by pressing the 3 buttons at the same time?

Hey, thx, I'll try with this version then !
Yes I have the green check, and I connect the phone with only the vol+ pressed.
I need to do the bypass every time, is that the normal behaviour, and is there another step I should redo ?

robicop2 said:
Hey, thx, I'll try with this version then !
Yes I have the green check, and I connect the phone with only the vol+ pressed.
I need to do the bypass every time, is that the normal behaviour, and is there another step I should redo ?
Click to expand...
Click to collapse
Because of the preloader mode I never use volume + I always use the 3 buttons, so I added the "libusb filter" the bypass I don't know exactly what it is for, but the 2 times that I used the mediatek program and I used it, I just look at it, and according to github it is used for: "Small utility to disable bootrom protection (sla and daa)" and according to google the bootrom: "Bootrom (or Boot ROM) is a small piece of ROM mask or write-protected flash embedded inside of the processor chip. It contains the first code that the processor executes when turning on or resetting. "Enteoria, if it doesn't write you that data from version 12.0.4, it doesn't turn on, follow all the steps correctly with the rom that is shared with you. above and I should start your phone.

It's working again !!
I searched for a similar version but global, and installed it (https://c.mi.com/thread-3565279-1-0.html)
Thanks a lot.
If that can help someone, this time I had an error on the 4th step, it wasn't finding my phone whereas the step 5 could. I had to rerun step 3.
Now I have to choose between settling with this version or trying again ^^ did you manage to install pixelExperience in the end ?

Hi, I'm glad you fix it in the end, the rom that you put is the same, it only changes that mine is the europe version and yours is International, the google patch also changes,
In the end, if I could install pixel from 12.0.4 to pixel 12, from 12.5 the firmware is different and there are many bricks, I bricked myself just like you did not turn on anything, when going from 12.5 to pixel 11, from 12.0 no It opens up risks of going to pixel 11 or 12.
in the end, you can only install pixel 12, wanting to put 11 could not mount the system and the provider
The problem that the cameras do not work well in pixel, even installing gcam they go lag and not all of them work, not even the 64mpx mode, right now I am in miui stock with bootloader closed again. the cameras are important to me, greetings
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Bootloop with standard ROM and working with custom

Hi there,
today I installed PixelExperience then ProjectElixir on my MI 10T Pro with no issues.
I basically just had to try it then I wanted to get back to the default OS but I'm unable to do it.
I tried to use Xiaomi Mi Tool v2 too and everything seems working correctly but when the system tries to boot it is stuck, bootlooping.
Then I tried again to flash TWRP 3.4.0.1 and flash a custom ROM (i.e. Pixel Experience) and it works.
Seems I'm having the problem only while flashing the factory OS; how is that possible? How can I dig deeper into the issue?
Thanks

gtorre92 said:
Hi there,
today I installed PixelExperience then ProjectElixir on my MI 10T Pro with no issues.
I basically just had to try it then I wanted to get back to the default OS but I'm unable to do it.
I tried to use Xiaomi Mi Tool v2 too and everything seems working correctly but when the system tries to boot it is stuck, bootlooping.
Then I tried again to flash TWRP 3.4.0.1 and flash a custom ROM (i.e. Pixel Experience) and it works.
Seems I'm having the problem only while flashing the factory OS; how is that possible? How can I dig deeper into the issue?
Thanks
Click to expand...
Click to collapse
Try with this tool
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/

gtorre92 said:
Hi there,
today I installed PixelExperience then ProjectElixir on my MI 10T Pro with no issues.
I basically just had to try it then I wanted to get back to the default OS but I'm unable to do it.
I tried to use Xiaomi Mi Tool v2 too and everything seems working correctly but when the system tries to boot it is stuck, bootlooping.
Then I tried again to flash TWRP 3.4.0.1 and flash a custom ROM (i.e. Pixel Experience) and it works.
Seems I'm having the problem only while flashing the factory OS; how is that possible? How can I dig deeper into the issue?
Thanks
Click to expand...
Click to collapse
You can flash stock rom using the official MiFlash tool using the fastboot rom or using twrp recovery rom but you'll need to FORMAT DATA due to different encryption. I'm using this twrp and works fine - https://dl.akr-developers.com/?file=skkk/TWRP/A12/v6.3_A12/[REC_BOOT]3.6.2_12-RedmiK30SUltra-Mi10T[Pro]_v6.3_A12-apollo-skkk_dc4ecad7.zip

Hello guys, i have a problem on my Mi10t non pro global version
whenever i tried, my TWRP can't proceed in installing Disable_Dm-Verity_ForceEncrypt_11.02.2020, also tried different force encrypt and other vmbeta file still no luck, my version is MIUI 12.5.2 android 11, can anyone help me? i really needed this to install custom ROMs too, thank you very much

NOSS8 said:
Try with this tool
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
Click to expand...
Click to collapse
Hi there,
I've not been able to use MiFlash, which was crashing both on Windows 10 and Windows 11 PCs.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Anyway, using the fastboot version of the official ROM (with the bat script flash_all.bat) worked correctly, even if it took quite a while to download.

gtorre92 said:
Hi there,
I've not been able to use MiFlash, which was crashing both on Windows 10 and Windows 11 PCs.
View attachment 5726557
Anyway, using the fastboot version of the official ROM (with the bat script flash_all.bat) worked correctly, even if it took quite a while to download.
Click to expand...
Click to collapse
Just create an empty txt file of the same name.