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!
Related
Hi I need help,
1. I used "Huawei update etractor" to create fleshable zip from official ROM (boot.img, system.img, cache,img, cust.img, userdata.img)
2. I flashed this zip via TWRP
3. after reboot is phone in BOOTLOOP and recovery(volume + and powerbutton ) dont work and ADB dont work too,
4. BOOTLOADER is UNLOCKED still
5. fastboot is working BUT I tried flash (boot.img and recovery.img) from many ROMs this is unsucessfully
Exist some solution for me?
I have HUAWEI ASCEND P7-L10
Could you still enter twrp(after flashing)?
Try to wipe everything and than flash all images via fastboot
But it should be the same version as you previously installed, otherwise it won't work
RangerP7 said:
Could you still enter twrp(after flashing)?
Try to wipe everything and than flash all images via fastboot
But it should be the same version as you previously installed, otherwise it won't work
Click to expand...
Click to collapse
THX for answer.
I cannot enter to twrp after flashed.
How can I wipe everything when I have available only fastboot.?
I don't know previously version. I tried flash images via fastboot several ROMS - without successfully.
Problem is in flash ROM version only ? really? If is it true I will be flash all rom order by version
Try to enter twrp via fastboot
"fastboot boot (YourTWRPName).img"
Could you now enter twrp?
Otherwise you can try (for wipe partitions)
"fastboot erase (partition = data, cache, system, boot)"
(do not type() )
And you need to flash the version you had previously installed... Don't flash any other roms or other versions... It won't work
RangerP7 said:
Try to enter twrp via fastboot
"fastboot boot (YourTWRPName).img"
Could you now enter twrp?
Otherwise you can try (for wipe partitions)
"fastboot erase (partition = data, cache, system, boot)"
(do not type() )
And you need to flash the version you had previously installed... Don't flash any other roms or other versions... It won't work
Click to expand...
Click to collapse
C:\adb>fastboot boot TWRP-2.8.7.0.img
downloading 'boot.img'...
OKAY [ 0.512s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.522s
C:\adb>fastboot erase boot
erasing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.003s
i cannot enter to twrp.
After flash previously instaled version rom ->> it is Without progress ->> Phone is in bootloop still
soki.niva said:
C:\adb>fastboot boot TWRP-2.8.7.0.img
downloading 'boot.img'...
OKAY [ 0.512s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.522s
Click to expand...
Click to collapse
Are your drivers correctly installed?
Is your bootloader really unlocked?
Did you previously installed Android 5.1 (B852/839)?
So you need to flash the version 3.0.0-0 of twrp
RangerP7 said:
Are your drivers correctly installed?
Is your bootloader really unlocked?
Did you previously installed Android 5.1 (B852/839)?
So you need to flash the version 3.0.0-0 of twrp
Click to expand...
Click to collapse
Yes is unlocked. If I reboot into bootloader There it is red title "PHONE UNLOCKED"
And comands "fastboot -S 512M flash boot boot.img" finished without fail...
1.. step: STOCK installed B129
2. step: i flash custom rom "Miui_HP7_4.9.18_GER_longest" via twrp -> all functionally after this step.
3.step. I flash "P7-L10C900B852_eu_channel_SW (wirhout recovery.img)"" via twrp -> BOOTLOOP(and recovery no work) after this step
twrp 3.0.0-0 not work too.
-maybe I use bad key combination for enter to recovery? (i use VOLUME UP + POWER BUTTON) or (VOLUME UP DOWN +POWERBUTTON)
Thats very strange...
Actually I don't know what to do now
I never had this problems
Did the B129 work without bootloop?
What exactly is B129?
I'm from Europe the first version I had on this phone was B126/B133
RangerP7 said:
Thats very strange...
Actually I don't know what to do now
I never had this problems
Did the B129 work without bootloop?
What exactly is B129?
I'm from Europe the first version I had on this phone was B126/B133
Click to expand...
Click to collapse
B129 is Vodafone version and worked without bootloop.
do you have any idea?
soki.niva said:
B129 is Vodafone version and worked without bootloop.
do you have any idea?
Click to expand...
Click to collapse
So your phone was branded before?
Now it would make sense why you can not install any other software...
You need to use original Vodafone software not the free public versions
But why twrp is not working... I don't know...
RangerP7 said:
So your phone was branded before?
Now it would make sense why you can not install any other software...
You need to use original Vodafone software not the free public versions
But why twrp is not working... I don't know...
Click to expand...
Click to collapse
I read other post, problem was made :
I created fleshable zip(via huawei extractor), BUT with bad profile(ASCEND P6 profile) because profile for P7 is missing.
Is it any solution for me?
Could you flash the images via fastboot?
RangerP7 said:
Could you flash the images via fastboot?
Click to expand...
Click to collapse
It appears that is working.
Commands of type: fastboot flash boot boot.img - are finised without error.
And all other images?
recovery data system
Flash them and try now the 3 buttons method
You know how this works?
RangerP7 said:
And all other images?
recovery data system
Flash them and try now the 3 buttons method
You know how this works?
Click to expand...
Click to collapse
I flashed all images (boot,recovery, cache, cust, userdata, and system)
No, I don't know 3 buttons method. What is it ? hold volume up volume down and power button. without changes...
Please I need name of partition for ASCEND P7 -> Do you know? for example : What is number of partition is for recovery partition="/dev/block/mmcblk0pXX" ...?
<File type="recovery" partition="/dev/block/mmcblk0p11">recovery.img</File>
<File type="boot" partition="/dev/block/mmcblk0p12">.boot.img</File>
<File type="system" partition="/dev/block/mmcblk0p16">system.img</File>
<File type="cache" partition="/dev/block/mmcblk0p17">cache.img</File>
<File type="cust" partition="/dev/block/mmcblk0p18">cust.img</File>
<File type="userdata" partition="/dev/block/mmcblk0p19">userdata.img</File>
The 3 buttons method is a direct flash of all partitions
You need to flash the stock recovery, put the full update.app into the dload folder on your external storage and boot up while holding all 3 buttons
But why you can't flash the stock recovery... I don't know... I never had this problems
If you find a fix for this it will be easy to do the rest
But without a working recovery a can't help you... Sorry
soki.niva said:
Yes is unlocked. If I reboot into bootloader There it is red title "PHONE UNLOCKED"
And comands "fastboot -S 512M flash boot boot.img" finished without fail...
1.. step: STOCK installed B129
2. step: i flash custom rom "Miui_HP7_4.9.18_GER_longest" via twrp -> all functionally after this step.
3.step. I flash "P7-L10C900B852_eu_channel_SW (wirhout recovery.img)"" via twrp -> BOOTLOOP(and recovery no work) after this step
twrp 3.0.0-0 not work too.
-maybe I use bad key combination for enter to recovery? (i use VOLUME UP + POWER BUTTON) or (VOLUME UP DOWN +POWERBUTTON)
Click to expand...
Click to collapse
Step 3 is wrong. You cannot flash official Huawei ROMs via custom recovery, even if they've been made bootable by Huawei Update Extractor.
What you need to do is use Update Extractor again to extract RECOVERY.IMG of the ROM that is currently installed on your phone. Then flash it with following command:
fastboot flash recovery RECOVERY.IMG
If that's not sufficient you can try the same thing with BOOT.IMG | SYSTEM.IMG | CUST.IMG
---------- Post added at 04:26 AM ---------- Previous post was at 04:21 AM ----------
RangerP7 said:
The 3 buttons method is a direct flash of all partitions
You need to flash the stock recovery, put the full update.app into the dload folder on your internal storage and boot up while holding all 3 buttons
But why you can't flash the stock recovery... I don't know... I never had this problems
If you find a fix for this it will be easy to do the rest
But without a working recovery a can't help you... Sorry
Click to expand...
Click to collapse
@RangerP7 I believe that the dload folder MUST be on a SD card and not on internal storage as 3 button method wipes internal storage.
Milan-XDA said:
@RangerP7 I believe that the dload folder MUST be on a SD card and not on internal storage as 3 button method wipes internal storage.
Click to expand...
Click to collapse
Sorry my fault... Of cause the external storage
Thank you
RangerP7 said:
Sorry my fault... Of cause the external storage
Thank you
Click to expand...
Click to collapse
I tried but no results... why not solution not work(not exists?)when fastboot menu still works?
What exactly is not working? I (we) cannot help you with no information?
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
I dirty flashed a new version of xiaomi.eu stable build, and it caused TWRP to uninstall itself.
Whenever I hold power on and volume up it just goes to fastboot.
Now I tried reinstalling TWRP like I've done many times before, but it keeps throwing an error. The error I get is when trying to boot without flashing the img. When I do this, I get the error:
Code:
fastboot boot TWRP.img"
downloading 'boot.img'...
OKAY [ 1.609s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.675s
Anyone gotten any ideas on what could be going on here? I'm scared to try anything as my phone currently works, but I need TWRP back to update my phone to a different versions and to install the clock mod again.
Thanks!
Got it to load once, but now back to square one. Throwing same error.
Now when running the command fastboot reboot recovery it's saying
Code:
fastboot: usage: unknown reboot target recovery
And writing 'fastboot boot twrp.img' turns the phone off / makes the screen go black. Fully bricked now as the OS wont load either.
Try on a computer with a USB 2.0 port, or a different usb cable, had the same issue once
Ended up having to reinstall dev rom. Device relocked, so have to wait 15 days again. @BusterBg_18 Thanks, will do when I unlock the device
EDIT: When using Mi Flash tool, make sure to check 'clean all' and not 'clean all and lock' in the bottom right. That's what set me back 2 weeks.
I have the same error. How can I fix this pls?
MrkoZino said:
I have the same error. How can I fix this pls?
Click to expand...
Click to collapse
Flash the latest official rom then start all over again. Follow the post above you about miflash.
Hello, I've had the same problem, then flashed latest dev rom via MiFlash and it booted, but now after I flash any custom ROM in TWRP i have this issue again and need to reflash chinese ROM. How can I flash any custom rom?
i'm stuck in the same issue. stuck in fastboot and it would not load recovery. any fix?
Hi, i fixed the "Failed to load/authenticate boot image: Load Error" by simply restarting the Device.
It seems to appear randomly when flashing partitions and then block all further Transfers.
If the Device loops in Fastboot, the only Solution to me was re flashing the Stock Firmware.
greendra8 said:
And writing 'fastboot boot twrp.img' turns the phone off / makes the screen go black. Fully bricked now as the OS wont load either.
Click to expand...
Click to collapse
I have the same Issue, but reflashing Stock Firmware or making OTA Updates dident helped for me. Ive already tried TWRP and OrangeFox without success. The Screen always turns black and Fastboot stays active in an limited Mode, any Ideas? My host Computer only has 3.0+ Ports only, but ive used an 2.0 Extender so it should be fine?
DJPlaya said:
Hi, i fixed the "Failed to load/authenticate boot image: Load Error" by simply restarting the Device.
It seems to appear randomly when flashing partitions and then block all further Transfers.
If the Device loops in Fastboot, the only Solution to me was re flashing the Stock Firmware.
I have the same Issue, but reflashing Stock Firmware or making OTA Updates dident helped for me. Ive already tried TWRP and OrangeFox without success. The Screen always turns black and Fastboot stays active in an limited Mode, any Ideas? My host Computer only has 3.0+ Ports only, but ive used an 2.0 Extender so it should be fine?
Click to expand...
Click to collapse
long time ago now. but i remember at one point having to flash the stock firmware using the mi unlock tool. i also remember trying every single version of twrp and rom until one finally worked. sorry i can't help much but i believe that's how i eventually fixed it.
hi, I've experienced with the same thing.
this methode help me out from it.
try to reflashing some file image from the rom where youre want to install in hh with adb.
copy this files below from rom image to adb folder
1. system.img (command in adb >> fastboot flash system system.img)
2. boot.img (command in adb like #1, change the name of img file) do till #6
3. vendor.img
4. dtbo.img
5. cust.img
6. misc.img
7. now flashing twrp/recovery.img (choose twrp compatible with rom you want to install) with adb
8. the "fastboot boot recovery.img" with adb
9. flashing the rom by twrp
Marihot said:
hi, I've experienced with the same thing.
this methode help me out from it.
try to reflashing some file image from the rom where youre want to install in hh with adb.
copy this files below from rom image to adb folder
1. system.img (command in adb >> fastboot flash system system.img)
2. boot.img (command in adb like #1, change the name of img file) do till #6
3. vendor.img
4. dtbo.img
5. cust.img
6. misc.img
7. now flashing twrp/recovery.img (choose twrp compatible with rom you want to install) with adb
8. the "fastboot boot recovery.img" with adb
9. flashing the rom by twrp
Click to expand...
Click to collapse
Where do you get these .img files?
iconoclasthero said:
Where do you get these .img files?
Click to expand...
Click to collapse
all img files come from the official rom china stable V12.0.2.0.QEBCNXM (.tgz), download and extract the tgz file then find img files from images folder
Marihot said:
all img files come from the official rom china stable V12.0.2.0.QEBCNXM (.tgz), download and extract the tgz file then find img files from images folder
Click to expand...
Click to collapse
Please tell the details for this method
greendra8 said:
Ended up having to reinstall dev rom. Device relocked, so have to wait 15 days again. @BusterBg_18 Thanks, will do when I unlock the device
EDIT: When using Mi Flash tool, make sure to check 'clean all' and not 'clean all and lock' in the bottom right. That's what set me back 2 weeks.
Click to expand...
Click to collapse
BROOOOOOOOOO HAHAHAHAHAHA I LITERALLY JUST READ YOUR COMMENT AND 10 SECONDS LATER I FLASH THE ROM WITH "CLEAN ALL AND LOCK" Im a f-king dumb bro
Marihot said:
你好，我也经历过同样的事情。
这个方法帮助我摆脱它。
尝试使用 adb 从要在 hh 中安装的 rom 中重新刷新一些文件映像。
将下面的文件从 rom 映像复制到 adb 文件夹
1.system.img（adb >> fastboot flash system system.img中的命令）
2. boot.img（adb 中的命令，如#1，更改 img 文件的名称）直到 #6
3. 供应商.img
4.dtbo.img
5. 自定义.img
6. 杂项.img
7. 现在用adb刷twrp/recovery.img（选择twrp与你要安装的rom兼容）
8. adb 的“fastboot boot recovery.img”
9. twrp刷入rom
Click to expand...
Click to collapse
Thank you, brother
try fastboot set_active a
or fastboot set_active b
Hello all.
Here is my problem
I successfully unlocked my bootloader and I flashed latest maunofrio twrp v35
In TWRP, I did a full wipe in TWRP and formatted data partition to remove encryption
But now, I can't boot again in twrp and I'm stucked in fastboot.
Vol UP + power does not boot in twrp but still in fastboot..
When I hit the command : fastboot flash recovery recovery.img, it says OK
But fastboot boot recovery.img no longer workos now, failed
( before wiping and formatting all it worked )
I don't know what to do now to access twrp..
Any help is very appreciated
Greetings
Try another recovery and if it failed try full flash latest stable rom
Well, I have been warning so many times that use any TWRP in MI9:
1. format data partition
2. reboot TWRP and then enter twrp. Make twrp mount data partition
3. wipe everything BUT please keep system partition only
4. reboot twrp and then enter twrp again
5. Now wipe system partition and then flash any rom you want
6. reboot
How to save your phone now ? Please try fastboot ROM and use miflash app to save your phone !
Kris
ManuBBXX said:
Hello all.
Here is my problem
I successfully unlocked my bootloader and I flashed latest maunofrio twrp v35
In TWRP, I did a full wipe in TWRP and formatted data partition to remove encryption
But now, I can't boot again in twrp and I'm stucked in fastboot.
Vol UP + power does not boot in twrp but still in fastboot..
When I hit the command : fastboot flash recovery recovery.img, it says OK
But fastboot boot recovery.img no longer workos now, failed
( before wiping and formatting all it worked )
I don't know what to do now to access twrp..
Any help is very appreciated
Greetings
Click to expand...
Click to collapse
@Kris Chen I am in similar situation here... Can you please help?
First of all - which TWRP should we use for Mi9T? IS this one good? https://mifirm.net/model/davinci.ttt#other-twrp
After flashing recovery-TWRP-3.3.1-0607-REDMI_K20-CN-wzsx150.img - fastboot boot twrp.img goes okay
And then after "fastboot boot twrp.img" the phone restarts and is just stuck on the "semitransparent" MI logo...
I can press Vol+- and power buttons and boot into Mi 3 recovery, wipe data, set up the phone again. And then it is all over again. I am new to this and probably making some basic mistake?
EDIT. I think the mistake was to trying to use a wrong TWRP...
Some questions here:
1. Is Redmi K20 CN the same as Mi9T?
If yes, that twrp is correct and the best one
2.After flashing twrp, can you enter twrp by general
method : power + volume up to enter twrp?
If yes, I think the problem is coming from your data
partition. Please format your data partition first and
then reboot to Twrp again. Then copy your rom in your
phone and then wipe cache/ dalvik cache/system. Next
to flash rom. Always Remeber not to reboot your
phone if you haven't flashed rom under twrp after
flashing system partition.
Kris
Ardysan said:
@Kris Chen I am in similar situation here... Can you please help?
First of all - which TWRP should we use for Mi9T? IS this one good? https://mifirm.net/model/davinci.ttt#other-twrp
After flashing recovery-TWRP-3.3.1-0607-REDMI_K20-CN-wzsx150.img - fastboot boot twrp.img goes okay
And then after "fastboot boot twrp.img" the phone restarts and is just stuck on the "semitransparent" MI logo...
I can press Vol+- and power buttons and boot into Mi 3 recovery, wipe data, set up the phone again. And then it is all over again. I am new to this and probably making some basic mistake?
EDIT. I think the mistake was to trying to use a wrong TWRP...
Click to expand...
Click to collapse
Thank you Kris!
Download the fastboot rom (Google it )then flash it with miflashtool just make sure the archive of the ROM is "tgz"before you unzip it .
Failykun said:
Download the fastboot rom (Google it )then flash it with miflashtool just make sure the archive of the ROM is "tgz"before you unzip it .
Click to expand...
Click to collapse
This is what I had to do both times this happened.
I have the same exact problem
I used the same TWRP and I also wiped system.
Did you fixed it already?
RebornCheiko said:
I have the same exact problem
I used the same TWRP and I also wiped system.
Did you fixed it already?
Click to expand...
Click to collapse
As i understand, you wiped system and then restarted? And now you can enter only fastboot?
When you wipe system you must flash a ROM without restart or after restart, only fastboot available. TWRP version has nothing to do with this.
Now you must use mi flash or adb and fastboot utility. Download fastboot version of ROM, then open archive and flash it using mi flash or flash_all.bat script. flash_all_lock.bat will also lock your bootloader and mi flash has that option too, so check twice what option you choose
After flashing ROM you can flash TWRP again and it will be available, because by flashing ROM you restored system
I had the same problem.
Try to flash vbmeta.img via fastboot (fastboot --disable-verity flash vbmeta vbmeta.img) and then flash recovery then boot recovery.
Or try to flash boot.img (fastboot flash boot boot.img) then flash recovery.
ManuBBXX said:
Hello all.
Here is my problem
I successfully unlocked my bootloader and I flashed latest maunofrio twrp v35
In TWRP, I did a full wipe in TWRP and formatted data partition to remove encryption
But now, I can't boot again in twrp and I'm stucked in fastboot.
Vol UP + power does not boot in twrp but still in fastboot..
When I hit the command : fastboot flash recovery recovery.img, it says OK
But fastboot boot recovery.img no longer workos now, failed
( before wiping and formatting all it worked )
I don't know what to do now to access twrp..
Any help is very appreciated
Greetings
Click to expand...
Click to collapse
I got you chief. Make sure you have adb and fastboot installed.
No you don't need Mi flash tool for this. All you need is a computer.
Go to fastboot mode, plug in your device and expand cepheus.tgz file you downloaded. Link below
https://xiaomifirmwareupdater.com/
Now open the folder. You have the flash_all files in there. Any .bat file is for Windows only. Any .sh files are for Mac and Linux.
Make sure the device is recognized in fastboot via cmd or terminal
WINDOWS ONLY: Open Command prompt and drag flash_all.bat into the cmd window and press enter
MAC/LINUX: Open terminal and drag flash_all.sh into the terminal window and press enter.
This part requires some patience. Wait until everything is finished.
Reboot using power button and it should be back to normal.
How to install stock rom after formatting all partitions like "adb fastboot format userdata" (including system, boot), download mode won't work, right?
I will do this process on an unrooted device.
Use Odin to flash the firmware in download mode.
V0latyle said:
Use Odin to flash the firmware in download mode.
Click to expand...
Click to collapse
"I think the download mode feature will not work because I will use the following commands to format the partitions:
fastboot format userdata
fastboot format cache
fastboot format system
fastboot format boot
fastboot format recovery
since I am formatting the boot partition."
V0latyle said:
Use Odin to flash the firmware in download mode.
Click to expand...
Click to collapse
Basically, does the download mode get damaged?
FATDROIDA said:
Basically, does the download mode get damaged?
Click to expand...
Click to collapse
no, you didnt erase the bootloader(hope you didnt)
FATDROIDA said:
"I think the download mode feature will not work because I will use the following commands to format the partitions:
fastboot format userdata
fastboot format cache
fastboot format system
fastboot format boot
fastboot format recovery
since I am formatting the boot partition."
Click to expand...
Click to collapse
It is a Samsung device. The proper way to flash firmware is by using Odin. Samsung does not use the same fastboot command procedure as AOSP model devlices such as the Pixel. You use Odin to flash partitions on the device, including recovery. If you flash a custom recovery such as TWRP, you can then install custom boot and system images.
If you don't know what you're doing, or what effect it will have, you probably shouldn't be doing it.
Hichem2006 said:
no, you didnt erase the bootloader(hope you didnt)
Click to expand...
Click to collapse
I want to clean all the disk space on my device and install a fresh stock ROM. I'm still in the planning stage and haven't done anything yet. My device is unrooted.
V0latyle said:
It is a Samsung device. The proper way to flash firmware is by using Odin. Samsung does not use the same fastboot command procedure as AOSP model devlices such as the Pixel. You use Odin to flash partitions on the device, including recovery. If you flash a custom recovery such as TWRP, you can then install custom boot and system images.
If you don't know what you're doing, or what effect it will have, you probably shouldn't be doing it.
Click to expand...
Click to collapse
oh yeah totally forgot about it, Samsung phones don't have a fastboot interface