Hello,
I have a Sensation XE with Android_Revolution_HD-Sensation_6.0.3_XE ROM installes. Two days ago the screen become black and I cant do anything with the Phone. I cannot put it on HBOOT because the screen is always black. I can see the screen its turned on, I also called the phone and it rings.
I tried to install a recovery using Android Flasher App and I get this:
< waiting for device >
security: off
finished. total time: 0.000s
sending 'recovery' (4618 KB)...
OKAY [ 1.094s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.406s
downloading 'boot.img'...
OKAY [ 1.094s]
booting...
FAILED (remote: not allowed)
finished. total time: 1.094s
rebooting...
finished. total time: 1.719s
Somebody has any idea about this problem?
Best Regards,
RC
May be it is a hardware problem? In this case you should try to put it into stock condition and bring it to service. I think you can do it, because you do not need the phone screen to flash RUU, change CID and S-ON it.
Hi all,
My moto g has a problem. It is stuck at the "warning bootloader unlocked screen"
I can boot into fastboot and flash stuff but when i try to boot it keeps displaying the "warning bootloader unlocked screen"
i have tryed several guides to flash orignal firmware but somehow it doesnt work.
Stange thing is is that i have CMW installed but when i flash TWRP or something it says its ok but then when i go to recovery CMW always comes back.
Had the same problem, white boot logo. Download from here http://forum.xda-developers.com/showthread.php?t=2646415 During the process it will say something about boot loader, but never mind. U should have a OTA update when it finished and will lose root, but its not a big problem
regards
bobrda said:
Had the same problem, white boot logo. Download from here http://forum.xda-developers.com/showthread.php?t=2646415 During the process it will say something about boot loader, but never mind. U should have a OTA update when it finished and will lose root, but its not a big problem
regards
Click to expand...
Click to collapse
Yeah i tryed that one but it doesnt work even the logo doesnt work.
Beukhof1 said:
Yeah i tryed that one but it doesnt work even the logo doesnt work.
Click to expand...
Click to collapse
Maybe to try this one? Its the GPE rom but it may fix the phone .. http://forum.xda-developers.com/showthread.php?t=2646404
bobrda said:
Maybe to try this one? Its the GPE rom but it may fix the phone .. http://forum.xda-developers.com/showthread.php?t=2646404
Click to expand...
Click to collapse
Same thing its says its all ok but when i boot i just keeps showing the logo.
Code:
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>SET fastboot=fastboot
.exe
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe getvar m
ax-sparse-size
max-sparse-size: 268435456
finished. total time: 0.002s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe oem fb_m
ode_set
... FAILED (remote failure)
finished. total time: 0.036s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash pa
rtition gpt.bin
sending 'partition' (32 KB)... OKAY [ 0.081s]
writing 'partition'... INFOThis may take a few seconds, if a
INFOdifferent partition table is being
INFOflashed since we need to backup
INFOand restore a few partitions
INFOFlashing primary GPT image...
INFOFlashing backup GPT image...
OKAY [ 0.469s]
finished. total time: 0.550s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash mo
toboot motoboot.img
sending 'motoboot' (1940 KB)... OKAY [ 0.205s]
writing 'motoboot'... INFOflashing tz ...
INFOflashing rpm ...
INFOflashing sdi ...
INFOflashing aboot ...
INFOflashing sbl1 ...
OKAY [ 1.380s]
finished. total time: 1.586s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash mo
dem NON-HLOS.bin
sending 'modem' (47484 KB)... OKAY [ 4.088s]
writing 'modem'... OKAY [ 0.732s]
finished. total time: 4.820s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash fs
g fsg.mbn
sending 'fsg' (719 KB)... OKAY [ 0.109s]
writing 'fsg'... OKAY [ 0.032s]
finished. total time: 0.142s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe erase mo
demst1
erasing 'modemst1'... OKAY [ 0.035s]
finished. total time: 0.035s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe erase mo
demst2
erasing 'modemst2'... OKAY [ 0.046s]
finished. total time: 0.046s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash lo
go logo.bin
sending 'logo' (2563 KB)... OKAY [ 0.271s]
writing 'logo'... OKAY [ 0.085s]
finished. total time: 0.356s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash bo
ot boot.img
sending 'boot' (10240 KB)... OKAY [ 0.896s]
writing 'boot'... OKAY [ 0.731s]
finished. total time: 1.627s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash re
covery recovery.img
sending 'recovery' (10240 KB)... OKAY [ 0.897s]
writing 'recovery'... OKAY [ 0.729s]
finished. total time: 1.626s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash sy
stem system.img_sparsechunk1
sending 'system' (248834 KB)... OKAY [ 21.396s]
writing 'system'... INFOInvalid signed image
OKAY [ 4.452s]
finished. total time: 25.848s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash sy
stem system.img_sparsechunk2
sending 'system' (253442 KB)... OKAY [ 23.077s]
writing 'system'... INFOFailed to validate sparse image
OKAY [ 4.052s]
finished. total time: 27.131s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash sy
stem system.img_sparsechunk3
sending 'system' (210534 KB)... OKAY [ 19.748s]
writing 'system'... INFOFailed to validate sparse image
OKAY [ 3.446s]
finished. total time: 23.195s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe erase ca
che
erasing 'cache'... OKAY [ 0.014s]
finished. total time: 0.015s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe erase us
erdata
erasing 'userdata'... OKAY [ 0.036s]
finished. total time: 0.037s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe oem fb_m
ode_clear
... OKAY [ 0.021s]
finished. total time: 0.022s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>pause
Press any key to continue . . .
Beukhof1 said:
Same thing its says its all ok but when i boot i just keeps showing the logo.
Code:
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>SET fastboot=fastboot
.exe
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe getvar m
ax-sparse-size
max-sparse-size: 268435456
finished. total time: 0.002s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe oem fb_m
ode_set
... FAILED (remote failure)
finished. total time: 0.036s
Sorry I cant help you than. This two rooms work on my phone.. talking about xt 1032
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash pa
rtition gpt.bin
sending 'partition' (32 KB)... OKAY [ 0.081s]
writing 'partition'... INFOThis may take a few seconds, if a
INFOdifferent partition table is being
INFOflashed since we need to backup
INFOand restore a few partitions
INFOFlashing primary GPT image...
INFOFlashing backup GPT image...
OKAY [ 0.469s]
finished. total time: 0.550s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash mo
toboot motoboot.img
sending 'motoboot' (1940 KB)... OKAY [ 0.205s]
writing 'motoboot'... INFOflashing tz ...
INFOflashing rpm ...
INFOflashing sdi ...
INFOflashing aboot ...
INFOflashing sbl1 ...
OKAY [ 1.380s]
finished. total time: 1.586s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash mo
dem NON-HLOS.bin
sending 'modem' (47484 KB)... OKAY [ 4.088s]
writing 'modem'... OKAY [ 0.732s]
finished. total time: 4.820s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash fs
g fsg.mbn
sending 'fsg' (719 KB)... OKAY [ 0.109s]
writing 'fsg'... OKAY [ 0.032s]
finished. total time: 0.142s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe erase mo
demst1
erasing 'modemst1'... OKAY [ 0.035s]
finished. total time: 0.035s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe erase mo
demst2
erasing 'modemst2'... OKAY [ 0.046s]
finished. total time: 0.046s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash lo
go logo.bin
sending 'logo' (2563 KB)... OKAY [ 0.271s]
writing 'logo'... OKAY [ 0.085s]
finished. total time: 0.356s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash bo
ot boot.img
sending 'boot' (10240 KB)... OKAY [ 0.896s]
writing 'boot'... OKAY [ 0.731s]
finished. total time: 1.627s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash re
covery recovery.img
sending 'recovery' (10240 KB)... OKAY [ 0.897s]
writing 'recovery'... OKAY [ 0.729s]
finished. total time: 1.626s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash sy
stem system.img_sparsechunk1
sending 'system' (248834 KB)... OKAY [ 21.396s]
writing 'system'... INFOInvalid signed image
OKAY [ 4.452s]
finished. total time: 25.848s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash sy
stem system.img_sparsechunk2
sending 'system' (253442 KB)... OKAY [ 23.077s]
writing 'system'... INFOFailed to validate sparse image
OKAY [ 4.052s]
finished. total time: 27.131s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe flash sy
stem system.img_sparsechunk3
sending 'system' (210534 KB)... OKAY [ 19.748s]
writing 'system'... INFOFailed to validate sparse image
OKAY [ 3.446s]
finished. total time: 23.195s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe erase ca
che
erasing 'cache'... OKAY [ 0.014s]
finished. total time: 0.015s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe erase us
erdata
erasing 'userdata'... OKAY [ 0.036s]
finished. total time: 0.037s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>fastboot.exe oem fb_m
ode_clear
... OKAY [ 0.021s]
finished. total time: 0.022s
C:\Users\beukhof1\Downloads\GPE_XT1032_KOT49H.M004_CFC.xml>pause
Press any key to continue . . .
Click to expand...
Click to collapse
Sorry I cant help you. It works on my phone. model xt 1032
bobrda said:
Sorry I cant help you. It works on my phone. model xt 1032
Click to expand...
Click to collapse
I have the same model
Beukhof1 said:
I have the same model
Click to expand...
Click to collapse
Don't know whats couching you the problem. try to push rom via adb
or maybe this one http://forum.xda-developers.com/showthread.php?t=2542219
i had no success with this rom, but...
it's beyond my knowledge
bobrda said:
Don't know whats couching you the problem. try to push rom via adb
or maybe this one http://forum.xda-developers.com/showthread.php?t=2542219
i had no success with this rom, but...
it's beyond my knowledge
Click to expand...
Click to collapse
Every thing i flash even recovery doesnt seem to stick because when i fastboot twrp i still have my cmw.
Beukhof1 said:
Every thing i flash even recovery doesnt seem to stick because when i fastboot twrp i still have my cmw.
Click to expand...
Click to collapse
Few dayes ago i download Gb 4.4.2 rom and flash it with no mistakes thru the flash! It have no errors while flashing. After that had a update to 176.44.1
So my phone is for European market and with sparsechunk.0 sparsechunk.1 sparsechunk.2 have no errors. With 1.2.and 3sparsechunk i have errors, but i can but in the rom normally...
Then i use a mototool 3 and root my phone with twrp recovery...
Beukhof1 said:
Hi all,
My moto g has a problem. It is stuck at the "warning bootloader unlocked screen"
I can boot into fastboot and flash stuff but when i try to boot it keeps displaying the "warning bootloader unlocked screen"
i have tryed several guides to flash orignal firmware but somehow it doesnt work.
Stange thing is is that i have CMW installed but when i flash TWRP or something it says its ok but then when i go to recovery CMW always comes back.
Click to expand...
Click to collapse
Did you manage to get a fix for this? I have the exact same issue, did all the steps you mentioned and have not found a fix, did you hace any luck?
Iggyavendano said:
Did you manage to get a fix for this? I have the exact same issue, did all the steps you mentioned and have not found a fix, did you hace any luck?
Click to expand...
Click to collapse
Nope sorry man. Mine is stille dead. I think the flash memory is defectieve.
Beukhof1 said:
Nope sorry man. Mine is stille dead. I think the flash memory is defectieve.
Click to expand...
Click to collapse
I went back to my carrier rom and It worked... after a few flashes on lollipop I couldn't get it to work even on stock lollipop...
hope it helps.
Try with mfastboot-v2. You can find the link with a quick search. mfastboot may help with flashing larger system images than normal fastboot. Just give it a try.
And if you are on lollipop & trying to downgrade to kitkat, skip flashing motoboot.img & gpt.bin
legolas06 said:
Try with mfastboot-v2. You can find the link with a quick search. mfastboot may help with flashing larger system images than normal fastboot. Just give it a try.
And if you are on lollipop & trying to downgrade to kitkat, skip flashing motoboot.img & gpt.bin
Click to expand...
Click to collapse
I had the same problem, and tried everithing said here, the only thing that worked, was mfastboot - v2, thank a lot for the sugestion.
Device not seen
I'm having the same problem – stuck on "Warning Booloader Unlocked" screen. Can't get to the bootloader screen. 'adb devices' and 'mfastboot devices' both show empty device lists, which means that I can't execute any adb or mfastboot commands...
Moto G XT1032 (Gen 1, 2013), attempted to install 5.1 firmware using steps at www . droidviews . com/restore-moto-g-to-stock-and-downgrade-firmware (sorry, not allowed to add live link). Bootloader unlocked, USB drivers installed, USB debugging enabled. All mfastboot steps executed without error, but I missed sparsechunk.0 – duh. Finished with a 'mfastboot reboot', and ever since, can't get past the bootloader warning, and no device seen by adb or mfastboot... Can't imagine it's a connectivity or PC driver issue, as was working fine minutes ago before the reboot.
All the solutions I've found depend on adb or mfastboot being able to see my device. Any tips to get the device seen again?
Thanks!
aussiejim said:
I'm having the same problem – stuck on "Warning Booloader Unlocked" screen. Can't get to the bootloader screen. 'adb devices' and 'mfastboot devices' both show empty device lists, which means that I can't execute any adb or mfastboot commands...
Moto G XT1032 (Gen 1, 2013), attempted to install 5.1 firmware using steps at www . droidviews . com/restore-moto-g-to-stock-and-downgrade-firmware (sorry, not allowed to add live link). Bootloader unlocked, USB drivers installed, USB debugging enabled. All mfastboot steps executed without error, but I missed sparsechunk.0 – duh. Finished with a 'mfastboot reboot', and ever since, can't get past the bootloader warning, and no device seen by adb or mfastboot... Can't imagine it's a connectivity or PC driver issue, as was working fine minutes ago before the reboot.
All the solutions I've found depend on adb or mfastboot being able to see my device. Any tips to get the device seen again?
Thanks!
Click to expand...
Click to collapse
Problem solved – eventually got into bootloader screen on phone, after at least 20 tries... If you have same problem, keep on trying.
hey guys
i have p920 with problem hang on the logo
but can not flash and error after 35 %
please help me thanks
can not go to recovery custom
phone is unlocke bootloader and write recovery philz_touch but after write can not go to recovery and still here bootloader!!!!?
C:\Documents and Settings\Administrator\Desktop\ADB & FASTBOOT>fastboot flash re
covery philz_touch_6.18.7-zaradug.img
sending 'recovery' (8056 KB)...
OKAY [ 1.750s]
writing 'recovery'...
OKAY [ 0.828s]
finished. total time: 2.578s
Hi all,
somehow my sons' D6603 messed up and didn't boot anymore. Had an old CarbonROM installed before, but that failed for no reason I can pinpoint.
OK, to recover I tried to reflash the ROM - but boot process got stuck in boot animation for hours (until battery ran out).
OK, so I fired up flashtool and tried to install an FTF - but all FTFs I tried to retrieve failed to unpack.
OK - one more try - got me a stock ROM that was supposed to be flashed through recovery.
Now I get Sony splashscreen, then display turns black and stays like that forever. Only sign of something happening is that the notification LED blinks occasionally.
I tried to enter recovery - wouldn't work at all: never saw any change in boot process.
I can put the phone into flash mode and into fastboot - so I tried to flash a new TWRP:
Code:
[email protected] ~/temp/TWRP-z3 $ fastboot flash FOTAKernel recovery.img
target didn't report max-download-size
sending 'FOTAKernel' (15904 KB)...
OKAY [ 0.502s]
writing 'FOTAKernel'...
OKAY [ 1.056s]
finished. total time: 1.558s
[email protected] ~/temp/TWRP-z3 $ fastboot flash recovery recovery.img
target didn't report max-download-size
sending 'recovery' (15904 KB)...
OKAY [ 0.501s]
writing 'recovery'...
OKAY [ 1.055s]
finished. total time: 1.556s
But still the mobile won't boot into recovery
OK, there's a different TWRP available - but I can't flash it to FOTAkernel:
Code:
[email protected] ~/Downloads $ fastboot flash FOTAkernel twrp_z3_2018-03-28.img
target didn't report max-download-size
sending 'FOTAkernel' (10808 KB)...
OKAY [ 0.342s]
writing 'FOTAkernel'...
FAILED (remote: Command not allowed)
finished. total time: 0.345s
[email protected] ~/Downloads $ fastboot flash recovery twrp_z3_2018-03-28.img
target didn't report max-download-size
sending 'recovery' (10808 KB)...
OKAY [ 0.342s]
writing 'recovery'...
OKAY [ 0.721s]
finished. total time: 1.063s
Can anyone help me to get stuff working again? I'm lost for options right now - TWRP won't come up, and I can't get an FTF via flashtool to my harddrive. Any other ways to unbrick the phone?
Got a recent LinuxMint 19.x here as my machine right now. Getting a Windows up and running would be an obstacle (although I might get a hand to one).
using cmd
when trying to unlock oem; giving:
FAILED (remote: OEM unlock is not allowed)
finished. total time: 0.011s
-----------------------------------------------------------------
when trying to flash boot or recovery; giving:
boot:
sending 'boot' (29069 KB)...
OKAY [ 0.765s]
writing 'boot'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.787s
recovery:
sending 'recovery' (42204 KB)...
OKAY [ 1.103s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 1.121s
-----------------------------------------------------------------
when trying to change the partition giving:
C:\Users\Rfastboot --set-active=b
fastboot: unknown option -- set-active=b
-----------------------------------------------------------------
please help!!!
FkReMy said:
using cmd
when trying to unlock oem; giving:
FAILED (remote: OEM unlock is not allowed)
finished. total time: 0.011s
-----------------------------------------------------------------
when trying to flash boot or recovery; giving:
boot:
sending 'boot' (29069 KB)...
OKAY [ 0.765s]
writing 'boot'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.787s
recovery:
sending 'recovery' (42204 KB)...
OKAY [ 1.103s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 1.121s
-----------------------------------------------------------------
when trying to change the partition giving:
C:\Users\Rfastboot --set-active=b
fastboot: unknown option -- set-active=b
-----------------------------------------------------------------
please help!!!
Click to expand...
Click to collapse
From what I found on the internet, I guess you didn't turn on the setting `oem allow unlock' in developer settings.
But isn't there `rescue party' (a subsystem of androids recovery which shows two options: 1) Try again 2) Factory data reset)?
If it is, just press that Try again button, wait until it boots into rescue party again and then press the Try again button again. Do that 5-7 times in a row (depending on the phone). Your phone should detect that your current slot is unbootable and should boot into the unupdated slot.
You could also try to find the stock image (or whatever image you have currently installed) and flash it within recovery (there should be a button labeled like `update...' or `sideload...' or something). That should also work.
If nothing helps, you could also factory data reset and hope that it works now...
If that also doesn't work, you could research abit about edl (emergency donwload mode) and how to use it to reflash your device.