Related
Bricked. Red "Your device is corrupt. It can't be trusted and may not work properly"
Following this guide I ended up bricking my Nexus 6. Please ask questions as this is my first time rooting a device.
http://forum.xda-developers.com/showpost.php?p=56938530&postcount=1
After typing "fastboot reboot" my phone begun rebooting, stopped and went to the red "Your device is corrupt. It can't be trusted and may not work properly". Now I am able to get to the fastboot menu. I am also able to get to the android recovery menu. Can anyone point me in the direction to get my phone working again?
Thank you in advance
You can get into fastboot. So restore to stock image. Or since you have custom recovery restore your working backup.
Then read the thread on root. Not just the first post. Read the most recent ones... They are the ones with the most up to date info. Never flash stuff or follow guides with out reading like the last 3-4 pages of the thread as well as the full OP AT A MINIMUM.
1)download google factory image
2)Extract everything in one folder.
3)Delete userdata.img from folder(because once i left it in folder and started flashing images one by one and ended up with empty internal storage.lost everything)
4)use these commands to flash
fastboot flash bootloader C:/image-shamu-XXXXXX/bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:/image-shamu-XXXXXX/radio.img
fastboot reboot-bootloader
fastboot flash system C:/image-shamu-XXXXXX/system.img
fastboot flash boot C:/image-shamu-XXXXXX/boot.img
fastboot flash recovery C:/image-shamu-XXXXXX/recovery.img
fastboot erase cache
5)reboot
You don't have to delete userdata.img... Just dont flash it, and don't use flashall
Your manually typing these commands. Just don't type it. Understand what the partitions are and don't flash the ones you don't want.
And on that point, rather then flash the stock recovery, flash something like TWRP since your trying to root.
Wow. Thank you guys. I really appreciate it. Great group here.
Got it back up and running with 6.0.1 with your help. Since I have gotten this far I think I'll try out some ROM's.
Thanks again.
my phone is moto g2 xt1068
i flash it with fastboot very much because after 3 days restarting and hang in boot but after flash it is work for 3-5 days
now i want to flash it but have this error fastboot
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.979s]
writing 'partition'...
FAILED (status read failed (Too many links))
finished. total time: 1.778
please help me
thanks
Do you have twrp?
Have you tried flashing twrp if you don't have it installed?
Which ROM are you flashing?
It looks like you don't have enough space if I'm reading that error correctly
We need to know so we can help you
what is twrp?
now my error (too many link) is resolved when changed my usb cable but my problem that need flash after 3-5 days
please help to solved it
my frimware is
XT1068_TITAN_RETAILDSDS_6.0_MPB24.65-34-3_cid7_CFC.xml
thanks
This is stock firmware, yes?
Are all your Moto G drivers up to date?
There are a number of different ways to install depending on the package type.
Some packages are flashable zips. Needs Twrp (Team Win Recovery Project)
Some are sideload packages installed via Fastboot.
Some are OTA packages (OTA, over the air) installed via phone update.
amir58hz said:
what is twrp?
now my error (too many link) is resolved when changed my usb cable but my problem that need flash after 3-5 days
please help to solved it
my frimware is
XT1068_TITAN_RETAILDSDS_6.0_MPB24.65-34-3_cid7_CFC.xml
thanks
Click to expand...
Click to collapse
make sure you have motorola drivers installed https://motorola-global-en-aus.custhelp.com/app/answers/prod_detail/a_id/86934/p/154,153
make sure adb is up to date, you can use this https://forum.xda-developers.com/showthread.php?t=2317790
You want to flash stock rom again? You have to know, that you must follow exact steps, else it fails.
I would recommend you to re-flash stock ROM and if it still breaks after 3-5 days, you know something is faulty with your hardware.
-- re-flashing stock rom, will erase ALL your data + internal storage, backup all your data to SD first!
You can get latest stock rom for your device here: https://firmware.center/firmware/ make sure its xt1068 model and for your country/region
reboot to bootloader, connect to pc,
in cmd, type
Code:
fastboot devices
-> it should show your device, proceed:
Code:
fastboot.exe flash partition gpt.bin
fastboot.exe flash motoboot motoboot.img
fastboot.exe flash logo logo.bin
fastboot.exe flash boot boot.img
fastboot.exe flash recovery recovery.img
fastboot.exe flash system system.img_sparsechunk.0
fastboot.exe flash system system.img_sparsechunk.1
fastboot.exe flash system system.img_sparsechunk.2
fastboot.exe flash system system.img_sparsechunk.3
fastboot.exe flash modem NON-HLOS.bin
fastboot.exe erase modemst1
fastboot.exe erase modemst2
fastboot.exe flash fsg fsg.mbn
fastboot.exe erase cache
fastboot.exe erase userdata
-> you need to follow exact the flashing steps, else it might fail! (if you have ...sparsechunk.4 or even .5 flash it also)
-> TWRP is a custom recovery. You dont need it, if you want to install a custom rom, you need TWRP.
peace & good luck!
bejunk said:
make sure you have motorola drivers installed https://motorola-global-en-aus.custhelp.com/app/answers/prod_detail/a_id/86934/p/154,153
make sure adb is up to date, you can use this https://forum.xda-developers.com/showthread.php?t=2317790
You want to flash stock rom again? You have to know, that you must follow exact steps, else it fails.
I would recommend you to re-flash stock ROM and if it still breaks after 3-5 days, you know something is faulty with your hardware.
-- re-flashing stock rom, will erase ALL your data + internal storage, backup all your data to SD first!
You can get latest stock rom for your device here: https://firmware.center/firmware/ make sure its xt1068 model and for your country/region
reboot to bootloader, connect to pc,
in cmd, type
Code:
fastboot devices
-> it should show your device, proceed:
Code:
fastboot.exe flash partition gpt.bin
fastboot.exe flash motoboot motoboot.img
fastboot.exe flash logo logo.bin
fastboot.exe flash boot boot.img
fastboot.exe flash recovery recovery.img
fastboot.exe flash system system.img_sparsechunk.0
fastboot.exe flash system system.img_sparsechunk.1
fastboot.exe flash system system.img_sparsechunk.2
fastboot.exe flash system system.img_sparsechunk.3
fastboot.exe flash modem NON-HLOS.bin
fastboot.exe erase modemst1
fastboot.exe erase modemst2
fastboot.exe flash fsg fsg.mbn
fastboot.exe erase cache
fastboot.exe erase userdata
-> you need to follow exact the flashing steps, else it might fail! (if you have ...sparsechunk.4 or even .5 flash it also)
-> TWRP is a custom recovery. You dont need it, if you want to install a custom rom, you need TWRP.
peace & good luck!
Click to expand...
Click to collapse
thanks for replying
i flashing with this metod to many about 50rd but after 3-5 days mobile is restarting and some of program is stoping (google play service and other progrm)then i know that mobile is after some restart stop on boot and after boot page show black page then i start to flashing again with above method and i download all of latest frimeware and flash it
now i thinking my emmc have problem?
thanks
amir58hz said:
thanks for replying
i flashing with this metod to many about 50rd but after 3-5 days mobile is restarting and some of program is stoping (google play service and other progrm)then i know that mobile is after some restart stop on boot and after boot page show black page then i start to flashing again with above method and i download all of latest frimeware and flash it
now i thinking my emmc have problem?
thanks
Click to expand...
Click to collapse
Can you make a picture of your bootloader? And can you post me the name of the update you allways flash?
Im not sure, but that really sounds like emmc is faulty... I mean above method makes sure all is good with software, so can be only HW. Its typical, when itcomes to write to some damaged cluster of emmc, all gets f#+"ed up & it than cant start again. Hmm if it happens again, i would try to first format internal fully, maybe it gets fixed.
For formatiing internal storage, you need TWRP (recovery), to install it:
1. unlock your bootloader here: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
2. download latest TWRP here https://dl.twrp.me/titan/
3. connect to bootloader then type:
Code:
fastboot flash recovery twrp-3.2.3-0-titan.img
after it flashes, choose "recovery" in bootloader using volume down. Volume up selects.
In TWRP enable modifies to system if asked
then in WIPE tab choose advanced & format Internal.
You can then reboot to system. Hopefully it goes well then.
If not, you can try install a custom ROM, but honestly, if the emmc broken it will probably not help.
Also if you are very experienced/know someone you could try located the exact location of broken clusters & then exclude them from filesystem, but this is very hard to examine...
Peace!
bejunk said:
Can you make a picture of your bootloader? And can you post me the name of the update you allways flash?
Im not sure, but that really sounds like emmc is faulty... I mean above method makes sure all is good with software, so can be only HW. Its typical, when itcomes to write to some damaged cluster of emmc, all gets f#+"ed up & it than cant start again. Hmm if it happens again, i would try to first format internal fully, maybe it gets fixed.
For formatiing internal storage, you need TWRP (recovery), to install it:
1. unlock your bootloader here: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
2. download latest TWRP here https://dl.twrp.me/titan/
3. connect to bootloader then type:
Code:
fastboot flash recovery twrp-3.2.3-0-titan.img
after it flashes, choose "recovery" in bootloader using volume down. Volume up selects.
In TWRP enable modifies to system if asked
then in WIPE tab choose advanced & format Internal.
You can then reboot to system. Hopefully it goes well then.
If not, you can try install a custom ROM, but honestly, if the emmc broken it will probably not help.
Also if you are very experienced/know someone you could try located the exact location of broken clusters & then exclude them from filesystem, but this is very hard to examine...
Peace!
Click to expand...
Click to collapse
my frimware is: XT1068_TITAN_RETAILDSDS_6.0_MPB24.65-34-3_cid7_CFC.xml
thi is my boot picture:
https://photoland.io/i/2mQe79
https://photoland.io/i/2mQuFx
https://photoland.io/i/2mQ0qZ
amir58hz said:
my frimware is: XT1068_TITAN_RETAILDSDS_6.0_MPB24.65-34-3_cid7_CFC.xml
thi is my boot picture:
https://photoland.io/i/2mQe79
https://photoland.io/i/2mQuFx
https://photoland.io/i/2mQ0qZ
Click to expand...
Click to collapse
Thx. But i need a picture of bootloader screen, see my picture!
-> hmm in your case i would try it now with formatting internal completly.. But even better would be full formating, so when you have TWRP:
- format Internal storage
- then tick system + data + cache and format them.
- You have to reflash stock then OR (i recommend) try it with a custom rom, like you said allready tried stock many times...
To install custom rom, get these files
ROM: https://forum.xda-developers.com/moto-g-2014/orig-development/rom-lineageos-15-1-t3786749 get latest build
GApps: https://opengapps.org/ choose ARM -> 8.1 -> nano version
put everything in sdcard or storage (after wiping it)
Then in TWRP -> factory reset in wipe menu -> install ROM zip -> install GApps -> reboot. 1st boot can take some time. Test & report.
EDIT: I read in other threads who have the same problem, that they have a wrong recovery or things dont get flashed..
Did in commandline window, when you execute a command get a [OKAY] in terminal after EVERY operation?
EDIT2: Your rom file seems okay. If you are sure that you have xt1068, i would try it with formatting internal, see above. When you unlock bootloader, it will completly wipe your device! Backup stuff 1st!
good luck
bejunk said:
Thx. But i need a picture of bootloader screen, see my picture!
EDIT: I read in other threads who have the same problem, that they have a wrong recovery or things dont get flashed..
Did in commandline window, when you execute a command get a [OKAY] in terminal after EVERY operation?
EDIT2: Your rom file seems okay. If you are sure that you have xt1068, i would try it with formatting internal, see above. When you unlock bootloader, it will completly wipe your device! Backup stuff 1st!
good luck
Click to expand...
Click to collapse
sorry for my mistake
yes is that xt1068 and after flashing all of step is ok and finished wirted in fastboot command
now in recovery twrp format all thing and flash it
https://photoland.io/i/2mQyAW
amir58hz said:
sorry for my mistake
yes is that xt1068 and after flashing all of step is ok and finished wirted in fastboot command
now in recovery twrp format all thing and flash it
https://photoland.io/i/2mQyAW
Click to expand...
Click to collapse
Yeah i updated my post, i would really recommend to try a custom rom and see how its there... But full format 1st..
You can allways go back to stock, so its worth a try..
I will be afk for some time now, good luck, bro :good:
bejunk said:
Yeah i updated my post, i would really recommend to try a custom rom and see how its there... But full format 1st..
You can allways go back to stock, so its worth a try..
I will be afk for some time now, good luck, bro :good:
Click to expand...
Click to collapse
Thanks very much
I dont have custom rom can you advise me to download it
I flashed it if is not have problem is very good but it crash and dont work i send here my problem
Thanks again good luck
bejunk said:
Yeah i updated my post, i would really recommend to try a custom rom and see how its there... But full format 1st..
You can allways go back to stock, so its worth a try..
I will be afk for some time now, good luck, bro :good:
Click to expand...
Click to collapse
hi man
after one day mobile is work true thanks alot
after 3 days restart phone but then stop in black page
now flash again
what is my problem?
amir58hz said:
after 3 days restart phone but then stop in black page
now flash again
what is my problem?
Click to expand...
Click to collapse
So you flashed custom ROM -> it worked for 3 days normal -> then black screen (page) ??
When yes, probably something with your HW is faulty (most likely the eMMC has a bad block or something..)
bejunk said:
So you flashed custom ROM -> it worked for 3 days normal -> then black screen (page) ??
When yes, probably something with your HW is faulty (most likely the eMMC has a bad block or something..)
Click to expand...
Click to collapse
No i flash it with same my frimware
Now for flashing with custom rom it need download rom android8?
i have this error in wipping and installing rombut instal it
my error is:
e:recv error on uevent
But now flashed to 8.1 android
Thanks
Hoping I could get some help for this old phone. I've spent over 5 hours trying to get twrp installed and having no success in what should be one of the quickest steps in the whole rooting/flashing game. Reaching out for help before I lose my mind...
I've tried 2 different builds of oreo and 2 different builds of pie (all stock) and for each build I flashed different twrp versions from this link https://androidfilehost.com/?w=files&flid=232371. I even tried the android 9/10 versions on the android 8 builds. No errors in fastboot. If I try using power plus either of the volume keys it just boots right to android. If I try using the fastboot command (fastboot boot recovery.img) it freezes at the Sony logo. Doesn't seem to be an issue with twrp because I couldn't find a single mention of anyone else having this issue in any of the threads I've read while trying to troubleshoot. Any suggestions?
Is your bootloader locked?
betacrypt said:
Is your bootloader locked?
Click to expand...
Click to collapse
Oh, right, I should have mentioned that it's definitely unlocked. I checked in the service menu and I get the warning at startup.
Hmm what android version are you running currently, latest stock pie? It's possible your recovery partition is corrupt somehow.
Open up a terminal for fastboot and try running:
fastboot format recovery
or
fastboot erase recovery
then
fastboot flash recovery twrp-3.3.1-0-lilac-pie-5.img
I used twrp-3.3.1-0-lilac-pie-5.img on my device so I can confirm that one is definitely working.
betacrypt said:
Hmm what android version are you running currently, latest stock pie? It's possible your recovery partition is corrupt somehow.
Open up a terminal for fastboot and try running:
fastboot format recovery
or
fastboot erase recovery
then
fastboot flash recovery twrp-3.3.1-0-lilac-pie-5.img
I used twrp-3.3.1-0-lilac-pie-5.img on my device so I can confirm that one is definitely working.
Click to expand...
Click to collapse
So I managed to get this working. I tried the fastboot erase command but still had no success. Googled "fastboot erase twrp" or something like that and found a thread discussing how twrp was suspected of corrupting someone's data partition and running a "fastboot erase userdata" command to reformat the partition. I didn't think this would help my situation but figured I had nothing to lose at this point. Ran the "erase userdata" command, set up the phone again, but had no success at first.
I re-ran the "erase recovery" command and had no success with twrp 3.3.1. Then I tried 3.2.1 and initially had no success with hardware buttons or the "boot recovery" command. What I did this final time though, which I don't think I did on my previous attempts, was that instead of going back immediately and trying to re-flash twrp after the frozen sony screen, I gave up this time. BUT....I also said "f* it...let me try booting into recovery with the hardware buttons one last time." Lo and behold, I finally got into twrp!
I don't know if running the "erase recovery" command is what was needed, or it was just some quirky glitch where I needed the phone to freeze. Nevertheless, many thanks for responding and prompting me to make the last few attempts. Flashed magisk with no issue afterwards.
I want to flash arrow os for sanders moto g5s plus but after flashing my imei and signal were gone so i flashed stock and got imei and signal back but i want to flash arrow os and restore twrp only efs and persist. but the only twrp which has option to backup persist is this https://unofficialtwrp.com/update-unofficial-twrp-3-3-1-for-moto-g5s-plus/ but everytime i flash , it gets encrypted and i have to format data but after formatting data and i reboot into system so after rebooting i go to fastboot mode and then go into recovery mode but it goes to stock instead of twrp i flashed earlier so to get into twrp i have to flash it again and after flashing it again, it gets encrypted and again i have to format data so i am unable to make backup of persist and efs, i alreday have persist and modemst1 and modemst2 bin files but i dont know how to flash them
this encryption problem only occurs in twrp 3.3.1-0 not in previous but the previous versions dont have option to backup persist
Vinay425003 said:
I want to flash arrow os for sanders moto g5s plus but after flashing my imei and signal were gone so i flashed stock and got imei and signal back but i want to flash arrow os and restore twrp only efs and persist. but the only twrp which has option to backup persist is this https://unofficialtwrp.com/update-unofficial-twrp-3-3-1-for-moto-g5s-plus/ but everytime i flash , it gets encrypted and i have to format data but after formatting data and i reboot into system so after rebooting i go to fastboot mode and then go into recovery mode but it goes to stock instead of twrp i flashed earlier so to get into twrp i have to flash it again and after flashing it again, it gets encrypted and again i have to format data so i am unable to make backup of persist and efs, i alreday have persist and modemst1 and modemst2 bin files but i dont know how to flash them
this encryption problem only occurs in twrp 3.3.1-0 not in previous but the previous versions dont have option to backup persist
Click to expand...
Click to collapse
Twrp - you have to boot back into recovery from twrp after install to get it to stay.
Format data to decrypt phone, after installing rom, flash magisk to keep device from encrypting again.
Phazmos said:
Twrp - you have to boot back into recovery from twrp after install to get it to stay.
Format data to decrypt phone, after installing rom, flash magisk to keep device from encrypting again.
Click to expand...
Click to collapse
And also what is the right way of restoring efs and persist on a rom
Should I do this
TWRP>ARROW OS>MAGISK>BOOT>TWRP>RESTORE EFS AND PERSIST
Vinay425003 said:
And also what is the right way of restoring efs and persist on a rom
Should I do this
TWRP>ARROW OS>MAGISK>BOOT>TWRP>RESTORE EFS AND PERSIST
Click to expand...
Click to collapse
Important part is root after os first, after that it doesn't matter. Best to flash everything in same twrp session
95% of the time persist isn't the problem,
You just need to reflash this from stock
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
sd_shadow said:
95% of the time persist isn't the problem,
You just need to reflash this from stock
Click to expand...
Click to collapse
Let me try again I flashed all the above from stock rom except fsg fsg
sd_shadow said:
95% of the time persist isn't the problem,
You just need to reflash this from stock
Click to expand...
Click to collapse
One more thing that I have noticed is
My baseband shows
M8953_50.59.07.96U(no Sim and imei)
Whereas in stock rom my baseband shows
M8953_50.59.07.96R (this is working)
Also if we edit fstab.qcom from inside the phone with file explorer and remove the force encrypt and verity flag will it remove encryption after reboot
I have a Mi 9t Pro and am stuck in fastboot mode. I am using ADB on MAC OS and do the following
1. ./fastboot flash recovery twrp.img
2. ./fastboot boot twrp.img
and get the following error:
Sending 'boot.img' (65536 KB) OKAY [ 1.614s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
fastboot: error: Command failed
I use the following TWRP:
twrp-3.3.1-32-raphael-raphaelin-mauronofrio.img
The output of the command './fastboot oem device-info' is:
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.006s]
Finished. Total time: 0.006s
Can someone help me to boot into TWRP? What am I doing wrong?
Do you really have unlocked bl?
wpron said:
I have a Mi 9t Pro and am stuck in fastboot mode. I am using ADB on MAC OS and do the following
1. ./fastboot flash recovery twrp.img
2. ./fastboot boot twrp.img
and get the following error:
Sending 'boot.img' (65536 KB) OKAY [ 1.614s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
fastboot: error: Command failed
...
Can someone help me to boot into TWRP? What am I doing wrong?
Click to expand...
Click to collapse
Try the following instead
1. ./fastboot flash recovery twrp.img
2. ./fastboot reboot
Immediately after sending the second command, grab the phone and press and hold volume up. Keeping holding volume up until it boots into recovery.
Robbo.5000 said:
Try the following instead
1. ./fastboot flash recovery twrp.img
2. ./fastboot reboot
Immediately after sending the second command, grab the phone and press and hold volume up. Keeping holding volume up until it boots into recovery.
Click to expand...
Click to collapse
Doesn't work, still boots into fastboot.
I have no experience using macs but I have found this guide, not sure if you've gone through the steps, so please forgive if you have, hopefully it helps
https://droidfeats.com/setup-adb-on-mac/
wpron said:
Doesn't work, still boots into fastboot.
Click to expand...
Click to collapse
What happens if you send the
Code:
fastboot devices
command?
Robbo.5000 said:
What happens if you send the
Code:
fastboot devices
command?
Click to expand...
Click to collapse
I get:
d98183fc fastboot
wpron said:
What happens if you send the
I get:
d98183fc fastboot
Click to expand...
Click to collapse
Your Mac is communicating with the phone OK in fastboot mode.
No idea why you're struggling to install TWRP then.
Have you tried the procedure on Mauronifrio's OP, flashing the modified vbmeta patcher file?
https://forum.xda-developers.com/k2...icial-twrp-xiaomi-redmi-t3944363/post79823568
I've never needed to do this, so couldn't say for certain if that would work or not.
Robbo.5000 said:
Your Mac is communicating with the phone OK in fastboot mode.
No idea why you're struggling to install TWRP then.
Have you tried the procedure on Mauronifrio's OP, flashing the modified vbmeta patcher file?
https://forum.xda-developers.com/k2...icial-twrp-xiaomi-redmi-t3944363/post79823568
I've never needed to do this, so couldn't say for certain if that would work or not.
Click to expand...
Click to collapse
I flashed the stock fastboot MIUIU ROM and repeated the two steps above after which I was able the boot into TWRP.
Now, after wiping cache, system, data and dalvik/ART cache I try to install the Havoc-os-v3.6 which leads to the following error:
ERROR: This package requires vendor from atleast V12.0.0.8.QFKMIXM. Please upgrade firmware and retry!
Update process ended with ERROR: 7
What did I do wrong this time?
wpron said:
I flashed the stock fastboot MIUIU ROM and repeated the two steps above after which I was able the boot into TWRP.
Now, after wiping cache, system, data and dalvik/ART cache I try to install the Havoc-os-v3.6 which leads to the following error:
ERROR: This package requires vendor from atleast V12.0.0.8.QFKMIXM. Please upgrade firmware and retry!
Update process ended with ERROR: 7
What did I do wrong this time?
Click to expand...
Click to collapse
Some ROMs, Havoc included, now check that you have the correct and latest firmware and vendor installed for your phone. For your phone the requirement is that the stable beta MIUI 12 global firmware and vendor files are installed.
You will find a link in the second post of the Havoc thread that has the correct firmware and vendor contained in a single zip file. You need to flash this zip file in TWRP before flashing the Havoc ROM.
Also, when flashing a custom ROM over MIUI you will need to format data in TWRP, to temporarily remove encryption. Follow this to install a custom ROM for the first time over stock MIUI.
Install TWRP
Boot into TWRP
Do a factory reset
Format data - Format not wipe, need to type yes to confirm
Reboot to recovery (TWRP)
Flash required firmware/vendor If needed
Flash custom ROM
Flash GApps if needed/wanted
Boot into the ROM
Everything should be good
Flash Magisk if required
Later, when you want to update the ROM, or flash a different custom ROM, it is recommended to remove lockscreen security before flashing.
Then restore lockscreen security again when finished.
Robbo.5000 said:
Some ROMs, Havoc included, now check that you have the correct and latest firmware and vendor installed for your phone. For your phone the requirement is that the stable beta MIUI 12 global firmware and vendor files are installed.
You will find a link in the second post of the Havoc thread that has the correct firmware and vendor contained in a single zip file. You need to flash this zip file in TWRP before flashing the Havoc ROM.
Can you send me the link to this zip file or thread please?
Also: When I try to reboot into recovery from TWRP, this boots me into fastboot again. Is this step really neccessary?
Click to expand...
Click to collapse
wpron said:
Can you send me the link to this zip file or thread please?
Click to expand...
Click to collapse
https://forum.xda-developers.com/k20-pro/development/rom-havoc-os-3-3-t4063081/post82237181
It's at the top, you want the file for Global/European/Russian
wpron said:
When I try to reboot into recovery from TWRP, this boots me into fastboot again. Is this step really neccessary?
Click to expand...
Click to collapse
Yes it's necessary, otherwise TWRP doesn't properly mount the data partition after formatting it.
Are you using the reboot menu in TWRP?
After formatting data, go back to the main main and then select the boot menu. From there choose boot to recovery.
One more thing.
If you're trying this after flashing a MIUI fastboot ROM, you must make sure you've booted into MIUI once, to finalise the installation, before you attempt to then flash something else.
Robbo.5000 said:
https://forum.xda-developers.com/k20-pro/development/rom-havoc-os-3-3-t4063081/post82237181
It's at the top, you want the file for Global/European/Russian
Yes it's necessary, otherwise TWRP doesn't properly mount the data partition after formatting it.
Are you using the reboot menu in TWRP?
After formatting data, go back to the main main and then select the boot menu. From there choose boot to recovery.
One more thing.
If you're trying this after flashing a MIUI fastboot ROM, you must make sure you've booted into MIUI once, to finalise the installation, before you attempt to then flash something else.
Click to expand...
Click to collapse
Yes, I formatted data successfully, but after I reboot into recovery, I get into fastboot mode.
Do I need to hold Volume up?
I always have to repeat flashing stock MIUI, unlock bootloader, boot into TWRP again which is tedious.
Is there no way to get into TWRP from fastboot and without flashing stock MIUI?
wpron said:
Yes, I formatted data successfully, but after I reboot into recovery, I get into fastboot mode.
Do I need to hold Volume up?
I always have to repeat flashing stock MIUI, unlock bootloader, boot into TWRP again which is tedious.
Is there no way to get into TWRP from fastboot and without flashing stock MIUI?
Click to expand...
Click to collapse
When flashing stock MIUI, change the flash option at the bottom of the Mi Flash Tool to 'clean all' before flashing. This will keep the bootloader unlocked.
After flashing MIUI you must boot into MIUI once, to finalise the installation, before trying to flash TWRP (or anything else)
Once you've flashed MIUI and booted into it at least once follow the steps in this post again.
https://forum.xda-developers.com/k20-pro/help/xiaomi-mi-9t-pro-boot-twrp-t4121037/post82900241
Do not add any extra steps, do not miss out any steps.
Do not be tempted to wipe any other partitions. Doing the factory reset in TWRP wipes all the necessary partitions.
After formatting data you do NOT need to hold volume up if you choose to reboot to recovery from TWRP
Robbo.5000 said:
When flashing stock MIUI, change the flash option at the bottom of the Mi Flash Tool to 'clean all' before flashing. This will keep the bootloader unlocked.
After flashing MIUI you must boot into MIUI once, to finalise the installation, before trying to flash TWRP (or anything else)
Once you've flashed MIUI and booted into it at least once follow the steps in this post again.
https://forum.xda-developers.com/k20-pro/help/xiaomi-mi-9t-pro-boot-twrp-t4121037/post82900241
Do not add any extra steps, do not miss out any steps.
Do not be tempted to wipe any other partitions. Doing the factory reset in TWRP wipes all the necessary partitions.
After formatting data you do NOT need to hold volume up if you choose to reboot to recovery from TWRP
Click to expand...
Click to collapse
In step 3, by "factory reset", do you mean wipe cache, dalkiv/ART cache and system or is this a different operation?
I think, I can only format data after I wipe cache, dalkiv/ART cache and system?
wpron said:
In step 3, by "factory reset", do you mean wipe cache, dalkiv/ART cache and system or is this a different operation?
I think, I can only format data after I wipe cache, dalkiv/ART cache and system?
Click to expand...
Click to collapse
I mean the swipe to do a factory reset, on the initial wipe menu. It is in the same place as the format data option. You do not need to go in to the advanced wipe option.
Robbo.5000 said:
I mean the swipe to do a factory reset, on the initial wipe menu. It is in the same place as the format data option. You do not need to go in to the advanced wipe option.
Click to expand...
Click to collapse
OK, I was able to reboot into TRRP with your instructions. Now, I cannot find the custom ROMs I previously moved to the device storage via Android File Transfer.
Have these files been removed by the factory reset, should I instead perform an advanced wipe of cache, dalkiv/ART cache and system?
How can I install the custom ROMS if they can not be found on the device after factory reset?
wpron said:
OK, I was able to reboot into TRRP with your instructions. Now, I cannot find the custom ROMs I previously moved to the device storage via Android File Transfer.
Have these files been removed by the factory reset, should I instead perform an advanced wipe of cache, dalkiv/ART cache and system?
How can I install the custom ROMS if they can not be found on the device after factory reset?
Click to expand...
Click to collapse
Formatting data will also wipe internal storage.
TWRP has MTP enabled, so you can access the phone storage from a PC (and I assume Mac) while booted into TWRP. You can also mount a USB OTG drive in TWRP.
Either copy them across from the Mac to the phone while booted in to TWRP after formatting data, or use a USB OTG pen drive for the ROM and other files to be flashed.
Robbo.5000 said:
Formatting data will also wipe internal storage.
TWRP has MTP enabled, so you can access the phone storage from a PC (and I assume Mac) while booted into TWRP. You can also mount a USB OTG drive in TWRP.
Either copy them across from the Mac to the phone while booted in to TWRP after formatting data, or use a USB OTG pen drive for the ROM and other files to be flashed.
Click to expand...
Click to collapse
Worked! I have now Havoc-OS on my Mi 9t pro. Thank you a lot for your help!