hi to all
i try many stock firmware without success show preflash validation failed
only 2 firmware flash ok
XT1068_TITAN_RETAILDSDS_6.0_MPB24.65-34-3_cid7_CFC.xml
XT1068_TITAN_RETDE_6.0_MPB24.65-34-3_cid7_CFC.xml
but at the end phone not factory reset and hang on logo
what can i do please any help
Code:
Easy Installer - Marshmallow 6.x Moto G (2nd Gen) 2014
For XT1063, XT1064, XT1068 and XT1069
Plug in USB CABLE and Put Phone in AP FASTBOOT Flash Mode
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
To cancel choose option 6
Choose a option:
1 - Flash stock ROM
2 - Flash stock ROM and ReLock Bootloader
3 - Flash Fixed Logo
4 - Reboot Phone
5 - Factory Reset
6 - Exit
Select your option : 1
RETURNING TO STOCK ROM - FLASHING PARTITIONS.
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.073s]
writing 'partition'...
OKAY [ 0.354s]
finished. total time: 0.434s
FLASHING BOOT LOADER..
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.128s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.052s]
finished. total time: 1.187s
FLASHING LOGO...
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 0.073s]
writing 'logo'...
OKAY [ 0.076s]
finished. total time: 0.153s
FLASHING BOOT....
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.375s]
writing 'boot'...
OKAY [ 0.630s]
finished. total time: 1.013s
FLASHING RECOVERY.....
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.377s]
writing 'recovery'...
OKAY [ 0.634s]
finished. total time: 1.020s
FLASHING SYSTEM IMAGE IN MULTIPLE SECTIONS......
target max-sparse-size: 256MB
sending 'system' (257467 KB)...
OKAY [ 8.238s]
writing 'system'...
OKAY [ 8.142s]
finished. total time: 16.389s
target max-sparse-size: 256MB
sending 'system' (257371 KB)...
OKAY [ 8.253s]
writing 'system'...
OKAY [ 7.901s]
finished. total time: 16.163s
target max-sparse-size: 256MB
sending 'system' (257534 KB)...
OKAY [ 8.245s]
writing 'system'...
OKAY [ 7.716s]
finished. total time: 15.968s
target max-sparse-size: 256MB
sending 'system' (248321 KB)...
OKAY [ 7.952s]
writing 'system'...
OKAY [ 8.538s]
finished. total time: 16.499s
FLASHING MODEM.......
target max-sparse-size: 256MB
sending 'modem' (50136 KB)...
OKAY [ 1.642s]
writing 'modem'...
OKAY [ 0.844s]
finished. total time: 2.492s
erasing 'modemst1'...
OKAY [ 0.012s]
finished. total time: 0.014s
erasing 'modemst2'...
OKAY [ 0.041s]
finished. total time: 0.043s
target max-sparse-size: 256MB
sending 'fsg' (652 KB)...
OKAY [ 0.078s]
writing 'fsg'...
OKAY [ 0.086s]
finished. total time: 0.171s
ERASING CACHE ......
erasing 'cache'...
OKAY [ 0.017s]
finished. total time: 0.020s
Choose a option:
1 - Flash stock ROM
2 - Flash stock ROM and ReLock Bootloader
3 - Flash Fixed Logo
4 - Reboot Phone
5 - Factory Reset
6 - Exit
Select your option : 3
FlASHING FIXED LOGO...
target max-sparse-size: 256MB
sending 'logo' (480 KB)...
OKAY [ 0.082s]
writing 'logo'...
OKAY [ 0.058s]
finished. total time: 0.143s
Done!...............
Choose a option:
1 - Flash stock ROM
2 - Flash stock ROM and ReLock Bootloader
3 - Flash Fixed Logo
4 - Reboot Phone
5 - Factory Reset
6 - Exit
Select your option :
bendou said:
hang on logo
what can i do please any help
Click to expand...
Click to collapse
do you have the bootloader unlocked ? and if is unlocked install TWRP and make a factory reset . and if the phone don't start try some custom roms. or just click the number 5 on that
software you are using for flash .
Related
The problem is my phone cannot turn on.
I instaled some roms. (KitKat and Lolipop)
When i try back from L to KK, phone stop on a logo.
Now i have not even system.
When i try use wipe, restore and other functions in twrp i can see
E: unable to mount '/data'
E: unable to mount '/system'
E: unable to mount '/cache'
E: unable to mount 'storage'
flash back ends without error but nothing change in phone(system not exist)
Use TWRP 2.8.0.1
CMD FLASH:
sending 'partition' (32 KB)...
OKAY [ 0.281s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
OKAY [ 0.453s]
finished. total time: 0.734s
sending 'motoboot' (1604 KB)...
OKAY [ 0.375s]
writing 'motoboot'...
(bootloader) flashing sbl1 ...
(bootloader) flashing sbl2 ...
(bootloader) flashing sbl3 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing aboot ...
OKAY [ 5.322s]
finished. total time: 5.713s
sending 'logo' (628 KB)...
OKAY [ 0.344s]
writing 'logo'...
OKAY [ 0.953s]
finished. total time: 1.297s
sending 'boot' (10240 KB)...
OKAY [ 0.938s]
writing 'boot'...
OKAY [ 1.656s]
finished. total time: 2.625s
sending 'recovery' (10240 KB)...
OKAY [ 0.955s]
writing 'recovery'...
OKAY [ 1.234s]
finished. total time: 2.220s
sending 'system' (597078 KB)...
OKAY [ 37.669s]
writing 'system'...
OKAY [ 31.546s]
finished. total time: 69.230s
sending 'modem' (53804 KB)...
OKAY [ 3.675s]
writing 'modem'...
OKAY [ 3.702s]
finished. total time: 7.392s
erasing 'modemst1'...
OKAY [ 0.457s]
finished. total time: 0.473s
erasing 'modemst2'...
OKAY [ 0.472s]
finished. total time: 0.472s
sending 'fsg' (225 KB)...
OKAY [ 0.346s]
writing 'fsg'...
OKAY [ 0.850s]
finished. total time: 1.195s
erasing 'cache'...
OKAY [ 0.804s]
finished. total time: 0.804s
erasing 'userdata'...
OKAY [ 1.055s]
finished. total time: 1.055s
erasing 'customize'...
OKAY [ 0.190s]
finished. total time: 0.190s
erasing 'clogo'...
OKAY [ 0.617s]
finished. total time: 0.617s
Click to expand...
Click to collapse
Why do people ignore threads like this? It is a viable question. These errors require a full-blown factory reset to my knowledge, because no one takes the time to help someone with this problem!
The OP stated errors that happen to me almost every time I try to delve into CM/CM-built roms, because most devs list limited instructions for installation of their roms.
I was using AICP for a while, and then an OTA update came along. The "Install Update" feature through the OTA app wouldn't do anything (a popup asking to reboot, but no reboots, nothing happens). So I tried to reboot to install the OTA myself, then wiped cache/dalvik.... sat at bootloader for 5 minutes... so I assumed bootloop, had to shut it off.
Can't even format /system due to this error., and would prefer not to do another freakin' complete factory reset.
Downgrading the Moto X is a good way to end up with a new Android phone.
aryma said:
The problem is my phone cannot turn on.
I instaled some roms. (KitKat and Lolipop)
When i try back from L to KK, phone stop on a logo.
Now i have not even system.
Click to expand...
Click to collapse
What model? XT1053, XT1058, XT1056, etc?
What Lollipop roms did you use?
And which KK rom are you trying to flash?
Hi Guys,
I have Moto G2 (XT1068) 2014 edition. I was using stock rom (5.0.2)
How the Problem started:
Dropped the phone.
What is the Issue:
Cannot charged - When connecting to wall charger, the bootlodaer icon shows and again device restarts. But i can enter Fastboot Menu. The phone will charge for some time then again restarts and enters boot loop (If battery is completely drained then it should start and then display the charging animation rt?).
When connecting to PC via USB same thing happens. When i enter boot menu, it shows Charging for few minutes then it says Battery - OK. IT does not enter boot loop in this case. But when i select 'Recovery' or 'Normal Powerup' or 'Factory Reset', it goes to 'Powered by Android' screen and then again goes into boot loop.
What I have tried:
1. Tried some fastboot commands 'erase usedata' & 'erase cache'.
2. I tired flashing Stock firmware. Used this guide - http://www.droidviews.com/restore-moto-g-2014-to-stock-and-lock-the-bootloader/
3. I unlocked bootloader. Flashed TWRP. But issue is not resolved. I cant enter Recovery coz phone will boot loop.
Need help!
@lost101
Kindly help. I have created new thread as u said.
Please provide a full and complete log of the factory firmware image fastboot flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
lost101 said:
Please provide a full and complete log of the factory firmware image fastboot flashing process. Copy and paste command prompt screen. Take screenshots if necessary.
Click to expand...
Click to collapse
Here u go:
'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
Restore to Original Stock Motorola Firmware for Motorola
Moto G 2014 Titan(XT1068) Provided with Unlock Bootloader
Please Do press Thanks Button If u really liked My Work @bhu999
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device '(null)' not found
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.031s]
writing 'partition'...
OKAY [ 0.325s]
finished. total time: 0.358s
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.102s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.048s]
finished. total time: 1.153s
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 0.057s]
writing 'logo'...
OKAY [ 0.097s]
finished. total time: 0.154s
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.367s]
writing 'boot'...
OKAY [ 0.273s]
finished. total time: 0.640s
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.415s]
writing 'recovery'...
OKAY [ 0.280s]
finished. total time: 0.695s
target max-sparse-size: 256MB
sending 'system' (257603 KB)...
OKAY [ 8.419s]
writing 'system'...
OKAY [ 6.401s]
finished. total time: 14.900s
target max-sparse-size: 256MB
sending 'system' (256614 KB)...
OKAY [ 8.271s]
writing 'system'...
OKAY [ 6.629s]
finished. total time: 15.310s
target max-sparse-size: 256MB
sending 'system' (257104 KB)...
OKAY [ 8.310s]
writing 'system'...
OKAY [ 6.372s]
finished. total time: 14.685s
target max-sparse-size: 256MB
sending 'system' (241377 KB)...
OKAY [ 7.774s]
writing 'system'...
OKAY [ 5.227s]
finished. total time: 13.005s
target max-sparse-size: 256MB
sending 'system' (38920 KB)...
OKAY [ 1.288s]
writing 'system'...
OKAY [ 0.870s]
finished. total time: 2.168s
target max-sparse-size: 256MB
sending 'modem' (49356 KB)...
OKAY [ 1.958s]
writing 'modem'...
OKAY [ 1.200s]
finished. total time: 3.597s
erasing 'modemst1'...
OKAY [ 0.028s]
finished. total time: 0.033s
erasing 'modemst2'...
OKAY [ 0.026s]
finished. total time: 0.031s
target max-sparse-size: 256MB
sending 'fsg' (1013 KB)...
OKAY [ 0.080s]
writing 'fsg'...
OKAY [ 0.090s]
finished. total time: 0.190s
erasing 'cache'...
OKAY [ 0.128s]
finished. total time: 0.132s
erasing 'userdata'...
OKAY [ 1.158s]
finished. total time: 1.158s
rebooting...
finished. total time: 0.003s
Press any key to Exit
Press any key to continue . . .
''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
You are using a script and I'm not seeing the names of sparsechunks. It's better if you do the commands manually, one at a time - and copy and paste everything from command prompt. Be sure to flash every sparsechunk file in the firmware folder you are working with.
Fastboot tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
lost101 said:
You are using a script and I'm not seeing the names of sparsechunks. It's better if you do the commands manually, one at a time - and copy and paste everything from command prompt. Be sure to flash every sparsechunk file in the firmware folder you are working with.
Fastboot tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
Flashed 5.0.2 stock manually:
''''''''''''''''''''''''''''''''''''''''''''''''''''''''
F:\Minimal ADB and Fastboot>fastboot devices
ZX1D63NZQP fastboot
F:\Minimal ADB and Fastboot>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.047s]
writing 'partition'...
OKAY [ 0.316s]
finished. total time: 0.362s
F:\Minimal ADB and Fastboot>mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.094s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.029s]
finished. total time: 1.140s
F:\Minimal ADB and Fastboot>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 0.048s]
writing 'logo'...
OKAY [ 0.078s]
finished. total time: 0.142s
F:\Minimal ADB and Fastboot>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.419s]
writing 'boot'...
OKAY [ 0.272s]
finished. total time: 0.707s
F:\Minimal ADB and Fastboot>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.372s]
writing 'recovery'...
OKAY [ 0.300s]
finished. total time: 0.672s
F:\Minimal ADB and Fastboot>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257603 KB)...
OKAY [ 8.176s]
writing 'system'...
OKAY [ 6.326s]
finished. total time: 14.534s
F:\Minimal ADB and Fastboot>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256614 KB)...
OKAY [ 8.148s]
writing 'system'...
OKAY [ 6.660s]
finished. total time: 14.808s
F:\Minimal ADB and Fastboot>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (257104 KB)...
OKAY [ 8.177s]
writing 'system'...
OKAY [ 6.348s]
finished. total time: 14.525s
F:\Minimal ADB and Fastboot>mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (241377 KB)...
OKAY [ 7.662s]
writing 'system'...
OKAY [ 5.256s]
finished. total time: 12.918s
F:\Minimal ADB and Fastboot>mfastboot flash system system.img_sparsechunk.4
target max-sparse-size: 256MB
sending 'system' (38920 KB)...
OKAY [ 1.289s]
writing 'system'...
OKAY [ 0.863s]
finished. total time: 2.151s
F:\Minimal ADB and Fastboot>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (49356 KB)...
OKAY [ 1.645s]
writing 'modem'...
OKAY [ 1.101s]
finished. total time: 2.751s
F:\Minimal ADB and Fastboot>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.031s]
finished. total time: 0.031s
F:\Minimal ADB and Fastboot>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.017s]
finished. total time: 0.017s
F:\Minimal ADB and Fastboot>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (1013 KB)...
OKAY [ 0.095s]
writing 'fsg'...
OKAY [ 0.079s]
finished. total time: 0.174s
F:\Minimal ADB and Fastboot>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.142s]
finished. total time: 0.142s
F:\Minimal ADB and Fastboot>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 1.131s]
finished. total time: 1.131s
F:\Minimal ADB and Fastboot>mfastboot reboot
rebooting...
finished. total time: 0.000s
F:\Minimal ADB and Fastboot>
'''''''''''''''''''''''''''''''''''''''''''''''''''''
Is there any reason why you are not flashing the 5.1 Firmware image or 6.0 image available here?
lost101 said:
Is there any reason why you are not flashing the 5.1 Firmware image or 6.0 image available here?
Click to expand...
Click to collapse
Let me try these
lost101 said:
Is there any reason why you are not flashing the 5.1 Firmware image or 6.0 image available here?
Click to expand...
Click to collapse
Still bootloop
now m worried
I used easy installer. Too tired for manual. Its 1 am here
'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
Easy Installer - Marshmallow 6.x Moto G (2nd Gen) 2014
For XT1063, XT1064, XT1068 and XT1069
Plug in USB CABLE and Put Phone in AP FASTBOOT Flash Mode
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
To cancel choose option 6
Choose a option:
1 - Flash stock ROM
2 - Flash stock ROM and ReLock Bootloader
3 - Flash Fixed Logo
4 - Reboot Phone
5 - Factory Reset
6 - Exit
Select your option : 5
FACTORY RESET - Wiping NOW ......
erasing 'userdata'...
OKAY [ 1.151s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.018s]
erasing 'cache'...
OKAY [ 0.125s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.021s]
finished. total time: 1.327s
Done!.........
Choose a option:
1 - Flash stock ROM
2 - Flash stock ROM and ReLock Bootloader
3 - Flash Fixed Logo
4 - Reboot Phone
5 - Factory Reset
6 - Exit
Select your option : 4
PRESS ANY KEY TO REBOOT PHONE
rebooting...
finished. total time: 0.002s
Choose a option:
1 - Flash stock ROM
2 - Flash stock ROM and ReLock Bootloader
3 - Flash Fixed Logo
4 - Reboot Phone
5 - Factory Reset
6 - Exit
Select your option : 2
LOCKED BOOTLOADER STOCK ROM - FLASHING PARTITIONS.
...
(bootloader) Please flash valid signed images firstly!
OKAY [ 0.528s]
finished. total time: 0.530s
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.043s]
writing 'partition'...
OKAY [ 0.336s]
finished. total time: 0.384s
FLASHING BOOT LOADER..
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.120s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 1.052s]
finished. total time: 1.176s
FLASHING LOGO...
target max-sparse-size: 256MB
sending 'logo' (697 KB)...
OKAY [ 0.088s]
writing 'logo'...
OKAY [ 0.066s]
finished. total time: 0.158s
FLASHING BOOT....
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.385s]
writing 'boot'...
OKAY [ 0.262s]
finished. total time: 0.652s
FLASHING RECOVERY.....
target max-sparse-size: 256MB
sending 'recovery' (10280 KB)...
OKAY [ 0.399s]
writing 'recovery'...
OKAY [ 0.281s]
finished. total time: 0.684s
FLASHING SYSTEM IMAGE IN MULTIPLE SECTIONS......
target max-sparse-size: 256MB
sending 'system' (257431 KB)...
OKAY [ 8.188s]
writing 'system'...
OKAY [ 6.459s]
finished. total time: 14.652s
target max-sparse-size: 256MB
sending 'system' (255474 KB)...
OKAY [ 8.128s]
writing 'system'...
OKAY [ 7.409s]
finished. total time: 15.542s
target max-sparse-size: 256MB
sending 'system' (257554 KB)...
OKAY [ 8.206s]
writing 'system'...
OKAY [ 5.798s]
finished. total time: 14.009s
target max-sparse-size: 256MB
sending 'system' (250957 KB)...
OKAY [ 8.068s]
writing 'system'...
OKAY [ 5.577s]
finished. total time: 13.650s
FLASHING MODEM.......
target max-sparse-size: 256MB
sending 'modem' (50136 KB)...
OKAY [ 1.635s]
writing 'modem'...
OKAY [ 1.150s]
finished. total time: 2.790s
erasing 'modemst1'...
OKAY [ 0.024s]
finished. total time: 0.024s
erasing 'modemst2'...
OKAY [ 0.062s]
finished. total time: 0.063s
target max-sparse-size: 256MB
sending 'fsg' (1012 KB)...
OKAY [ 0.120s]
writing 'fsg'...
OKAY [ 0.093s]
finished. total time: 0.217s
RELOCKING BOOT LOADER.....(if possible)
...
(bootloader) Please flash valid signed images firstly!
OKAY [ 0.521s]
finished. total time: 0.523s
ERASING CACHE ......
erasing 'cache'...
OKAY [ 0.186s]
finished. total time: 0.189s
Choose a option:
1 - Flash stock ROM
2 - Flash stock ROM and ReLock Bootloader
3 - Flash Fixed Logo
4 - Reboot Phone
5 - Factory Reset
6 - Exit
Select your option : 4
PRESS ANY KEY TO REBOOT PHONE
rebooting...
finished. total time: 0.002s
Choose a option:
1 - Flash stock ROM
2 - Flash stock ROM and ReLock Bootloader
3 - Flash Fixed Logo
4 - Reboot Phone
5 - Factory Reset
6 - Exit
Select your option :
''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
Don't flash any older Bootloader (motoboot.img) such as the one in 5.0.1 or 5.1 from this point on. I would focus on trying to get Android 6.0 to boot. Can you try again flashing different custom recoverys: TWRP and CWM.
It is possible to boot directly into a custom recovery with the following command: mfastboot boot twrp.img
Change the name of twrp.img to the name of the actual recovery.img
lost101 said:
Don't flash any older Bootloader (motoboot.img) such as the one in 5.0.1 or 5.1 from this point on. I would focus on trying to get Android 6.0 to boot. Can you try again flashing different custom recoverys: TWRP and CWM.
It is possible to boot directly into a custom recovery with the following command: mfastboot boot twrp.img
Change the name of twrp.img to the name of the actual recovery.img
Click to expand...
Click to collapse
after flashing twrp, i saw the 'powered by android' screen followed by bootloader warning followed by boot loop.
Fir3lordZuk0 said:
after flashing twrp, i saw the 'powered by android' screen followed by bootloader warning followed by boot loop.
Click to expand...
Click to collapse
What happens if you use the 'mfastboot boot twrp.img' command?
lost101 said:
What happens if you use the 'mfastboot boot twrp.img' command?
Click to expand...
Click to collapse
''''''''''''''''''''''''''''''''''''''''
C:\Users\Yogesh\Downloads\uploadfromtaptalk1455326923057.easy_installer\XT1068_TITAN_RETAILDSDS_6.0_MPB.24.65-34_Easy_Installer>mfastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.285s]
booting...
OKAY [ 0.221s]
finished. total time: 0.507s
''''''''''''''''''''''''''''''''''''''''''''''''''''''
After this on phone, i see 'powered by android' screen with motorola logo...after that it shows bootloader warning and then again it restarts and goes to boot loop
What version of TWRP are you using? Latest is here: http://forum.xda-developers.com/mot...recovery-twrp-2-8-2-0-touch-recovery-t2979149
Also try Philz Touch CWM from here: http://forum.xda-developers.com/mot...covery-cwm-philz-touch-6-moto-g-2014-t2896586 and here: http://forum.xda-developers.com/moto-g-2014/orig-development/recovery-philz-touch-recovery-t3006838
lost101 said:
What version of TWRP are you using? Latest is here: http://forum.xda-developers.com/mot...recovery-twrp-2-8-2-0-touch-recovery-t2979149
Also try Philz Touch CWM from here: http://forum.xda-developers.com/mot...covery-cwm-philz-touch-6-moto-g-2014-t2896586 and here: http://forum.xda-developers.com/moto-g-2014/orig-development/recovery-philz-touch-recovery-t3006838
Click to expand...
Click to collapse
TWRP - 3.0
Same behavior with Philz Touch
''''''''''''''''''''''''''''''''''''
C:\Users\Yogesh\Downloads\uploadfromtaptalk1455326923057.easy_installer\XT1068_TITAN_RETAILDSDS_6.0_MPB.24.65-34_Easy_Installer>mfastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.268s]
booting...
OKAY [ 0.237s]
finished. total time: 0.504s
C:\Users\Yogesh\Downloads\uploadfromtaptalk1455326923057.easy_installer\XT1068_TITAN_RETAILDSDS_6.0_MPB.24.65-34_Easy_Installer>mfastboot boot CWM_Touch_Titan_v2.img
downloading 'boot.img'...
OKAY [ 0.332s]
booting...
OKAY [ 0.237s]
finished. total time: 0.586s
'''''''''''''''''''''''''''''''''''''''''''''''
Without custom recovery access you have run out of options. Are you absolutely sure your handset is an XT1068?
lost101 said:
Without custom recovery access you have run out of options. Are you absolutely sure your handset is an XT1068?
Click to expand...
Click to collapse
Yes it is XT1068
so is it hard brick? No other way to get it start? any other way to charge it?
Fir3lordZuk0 said:
Yes it is XT1068
so is it hard brick? No other way to get it start? any other way to charge it?
Click to expand...
Click to collapse
The phone appears to have been physically damaged (internally) by the fall. I don't know of any solution other than maybe replace mainboard - cheap off ebay if pulled from a screen-damaged unit.
Thanks a lot for your time and help!
I appreciate it
Hey guys. I really need the eu firmware (germany) for my G6!!! I bricked my G6 and cant boot up.
I wanted to flash the magisk patched boot img from the forum and have unfortunately overlooked that it was for the g6 plus -.- My bootloader is unlocked, but everytime when i turn on device, i have the message: Your device has been unlocked and cant be trusted. ID: bad key... and i cant boot up! I tried to flash the g6 firmware from the forum, but without solution... The Message freeze it and the phone cant boot.
i hope anyone has the eu firmware for me or any help! ^^
Heres my log:
C:\adb>fastboot oem fb_mode_set
... OKAY [ -0.000s]
finished. total time: -0.000s
C:\adb>fastboot flash partition gpt.bin
sending 'partition' (45 KB)... OKAY [ 0.000s]
writing 'partition'... INFOValidating 'gpt.default.xml'
INFOCommitting 'gpt.default.xml'
INFO- flashing 'gpt_main0.bin' to 'partition:0'
INFOFlashing primary GPT image...
INFOFlashing backup GPT image...
OKAY [ 0.078s]
finished. total time: 0.078s
C:\adb>fastboot flash bootloader bootloader.img
sending 'bootloader' (7419 KB)... OKAY [ 0.234s]
writing 'bootloader'... INFOValidating 'bootloader.default.xml'
INFOSecurity version downgrade
INFOImage aboot failed validation
INFOPreflash validation failed
INFOCancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.438s
C:\adb>fastboot flash logo logo.bin
sending 'logo' (2182 KB)... OKAY [ 0.062s]
writing 'logo'... OKAY [ 0.047s]
finished. total time: 0.109s
C:\adb>fastboot flash boot boot.img
sending 'boot' (22528 KB)... OKAY [ 0.719s]
writing 'boot'... INFOImage signed with key bad key
OKAY [ 0.266s]
finished. total time: 0.984s
C:\adb>fastboot flash recovery recovery.img
sending 'recovery' (22628 KB)... OKAY [ 0.734s]
writing 'recovery'... INFOImage signed with key bad key
OKAY [ 0.359s]
finished. total time: 1.094s
C:\adb>fastboot flash dsp adspso.bin
sending 'dsp' (16384 KB)... OKAY [ 0.516s]
writing 'dsp'... OKAY [ 0.156s]
finished. total time: 0.672s
C:\adb>fastboot flash oem oem.img
sending 'oem' (206464 KB)... OKAY [ 6.550s]
writing 'oem'... OKAY [ 1.456s]
finished. total time: 8.006s
C:\adb>fastboot flash system system.img_sparsechunk.0
sending 'system' (259756 KB)... OKAY [ 8.238s]
writing 'system'... OKAY [ 2.132s]
finished. total time: 10.370s
C:\adb>fastboot flash system system.img_sparsechunk.1
sending 'system' (253441 KB)... OKAY [ 8.033s]
writing 'system'... OKAY [ 1.669s]
finished. total time: 9.703s
C:\adb>fastboot flash system system.img_sparsechunk.2
sending 'system' (254074 KB)... OKAY [ 8.048s]
writing 'system'... OKAY [ 1.679s]
finished. total time: 9.727s
C:\adb>fastboot flash system system.img_sparsechunk.3
sending 'system' (260545 KB)... OKAY [ 8.251s]
writing 'system'... OKAY [ 1.711s]
finished. total time: 9.962s
C:\adb>fastboot flash system system.img_sparsechunk.4
sending 'system' (259733 KB)... OKAY [ 8.221s]
writing 'system'... OKAY [ 1.696s]
finished. total time: 9.917s
C:\adb>fastboot flash modem NON-HLOS.bin
sending 'modem' (71577 KB)... OKAY [ 2.272s]
writing 'modem'... OKAY [ 0.547s]
finished. total time: 2.819s
C:\adb>fastboot erase modemst1
erasing 'modemst1'... OKAY [ 0.016s]
finished. total time: 0.016s
C:\adb>fastboot erase modemst2
erasing 'modemst2'... OKAY [ 0.016s]
finished. total time: 0.016s
C:\adb>fastboot flash fsg fsg.mbn
sending 'fsg' (6780 KB)... OKAY [ 0.212s]
writing 'fsg'... OKAY [ 0.078s]
finished. total time: 0.290s
C:\adb>fastboot erase cache
erasing 'cache'... OKAY [ -0.000s]
finished. total time: -0.000s
C:\adb>fastboot erase userdata
erasing 'userdata'... OKAY [ 0.047s]
finished. total time: 0.047s
C:\adb>fastboot erase customize
erasing 'customize'... INFOPermission denied
FAILED (remote failure)
finished. total time: 0.000s
C:\adb>fastboot erase clogo
erasing 'clogo'... INFOPermission denied
FAILED (remote failure)
finished. total time: 0.000s
C:\adb>fastboot oem fb_mode_clear
... OKAY [ 0.016s]
finished. total time: 0.016s
C:\adb>fastboot reboot
DeineMudda111 said:
Hey guys. I really need the eu firmware (germany) for my G6!!! I bricked my G6 and cant boot up.
I wanted to flash the magisk patched boot img from the forum and have unfortunately overlooked that it was for the g6 plus -.- My bootloader is unlocked, but everytime when i turn on device, i have the message: Your device has been unlocked and cant be trusted. ID: bad key... and i cant boot up! I tried to flash the g6 firmware from the forum, but without solution... The Message freeze it and the phone cant boot.
i hope anyone has the eu firmware for me or any help! ^^
Heres my log:
C:\adb>fastboot oem fb_mode_set
... OKAY [ -0.000s]
finished. total time: -0.000s
C:\adb>fastboot flash partition gpt.bin
sending 'partition' (45 KB)... OKAY [ 0.000s]
writing 'partition'... INFOValidating 'gpt.default.xml'
INFOCommitting 'gpt.default.xml'
INFO- flashing 'gpt_main0.bin' to 'partition:0'
INFOFlashing primary GPT image...
INFOFlashing backup GPT image...
OKAY [ 0.078s]
finished. total time: 0.078s
C:\adb>fastboot flash bootloader bootloader.img
sending 'bootloader' (7419 KB)... OKAY [ 0.234s]
writing 'bootloader'... INFOValidating 'bootloader.default.xml'
INFOSecurity version downgrade
INFOImage aboot failed validation
INFOPreflash validation failed
INFOCancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.438s
C:\adb>fastboot flash logo logo.bin
sending 'logo' (2182 KB)... OKAY [ 0.062s]
writing 'logo'... OKAY [ 0.047s]
finished. total time: 0.109s
C:\adb>fastboot flash boot boot.img
sending 'boot' (22528 KB)... OKAY [ 0.719s]
writing 'boot'... INFOImage signed with key bad key
OKAY [ 0.266s]
finished. total time: 0.984s
C:\adb>fastboot flash recovery recovery.img
sending 'recovery' (22628 KB)... OKAY [ 0.734s]
writing 'recovery'... INFOImage signed with key bad key
OKAY [ 0.359s]
finished. total time: 1.094s
C:\adb>fastboot flash dsp adspso.bin
sending 'dsp' (16384 KB)... OKAY [ 0.516s]
writing 'dsp'... OKAY [ 0.156s]
finished. total time: 0.672s
C:\adb>fastboot flash oem oem.img
sending 'oem' (206464 KB)... OKAY [ 6.550s]
writing 'oem'... OKAY [ 1.456s]
finished. total time: 8.006s
C:\adb>fastboot flash system system.img_sparsechunk.0
sending 'system' (259756 KB)... OKAY [ 8.238s]
writing 'system'... OKAY [ 2.132s]
finished. total time: 10.370s
C:\adb>fastboot flash system system.img_sparsechunk.1
sending 'system' (253441 KB)... OKAY [ 8.033s]
writing 'system'... OKAY [ 1.669s]
finished. total time: 9.703s
C:\adb>fastboot flash system system.img_sparsechunk.2
sending 'system' (254074 KB)... OKAY [ 8.048s]
writing 'system'... OKAY [ 1.679s]
finished. total time: 9.727s
C:\adb>fastboot flash system system.img_sparsechunk.3
sending 'system' (260545 KB)... OKAY [ 8.251s]
writing 'system'... OKAY [ 1.711s]
finished. total time: 9.962s
C:\adb>fastboot flash system system.img_sparsechunk.4
sending 'system' (259733 KB)... OKAY [ 8.221s]
writing 'system'... OKAY [ 1.696s]
finished. total time: 9.917s
C:\adb>fastboot flash modem NON-HLOS.bin
sending 'modem' (71577 KB)... OKAY [ 2.272s]
writing 'modem'... OKAY [ 0.547s]
finished. total time: 2.819s
C:\adb>fastboot erase modemst1
erasing 'modemst1'... OKAY [ 0.016s]
finished. total time: 0.016s
C:\adb>fastboot erase modemst2
erasing 'modemst2'... OKAY [ 0.016s]
finished. total time: 0.016s
C:\adb>fastboot flash fsg fsg.mbn
sending 'fsg' (6780 KB)... OKAY [ 0.212s]
writing 'fsg'... OKAY [ 0.078s]
finished. total time: 0.290s
C:\adb>fastboot erase cache
erasing 'cache'... OKAY [ -0.000s]
finished. total time: -0.000s
C:\adb>fastboot erase userdata
erasing 'userdata'... OKAY [ 0.047s]
finished. total time: 0.047s
C:\adb>fastboot erase customize
erasing 'customize'... INFOPermission denied
FAILED (remote failure)
finished. total time: 0.000s
C:\adb>fastboot erase clogo
erasing 'clogo'... INFOPermission denied
FAILED (remote failure)
finished. total time: 0.000s
C:\adb>fastboot oem fb_mode_clear
... OKAY [ 0.016s]
finished. total time: 0.016s
C:\adb>fastboot reboot
Click to expand...
Click to collapse
Hi, I am sorry to hear that. What version of firmware you had installed and what version are trying to flash? it seems that you are flashing a firmware older than firmware installed
jekyll86 said:
Hi, I am sorry to hear that. What version of firmware you had installed and what version are trying to flash? it seems that you are flashing a firmware older than firmware installed
Click to expand...
Click to collapse
I flashed that one: https://forum.xda-developers.com/moto-g6/development/stock-firmware-moto-g6-t3792292
I cant find another new firmware for my g6, there seems to be only this version. I dont know which Version i had before, but it must have been a EU version (i'm from germany) with april update... I'm very frustrated...
DeineMudda111 said:
I flashed that one: https://forum.xda-developers.com/moto-g6/development/stock-firmware-moto-g6-t3792292
I cant find another new firmware for my g6, there seems to be only this version. I dont know which Version i had before, but it must have been a EU version (i'm from germany) with april update... I'm very frustrated...
Click to expand...
Click to collapse
That seems March firmware, you have to wait someone that upload April firmware.
Inviato dal mio moto g(6) plus utilizzando Tapatalk
jekyll86 said:
That seems March firmware, you have to wait someone that upload April firmware.
Inviato dal mio moto g(6) plus utilizzando Tapatalk
Click to expand...
Click to collapse
I will wait... Thank you
Hello there. I need some urgente help here.
I was trying to update my Mi A2 flashing some images on fastboot, and the following happened:
Code:
PS D:\ADB Fastboot\platform-tools> .\fastboot flash devcfg_a devcfg.img
>> .\fastboot flash devcfg_b devcfg.img
>>
>> .\fastboot flash dsp_a dsp.img
>> .\fastboot flash dsp_b dsp.img
>>
>> .\fastboot flash modem_a modem.img
>> .\fastboot flash modem_b modem.img
>>
>> .\fastboot flash rpm_a rpm.img
>> .\fastboot flash rpm_b rpm.img
>>
>> .\fastboot flash tz_a tz.img
>> .\fastboot flash tz_b tz.img
>>
>> .\fastboot flash keymaster_a keymaster.img
>> .\fastboot flash keymaster_b keymaster.img
>>
>> .\fastboot flash cmnlib64_a cmnlib64.img
>> .\fastboot flash cmnlib64_b cmnlib64.img
>>
>> .\fastboot flash cmnlib_a cmnlib.img
>> .\fastboot flash cmnlib_b cmnlib.img
>>
>> .\fastboot flash boot_a boot.img
>> .\fastboot flash boot_b boot.img
>>
>> .\fastboot flash system_a system.img
>> .\fastboot flash system_b system.img
>>
>> .\fastboot flash vendor_a vendor.img
>> .\fastboot flash vendor_b vendor.img
>>
>> .\fastboot flash mdtp_a mdtp.img
>> .\fastboot flash mdtp_b mdtp.img
>>
>> .\fastboot flash aboot_a aboot.img
>> .\fastboot flash aboot_b aboot.img
>>
>> .zfastboot flash sbl1_a sbl1.img
>> .\fastboot flash sbl1_b sbl1.img
Sending 'devcfg_a' (40 KB) OKAY [ 0.008s]
Writing 'devcfg_a' OKAY [ 0.005s]
Finished. Total time: 0.018s
Sending 'devcfg_b' (40 KB) OKAY [ 0.008s]
Writing 'devcfg_b' OKAY [ 0.003s]
Finished. Total time: 0.018s
Sending 'dsp_a' (16384 KB) OKAY [ 0.625s]
Writing 'dsp_a' OKAY [ 0.004s]
Finished. Total time: 0.659s
Sending 'dsp_b' (16384 KB) OKAY [ 0.545s]
Writing 'dsp_b' OKAY [ 0.004s]
Finished. Total time: 0.555s
Sending 'modem_a' (131072 KB) OKAY [ 4.949s]
Writing 'modem_a' OKAY [ 0.003s]
Finished. Total time: 4.993s
Sending 'modem_b' (131072 KB) OKAY [ 4.329s]
Writing 'modem_b' OKAY [ 0.005s]
Finished. Total time: 4.338s
Sending 'rpm_a' (172 KB) OKAY [ 0.018s]
Writing 'rpm_a' OKAY [ 0.004s]
Finished. Total time: 0.042s
Sending 'rpm_b' (172 KB) OKAY [ 0.012s]
Writing 'rpm_b' OKAY [ 0.003s]
Finished. Total time: 0.021s
Sending 'tz_a' (1500 KB) OKAY [ 0.070s]
Writing 'tz_a' OKAY [ 0.004s]
Finished. Total time: 0.101s
Sending 'tz_b' (1500 KB) OKAY [ 0.060s]
Writing 'tz_b' OKAY [ 0.004s]
Finished. Total time: 0.070s
Sending 'keymaster_a' (268 KB) OKAY [ 0.024s]
Writing 'keymaster_a' OKAY [ 0.004s]
Finished. Total time: 0.038s
Sending 'keymaster_b' (268 KB) OKAY [ 0.018s]
Writing 'keymaster_b' OKAY [ 0.004s]
Finished. Total time: 0.027s
Sending 'cmnlib64_a' (264 KB) OKAY [ 0.014s]
Writing 'cmnlib64_a' OKAY [ 0.005s]
Finished. Total time: 0.039s
Sending 'cmnlib64_b' (264 KB) OKAY [ 0.017s]
Writing 'cmnlib64_b' OKAY [ 0.004s]
Finished. Total time: 0.027s
Sending 'cmnlib_a' (212 KB) OKAY [ 0.011s]
Writing 'cmnlib_a' OKAY [ 0.004s]
Finished. Total time: 0.027s
Sending 'cmnlib_b' (212 KB) OKAY [ 0.015s]
Writing 'cmnlib_b' OKAY [ 0.004s]
Finished. Total time: 0.025s
Sending 'boot_a' (27220 KB) OKAY [ 1.050s]
Writing 'boot_a' OKAY [ 0.004s]
Finished. Total time: 1.085s
Sending 'boot_b' (27220 KB) OKAY [ 1.137s]
Writing 'boot_b' OKAY [ 0.003s]
Finished. Total time: 1.145s
Invalid sparse file format at header magic
Sending sparse 'system_a' 1/4 (524284 KB) OKAY [ 18.973s]
Writing sparse 'system_a' 1/4 OKAY [ 0.013s]
Sending sparse 'system_a' 2/4 (524284 KB) OKAY [ 21.103s]
Writing sparse 'system_a' 2/4 OKAY [ 0.005s]
Sending sparse 'system_a' 3/4 (487210 KB) OKAY [ 19.443s]
Writing sparse 'system_a' 3/4 OKAY [ 0.003s]
Sending sparse 'system_a' 4/4 (470645 KB) OKAY [ 22.815s]
Writing sparse 'system_a' 4/4 OKAY [ 0.004s]
Finished. Total time: 123.482s
Invalid sparse file format at header magic
Sending sparse 'system_b' 1/4 (524284 KB) OKAY [ 19.237s]
Writing sparse 'system_b' 1/4 OKAY [ 0.003s]
Sending sparse 'system_b' 2/4 (524284 KB) OKAY [ 22.565s]
Writing sparse 'system_b' 2/4 OKAY [ 0.003s]
Sending sparse 'system_b' 3/4 (487210 KB) OKAY [ 18.924s]
Writing sparse 'system_b' 3/4 OKAY [ 0.003s]
Sending sparse 'system_b' 4/4 (470645 KB) OKAY [ 18.155s]
Writing sparse 'system_b' 4/4 OKAY [ 0.003s]
Finished. Total time: 228.714s
Invalid sparse file format at header magic
Sending sparse 'vendor_a' 1/2 (513365 KB) OKAY [ 18.165s]
Writing sparse 'vendor_a' 1/2 OKAY [ 0.003s]
Sending sparse 'vendor_a' 2/2 (43596 KB) OKAY [ 8.365s]
Writing sparse 'vendor_a' 2/2 OKAY [ 0.003s]
Finished. Total time: 160.975s
Invalid sparse file format at header magic
Sending sparse 'vendor_b' 1/2 (513365 KB) OKAY [ 18.292s]
Writing sparse 'vendor_b' 1/2 OKAY [ 0.004s]
Sending sparse 'vendor_b' 2/2 (43596 KB) OKAY [ 9.543s]
Writing sparse 'vendor_b' 2/2 OKAY [ 0.003s]
Finished. Total time: 82.975s
Sending 'mdtp_a' (17392 KB) OKAY [ 0.711s]
Writing 'mdtp_a' OKAY [ 0.005s]
Finished. Total time: 44.537s
Sending 'mdtp_b' (17392 KB) OKAY [ 0.675s]
Writing 'mdtp_b' OKAY [ 0.004s]
Finished. Total time: 0.685s
Sending 'aboot_a' (672 KB) OKAY [ 0.055s]
Writing 'aboot_a' OKAY [ 0.005s]
Finished. Total time: 0.152s
Sending 'aboot_b' (672 KB) FAILED (remote: 'No such partition.')
Finished. Total time: 0.009s
.zfastboot : O termo '.zfastboot' não é reconhecido como nome de cmdlet, função, arquivo de script ou programa
operável. Verifique a grafia do nome ou, se um caminho tiver sido incluído, veja se o caminho está correto e tente
novamente.
No linha:40 caractere:1
+ .zfastboot flash sbl1_a sbl1.img
+ ~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (.zfastboot:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
Sending 'sbl1_b' (396 KB) OKAY [ 0.028s]
Writing 'sbl1_b' OKAY [ 0.003s]
Finished. Total time: 0.080s
PS D:\ADB Fastboot\platform-tools> .\fastboot reboot
Rebooting
Finished. Total time: 0.005s
I pasted everything so maybe someone can find some error and help me out.
After I hit reboot, the phone flashed and I immediately disconnected USB cable. Was it the problem?
Now it won't turn on, and won't even light on the led indicator, as if it is not even charging.
I need some URGENT help.
Click to expand...
Click to collapse
SOLVED.
How to do it, in case you find yourself in the same situation:
1- Download and extract twice stock ROMfrom xiaomi official website.
-(first extract the .tgz file, which will give you a .tar file. Then extract the .tar)
2- Download and install Qualcomm HS-USB 9008 driver.
3- Download and install Mi Flash Tool.
4- Open Mi Flash tool
4.1 - "select" the folder extracted from what you downloaded as Stock ROM. Should be like this: D:\Mi A2 ROM\jasmine_global_images_V9.6.16.0.ODIMIFE_8.1
4.2- hit "refresh".
4.3- hit "flash". Mi flash should recognize device as "COM3".
4.4- Wait until finished and power on device.
Smile.
Look at how many typos you have
What is aboot_a?
What is zfastboot?
Nebrassy said:
Look at how many typos you have
What is aboot_a?
What is zfastboot?
Click to expand...
Click to collapse
Yeah... mistyping on that .zfastboot. Meant to be .\fastboot. That was surely an error I hadn't even seen.
But before that, aboot_b.img failed to be flashed on the device. That code line was copied from a post here on XDA, one which I'm not having much success on finding it again.
Well, anyways, my computer recognized the device only as Qualcomm HS-USB 9008 (COM3). I managed to install a qualcomm driver.
After that, I installed Mi Flash Tool, which was able to identify the Qualcomm device (something that fastboot wouldn't do).
Following that, I download stock ROM from Xiaomi official website, on .tgz format. Extracted it twice until I got the images folder.
I disabled integrity check function on windows 10, restarted my PC.
Opened Mi Flash Tool, selected the folder which contained the stock ROM images, refreshed the software to recognize the qualcomm on COM3, and hit flash.
It worked! It's been a few seconds since I managed to turn my phone on again. I'm configuring and installing my most used apps right now.
It's boot_a and boot_b, there is no aboot_b partition
Nebrassy said:
It's boot_a and boot_b, there is no aboot_b partition
Click to expand...
Click to collapse
I just download the folder and ran the code (almost) exactly as estated on the topic I read here. I just added the "." because I was running it on powershell, not cmd.
But... I get what you're saying. It totally makes sense, but what about the following lines?
Code:
Sending 'aboot_a' (672 KB) OKAY [ 0.055s]
Writing 'aboot_a' OKAY [ 0.005s]
After i i flash custom rom the i cant turn on the wifi so i decided to reset factory of my red magic 3 but after a rest i got stuck in FASTBOOT MODE no matter what i choice from reboot from recovery mode or reboot from system it will just restart and back again to FASTBOOT MODE can some one help me please is this permanent brick?
I USE ALL COMMANDS BUT DON'T WORK :
C:\Users\PC-NaMi\Downloads\NX629J-update_2.30>fastboot oem nubia_unlock NUBIA_NX629J
...
(bootloader) START update nubia fastboot unlock flag!!!
(bootloader) set state to 1 ok!!!
OKAY [ 0.011s]
finished. total time: 0.011s
C:\Users\PC-NaMi\Downloads\NX629J-update_2.30>fastboot flash vbmeta vbmeta.img
target reported max download size of 805306368 bytes
sending 'vbmeta' (8 KB)...
OKAY [ -0.000s]
writing 'vbmeta'...
OKAY [ -0.000s]
finished. total time: 0.016s
C:\Users\PC-NaMi\Downloads\NX629J-update_2.30>fastboot flash dsp dspso.bin
target reported max download size of 805306368 bytes
sending 'dsp' (65536 KB)...
OKAY [ 1.819s]
writing 'dsp'...
OKAY [ 0.406s]
finished. total time: 2.230s
C:\Users\PC-NaMi\Downloads\NX629J-update_2.30>fastboot flash splash splash.img
target reported max download size of 805306368 bytes
sending 'splash' (7419 KB)...
OKAY [ 0.219s]
writing 'splash'...
OKAY [ 0.031s]
finished. total time: 0.266s
C:\Users\PC-NaMi\Downloads\NX629J-update_2.30>fastboot flash modem NON-HLOS.bin
target reported max download size of 805306368 bytes
sending 'modem' (144196 KB)...
OKAY [ 4.018s]
writing 'modem'...
OKAY [ 0.869s]
finished. total time: 4.888s
C:\Users\PC-NaMi\Downloads\NX629J-update_2.30>fastboot flash boot boot.img
target reported max download size of 805306368 bytes
sending 'boot' (98304 KB)...
OKAY [ 2.780s]
writing 'boot'...
OKAY [ 0.469s]
finished. total time: 3.253s
C:\Users\PC-NaMi\Downloads\NX629J-update_2.30>fastboot flash dtbo dtbo.img
target reported max download size of 805306368 bytes
sending 'dtbo' (8192 KB)...
OKAY [ 0.234s]
writing 'dtbo'...
OKAY [ 0.063s]
finished. total time: 0.297s
C:\Users\PC-NaMi\Downloads\NX629J-update_2.30>fastboot flash system system.img
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
erasing 'system'...
OKAY [ 0.172s]
sending sparse 'system' (767446 KB)...
OKAY [ 24.161s]
writing 'system'...
OKAY [ 0.016s]
sending sparse 'system' (786430 KB)...
OKAY [ 33.767s]
writing 'system'...
OKAY [ 0.016s]
sending sparse 'system' (744616 KB)...
OKAY [ 30.043s]
writing 'system'...
OKAY [ -0.000s]
sending sparse 'system' (786429 KB)...
OKAY [ 37.173s]
writing 'system'...
OKAY [ 0.003s]
sending sparse 'system' (532404 KB)...
OKAY [ 26.319s]
writing 'system'...
OKAY [ 0.002s]
finished. total time: 151.675s
C:\Users\PC-NaMi\Downloads\NX629J-update_2.30>fastboot flash recovery recovery.img
target reported max download size of 805306368 bytes
sending 'recovery' (98304 KB)...
OKAY [ 2.800s]
writing 'recovery'...
OKAY [ 0.523s]
finished. total time: 3.339s
Instructions are everywhere. Follow them, or forever hold your peace.
after "fastboot flash recovery recovery.img"
write fastboot oem nubia_lock NUBIA_NX629J
and then fastboot reboot
u will get into recovery mode
Sir my Nubia red Magic 3 stuck on logo can any one help me please