Related
Okay guys first let me tell you why I have created a new thread just for updating the BL and Firmware ,
I know we already have methods of updating like:
1. flashing the full OOS3 zip through stock recovery ,this method is quite simple for the ones who are on stock recovery and just want to update their OOS version.If you fall in this category then you have no purpose here,you may leave.
2. Is method provided by our fav helping hand @Joshwin Aranha ,that method is sure for the rest of us who dont fall in the above category,but is way too long,although simple and effective still "long".
I created this thread to help the CM13(Official or Sultan's)//any custom rom using new BL,users who want to update their BL without flashing the OOS through the tedious way just to update BL and users who are stuck on bootlogo due to old BL with roms using new BL.
Here I will guide you through the required steps to update our bootloader "In easiest and fastest way without wiping and restoring anything".
So what are we waiting for ,lets start .
Prerequisites
you will need two files for this process,nothing else.
1 . First one is BLUpdater zip --->Here.
2. Second is TWRP compiled from latest sources use either This or the one from Here<--use v41 or use Sultan's from Here OR if you are Martin's fan like me and want to use his MutiRom TWRP goHere.
PS:I am assuming you have Unlocked Bootloader and have either
official/blu_spark/sultan's/ Multirom TWRP installed,in a working condition on OOS2.x BL(if not what are you doing here).
Note: make sure oem unlocking is checked in developer options in your current rom,else updating the BL may cause it to get locked ,and you will have to unlock it again and flash the recovery manually through fastboot itself.
Now the steps
1.First copy both of the above files in your sdcard or otg or ext-sdcard,any place accessible in recovery.
2. Now boot into recovery Choose Install and choose the "OPXBLUpdateOOS3.1" zip and flash it.
3. Don't reboot now ,go to Install again ,this time use "Install Image" button in lower right corner,navigate to folder where you copied the new TWRP,you should be able to see the file,select it ,choose recovery in the next menu and flash.
NOTE:If you chose to use Sultan's recovery.zip then just flash it normally.
4. Don't reboot come back to TWRP home ,goto reboot and recovery ,if TWRP says no OS installed ignore it.
Now voila you should have updated your firmware/BL.Congrats.
You can now install any rom that supports the new BL.Older roms won't boot on the new MM BL.So check the rom thread before installing the rom and later on quacking here about your device being stuck at bootlogo.
Notes
i)Neither I nor XDA will be responsible if your OPX bricks or explodes or ditches you and flies to space.
ii)We are not touching system partition so last installed ROM will be intact.
iii)This guide will leave you into bootable rom only if you have a rom installed that works on latest firmware.
iv)This can also be used to restore all your OPX partitions back to OOS3.x partition state,if you messed any.
v)In case you are using latest nightly (cm13) and face bootloop - go Here
psst:If you are not diggin the new BL,and wanna downgrade again ,back to old BL,check this post.
PS: (second one,I know) This guide was made by taking inspiration from Joshwin's post and devtry method.
Also click Thanks if I helped you
matwaking said:
Okay guys first let me tell you why I have created a new thread just for updating the BL and Firmware ,
I know we already have methods of updating like:
1. flashing the full OOS3 zip through stock recovery ,this method is quite simple for the ons who are on stock recovery and just want to their OOS version.If you fall in this category then you have no purpose here,you may leave.
2. Is method provided by our fav helping hand @Joshwin Aranha ,that method is sure for the rest of us who dont fall in the above category,but is way too long,although simple and effective still "long".
So I created this thread just to shorten the process provided by Joshwin.I also created this thread to help the official CM13 users who have problem with latest nightlies due to new bootloader or are stuck in bootlogo.
...
PS: (second one,I know) This guide was made by taking inspiration from Joshwin's post and devtry method.
Also click Thanks if I helped you
Click to expand...
Click to collapse
Booomshkalaka!!!
Great guide, can't test (already have new bootloader and too lazy to switch back but look very good.
Thx to all
Kurt
Kurt Krummbein said:
Booomshkalaka!!!
Click to expand...
Click to collapse
Lol .
Thanks mate.
Will this work if I'm in bluspark twrp but the previous version..? Or do I have to change to official twrp?
jonrodz said:
Will this work if I'm in bluspark twrp but the previous version..? Or do I have to change to official twrp?
Click to expand...
Click to collapse
Will work with any twrp,no requirement of official one.
Thanks, bro. One more doubt. I'm currently on DU rom with custom kernel... Do you think rom will boot after this..?
jonrodz said:
Thanks, bro. One more doubt. I'm currently on DU rom with custom kernel... Do you think rom will boot after this..?
Click to expand...
Click to collapse
No it wont,right now almost all the custom roms need to update to support new firmware.Only latest cm13 nightlies are booting now,also aosp compiled by olddroid for new BL(shh its only for testers right now)
also maybe the MIUI8 port ,just posted in the forums.
I'm a litte bit confused.
Currently I'm on nighty October 1st. (cm-13.0-20161001-NIGHTLY-onyx.zip)
Can i update the Bootloader with your method and after that booting up my current nightly version?
Or do I have to update after the bootloader update to nightly version 12 (the currently latest)?
jerikooo said:
I'm a litte bit confused.
Currently I'm on nighty October 1st. (cm-13.0-20161001-NIGHTLY-onyx.zip)
Can i update the Bootloader with your method and after that booting up my current nightly version?
Or do I have to update after the bootloader update to nightly version 12 (the currently latest)?
Click to expand...
Click to collapse
no update the BL using the steps above ,then flash the latest nightly.That way it would be good.
Or you can flash nightly first then update BL.Choice is yours.I recommend updating the BL first.
I followed your guide with a locked bootloader, and now I'm in bootloops . Just suggest you put a big red "make sure your bootloader is unlocked" in the steps, not in the footnote.
Duplicate post.Deleted
ccaappton said:
I followed your guide with a locked bootloader, and now I'm in bootloops . Just suggest you put a big red "make sure your bootloader is unlocked" in the steps, not in the footnote.
Click to expand...
Click to collapse
Reboot into fastboot mode and
Code:
fastboot oem unlock
And using a custom recovery and custom rom makes me assume one have unlocked bootloader
matwaking said:
Reboot into fastboot mode and
Code:
fastboot oem unlock
And using a custom recovery and custom rom makes me assume one have unlocked bootloader
Click to expand...
Click to collapse
Thanks! I actually relocked my bootloader not long after installed cm13, and disabled "unlock oem" in "developer settings"(I don't know why I did this). So both system and rec is inaccessible, and fastboot is useless in this case. Fortunately I followed the unbrick guide: http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 and get the old bootloader back. Now I could enter CM13-09-28 with all my data intact.
Just hope to let people know the hard lesson I learned, and how to deal the bootloops.
And guys, NEVER RELOCK BOOTLOADER AGAIN!
ccaappton said:
Thanks! I actually relocked my bootloader not long after installed cm13, and disabled "unlock oem" in "developer settings"(I don't know why I did this). So both system and rec is inaccessible, and fastboot is useless in this case. Fortunately I followed the unbrick guide: http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 and get the old bootloader back. Now I could enter CM13-09-28 with all my data intact.
Just hope to let people know the hard lesson I learned, and how to deal the bootloops.
And guys, NEVER RELOCK BOOTLOADER AGAIN!
Click to expand...
Click to collapse
Well no fix without any problems hehehe,.Haapy 4 u.
Click that button if you think my posts are useful
Is this enough to install CM14 or do i have to install the whole room and them flash CM14?
Manelit said:
Is this enough to install CM14 or do i have to install the whole room and them flash CM14?
Click to expand...
Click to collapse
taking you wanna flash ashwins cm14 right. You just wanna follow the instructions in first post and then flash the cm14.No need to install the whole Oos zip.
This way you should have updated BL and working cm14.
Just flash the cm14 after booting into new TWRP
I've just followed the procedure from OP and all went smooth as butter. Thanks
Directly after that (without reboot) I've installed the latest CM13 (with GApps) and Arsenic R24. Working as a charm
slaav said:
I've just followed the procedure from OP and all went smooth as butter. Thanks
Directly after that (without reboot) I've installed the latest CM13 (with GApps) and Arsenic R24. Working as a charm
Click to expand...
Click to collapse
Press that sweet sweet button mate
1.First copy both of the above files in your sdcard or otg or ext-sdcard,any place accessible in recovery.
2. Now boot into recovery Choose Install and choose the "OPXBLUpdateOOS3.1" zip and flash it.
3. Don't reboot now ,go to Install again ,this time use "Install Image" button in lower right corner,navigate to folder where you copied the new TWRP,you should be able to see the file,select it ,choose recovery in the next menu and flash.
4. Don't reboot come back to TWRP home ,goto reboot and recovery ,if TWRP says no OS installed ignore it.
Click to expand...
Click to collapse
Hi, everyone
I'm accidentally reboot device after second step. Now device freezing on "+1 powered by android". Can I remove this zip, or... what can I do next?)
walsash said:
Hi, everyone
I'm accidentally reboot device after second step. Now device freezing on "+1 powered by android". Can I remove this zip, or... what can I do next?)
Click to expand...
Click to collapse
u can flash bluespark twrp via fasboot
Sent from my ONE E1003 using XDA-Developers mobile app
This is for people who have received their phone with a pre-installed Vendor ROM (MIUI Global Stable 8.0.8.0) and wants to switch to the Unofficial EU ROM. In my opinion, the EU ROM is currently the best ROM without any Chinese bloatware or popups until Xiaomi decides to release an actual Global ROM.
For those who are already on a China Stable ROM, there is already an excellent guide to install TWRP, ROOT, compiled by @underlines. This is only intended for switching from a Vendor ROM as I wasn't able to switch from a Vendor ROM to an official build using the previous guide. You need to be on an official build to be able to use TWRP and flash the EU ROM.
EDIT : The reason why I have mentioned to flash an official build at first is because, TWRP can be unresponsive with some Vendor ROMS. You'll be able to boot TWRP but touch would be frozen. I've tried with both versions of TWRP and it wouldn't work with the Vendor ROM installed on my device. TWRP over the Vendor ROM may work for some users.. For some builds like the one which came installed on my phone, it may not work. If TWRP works for you without being on an official build, you can skip the part where you have to flash an official ROM.
1. You need to have an unlocked bootloader. Please follow instructions on the other guide on how to do this.
2. You need the older version of MiFlash found on this link. Thanks to @Thorin78 for this link.
3. Download and extract fastboot Stable or Dev ROM and extract ROM folder to the C:\ Drive. This is because MiFlash may show a "cannot find file" error if you have a lot of subfolders. To avoid this, its best if the folder is C:\ROM Folder.
4.In the older version of MiFlash, click advanced and change the fastboot script location to the flash_all.bat in your unzipped rom folder.
5.Connect your phone in fastboot mode, click "Refresh" in MiFlash. Once your phone is detected, click "Flash" and it should now successfully flash the official ROM of your choice.
If you wish to be on a Xiaomi Official Stable or Dev ROM, Stop here! If you wish to continue installing the EU ROM proceed with the steps below.
6. Now that you have successfully flashed Official Stable or Dev ROM, use Minimal ADB and flash TWRP RC2 using the instructions in the other guide.
7. Once you are in TWRP, Swipe right to allow System Modifications and copy the forced encryption disabler using MTP. Flash this file to ensure that there are no bootloops.
8. After this step, go to WIPE, Format Storage, type "yes" and then Reboot Recovery. Copy SuperSU and EU ROM to storage and flash. Phone may take a few minutes to boot up and you will successfully boot the EU ROM.
For everything else, please follow the guide posted by underlines.
TWRP EU RC2 works with the China Dev ROM as well. Once you Swipe to Right to allow modifications, don't forget to flash the latest dm-verity and forced encryption disabler script from here. This is to prevent the device going into a bootloop.
These are the steps I followed and I am on EU ROM. Hope this helps people who wish to switch to the EU ROM from the Vendor ROM.
The link to miflash takes you DL minimal adb?
jazz452 said:
The link to miflash takes you DL minimal adb?
Click to expand...
Click to collapse
Corrected. Thanks for letting me know! Cheers!
satishp said:
Corrected. Thanks for letting me know! Cheers!
Click to expand...
Click to collapse
I managed to flash with latest miflash using your guide my bootloader was already unlocked check using:
boot your phone into fastboot and COMMAND PROMPT " fastboot oem device-info "
most are probably unlocked with vendor rom but not all.
Don't try to unlock with this method just check to save sometime.
guide: http://xiaomitips.com/guide/how-to-check-if-redmi-note-3-bootloader-is-locked-or-unlocked/
jazz452 said:
I managed to flash with latest miflash using your guide my bootloader was already unlocked check using:
boot your phone into fastboot and COMMAND PROMPT " fastboot oem device-info "
most are probably unlocked with vendor rom but not all.
Don't try to unlock with this method just check to save sometime.
guide: http://xiaomitips.com/guide/how-to-check-if-redmi-note-3-bootloader-is-locked-or-unlocked/
Click to expand...
Click to collapse
I guess it also depends on the Vendor ROM and customization which comes installed on your device. Not all Vendor ROMs for this device are the same. I tried everything under the sun with the latest miflash. It would detect device and even give a "success" output but the ROM was never actually flashed. The phone would still be on the Vendor ROM. Its as if some Vendor ROMs have some form of write protection baked in.
I could only get it working with the older miflash.
I'm not saying it was easy, the hard thing was making the unpack ING of the file. Sort of did it twice never had that problem before.
Why is it required to flash the official rom before flashing the EU rom?
nkatz565 said:
Why is it required to flash the official rom before flashing the EU rom?
Click to expand...
Click to collapse
This for people who don't want TWRP, root and dm-verify, just genuine Xiaomi rom with OTA updates and remove vendor rom.
QQ.
I did the following on my Mix and wondering if I am missing anything. I should say that everything "appears" to be working perfectly on the EU rom.
My Mix came with 8.0.8.0 Global (Vendor ROM) and I wanted to move onto the Xiaomi.eu rom. I loosely followed the above guide and did the following steps:
Applied for Unlock
Unlocked the device via MiUnlock
Used Minimal ADB and booted the device into FastBoot
Confirmed device was Bootloader unlocked
Flashed TWRP (latest non-eu build)
Booted to recovery
DID NOT swipe to edit system partition, left that read only
Flashed the latest Weekly Xiaomi.eu build
Wiped Dalvik/Cache
Booted phone
Performed a Factory reset.
All seemed a little too easy and I didnt need to go to an "Official" china ROM first. But I do have a few questions...
Should I have swiped Yes to enter Read/Write mode for the system partition and run a dm-verify? (I am not interested in Rooting the device at this stage)
Should I have performed a System clear in TWRP before installing Xiaomi.eu ontop of the Vendor ROM?
geubes said:
QQ.
I did the following on my Mix and wondering if I am missing anything. I should say that everything "appears" to be working perfectly on the EU rom.
My Mix came with 8.0.8.0 Global (Vendor ROM) and I wanted to move onto the Xiaomi.eu rom. I loosely followed the above guide and did the following steps:
Applied for Unlock
Unlocked the device via MiUnlock
Used Minimal ADB and booted the device into FastBoot
Confirmed device was Bootloader unlocked
Flashed TWRP (latest non-eu build)
Booted to recovery
DID NOT swipe to edit system partition, left that read only
Flashed the latest Weekly Xiaomi.eu build
Wiped Dalvik/Cache
Booted phone
Performed a Factory reset.
All seemed a little too easy and I didnt need to go to an "Official" china ROM first. But I do have a few questions...
Should I have swiped Yes to enter Read/Write mode for the system partition and run a dm-verify? (I am not interested in Rooting the device at this stage)
Should I have performed a System clear in TWRP before installing Xiaomi.eu ontop of the Vendor ROM?
Click to expand...
Click to collapse
Wouldn't worry about it the vendor ROMs aren't poison, not sure about dm-verify if you kept read only. I would of swiped then flashed dm-verify but didn't mean I know what I'm doing.
nkatz565 said:
Why is it required to flash the official rom before flashing the EU rom?
Click to expand...
Click to collapse
This is because some Vendor ROMS have some compatibility issues with TWRP. Touch screen wouldn't work on TWRP. I tried both TWRP versions and couldn't get touch to work.
Finally, I flashed the China Dev ROM and then used TWRP RC2 and touch functionality worked.
As some users below have pointed out that they could get to EU without flashing the one of the official builds, I guess it depends on the amount or type of vendor customizations applied on your device.
Which version do you own? I was wondering if this would work with the 6GB as well.
dbesada said:
Which version do you own? I was wondering if this would work with the 6GB as well.
Click to expand...
Click to collapse
This works with both versions. The ROM is compatible with both variants as the size of memory and storage doesn't affect compatibility.
I have the 6\256 variant.
satishp said:
This works with both versions. The ROM is compatible with both variants as the size of memory and storage doesn't affect compatibility.
I have the 6\256 variant.
Click to expand...
Click to collapse
Thank you. It worked. I fastboot twrp then factory reset the device and flashed the eu rom. All good. My bootloader was unlocked by the vendor.
Can someone please give me some advice? Just got the phone a couple hours ago. I took a picture of the info page. Based on the screenshot am I on the vendor ROM or official? I'm thinking I'm on Vendor because it has GAPPS already included.
If I'm on Vendor ROM and want to get to rooted EU Rom I can follow directions in the OP right?
How do I know is if my bootloader is already unlocked? Many thanks
SantinoInc said:
Can someone please give me some advice? Just got the phone a couple hours ago. I took a picture of the info page. Based on the screenshot am I on the vendor ROM or official? I'm thinking I'm on Vendor because it has GAPPS already included.
If I'm on Vendor ROM and want to get to rooted EU Rom I can follow directions in the OP right?
How do I know is if my bootloader is already unlocked? Many thanks
Click to expand...
Click to collapse
Vendor (there is no Global ROM for Mix). You should unlock your bootloader (check if it's already unlocked using "fastboot oem device-info"), flash TWRP, wipe and flash EU
Razorbacktrack5535 said:
Vendor (there is no Global ROM for Mix). You should unlock your bootloader (check if it's already unlocked using "fastboot oem device-info"), flash TWRP, wipe and flash EU
Click to expand...
Click to collapse
Do I have to do Power + Vol Down (that's bootloader mode right) in order to input the ADB code you gave me?
SantinoInc said:
Do I have to do Power + Vol Down (that's bootloader mode right) in order to input the ADB code you gave me?
Click to expand...
Click to collapse
Yes, you have to use Fastboot Mode
Razorbacktrack5535 said:
Yes, you have to use Fastboot Mode
Click to expand...
Click to collapse
I'm not unlocked right? Hope they approve my unlock request soon
SantinoInc said:
I'm not unlocked right? Hope they approve my unlock request soon
Click to expand...
Click to collapse
Yes, you have to wait
Hello,
I have flashed TWRP and roms before on other phones, so i know how to do it, but is was always Samsung..
Now i want to make sure on Huawei that i'm correct doing..
step1 would be: https://forum.xda-developers.com/p8lite/general/step-step-guide-to-unlock-bootloader-t3150616
Step2 would be: https://forum.xda-developers.com/p8lite/orig-development/twrp-t3583180
Step3 would be: https://forum.xda-developers.com/p8lite/development/rom-t3606568
I have a couple of questions:
- Do i need step1? I bought this device fully, so its unlocked..
- Should i consider any other stable rom?
Thanks for the responds in advance.
Ward
Step1,when in fastboot mode says phone unlocked this step is unncessary,when phone locked you need unlock bootloader
I use AOSPA and I used RROS and AOSPA is faster,more stable ?
Adi5 said:
Step1,when in fastboot mode says phone unlocked this step is unncessary,when phone locked you need unlock bootloader
I use AOSPA and I used RROS and AOSPA is faster,more stable
Click to expand...
Click to collapse
Thanks.
How to Fix for WIERD LOCKSCREEN BUG on Android 8 and + custom roms
Many of them are facing this Bug after setting up Lockscreen, after few reboots we face System UI FC when entering Unlock code or pattern. This bug is faced when using Oreo, Pie and 10. And this bug is not present on Nougat.
Warning You will loss your all data including your device internal storage and i will be not responsible for any bricks if it happens on your device
Steps :-
Step 1 :- First of all Download MIUI global stable FASTBOOT ROM from the link http://bigota.d.miui.com/V10.2.1.0....XM_20190114.0000.00_6.0_global_8a48e54fe3.tgz
Step 2 :- download mi flashtool and install on your pc and extract fastboot_rom.tgz to a folder.
Step 3 :- Important to have Official Unlock, if you are Unofficially unlocked try this method :- https://forum.xda-developers.com/re...icially-unlock-bootloader-redmi-note-t4009799
Step 4 :- Now copy userdata.img and persist.img from images folder to minimal adb and fastboot folder.
Step 5 :- Now open command window and write following commands -
fastboot erase persist
fastboot erase userdata
fastboot flash persist persist.img
fastboot flash userdata userdata.img
Step 6 :- Now "clean" flash a custom rom 8 or above it. And check whether this bug is still present of not. If you still face the bug then once flash full MIUI through Mi flash tool and repeat Step 5. Note :- After repeating Step 5 don't boot back into MIUI. After performing Step 5 quickly flash twrp and wipe MIUI and flash Custom rom.
Step 7 :- The bug will be gone.
I have made it easy.
If you guys have any Problem regarding this Pm or contact me on telegram my account @sk_ik_27400
Enjoy Flashing:fingers-crossed:
How many days have you checked? Actually after clean flash it happens after roughly one and a half day
One more thing, I am not officially unlocked, I use twrp with locked bootloader, should I try this?
arnabbandopadhyay said:
How many days have you checked? Actually after clean flash it happens after roughly one and a half day
One more thing, I am not officially unlocked, I use twrp with locked bootloader, should I try this?
Click to expand...
Click to collapse
i can 100 percent guarantee it will work i tried about 2 to 3 weeks no issues.
if u are unofficially unlocked then then i would recommend unlock officially using china dev fastboot rom because for many global dev or stable doesnt work
by the way u can if u flash with unofficialy unlocked bootloader then u will be stuck simply do is first of all flash all clean and lock then but remember use that fastboot rom which is recommended for unlocking unofficially rather than latest. then unlock its bootloader then on bootloader flash same image files i have said in above thread simple. also kindly check thread for unnoficial unlocking. http://en.miui.com/thread-345728-1-1.html
tap thanks if helped
Ishaan Kaushal said:
i can 100 percent guarantee it will work i tried about 2 to 3 weeks no issues.
if u are unofficially unlocked then then i would recommend unlock officially using china dev fastboot rom because for many global dev or stable doesnt work
by the way u can if u flash with unofficialy unlocked bootloader then u will be stuck simply do is first of all flash all clean and lock then but remember use that fastboot rom which is recommended for unlocking unofficially rather than latest. then unlock its bootloader then on bootloader flash same image files i have said in above thread simple. also kindly check thread for unnoficial unlocking. http://en.miui.com/thread-345728-1-1.html
tap thanks if helped
Click to expand...
Click to collapse
after doing all, should I wipe all dalvik, system, data, cache, internl before flashing oreo rom?
arnabbandopadhyay said:
after doing all, should I wipe all dalvik, system, data, cache, internl before flashing oreo rom?
Click to expand...
Click to collapse
yes after flashing image files from bootloader simply flash twrp and wipe everything and flash any oreo rom but remember once check in twrp recent screen that there is no warning regarding encrption
It was probably magisk issue
nathanchance said:
also @D-m-x (and everyone else), please try this Magisk build (it can be installed in the modules tab in Magisk Manager)
https://transfer.sh/YVFdi/Magisk-v16.7-1674-.zip
It includes a commit that should fix all of the weird issues with Magisk like the PIN not being accepted after a reboot or the phone getting stuck at the Google logo with the progress bar. The root cause is services crashing during the boot chain and either causing deadlock or lack of functionality. It's entirely possible that a service crashed during boot and started causing issues.
Click to expand...
Click to collapse
Please refer to this post if you have magisk installed. thanks to @nathanchance
Ishaan Kaushal said:
yes after flashing image files from bootloader simply flash twrp and wipe everything and flash any oreo rom but remember once check in twrp recent screen that there is no warning regarding encrption
Click to expand...
Click to collapse
No decryption related message in twrp. I did all qnd will report you back after couple of days, whether is it fixed or not.
arnabbandopadhyay said:
No decryption related message in twrp. I did all qnd will report you back after couple of days, whether is it fixed or not.
Click to expand...
Click to collapse
ok :good:
Dims_Camper said:
Please refer to this post if you have magisk installed. thanks to @nathanchance
Click to expand...
Click to collapse
ok i tried all magisk version but i was fed up with this bug i dont know whether ur method works or not but i know this bug happens due to encryption on userdata. i dont think ur method will because magisk is universal and if problem is related to magisk then it should have happened with many devices not kenzo only
by the way thanks if ever faced again that bug i will try your method:laugh:
Ishaan Kaushal said:
ok :good:
Click to expand...
Click to collapse
On 1st reboot device asking " enter your password to start android", I tried to enter twrp, same thing happens, asking for password.
arnabbandopadhyay said:
On 1st reboot device asking " enter your password to start android", I tried to enter twrp, same thing happens, asking for password.
Click to expand...
Click to collapse
do u use telegram? if yes pm tag mentioned above in thread else send a screenshot of it
Ishaan Kaushal said:
do u use telegram? if yes pm tag mentioned above in thread else send a screenshot of it
Click to expand...
Click to collapse
I use but coudn't start my phone now, I am uploading pic
Ishaan Kaushal said:
ok i tried all magisk version but i was fed up with this bug i dont know whether ur method works or not but i know this bug happens due to encryption on userdata. i dont think ur method will because magisk is universal and if problem is related to magisk then it should have happened with many devices not kenzo only
by the way thanks if ever faced again that bug i will try your method:laugh:
Click to expand...
Click to collapse
i'm referring a post on pixel 2 thread, it's not only kenzo things apparently.
arnabbandopadhyay said:
I use but coudn't start my phone now, I am uploading pic
Click to expand...
Click to collapse
i am not able to see any screenshots attach again
Dims_Camper said:
i'm referring a post on pixel 2 thread, it's not only kenzo things apparently.
Click to expand...
Click to collapse
ok:good:
arnabbandopadhyay said:
I use but coudn't start my phone now, I am uploading pic
Click to expand...
Click to collapse
which rom u flashed?
before doing the method i suggested did u had your set a lockscreen password?
if yes simply enter that password and check else from boot loader enter followimg commands from cmd fastboot erase persist
the again flash persist using fastboot and then reboot to rom
Ishaan Kaushal said:
which rom u flashed?
before doing the method i suggested did u had your set a lockscreen password?
if yes simply enter that password and check else from boot loader enter followimg commands from cmd fastboot erase persist
the again flash persist using fastboot and then reboot to rom
Click to expand...
Click to collapse
I flashed cardinal. I never set any lockscreen password or pin, only a set a pattern.
I couldn't flash persist from fastboot, as I am unofficially unlocked, I need to flash only using mi flash in edl mode.
Unlocking bootloader officially is a harrassment, always getting "couldn't add your account: error 20075" something like that
arnabbandopadhyay said:
I flashed cardinal. I never set any lockscreen password or pin, only a set a pattern.
I couldn't flash persist from fastboot, as I am unofficially unlocked, I need to flash only using mi flash in edl mode.
Unlocking bootloader officially is a harrassment, always getting "couldn't add your account: error 20075" something like that
Click to expand...
Click to collapse
bro its better u contact me on telegram it will better to help Your there
arnabbandopadhyay said:
I use but coudn't start my phone now, I am uploading pic
Click to expand...
Click to collapse
Your device is encrypted!!!
Format data through recovery.
nilesh8343 said:
Your device is encrypted!!!
Format data through recovery.
Click to expand...
Click to collapse
doing this only produces lock screen bug
Hello everyone i am in desparate need of some guidance where i unfortunately Hard bricked my Mi9t while trying to flash the new Mokee Rom.
Where i think i went wrong was wiping the system option in twrp. After reboot i was stuck on flashboot and unable to get back into twrp recovery.
I then proceeded to flashboot twrp, also used multiple versions of twrp, again to hopefully be able to get into twrp recovery with no prevail.
Also tried to fastboot via Miflash tool with all latest fastboot roms available currently but kept getting a anti-rollback error.
So then i searched a way to install recovery or stock rom manually via flashboot commands. This caused me to end up where im at, no fastboot, no recovery, no logo at all. I connect the usb and the phone wont turn on at all, just a dead phone. Power button completely unresponsive now, Vol-Up/Vol-Down + Power and nothing.
I worked on it for countless hours trying to simply get into fastboot now with huge anxiety thinking i killed my phone.
I left my phone to charge all night and woke up this morning trying to get into fastboot again and nothing again.
Can someone please lead me in the right direction???
Everywhere i look the info seems to be outdated. At this point i am willing to send it in for repairs but i live in Indiana, US and there isnt a Xiaomi Service location anywhere in site.
Sad story. What did you do in fastboot? If you can't flash a certain twrp version you would have to do:
1. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (in twrp archives)
2. fastboot erase recovery
3. fastboot flash recovery your-twrp.img
Concerning AntiRollBack:
You can bypass ARB in miflashtool, set the number of your new rom higher or edit the batch/shell-files manually. The first few lines are ARB and device-check.
I know the info comes too late, but maybe someone reads this before trying things the way you did. There have to be some EDL-pins inside the phone to reflash fastboot but you would have to open your phone. My opinion/solution: Cry and send in.
Anyway: Can you tell us what you did to wipe fastboot?
fabsen said:
Sad story. What did you do in fastboot? If you can't flash a certain twrp version you would have to do:
1. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (in twrp archives)
2. fastboot erase recovery
3. fastboot flash recovery your-twrp.img
Concerning AntiRollBack:
You can bypass ARB in miflashtool, set the number of your new rom higher or edit the batch/shell-files manually. The first few lines are ARB and device-check.
I know the info comes too late, but maybe someone reads this before trying things the way you did. There have to be some EDL-pins inside the phone to reflash fastboot but you would have to open your phone. My opinion/solution: Cry and send in.
Anyway: Can you tell us what you did to wipe fastboot?
Click to expand...
Click to collapse
When i 1st attempted to recover twrp i used TWRP 3.1.1-2 fixed from 4PDA. Ran the .exe file and the prompt said both fires installed successfully, but when i did a reboot it wouldnt go into twrp anymore, just stuck in logo so i would end up back in bootloader.
ttp://en.miui.com/thread-942449-1-1.html
This is exactly the instructions i tried to use before i lost fastboot.
At one point while entering the commands, it froze then my phone completely died and could never make it do anything else.
Why the hell did you use an outdated tutorial for an other phone? A few of the commands also wouldn't work because there are only some of these partitions. But if you did it with the right firmware it shouldn't brick anyway. So maybe you were stuck at boot flash. Else you still would be able to boot into fastboot.#
I feel sorry for you bro but it looks like you were searching for a possiblity to brick your phone
fabsen said:
Why the hell did you use an outdated tutorial for an other phone? A few of the commands also wouldn't work because there are only some of these partitions. But if you did it with the right firmware it shouldn't brick anyway. So maybe you were stuck at boot flash. Else you still would be able to boot into fastboot.#
I feel sorry for you bro but it looks like you were searching for a possiblity to brick your phone
Click to expand...
Click to collapse
I kno bro i felt like shyt believe me. Literally all day in panic and anxiety that i just wasnt thinking straight and using any kind of guide i can find and ended up here.
Made some progress today tho.
Since my device manager or MiFlash tool wasnt recognizing my device even when i installed Qualcom drivers and pushing all sorts of buttons lol,
I have now opened her up for some surgery and using the Test-Point EDL method.
https://i.postimg.cc/HWJGWHRw/test-point-redmi-k20-mi-9t.png
While USB connected and shorted these 2 pins my computer finally recognized my device in MiFlash Tool and Device Manager again as Qualcomm HS-USB QDLoader 9008 (COM3)!!!
Now the next problem is the MiFlash tool. I tried to flash rom and status states cannot receive hello packet. From what i understand, i need an authorized account.
Only thing i could find to bypass this was this but currently not yet working. - https://forum.xda-developers.com/mi-8/how-to/unbrick-mi8-edl-authorized-account-t3896677
Any ideas where to go from here?
https://mi-globe.com/unbrick-your-xiaomi-phone-without-authorized-mi-account/
https://c.mi.com/thread-1479882-1-0.html
I didn't need an authorized account last year but maybe they've changed something. The guides are up to date so maybe follow these steps.
fabsen said:
https://mi-globe.com/unbrick-your-xiaomi-phone-without-authorized-mi-account/
https://c.mi.com/thread-1479882-1-0.html
I didn't need an authorized account last year but maybe they've changed something. The guides are up to date so maybe follow these steps.
Click to expand...
Click to collapse
Already ran into those sites and actually am currently trying out S-Unlock service to bypass Authorized Account with there XiaomiTool v0.01, and unfortunately again with no prevail.
https://imgur.com/gallery/WMt968b
As you can see i got passed Hello packet, but now it doesn't go passed this message or looks like it didnt do anything.
https://imgur.com/gallery/hHApyJL
Already contacted S-Unlock Admin and now waiting for response. Im assuming im using the right Flashboot Roms. Tried latest flashboot roms from here available. https://xiaomifirmwareupdater.com/miui/davinci/
I also emailed unbrick.ru if they support K20/Mi9T variant and waiting for there reply.
Firmware on your page is not up to date. Use https://mifirm.net/
What device do you have? EEA/Global/CN? And what flashfiles did you use? I'm asking this because the only way I know to brick your device is to flash global/eea-rom on chinese device and lock the bootloader.
fabsen said:
Sad story. What did you do in fastboot? If you can't flash a certain twrp version you would have to do:
1. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (in twrp archives)
2. fastboot erase recovery
3. fastboot flash recovery your-twrp.img
Concerning AntiRollBack:
You can bypass ARB in miflashtool, set the number of your new rom higher or edit the batch/shell-files manually. The first few lines are ARB and device-check.
I know the info comes too late, but maybe someone reads this before trying things the way you did. There have to be some EDL-pins inside the phone to reflash fastboot but you would have to open your phone. My opinion/solution: Cry and send in.
Anyway: Can you tell us what you did to wipe fastboot?
Click to expand...
Click to collapse
Hey,
I'm in a similar boat but I still have fastboot.
I can flash everything I wan't. But flashing a recovery doesn't do anything.
I can not boot into the recovery.
When I boot into the recovery i'm at the bootloop screen.
My PC does recocgnize it as recovery mode tho.
Anyways is there a way to get out of this mess? I wanted to try to flash with miflash over fastboot.img but I can't find any .img to flash.
All I can find are the .zips for twrp.
I didn't want to flash cfw tho. I got into the mess because there was an update today for stock rom and I flashed it with twrp. Because OTA didn't work.
/edit
I found the fastboot files.
But how do I bypass the antirollback error
Waidowai said:
Hey,
I'm in a similar boat but I still have fastboot.
I can flash everything I wan't. But flashing a recovery doesn't do anything.
I can not boot into the recovery.
When I boot into the recovery i'm at the bootloop screen.
My PC does recocgnize it as recovery mode tho.
Anyways is there a way to get out of this mess? I wanted to try to flash with miflash over fastboot.img but I can't find any .img to flash.
All I can find are the .zips for twrp.
I didn't want to flash cfw tho. I got into the mess because there was an update today for stock rom and I flashed it with twrp. Because OTA didn't work.
/edit
I found the fastboot files.
But how do I bypass the antirollback error
Click to expand...
Click to collapse
https://mifirm.net/model/davinci.ttt
to bypass the ARB you can edit the batch/shell files. the first few lines are device-check and ARB. you can also use xiaomitool and select it there.
Edit: I had the same problem with a twrp version I had installed. After switching to russian version I couldn't downgrade twrp. Just try one of the other 2 versions available.
fabsen said:
https://mifirm.net/model/davinci.ttt
to bypass the ARB you can edit the batch/shell files. the first few lines are device-check and ARB. you can also use xiaomitool and select it there.
Edit: I had the same problem with a twrp version I had installed. After switching to russian version I couldn't downgrade twrp. Just try one of the other 2 versions available.
Click to expand...
Click to collapse
I've had the russian version of twrp that didn't allow backups.
I know tried all the other version as well.
What happens is it stays in mi.com unblocked screen and my pc will recognize that it's in recovery but twrp never opens.
Like I said the normal stock recovery is flashable but all other twrp versions don't work for some reason.
I've tried all 3.
I know where the lines are but idk what to write in there.
I tried to just delete the lines and then I've got a different error.
Also when changing the version number it says success it actually flashes for 0 seconds and nothing happens.
Waidowai said:
I've had the russian version of twrp that didn't allow backups.
I know tried all the other version as well.
What happens is it stays in mi.com unblocked screen and my pc will recognize that it's in recovery but twrp never opens.
Like I said the normal stock recovery is flashable but all other twrp versions don't work for some reason.
I've tried all 3.
I know where the lines are but idk what to write in there.
I tried to just delete the lines and then I've got a different error.
Also when changing the version number it says success it actually flashes for 0 seconds and nothing happens.
Click to expand...
Click to collapse
The russian version I've installed allows backups, tried allready.
You can simply remove the lines, just care you dodn't left something or delete too much. Use xiaomitool v2, it'll bypass the lines.
fabsen said:
The russian version I've installed allows backups, tried allready.
You can simply remove the lines, just care you dodn't left something or delete too much. Use xiaomitool v2, it'll bypass the lines.
Click to expand...
Click to collapse
If i download the xiamitool v2 and choose my device is bricked it says feature is not available yet.
/edit
If I choose mod the phone it says my phone serial and all the 3 other things are unknown.
if I select my phone my phone reboots and says waiting for debugging mode....
Then if I delete the ARB lines and try to flash via MiFlash it says error error no such file found
Can someone pls give me some clearer instructions.
Ok I somehow fixed it.
I flashed everything manually like the times before twrp existested.
Now I don't have the OS running but a running twrp.
I could flash xiaomi eu now and be done with it. But I actually wanted to use stock rom and not a costume rom right now because I wanted to switch to a costume rom when a good official comes out whenever that is.
Although flashing the stock rom got me in this mess in the first place. I never had this problem with flashing costume roms.
Anyhow I know this might not be the place to ask but are xiaomi eu and stock actually that different? Also are there any downsides in using it over stock?
My experience on most phones was that early costume roms usually didn't work with all features etc.
/edit
alright who gives a dang I just flashed the eu rom to be safe with updates..
anyhow is it normal that my devices says Redmi by Xiaomi now?
Prior on my stock rom it said MI by mi.com or something
Waidowai said:
Ok I somehow fixed it.
I flashed everything manually like the times before twrp existested.
Now I don't have the OS running but a running twrp.
I could flash xiaomi eu now and be done with it. But I actually wanted to use stock rom and not a costume rom right now because I wanted to switch to a costume rom when a good official comes out whenever that is.
Although flashing the stock rom got me in this mess in the first place. I never had this problem with flashing costume roms.
Anyhow I know this might not be the place to ask but are xiaomi eu and stock actually that different? Also are there any downsides in using it over stock?
My experience on most phones was that early costume roms usually didn't work with all features etc.
Click to expand...
Click to collapse
Basically it's (xiaomi.eu) debloated and optimized but sadly based on chinese official rom. That means no widevine L1.
In my opinion the best rom is EEA (because of "spy restrictions"), debloated with ADBTools with same optimizations which come with mi-globe rombuilder (gpsset, preinstalled magisk, adaway, removed apps). Sadly mi-globe is based on xiaomi.eu which is based on chinese official.
Waidowai
Could you explain the steps you did to flash ALL manual? Which Commands? Which imagens?
Thanks friend.
fabsen said:
Basically it's (xiaomi.eu) debloated and optimized but sadly based on chinese official rom. That means no widevine L1.
In my opinion the best rom is EEA (because of "spy restrictions"), debloated with ADBTools with same optimizations which come with mi-globe rombuilder (gpsset, preinstalled magisk, adaway, removed apps). Sadly mi-globe is based on xiaomi.eu which is based on chinese official.
Click to expand...
Click to collapse
Well i did instal xiaomi.eu now. Not because of optimizations etc.
The only reason is that like i said i don't wanna brick by updating official roms anymore.
I mean maybe it's my bad since I'm running costume roms on all my phones for about 12 years or longer.. can't remember when I started but I think with first xyanogen mod.
And I don't know how to flash stock roms.
But with a costume rom it won't brick and if it does I'm not loosing twrp again.
For debloating I do that myself with the android terminal. So idk what the rom has on bloat I'll just uninstall it.
My only fear was that main features don't work with the costume rom. But from first sight everything but themes work fine. And I couldn't care less.
Well one thing changed the icons look like a chineese appleish phone now. Oh well I'll change that later.
Other than that the fingerprint is more responsive which I do like.
And for some reason my Modelnumber changed from Mi 9T to RedmiK20. Even on the boot it says Redmi now instead of MI.
Idk if it's because of the ROM or because I manually flashed the phone.
---------- Post added at 02:51 PM ---------- Previous post was at 02:42 PM ----------
mauriciocardoso said:
Waidowai
Could you explain the steps you did to flash ALL manual? Which Commands? Which imagens?
Thanks friend.
Click to expand...
Click to collapse
Just download the fastboot rom and flash everything but dummy. You can flash dummy to but that is just for ARB. Depending on what your ARB index is you can flash it to ignore future problems.
My index was 1 tho and apperently if it's under 4 ARB is supposed to be irrelavent.
I'm not to sure on ARB tho because it's my first time dealing with ARB.
Other then that u flash everything else.
You will end up with a phone that is empty. Basically you reformate your phone so nothing is on there but TWRP. My phone was at 59gb/60 or something like that. basically the only folder I've had left was twrp.
Like I said I remembered the method from like 8 years ago when we didn't have twrp.
The problem with this method is that you can easily hardbrick tho I think. Since if it doesn't work you turned your phone into a fancy usb drive.
I only did it because I thought of buying a new one so since the phone was dead in my eyes already I just tried the old method and it worked fine, besides rebranding the phone to RedmiK20 from Mi9T.
Anyhow if your not giving up on the phone yet I wouldn't try it. Only try if you wanna throw the phone in the trash anyways.
just like me , for the anti roll issue u need to flash newers rom like from latest u flash on ur device before (recommend V10.3.11.0.PFJMIXM) u can get on mifirm.net . after download rom extract the file into fastboot tools then copy all .img file into fastboot tools . after that open the fastboot mode on ur phone and tools on pc
then flash this file
fastboot flash dtbo dtbo.img
fastboot flash logo logo.img
fastboot flash vbmeta vbmeta.img
fastboot flash boot boot.img
fastboot flash misc misc.img (u can get on fastboot rom not .zip)
fastboot flash recovery recovery.img (recommend used twrp-3.3.1-2-davinci-fix)
then try reboot phone into recovery
if work let me know . im trying make this method because before this i got this problem to after flashing paranoid rom without format data .
Waidowai said:
Well i did instal xiaomi.eu now. Not because of optimizations etc.
The only reason is that like i said i don't wanna brick by updating official roms anymore.
I mean maybe it's my bad since I'm running costume roms on all my phones for about 12 years or longer.. can't remember when I started but I think with first xyanogen mod.
And I don't know how to flash stock roms.
But with a costume rom it won't brick and if it does I'm not loosing twrp again.
For debloating I do that myself with the android terminal. So idk what the rom has on bloat I'll just uninstall it.
My only fear was that main features don't work with the costume rom. But from first sight everything but themes work fine. And I couldn't care less.
Well one thing changed the icons look like a chineese appleish phone now. Oh well I'll change that later.
Other than that the fingerprint is more responsive which I do like.
And for some reason my Modelnumber changed from Mi 9T to RedmiK20. Even on the boot it says Redmi now instead of MI.
Idk if it's because of the ROM or because I manually flashed the phone.
---------- Post added at 02:51 PM ---------- Previous post was at 02:42 PM ----------
Just download the fastboot rom and flash everything but dummy. You can flash dummy to but that is just for ARB. Depending on what your ARB index is you can flash it to ignore future problems.
My index was 1 tho and apperently if it's under 4 ARB is supposed to be irrelavent.
I'm not to sure on ARB tho because it's my first time dealing with ARB.
Other then that u flash everything else.
You will end up with a phone that is empty. Basically you reformate your phone so nothing is on there but TWRP. My phone was at 59gb/60 or something like that. basically the only folder I've had left was twrp.
Like I said I remembered the method from like 8 years ago when we didn't have twrp.
The problem with this method is that you can easily hardbrick tho I think. Since if it doesn't work you turned your phone into a fancy usb drive.
I only did it because I thought of buying a new one so since the phone was dead in my eyes already I just tried the old method and it worked fine, besides rebranding the phone to RedmiK20 from Mi9T.
Anyhow if your not giving up on the phone yet I wouldn't try it. Only try if you wanna throw the phone in the trash anyways.
Click to expand...
Click to collapse
Don't know how you manage to brick your phone with official firmware tbh. And why should you lose TWRP? I flashed about 10 times (global, eea, chinese, xiaomi.eu, mi-globe) and I still didn't have to reflash twrp once. It won't even touch the recovery partition. I also don't see a reason to mess with fastboot (except your brick haha). The boot behavior (redmi instead of mi) is fine, depends on the rom you've flashed. If you flash global or eea rom it'll switch back to "Mi".
What do you mean by "I don't know how to flash official rom"? Boot up twrp, clean dalvik cache/cache, install... tadaaa. I was also using custom roms on all of my phones but I can't find a reason for now to do so. I see only bugs and things not working. I want my widevine L1 and I want AndroidAuto to be working. I'll stay on global/eea till a good rom pops up.
fabsen said:
Don't know how you manage to brick your phone with official firmware tbh. And why should you lose TWRP? I flashed about 10 times (global, eea, chinese, xiaomi.eu, mi-globe) and I still didn't have to reflash twrp once. It won't even touch the recovery partition. I also don't see a reason to mess with fastboot (except your brick haha). The boot behavior (redmi instead of mi) is fine, depends on the rom you've flashed. If you flash global or eea rom it'll switch back to "Mi".
What do you mean by "I don't know how to flash official rom"? Boot up twrp, clean dalvik cache/cache, install... tadaaa. I was also using custom roms on all of my phones but I can't find a reason for now to do so. I see only bugs and things not working. I want my widevine L1 and I want AndroidAuto to be working. I'll stay on global/eea till a good rom pops up.
Click to expand...
Click to collapse
I mean yeah that's what i thought just flash a official rom like any stock rom. Or rather if you change roms cuz if you update existing roms you don't really need to wipe anything anymore.
But apperently it busted my whole phone. It was a weird brick. My phone wasn't recognized as a phone anymore in fastboot. But it was recognized normal in adb. So I needed to change windows drivers to make my phone recognize.
And after that nothing booted but stock recovery and even then it said I don't have debugging enabled. Eventho I was connected to adb??
Anyhow I think the flash messed up the whole system partition. So what I did is in short formate the whole drive and start with a clean slate.. anyhow don't need to repeat all that.
But yeah I'm with you with the take on costume roms. I don't see the need anymore since most stock roms are decent nowadays and costume roms especially are most likely buggy somehow. Good thing is that most stuff I need in my phone is working on the eu rom. Like I said only thing that I could find not working are themes. But thats ok.
I don't know what that widevine L1 thing is. So I prolly don't need it. But maybe u can explain it to me Always up to learn new things.
Well for now I stick with the costume rom since it's basically no different to me. And the chance of bricking again like that with a costume rom are slim to none. If the phone brick it's most likely just a simple brick that can be fixed with twrp. and if that doesn't work by booting into twrp from adb.
Btw that didn't work on my weird brick either. I couldn't boot anything from adb. It gave me a black screen when trying to boot something.
Anyhow I'm glad I've got it running again. But somehow I'm not that surprised. Most times when I brick phones I can fix it when I'm at the point where I wanna throw the phone away. Cuz then I'm just flashing everything I can to make it work xD.