Database Develop

S-off 1.44 hboot but cant flash recovery

ok I have 2 htc one, I s-off'ed one 6 months ago and its been working fine since then.
but today I tried to s-off the other one may built having hboot 1.44
I got it s-off successfully and unlocked but there are no red warning that your htc one is a development blah blah on the welcome screen
I flashed the twrp recovery 3 times but when I enter the recovery mode first a blue screen appears and then the red triangle with exclamation mark!
note: the custome recovery flashes successfully
also I have used fastboot erase cache also

Just to clear things up: S-off was achieved back in June/early July for Hboot 1.44
Hboot 1.54 S-off was achieved two weeks ago with a different method to the first one.
Hboot 1.44 modified Hboots are available where the red warning flag has been removed, and I guess you put that one on your second One.

gunswordx said:
ok I have 2 htc one, I s-off'ed one 6 months ago and its been working fine since then.
but today I tried to s-off the other one may built having hboot 1.44
I got it s-off successfully and unlocked but there are no red warning that your htc one is a development blah blah on the welcome screen
I flashed the twrp recovery 3 times but when I enter the recovery mode first a blue screen appears and then the red triangle with exclamation mark!
note: the custome recovery flashes successfully
also I have used fastboot erase cache also
Click to expand...
Click to collapse
Bad download? Try to download Twrp again or try CWM rercovery

hardstuffmuc said:
Just to clear things up: S-off was achieved back in June/early July for Hboot 1.44
Hboot 1.54 S-off was achieved two weeks ago with a different method to the first one.
Hboot 1.44 modified Hboots are available where the red warning flag has been removed, and I guess you put that one on your second One.
Click to expand...
Click to collapse
I tried the old revone method(same file I used for the previous one)
also I checked the md5 and have download almost all the versions of twrp. to be sure I even flashed it on my previous one and was working there

I would also try the CWM recovery with
fastboot erase cache
fastboot flash recovery recovery.img
fastboot erase cache
and make sure you use a USB 2.0 on your computer. Apparently USB 3.0 may cause problems

hardstuffmuc said:
I would also try the CWM recovery with
fastboot erase cache
fastboot flash recovery recovery.img
fastboot erase cache
and make sure you use a USB 2.0 on your computer. Apparently USB 3.0 may cause problems
Click to expand...
Click to collapse
yes tried all the recoveries
the thing is even though fastboot says flashed successfully, the stock recovery is still there !
also i have only usb 2.0

gunswordx said:
yes tried all the recoveries
the thing is even though fastboot says flashed successfully, the stock recovery is still there !
also i have only usb 2.0
Click to expand...
Click to collapse
can you copy/paste the command prompt, including a DIR of the folder, so we can take a look?

