Hi,
I have a Motorola XT925 that appears to be unrecoverable and I was wondering if anyone here has been able to solve. I have looked through this group and there seems to be similar issues but non resolved for my particular issue.
When the phone attempts to boot I get the "Encryption unsuccessful" message with a "Reset phone" button that does nothing. According to other posts I have read on this error, if I could unlock the bootloader (and wipe the device) all would be well, however, when I get the phone into fastboot mode and attempt the unlock (as detailed on the Motorola website), it states the phone does not qualify for bootloader unlocking.
I see there is an exploit that can unlock the bootloader if the phone has root installed, however this phone does not and will not boot...
Is there anything that can be done?
Do you have the unlock key?
If its an xt925 ,it should qualify for unlock.
Make sure you update your drivers, try using another port (2.0 preferably), and that you copy the string correctly.
Tapatalk with RAZR HD
neo.ank said:
Do you have the unlock key?
If its an xt925 ,it should qualify for unlock.
Make sure you update your drivers, try using another port (2.0 preferably), and that you copy the string correctly.
Tapatalk with RAZR HD
Click to expand...
Click to collapse
Thanks for replying, you are indeed correct. I must have cut and paste the unlock key incorrectly. However, I still do not think thing the phone is functioning correctly as I am not able to do anything with the fastboot command. I can not erase/format partitions (userdata or cache), I can not flash either the recovery (to CWM) or boot partitions and can't even boot the phone directly to the recovery image.
Here are some outputs from the fastboot:
C:\Users\EIT-Z820\Downloads>fastboot getvar all
(bootloader) version-bootloader: 109B(*)
(bootloader) product: vanquish_u
(bootloader) secure: yes
(bootloader) mid: 0056
(bootloader) version: 0.5
(bootloader) serialno: TA24000RHS
(bootloader) qe: qe 0/0
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 31457280
(bootloader) emmc-size: 16GB
(bootloader) reason: Reboot to bootloader
(bootloader) revision-hardware: 0x8300
(bootloader) cpu: MSM8960 CS
(bootloader) uid: 1789E20102000100000000000000
(bootloader) cid: 0x0e
all:
C:\Users\EIT-Z820\Downloads>fastboot erase cache
(bootloader) Variable not supported!
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 0.049s
C:\Users\EIT-Z820\Downloads>fastboot flash recovery recovery.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (7892 KB)...
OKAY [ 0.612s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
Not sure what the Variable not supported message is, however even when I unlocked the device, there was a message saying that it was unable to erase partition.
Any ideas?
Drivers, could be the reason. Try re-installing.
Also, use 'mfastboot' and see if the issue persist.
Tapatalk with RAZR HD
Related
Hi,
Unlocked my wife's Legend using the HTC-Dev method. Installed CM7 and she was happy... Now she is missing the HTC weather animations and wants to go back to the stock Froyo.
I have the correct RUU for her phone, carrier, and region, extracted from:
RUU_Legend_BellMobility_WWE_2.02.666.3_Radio_47.37.35.09_7.08.35.05_release_130094_signed.exe
First I tried to flash by renaming the rom.zip to LEGEIMG.zip. The bootloader saw it and chewed on it for a while, but the RUU ended up not being applied and the phone booted back into CM. Confusing.
Next attempt: fastboot, with bootloader unlocked.
Code:
[[email protected] ruu]# [B]fastboot erase cache[/B]
erasing 'cache'...
OKAY [ 0.258s]
finished. total time: 0.258s
[[email protected] ruu]# [B]fastboot oem rebootRUU[/B]
...
OKAY [ 0.017s]
finished. total time: 0.017s
[[email protected] ruu]# [B]fastboot flash zip rom.zip[/B]
sending 'zip' (124420 KB)...
OKAY [ 12.795s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
[B]FAILED (remote: 99 unknown fail)[/B]
finished. total time: 18.643s
Did some more reading, found that RUUs only apply when the bootloader is locked. So I relocked the bootloader with fastboot oem lock and tried again:
Code:
[[email protected] ruu]# [B]fastboot erase cache[/B]
< waiting for device >
erasing 'cache'...
OKAY [ 0.258s]
finished. total time: 0.258s
[[email protected] ruu]# [B]fastboot oem rebootRUU[/B]
...
OKAY [ 0.017s]
finished. total time: 0.017s
[[email protected] ruu]# [B]fastboot flash zip rom.zip[/B]
sending 'zip' (124420 KB)...
OKAY [ 12.874s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
[B]FAILED (remote: 43 main version check fail)[/B]
finished. total time: 44.062s
And trying the LEGEIMG.zip method after relocking:
Code:
Main version is older!
Update Fail!
Do you want to reboot device?
Here are my bootvars:
Code:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.02.0000
(bootloader) version-baseband: 7.13.35.13
(bootloader) version-cpld: None
(bootloader) version-microp: 0816
(bootloader) version-main: 3.30.0.0
(bootloader) serialno: HT05NRA07XX
(bootloader) imei: XXXXX
(bootloader) product: legend
(bootloader) platform: HBOOT-7227
(bootloader) modelid: PB7611000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3905mV
(bootloader) partition-layout: HTC
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-39ec9098
(bootloader) hbootpreupdate: 11
Apparently this means that I'm trying to flash an RUU that is older than what is on the device. The problem is, the RUU update that I last applied was the HTCDev one to allow unlocking. So the most recent "full" RUU is older than the HTCDev RUU and I can't seem to downgrade.
Am I missing something? I must be missing something. Please help, or the wife will have one up on me. Can't allow that
Hello,
try this ROM from BlaY0, its an improved stock ROM and you keep root.
When I remember right, there was no version check during installation, you can install it with Clockwork mode Recovery.
alligator_asl said:
Hello,
try this ROM from BlaY0, its an improved stock ROM and you keep root.
Click to expand...
Click to collapse
Thanks, that's an acceptable workaround for now. I ended up going this route. Since CWM 5.X doesn't like "amend" scripting, it took some doing though. :highfive:
If anyone knows of a way to downgrade to a stock RUU after applying the HBOOT 1.02 RUU to the Legend, that would be a help.
I'd suggest if you really need to go back stock froyo it can't be done with hboot 1.02, I have tried various different methods with no success.
I can't remember who, but some where on legend forums (I think in the dev section) there is a method to downgrade back to hboot 1.01, if it works you can do it and flash ruu. I can't confirm if it works or not.
Sent from my Legend using xda app-developers app
ranger4740 said:
I can't remember who, but some where on legend forums (I think in the dev section) there is a method to downgrade back to hboot 1.01, if it works you can do it and flash ruu. I can't confirm if it works or not.
Click to expand...
Click to collapse
Yeah, that sounds right.
So for anyone reading this thread in the future, if you've unlocked your bootloader using HTC-dev you will be unable to return to stock Froyo using an official RUU without first downgrading to HBOOT 1.01 or older.
The HBOOT downgrade process is pretty involved. You need a goldcard and the hack4legend kit. See this thread for details.
And for good measure, here's a thread with someone else working out the same problem we just worked out here... :silly:
At the end of the day, if you ran a nandroid backup of your stock ROM before blowing it away, you won't need all this jazz.
ariaxu said:
Since CWM 5.X doesn't like "amend" scripting, it took some doing though.
Click to expand...
Click to collapse
You can take an older Versin of CWM ( recovery-clockwork-2.5.0.7-legend.zip ), ther are no problems with scripting, a google search brings several results.
If necessary, you lan load the old version of CWM from the new version and then you can flash this ROM !
I believe I did all the steps correctly but it did not seem to work. May have not done the 'immediate' step quickly enough (fastboot oem boot)? Anyway, i tried it a few more times again without success. I seemed to not be able to write the 3 files equired at the end specifically #2 + 3. Now it says it can't find my fastboot flash zip (I renamed mine soff.zip) but it is there...Thought I would give it and me space for a while before I try again. Anyone with any suggestions?
The soffbin3 is the file inside the zip... You need to pull that file out and flash that the p830000000-dna.zip is the one you leave alone
Sent from my Nexus 7 using XDA Premium HD app
.torrented said:
The soffbin3 is the file inside the zip... You need to pull that file out and flash that the p830000000-dna.zip is the one you leave alone
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Pretty sure I extracted that but will double check, thanks..
rootntootn said:
Pretty sure I extracted that but will double check, thanks..
Click to expand...
Click to collapse
Posting command file here as it did not work again...... I put the zip file and extracted in my working directory not the phone,is that correct? just occured to me that it may need to be on phone sd card anyway below is what got spit out, any help appreciated.
C:\adt-bundle-windows-x86\sdk\platform-tools>adb reboot bootloader
adb server is out of date. killing...
* daemon started successfully *
C:\adt-bundle-windows-x86\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.047s]
finished. total time: 0.049s
C:\adt-bundle-windows-x86\sdk\platform-tools>fastboot flash zip soff.zip
sending 'zip' (36905 KB)...
OKAY [ 3.370s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 3.595s
C:\adt-bundle-windows-x86\sdk\platform-tools>fastboot oem boot
...
(bootloader) monarudo_vibrate_device_time(): vibrate 200(ms)...
(bootloader) Boot/Recovery signature checking...
(bootloader) TZ_HTC_SVC_HASH ret = 0
(bootloader) setup_tag addr=0x80600100 cmdline add=0x003147C8
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:skuid 0x32401
(bootloader) TAG:hero panel = 0x94005B
(bootloader) TAG:engineerid = 0x0
(bootloader) TAG: PS ID = 0x0
(bootloader) TAG: Gyro ID = 0x1
(bootloader) Device CID is super CID
(bootloader) CID is super CID
(bootloader) Backup CID is empty
(bootloader) setting->cid::22222222
(bootloader) serial number: FA2BAS504674
(bootloader) commandline from head: console=ttyHSL0,115200,n8 androidboot
(bootloader) .hardware=dlx user_debug=31
(bootloader) command line length =796
(bootloader) active commandline: poweron_status=1 reset_status=0 board_mo
(bootloader) narudo.disable_uart3=0 diag.enabled=0 board_monarudo.debug_u
(bootloader) art=0 userdata_sel=0 androidboot.emmc=true androidboot.pages
(bootloader) ize=2048 skuid=0 ddt=20 ats=0 androidboot.lb=1 td.td=1 td.s
(bootloader) f=1 td.ofs=328 td.prd=1 td.dly=0 td.tmo=300 hlog.ofs=628 un.
(bootloader) ofs=694 imc_online_log=0 androidboot.efuse_info=SNSL androi
(bootloader) dboot.baseband=1.00.00.1023_3 androidboot.cid=22222222 andro
(bootloader) idboot.devicerev=3 androidboot.batt_poweron=good_battery and
(bootloader) roidboot.carrier=COM
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=local
(bootloader) aARM_Partion[5].name=cache
(bootloader) aARM_Partion[6].name=userdata
(bootloader) aARM_Partion[7].name=devlog
(bootloader) aARM_Partion[8].name=pdata
(bootloader) aARM_Partion[9].name=extra
(bootloader) aARM_Partion[A].name=radio
(bootloader) aARM_Partion.name=adsp
(bootloader) aARM_Partion[C].name=dsps
(bootloader) aARM_Partion[D].name=radio_config
(bootloader) aARM_Partion[E].name=modem_st1
(bootloader) aARM_Partion[F].name=modem_st2
(bootloader) aARM_Partion[10].name=cdma_record
(bootloader) aARM_Partion[11].name=reserve
(bootloader) partition number=18
(bootloader) Valid partition num=18
(bootloader) setting_get_bootmode() = 9
(bootloader) smem 8CF04000 (phy 8CF04000): TZ_HTC_SVC_UPDATE_SMEM ret = 0
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) TZ_HTC_SVC_DISABLE ret = 205643776 (0xC41E000)
(bootloader) jump_to_kernel: machine_id(4060), tags_addr(0x80600100), ker
(bootloader) nel_addr(0x80608000)
(bootloader) -------------------hboot boot time:156503 msec
FAILED (status read failed (Too many links))
finished. total time: 2.904s
C:\adt-bundle-windows-x86\sdk\platform-tools>
I already see what's wrong..
When you
fastboot flash zip P8300000-DNA.ZIP
you flash that not the soffbin3 file the soffbin3 is for later
Sent from my HTC6435LVW using XDA Premium HD app
.torrented said:
I already see what's wrong..
When you
fastboot flash zip P8300000-DNA.ZIP
you flash that not the soffbin3 file the soffbin3 is for later
Sent from my HTC6435LVW using XDA Premium HD app
Click to expand...
Click to collapse
I did do that, It looks like I didn't because I renamed my P8300000-DNA.ZIP file to soff.zip so I wouldn't have to type all those characters.
rootntootn said:
I did do that, It looks like I didn't because I renamed my P8300000-DNA.ZIP file to soff.zip so I wouldn't have to type all those characters.
Click to expand...
Click to collapse
try putting it back to its orig name and then when your in cmd prmpt just type the P and press tab it will fill the rest in (i dont know the exact name so if i were you i would look it up)
if that doesnt work do a data factory reset in recovery and wipe both caches
.torrented said:
try putting it back to its orig name and then when your in cmd prmpt just type the P and press tab it will fill the rest in (i dont know the exact name so if i were you i would look it up)
if that doesnt work do a data factory reset in recovery and wipe both caches
Click to expand...
Click to collapse
I downloaded the file again and used the original name and still a no go gets the remote 99 unknown fail below
sending 'zip' (36905 KB)...
OKAY [ 3.370s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 3.595s
Is it possible I need stock kernal first?
rootntootn said:
I downloaded the file again and used the original name and still a no go gets the remote 99 unknown fail below
sending 'zip' (36905 KB)...
OKAY [ 3.370s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 3.595s
Is it possible I need stock kernal first?
Click to expand...
Click to collapse
The remote 99 for me and for .torrented the night it was released meant that we had to start over, he restored a nandroid backup from before the process and I just wiped and installed the rom clean.
Mine was because I goofed and ran the flash zip command line twice after the error 92 I ran it one more time because I misinterpreted the message.
So I ended up wiping and reflashing the rom, going into settings/developer options and enabling USB debugging, and doing the process correctly and it worked right off the bat.
But for me at least once I got that error 99 I couldn't get past it until I started with clean system files from before I began pushing the adb lines after the system reboot.
CharliesTheMan said:
The remote 99 for me and for .torrented the night it was released meant that we had to start over, he restored a nandroid backup from before the process and I just wiped and installed the rom clean.
Mine was because I goofed and ran the flash zip command line twice after the error 92 I ran it one more time because I misinterpreted the message.
So I ended up wiping and reflashing the rom, going into settings/developer options and enabling USB debugging, and doing the process correctly and it worked right off the bat.
But for me at least once I got that error 99 I couldn't get past it until I started with clean system files from before I began pushing the adb lines after the system reboot.
Click to expand...
Click to collapse
Thanks! I tried doing factory reset and wiped all cache and that also did not work...will find a backup from earlier and go again, I did do some repeats of commands so this sounds like maybe what I need to do...
rootntootn said:
Thanks! I tried doing factory reset and wiped all cache and that also did not work...will find a backup from earlier and go again, I did do some repeats of commands so this sounds like maybe what I need to do...
Click to expand...
Click to collapse
BINGO! That did it. Thanks for everyones help!!
Hi everyone.
Thanks to all of you who help us non-devs upgrade our phones to be so much better than they would be with just stock software and OS. I'm hoping that someone knows how to fix my phone. I have done a lot of reading, and don't intend to be like the bear in that neat animation, "Trying to give a, Phone Idiot, Support," about the noob who fried his phone and doesn't know what kind of phone he has, or what ROM he flashed.
I read several helpful posts, but am still not sure that I have the tools I need to fix this thing. The best lead so far looks to be deBricker's guide to un-brick a Galaxy S3. After some delayed sleep, I might be sane enough (back to about halfway again) to find the right files for my Evo 3d, and will give that approach a try. But I figured I'd post this in case someone out there sees from the data provided, that doing something similar to what deBricker's guide details for a Galaxy, will make things even worse for me. I would appreciate a lead on where to get the right files for my Evo 3d. I'm at least clued in enough to not try the files for the S3 in my Evo 3d. Oh, and I regularly do Nandroid backups.
I have a hard bricked HTC Evo 3d. It's likely my fault for installing something incorrectly, or something that isn't supposed to go on my phone, or for missing something that I should have done prior to installing. Other ROMs I've tried have worked well.
I installed MNRGS2JB108.zip, aka MidnightRomGS2JB, by xthedakmanx. It looked like it was a neat ROM worth trying. But, it was a bad decision, in my case! No blame to anyone (other than me), though. Responsibility is mine, but I sure would love to have someone be hero of the day and tell me how to fix it!
I ended up with NO MEANS OF LOADING OR FLASHING ANYTHING by a battery pull and volume down + power on. Plus, the phone won't even try to power up. In a darkened room, I can sometimes get, with a fully-charged battery, a super-dim, barely-detectable, red power light to light up.
Early on, I saw the not-uncommon QHSUSB_DLOAD on my Win7 laptop when I connected my phone via USB. After some frantic searching around, I got drivers to allow my laptop to now show it on the device manager under ports as "Qualcomm HS-USB QDLoader9000" on COM4. But that hardly lets me just open up a file explorer and fix things.
When I open a cmd box and try to use fastboot commands to flash and such, my laptop does see my phone, briefly (maybe 8 seconds or so, as others have mentioned in other threads), and while I have been able to successfully use some of the commands. Here's what I was able to do, and the information I was able to pull from my phone, in case it helps you guys to figure out what's wrong, and better still, how I can fix it. I think it might be better to give lots of info rather than leaving people playing 20 questions to understand my particular predicament. But, if the following copy-paste is superfluous and of little value after all, sorry about that.
C:\Users\Hedgehog\Desktop\RootEvo4GNew2>fastboot oem readcid
< waiting for device >
...
(bootloader) cid: 11111111
C:\Users\Hedgehog\Desktop\RootEvo4GNew2>fastboot oem checkSbl1
(bootloader) sbl1 signature checking...
(bootloader) TZ_HTC_SVC_VERIFY_BOOTLOADER ret = 0
(bootloader) sbl1 verified successfully
C:\Users\Hedgehog\Desktop\RootEvo4GNew2>fastboot oem checkHWSecurity
...
(bootloader) HW Security has been enabled !
C:\Users\Hedgehog\Desktop\RootEvo4GNew2>fastboot oem keytest
...
(bootloader) start keypad testing ...
FAILED (status read failed (Too many links))
finished. total time: 8.402s
C:\Users\Hedgehog\Desktop\RootEvo4GNew2>fastboot oem heap
...
(bootloader) Total free heap size: 536784792 Bytes (0x1FFEAF98)
(bootloader) Max. free heap segment size: 536760320 Bytes (0x1FFE5000)
(bootloader) Max. free NPC heap segment size: 536760320 Bytes (0x1FFE5000
(bootloader) )
OKAY [ 0.019s]
C:\Users\Hedgehog\Desktop\RootEvo4GNew2>fastboot oem heap_test
...
(bootloader) ======heap_test (Ver: 1.0)======
(bootloader) heap_test <test_mode> <cyles> <break> <cache/non-cache> <ob
(bootloader) verse/reverse> <seed/pattern>
(bootloader) <test_mode> (0): Mix pattern mode -> heap_test 0 <cy
(bootloader) les> <break>
(bootloader) <test_mode> (1): Fix pattern mode -> heap_test 1 <cy
(bootloader) les> <break>
(bootloader) <test_mode> (2): Random pattern mode -> heap_test 2 <cy
(bootloader) les> <break>
(bootloader) <test_mode> (3): Assign seed mode -> heap_test 3 <cyles
(bootloader) > <break> <cache/non-cache> <obverse/reverse> <seed>
(bootloader) <test_mode> (4): Assign fix pattern mode -> heap_test 4 <cy
(bootloader) les> <break> <cache/non-cache> <obverse/reverse> <pattern>
(bootloader) <cyles> The number of testing cycle
(bootloader) <break> Command break off when RAM issue occurs 0:Not break
(bootloader) off 1:Break off when RAM issue occurs
(bootloader) <cache/non-cache> use cache or non-cache memory space 0:cac
(bootloader) he 1:non-cache
(bootloader) <obverse/reverse> assign the direction of scanning 0bvers
(bootloader) e 1:reverse
(bootloader) <seed/pattern> seed to create random pattern for each byte
(bootloader) / pattern for every byte
C:\Users\Hedgehog\Desktop\RootEvo4GNew2>fastboot oem enableqxdm 0
...
(bootloader) Start Verify: -1
(bootloader) Start Verify: -1
(bootloader) erase sector 130560 ~ 131071 (512)
C:\Users\Hedgehog\Desktop\RootEvo4GNew2>fastboot oem gencheckpt
...
(bootloader) Start Verify: -1
(bootloader) Start Verify: -1
(bootloader) erase sector 130560 ~ 131071 (512)
(bootloader) [DISPLAY_ERR] allocate heap for splash image fail!!!
(bootloader) setup_tag addr=0x48000100 cmdline add=0x801DD990
(bootloader) TAG:Ramdisk OK
FAILED (status read failed (Too many links))
finished. total time: 8.495s
C:\Users\Hedgehog\Desktop\RootEvo4GNew2>fastboot oem boot
...
(bootloader) [DISPLAY_ERR] allocate heap for splash image fail!!!
(bootloader) setup_tag addr=0x48000100 cmdline add=0x801DD990
(bootloader) TAG:Ramdisk OK
FAILED (status read failed (Too many links))
finished. total time: 8.580s
C:\Users\Hedgehog\Desktop\RootEvo4GNew2>fastboot oem readimei
...
(bootloader) imei: [my imei number was here]
C:\Users\Hedgehog\Desktop\RootEvo4GNew2>fastboot oem readsecureflag
...
(bootloader) secure_flag: -1
So at least the thing is showing something still inside my phone, and that it can be read. The trouble is, that I'm not able to get it to receive any changes:
C:\Users\Hedgehog\Desktop\RootEvo4GNew2>fastboot flash recovery recovery-clockwo
rk-touch-5.8.0.1-shooter.img
< waiting for device >
sending 'recovery' (4128 KB)...
OKAY [ 0.566s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.567s
C:\Users\Hedgehog\Desktop\RootEvo4GNew2>
That part about "FAILED (remote: not allowed)," is a little saddening, to say the least. And, I've been struggling and worrying about this, a lot longer than 0.567 second! If not for that "not allowed" error, things might be OK. So, is the deBricker's guide the approach to try next?
FWIW, I do have a broken but not bricked, Evo 3d (bad touch screen but probably good data files) that might help supply data files. Yeah, I ought to try pulling stuff off of it and beat the odds and fix it on my own, but I've been reading and tinkering for a couple of days already, and someone else might know just what to do, hence I am humbly asking for some pointers.
Again, sorry for the size of this post, and thanks for any help!
No adb, no recovery. QHSUSB_DLOAD fastboot gets msg FAILED (remote: not allowed)
hedgehog45ve;43863237
...
Early on said:
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.567s
That part about "FAILED (remote: not allowed)," is a little saddening, to say the least.
Click to expand...
Click to collapse
Some additional information I have gotten out of my phone, in case it helps anyone reading this thread, to come up with a fix, is:
platform: HBOOT-8260
modelid: CΣCΣCΣCΣCΣCΣCΣCΣCΣCΣCΣCΣCΣCΣCΣCΣ
cidnum: C
Σ
C:\Users\Hedgehog\Desktop\RootEvo4GNew2>fastboot getvar battery-voltage [DONE WITH THE BATTERY IN]
< waiting for device >
battery-voltage: 3800mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: UNKNOWN
commitno-bootloader: dirty-3f645641
hbootpreupdate: 11
gencheckpt: 0
The main stumbling block I have right now, in addition to not powering up, especially to recovery, is that the phone doesn't stay connected to fastboot longer, and that whatever I try to do to the phone with fastboot, is always rejected, "FAILED (remote: not allowed)".
Any ideas?
Thanks.
My moto z got stucked in the famous Qualcomm 9008 Emergency mode. How i bricked my moto z? Or maybe would be better say, how Motorola did brick my moto z?
Yes I'm blaming motorola for this, and i have some good motivations for this.
I'll tell you the complete story of my brick.
I was having some trouble on oreo due to a failed root, so just came back to 7.1.1 and i was trying to go to oreo again by installing ota after ota. Actually i was able to install something about 4 or 5 otas before the boom. After the last ota the phone just turned off and after a couple of hours I noticed that the phone was detected as Qualcomm 9008 in Windows device manager.
Here the story get very interesting.
In fact i firstly tried to flash many blankflash files without success, seems like my moto z wasn't happy with them.
After some searching I discovered those QFIL files wich should help me out with completely reflash my moto z.
There was only one problem, Motorola didn't release the complete QFIL rom (for economic motivations i think).
So my situation is this
I have the .elf file releated to the moto z but I can't generate the rawprogram0.xml and the patch0.xml files (both contains infos about partitions).
But why I can't generate those files?
Simply because thos files are extracted from the GPTmain0.bin files (or something like that) contained in the QFIL rom, that isn't released by motorola.
You see why I'm blaming motorola now?
1)No direct factory for oreo (or at least i didn't find it)
2)this seems like a common moto z family (moto z play too have got this) problem, I've seen other people around here with the same problem, some of them have fixed this mess but some other like me no.
3)No QFIL rom, i mean, come on guys...EVEN XIAOMI RELEASES them. I understand that if a company releases this kind of files then all the fixing center would have less crying people with broken/bricked devices but come on, it's a shame.
I'm trying to get my moto z back to live from 2 weeks now, I think it's time to stop and ask for help.
If I've said something wrong and motorola have released the QFIL rom then I'm asking sorry but i didn't find them (in this case please post a link to it below)
If someone know how to extract rawprogram0.xml and patch0.xml files from the normal 7.1.1 factory then write how here please.
EDIT(MOTO Z IS BACK):
i've restored my phone thanks to an oreo based blankflash (and thanks to @The Marionette)
here is the link and the short guide on how to do that: https://forum.xda-developers.com/showpost.php?p=76310273&postcount=183
BUT, right after the blank flash flash your phone will have the bootloader locked, and you will not be able to unlock it since there is no partition table inside it.
so how can you restore your moto z?
dowload the factory in the link and then in the terminal use this command
fastboot flash partition gpt.bin
ok now you are ready for RSD lite, flash everything trough it.
Hope your moto z is back as mine
this files?
eLaDiio said:
this files?
Click to expand...
Click to collapse
I've never noticed them. Actually I've never checked in the ota packages, so thanks maybe those files can help me even if normally there should be only one gpt main 0.bin, so i don't know how can i merge them and if it's possible
I had pretty much the same brick cause and I posted what I did to fix it on the top brick-related thread.
You should check your bootloader version and if it's below version 92.09 or something, you are fine.
And if blankflash won't flash things, it's either your cable, your PC or the fact that the bootloader in the blankflash you used has an older bootloader and you can't flash an older bootloader over the newer one.
The Marionette said:
I had pretty much the same brick cause and I posted what I did to fix it on the top brick-related thread.
You should check your bootloader version and if it's below version 92.09 or something, you are fine.
And if blankflash won't flash things, it's either your cable, your PC or the fact that the bootloader in the blankflash you used has an older bootloader and you can't flash an older bootloader over the newer one.
Click to expand...
Click to collapse
Probably i have a newer bootloader then the blank flash one, i want to make a try with the QFIL method, but do you know what should i do to build a blank flash? I mean a blank flash with a newer bootloader (the oreo one)
MasterJack1697 said:
Probably i have a newer bootloader then the blank flash one, i want to make a try with the QFIL method, but do you know what should i do to build a blank flash? I mean a blank flash with a newer bootloader (the oreo one)
Click to expand...
Click to collapse
The blankflash mentioned in my post has an Oreo bl as far as I can see.
You need the Oreo firmware( mentioned in my post) and the Oreo OTA ( link available in the Oreo thread ).
The Marionette said:
The blankflash mentioned in my post has an Oreo bl as far as I can see.
You need the Oreo firmware( mentioned in my post) and the Oreo OTA ( link available in the Oreo thread ).
Click to expand...
Click to collapse
Can you please give me te link to this blank flash? I can't find the oreo based one
MasterJack1697 said:
Can you please give me te link to this blank flash? I can't find the oreo based one
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=76453284&postcount=222
The Marionette said:
https://forum.xda-developers.com/showpost.php?p=76453284&postcount=222
Click to expand...
Click to collapse
i'll try as soon as possible thanks
eLaDiio said:
this files?
Click to expand...
Click to collapse
anyway those file are totally useless to me, or at least i don't know how to merge them in one file so i can't use them
The Marionette said:
https://forum.xda-developers.com/showpost.php?p=76453284&postcount=222
Click to expand...
Click to collapse
oh god this worked, i'll edit the thread and i'll ad the link to this blank flash
MasterJack1697 said:
oh god this worked, i'll edit the thread and i'll ad the link to this blank flash
Click to expand...
Click to collapse
Yeah, you're welcome.
Issue with partition table
Thanks for the blankflash, it did work on Moto Z. I was able to get my phone back to recovery mode.
But now i get the below message when i run "fastboot flash partition gpt.bin"
C:\adb>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (142 KB)...
OKAY [ 0.031s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.218s
My phone is still locked and i am using official stock firmware - XT1650-03_GRIFFIN_RETUS_8.0.0_OPL27.76-51_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.
If i try to run other commands, below is the error:
C:\adb>fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (7792 KB)...
OKAY [ 0.187s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Invalid partition name xbl
(bootloader) Invalid partition name cmnlib
(bootloader) Invalid partition name cmnlib64
(bootloader) Invalid partition name prov
(bootloader) Invalid partition name aboot
(bootloader) Invalid partition name keymaster
(bootloader) Invalid partition name rpm
(bootloader) Invalid partition name pmic
(bootloader) Invalid partition name hyp
(bootloader) Invalid partition name tz
(bootloader) Invalid partition name devcfg
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.281s
Please see if you can help me to overcome these errors.
Thanks.
MasterJack1697 said:
My moto z got stucked in the famous Qualcomm 9008 Emergency mode. How i bricked my moto z? Or maybe would be better say, how Motorola did brick my moto z?
Yes I'm blaming motorola for this, and i have some good motivations for this.
I'll tell you the complete story of my brick.
I was having some trouble on oreo due to a failed root, so just came back to 7.1.1 and i was trying to go to oreo again by installing ota after ota. Actually i was able to install something about 4 or 5 otas before the boom. After the last ota the phone just turned off and after a couple of hours I noticed that the phone was detected as Qualcomm 9008 in Windows device manager.
Here the story get very interesting.
In fact i firstly tried to flash many blankflash files without success, seems like my moto z wasn't happy with them.
After some searching I discovered those QFIL files wich should help me out with completely reflash my moto z.
There was only one problem, Motorola didn't release the complete QFIL rom (for economic motivations i think).
So my situation is this
I have the .elf file releated to the moto z but I can't generate the rawprogram0.xml and the patch0.xml files (both contains infos about partitions).
But why I can't generate those files?
Simply because thos files are extracted from the GPTmain0.bin files (or something like that) contained in the QFIL rom, that isn't released by motorola.
You see why I'm blaming motorola now?
1)No direct factory for oreo (or at least i didn't find it)
2)this seems like a common moto z family (moto z play too have got this) problem, I've seen other people around here with the same problem, some of them have fixed this mess but some other like me no.
3)No QFIL rom, i mean, come on guys...EVEN XIAOMI RELEASES them. I understand that if a company releases this kind of files then all the fixing center would have less crying people with broken/bricked devices but come on, it's a shame.
I'm trying to get my moto z back to live from 2 weeks now, I think it's time to stop and ask for help.
If I've said something wrong and motorola have released the QFIL rom then I'm asking sorry but i didn't find them (in this case please post a link to it below)
If someone know how to extract rawprogram0.xml and patch0.xml files from the normal 7.1.1 factory then write how here please.
EDIT(MOTO Z IS BACK):
i've restored my phone thanks to an oreo based blankflash (and thanks to @The Marionette)
here is the link and the short guide on how to do that: https://forum.xda-developers.com/showpost.php?p=76310273&postcount=183
BUT, right after the blank flash flash your phone will have the bootloader locked, and you will not be able to unlock it since there is no partition table inside it.
so how can you restore your moto z?
dowload the factory in the link and then in the terminal use this command
fastboot flash partition gpt.bin
ok now you are ready for RSD lite, flash everything trough it.
Hope your moto z is back as mine
Click to expand...
Click to collapse
bmskartik said:
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.218s
My phone is still locked and i am using official stock firmware - XT1650-03_GRIFFIN_RETUS_8.0.0_OPL27.76-51_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.
Please see if you can help me to overcome these errors.
Thanks.
Click to expand...
Click to collapse
Did you try deducing the output? I think I even mentioned this.
Sorry didnt get you. Can you come again.
If you were looking for output from getvar, here it is:
C:\Downloads\XT1650-03_GRIFFIN_RETUS_8.0.0_OPL27.76-51_cid50_subsi
dy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8996-91.09(*)
(bootloader) product: sheridan
(bootloader) board: sheridan
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 2
(bootloader) storage-type: ufs
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1CB-B0B1 FV=0800
(bootloader) ram: 4GB SAMSUNG LP4 DIE=8Gb M5=01 M6=05 M7=00 M8=08
(bootloader) cpu: MSM8996
(bootloader) serialno: 5552ed0g
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: E778AC6200000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) xbl.git: xbl.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) hyp.git: hyp.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) pmic.git: pmic.git
(bootloader) aboot.git: git=MBM-NG-V91.09-0-g7de07a7
(bootloader) qe:
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.140s
The Marionette said:
Did you try deducing the output? I think I even mentioned this.
Click to expand...
Click to collapse
bmskartik said:
Sorry didnt get you. Can you come again.
If you were looking for output from getvar, here it is:
Click to expand...
Click to collapse
https://www.merriam-webster.com/dictionary/deduce
You are trying to flash an older bootloader over your current one.
Thanks, few questions:
1. How do I find out the bootloader version of the downloaded factory image? In getvar command on my phone, I see 91.09 as my version.
(bootloader) version-bootloader: moto-msm8996-91.09(*)
2. where can I find the latest bootloader version as I have searched a lot and this is the latest image I found for moto z - XT1650-03_GRIFFIN_RETUS_8.0.0_OPL27.76-51_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
The Marionette said:
You are trying to flash an older bootloader over your current one.
Click to expand...
Click to collapse
bmskartik said:
Thanks, few questions:
1. How do I find out the bootloader version of the downloaded factory image? In getvar command on my phone, I see 91.09 as my version.
(bootloader) version-bootloader: moto-msm8996-91.09(*)
2. where can I find the latest bootloader version as I have searched a lot and this is the latest image I found for moto z - XT1650-03_GRIFFIN_RETUS_8.0.0_OPL27.76-51_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Click to expand...
Click to collapse
One page backwards, I put a link to my post, where I explained everything I did. The OTA or the whole update zip should have the newest bootloader.
Again, I mentioned everything I did there.
I did try all the 4 GPT files in the OTA - Blur_Version.27.211.6.griffin.retail.en.US but it failed at gpt_main2.bin installation. Looks like its not accepting the image:
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
FAILED <remote failure>
May be I have to wait for OPLS27.76.51-5 Stock Rom since the phone is still locked.
bmskartik said:
I did try all the 4 GPT files in the OTA - Blur_Version.27.211.6.griffin.retail.en.US but it failed at gpt_main2.bin installation. Looks like its not accepting the image:
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
FAILED <remote failure>
May be I have to wait for OPLS27.76.51-5 Stock Rom since the phone is still locked.
Click to expand...
Click to collapse
Mine did the same, now try flashing the gpt.bin from the whole Oreo firmware, not the OTA.
hi
I hope you have a great day.
I have a problem with my HTC d728w phone, after months I turned on the phone and the phone just boot into fastboot mode.
I select the "boot to bootloader" or "reboot" option but the phone comes back to fastboot mode.
I tried many ways, like: download the Flashman program to flash the ROM of the device and get the Fail message.
I tried the RUU and ADB and I get Unknows command for every command. just I can see the limited information of the device with "fastboot Getvar all".
so what I should do ? just I saw whole google links and I m so confused with this problem.
"Sorry for bad English"
(bootloader) battery-status: good
(bootloader) max-download-size: 0x8000000
(bootloader) warranty: yes
(bootloader) unlocked: no
(bootloader) secure: yes
(bootloader) version: 0.5
all: Done!!
finished. total time: 0.005s