Hi,
I have XT1635-03, when i try to unlock bootloader got following message
fastboot oem get_unlock_data
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found ...
(bootloader) Unlock data:
(bootloader) cid_get_cid_data: Version 0 datablock
(bootloader) Failed OKAY [ 0.012s] finished. total time: 0.014s
How to fix it? want to install custom rom, its chinese set without playstore, tried couple of methods to install
playstore put also they fail. any help plz?
thx
XT 1635-03 is a moto z play. Better ask in the moto z play forum.
kami2k said:
Hi,
I have XT1635-03, when i try to unlock bootloader got following message
fastboot oem get_unlock_data
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found ...
(bootloader) Unlock data:
(bootloader) cid_get_cid_data: Version 0 datablock
(bootloader) Failed OKAY [ 0.012s] finished. total time: 0.014s
How to fix it? want to install custom rom, its chinese set without playstore, tried couple of methods to install
playstore put also they fail. any help plz?
thx
Click to expand...
Click to collapse
Man, if your 1635-03 are from Gearbest or Banggod - it`s already with unlocked BL.
Just run
"fastboot oem get_unlock_data "
twice ))
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 !
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.
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
Hello everyone and thanks in advance for your help. Recently I updated the last rom cyanogen cyandelta through 13, I left the phone do the job and on my return I found the phone in bootloop!
First I tried to enter the recovery, but nothing!Then I connected the phone to the PC via Fastboot with adb but:
C:\adb>fastboot oem device-info...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.008s]
finished. total time: 0.008s
so I tried with :
C:\adb> fastboot oem unlock
...
FAILED (remote: oem unlock is disabled)
finished. total time: 0.007s
So I end up, the locked bootloader and i can't flash the rom or recovery
you have tips?
Same here...
Follow this guide.
http://forum.xda-developers.com/one...unbrick-guide-hard-bricked-t3272108?nocache=1
i try the guide but the pc (windows 10 ) want Install the qualcomm driver. So the program does not find the phone (instead with the original drivers the phone is found by adb)!
Hello guys can you help me, i cant unlock the bootloader of HTC Desire 10 PRO cos the command "fastboot flash unlocktoken Unlock_code.bin" is not working getting this message below again n again. i have checked usb debugging & OEM Unlock options too in Developer options too. i really don't understand why is this happening. Also there is not much help from this device available here on XDA or other sites too.
M:\HTCRoot>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.042s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/platform/mtk-msdc.0/11230000.msdc
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
finished. total time: 0.132s
need help guys..
here is more info if required.... guys plz help
C:\Users\Desktop\platform-tools>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_a56dj_pro_dtwl
(bootloader) version: 1.0
(bootloader) max-download-size: 1596000000
(bootloader) serialno: LC73XZ9*****
(bootloader) current-slot:
(bootloader) imei: 35**520********
(bootloader) version-main: 1.18.400.22
(bootloader) boot-mode: download
(bootloader) version-baseband: READ version-baseband ERROR
(bootloader) version-bootloader: 1.01.0000(8804eff8)
(bootloader) mid: 2PYA10000
(bootloader) cid: HTC__060
all:
finished. total time: 0.037s
Same error here. Tried Desire* and other supported devices from the HTCdev site.
Kindly help which device to choose from dev site.
D:\HTC Desire 10 PRO\ADB-Windows> fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1602400000 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 1.009s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/platform/mtk-msdc.0/11230000.msdc
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
finished. total time: 1.033s
princepavs said:
Hello guys can you help me, i cant unlock the bootloader of HTC Desire 10 PRO cos the command "fastboot flash unlocktoken Unlock_code.bin" is not working getting this message below again n again. i have checked usb debugging & OEM Unlock options too in Developer options too. i really don't understand why is this happening. Also there is not much help from this device available here on XDA or other sites too.
M:\HTCRoot>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.042s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/platform/mtk-msdc.0/11230000.msdc
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
finished. total time: 0.132s
need help guys..
Click to expand...
Click to collapse
Are you still able to unlock? I have the same issue too. Stuck here
I don't know if this one helps you too but I was unable to unlock bootloader from bootloader mode and I tried it from download mode. It was successfully done with fastboot.... command. Root? I used Magisk. only problem is it takes 5 minutes to start up every time I reboot.
carlochiefsg said:
Are you still able to unlock? I have the same issue too. Stuck here
Click to expand...
Click to collapse
naaa never worked.. so gave this phone to my dad as he's a normal android user... must say MTK processors r the worst
princepavs said:
naaa never worked.. so gave this phone to my dad as he's a normal android user... must say MTK processors r the worst
Click to expand...
Click to collapse
to be exact HTC MTK processor is the worst, HTC lied about all HTC phones boot loader is unlockable.... BS!