251|[email protected]:/data/local/tmp $
c:\ADB>adb shell
[email protected]:/ $ cd /data/local/tmp
cd /data/local/tmp
[email protected]:/data/local/tmp $ ./revone -P
./revone -P
revone v0.2.1
Gaining root access (thanks to Dan's motochopper)...Success.
revone successful - no need to reboot.
10|[email protected]:/data/local/tmp $ ./revone -s 0 -u
./revone -s 0 -u
revone v0.2.1
Gaining root access (thanks to Dan's motochopper)...Success.
revone successful.
[email protected]:/data/local/tmp $ exit
exit
c:\ADB>adb reboot-bootloader
c:\ADB>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
sending 'recovery' (8432 KB)...
OKAY [ 1.186s]
writing 'recovery'...
OKAY [ 0.640s]
finished. total time: 1.841s
c:\ADB>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
sending 'recovery' (8432 KB)...
OKAY [ 1.186s]
writing 'recovery'...
OKAY [ 0.640s]
finished. total time: 1.825s
c:\ADB>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
sending 'recovery' (8432 KB)...
OKAY [ 1.186s]
writing 'recovery'...
OKAY [ 0.655s]
finished. total time: 1.841s
c:\ADB>fastboot flash recovery recovery.img
< waiting for device >
sending 'recovery' (7270 KB)...
OKAY [ 1.201s]
writing 'recovery'...
OKAY [ 0.593s]
finished. total time: 1.810s
c:\ADB>fastboot flash recovery recovery.img
sending 'recovery' (7270 KB)...
OKAY [ 1.201s]
writing 'recovery'...
OKAY [ 0.608s]
finished. total time: 1.810s
c:\ADB>fastboot oem writecid 11111111
< waiting for device >
...
(bootloader) Start Verify: 0
OKAY [ 0.016s]
finished. total time: 0.016s
c:\ADB>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.031s]
finished. total time: 0.031s
c:\ADB>fastboot erase cache
erasing 'cache'...
OKAY [ 0.062s]
finished. total time: 0.062s
c:\ADB>fastboot flash recovery recovery-clockwork-touch-6.0.4.4-m7ul.img
sending 'recovery' (8840 KB)...
OKAY [ 1.201s]
writing 'recovery'...
OKAY [ 0.655s]
finished. total time: 1.856s
c:\ADB>fastboot erase cache
erasing 'cache'...
OKAY [ 0.047s]
finished. total time: 0.062s
c:\ADB>fastboot flash recovery recovery-clockwork-touch-6.0.4.4-m7ul.img
sending 'recovery' (8840 KB)...
OKAY [ 1.206s]
writing 'recovery'...
OKAY [ 0.663s]
finished. total time: 1.871s
c:\ADB>fastboot flash recovery recovery-TWRP-newbl.img
sending 'recovery' (7238 KB)...
OKAY [ 1.201s]
writing 'recovery'...
OKAY [ 0.593s]
finished. total time: 1.794s
c:\ADB>fastboot erase cache
erasing 'cache'...
OKAY [ 0.047s]
finished. total time: 0.047s
c:\ADB>adb reboot-bootloader
c:\ADB>

gunswordx said:
251|[email protected]:/data/local/tmp $
c:\ADB>adb shell
[email protected]:/ $ cd /data/local/tmp
cd /data/local/tmp
[email protected]:/data/local/tmp $ ./revone -P
./revone -P
revone v0.2.1
Gaining root access (thanks to Dan's motochopper)...Success.
revone successful - no need to reboot.
10|[email protected]:/data/local/tmp $ ./revone -s 0 -u
./revone -s 0 -u
revone v0.2.1
Gaining root access (thanks to Dan's motochopper)...Success.
revone successful.
[email protected]:/data/local/tmp $ exit
exit
c:\ADB>adb reboot-bootloader
c:\ADB>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
sending 'recovery' (8432 KB)...
OKAY [ 1.186s]
writing 'recovery'...
OKAY [ 0.640s]
finished. total time: 1.841s
c:\ADB>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
sending 'recovery' (8432 KB)...
OKAY [ 1.186s]
writing 'recovery'...
OKAY [ 0.640s]
finished. total time: 1.825s
c:\ADB>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
sending 'recovery' (8432 KB)...
OKAY [ 1.186s]
writing 'recovery'...
OKAY [ 0.655s]
finished. total time: 1.841s
c:\ADB>fastboot flash recovery recovery.img
< waiting for device >
sending 'recovery' (7270 KB)...
OKAY [ 1.201s]
writing 'recovery'...
OKAY [ 0.593s]
finished. total time: 1.810s
c:\ADB>fastboot flash recovery recovery.img
sending 'recovery' (7270 KB)...
OKAY [ 1.201s]
writing 'recovery'...
OKAY [ 0.608s]
finished. total time: 1.810s
c:\ADB>fastboot oem writecid 11111111
< waiting for device >
...
(bootloader) Start Verify: 0
OKAY [ 0.016s]
finished. total time: 0.016s
c:\ADB>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.031s]
finished. total time: 0.031s
c:\ADB>fastboot erase cache
erasing 'cache'...
OKAY [ 0.062s]
finished. total time: 0.062s
c:\ADB>fastboot flash recovery recovery-clockwork-touch-6.0.4.4-m7ul.img
sending 'recovery' (8840 KB)...
OKAY [ 1.201s]
writing 'recovery'...
OKAY [ 0.655s]
finished. total time: 1.856s
c:\ADB>fastboot erase cache
erasing 'cache'...
OKAY [ 0.047s]
finished. total time: 0.062s
c:\ADB>fastboot flash recovery recovery-clockwork-touch-6.0.4.4-m7ul.img
sending 'recovery' (8840 KB)...
OKAY [ 1.206s]
writing 'recovery'...
OKAY [ 0.663s]
finished. total time: 1.871s
c:\ADB>fastboot flash recovery recovery-TWRP-newbl.img
sending 'recovery' (7238 KB)...
OKAY [ 1.201s]
writing 'recovery'...
OKAY [ 0.593s]
finished. total time: 1.794s
c:\ADB>fastboot erase cache
erasing 'cache'...
OKAY [ 0.047s]
finished. total time: 0.047s
c:\ADB>adb reboot-bootloader
c:\ADB>
Click to expand...
Click to collapse
why use revone again, and why so many flashes?
Just:
adb reboot bootloader (no - needed in adb)
fastboot flash recovery recovery-clockwork-touch-6.0.4.4-m7ul.img
fastboot erase cache
fastboot reboot-bootloader (- is needed in fastboot)
Then just select RECOVERY using VOL Up or Down, press POWER to enter into recovery.

the first time revone didn't work so I had to do it again.
got s-off and super cid
after each recovery flash I rebooted bootloader and went to recovery but same red triangle
that's why so many recovery flashes

gunswordx said:
the first time revone didn't work so I had to do it again.
got s-off and super cid
after each recovery flash I rebooted bootloader and went to recovery but same red triangle
that's why so many recovery flashes
Click to expand...
Click to collapse
OK, just reboot your phone and try the steps, I posted above.

tried but same result. I can't seem to flash the recovery even though the cmd window says successful

gunswordx said:
tried but same result. I can't seem to flash the recovery even though the cmd window says successful
Click to expand...
Click to collapse
very weird, you feel like trying one more time?
Download this:
recovery-clockwork-touch-6.0.3.2-m7--v2.img (7.2 MB)
https://mega.co.nz/#!6E8RiIrQ!GF5LyhmEdg8OQJxuQVVjwSxBljxhW7xsZAHLzjVACsc
Check MD5: 1c6afb14db3f305b0ad7d85d5af80bef
adb reboot bootloader
fastboot erase cache
fastboot flash recovery recovery-clockwork-touch-6.0.3.2-m7--v2.img
fastboot erase cache
fastboot reboot
adb reboot recovery
and post back command prompt.

nkk71 said:
very weird, you feel like trying one more time?
Download this:
recovery-clockwork-touch-6.0.3.2-m7--v2.img (7.2 MB)
https://mega.co.nz/#!6E8RiIrQ!GF5LyhmEdg8OQJxuQVVjwSxBljxhW7xsZAHLzjVACsc
Check MD5: 1c6afb14db3f305b0ad7d85d5af80bef
adb reboot bootloader
fastboot erase cache
fastboot flash recovery recovery-clockwork-touch-6.0.3.2-m7--v2.img
fastboot erase cache
fastboot reboot
adb reboot recovery
and post back command prompt.
Click to expand...
Click to collapse
ok will try

[HELP] - Bootloop, Cant access recovery, Cant factory reset

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

fastboot reboot "failed" after unlooking bootloader

Hello,
after unlooking bootloader of my Sony X Z3c (D5803), I tried to fastboot flash boot "Z_DooMLoRD_CF-Auto-Root-ported_FW-350.img" But got the message:
target didn't report max-download-size
sending 'boot' (7166 KB)...
OKAY [ 0.235s]
writing 'boot'...
OKAY [ 0.476s]
finished. total time: 0.726s
No error while fastboot reboot:
rebooting...
finished. total time: 0.000s
BUT the phone did not reboot. By pressing "power" and "Vol down" phone vibrated once, "Sony Xperia" appears and that's it. No soft or hard reset works.
Thanks for your help
Tony

Help please !

I am leaving house for 2 weeks in 7 hours i realluy need help in flashing my phone I cant flash Vendor in fastboot
and i think it doesnt boot becxause of error flashing and erasing vendor
C:\Users\Matas Niewulis\Desktop\Pulpit>fastboot flash recovery twrp-3.1.1-2-v1-prague.img
target reported max download size of 471859200 bytes
sending 'recovery' (24468 KB)...
OKAY [ 0.855s]
writing 'recovery'...
OKAY [ 0.313s]
finished. total time: 2.042s
C:\Users\Matas Niewulis\Desktop\Pulpit>
C:\Users\Matas Niewulis\Desktop\Pulpit>fastboot flash erase vendor
error: cannot load 'vendor'
C:\Users\Matas Niewulis\Desktop\Pulpit>fastboot erase vendor
erasing 'vendor'...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
C:\Users\Matas Niewulis\Desktop\Pulpit>fastboot reboot
rebooting...
finished. total time: 0.341s
C:\Users\Matas Niewulis\Desktop\Pulpit>
please help me fix my device.. sorry for a mess in this post, im in a hurry

ooooh **** i restored my device to working oreder by doing fix vendor partition in twrp..

but i still have the problem with fingerprint, security, dev options etc

Vendor you can flash only by twrp/ restoring.
Which firmware do you have?

fastboot boot recovery.img FAILED(remote: unknown command)

Hey guys,
I have ZTE Red Magic with an unlocked bootloader. It is my first time rooting, and after unlocking the bootloader, I wanted to boot TWRP. So I booted into the bootloader, entered "fastboot boot recovery.img" and I got this message:
downloading 'boot.img'...
OKAY [ 0.579s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.582s
The installation of recovery was successful as I typed the command "fastboot flash recovery recovery.img"
target reported max download size of 536870912 bytes
sending 'recovery' (26721 KB)...
OKAY [ 0.580s]
writing 'recovery'...
OKAY [ 0.001s]
finished. total time: 0.583s
I have absolutely no idea what I'm doing wrong. pls help

boyDbest said:
Hey guys,
I have ZTE Red Magic with an unlocked bootloader. It is my first time rooting, and after unlocking the bootloader, I wanted to boot TWRP. So I booted into the bootloader, entered "fastboot boot recovery.img" and I got this message:
downloading 'boot.img'...
OKAY [ 0.579s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.582s
The installation of recovery was successful as I typed the command "fastboot flash recovery recovery.img"
target reported max download size of 536870912 bytes
sending 'recovery' (26721 KB)...
OKAY [ 0.580s]
writing 'recovery'...
OKAY [ 0.001s]
finished. total time: 0.583s
I have absolutely no idea what I'm doing wrong. pls help
Click to expand...
Click to collapse
Did you unlocked bootloader?

methuselah said:
Did you unlocked bootloader?
Click to expand...
Click to collapse
Yes brother i did