Hello all,
I'm hoping someone can tell me what I'm doing wrong.
I went to HTCdev and got the unlock code emailed but this is happening when i try to unlock,I put the code in the same folder as the fastboot...
C:\Joey\Unlock Tools>fastboot oem get_identifier_token
...
(bootloader)
(bootloader) < Please cut following message >
(bootloader) <<<< Identifier Token Start >>>>
(bootloader) 09676CC238975AE58745ED43A1A50C8A
(bootloader) ECF90A6E24B47051377B15F0178DF92C
(bootloader) A393503ADCC8606FC14ED1761E2456F6
(bootloader) F57F798477728947A8B7E1EBD8C343BA
(bootloader) 3966E2A81DF8844D9470FF08C7F75B60
(bootloader) AE0F848DE98EA5CE3D0C4341902723C5
(bootloader) F773CAAACE0D1F8E84BCB246BCC410E3
(bootloader) 02670551F637FB8AD6E4783FDDABD8D4
(bootloader) CAC4613F93ABB73203D1EB8552BA705F
(bootloader) 9417AC2E0E0DFD82F424EB0141A0E47F
(bootloader) B1CDF5791CD1F196A2B5282143FCFB1E
(bootloader) 57453E81BFC316B3D372F6DD74D65FA6
(bootloader) F6DB2C323BCB1BFE4040B59C10B4FC90
(bootloader) 77CFE117D6670229E2FF6C64C6125601
(bootloader) C7671A07B7034C492C85213FCCDC0DD3
(bootloader) A019ADDF0F220049A7404264BAE50571
(bootloader) <<<<< Identifier Token End >>>>>
OKAY [ 0.063s]
finished. total time: 0.063s
C:\Joey\Unlock Tools>fastboot flash unlocktoken Unlock_code.bin
error: cannot load 'Unlock_code.bin'
Idea
I don't see the part where you got an email with the unlock code from HTC.
You have to submit that text to HTC, get an email with the file, put the file in the same folder as Fastboot, and then apply it.
Thanks for the reply,I got the code emailed and downloaded.I put it in the folder with the fastboot and got the error...I have no Idea what I did wrong.
Don't reboot your phone...also...male sure the phone is still in fastboot obviously.
Sent from my ADR6425LVW using XDA App
Thanks for your reply also.
I got it unlocked I had to change the folder name,I guess it wouldn't work cause unlock was in the folder name as soon as I changed it and entered the path it went though.. so I'm guessing that was the problem.
shooter_454 said:
Thanks for your reply also.
I got it unlocked I had to change the folder name,I guess it wouldn't work cause unlock was in the folder name as soon as I changed it and entered the path it went though.. so I'm guessing that was the problem.
Click to expand...
Click to collapse
Glad you got it figured out man!
Use fastboot for kernels, lol, I wish I had and almost bricked my phone.
Related
Rogers said the new HTC EVO 3D bootloader would come unlocked, yet, on the bootloader screen, I get this:
Code:
*** LOCKED ***
SHOOTER_U PVT SHIP S-ON RL
HBOOT-1.49.0008
eMMC-boot
Jul 15 2011,14:39:25
Does't look unlocked to me...
Has anyone been able to successfully unlock/root a GSM EVO 3D yet?
Don't take Social Media's "word" as any sort of truth, they just relay information.
HTC hasn't released the OTA yet to unlock the bootloader but they will.
This actually came from a Rogers rep on a Rogers website: http://mobilesyrup.com/2011/07/18/rogers-yes-our-htc-evo-3d-will-have-an-unlocked-bootloader/
Here's the actual Rogers site: http://redboard.rogers.com/2011/eve...oducing-the-htc-evo-3d-and-the-lg-optimus-3d/
Yeah I was hoping it would come unlocked too but it looks like we're going to have to wait.
Sent from my HTC EVO 3D using Tapatalk
Turge said:
This actually came from a Rogers rep on a Rogers website: http://mobilesyrup.com/2011/07/18/rogers-yes-our-htc-evo-3d-will-have-an-unlocked-bootloader/
Here's the actual Rogers site: http://redboard.rogers.com/2011/eve...oducing-the-htc-evo-3d-and-the-lg-optimus-3d/
Click to expand...
Click to collapse
I know where your information came from.
I told you, never take Social Media's information as any form of "truth". Anything they post is still bound by the legal disclaimer on all Rogers websites that their information is subject to change and may not be accurate. Do you really expect a journalist to know anything about a Bootloader? All they do is spew information they're told, and do a half assed job at best with that.
That being said, the bootloader will get unlocked, likely sooner by Revolutionary than by HTC themselves.
Don't feel bad, the European EVO3D users are in the same boat.
It actually shows "locked" in the bootloader? Just out of curiousity, can someone check to see what fastboot commands are available? You can find out by using fastboot oem ? (with the question mark) or fastboot oem h while it is in fastboot mode.
xHausx said:
It actually shows "locked" in the bootloader? Just out of curiousity, can someone check to see what fastboot commands are available? You can find out by using fastboot oem ? (with the question mark) or fastboot oem h while it is in fastboot mode.
Click to expand...
Click to collapse
Here ya go:
(bootloader) command list
(bootloader) get_identifier_token
(bootloader) checkSbl1
(bootloader) checkHWSecurity
(bootloader) keytest
(bootloader) heap
(bootloader) boot
(bootloader) reset
(bootloader) powerdown
(bootloader) rebootRUU
(bootloader) heap_test
(bootloader) rtask
(bootloader) task
(bootloader) enableqxdm
(bootloader) gencheckpt
(bootloader) readpid
(bootloader) writepid
(bootloader) readcid
(bootloader) writecid
(bootloader) readimei
(bootloader) writeimei
(bootloader) readsecureflag
(bootloader) writesecureflag
(bootloader) lock
(bootloader) list_partition_emmc
(bootloader) load_emmc
(bootloader) check_emmc
(bootloader) check_emmc_mid
(bootloader) read_mmc
(bootloader) load_modem_emmc
(bootloader) get_wp_info_emmc
(bootloader) send_wp_info_emmc
(bootloader) get_ext_csd_emmc
(bootloader) get_sector_info_emmc
They must have just added that get_identifier_token command, I don't remember seeing it in the 1.30 hboot and the it's not in the eng hboot either.
Can you give it a try to see what it does?
Code:
fastboot oem writesecureflag 0
fastboot oem get_identifier_token ?
xHausx said:
They must have just added that get_identifier_token command, I don't remember seeing it in the 1.30 hboot and the it's not in the eng hboot either.
Can you give it a try to see what it does?
Code:
fastboot oem writesecureflag 0
fastboot oem get_identifier_token ?
Click to expand...
Click to collapse
From the looks of it, a gold card might be needed?
Code:
fastboot oem writesecureflag 0
...
(bootloader) vreg_set: request is duplicated id 14
(bootloader) shooter_u_init_sd, SD card power on ok
(bootloader) sdcc_init_memory_device done
(bootloader) [FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
(bootloader) [JAVACARD_ERR] SMART_IO.CRD cann't find
(bootloader) writesecureflag: Permission denied, value 1
OKAY [ 1.084s]
finished. total time: 1.086s
fastboot oem get_identifier_token ?
...
(bootloader)
(bootloader) < Please cut following message >
(bootloader) <<<< Identifier Token Start >>>>
(bootloader) 979CAC9BC47B6A2DA6164C92F581BE6C
(bootloader) D48C11BF91C56DF93EB96ABBFDC0B557
(bootloader) 5C3794863CB29EE44BF2BDA4B684ECDC
(bootloader) D091FAA3D9373B838B81138D5E930523
(bootloader) 41343BCE21D915B2926BD3E20F6F62CB
(bootloader) D22B9904764499498AE78DC6880CBD81
(bootloader) 6A337E89DDB34F9970F3CCB3E042FD87
(bootloader) A89849D1FDBE1DAA7E63D979E43B2849
(bootloader) F4D1E2207BEEEE481E4AEF3DF8A569D1
(bootloader) 75C66DAA8B41FA6812A462A0F12E469E
(bootloader) F505A0B8B986E40745A81633FC287B2A
(bootloader) 7C975C2B54AE7FF86002FA119B4ACD66
(bootloader) DC92B98D6C1636F71EC23FBC5FFD153B
(bootloader) 8EEFB5A7A9BF12448EA5234CD62B43B7
(bootloader) 1F97385D6A6D890BBDD3ED1673AB2EBD
(bootloader) FE90D203A4F1EAF01FAC3FC5A4A06627
(bootloader) <<<<< Identifier Token End >>>>>
OKAY [ 0.073s]
finished. total time: 0.075s
The locked part it says must be for world unlocked. To use any sim.
They updated the RedBoard yesterday:
Rogers_Chris says: August 10, 2011 at 5:04 pm
Hi Andy,
When we announced the HTC EVO 3D coming to Rogers, we communicated that the device would launch with an unlocked bootloader (as Katie wrote above). Our apologies – we have since learned that the device will not be shipped unlocked. For more information on webtools, please visit the HTC website ww.HTCdev.com. If you decide to make a change, please note that some actions may void warranties.
Mnemoch said:
They updated the RedBoard yesterday:
Rogers_Chris says: August 10, 2011 at 5:04 pm
Hi Andy,
When we announced the HTC EVO 3D coming to Rogers, we communicated that the device would launch with an unlocked bootloader (as Katie wrote above). Our apologies – we have since learned that the device will not be shipped unlocked. For more information on webtools, please visit the HTC website ww.HTCdev.com. If you decide to make a change, please note that some actions may void warranties.
Click to expand...
Click to collapse
Looks like June 24th all over again.
My "DU4L C0R3 SH00T3R" shot you down in 3D! -Security Off-
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!!
I'm trying to RUU back to stock DNA on Verizon but it keeps telling me there is an error
it tells me "ERROR [158]: Image error"
am i missing something?
kreep22 said:
I'm trying to RUU back to stock DNA on Verizon but it keeps telling me there is an error
it tells me "ERROR [158]: Image error"
am i missing something?
Click to expand...
Click to collapse
Did you lock the phone again first, if you had previously unlocked/rooted?
GreginNH said:
Did you lock the phone again first, if you had previously unlocked/rooted?
Click to expand...
Click to collapse
yes, it's showing relocked status and it wont let me do anything just takes me to the bootloader no matter what i do
kreep22 said:
yes, it's showing relocked status and it wont let me do anything just takes me to the bootloader no matter what i do
Click to expand...
Click to collapse
Right Click and Run as Admin try that... make sure you are in fastboot usb mode as well or redownload the RUU maybe you got a bad DL
.torrented said:
Right Click and Run as Admin try that... make sure you are in fastboot usb mode as well or redownload the RUU maybe you got a bad DL
Click to expand...
Click to collapse
I tried to Run as Admin and no luck tells me the same error message, i've done it before with the same ruu that i am trying with now but idk what is going on, am i bricked?
kreep22 said:
I tried to Run as Admin and no luck tells me the same error message, i've done it before with the same ruu that i am trying with now but idk what is going on, am i bricked?
Click to expand...
Click to collapse
does your phone boot to android at all? or recovery
.torrented said:
does your phone boot to android at all? or recovery
Click to expand...
Click to collapse
I got it wprking, just re unlocked and rom came back on. Thank u
Sent from my HTC6435LVW using xda app-developers app
kreep22 said:
I got it wprking, just re unlocked and rom came back on. Thank u
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
How did you do it can you please explain?
Tried going back to stock settings
Relocked m errory phone s- off still the ruu wizard keeps giving me error 158? Flashed hboot with no luck. how do I unlock again like I said still s-off
wondering how u unlocked again
chris1569810 said:
How did you do it can you please explain?
Click to expand...
Click to collapse
I'm in the same situation
You flashed the stock hboot with no problems? Which hboot?
Help! I have a similar problem
GreginNH said:
Did you lock the phone again first, if you had previously unlocked/rooted?
Click to expand...
Click to collapse
I used moonshine S-OFF to root my DNA. I dont know how to get back to the stock locked hboot. and i keep getting that error 158.
any recommendations?
madc321 said:
I used moonshine S-OFF to root my DNA. I dont know how to get back to the stock locked hboot. and i keep getting that error 158.
any recommendations?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2293919
finanandroid said:
http://forum.xda-developers.com/showthread.php?t=2293919
Click to expand...
Click to collapse
Thanks but I tried that with no luck. I was able to flash viper venom though. no idea why the bamf rom did not work.
Solution?
So what ended up being the solution for the Error 158 and being stuck at Fastboot? I can't seem to find one that will work. Check my thread in Q & A: http://forum.xda-developers.com/showthread.php?t=2649525
Before running ruu u should boot into fastboot and make u see fastboot usb then start ruu, the error is because ur device can't boot into bootloader to finish with ruu
Sent from my HTC6435LVW using xda app-developers app
jaymazz13 said:
Before running ruu u should boot into fastboot and make u see fastboot usb then start ruu, the error is because ur device can't boot into bootloader to finish with ruu
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I just spent 20 minutes freaking out. I kept getting the 158 error over and over. I fastboot flashed the locked bootloader file and it said RELOCKED, but still errored out.
I was on the ENG hboot at the time and fastboot flashed the vanilla 3.06 hboot and this time the RUU went through.
Hopefully this will help somebody else out.
sasquatch1 said:
I just spent 20 minutes freaking out. I kept getting the 158 error over and over. I fastboot flashed the locked bootloader file and it said RELOCKED, but still errored out.
I was on the ENG hboot at the time and fastboot flashed the vanilla 3.06 hboot and this time the RUU went through.
Hopefully this will help somebody else out.
Click to expand...
Click to collapse
How can I do this if phone was fully stock before recieving an OTA via Verizon and now wont get past white HTC screen?
I am s-on...I cant flash anything...and RUU keeps failing.
---------- Post added at 04:56 PM ---------- Previous post was at 04:51 PM ----------
C:\>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.01.01.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.09.605.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA2BPS501936
(bootloader) imei: 990000671822338
(bootloader) meid: 99000067182233
(bootloader) product: monarudo
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PL8320000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4192mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ae8bbb39
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
DuceTheTruth said:
How can I do this if phone was fully stock before recieving an OTA via Verizon and now wont get past white HTC screen?
I am s-on...I cant flash anything...and RUU keeps failing.
---------- Post added at 04:56 PM ---------- Previous post was at 04:51 PM ----------
C:\>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.01.01.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.09.605.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA2BPS501936
(bootloader) imei: 990000671822338
(bootloader) meid: 99000067182233
(bootloader) product: monarudo
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PL8320000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4192mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ae8bbb39
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
By above post i could understand that your phone is S-On and LOCKED.
If that was the case, How your phone got updated to boot 1.57.0000?
Have you flashed anything (firmware) in fastboot mode?
If yes, You have very less chance to get the phone working unless its JTAGed.
First of all thank you for your reply...
This phone was all stock when I received it in this state...never been rooted ...unlocked or anything....
All I know is that after accepting an OTA update from vzw the phone never booted up fully again...
Now I did try the flashing instructions from .torrented but everything I do fails...
I get "remote 22 loading zip info fail"...
I also get " remote 12 signature verify fail"....
Sent from my SPH-L710 using XDA Free mobile app
---------- Post added at 06:34 PM ---------- Previous post was at 06:19 PM ----------
DuceTheTruth said:
First of all thank you for your reply...
This phone was all stock when I received it in this state...never been rooted ...unlocked or anything....
All I know is that after accepting an OTA update from vzw the phone never booted up fully again...
Now I did try the flashing instructions from .torrented but everything I do fails...
I get "remote 22 loading zip info fail"...
I also get " remote 12 signature verify fail"....
Sent from my SPH-L710 using XDA Free mobile app
Click to expand...
Click to collapse
C:\adb>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.073s]
finished. total time: 0.073s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.038s]
finished. total time: 0.039s
C:\adb>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.041s]
finished. total time: 0.042s
C:\adb>fastboot flash zip PL83IMG_3.06_Recovery.zip
target reported max download size of 1514139648 bytes
sending 'zip' (11248 KB)...
OKAY [ 1.343s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 2.451s
C:\adb>fastboot flash zip PL83IMG_1.15_hboot
error: cannot open 'PL83IMG_1.15_hboot'
C:\adb>fastboot flash zip PL83IMG_1.15_hboot.zip
target reported max download size of 1514139648 bytes
sending 'zip' (434 KB)...
OKAY [ 0.202s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 0.252s
C:\adb>fastboot flash recovery PL83IMG_3.06_Recovery.zip
target reported max download size of 1514139648 bytes
sending 'recovery' (11248 KB)...
OKAY [ 1.364s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 2.470s
I was going through the steps to try to flash the Google Edition ROM onto my T-Mobile HTC One using this guide: http://htc-one.wonderhowto.com/how-...with-bootloader-recovery-ota-updates-0148068/
I have unlocked the bootloader, rooted, and gotten S-off. I'm on Step 3, changing the model ID if necessary. I was stupid and was not reading carefully enough, and missed the edit at the top of the section saying I didn't actually need to change this. So I went to the guide he linked to: http://forum.xda-developers.com/showthread.php?t=2322820
In this guide, I downloaded the PL83IMG.zip and edited the text file to put in my current Model ID, Cell ID, and ROM version. Rezipped, then did the command he gives:
Code:
c:\sdk-tools>fastboot flash zip android-info.zip
target reported max download size of 1526722560 bytes
sending 'zip' (479 KB)...
OKAY [ 0.247s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping & flushing...
(bootloader) [RUU]UZ,hboot,0
(bootloader) [RUU]UZ,hboot,43
(bootloader) [RUU]UZ,hboot,99
(bootloader) [RUU]UZ,hboot,100
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
OKAY [ 2.401s]
finished. total time: 2.653s
Ok, now as he says in the guide, I saw the HTC logo and a progress bar that was sitting at about 3/4 done. He says to reboot the phone, so I did this. The screen remains blank, I don't get the gray spotted screen he describes. I tried the "fastboot oem writemid PN0712000" command, and it just sat on "< waiting for device >" for a long time, until I finally cancelled the command.
I can still get into the bootloader by holding down power and volume down, but if I try to boot normally or boot into recovery, the screen just turns off and remains off. Also, the device can no longer be recognized on my computer. I get a popup from Windows saying "the last USB device connected to this computer malfunctioned, Windows does not recognize it." And neither adb or fastboot can see that there is a device connected.
So...is my phone bricked? Is there some way I can recover from this? I assume the problem is this HBOOT that I flashed. This is what I'm seeing on my bootloader screen
Code:
*** LOCKED ***
M7_UL PVT ENG S-OFF
CID-T-MOB010
HBOOT-1.39.2000 (PN0713000)
OpenDSP-v32.120.274.0909
eMMC-boot
I do notice that it changed to LOCKED from UNLOCKED and TAMPERED.
Mine followed the same pattern. You should be able to make sure your in fastboot and write your CID and MID and then run an RUU through the fastboot OEM rebootRUU command
Sent from my Nexus 10 using Tapatalk 4
Hi
My fone htc one m8 es rooted and i want to go back my stock plz halp
I try rru img fil but error 130 bootloader also lock and (s-on )
Error 130 means you aren't using the right RUU. You have to use one that is specific to your carrier or region and must be the same version or newer. You can not downgrade while S-On.
htc on m8
I am use version4.28.502.1 dame error come
How i unroot my htc one m8 mey region asia
4.28.502.1 is the RUU you are trying to use? That appears to be one for ATT, which is an American cellular service provider. You should be able to find something here http://forum.xda-developers.com/showthread.php?t=2701376
htc on m8 how unroot and delete supersu
how unroot and delete supersu i am not able to find my htc one m8 arabic version
I want to restore orignal stock 4.4.4 kitkat
I can't guess which update you need. Since you don't know, the best way is to boot to the bootloader and use fastboot (if you don't have it, Google : Minimal ADB and Fastboot). Once in bootloader use the terminal or command prompt to enter : fastboot getvar all. Copy and paste results here and leave out your IMEI and serial number for security's sake.
es0tericcha0s said:
I can't guess which update you need. Since you don't know, the best way is to boot to the bootloader and use fastboot (if you don't have it, Google : Minimal ADB and Fastboot). Once in bootloader use the terminal or command prompt to enter : fastboot getvar all. Copy and paste results here and leave out your IMEI and serial number for security's sake.
Click to expand...
Click to collapse
my htc datail
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.21331147A1.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B67000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 56f9ae32
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.046s
Like I said in my last post, you should not post your IMEI / serial number.
I believe this RUU should work and is Lollipop 5.0.2 https://www.androidfilehost.com/?fid=95916177934518148
You must relock your bootloader since you are S-On. In bootloader, use fastboot command: fastboot oem lock
How to s-off and plz tel me how to install ruu zip file
Thanks
htc on m8
How to s-off and plz tel me how to install ruu zip file
Thanks
S-Off might not be the best idea for someone who isn't comfortable with how to search for information on XDA or Google. Double click the RUU exe and follow directions. S-Off can be achieved with Sunshine. It is a paid app. There are no free solutions anymore.
htc on m8
Dear
This on zip file not img
Did you try extracting it? It's probably compressed for easier uploading / downloading.
htc on m8
Yes i try to extrac
Ok can i use with adb fastboot comnd to install ?
I will try to flash but not load any ruu
I flash with fastboot error come
Target reported max download size 1826418688 byets
Error cannot load 0P6BIMG.zip no error
Thanks
htc one m8
i try but fastboot come like this
C:\Users\TOSHIBA\Desktop\adb fastboot-s.off\adb fastboot>fastboot flash zip 0P6B
IMG.zip
target reported max download size of 1826418688 bytes
error: cannot load '0P6BIMG.zip': No error
syedfawaf said:
i try but fastboot come like this
C:\Users\TOSHIBA\Desktop\adb fastboot-s.off\adb fastboot>fastboot flash zip 0P6B
IMG.zip
target reported max download size of 1826418688 bytes
error: cannot load '0P6BIMG.zip': No error
Click to expand...
Click to collapse
Sorry, didn't realize it was actually the zip as most RUUs are exes. To load the RUU zips you have to boot to the special fastboot screen by using the command:
fastboot oem rebootRUU
then flash the rom zip like you were trying. It might fail after the bootloader, which is common, you just need to immediately redo the command and it should go through.
no dear same error
Is the zip in the same folder where you are running the commands?
Yas zip is same folder