Related
A flash went bad. Now I am stuck on the bootloop. I amn able to access both recovery as well as fastboot.
Tried pushing a rom via cmd on pc in adb, and it doesn;t go through.
Please help flash a rom via fastboot.
So far on my attempts, I get this in cmd:
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater th
an
size. 0 to disable
I have faced the same issue in the past with our device...Use adb side load... If it doesn't work, its most likely that your partitions are corrupted so you will have to reflash the stock firmware and then flash the recovery and repeat the ROM flashing procedure....
Sent from my Moto G using XDA Premium 4 mobile app
I feel like I'm in the weirdest situation I've ever come across. In an attempt to root the Moto G, I unlocked the bootloader and wiped the data. I have looked at every tutorial that tells me to flash the stock rom with the mfastboot command, and all it does is reboot nonstop. After the motoboot, it'll give me a screen that says "Starting Services" and it will not do anything except eventually give me an error message that said "Unfortunately, Google Play Services has stopped" or something similar, then just repeat this cycle.
The only theory I have is that my battery may not be charged enough to handle anything, but then I come to the problem of not being about to charge. I can't charge it while it's doing this, since it has been staying at 1% for the longest, and I'm not sure if my phone is even charging when I'm on the fastboot/bootloader menu, whether it's plugged into my laptop or an outlet. I do know that when I plug it up to my laptop, it says "Charging", but when I plug it up to a wall, it doesn't (this all being in the bootloader menu).
At this point I'm wondering if I truly did brick my phone, but the fact that I can still load fastboot and flash stock recoveries and custom recoveries would make that theory seem really off.
Additional Details: I have a XT1031, Boost phone US. I do believe that before I unlocked bootloader, they rolled out the 4.4.4 update (I can only assume it was 4.4.4 at this point), which caused my phone to not charge for a while, though it did eventually, but it gave me a big question mark before I booted my phone, not even charging, and it's doing that now. What I tried to do was flash the 4.4.2 stock rom to get it working, but this has lead to only these results.
Can I flash Verizon 4.4.4 stock rom just to get to the adb?
Update 2:44pm: Battery started charging simply by changing the cord.
Update 7:16pm: Was able to find a better motoboot img suited for my phone, but still can't get gpt.bin to get past the "preflash validation".
Picture in Attachment.
Command log from rom installation
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Cam>C:\Users\Cam\Downloads\adt-bundle-windows-x86_64-20130522\adt-bundl
e-windows-x86_64-20130522\sdk\platform-tools
'C:\Users\Cam\Downloads\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-x8
6_64-20130522\sdk\platform-tools' is not recognized as an internal or external c
ommand,
operable program or batch file.
C:\Users\Cam>cd C:\Users\Cam\Downloads\adt-bundle-windows-x86_64-20130522\adt-bu
ndle-windows-x86_64-20130522\sdk\platform-tools
C:\Users\Cam\Downloads\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-x86
_64-20130522\sdk\platform-tools>fastboot.exe -w
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 0.237s]
erasing 'cache'...
OKAY [ 0.079s]
finished. total time: 0.322s
C:\Users\Cam\Downloads\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-x86
_64-20130522\sdk\platform-tools>C:\Users\Cam\Downloads\adt-bundle-windows-x86_64
-20130522\adt-bundle-windows-x86_64-20130522\sdk\platform-tools\Something
'C:\Users\Cam\Downloads\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-x8
6_64-20130522\sdk\platform-tools\Something' is not recognized as an internal or
external command,
operable program or batch file.
C:\Users\Cam\Downloads\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-x86
_64-20130522\sdk\platform-tools>cd C:\Users\Cam\Downloads\adt-bundle-windows-x86
_64-20130522\adt-bundle-windows-x86_64-20130522\sdk\platform-tools\Something
C:\Users\Cam\Downloads\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-x86
_64-20130522\sdk\platform-tools\Something>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.066s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.444s
C:\Users\Cam\Downloads\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-x86
_64-20130522\sdk\platform-tools\Something>mfastboot.exe -w
erasing 'userdata'...
OKAY [ 0.215s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.017s]
erasing 'cache'...
OKAY [ 0.071s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.016s]
finished. total time: 0.326s
C:\Users\Cam\Downloads\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-x86
_64-20130522\sdk\platform-tools\Something>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.043s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.402s
C:\Users\Cam\Downloads\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-x86
_64-20130522\sdk\platform-tools\Something>fastboot flash motoboot motoboot.img
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\Cam\Downloads\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-x86
_64-20130522\sdk\platform-tools\Something>mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1940 KB)...
OKAY [ 0.116s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.442s
C:\Users\Cam\Downloads\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-x86
_64-20130522\sdk\platform-tools\Something>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (619 KB)...
OKAY [ 0.092s]
writing 'logo'...
OKAY [ 0.126s]
finished. total time: 0.223s
C:\Users\Cam\Downloads\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-x86
_64-20130522\sdk\platform-tools\Something>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.390s]
writing 'boot'...
OKAY [ 1.002s]
finished. total time: 1.396s
C:\Users\Cam\Downloads\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-x86
_64-20130522\sdk\platform-tools\Something>fastboot flash recovery recovery.img
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\Cam\Downloads\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-x86
_64-20130522\sdk\platform-tools\Something>mfastbook.exe -w
'mfastbook.exe' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\Cam\Downloads\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-x86
_64-20130522\sdk\platform-tools\Something>mfastboot,exe -w
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache
-P enable parallel loading for multi-fla
sh if
there is no enough memory on host to
load
whole image
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater th
an
size. 0 to disable
C:\Users\Cam\Downloads\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-x86
_64-20130522\sdk\platform-tools\Something>mfastboot.exe -w
erasing 'userdata'...
OKAY [ 0.230s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.029s]
erasing 'cache'...
OKAY [ 0.110s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.026s]
finished. total time: 0.407s
C:\Users\Cam\Downloads\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-x86
_64-20130522\sdk\platform-tools\Something>fastboot -w
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\Cam\Downloads\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-x86
_64-20130522\sdk\platform-tools\Something>mfastboot -w
erasing 'userdata'...
OKAY [ 0.215s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.024s]
erasing 'cache'...
OKAY [ 0.067s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type raw not supported.
OKAY [ 0.025s]
finished. total time: 0.346s
C:\Users\Cam\Downloads\adt-bundle-windows-x86_64-20130522\adt-bundle-windows-x86
_64-20130522\sdk\platform-tools\Something>
Classy Developer said:
I feel like I'm in the weirdest situation I've ever come across. In an attempt to root the Moto G, I unlocked the bootloader and wiped the data. I have looked at every tutorial that tells me to flash the stock rom with the mfastboot command, and all it does is reboot nonstop. After the motoboot, it'll give me a screen that says "Starting Services" and it will not do anything except eventually give me an error message that said "Unfortunately, Google Play Services has stopped" or something similar, then just repeat this cycle.
The only theory I have is that my battery may not be charged enough to handle anything, but then I come to the problem of not being about to charge. I can't charge it while it's doing this, since it has been staying at 1% for the longest, and I'm not sure if my phone is even charging when I'm on the fastboot/bootloader menu, whether it's plugged into my laptop or an outlet. I do know that when I plug it up to my laptop, it says "Charging", but when I plug it up to a wall, it doesn't (this all being in the bootloader menu).
At this point I'm wondering if I truly did brick my phone, but the fact that I can still load fastboot and flash stock recoveries and custom recoveries would make that theory seem really off.
Additional Details: I have a XT1031, Boost phone US. I do believe that before I unlocked bootloader, they rolled out the 4.4.4 update (I can only assume it was 4.4.4 at this point), which caused my phone to not charge for a while, though it did eventually, but it gave me a big question mark before I booted my phone, not even charging, and it's doing that now. What I tried to do was flash the 4.4.2 stock rom to get it working, but this has lead to only these results.
Can I flash Verizon 4.4.4 stock rom just to get to the adb?
Update 2:44pm: Battery started charging simply by changing the cord.
Update 7:16pm: Was able to find a better motoboot img suited for my phone, but still can't get gpt.bin to get past the "preflash validation".
Picture in Attachment.
Click to expand...
Click to collapse
Were you ever able to fix this? I'm having the same issue.
ejames2001 said:
Were you ever able to fix this? I'm having the same issue.
Click to expand...
Click to collapse
Me too, have you fixed it?
Q&A for [ GUIDE ]unlock bootloader and **ROOT** for ALCATEL IDOL 3 6045
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ GUIDE ]unlock bootloader and **ROOT** for ALCATEL IDOL 3 6045. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
famewolf said:
That's great for those who are buying their phones now....some of us rooted before twrp was an option and you CAN'T create image backups of system until you HAVE root.
Click to expand...
Click to collapse
I have not yet rooted my phone and would like to make a pre-root backup but have no idea how that would be done. I don't know much when it comes to developing. Is it actually possible to create a backup without root?
totalrecarl said:
I have not yet rooted my phone and would like to make a pre-root backup but have no idea how that would be done. I don't know much when it comes to developing. Is it actually possible to create a backup without root?
Click to expand...
Click to collapse
Yes, just boot on TWRP (read only mode) and backup as usually
frankee207 said:
Yes, just boot on TWRP (read only mode) and backup as usually
Click to expand...
Click to collapse
Would I need to do that via fastboot or could I flash it with Flashify? Sorry for all the questions, I don't have much experience in this area.
totalrecarl said:
Would I need to do that via fastboot or could I flash it with Flashify? Sorry for all the questions, I don't have much experience in this area.
Click to expand...
Click to collapse
You must do it through fastboot. Reboot in bootloader and boot into TWRP. Have a look to unlock and root thread. It's explained how root using TWRP. Do the same, but don't flash SuperSu, just perform backup
how we will upgrade to OTAs? can we flash em?
gecko702 said:
how we will upgrade to OTAs? can we flash em?
Click to expand...
Click to collapse
Detailed info is here with step by step instructions: http://forum.xda-developers.com/idol-3/help/want-to-able-to-install-ota-updates-t3163745
am i doing it wrong?
this is all iget every time i input the commands
C:\Users\Surgat_AND_Nath\Desktop\Downloads\IDOL3_6045_ROOT>adb reboot-bootloader
C:\Users\Surgat_AND_Nath\Desktop\Downloads\IDOL3_6045_ROOT>fastboot-i0x1bbb devi
ces
'fastboot-i0x1bbb' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\Surgat_AND_Nath\Desktop\Downloads\IDOL3_6045_ROOT>fastboot -i0x1bbb dev
ices
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
C:\Users\Surgat_AND_Nath\Desktop\Downloads\IDOL3_6045_ROOT>fastboot -i0x1bbb oem
device-info
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
C:\Users\Surgat_AND_Nath\Desktop\Downloads\IDOL3_6045_ROOT>fastboot -i0x1bbb oem
unlock
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
C:\Users\Surgat_AND_Nath\Desktop\Downloads\IDOL3_6045_ROOT>fastboot -i0x1bbb ome
n device-info
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
C:\Users\Surgat_AND_Nath\Desktop\Downloads\IDOL3_6045_ROOT>fastboot -i0x1bbb reb
oot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
C:\Users\Surgat_AND_Nath\Desktop\Downloads\IDOL3_6045_ROOT>
surgat666 said:
this is all iget every time i input the commands
C:\Users\Surgat_AND_Nath\Desktop\Downloads\IDOL3_6045_ROOT>adb reboot-bootloader
C:\Users\Surgat_AND_Nath\Desktop\Downloads\IDOL3_6045_ROOT>fastboot-i0x1bbb devi
ces
'fastboot-i0x1bbb' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\Surgat_AND_Nath\Desktop\Downloads\IDOL3_6045_ROOT>fastboot -i0x1bbb dev
ices
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
C:\Users\Surgat_AND_Nath\Desktop\Downloads\IDOL3_6045_ROOT>fastboot -i0x1bbb oem
device-info
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
C:\Users\Surgat_AND_Nath\Desktop\Downloads\IDOL3_6045_ROOT>fastboot -i0x1bbb oem
unlock
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
C:\Users\Surgat_AND_Nath\Desktop\Downloads\IDOL3_6045_ROOT>fastboot -i0x1bbb ome
n device-info
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
C:\Users\Surgat_AND_Nath\Desktop\Downloads\IDOL3_6045_ROOT>fastboot -i0x1bbb reb
oot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
C:\Users\Surgat_AND_Nath\Desktop\Downloads\IDOL3_6045_ROOT>
Click to expand...
Click to collapse
Look at the example. There is a space both before and after the -i
Bootloader won't show
I followed the procedures to enter boot-loader but my phone will not do.
Here is the procedures I have followed through (the red text is where it fails)
Get/install Alcatel USB driver if Windows. (no need for Mac). FROM HERE, or just connect your idol3 to the computer and from the phone select "cd rom" drive..it will install the drivers automatically
download the root zip from my GOOGLE DRIVE and unzip it.
Set USB debugging on in Developer settings (if these are not exposed, go to Settings/About Phone/Build number, and tap 7 times.)
Plug in USB cable to phone and computer. Tap on USB icon in notifications panel; select MTP (file transfer) mode.
Open command prompt in direcotry where you have the unzipped files (when using windows in the direcotry hold shift and press the right button on the mouse, it will pop-up a window where you have to select "open command promt here" and type "adb reboot-bootloader" to reboot into bootloader
Specifications of the phone
Model Number - 6045I
Android version - 5.0.2
Kernel Version - 3.10.49
Build Number - 7SQR-UER0
I am trying to offer my TWRP backup to the following forum
All that appears is this frozen screen on the phone and when I try to use command prompt to detect if any devices are currently connected, nothing shows ("fastboot devices" & "fastboot -i 0x1bbb devices" are both not stating any devices)
Frozen image of alcatel trying to enter bootloader
IsaacEncinas said:
I followed the procedures to enter boot-loader but my phone will not do.
Frozen image of alcatel trying to enter bootloader
Click to expand...
Click to collapse
That IS the bootloader, IsaacEncinas. Unlike other devices, like the Nexus ones I know, this bootloader screen doesn't look like anything. It seems like it's stuck somewhere, but it's not. That threw me off at one point, too. Use fastboot commands from that screen to see if, in fact, you're there.
Code:
fastboot -i 0x1bbb devices
Then, if you get something returned, try booting into TWRP using fastboot.
Code:
fastboot -i 0x1bbb boot twrp-2.8.7.0-idol3.img
This assumes that you have the TWRP image present in the Windows directory where your command line is.
Well like I said, I tried the following commands that you have stated including "fastboot devices", nothing was given in return. Shall I fall through with the commands hopes of a return? I highly doubt it would work though since it was not being detected.
EDIT:
So i skipped and ignored trying to find why the device did not get detected. I went ahead and applied the following code.
Code:
fastboot -i 0x1bbb boot twrp-2.8.7.0-idol3.img
and it worked! Thanks!
Sent from my 6045I using XDA Free mobile app
Good!
alcatel OT 6045Y idol 3
will this proccess works on 6045Y version?
thanks
harrisxr650 said:
will this proccess works on 6045Y version?
thanks
Click to expand...
Click to collapse
Yes
I have the root and now I can't update the phone, what can I do?
6045k
Enviado do meu Alcatel Idol 3 5.5" através do Tapatalk
Yep. That's how it works.
RodrigoIsaac said:
I have the root and now I can't update the phone, what can I do?
6045k
Enviado do meu Alcatel Idol 3 5.5" através do Tapatalk
Click to expand...
Click to collapse
RodrigoIsaac, there's lots of talk all over this forum about exactly this subject. You need to revert to stock to take the OTA. Then, you can root again. Read through the topics for plenty of detail.
Yes but the update isn't out for 6045k yet ..
Cant find device?
Im trying to do whatever I can, when I open command window at the unzipped folder and type adb reboot-bootloader, it starts but right after a second it says: "error: device not found" I cant figure out whats wrong, I put the usb debugging mode, turned on the drive, installed the drivers, switched to file transfer mode, and it still says "device not found", I have the Alcatel Idol 3 5,5i 32gb dual sim version without an SD card slot. Please help!
I got an OTA update for marshmallow. At this stage phone was locked, unrooted and not tampered with.
After updating OTA phone went into a bootloop.
'Allow OEM Unlock' is disabled from developer options before even updating OTA so bootloader can't be unlocked.
After bootloop, from bootloader using fastboot (and mfastboot also tried) I flashed "XT1550_OSPREY_RETASIA_DS_2GB_6.0.1_MPI24.107..... ..." this marshmallow firmware using standard commands for newer Moto devies. Even after flashing firmware, still bootloop happens.
Code:
fastboot flash bootloader O:\MotoG3\Firmwares\bootloader.img
fastboot flash logo O:\MotoG3\Firmwares\logo.bin
fastboot flash boot O:\MotoG3\Firmwares\boot.img
fastboot flash recovery O:\MotoG3\Firmwares\recovery.img
fastboot flash system O:\MotoG3\Firmwares\system.img_sparsechunk.0
fastboot flash system O:\MotoG3\Firmwares\system.img_sparsechunk.1
fastboot flash system O:\MotoG3\Firmwares\system.img_sparsechunk.2
fastboot flash system O:\MotoG3\Firmwares\system.img_sparsechunk.3
fastboot flash system O:\MotoG3\Firmwares\system.img_sparsechunk.4
fastboot flash system O:\MotoG3\Firmwares\system.img_sparsechunk.5
fastboot flash system O:\MotoG3\Firmwares\system.img_sparsechunk.6
fastboot flash system O:\MotoG3\Firmwares\system.img_sparsechunk.7
fastboot flash modem O:\MotoG3\Firmwares\NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg O:\MotoG3\Firmwares\fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
pause
At this stage, phone still goes into a bootloop. Clicking on recovery from bootloader also sends phone into a bootloop so can't even access stock recovery.
Also no way to erase system as bootloader is locked.
How do I get the phone back in working state, my device is not in warranty now.
Other bootloop guides were not useful as here even after flashing stock firmware phone still goes into a bootloop. ALso no stock recovery is accessible and BL is locked.
Thanks in advance
Did everything return an OKAY?? Can you copy the whole command prompt text here, it can be really helpful.
Broadcasted from Zeta Reticuli
Yes everything went fine no issue in any command,command prompt code will re-post once i'll try again to flash stock ROM.
On the bootloader menu, connect to computer and type-
#removed code,it was invalid.#
Check if you get the default recovery screen now. We have to restore factory settings from the stock recovery first before flashing stock images. So if by this method you can access stock recovery (as you have already flashed it) you can just factory restore and again flash factory images. Best of luck.
Broadcasted from Zeta Reticuli
No this command is invalid , not working with my case.
Gravemind2015 said:
On the bootloader menu, connect to computer and type-
Code:
fastboot reboot recovery
Check if you get the default recovery screen now. We have to restore factory settings from the stock recovery first before flashing stock images. So if by this method you can access stock recovery (as you have already flashed it) you can just factory restore and again flash factory images. Best of luck.
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
No this command is invalid , not working with my case.
sanju25 said:
No this command is invalid , not working with my case.
Click to expand...
Click to collapse
Yes I forgot to edit my reply, I became aware of that. I actually read it somewhere and confused with adb.
Is the phone rebooting when you go to bootloader>volume down>recovery?
Broadcasted from Zeta Reticuli
Here is whole command prompt code @Gravemind2015
sanju25 said:
Yes everything went fine no issue in any command,command prompt code will re-post once i'll try again to flash stock ROM.
Click to expand...
Click to collapse
Code:
C:\Users\dell\Desktop\Moto Software\adb-fastboot-latest_win_linux>fastboot flash partition gpt.bin
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.007s]
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
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.715s]
finished. total time: 0.727s
C:\Users\dell\Desktop\Moto Software\adb-fastboot-latest_win_linux>fastboot flash bootloader bootloader.img
target reported max download size of 268435456 bytes
sending 'bootloader' (2546 KB)...
OKAY [ 0.089s]
writing 'bootloader'...
(bootloader) flashing sbl1 ...
(bootloader) flashing aboot ...
(bootloader) flashing tz ...
(bootloader) flashing hyp ...
(bootloader) flashing rpm ...
OKAY [ 1.503s]
finished. total time: 1.600s
C:\Users\dell\Desktop\Moto Software\adb-fastboot-latest_win_linux>fastboot flash logo logo.bin
target reported max download size of 268435456 bytes
sending 'logo' (1352 KB)...
OKAY [ 0.051s]
writing 'logo'...
OKAY [ 0.065s]
finished. total time: 0.122s
C:\Users\dell\Desktop\Moto Software\adb-fastboot-latest_win_linux>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.524s]
writing 'boot'...
OKAY [ 0.761s]
finished. total time: 1.291s
C:\Users\dell\Desktop\Moto Software\adb-fastboot-latest_win_linux>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.526s]
writing 'recovery'...
OKAY [ 0.767s]
finished. total time: 1.301s
C:\Users\dell\Desktop\Moto Software\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.0
target reported max download size of 268435456 bytes
sending 'system' (247489 KB)...
OKAY [ 7.767s]
writing 'system'...
OKAY [ 6.453s]
finished. total time: 14.229s
C:\Users\dell\Desktop\Moto Software\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.1
target reported max download size of 268435456 bytes
sending 'system' (230229 KB)...
OKAY [ 7.314s]
writing 'system'...
OKAY [ 5.119s]
finished. total time: 12.442s
C:\Users\dell\Desktop\Moto Software\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.2
target reported max download size of 268435456 bytes
sending 'system' (259434 KB)...
OKAY [ 8.229s]
writing 'system'...
OKAY [ 5.816s]
finished. total time: 14.055s
C:\Users\dell\Desktop\Moto Software\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.3
target reported max download size of 268435456 bytes
sending 'system' (254590 KB)...
OKAY [ 8.079s]
writing 'system'...
OKAY [ 5.677s]
finished. total time: 13.765s
C:\Users\dell\Desktop\Moto Software\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.4
target reported max download size of 268435456 bytes
sending 'system' (254861 KB)...
OKAY [ 8.111s]
writing 'system'...
OKAY [ 6.110s]
finished. total time: 14.230s
C:\Users\dell\Desktop\Moto Software\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.5
target reported max download size of 268435456 bytes
sending 'system' (258017 KB)...
OKAY [ 8.183s]
writing 'system'...
OKAY [ 5.610s]
finished. total time: 13.802s
C:\Users\dell\Desktop\Moto Software\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.6
target reported max download size of 268435456 bytes
sending 'system' (251037 KB)...
OKAY [ 7.967s]
writing 'system'...
OKAY [ 9.902s]
finished. total time: 17.876s
C:\Users\dell\Desktop\Moto Software\adb-fastboot-latest_win_linux>fastboot flash system system.img_sparsechunk.7
target reported max download size of 268435456 bytes
sending 'system' (14420 KB)...
OKAY [ 0.549s]
writing 'system'...
OKAY [ 0.372s]
finished. total time: 0.929s
C:\Users\dell\Desktop\Moto Software\adb-fastboot-latest_win_linux>fastboot flash modem NON-HLOS.bin
target reported max download size of 268435456 bytes
sending 'modem' (36988 KB)...
OKAY [ 1.258s]
writing 'modem'...
OKAY [ 0.678s]
finished. total time: 1.940s
C:\Users\dell\Desktop\Moto Software\adb-fastboot-latest_win_linux>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.091s]
finished. total time: 0.095s
C:\Users\dell\Desktop\Moto Software\adb-fastboot-latest_win_linux>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.109s]
finished. total time: 0.113s
C:\Users\dell\Desktop\Moto Software\adb-fastboot-latest_win_linux>fastboot flash fsg fsg.mbn
target reported max download size of 268435456 bytes
sending 'fsg' (2280 KB)...
OKAY [ 0.216s]
writing 'fsg'...
OKAY [ 0.084s]
finished. total time: 0.307s
C:\Users\dell\Desktop\Moto Software\adb-fastboot-latest_win_linux>fastboot erase cache
erasing 'cache'...
OKAY [ 0.102s]
finished. total time: 0.106s
C:\Users\dell\Desktop\Moto Software\adb-fastboot-latest_win_linux>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.094s]
finished. total time: 0.097s
Gravemind2015 said:
Yes I forgot to edit my reply, I became aware of that. I actually read it somewhere and confused with adb.
Is the phone rebooting when you go to bootloader>volume down>recovery?
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
Yes, only thing phone is doing is re-booting
sanju25 said:
Yes, only thing phone is doing is re-booting
Click to expand...
Click to collapse
Sorry, after seeing the logs, I am out of ideas. You can check the folder for any extra sparsechunk files (sparsechunk8 or 9, I cant remember the exact no. For xt1550). I had to do it once and it worked flawlessly the very first time, same xt1550 and same package, weird you have to face this.
Broadcasted from Zeta Reticuli
sanju25 said:
No this command is invalid , not working with my case.
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot recovery
usage: fastboot [ <option> ] <command>
commands:
update <filename> Reflash device from update.zip.
flashall Flash boot, system, vendor, and --
if found -- recovery.
flash <partition> [ <filename> ] Write a file to a flash partition.
flashing lock Locks the device. Prevents flashing.
flashing unlock Unlocks the device. Allows flashing
any partition except
bootloader-related partitions.
flashing lock_critical Prevents flashing bootloader-related
partitions.
flashing unlock_critical Enables flashing bootloader-related
partitions.
flashing get_unlock_ability Queries bootloader to see if the
device is unlocked.
flashing get_unlock_bootloader_nonce Queries the bootloader to get the
unlock nonce.
flashing unlock_bootloader <request> Issue unlock bootloader using request.
flashing lock_bootloader Locks the bootloader to prevent
bootloader version rollback.
erase <partition> Erase a flash partition.
format[:[<fs type>][:[<size>]] <partition>
Format a flash partition. Can
override the fs type and/or size
the bootloader reports.
getvar <variable> Display a bootloader variable.
set_active <suffix> Sets the active slot. If slots are
not supported, this does nothing.
boot <kernel> [ <ramdisk> [ <second> ] ] Download and boot kernel.
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ]
Create bootimage and flash it.
devices [-l] List all connected devices [with
device paths].
continue Continue with autoboot.
reboot [bootloader] Reboot device [into bootloader].
reboot-bootloader Reboot device into bootloader.
help Show this help message.
options:
-w Erase userdata and cache (and format
if supported by partition type).
-u Do not erase partition before
formatting.
-s <specific device> Specify a device. For USB, provide either
a serial number or path to device port.
For ethernet, provide an address in the form <protocol>:<hostname>[ort] where <protocol> is either tcp or udp.
-p <product> Specify product name.
-c <cmdline> Override kernel commandline.
-i <vendor id> Specify a custom USB vendor id.
-b, --base <base_addr> Specify a custom kernel base
address (default: 0x10000000).
--kernel-offset Specify a custom kernel offset.
(default: 0x00008000)
--ramdisk-offset Specify a custom ramdisk offset.
(default: 0x01000000)
--tags-offset Specify a custom tags offset.
(default: 0x00000100)
-n, --page-size <page size> Specify the nand page size
(default: 2048).
-S <size>[K|M|G] Automatically sparse files greater
than 'size'. 0 to disable.
--slot <suffix> Specify slot suffix to be used if the
device supports slots. This will be
added to all partition names that use
slots. 'all' can be given to refer
to all slots. 'other' can be given to
refer to a non-current slot. If this
flag is not used, slotted partitions
will default to the current active slot.
-a, --set-active[=<suffix>] Sets the active slot. If no suffix is
provided, this will default to the value
given by --slot. If slots are not
supported, this does nothing. This will
run after all non-reboot commands.
--unbuffered Do not buffer input or output.
--version Display version.
-h, --help show this message
no what to do...pls help me
reeeju said:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot recovery
usage: fastboot [ ]
commands:
update Reflash device from update.zip.
flashall Flash boot, system, vendor, and --
if found -- recovery.
flash [ ] Write a file to a flash partition.
flashing lock Locks the device. Prevents flashing.
flashing unlock Unlocks the device. Allows flashing
any partition except
bootloader-related partitions.
flashing lock_critical Prevents flashing bootloader-related
partitions.
flashing unlock_critical Enables flashing bootloader-related
partitions.
flashing get_unlock_ability Queries bootloader to see if the
device is unlocked.
flashing get_unlock_bootloader_nonce Queries the bootloader to get the
unlock nonce.
flashing unlock_bootloader Issue unlock bootloader using request.
flashing lock_bootloader Locks the bootloader to prevent
bootloader version rollback.
erase Erase a flash partition.
format[:[][:[]]
Format a flash partition. Can
override the fs type and/or size
the bootloader reports.
getvar Display a bootloader variable.
set_active Sets the active slot. If slots are
not supported, this does nothing.
boot [ [ ] ] Download and boot kernel.
flash:raw boot [ [ ] ]
Create bootimage and flash it.
devices [-l] List all connected devices [with
device paths].
continue Continue with autoboot.
reboot [bootloader] Reboot device [into bootloader].
reboot-bootloader Reboot device into bootloader.
help Show this help message.
options:
-w Erase userdata and cache (and format
if supported by partition type).
-u Do not erase partition before
formatting.
-s Specify a device. For USB, provide either
a serial number or path to device port.
For ethernet, provide an address in the form :[ort] where is either tcp or udp.
-p Specify product name.
-c Override kernel commandline.
-i Specify a custom USB vendor id.
-b, --base Specify a custom kernel base
address (default: 0x10000000).
--kernel-offset Specify a custom kernel offset.
(default: 0x00008000)
--ramdisk-offset Specify a custom ramdisk offset.
(default: 0x01000000)
--tags-offset Specify a custom tags offset.
(default: 0x00000100)
-n, --page-size Specify the nand page size
(default: 2048).
-S [K|M|G] Automatically sparse files greater
than 'size'. 0 to disable.
--slot Specify slot suffix to be used if the
device supports slots. This will be
added to all partition names that use
slots. 'all' can be given to refer
to all slots. 'other' can be given to
refer to a non-current slot. If this
flag is not used, slotted partitions
will default to the current active slot.
-a, --set-active[=] Sets the active slot. If no suffix is
provided, this will default to the value
given by --slot. If slots are not
supported, this does nothing. This will
run after all non-reboot commands.
--unbuffered Do not buffer input or output.
--version Display version.
-h, --help show this message
no what to do...pls help me
Click to expand...
Click to collapse
Thats normal because fastboot does not have the option to reboot directly into recovery. So your command-
Code:
fastboot reboot recovery
is invalid.
Try this-
Code:
fastboot reboot-bootloader
From bootloader, press volume down twice to enter recovery.
Broadcasted from Zeta Reticuli
Gravemind2015 said:
Thats normal because fastboot does not have the option to reboot directly into recovery. So your command-
is invalid.
Try this-
From bootloader, press volume down twice to enter recovery.
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
Then how to get twrp recovery which image file to be flashed?
Vikas Tewatia said:
I can give u a link to the latest working twrp v3.2.0.r for moto g3
Sent from my MotoG3 using XDA Labs
Click to expand...
Click to collapse
Here is the thread : http://forum.xda-developers.com/showthread.php?t=3170537.
Broadcasted from Zeta Reticuli
Hello guys!
Today I unlocked my old oneplus 6 phone,I wanted to flash google rom,so I execute
Bash:
adb reboot bootloader
and run flash script inside google android images.
Bash:
└─$ ./flash-all.sh
Sending 'bootloader' (4620 KB) OKAY [ 0.154s]
Writing 'bootloader' FAILED (remote: 'Flashing is not allowed for Critical Partitions
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.051s
I have no idea why this happpened,so I searched on google but got nothing.
And I've tried
Bash:
└─$ fastboot flashing unlock_critical
FAILED (remote: ' Device already : unlocked!')
Since I am new to these kinds of topics,any advice would be appreciated.
did you already set fastboot flashing unlock ?
makesure your adb / platform-tools is the latest too