Related
i have read that if you wipe the boot partition (not bootloader) and try to reboot before flashing a boot image. the device will not boot. i was surprised to read this because i thought as long as the bootloader was intact you would be able to get into fastboot/bootloader mode. i thought the boot partition was just the android kernel/ramdisk, and that there was a separate bootloader partition for the bootloader
but i think this is wrong
so if i run this:
Code:
fastboot format boot
fastboot reboot-bootloader
i wont be able to boot into android, but i'll still be able to get into recovery and fastboot modes, right?
gnarlycs said:
i have read that if you wipe the boot partition (not bootloader) and try to reboot before flashing a boot image. the device will not boot. i was surprised to read this because i thought as long as the bootloader was intact you would be able to get into fastboot/bootloader mode. i thought the boot partition was just the android kernel/ramdisk, and that there was a separate bootloader partition for the bootloader
but i think this is wrong
so if i run this:
Code:
fastboot format boot
fastboot reboot-bootloader
i wont be able to boot into android, but i'll still be able to get into recovery and fastboot modes, right?
Click to expand...
Click to collapse
What exactly are you trying to accomplish here?
You can wipe the boot partition, but you cannot wipe the BOOTLOADER.
If you wipe the bootloader, you'll be screwed.
The bootloader is on a partition called "aboot".
Interestingly, Nexus 6 has a second aboot partition named "abootBackup". Wonder what's up with that...?
doitright said:
You can wipe the boot partition
Click to expand...
Click to collapse
I'm curious. What would be the reason to wipe boot partition?
cam30era said:
I'm curious. What would be the reason to wipe boot partition?
Click to expand...
Click to collapse
Sometimes just to clear out anything before an install of a new kernel - if some kernel put something special there. I never do it personally but it can be done, but you should flash another kernel immediately. No need to reboot the bootloader.
I would bring my Nexus 6 to the stock...to have a phone completely clean, can I do (with the toolkit) the various erase boot, cache, recovery, system, userdata? And then flash, even with the tool, the stock ROM? I would not make mistakes
hollywood_jack said:
I would bring my Nexus 6 to the stock...to have a phone completely clean, can I do (with the toolkit) the various erase boot, cache, recovery, system, userdata? And then flash, even with the tool, the stock ROM? I would not make mistakes
Click to expand...
Click to collapse
Or do it manualy with adb, look here as a guide http://forum.xda-developers.com/nexus-6/general/guide-properly-prepare-nexus-6-resale-t3104504 method 2. Toolkits will always bite you in the ass at some point in the future
gee2012 said:
Toolkits will always bite you in the ass at some point in the future
Click to expand...
Click to collapse
Sorry but I not have understood this
hollywood_jack said:
Sorry but I not have understood this
Click to expand...
Click to collapse
If you use automated software to flash or alter the OS or parts of it you don`t understand whats going on and if something goes wrong you will not be able to solve the issue because you don`t know what went wrong
gee2012 said:
If you use automated software to flash or alter the OS or parts of it you don`t understand whats going on and if something goes wrong you will not be able to solve the issue because you don`t know what went wrong
Click to expand...
Click to collapse
Ok :good:
But in this page http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008 I read only erase cache...can I do, in the same way, all erase (boot, cache, recovery, system, userdata)?
hollywood_jack said:
Ok :good:
But in this page http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008 I read only erase cache...can I do, in the same way, all erase (boot, cache, recovery, system, userdata)?
Click to expand...
Click to collapse
Some more info please: do you have stock rom, recovery, kernel and are you rooted?
If the answer is yes to the above just:
- fastboot erase system
- fastboot flash system system.img
- data factory reset in recovery
- reboot and you`re done.
gee2012 said:
Some more info please: do you have stock rom, recovery, kernel and are you rooted?
If the answer is yes to the above just:
- fastboot erase system
- fastboot flash system system.img
- data factory reset in recovery
- reboot and you`re done.
Click to expand...
Click to collapse
I have stock rom with TWRP recovery...then I have multirom app with (I think) modified kernel
hollywood_jack said:
I have stock rom with TWRP recovery...then I have multirom app with (I think) modified kernel
Click to expand...
Click to collapse
Then after you flash system.img (look in my previous post)you also flash boot.img and recovery.img
gee2012 said:
Then after you flash system.img (look in my previous post)you also flash boot.img and recovery.img
Click to expand...
Click to collapse
Thanks gee2012...you are very exhaustive :good:
Only another little question: can I erase cache and userdata? Or is better to use the format command? What is the difference between format and erase?
hollywood_jack said:
Thanks gee2012...you are very exhaustive :good:
Only another little question: can I erase cache and userdata? Or is better to use the format command? What is the difference between format and erase?
Click to expand...
Click to collapse
I always use the erase command, but i guess format will work too. The outcome should be the same And if you flash userdata it will erase userdata before the flash automaticaly, so no need to erase/format.
gee2012 said:
I always use the erase command, but i guess format will work too. The outcome should be the same And if you flash userdata it will erase userdata before the flash automaticaly, so no need to erase/format.
Click to expand...
Click to collapse
Sorry my friend for a new question but I have many doubts about the factory image flash, I'm a newbie
I would flash also the original bootloader and now my question is this: after the flash the original bootloader and after reboot-bootloader (http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008 method 2) I have a locked bootloader or unlocked bootloader? If the bootloader is locked might I end up in a boot loop with the following flash (always method 2)?
hollywood_jack said:
Sorry my friend for a new question but I have many doubts about the factory image flash, I'm a newbie
I would flash also the original bootloader and now my question is this: after the flash the original bootloader and after reboot-bootloader (http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008 method 2) I have a locked bootloader or unlocked bootloader? If the bootloader is locked might I end up in a boot loop?
Click to expand...
Click to collapse
First you have to unlock the bootloader and then you can flash the factory image in parts (system, boot, recovery, cache).
Fastboot command in cmd and bootloader/fastboot mode: fastboot oem unlock. Only flash the bootloader and radio if you don`t have the correct BL/radio installed, if you have there os no need to flash it again.
gee2012 said:
First you have to unlock the bootloader and then you can flash the factory image in parts (system, boot, recovery, cache).
Fastboot command in cmd and bootloader/fastboot mode: fastboot oem unlock. Only flash the bootloader and radio if you don`t have the correct BL/radio installed, if you have there os no need to flash it again.
Click to expand...
Click to collapse
Ok, all clear but if I need to flash also the bootloader what would be the correct steps?
hollywood_jack said:
Ok, all clear but if I need to flash also the bootloader what would be the correct steps?
Click to expand...
Click to collapse
Extract the rom and flash the bootloader first (fastboot flash bootloader namebootloader.img) and fastboot reboot-bootloader, then the radio and also reboot and then the rest in one go. Good luck an if you have doubts/problems post it here. Plenty of helpfull members around
But after flash and reboot bootloader can I flash the other factory image parts? The original bootloader that I just flashed not is locked?
Inviato dal mio Nexus 6 utilizzando Tapatalk
hollywood_jack said:
But after flash and reboot bootloader can I flash the other factory image parts? The original bootloader that I just flashed not is locked?
Inviato dal mio Nexus 6 utilizzando Tapatalk
Click to expand...
Click to collapse
Once you unlock the BL it stays unlocked unless you lock it manualy. Even if you flash a new bootloader.
Thanks my friend...thanks alot
with my Nexus 6
hollywood_jack said:
Thanks my friend...thanks alot
with my Nexus 6
Click to expand...
Click to collapse
Good luck, its only a bit stressfull the first time
gee2012 said:
Good luck, its only a bit stressfull the first time
Click to expand...
Click to collapse
Can I flash directly a no force encryption boot.img like this http://forum.xda-developers.com/showpost.php?p=61203588&postcount=913?
Then
- fastboot erase system
- fastboot flash system system.img
- fastboot flash userdata userdata.img
- fastboot erase boot
- fastboot flash boot "no force encryption boot".img
- fastboot erase recovery (optional if I want the original recovery)
- fastboot flash recovery recovery.img (optional if I want the original recovery)
- fastboot erase cache
- fastboot flash cache cache.img
- data factory reset in recovery (it's necessary?)
- reboot system.
Then...root with WugFresh toolkit...
It's correct?
hollywood_jack said:
Can I flash directly a no force encryption boot.img like this http://forum.xda-developers.com/showpost.php?p=61203588&postcount=913?
Then
- fastboot erase system
- fastboot flash system system.img
- fastboot flash userdata userdata.img
- fastboot erase boot
- fastboot flash boot "no force encryption boot".img
- fastboot erase recovery (optional if I want the original recovery)
- fastboot flash recovery recovery.img (optional if I want the original recovery)
- fastboot erase cache
- fastboot flash cache cache.img
- data factory reset in recovery (it's necessary?)
- reboot system.
Then...root with WugFresh toolkit...
It's correct?
Click to expand...
Click to collapse
- You don`t have to erase boot and recovery
- Yes you can flash a non encryped kernel but you`ll have to factory reset after you flashed and the N6 is booting or your storage will say its 32GB.
- Rooting is easiest by placing the latest 2.8.7.1 TWRP recovery in the sdk-platform-tools folder, reboot in bootloadermode and fastboot boot namerecovery.img and boot up and flash the latest superSU.zip (Beta 2.49 afaik) or use a toolkit if want to.
After following the directions to the T i restarted my phone and now the only thing that is happening is my moto x blinks the android figure. Is my phone bricked? i can get into recovery. How do it fix my phone? Thanks ahead!!!
D.A.N. said:
After following the directions to the T i restarted my phone and now the only thing that is happening is my moto x blinks the android figure. Is my phone bricked? i can get into recovery. How do it fix my phone? Thanks ahead!!!
Click to expand...
Click to collapse
You need to be more specific. Hopefully you didn't downgrade the bootloader or partition table. Can you put the phone in bootloader mode and type this?
fastboot getvar all
You need to find the latest stock firmware for your variant and region, and flash it like this (example from my variant):
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
Hello, I just tried that and it's stuck at boot loader unlocked screen. Thank you for the advice. Am I able to get past this screen or is it bricked?
D.A.N. said:
Hello, I just tried that and it's stuck at boot loader unlocked screen. Thank you for the advice. Am I able to get past this screen or is it bricked?
Click to expand...
Click to collapse
I don't think it's bricked, it wouldn't show the bootloader unlocked screen. Can you power it off by long pressing the power button, then getiing into bootloader by pressing power and volume down at the same time. then do:
fastboot getvar all
Gus Ghanem said:
I don't think it's bricked, it wouldn't show the bootloader unlocked screen. Can you power it off by long pressing the power button, then getiing into bootloader by pressing power and volume down at the same time. then do:
fastboot getvar all
Click to expand...
Click to collapse
Yes, i type that in and i get the long list of options. Once i restart the phone I get the blinking android guy again.
D.A.N. said:
Yes, i type that in and i get the long list of options. Once i restart the phone I get the blinking android guy again.
Click to expand...
Click to collapse
Can you flash TWRP 3.1.1-0 and boot into it.
fastboot flash recovery twrp-3.1.1-0-victara.img
If you can, then it's not bricked.
https://dl.twrp.me/victara/
Gus Ghanem said:
Can you flash TWRP 3.1.1-0 and boot into it.
fastboot flash recovery twrp-3.1.1-0-victara.img
If you can, then it's not bricked.
https://dl.twrp.me/victara/
Click to expand...
Click to collapse
I just did that and it worked, but an error at the bottom says "mismatched partition size (recovery)
it does go into recovery now. Tried to install rom and it reboots over and over into recovery. Weird.
D.A.N. said:
I just did that and it worked, but an error at the bottom says "mismatched partition size (recovery)
it does go into recovery now. Tried to install rom and it reboots over and over into recovery. Weird.
Click to expand...
Click to collapse
The "mismatch" is normal because you're flashing a non-stock recovery.
In TWRP, tap wipe, advanced, and do repair for each partition, then do format data. In case you have corrupt partitions.
Gus Ghanem said:
The "mismatch" is normal because you're flashing a non-stock recovery.
In TWRP, tap wipe, advanced, and do repair for each partition, then do format data. In case you have corrupt partitions.
Click to expand...
Click to collapse
It says fails to mount data, dalvik, cache and storage. invalid arguement for each is the reason. unable to repair.
D.A.N. said:
It says fails to mount data, dalvik, cache and storage. invalid arguement for each is the reason. unable to repair.
Click to expand...
Click to collapse
What storage type should i have?EXT4 or something else?
D.A.N. said:
What storage type should i have?EXT4 or something else?
Click to expand...
Click to collapse
I think it's normally ext4, not sure if it's for all partitions. Data might be f2fs.
Gus Ghanem said:
The "mismatch" is normal because you're flashing a non-stock recovery.
In TWRP, tap wipe, advanced, and do repair for each partition, then do format data. In case you have corrupt partitions.
Click to expand...
Click to collapse
It wont let me wipe or repair anything. it just is red all over the place with errors. I seem to be stuck.
D.A.N. said:
It wont let me wipe or repair anything. it just is red all over the place with errors. I seem to be stuck.
Click to expand...
Click to collapse
Even if you reboot TWRP?
Is your stock firmware MPES24.49-18-7
Gus Ghanem said:
Even if you reboot TWRP?
Click to expand...
Click to collapse
yes, i am attempting to restore from twrp a from a folder i have. It seems to be working but said when it started it failed to mount storage so i don't know if it will work? Do you know how to wipe everything completely and start all over again or have I screwed it up to much? Thanks for your help.
D.A.N. said:
yes, i am attempting to restore from twrp a from a folder i have. It seems to be working but said when it started it failed to mount storage so i don't know if it will work? Do you know how to wipe everything completely and start all over again or have I screwed it up to much? Thanks for your help.
Click to expand...
Click to collapse
Your stock firmware files, are they MPES24.49-18-7
I have a XT1097 RETCA
You could try reflashing the partition table and bootloader if you're absoluitely sure you have the latest firmware.
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
D.A.N. said:
yes, i am attempting to restore from twrp a from a folder i have. It seems to be working but said when it started it failed to mount storage so i don't know if it will work? Do you know how to wipe everything completely and start all over again or have I screwed it up to much? Thanks for your help.
Click to expand...
Click to collapse
I am wondering if its because I changed the file system type to ext4 and it should be something else. Do you know what the normal file system should be?
D.A.N. said:
I am wondering if its because I changed the file system type to ext4 and it should be something else. Do you know what the normal file system should be?
Click to expand...
Click to collapse
It is ext4 except data, which is f2fs
File system
\
Gus Ghanem said:
It is ext4 except data, which is f2fs
Click to expand...
Click to collapse
it was the file system types. I changed them to what you said and it wiped them. attempting to reinstall rom and if it works i can try to go to stock again i guess. Thank you Gus for taking time to help.
Gus Ghanem said:
File system
Click to expand...
Click to collapse
I installed stock rooted rom. It booted backed into recovery. I had to reboot into bootloader, rebooted from there and it is turning on. I think something is still screwed up though because it always boots back into recovery.
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 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!