Today my cell phone got stuck on the android one logo.
I was using the cell phone when it suddenly fired, so I forced a restart with the power button and from that moment on it never turned on again.
I have the bootloader unlocked and I was running the Paranoid Quartz 4 rom about 3 months ago without any problem.
The first thing I did was try to enter recovery mode (twrp) and it was not possible. The only thing I can do with the cell phone is enter fastboot mode. So I decided to flash the stock rom using MiFlash (I tried with android 9 and android 10), but the error is always the same: "remote: Error flashing partition: Write Protected".
I have been trying to find a solution for several hours, I watched a lot of videos, I read a lot of threads, but there is no case: no solution has worked so far.
In the MiA2 forums the only thread I found is the following:
https://forum.xda-developers.com/mi-a2/help/help-xiaomi-mi-a2-write-protected-t4153629
I followed all the steps you left in the comments but nothing worked.
I wanted to know if this is happening to anyone else, and if anyone can try to help me fix it.
Thank you very much, I appreciate any kind of help.
try running :
fastboot flashing unlock_critical
*if that doesn't work then try to run
fastboot getvar all
***post the output here so we can see what's going on
have you checked the basics ? are you CERTAIN you didn't lock bootloader ..
when you went back to stock from the custom rom did you remember to go into dev settings afterwards & to check that oem unlock and adb debug were toggled to on position
lastly if trying to restore stock using miflash try it in edl mode :
fastboot oem edl
then flash latest stock in miflash
the write protect error sounds strange to me .. what happens while trying to enter twrp ? what error do you get ? did you hold power and volume up until entering recovery ..are you sure you don't have ARB triggered ?
KevMetal said:
try running :
fastboot flashing unlock_critical
*if that doesn't work then try to run
fastboot getvar all
***post the output here so we can see what's going on
have you checked the basics ? are you CERTAIN you didn't lock bootloader ..
when you went back to stock from the custom rom did you remember to go into dev settings afterwards & to check that oem unlock and adb debug were toggled to on position
lastly if trying to restore stock using miflash try it in edl mode :
fastboot oem edl
then flash latest stock in miflash
the write protect error sounds strange to me .. what happens while trying to enter twrp ? what error do you get ? did you hold power and volume up until entering recovery ..are you sure you don't have ARB triggered ?
Click to expand...
Click to collapse
Thanks for the reply.
This is the output when i put "fastboot getvar all"
(bootloader) crc:1
(bootloader) anti:1
(bootloader) token:/+VhxhMzqIjkRrCKNtCRXkCZccE=
(bootloader) parallel-download-flash:yes
(bootloader) hw-revision:10000
(bootloader) unlocked:yes
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4346
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) erase-block-size: 0x200
(bootloader) logical-block-size: 0x200
(bootloader) variant:SDM EMMC
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xBB77F7E00
(bootloader) partition-type:vendor_b:raw
(bootloader) partition-size:vendor_b: 0x80000000
(bootloader) partition-type:vendor_a:raw
(bootloader) partition-size:vendor_a: 0x80000000
(bootloader) partition-type:system_b:ext4
(bootloader) partition-size:system_b: 0xC0000000
(bootloader) partition-type:system_a:ext4
(bootloader) partition-size:system_a: 0xC0000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x10000000
(bootloader) partition-type:boot_b:raw
(bootloader) partition-size:boot_b: 0x4000000
(bootloader) partition-type:boot_a:raw
(bootloader) partition-size:boot_a: 0x4000000
(bootloader) partition-type:minidump:raw
(bootloader) partition-size:minidump: 0x8000000
(bootloader) partition-type:rawdump:raw
(bootloader) partition-size:rawdump: 0x8000000
(bootloader) partition-type:modem_b:raw
(bootloader) partition-size:modem_b: 0xC000000
(bootloader) partition-type:modem_a:raw
(bootloader) partition-size:modem_a: 0xC000000
(bootloader) partition-type:logdump:raw
(bootloader) partition-size:logdump: 0x4000000
(bootloader) partition-typeersistbak:raw
(bootloader) partition-sizeersistbak: 0x2000000
(bootloader) partition-typeersist:raw
(bootloader) partition-sizeersist: 0x2000000
(bootloader) partition-type:splash:raw
(bootloader) partition-size:splash: 0x4000000
(bootloader) partition-type:mdtp_b:raw
(bootloader) partition-size:mdtp_b: 0x2000000
(bootloader) partition-type:mdtp_a:raw
(bootloader) partition-size:mdtp_a: 0x2000000
(bootloader) partition-type:bk1:raw
(bootloader) partition-size:bk1: 0x700000
(bootloader) partition-type:bluetooth_b:raw
(bootloader) partition-size:bluetooth_b: 0x100000
(bootloader) partition-type:dsp_b:raw
(bootloader) partition-size:dsp_b: 0x1000000
(bootloader) partition-type:dsp_a:raw
(bootloader) partition-size:dsp_a: 0x1000000
(bootloader) partition-type:modemst2:raw
(bootloader) partition-size:modemst2: 0x800000
(bootloader) partition-type:modemst1:raw
(bootloader) partition-size:modemst1: 0x800000
(bootloader) partition-type:fsg:raw
(bootloader) partition-size:fsg: 0x800000
(bootloader) partition-type:logfs:raw
(bootloader) partition-size:logfs: 0x800000
(bootloader) partition-type:devinfo:raw
(bootloader) partition-size:devinfo: 0x800000
(bootloader) partition-type:misc:raw
(bootloader) partition-size:misc: 0x400000
(bootloader) partition-type:xbl_b:raw
(bootloader) partition-size:xbl_b: 0x380000
(bootloader) partition-type:xbl_a:raw
(bootloader) partition-size:xbl_a: 0x380000
(bootloader) partition-type:sti:raw
(bootloader) partition-size:sti: 0x200000
(bootloader) partition-type:bluetooth_a:raw
(bootloader) partition-size:bluetooth_a: 0x100000
(bootloader) partition-type:keymaster_b:raw
(bootloader) partition-size:keymaster_b: 0x100000
(bootloader) partition-type:keymaster_a:raw
(bootloader) partition-size:keymaster_a: 0x100000
(bootloader) partition-type:mdtpsecapp_b:raw
(bootloader) partition-size:mdtpsecapp_b: 0x400000
(bootloader) partition-type:mdtpsecapp_a:raw
(bootloader) partition-size:mdtpsecapp_a: 0x400000
(bootloader) partition-type:tz_b:raw
(bootloader) partition-size:tz_b: 0x400000
(bootloader) partition-type:tz_a:raw
(bootloader) partition-size:tz_a: 0x400000
(bootloader) partition-type:devcfg_b:raw
(bootloader) partition-size:devcfg_b: 0x100000
(bootloader) partition-type:devcfg_a:raw
(bootloader) partition-size:devcfg_a: 0x100000
(bootloader) partition-type:toolsfv:raw
(bootloader) partition-size:toolsfv: 0x100000
(bootloader) partition-type:ddr:raw
(bootloader) partition-size:ddr: 0x100000
(bootloader) partition-type:dip:raw
(bootloader) partition-size:dip: 0x100000
(bootloader) partition-type:abl_b:raw
(bootloader) partition-size:abl_b: 0x100000
(bootloader) partition-type:abl_a:raw
(bootloader) partition-size:abl_a: 0x100000
(bootloader) partition-type:cmnlib64_b:raw
(bootloader) partition-size:cmnlib64_b: 0x100000
(bootloader) partition-type:cmnlib_b:raw
(bootloader) partition-size:cmnlib_b: 0x100000
(bootloader) partition-type:cmnlib64_a:raw
(bootloader) partition-size:cmnlib64_a: 0x100000
(bootloader) partition-type:cmnlib_a:raw
(bootloader) partition-size:cmnlib_a: 0x100000
(bootloader) partition-typemic_b:raw
(bootloader) partition-sizemic_b: 0x80000
(bootloader) partition-typemic_a:raw
(bootloader) partition-sizemic_a: 0x80000
(bootloader) partition-type:hyp_b:raw
(bootloader) partition-size:hyp_b: 0x80000
(bootloader) partition-type:hyp_a:raw
(bootloader) partition-size:hyp_a: 0x80000
(bootloader) partition-type:rpm_b:raw
(bootloader) partition-size:rpm_b: 0x80000
(bootloader) partition-type:rpm_a:raw
(bootloader) partition-size:rpm_a: 0x80000
(bootloader) partition-type:frp:raw
(bootloader) partition-size:frp: 0x80000
(bootloader) partition-type:keystore:raw
(bootloader) partition-size:keystore: 0x80000
(bootloader) partition-type:msadp:raw
(bootloader) partition-size:msadp: 0x40000
(bootloader) partition-type:apdp:raw
(bootloader) partition-size:apdp: 0x40000
(bootloader) partition-typeraw
(bootloader) partition-size 0x20000
(bootloader) partition-type:storsec:raw
(bootloader) partition-size:storsec: 0x20000
(bootloader) partition-type:vbmeta_b:raw
(bootloader) partition-size:vbmeta_b: 0x10000
(bootloader) partition-type:vbmeta_a:raw
(bootloader) partition-size:vbmeta_a: 0x10000
(bootloader) partition-type:sec:raw
(bootloader) partition-size:sec: 0x5000
(bootloader) partition-type:ssd:raw
(bootloader) partition-size:ssd: 0x8000
(bootloader) partition-type:limits:raw
(bootloader) partition-size:limits: 0x8000
(bootloader) partition-type:fsc:raw
(bootloader) partition-size:fsc: 0x2000
(bootloader) partition-type:dpo:raw
(bootloader) partition-size:dpo: 0x2000
(bootloader) partition-type:switch:raw
(bootloader) partition-size:switch: 0x2000
(bootloader) has-slot:modem:yes
(bootloader) has-slot:system:yes
(bootloader) current-slot:b
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:6
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:yes
(bootloader) slot-retry-count:a:7
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:no
(bootloader) slot-count:2
(bootloader) secure:yes
(bootloader) serialno:ca5094d9
(bootloader) product:jasmine
(bootloader) max-download-size:805306368
(bootloader) kernel:uefi
all:
finished. total time: 0.570s
Click to expand...
Click to collapse
And when I put fastboot flashing unlock_critical
FAILED (remote: Device already : unlocked!)
finished. total time: 0.004s
The problem is that I never thought to go back to the stock rom, I am trying to do it because my cell is dead. But the usb debugging was activated (I remember, whenever I connected the cell phone to the car, the notification would appear).
I already tried flashing the stock rom in EDL. I tried different versions but they all end in the same error. At this moment I am again downloading the last stable that they uploaded (V11.0.14.0.QDIMIXM) to try, but without hope hahaha
Finally, it doesn't let me enter TWRP, the only way is with a boot from fastboot (because flashing does not allow me, just like the roms). When I boot the twrp it starts up but gets stuck at the boot logo, it never enters recovery. And I don't know what you mean by "ARB triggered"
This MiA2 literally looks like a stone, I don't know what else to do. In a forum they told me that I have to have an "authorized EDL account" or contact one in order to unbrick the terminal.
Thanks again for the reply, I appreciate it.
ivan.lxc.10 said:
Thanks for the reply.
This is the output when i put "fastboot getvar all"
And when I put fastboot flashing unlock_critical
FAILED (remote: Device already : unlocked!)
finished. total time: 0.004s
The problem is that I never thought to go back to the stock rom, I am trying to do it because my cell is dead. But the usb debugging was activated (I remember, whenever I connected the cell phone to the car, the notification would appear).
I already tried flashing the stock rom in EDL. I tried different versions but they all end in the same error. At this moment I am again downloading the last stable that they uploaded (V11.0.14.0.QDIMIXM) to try, but without hope hahaha
Finally, it doesn't let me enter TWRP, the only way is with a boot from fastboot (because flashing does not allow me, just like the roms). When I boot the twrp it starts up but gets stuck at the boot logo, it never enters recovery. And I don't know what you mean by "ARB triggered"
This MiA2 literally looks like a stone, I don't know what else to do. In a forum they told me that I have to have an "authorized EDL account" or contact one in order to unbrick the terminal.
Thanks again for the reply, I appreciate it.
Click to expand...
Click to collapse
it will work by flashing the stock rom in edl
1. install Qualcomm 9008 drivers
2. run : fastboot oem edl
3.open miflash and refresh and flash rom
make sure you are using THE LATEST miflash ( use it to install drivers)
you can also try just changing to your other slot ...stock android 1 might still be there :
fastboot set_active b
or if you are b just put :
fastboot set_active a
KevMetal said:
it will work by flashing the stock rom in edl
1. install Qualcomm 9008 drivers
2. run : fastboot oem edl
3.open miflash and refresh and flash rom
make sure you are using THE LATEST miflash ( use it to install drivers)
you can also try just changing to your other slot ...stock android 1 might still be there :
fastboot set_active b
or if you are b just put :
fastboot set_active a
Click to expand...
Click to collapse
it didn't work. I'll leave you the log so you can see if you see something that I don't
"ACK count don't match!"
http://www.mediafire.com/file/z746700jxil5d6e/COM8%4020201019114123.txt/file (1st)
http://www.mediafire.com/file/5ba9u2yb0rnzqg9/COM8%402020101911540.txt/file (2nd)
ivan.lxc.10 said:
it didn't work. I'll leave you the log so you can see if you see something that I don't
"ACK count don't match!"
http://www.mediafire.com/file/z746700jxil5d6e/COM8%4020201019114123.txt/file (1st)
http://www.mediafire.com/file/5ba9u2yb0rnzqg9/COM8%402020101911540.txt/file (2nd)
Click to expand...
Click to collapse
I will take a look when i can
were you able to enter EDL correctly ?
did you try changing slots using the commands specified ?
KevMetal said:
I will take a look when i can
were you able to enter EDL correctly ?
did you try changing slots using the commands specified ?
Click to expand...
Click to collapse
Yes, every time I try to flash (so far without success) I try in fastboot mode and in EDL mode. Each mode has a different error: in fastboot mode the error is "remote: Error flashing partition: Write Protected". In EDL mode the error is: "ACK count don't match!".
ivan.lxc.10 said:
Yes, every time I try to flash (so far without success) I try in fastboot mode and in EDL mode. Each mode has a different error: in fastboot mode the error is "remote: Error flashing partition: Write Protected". In EDL mode the error is: "ACK count don't match!".
Click to expand...
Click to collapse
ACK count doesn't match error is because you didn't listen to me ..USE THE LATEST BETA MI FLASH ... uninstall old ones first ... send a photo to show you are using latest
---------- Post added at 11:47 PM ---------- Previous post was at 11:33 PM ----------
I looked at the logs.. you also seem to be using patched programmer files ..STOP ..use only the stock rom ..without copying or replacing files ...
send me a summary of exactly which version of miflash you are using ..which stock rom and explain what you are trying to do correctly
KevMetal said:
ACK count doesn't match error is because you didn't listen to me ..USE THE LATEST BETA MI FLASH ... uninstall old ones first ... send a photo to show you are using latest
---------- Post added at 11:47 PM ---------- Previous post was at 11:33 PM ----------
I looked at the logs.. you also seem to be using patched programmer files ..STOP ..use only the stock rom ..without copying or replacing files ...
send me a summary of exactly which version of miflash you are using ..which stock rom and explain what you are trying to do correctly
Click to expand...
Click to collapse
Sorry but you said to use the latest version of my flash .. not the BETA of my flash.
Anyway I just downloaded the beta version of miflash and it didn't work either, I'm starting to go crazy lol
What do you mean by "patched programmer files"? I am using the latest fastboot rom from 09/28/2020, I did not touch or replace anything (neither now nor in the previous times I tried to flash)
Now the step by step is as follows:
I am using the beta version of my flash that I downloaded from here https://drive.google.com/file/d/12Gy2RP1eWBBKS6R2S2G9qzt-UQRIxpAM/view
and the fastboot rom I downloaded it from here https://xiaomifirmwareupdater.com/archive/miui/jasmine/
(from the xiaomi page the links for the roms do not work)
So what I do is:
- Open cmd and MiFlash
- I put in MiFlash the option "clean all"
- I select the path where the rom is located (I have it in c: \ rom)
- fastboot oem edl
- refresh and flash in MiFlash
ivan.lxc.10 said:
Sorry but you said to use the latest version of my flash .. not the BETA of my flash.
Anyway I just downloaded the beta version of miflash and it didn't work either, I'm starting to go crazy lol
What do you mean by "patched programmer files"? I am using the latest fastboot rom from 09/28/2020, I did not touch or replace anything (neither now nor in the previous times I tried to flash)
Now the step by step is as follows:
I am using the beta version of my flash that I downloaded from here https://drive.google.com/file/d/12Gy2RP1eWBBKS6R2S2G9qzt-UQRIxpAM/view
and the fastboot rom I downloaded it from here https://xiaomifirmwareupdater.com/archive/miui/jasmine/
(from the xiaomi page the links for the roms do not work)
So what I do is:
- Open cmd and MiFlash
- I put in MiFlash the option "clean all"
- I select the path where the rom is located (I have it in c: \ rom)
- fastboot oem edl
- refresh and flash in MiFlash
Click to expand...
Click to collapse
well if that the case you need to consider a hardware failure...
please try the command to change slots and send me a photo of what is says in fastboot
also when you try to edl flash did you check that your phone appears as qualcomm 9008 device in device manager * just to make sure your 9008 drivers were installed correctly.
anyway try another thing .... download the fastboot version aosip-derp from their official page ...then flash all the image files one by one from fastboot ..but before starting first do :
fastboot -w
send me photo of what happens
KevMetal said:
well if that the case you need to consider a hardware failure...
please try the command to change slots and send me a photo of what is says in fastboot
also when you try to edl flash did you check that your phone appears as qualcomm 9008 device in device manager * just to make sure your 9008 drivers were installed correctly.
anyway try another thing .... download the fastboot version aosip-derp from their official page ...then flash all the image files one by one from fastboot ..but before starting first do :
fastboot -w
send me photo of what happens
Click to expand...
Click to collapse
I spoke with a person from the xiaomi forum and checking the log he told me that apparently the device has memory damaged, so it could not be solved with the firmware flashing. After that, he consulted another person and gave him the same diagnosis: the memory is damaged so it does not allow me to write in various sectors. So effectively, my problem is hardware.
I will send it to the technical service and then I will make an update on this thread to tell my experience.
Thank you very much for the answer, I appreciate it.
ivan.lxc.10 said:
I spoke with a person from the xiaomi forum and checking the log he told me that apparently the device has memory damaged, so it could not be solved with the firmware flashing. After that, he consulted another person and gave him the same diagnosis: the memory is damaged so it does not allow me to write in various sectors. So effectively, my problem is hardware.
I will send it to the technical service and then I will make an update on this thread to tell my experience.
Thank you very much for the answer, I appreciate it.
Click to expand...
Click to collapse
yeah hardware failure makes sense
KevMetal said:
yeah hardware failure makes sense
Click to expand...
Click to collapse
Hi there
having a similar issue with regards to flashing a rom over to an Asus Zenfone 5 ZC600KL X017DA has a Qualcomm Chipset 630
the issue i have is the phone is stuck on Asus logo and all i can get from the device using the power and volume Keys is CSC fastboot mode no recovery or anything
downloaded a couple firmwares details are
Asus_Zenfone_5_Lite_ZC600KL_630_14.0400_1808.057_20180903_CMD
And
[firmware27]CSC__ZC600KL(630)_14.0400.1801.006_20191023_Phone_PtoN
both firmwares in fastboot mode will fail and one thing to note is write protected keeps appearing and the interesting thing is the first firmware i listed seems to not do very much it will show several lines and then fail but the second firmware had more activity it seemed to be pushing something but then several points it kept saying write protected
i am to assume the device bootloader is locked
i keep seeing everywhere to try unlock bootloader i need to be able to disable the OEM within the phone settings ( obviously i cannot due to it not booting ) as well as debugging mode being enabled again i cant enable
i have a third firmware that is meant to be used with QPTS / Qfil and that throws up a couple of errors also
really could use some help with this it would be super appreciated and would owe an virtual beer haha
any solutions
nighthawk658 said:
Hi there
having a similar issue with regards to flashing a rom over to an Asus Zenfone 5 ZC600KL X017DA has a Qualcomm Chipset 630
the issue i have is the phone is stuck on Asus logo and all i can get from the device using the power and volume Keys is CSC fastboot mode no recovery or anything
downloaded a couple firmwares details are
Asus_Zenfone_5_Lite_ZC600KL_630_14.0400_1808.057_20180903_CMD
And
[firmware27]CSC__ZC600KL(630)_14.0400.1801.006_20191023_Phone_PtoN
both firmwares in fastboot mode will fail and one thing to note is write protected keeps appearing and the interesting thing is the first firmware i listed seems to not do very much it will show several lines and then fail but the second firmware had more activity it seemed to be pushing something but then several points it kept saying write protected
i am to assume the device bootloader is locked
i keep seeing everywhere to try unlock bootloader i need to be able to disable the OEM within the phone settings ( obviously i cannot due to it not booting ) as well as debugging mode being enabled again i cant enable
i have a third firmware that is meant to be used with QPTS / Qfil and that throws up a couple of errors also
really could use some help with this it would be super appreciated and would owe an virtual beer haha
any solutions
Click to expand...
Click to collapse
Good day, I would like to ask did you resolve the problem we have exactly same problem.
KevMetal said:
try running :
fastboot flashing unlock_critical
*if that doesn't work then try to run
fastboot getvar all
***post the output here so we can see what's going on
have you checked the basics ? are you CERTAIN you didn't lock bootloader ..
when you went back to stock from the custom rom did you remember to go into dev settings afterwards & to check that oem unlock and adb debug were toggled to on position
lastly if trying to restore stock using miflash try it in edl mode :
fastboot oem edl
then flash latest stock in miflash
the write protect error sounds strange to me .. what happens while trying to enter twrp ? what error do you get ? did you hold power and volume up until entering recovery ..are you sure you don't have ARB triggered ?
Click to expand...
Click to collapse
Bro i have the same problem with my redmi note 5 pro .one day it running smoothly but suddenly it stuck.when i restarted the device it stuck on logo. Recovery also got stucked.fastboot logo not showing only black screen but computer detected fastboot.i tried many things .but it says that the device is write protected
Related
Hey I was hoping that someone here would be able to help.
Ive been trying for get s-off on my device, I have tried everything but it dosent wnat to work. I am probably missing something basic.
I have a GPE HTC one that I until recently used with RevolutionHD 30 (Sense version).
Now that 4.4 is out I want to flash that, but every rom seems to require s-off.
Being that my Hboot version is 1.54, i understand that my only option to s-off is using rumrunner.
I have tried to rumrunner a number of times:
Using a windows machine
Using a Linux machine
I have tried both wirh the following roms: CM 10.2, CM 11, ADR 30
But I cant seem to have any luck. On both machines I alwasy get stuck at the same place:
HTML:
Please wait....
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
Test 2: Booting device
Waiting for ADB (17/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[************************************************************]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
FATAL: Download updated package at www.rumrunner.us
I dont know if it helps but "fastboot getvar mainver" alwasy rettuns blank.
I tried to log onto the rumrunner irc, but it looks to be empty.
Is their anything that I can do?
Please tell me your cid and your model id and I 'll guide you
Sent from my HTC One using Tapatalk
Thanks,
Cid num: GOOGL001
Model id: PN0712000
Just in case fastboot getvar all output:
HTML:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT36JW913072
(bootloader) imei: *******************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4313mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-94cf81a8fd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.048s
AmirH said:
Hey I was hoping that someone here would be able to help.
Ive been trying for get s-off on my device, I have tried everything but it dosent wnat to work. I am probably missing something basic.
I have a GPE HTC one that I until recently used with RevolutionHD 30 (Sense version).
Now that 4.4 is out I want to flash that, but every rom seems to require s-off.
Being that my Hboot version is 1.54, i understand that my only option to s-off is using rumrunner.
I have tried to rumrunner a number of times:
Using a windows machine
Using a Linux machine
I have tried both wirh the following roms: CM 10.2, CM 11, ADR 30
But I cant seem to have any luck. On both machines I alwasy get stuck at the same place:
HTML:
Please wait....
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
Test 2: Booting device
Waiting for ADB (17/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[************************************************************]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
FATAL: Download updated package at www.rumrunner.us
I dont know if it helps but "fastboot getvar mainver" alwasy rettuns blank.
I tried to log onto the rumrunner irc, but it looks to be empty.
Is their anything that I can do?
Click to expand...
Click to collapse
Since your hboot is 1.54 use Guru Reset: 2.24.xxx.x, such as: http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-1-zip/ (if this doesnt work try a different 2.24 version)
in installer, select ROOT, and unselect "stock recovery", then give rumrunner a chance
nkk71 said:
Since your hboot is 1.54 use Guru Reset: 2.24.xxx.x, such as: http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-1-zip/ (if this doesnt work try a different 2.24 version)
in installer, select ROOT, and unselect "stock recovery", then give rumrunner a chance
Click to expand...
Click to collapse
Although not mentiond I also tried with "Guru Reset M7 3.63.707.4" maybe the version number that I tried wasnt good.
The download is on the way and I will try it then.
This wont cause any problems with the touch issues correct? I dont not have a OTG cable.
Or follow this guide http://forum.xda-developers.com/showthread.php?t=2358781 to flash the 4.4 Google edition RUU and be completely stock. Then your main version won't be blank, and can try to get s-off
Sent from my HTC One using Tapatalk
Ivanovic said:
Or follow this guide http://forum.xda-developers.com/showthread.php?t=2358781 to flash the 4.4 Google edition RUU and be completely stock. Then your main version won't be blank, and can try to get s-off
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
That was one of the posts that I was looking at but then i saw this
HTML:
Prerequisites
S-Off,
ADB knowledge
Fastboot knowledge
Should I not be worried about that?
I thought about that but you already have the correct CID and MID. I believe it will flash just fine
Sent from my HTC One using Tapatalk
Sounds reasonable ... I will update once finished.
AmirH said:
Sounds reasonable ... I will update once finished.
Click to expand...
Click to collapse
why not try s-off with 2.24 rom, and if that doesnt work you can always try the second method. once you upgrade you can no longer downgrade with S-On.
nkk71 said:
why not try s-off with 2.24 rom, and if that doesnt work you can always try the second method. once you upgrade you can no longer downgrade with S-On.
Click to expand...
Click to collapse
Thats what I plan to do.. Im downloading both roms at the same time.
Once they are finished and I have gotten a chance to play around with them, I will update.
I do hope that one of the methods work.
OK so both methods failed, maybe I'm doing something wrong...
First:
The real reason that I wanted s-off was because I wanted to install 4.4 so i decided to try with the RUU.
I tried with a locked and unlocked boot loader. the errors i got were;
1. FAILED (remote: 12 signature verify fail)
2. FAILED (remote: 99 unknown fail)
Then I went with the GURU method...
I installed the Rom, flashed stock recovery, and added root (Bootloader still unlocked).
1. Setup my HTC
2. Allowed USB debugging
3. turned fast boot off
4. Tried to run the rumrunner again (Am I missing a step here?!?)
Still get the rumrunner error.
Im not sure if its relevent, but I get this when trying to lock and unlock the bootloader:
HTML:
fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (No such file or directory))
finished. total time: 1.189s
And
HTML:
fastboot oem unlock
...
(bootloader) Erasing userdata...
(bootloader) eMMC Manufacturer ID: 15
(bootloader) Start Verify: 3
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (No such file or directory))
finished. total time: 10.802s
Does this tell you guys anything?
Check your drivers.. ? or install HTC Naked drivers.
SaHiLzZ said:
Check your drivers.. ? or install HTC Naked drivers.
Click to expand...
Click to collapse
Based on what part are you saying that?
Should I update the drivers and try to install RUU
or install and try to lock/unlock the bootloader.
ADB and fastboot do work just fine.
As for the rumrunner it was ran on a Unix machine. So the drivers shouldn't be an issue.
As an added suggestion, perhaps the drivers are not interacting properly to give those messages. Haven't seen those before. http://forum.xda-developers.com/showthread.php?t=2139767
(bootloader) Erasing userdata...
(bootloader) eMMC Manufacturer ID: 15
(bootloader) Start Verify: 3
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
AmirH said:
OK so both methods failed, maybe I'm doing something wrong...
First:
The real reason that I wanted s-off was because I wanted to install 4.4 so i decided to try with the RUU.
I tried with a locked and unlocked boot loader. the errors i got were;
1. FAILED (remote: 12 signature verify fail)
2. FAILED (remote: 99 unknown fail)
Then I went with the GURU method...
I installed the Rom, flashed stock recovery, and added root (Bootloader still unlocked).
1. Setup my HTC
2. Allowed USB debugging
3. turned fast boot off
4. Tried to run the rumrunner again (Am I missing a step here?!?)
Still get the rumrunner error.
Im not sure if its relevent, but I get this when trying to lock and unlock the bootloader:
HTML:
fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (No such file or directory))
finished. total time: 1.189s
And
HTML:
fastboot oem unlock
...
(bootloader) Erasing userdata...
(bootloader) eMMC Manufacturer ID: 15
(bootloader) Start Verify: 3
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (No such file or directory))
finished. total time: 10.802s
Does this tell you guys anything?
Click to expand...
Click to collapse
I didnt know that "fastboot oem unlock" works with the M7, but maybe it does with the GPe
have you checked the rumrunner thread? recommend you head over there and see if you get some help. i'm not familiar enough with GPe to be able to guide you properly. sorry
I cant believe I cant get this too work... after a little investigation, I'm starting to think that it might have something to do with the fact that
"fastboot getvar mainver" returns "mainver: "
I cant even flash a stock RUU
Edit:
Updated my mainver using this tool:
http://forum.xda-developers.com/showthread.php?t=2344671
still no help
I upgraded the firmware on the HTC One (AT&T Branded). In order to do that, I had to relock the bootloader and flash firmware.zip using fastboot. I did have a proper Nandroid backup from TWRP before doing this.. Now the phone is bricked, and TWRP does not start for some reason...
I can't flash TWRP again because the bootloaded is relocked.. And when I request the bootloader unlock key from htcdev.com, I get an error
Error Code: 173.
Error Reason: Check Rule Fail with exception.
Is there any way I can get around this?
Quick update - @HTCDev came back and told me that their unlock service was down. They fixed it now and I was able to download the unlock code file.
HOWEVER, when I go to fastboot and try to flash it, nothing happens on the device (the status still shows relocked) even though fastboot says that the command succeeded..
C:\Users\walletless\Desktop\One_All-In-One_Kit_v\Data>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.156s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.008s]
finished. total time: 0.167s
I also tried "fastboot reboot-bootloader" after this and it still shows status as relocked. I am on hboot 1.56 and supercid if it matters.
Anyone has suggestions?
fastboot getvar all shows:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.1540.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: (delete)
(bootloader) imei: (delete)
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4259mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.095s
Also tried fastboot erase cache.. Command completed successfully but still cannot boot into recovery
Next try would be ruu... any idea which RUU I should try?
I cant use guru reset since booting into recovery does not work (I get a screen with a red triangle and exclamation when I attempt to boot to recovery)
Finally, found a solution. Phew!
Just flashed an older firmware (http://arhd.onedroid.net/db_mirror/Firmware/HTC/HTC_One/401/3.62.401.1.zip) and I am able to boot into android now...
You shouldn't need to lock the bootloader to flash firmware. Anyway, you erased your custom recovery when you flashed that firmware. Re-flash TWRP again. Make sure you have the same version as you did before so you can restore your nandroid. Did you get your bootloader unlocked?
BTW, I'd advise that you delete the Serial and imei numbers from your getvar readout in your post.
Edit: Too slow to post again, glad your device working. Still should delete those numbers.
farang4u said:
You shouldn't need to lock the bootloader to flash firmware. Anyway, you erased your custom recovery when you flashed that firmware. Re-flash TWRP again. Make sure you have the same version as you did before so you can restore your nandroid. Did you get your bootloader unlocked?
BTW, I'd advise that you delete the Serial and imei numbers from your getvar readout in your post.
Edit: Too slow to post again, glad your device working. Still should delete those numbers.
Click to expand...
Click to collapse
I cant reflash anything for some reason.. the bootloader remains in "relocked" state even after I flash unlockcode..
Immediately after flashing unlockcode, my command window shows:
Code:
> fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.156s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.006s]
finished. total time: 0.165s
And the phone freezes on the fastboot screen - does not respond to any button presses, etc..
Finally got everything!!
Managed to unlock bootloader again using revone (./revone -u) and also removed the tamper flag using the -t switch.. flashed twrp and all is good again!!
Thanks....!
walletless said:
Finally got everything!!
Managed to unlock bootloader again using revone (./revone -u) and also removed the tamper flag using the -t switch.. flashed twrp and all is good again!!
Thanks....!
Click to expand...
Click to collapse
for future the best way to reclock and unlock boot loader if you are stuck is to flash any gpe firmware and simply run this command fastboot oem unlock voila it will be unlocked.
gunswordx said:
for future the best way to reclock and unlock boot loader if you are stuck is to flash any gpe firmware and simply run this command fastboot oem unlock voila it will be unlocked.
Click to expand...
Click to collapse
Thanks. I had tried that but it error'd out as well
btw, sorry I am not very good with acronyms.. what does "gpe firmware" mean?
Sent from my SGH-I337 using xda app-developers app
walletless said:
Thanks. I had tried that but it error'd out as well
btw, sorry I am not very good with acronyms.. what does "gpe firmware" mean?
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
gpe is the google edition firmware not having sense
gunswordx said:
gpe is the google edition firmware not having sense
Click to expand...
Click to collapse
Ah ok, that I did not try. Thanks for the tip!
Anyway, phone is up and running well now.. Rocking Android RevolutionHD 40.2
I mistakenly wiped the htc one m7 trying to install a rom based off kit kat I believe. Well, now I have no radios listed at all on the boot screen. I followed the tutorial on the forum for using fast boot to reflash the boot I believe. Process involved an older boot, which didn't flash with an error. I successfully flashed the latest 4.06 version of boot which was successful.
The thread went on to say I should start with the stock rom. Couldn't get it to load with adb side loader or fast boot flash zip name.zip. I have been able to successfully side load viper one, the latest version, and I have the latest version of terp as the recovery.
My problem is the phone will stay on no more than 15 sec. Before it reboots. I cannot see it in my computer although it shows up in device manager. I installed the latest driver from a thread on here.
Seems my options are fast boot and side loader, but I get a signed verification fail when I try to fast boot the radio , also taken from a radio thread here. I'm pretty sure I need s off which is the only thing left. Would this cause the phone to reboot continuously?
I'm tired of messing with it is it time to trash it or is this fixable? Thanks in advance and I'll give any info you guys need to help.
Latest Sprint Radio
from fastboot getvar
C:\Users\Tai\Desktop\HTC One Backup\Restore Data\Others>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA3C4S903734
(bootloader) imei: 990004288501756
(bootloader) meid: 99000428850175
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3796mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.040s
C:\Users\Tai\Desktop\HTC One Backup\Restore Data\Others>
I dont know if this helps or not.
This is what I get from fastboot when I try to load the radio...
C:\Users\Tai\Desktop\HTC One Backup\Restore Data\Others>fastboot flash radio Rad
io_HTC.zip
sending 'radio' (18554 KB)...
OKAY [ 2.250s]
writing 'radio'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 5.500s
C:\Users\Tai\Desktop\HTC One Backup\Restore Data\Others>
This is where I was last night. After searching on the threads, it seems that flashing hboot is ok, but the radios cannot be flashed without S-OFF. At this point what are my options as far as getting this radio in.
It did this auto reboot every 10-15 sec. the minute i flashed the improper rom. Again I've tried fixing with thread guidance on here for softbricking a Sprint device by flashing an ATT, etc. device.
Please help. Are there people you can call to undo damage like this or are you stuck fixing yourself?
Thanks
tpan1983 said:
This is what I get from fastboot when I try to load the radio...
C:\Users\Tai\Desktop\HTC One Backup\Restore Data\Others>fastboot flash radio Rad
io_HTC.zip
sending 'radio' (18554 KB)...
OKAY [ 2.250s]
writing 'radio'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 5.500s
C:\Users\Tai\Desktop\HTC One Backup\Restore Data\Others>
This is where I was last night. After searching on the threads, it seems that flashing hboot is ok, but the radios cannot be flashed without S-OFF. At this point what are my options as far as getting this radio in.
It did this auto reboot every 10-15 sec. the minute i flashed the improper rom. Again I've tried fixing with thread guidance on here for softbricking a Sprint device by flashing an ATT, etc. device.
Please help. Are there people you can call to undo damage like this or are you stuck fixing yourself?
Thanks
Click to expand...
Click to collapse
if you are using fastboot the radio has to be an image file, not a zip, or a boot.img, or get a radio zip file and flash from recovery.
54594563 3255
Aldo101t said:
if you are using fastboot the radio has to be an image file, not a zip, or a boot.img, or get a radio zip file and flash from recovery.
Click to expand...
Click to collapse
Woops typo. So, what I was doing was opening the .zip, and there are two files. A .inf I believe, and the image file (which Windows recognizes as such). I'm copying and pasting this file in the folder with the tools and fastbooting the .img with the command
fastboot devices
I see the phone serial and fastboot
fastboot flash radio radio.img
I get the error I posted before...
I would like to explore flashing from recovery. Given my situation is this possible? Also, do the stock ROMs, the RUU I believe, does it have the radio installed?
The link BD Posted here are flashable zips for recovery install
Sent from my HTCONE using Tapatalk
MODS PLEASE DELETE , cant find solution , thanks anyway
Im a dare to start my own thread to see if i can solve my problem, anyway, i own a xt1063 in wich i unlocked the bootloader in order to install lollipop and root, i have done this in the past with 3 xt1064's with no problem, however im facing a weird problem this time. So after i installed lollipop rom RETUGLB_XT1063_5.0.2_LXB22.46-28_cid9_CFC.xml via fasboot,everything went smooth as always, the phone boots up but after the world and blue m animation the phone goes into a blank (or black) screen and stays there and it goes no further than that, ive waited 20 plus minutes and nothing happens,i know the phone is on because i can see the screen its a bit bright but black, so i went to the original recovery and did a factory reset wich went nice, reboot and same result, so i instaled twrp via the Moto-G-2014-ToolKit-stable i found here, and booted the twrp recovery, wiped davilk cache,cache and after rebooting i got the same result. One thing i notice is, if i want to erase cache via stock recovery, the phone reboots inmediatly as if something went wrong, i twrp i get an error, trying to install the titan rom [ROM][5.0.2][titan][XT1063/64]The Titan Prime ROM[FEB 1](Version 1.1.2 RC) gives me a bunch of errors and nothing happens. Other thing i notice is that if i boot in twrp and mount the usb storage, i get terrible transfer rate speed, also if i copy something,lets say a rom, i can install such rom but once i restart and boot into twrp and mount the usb again, is like nothing was transfered, thres no rom in there, like if it wipes it self . Dont know what ealse to do, wonder if the cache partition its corrupted and dosnt let the phone fully start. Thanks for any help provided, and pardon my bad grammar, english its my second lenguage...
edited to add more details:
Everytime i try to lock the bootloader i get diferent mesages, but it nevers locks the bootloader.
or if i run the boot logo fix, the tool succesfully does the job as i can tell in the command window, but when i reboot i still get the warning logo as if nothing happened.
Click to expand...
Click to collapse
anyone please? im running out of ideas, thanks.
update 2 just in case someone wants to help, i instaled kk 4.4.4 with titan flasher, then instaled twrp, tried to instal any rom in twrp gets stuck in format system partition....
Have you tried to flash any stock firmware with fastboot?
dpdp73 said:
Have you tried to flash any stock firmware with fastboot?
Click to expand...
Click to collapse
Yes, kk 4.4.4 or lollipop 5.0.2 , no go , both gave the same result.
I wonder if theres a way to install a rom,at the same time wipe all the estructure inside the phone, can that be achieved via adb perhaps? as fastboot seems a bit limited. anyway heres a video that shows how the phone boots to a blank screen on a clean fasboot instaled 5.0.2 stock rom www.youtube.com/watch?v=D8CgqNOp-_g
and this is what happens if i try to clean cache with recovery
www.youtube.com/watch?v=oBivRORNH1I
Try things like "fastboot erase cache", "fastboot erase data(/system etc.)".
But it doesn't look good.
dpdp73 said:
Try things like "fastboot erase cache", "fastboot erase data(/system etc.)".
But it doesn't look good.
Click to expand...
Click to collapse
tried too,was a no go.... dont no what ealse to try, i pretty much done everything
another update while someone steps up and helps.
My phone looks like its write protected, but i can install any recovery i want and boot it. so if i install twrp i can boot to it, if i mount the usb system i can copy files to it, but as soon as i reboot, the files get deleted by magic... so next thing i tried, install stock kk 4 or lollipop via stock recover and sideload adb, i get a fingerprint error message, package expects build fingerprint of motorola/titan_retuglb/titan_umts:4.4.4/KXB/21.85-17/14:user/release , but after that i flashed KK rom via fastboot, all goes well , so i reboot and start recovery and tried to install lollipop via adb side load and i get a fingerprint message again, and dont mater how many roms i flash via fasboot and they look like they installed ok, if i restart stock recovery and try to update with any rom , i get this message,
package expects build fingerprint of motorola/titan_retuglb/titan_umts:4.4.4/KXB/21.85-17/14:user/release-keys or motorola/titan_retuglb/titan_umts:5.0/LXB22.39-6/6:user/release-keys; this device has motorola/titan_retuglb/titan_umts:4.4.4/KXB23/25:u
instalation aborted.
even after flashing lollipop, system says device has KK ,wich lead me to think its been wirte protected.
will keep looking and hope for some smart help, thanks.
please help anyone
Code:
C:\mfastboot-v2>fastboot getvar all > command.txt
(bootloader) version: 0.5
(bootloader) version-bootloader: 4807(*)
(bootloader) product: titan
(bootloader) secure: yes
(bootloader) hwrev: 0x8400
(bootloader) radio: 0x1
(bootloader) emmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Elpida S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: ZX1D3239LM
(bootloader) cid: 0x0009
(bootloader) channelid: 0x8d
(bootloader) uid: D59CBB060F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: 359297052588158
(bootloader) meid:
(bootloader) date: 10-23-2014
(bootloader) sku: XT1063
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Dec 2 3:44:40 UTC 2014"
(bootloader) ro.build.fingerprint[0]: motorola/titan_retuglb/titan_umts:
(bootloader) ro.build.fingerprint[1]: 4.4.4/KXB21.85-23/21:user/release-
(bootloader) ro.build.fingerprint[2]: keys
(bootloader) ro.build.version.full[0]: Blur_Version.21.11.23.titan_retug
(bootloader) ro.build.version.full[1]: lb.retuglb.en.US
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-g668a77b ([email protected]
(bootloader) kernel.version[1]: ilclbld53) (gcc version 4.7 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Tue Aug 26 20:21:50 CDT 2014
(bootloader) sdi.git: git=MBM-NG-V48.07-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V48.07-0-g683cb0c
(bootloader) rpm.git: git=MBM-NG-V48.07-0-g71b1aae-dirty
(bootloader) tz.git: git=MBM-NG-V48.07-0-ga27c415
(bootloader) aboot.git: git=MBM-NG-V48.07-0-ge875a20
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 0/0
(bootloader) productid: ZX1D3239LM
(bootloader) sutinfo:
all: listed above
finished. total time: 0.088s
I have the exact same problem
xGiorgos said:
I have the exact same problem
Click to expand...
Click to collapse
come here and fight with us http://forum.xda-developers.com/moto-g-2014/help/phone-write-protected-freezed-t3030812
Hi.
I have black screen after motorola moto g animation (I can see some light, but blank screen).
I can enter on fastboot mode and have the bootloader unlocked. . I tried to reflash the firmware but i have still the same error.
I tried to downgrade from 5.0.2 to 4.4.4 but I can't do it, it displays this error:
"C:\A>mfastboot.exe flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (2184 KB)...
OKAY [ 0.160s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.472s"
I tried a lot of procedures searching my problem in google, but noone works.
Maybe is a wrong firmware image? can you help me with the correct image or solving the issue?
I'm desperate and need a solution, here you can see some information:
"C:\A>mfastboot.exe getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 4882(*)
(bootloader) product: titan
(bootloader) secure: yes
(bootloader) hwrev: 0x8400
(bootloader) radio: 0x5
(bootloader) emmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Hynix S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: ZX1D22PPCL
(bootloader) cid: 0x0007
(bootloader) channelid: 0x40
(bootloader) uid: C26F6D070F000000000000000000
(bootloader) securestate: unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: XXXXXXXXXXX
(bootloader) meid:
(bootloader) date: 12-13-2014
(bootloader) sku: XT1068
(bootloader) battid: (null)
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Jul 14 15:45:22 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/titan_retaildsds/titan_um
(bootloader) ro.build.fingerprint[1]: tsds:5.0.2/LXB22.46-28/28:user/rel
(bootloader) ro.build.fingerprint[2]: ease-keys
(bootloader) ro.build.version.full[0]: Blur_Version.22.21.28.titan_retai
(bootloader) ro.build.version.full[1]: ldsds.retaildsdsall.en.03
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-g48d3b85 ([email protected]
(bootloader) kernel.version[1]: ilclbld54) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Tue Jan 6 10:38:33 CST 2015
(bootloader) sdi.git: git=MBM-NG-V48.82-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V48.82-0-g7e74e90
(bootloader) rpm.git: git=MBM-NG-V48.82-0-g20516c3-dirty
(bootloader) tz.git: git=MBM-NG-V48.82-0-g72f9f12
(bootloader) aboot.git: git=MBM-NG-V48.82-0-ge004609
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 0/0
(bootloader) productid: ZX1D22PPCL
(bootloader) sutinfo:
(bootloader) ro.carrier: reteu
all: listed above
finished. total time: 0.101s"
Very thanks guys. :crying:
If you are trying to downgrade from 5.x/6.x to 4.4, remember you do not flash .mbn file. Flashing .mbn will attempt to downgrade your bootloader and might corrupt it, as bootloader downgrade is not supported/advised. I suggest you flash 5.x stock firmware WITH .mbn file and this should solve your problem.
Try firmware from this thread:
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-original-motorola-t3155774
just try to flash a recovery like twrp then install cm like rom first
pank.dhnd said:
If you are trying to downgrade from 5.x/6.x to 4.4, remember you do not flash .mbn file. Flashing .mbn will attempt to downgrade your bootloader and might corrupt it, as bootloader downgrade is not supported/advised. I suggest you flash 5.x stock firmware WITH .mbn file and this should solve your problem.
Try firmware from this thread:
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-original-motorola-t3155774
Click to expand...
Click to collapse
What image should I use for XT1068 Europe Dual Sim ??? in relation with the fastboot vars?
When i Install twrp it won't display errors, but when i access to recovery it access to the stock recovery :/
If I manually boot from twrp whitout flashing it, i get stuck on "teamwin" logo.
vaisakmct said:
just try to flash a recovery like twrp then install cm like rom first
Click to expand...
Click to collapse
lsard said:
When i Install twrp it won't display errors, but when i access to recovery it access to the stock recovery :/
If I manually boot from twrp whitout flashing it, i get stuck on "teamwin" logo.
Click to expand...
Click to collapse
That's what I am saying, flash stock Lollipop, it will restore your bootloader and recovery (if any changes were made during downgrade), and then flash recovery.
---------- Post added at 05:46 AM ---------- Previous post was at 05:37 AM ----------
lsard said:
What image should I use for XT1068 Europe Dual Sim ??? in relation with the fastboot vars?
Click to expand...
Click to collapse
Ohh, for Europe dual sim, you can use image from below thread:
http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-5-0-2-lxb22-46-t3019612
The thread I posted earlier has Indian images mostly, but it won't make much difference.
pank.dhnd said:
That's what I am saying, flash stock Lollipop, it will restore your bootloader and recovery (if any changes were made during downgrade), and then flash recovery.
---------- Post added at 05:46 AM ---------- Previous post was at 05:37 AM ----------
Ohh, for Europe dual sim, you can use image from below thread:
http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-5-0-2-lxb22-46-t3019612
The thread I posted earlier has Indian images mostly, but it won't make much difference.
Click to expand...
Click to collapse
Still the same error, blank screen after motorola animation, reflashing this firmware -> ***NEW*** DOWNLOAD XT1068 5.0.2 LXB22.99-16.3 RETDSDS WITH STAGE FRIGHT FIX RETAIL DUAL SIM DUAL STANDBY (EU/INDIAN/GLOBAL) 26/08/2015 BUILD ***NEW***
Nobody can help me?
Do you think my phone is not recoverable?
:crying:
lsard said:
Nobody can help me?
Do you think my phone is not recoverable?
:crying:
Click to expand...
Click to collapse
Did u try any custom ROM?
And don't worry, your phone boots perfectly that means no issue with it.
pank.dhnd said:
Did u try any custom ROM?
And don't worry, your phone boots perfectly that means no issue with it.
Click to expand...
Click to collapse
I can't install any ROM, I tried to install cm rom by adb but it fails at the installation process. Can't install neither any recovery.
I think is a blocked partition or something like this.
Please help me solving this.... nobody know why I can't install any rom/recovery?
lsard said:
Please help me solving this.... nobody know why I can't install any rom/recovery?
Click to expand...
Click to collapse
You can try to boot into twrp, you have to use the 2.8.5.0 version, newer ones will fail.
Sent from my Moto G 2014 using XDA Free mobile app
Wolfcity said:
You can try to boot into twrp, you have to use the 2.8.5.0 version, newer ones will fail.
Sent from my Moto G 2014 using XDA Free mobile app
Click to expand...
Click to collapse
Hi Wolfcity, thanks for your support.
I installed twrp 2.8.5.0 version as you told me. I'm still with the same problem. When I installer the twrp recovery it will boot from stock recovery. If I manually boot from trwp it will stuck on the Teawin logo.
I installed this iso -> https://dl.twrp.me/titan/twrp-2.8.5.0-titan.img
I'm desperate
You say your bootloader is possibly corrupt, that would be a result of a bad mbn flash in your phones bootloader. Explain to me exactly how you performed the .mbn flashing process so I may formulate a solution. Thanks
GhettoButta said:
You say your bootloader is possibly corrupt, that would be a result of a bad mbn flash in your phones bootloader. Explain to me exactly how you performed the .mbn flashing process so I may formulate a solution. Thanks
Click to expand...
Click to collapse
I tried various processes searching by google, but the last i think was following this thread:
http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-t3018682
Thanks you so much, I can post you all the fastboot vars if you need.
You say your bootloader is possibly corrupt, that would be a result of a bad mbn flash in your phones bootloader. Explain to me exactly how you performed the .mbn flashing process so I may formulate a solution. Thanks
EDIT: Also list your previous motoboot.img version you used for the flashing process.
Tell me your carrier?
http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-5-0-2-lxb22-46-t3019612
go here may be this post will help you for your issue .
GhettoButta said:
You say your bootloader is possibly corrupt, that would be a result of a bad mbn flash in your phones bootloader. Explain to me exactly how you performed the .mbn flashing process so I may formulate a solution. Thanks
EDIT: Also list your previous motoboot.img version you used for the flashing process.
Tell me your carrier?
Click to expand...
Click to collapse
I tried so many proceduress..
I used this posts:
- http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-t3018682
- http://forum.xda-developers.com/moto-g-2014/development/rom-stock-lollipop-rom-t3024800
- http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
Maybe is not the order... i tried like 4 or 5 reflash to stock but nothing changes, i'm getting the exact same error.
Thanks
Can't believe it can't be solved!!
I have a great commitment with this smartphone
go to service center dont mention about ur bootloader unlocked just told them u face this screen at the time of update .dont touch anything else just submit your handset