Hey guys i just flashed the 1.54 firmware and in the process i relocked the phone. I flashed the firmware and everything works fine, but now i can't unlock it for some reason i'm S-OFF and my CID is 11111111. I tried the command to flash the token but no luck and have even tried getting a new token.
C:\Users\haswell\Desktop\platform-tools>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1830711296 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.124s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.129s
i've also tried this (http://forum.xda-developers.com/show....php?t=2708571) however i got this:
1|[email protected]_m8:/ $ echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
lock/mmcblk0p2 bs=1 seek=33796 <
/dev/block/mmcblk0p2: cannot open for write: Permission denied
1|[email protected]_m8:/ $
C:\Users\haswell\Desktop\platform-tools>
i also realized that my recovery is no longer working as well as superSU... please someone help me
itzjonjon69 said:
Hey guys i just flashed the 1.54 firmware and in the process i relocked the phone. I flashed the firmware and everything works fine, but now i can't unlock it for some reason i'm S-OFF and my CID is 11111111. I tried the command to flash the token but no luck and have even tried getting a new token.
C:\Users\haswell\Desktop\platform-tools>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1830711296 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.124s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.129s
i've also tried this (http://forum.xda-developers.com/show....php?t=2708571) however i got this:
1|[email protected]_m8:/ $ echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
lock/mmcblk0p2 bs=1 seek=33796 <
/dev/block/mmcblk0p2: cannot open for write: Permission denied
1|[email protected]_m8:/ $
C:\Users\haswell\Desktop\platform-tools>
i also realized that my recovery is no longer working as well as superSU... please someone help me
Click to expand...
Click to collapse
You only need to enter the token on your original unlock. After that, you can lock unlock as much as you want, no token needed
fastboot oem unlock
When you flash the new firmware, it flashed your recovery and took root, simply download twrp or whatever you are using and
fastboot flash recovery twrp.img
go into recovery and flash supersu.zip to regain root.
Also for future notice, you do NOT have to lock boot loader to flash any firmware, rom, kernel, ruu on this phone if you are soff. I don't care what the guide says. Just remember you have to be soff and super cid for other firmwares. You can even downgrade firmwares, hboots, etc… NEVER flash cdma firmware, hboot, recovery!
fixed!!! forum member russellvone just SAVED my ass. So what he did was he had me download this file for my ATT M8
https://mega.co.nz/#!NUURzC5T!tCjG3n...c6zRAwOPZ8T2PI and told me to rename it 0P6BIMG.zip and place it in my adb fastboot folder
then he told me to run these commands:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip 0P6BIMG.zip
fastboot reboot
then once everything was done we ran the commands from this thread (http://forum.xda-developers.com/showthread.php?t=2708571) and voila! i'm once again unlocked! He explained to me that when i tried to run the unlock commands before it didn't work because i had the secure boot.img and what he had me flash was a file he created which made it unsecure so i could run the command. HUGE HUGE props to this guy.
ANYONE, please help me i exactly got the same problem.....
And the link is decrypted Please help !!
iceman667 said:
ANYONE, please help me i exactly got the same problem.....
And the link is decrypted Please help !!
Click to expand...
Click to collapse
DO NOT zombie a 6 month old thread and then just say "I got the same problem".
I'm almost completely certain you DO NOT have the exact same problem. But since you gave zero details about your own issue, its impossible to know what is different and what is the same; therefore, also impossible to give any meaningful help.
AT&T variant (this is the AT&T versions specific forum section)? S-off? 1.54 firmware? You did the EXACT same things the OP did?
Answer to most or all the above is probably NO. So post all the relevant details of your phone and what you did to it, if you want help. Also, you probably need to post to the "international" forum instead of here, also if you do not have the AT&T version (based on your location).
Related
Well, I guess I unintentionally softbricked my Hero...
So the story:
I downloaded via OTA the update. And i tried to install, but in the middle the install just stopped, and... stood still for a long long time... ok, battery ran out and i plugged the charger and tried to turn on ... annnd stucked at HERO sign...
i tried hard reset and nothing.. im trying that with the SDK and CMD and the fastboot devices doesn't show anything.
I tried to boot one of millions of customed ROMs and nothing, i guess i had to root earlier, or something /noob here.
I kinda ran out of options here and i don't know what to do...
Could you guys please help me out?
Taiwanese version of HTC Hero here.
yep, and i'm kinda desperate here too.
---
HERO CVT SHIP S-ON
HBOOT-1.76.0007 (HERO10000)
MICROP-010f
TOUCH PANEL-SYN0104
RADIO-6.35.08.29
Can you force into hboot/fastboot via holding volume down and power for a bit from cold start?
-------------------------------------
Sent via the XDA Tapatalk App
Yes, I Can access HBoot and fastboot...
aaaaaand i found my device at the fastboot devices.
HTxxxxxxxxxx64
Excellent then you should now be able to redo things ... let us know
OK, accessed the hero... then, tried to apply the update and...
E:Failure at line 11: run_program PACKAGE:checkspace -f /data 26214400 "ro.build.fingerprint=chunghwa/htc_hero/hero/hero:1.5CUPCAKE" FOTAERRORMESSAGES
actually i don't know what to do... :/
Try this ... http://forum.xda-developers.com/showpost.php?p=6714023&postcount=14
Basically go back into fastboot and try to install the official 1.5 (which will fail) but the process clears something up and allowed another member here to reflash cleanly ...
Try to wipe your data and then install the next ROM, i had the same problem
I do not think he has rooted or installed a modded recovery image if I read his first post correctly
i guess i had to root earlier, or something /noob here.
Click to expand...
Click to collapse
Yeah, i didn't root or anything... and i tried the other dude footsteps... and... blank, nothing...
and waiting for HTC Response team says something...
tried installing official rom, nothing.
tried updating the official update, also nothing.
tried wipe data, same thing.
well, i guess i have a new brick :/
If you can get it to fastboot ok and open the conversation, there must be something that can be done.
According to the definitive fastboot docs (http://android-dls.com/wiki/index.php?title=Fastboot) there might be a few options to try ...
HTML:
<pre>usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall 'flash boot' + 'flash system'
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline</pre>
Perhaps the -w to clear those areas might do it ...
Alternatively, I _believe_ you could flash the 1.62 recovery image to the phone in fastboot and then wipe from in there, or flash an 'update.zip' style rom from in here as well ...
Good luck, someone more knowledgeable than I may have other ideas ...
Broken Root???????
WELLLLLL...
I'm not sure how I did it, but I cannot open my custom recovery image. Happened a couple weeks after I flashed a new image. When I tried to apply an update.zip, the image froze at the 'opening update package' stage. I tried multiple roms and wipes to fix the problem, but none worked.
I've flashed multiple images through the terminal, and cannot open any. I've tried using flashrec again, but command line error always pops up. The error in fastboot when trying to load the image is as follows "Wrong or no image!"
This error reoccurs several times as the image recovery is attemped to be retrieved several times.
My rom is Darchdroid 262, and works 100%.
chachi said:
If you can get it to fastboot ok and open the conversation, there must be something that can be done.
According to the definitive fastboot docs (http://android-dls.com/wiki/index.php?title=Fastboot) there might be a few options to try ...
Click to expand...
Click to collapse
I was having a play with those commands yesterday to see if it was possible to restore to a ROM through fastboot but had no luck unfortunately.
chachi said:
If you can get it to fastboot ok and open the conversation, there must be something that can be done.
According to the definitive fastboot docs there might be a few options to try ...
HTML:
<pre>usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall 'flash boot' + 'flash system'
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline</pre>
Perhaps the -w to clear those areas might do it ...
Alternatively, I _believe_ you could flash the 1.62 recovery image to the phone in fastboot and then wipe from in there, or flash an 'update.zip' style rom from in here as well ...
Good luck, someone more knowledgeable than I may have other ideas ...
Click to expand...
Click to collapse
tried the fastboot -w and... not allow. I will try with the gold card.
Yeah, i'll try the 1.62, but the ADB don't find my device.
Try this,...
Go into fastboot on your phone.
Open CMD and type the following, obviously you will have to change slightly depending on where you extracted the sdk to.
cd c:\sdk\tools
fastboot oem rebootRUU
Then try running one of the 1.5 RUU .exe files on your pc/lappy.
ddotpatel said:
Try this,...
Go into fastboot on your phone.
Open CMD and type the following, obviously you will have to change slightly depending on where you extracted the sdk to.
cd c:\sdk\tools
fastboot oem rebootRUU
Then try running one of the 1.5 RUU .exe files on your pc/lappy.
Click to expand...
Click to collapse
i tried running one of the southeast asia RUU, the 2.73.728.5 file yesterday, and... nothing show up. Sayin' ive got to use the correct one.
The thing i thinked about is to rewrite the checksum in the update (the taiwanese 1.5 to 2.1 the one i've tried to update), verifying if its cupcake (in the fact that the update stopped in the middle), so if delete the verification code, it will continue the installation, and hopefuly, boot correctly.
-
update: ok trying to update again, then he says:
Error in checkspace (Status 256)
run_program PACKAGE:checkspace -f /data 26214400 "ro.build.fingerprint=chunghwa/htc_hero/hero/hero:1.5/CUPCAKE" FOTAERRORMESSAGES
Instalation aborted.
Click to expand...
Click to collapse
OK,... Now this,...
cd c:\sdk\tools
fastboot oem rebootRUU
fastboot erase cache
then try running the RUU again....... ?
Customer ID error... can't it erase the previous update?
it hasn't the original taiwanese RUU available?
the 2.73.751.13 file?
Customer ID Error?.... Ahaaaa,..... We might be on to something. Try with a goldcard now.
Use an old RUU with 1.5, not the new 2.1 ROM.
If you need to know how to make a goldcard follow BTDAGs guide linked in my signature.
ddotpatel said:
Customer ID Error?.... Ahaaaa,..... We might be on to something. Try with a goldcard now.
Use an old RUU with 1.5, not the new 2.1 ROM.
If you need to know how to make a goldcard follow BTDAGs guide linked in my signature.
Click to expand...
Click to collapse
This is beginning to sound like a happy ending is more than a remote possibility now
chachi said:
This is beginning to sound like a happy ending is more than a remote possibility now
Click to expand...
Click to collapse
Don't speak too soon, we might not be on to a winner just yet,.... Fingers crossed.
Hi
I got my HTC One replaced because of some screen issue . On my earlier phone i had the bootloader unlocked and had Trickdroid running great.
I got the replacement and unlocked the bootloader and flash CMW recovery , but i am not able to boot into recovery i tried both the AIO kit and
power + up and power + vold down the phone just keeps rebooting doesnt ever going into the recovery . Is there something i am missing ?
dint have this issues first time aroung on my other HTC ONe.
any help is appreciated
THanks
if i flash the stock att recovery and reboot to recovery , i am able to boot into recovery. this is strange
i flashed back CWM and see that it again keeps rebooting . i tried the perm root tool and this is the error i am gettign
E:\HTC_One\One_M7_All-In-One_Kit_v1.0\data>adb shell "echo 'boot-recovery ' > /c
ache/recovery/command"
/system/bin/sh: can't create /cache/recovery/command: Permission denied
E:\HTC_One\One_M7_All-In-One_Kit_v1.0\data>adb shell "echo '--update_package=SDC
ARD:SuperSU.zip' >> /cache/recovery/command"
/system/bin/sh: can't create /cache/recovery/command: Permission denied
E:\HTC_One\One_M7_All-In-One_Kit_v1.0\data>adb shell "reboot recovery"
reboot: Operation not permitted
E:\HTC_One\One_M7_All-In-One_Kit_v1.0\data>pause
Press any key to continue . . .
event tried
fastboot boot Recoveries\TWRP.img
it still reboots the phone
assuming flashing the recovery was successful (fastboot flash recovery recovery.img), have you tried fastboot erase cache ?
what is the output of those two commands when running them from your pc's cmd prompt?
colmustrd said:
assuming flashing the recovery was successful (fastboot flash recovery recovery.img), have you tried fastboot erase cache ?
what is the output of those two commands when running them from your pc's cmd prompt?
Click to expand...
Click to collapse
E:\HTC_One\One_M7_All-In-One_Kit_v1.0\data>fastboot flash recovery Recoveries\TW
RP.img
sending 'recovery' (7916 KB)...
OKAY [ 1.183s]
writing 'recovery'...
OKAY [ 0.640s]
finished. total time: 1.829s
E:\HTC_One\One_M7_All-In-One_Kit_v1.0\data>fastboot erase cache
erasing 'cache'...
OKAY [ 0.054s]
finished. total time: 0.057s
one thing i notice is in the bootloader mode it just says unlocked , but on my earlier HTC One it use to say both
Tampered and unlocked does that matter ?
i even tried to relock it and unlock it again hoping it would say tampered.
Thanks
anilkuj said:
one thing i notice is in the bootloader mode it just says unlocked , but on my earlier HTC One it use to say both
Tampered and unlocked does that matter ?
i even tried to relock it and unlock it again hoping it would say tampered.
Thanks
Click to expand...
Click to collapse
unlocked is for your bootloader, and tampered I dont remember exactly if it showed up after I flashed the new recovery or later (after rooting it).
I would try the following:
unlock your bootloader again
erase the cache again: fastboot erase cache
attempt to flash the recovery one more time: fastboot flash recovery recovery.img
reboot via adb: adb reboot recovery
thanks for your help
i was trying this and finally got it working
http://forum.xda-developers.com/showpost.php?p=40516203&postcount=40
anilkuj said:
thanks for your help
i was trying this and finally got it working
http://forum.xda-developers.com/showpost.php?p=40516203&postcount=40
Click to expand...
Click to collapse
you are very welcome, glad you were able to get the phone into recovery.
Hey folks,
I'm trying to install a recovery image using fastboot, as per the directions presented here:
http://wiki.cyanogenmod.org/w/Install_CM_for_fireball
When I try flashing the recovery, I get the following error message:
Code:
sudo fastboot flash recovery recovery-clockwork-6.0.4.6-fireball.img
sending 'recovery' (7784 KB)...
OKAY [ 1.117s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.149s
I was able to obtain S-OFF following the directions presented in this thread:
http://forum.xda-developers.com/showthread.php?t=2664460
but I am now currently in "relocked" state because I followed step 5 and tried running DirtyRacun.
Phone: HTC incredible 4g lte.
hboot: 1.15.0000
radio: 1.53.06.0919
OpenDSP-v29.1.0.45.0622
Thanks in advance!
in other news ...
My phone is in an unusable state. I still have access to the bootloader, and when it's plugged into my computer, I have access to it through adb, but otherwise, I can't send or receive phone calls from it.
stringedonbass said:
My phone is in an unusable state. I still have access to the bootloader, and when it's plugged into my computer, I have access to it through adb, but otherwise, I can't send or receive phone calls from it.
Click to expand...
Click to collapse
Apparently shutting down and pulling the battery "fixes" that problem.
Step 5 was not to run dirty racoon it was to flash the engineering hboot from the DirtyRacun webpage, but with S-off you should still be able to flash the hboot and recovery.
I find this page useful when I am working in ADB to keep the ideas fresh. http://forum.xda-developers.com/showthread.php?t=2141817
stringedonbass said:
Hey folks,
I'm trying to install a recovery image using fastboot, as per the directions presented here:
http://wiki.cyanogenmod.org/w/Install_CM_for_fireball
When I try flashing the recovery, I get the following error message:
Code:
sudo fastboot flash recovery recovery-clockwork-6.0.4.6-fireball.img
sending 'recovery' (7784 KB)...
OKAY [ 1.117s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.149s
I was able to obtain S-OFF following the directions presented in this thread:
http://forum.xda-developers.com/showthread.php?t=2664460
but I am now currently in "relocked" state because I followed step 5 and tried running DirtyRacun.
Phone: HTC incredible 4g lte.
hboot: 1.15.0000
radio: 1.53.06.0919
OpenDSP-v29.1.0.45.0622
Thanks in advance!
Click to expand...
Click to collapse
Re: adb guide
wmuflyer said:
Step 5 was not to run dirty racoon it was to flash the engineering hboot from the DirtyRacun webpage, but with S-off you should still be able to flash the hboot and recovery.
I find this page useful when I am working in ADB to keep the ideas fresh. http://forum.xda-developers.com/showthread.php?t=2141817
Click to expand...
Click to collapse
That's a nice guide on the Android Debug Bridge (abd). As a side note, I was pleased to find that fastboot and adb can be found in Ubuntu's repositories.
Update: flashed DirtyRacun's HBOOT
My phone now says
-- DirtyRacun --
at the top of the bootloader. No need to "unlocking" the phone because it was already in S-OFF state. After downloading the HBOOT file from unlimited's fireball website, I typed these commands, also available from their website:
Code:
sudo ./fastboot erase cache
sudo ./fastboot oem rebootRUU
sudo ./fastboot flash zip [file name]
sudo ./fastboot reboot
Happily rooted with CyanogenMOD installed
I'm happily rooted and have CyanogenMOD up and running.
After flashing the engineering hboot onto my phone using unlimited's directions, I was able to install ClockworkMod Recovery for fireball following the directions posted on their website.
Code:
sudo fastboot flash recovery recovery-clockwork-6.0.4.6-fireball.img
sending 'recovery' (7784 KB)...
OKAY [ 1.141s]
writing 'recovery'...
OKAY [ 2.129s]
finished. total time: 3.271s
I then was able to install CyanogenMod from recovery like "clockwork". Of course, "abd reboot-bootloader" is much faster than the crazy key combinations they ask you do to. When asked to install from sdcard, there were two locations to look at.
Cheers everyone! :victory:
Yesterday afternoon I upgraded my C6802/Z Ultra to 14.4.A.0.108 aka 4.4.4 and to persuade the Sony PC Companion program on windows to download the update, I used flashtool to lock my bootloader.
I've used the phone happily all day but I want to root it so I can use Titanium Backup Root/Pro, and hack the platform.xml file so as to allow full use of the microSDHC card.
I went to the service menu with the *#*#7378423#*#* and it says my bootloader is unlockable. I then put the phone into fastboot mode and ran the unlock sequence, but it failed the first time and reported device already unlocked.
I am using the tools from the full Android SDK
Code:
$ ./fastboot -i 0x0fce getvar version
< waiting for device >
version: 0.5
finished. total time: 0.003s
$ ./fastboot -i 0x0fce oem unlock 0xXXXXXXXXXXXXXXXXXX
...
FAILED (remote: Command did not succeed)
finished. total time: 0.018s
$ ./fastboot -i 0x0fce oem unlock 0xXXXXXXXXXXXXXXXXXX
...
FAILED (remote: Device is already rooted)
finished. total time: 0.004s
$ ./fastboot -i 0x0fce oem unlock 0xXXXXXXXXXXXXXXXXXX
...
FAILED (remote: Device is already rooted)
finished. total time: 0.004s
So then I tried to flash Jackie's 108 Dual Recovery kernel and it failed; I tried again as root just to make sure:
Code:
# ./fastboot flash boot ~/download/android/sony/xperia_z_ultra/C68xx_kernel_108_DualRec_Jackie099.bin
sending 'boot' (17728 KB)...
OKAY [ 0.557s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.560s
I get the same result if I use FlashTool's built-in tools. I have tweaked the phone's configuration to allow/disallow USB ADB debugging, allow/disallow side-loading, verification of apps etc etc, makes no difference.
I suspect that the phone is falsely reporting its bootloader is already unlocked, but where do I go from here?
thanks for any ideas
Paul
first off you may have lost your DRM keys by not doing a TA backup before unlocking the bootloader.
try and flash doomkernel's boot.img and see if that works? (unpack the zip)
I think I can remember someone not beinf able to flash jackie's .bin but doomlord's boot.img worked?
blueether said:
first off you may have lost your DRM keys by not doing a TA backup before unlocking the bootloader.
try and flash doomkernel's boot.img and see if that works? (unpack the zip)
I think I can remember someone not beinf able to flash jackie's .bin but doomlord's boot.img worked?
Click to expand...
Click to collapse
thanks, I'll give the doomkernel a go.
I lost my DRM keys the same day I received my XZU.. what you've never used you don't miss
Looks like the problem that I had:
http://forum.xda-developers.com/xperia-z-ultra/help/reunlocking-bootloader-error-t2808395
Everytime I type the command 'fastboot oem unlock', the screen says;
OKAY [ 0.002s]
finished. total time: 0.002s
but then when I want to flash a recovery it says;
target reported max download size of 1073741824 bytes
sending 'recovery' (15482 KB)...
OKAY [ 0.498s]
writing 'recovery'...
FAILED (remote: Device not unlocked cannot flash or erase)<<< Why does this happen? -_-
finished. total time: 0.501s
Anybody has a solution for this?
Have you tried just flashing stock recovery? Does it say that for everything you try and flash? A lot of people are trying these shortcuts to try and upgrade bootloader. Though most can work the safest bet is to flash original stock recovery and upgrade from there. You might be looking at going through the hard brick guide.
seems like you locked the bootloader while you are rooted...iam stack on same step too...
Exodusche said:
Have you tried just flashing stock recovery? Does it say that for everything you try and flash? A lot of people are trying these shortcuts to try and upgrade bootloader. Though most can work the safest bet is to flash original stock recovery and upgrade from there. You might be looking at going through the hard brick guide.
Click to expand...
Click to collapse
But everything else works. And yeah, I did try flashing the stock recovery too
Fastboot oem unlock>fastboot reboot>doesn't ask about wiping
I've followed every tutorial they all say that after requesting oem unlock, you can verify the unlock was successful with fastboot oem devices-info> device tampered-false, device unlock-true, then fastboot reboot> system reboot, but it does NOT ask to wipe the data. Am I missing something?
Ubuntu_noobi said:
I've followed every tutorial they all say that after requesting oem unlock, you can verify the unlock was successful with fastboot oem devices-info> device tampered-false, device unlock-true, then fastboot reboot> system reboot, but it does NOT ask to wipe the data. Am I missing something?
Click to expand...
Click to collapse
Not necessarly.
If it 's device unlock-true , you're OK. If not...