Database Develop

Custom ROM

Hi,
i try to install Lollipop on my Z1. A Long Time ago i had cm mod installed, after that stock rom.
i use actually C6903_14.4.A.0.157_Central Europe 1. i want to install cm 12, device downgrade on .108, root and upgrade to .157. unlocking the bootloader via Fastboot and flashtool failed:
04/041/2015 18:41:52 - INFO - FAILED (remote: Command did not succeed)
04/041/2015 18:41:52 - INFO - finished. total time: 0.019s
second time:
04/041/2015 18:41:57 - INFO - FAILED (remote: Device is already rooted)
04/041/2015 18:41:57 - INFO - finished. total time: 0.004s
at servicemenu: Bootloader unlocked allowed: Yes. i think the bootloader is locked, but i can unlock. otherwise i try to install boot.img via fastboot from cm 12.
sending 'boot' (13252 KB)...
OKAY [ 0.461s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.470s
than i tried with Z1-lockeddualrecovery2.8.1 to install crdroid 5.0.2, installation from dualrecovery without problems. after flashing crdroid and direct after Z1-lockeddualrecovery2.8.1-RELEASE.flashable i had a black screen after reboot. when i press the on button there is one time vibration, than nothing. the z1 will not boot or start recovery. i installed via flashtool -> flash mode C6903_14.4.A.0.157_Central Europe 1 stock rom. someone any idea ?
thx

thc2oo2 said:
Hi,
i try to install Lollipop on my Z1. A Long Time ago i had cm mod installed, after that stock rom.
i use actually C6903_14.4.A.0.157_Central Europe 1. i want to install cm 12, device downgrade on .108, root and upgrade to .157. unlocking the bootloader via Fastboot and flashtool failed:
04/041/2015 18:41:52 - INFO - FAILED (remote: Command did not succeed)
04/041/2015 18:41:52 - INFO - finished. total time: 0.019s
second time:
04/041/2015 18:41:57 - INFO - FAILED (remote: Device is already rooted)
04/041/2015 18:41:57 - INFO - finished. total time: 0.004s
at servicemenu: Bootloader unlocked allowed: Yes. i think the bootloader is locked, but i can unlock. otherwise i try to install boot.img via fastboot from cm 12.
sending 'boot' (13252 KB)...
OKAY [ 0.461s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.470s
than i tried with Z1-lockeddualrecovery2.8.1 to install crdroid 5.0.2, installation from dualrecovery without problems. after flashing crdroid and direct after Z1-lockeddualrecovery2.8.1-RELEASE.flashable i had a black screen after reboot. when i press the on button there is one time vibration, than nothing. the z1 will not boot or start recovery. i installed via flashtool -> flash mode C6903_14.4.A.0.157_Central Europe 1 stock rom. someone any idea ?
thx
Click to expand...
Click to collapse
try to boot your device in flashmode
install stock rom

If you failed to install a custom kernel is because you did not have unlocked your bootloader. You need a unlocked bootloader to flash boot.img, otherwise it will fail.
You got a black screen because you have not followed the right steps to install the ROM, some ROM needs to wipe everything (except sdcard) to work properly.

[Q] C6903 unable to flash images using fastboot

Dear all,
I want to update my C6903 to Anndroid Lollipop by flashing AOSP images after building them by following the instructions from Sony. But when I tried to flash them, below error occurred.
----------------------------
fastboot flash boot boot.img
sending 'boot' (8866 KB)...
OKAY [ 0.482s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.485s
----------------------------
I used flashtool(0.9.18.5) and EasyRootTool(v12.3) to flash the firmware(C6903_14.4.A.0.108_HK.ftf) and root the system, and used that flashtool to relock the bootloader.
When I tried to unlock the bootloader again, below errors occurred.
------------------------------
[email protected]:/home/zhiming/Soft/PhoneBak/FlashTool# fastboot -i 0x0fce oem unlock 0xXXXXXXXXXXXXXXXX
//first time the command run
FAILED (remote: Command did not succeed)
finished. total time: 0.019s
//second time the command run
FAILED (remote: Device is already rooted)
finished. total time: 0.004s
------------------------------
The rooting status showed by "*#*#7378423#*#*" -> "Service Info" -> "Configuration" is below.
After bootloader relocked using flashtool:
-------------------
Rooting status:
Bootloader unlock allowed: Yes
-------------------
After unlocking bootloader again using flashtool:
-------------------
Rooting Status:
Unknown
-------------------
Could anybody help to resolve the problem? Thanks very much!
Thanks & Regards, Zhiming WU

Can anybody help me to solve this problem?
Thanks & Regards, Zhiming WU

ZhimingWU said:
Can anybody help me to solve this problem?
Thanks & Regards, Zhiming WU
Click to expand...
Click to collapse
Check drivers then flash stock firmware again then check your bootloader status in service menu if unlocking is allowed use fastboot commands...
Follow this site
http://forum.xda-developers.com/showthread.php?t=2440597
Then go to [ how to unlock ]*(official way) in first page follow each step carefully remember Read twice, Do once.

Moto G 3rd Gen (XT1541) Bootloader with Tesla Android ROM 6.0.

Hi everyone
Yesterday I've installed Android 6.0. Tesla ROM after downgrading to Stock Android 5.1. (Stock 6.0. was slow as hell)
When I was beginning to install Android 5.1. stock fastboot had said that it cant install gpt.bin file. I've read that it's possible to do the install without it. Restarting or turning on after completely successful install it shows every time the bootloader and I always have to press START. I've decided to install Tesla ROM thinking it will fix that. But the problem remains still. I've tried to re-lock my bootloader but it says Please fully flash the signed build before locking phone. What do I have to do now to fix it? Thanks in advance

Check your phone box, there is a sticker that should say "XT 1541 retXX" so you know wich region is right for your phone, then download the fw from the filefacory repo http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=50 and flash it whit mfastbootV2
PS
Your phone have a dedicated section --> http://forum.xda-developers.com/2015-moto-g

edrpomidor said:
Hi everyone
Yesterday I've installed Android 6.0. Tesla ROM after downgrading to Stock Android 5.1. (Stock 6.0. was slow as hell)
When I was beginning to install Android 5.1. stock fastboot had said that it cant install gpt.bin file. I've read that it's possible to do the install without it. Restarting or turning on after completely successful install it shows every time the bootloader and I always have to press START. I've decided to install Tesla ROM thinking it will fix that. But the problem remains still. I've tried to re-lock my bootloader but it says Please fully flash the signed build before locking phone. What do I have to do now to fix it? Thanks in advance
Click to expand...
Click to collapse
Use mfastboot v2, and try to flash a 5.1 firmware from the same region (if your phone was from Latin America use retLA, if it's from asia use retasia, for the US use retUS, etc.)

benjausen said:
Use mfastboot v2, and try to flash a firmware FROM THE SAME REGION. Did you change motoboot.img? If so then skip 5.X gpt.bin and motoboot.img flashing.
Click to expand...
Click to collapse
No I didn't

deleted

benjausen said:
Use mfastboot v2, and try to flash a 5.1 firmware from the same region (if your phone was from Latin America use retLA, if it's from asia use retasia, for the US use retUS, etc.)
Click to expand...
Click to collapse
I've done everything you said (gpt.bin has been installed!), showing of bootloader is gone.
But the problem with blocking of bootloader exist yet... However, thanks
C:\Users\\Desktop\ADB and Fastboot>fastboot oem lock
...
(bootloader) Please run fastboot oem lock begin first!
OKAY [ 0.047s]
finished. total time: 0.052s
C:\Users\\Desktop\ADB and Fastboot>fastboot oem lock begin
...
(bootloader) Please fully flash the signed build before locking phone!
OKAY [ 0.015s]
finished. total time: 0.017s
or in mfastboot-v2
C:\Users\\Desktop\Новая папка>mfastboot oem lock begin
...
(bootloader) Not supported command in current status!
FAILED (remote failure)
finished. total time: 0.020s
C:\Users\\Desktop\Новая папка>mfastboot oem lock
...
(bootloader) Please flash valid signed images just after lock begin
(bootloader) command!
OKAY [ 0.032s]
finished. total time: 0.035s

edrpomidor said:
I've done everything you said (gpt.bin has been installed!), showing of bootloader is gone.
But the problem with blocking of bootloader exist yet... However, thanks
C:\Users\\Desktop\ADB and Fastboot>fastboot oem lock
...
(bootloader) Please run fastboot oem lock begin first!
OKAY [ 0.047s]
finished. total time: 0.052s
C:\Users\\Desktop\ADB and Fastboot>fastboot oem lock begin
...
(bootloader) Please fully flash the signed build before locking phone!
OKAY [ 0.015s]
finished. total time: 0.017s
or in mfastboot-v2
C:\Users\\Desktop\Новая папка>mfastboot oem lock begin
...
(bootloader) Not supported command in current status!
FAILED (remote failure)
finished. total time: 0.020s
C:\Users\\Desktop\Новая папка>mfastboot oem lock
...
(bootloader) Please flash valid signed images just after lock begin
(bootloader) command!
OKAY [ 0.032s]
finished. total time: 0.035s
Click to expand...
Click to collapse
Try to flash a 6.0 firmware for your region after the lock. Might not be the best, but at least you will have a working phone. It seems you relocked it, so you won't be able to use other images or to root and install custom ROMS. My XT1072 runs 6.0.1 CM13 and the touchscreen is lagged plus a reduced gaming perfomance, but the phone works.

benjausen said:
Try to flash a 6.0 firmware for your region after the lock. Might not be the best, but at least you will have a working phone. It seems you relocked it, so you won't be able to use other images or to root and install custom ROMS. My XT1072 runs 6.0.1 CM13 and the touchscreen is lagged plus a reduced gaming perfomance, but the phone works.
Click to expand...
Click to collapse
Now I have stock Android 6.0.1 RETEU XT1541, working phone with unlocked bootloader, so if I want, I can flash other ROMs.

edrpomidor said:
Now I have stock Android 6.0.1 RETEU XT1541, working phone with unlocked bootloader, so if I want, I can flash other ROMs.
Click to expand...
Click to collapse
Try flashing CM12.1 then.

P9 (EVA-L09) Locking Bootloader failure

Hi all,
I have debranded my EVA-L09 from Three UK, so that I can get faster OTA updates (and also to try to participate in future betas) - I'm now successfully on C432B166
However, I'd like to now re-lock my bootloader, but am struggling.
Whenever I boot to fastboot and run "fastboot oem relock ****************", I get the following response:
Code:
...
FAILED (remote: root type is risk)
finished. total time: 0.006s
If I try "fastboot oem lock ****************", I get the following:
Code:
...
FAILED (remote: Command not allowed)
finished. total time: 0.009s
I have tried with "Enable OEM unlock" both enabled and disabled in Developer Options.
Can anyone give me any pointers on how to re-lock the bootloader?
Many thanks!

Sorry to bump an old thread. I'm currently having the same problems @ConfusedTA . Unfortunately I think it's difficult to re-lock bootloader without being on the same firmware that you were on when you unlocked it.
If anybody knows a way of forcing the bootloader to lock it'd be much appreciated!

Unbrick

Hi everyone,
i've the phone can only go into eRecovey and fastboot. I think that the corrupted file is oeminfo.bin, bacause i was replaced with file explorer to have the exact version of the firmware.
Recovery i've tried to download by wifi the firmware, but when install return with authentication info failed error red exclamation dot. I've tried with full wipe but after reboot it return into eRecovery.
Into fastboot return with FAILED (remote: Command not allowed).
Bootloader after update was began locked and i cannot unlock, so TWRP is cutted out.
There's some method to flash the .img system etc like odin for samsung?
i've also the old version of oeminfo.bin on my PC, if i have a method to flash it trough ADB, but i don't know how to unbrick.
Thanks

frencisis said:
Hi everyone,
i've the phone can only go into eRecovey and fastboot. I think that the corrupted file is oeminfo.bin, bacause i was replaced with file explorer to have the exact version of the firmware.
Recovery i've tried to download by wifi the firmware, but when install return with authentication info failed error red exclamation dot. I've tried with full wipe but after reboot it return into eRecovery.
Into fastboot return with FAILED (remote: Command not allowed).
Bootloader after update was began locked and i cannot unlock, so TWRP is cutted out.
There's some method to flash the .img system etc like odin for samsung?
i've also the old version of oeminfo.bin on my PC, if i have a method to flash it trough ADB, but i don't know how to unbrick.
Thanks
Click to expand...
Click to collapse
Run these commands in fastboot and report back
fastboot oem get-product-model
fastboot getvar vendorcountry

danifilth4king said:
Run these commands in fastboot and report back
fastboot oem get-product-model
fastboot getvar vendorcountry
Click to expand...
Click to collapse
Thanks, the resuls are:
C:\adb>fastboot devices
LCL0218428003429 fastboot
C:\adb>fastboot oem get-product-model
...
FAILED (remote: FAIL)
finished. total time: 0.006s
C:\adb>fastboot getvar vendorcountry
getvar:vendorcountry FAILED (remote: cannot get vendorcountry in oeminfo)
finished. total time: 0.011s
C:\adb>

frencisis said:
Thanks, the resuls are:
C:\adb>fastboot devices
LCL0218428003429 fastboot
C:\adb>fastboot oem get-product-model
...
FAILED (remote: FAIL)
finished. total time: 0.006s
C:\adb>fastboot getvar vendorcountry
getvar:vendorcountry FAILED (remote: cannot get vendorcountry in oeminfo)
finished. total time: 0.011s
C:\adb>
Click to expand...
Click to collapse
As your normal eRecovery method isn't working you could try using the FunkyHuawei eRecovery method to flash firmware but you'd have to pay for credits and there's no guarantee it would work. Problem is knowing which firmware to choose as we don't know if your rebrand was successful.
You could try a firmware that matches what your model and region of your phone was originally and if that doesn't work try the firmware meant for the model/region you were trying to rebrand to?
Other than that I'm out of ideas if you can't unlock your bootloader :/

danifilth4king said:
As your normal eRecovery method isn't working you could try using the FunkyHuawei eRecovery method to flash firmware but you'd have to pay for credits and there's no guarantee it would work. Problem is knowing which firmware to choose as we don't know if your rebrand was successful.
You could try a firmware that matches what your model and region of your phone was originally and if that doesn't work try the firmware meant for the model/region you were trying to rebrand to?
Other than that I'm out of ideas if you can't unlock your bootloader :/
Click to expand...
Click to collapse
I've tried to contact Funky Huawei, but they answered to me that: "Unfortunately in your situation recovery might not be possible".
So the last one is to try with warranty into Huawei service.
I hope they could repair it with less money as possible. Maybe they will replace the main board or just re flash he firmware with special method?:crying:

not possible to flash firmware in downloade mode?

mrt box

elvis87 said:
mrt box
Click to expand...
Click to collapse
Have you seriously just answered a 2 years old thread?..

Dude, I have the same problem with a P20 Pro since january!

Usb-c pendrive with proper firmware did the trick for me last time. Nothing else worked. Erecovery is useless crap.

deucecorp said:
Usb-c pendrive with proper firmware did the trick for me last time. Nothing else worked. Erecovery is useless crap.
Click to expand...
Click to collapse
Can I pm you for details?