Guest eViL D: Posted May 14, 2010 Report Share Posted May 14, 2010 Nope, looks like it's gonna be unlocked bootloader or some way to circumvent the fastboot flashing, ala testruu. Link to comment Share on other sites More sharing options...
Guest xhemp Posted May 14, 2010 Report Share Posted May 14, 2010 Nope, looks like it's gonna be unlocked bootloader or some way to circumvent the fastboot flashing, ala testruu. Yep, it's a shame but I believe that's the other way. Link to comment Share on other sites More sharing options...
Guest Biliskner Posted May 14, 2010 Report Share Posted May 14, 2010 flash TestRUU and run MTTY commands over Fastboot USB? Link to comment Share on other sites More sharing options...
Guest Biliskner Posted May 14, 2010 Report Share Posted May 14, 2010 actually I don't care about Mass Storage when I plug into Windows/Linux. I just want to flash ROMs like yours Evild D: :) Link to comment Share on other sites More sharing options...
Guest eViL D: Posted May 14, 2010 Report Share Posted May 14, 2010 Anyone know how to get these sigs? C:\SDK\tools>fastboot update update.zip archive does not contain 'boot.sig' archive does not contain 'recovery.img' archive does not contain 'system.sig' -------------------------------------------- Bootloader Version...: 0.75.0000 Baseband Version.....: 4.05.00.30_2 Serial Number........: HT03YPL08879 -------------------------------------------- sending 'boot' (2560 KB)... OKAY writing 'boot'... INFOsignature checking... FAILED (remote: signature verify fail) Link to comment Share on other sites More sharing options...
Guest Biliskner Posted May 14, 2010 Report Share Posted May 14, 2010 Anyone know how to get these sigs? along those lines... what do you guys think of "rebuilding" the testruu.exe with .img files from rootedupdate.zip ? do-able? or will it confuse fastboot and fail halfway? (when it doesn't get the signatures it expects because I've replaced (for example) boot.img from rootedupdate.zip into the testruu.exe file.... i know it's a bit of a hack job...) Link to comment Share on other sites More sharing options...
Guest ZiCoN Posted May 14, 2010 Report Share Posted May 14, 2010 along those lines... what do you guys think of "rebuilding" the testruu.exe with .img files from rootedupdate.zip ? do-able? or will it confuse fastboot and fail halfway? (when it doesn't get the signatures it expects because I've replaced (for example) boot.img from rootedupdate.zip into the testruu.exe file.... i know it's a bit of a hack job...) Personally I think we either need to go to the store, play dumb and hope for a replacement or wait till we can our hands on an unlocked SPL... It's the bootloader that makes all of this a pain in the ¤ss What I don't understand, is how this happend... Is it because everything is unlocked during the recovery session? Don't misunderstand me.... I'll try just about anything, help where I can, but I'm getting kinda frustrated now :) Link to comment Share on other sites More sharing options...
Guest Biliskner Posted May 14, 2010 Report Share Posted May 14, 2010 Personally I think we either need to go to the store, play dumb and hope for a replacement or wait till we can our hands on an unlocked SPL... It's the bootloader that makes all of this a pain in the ¤ss What I don't understand, is how this happend... Is it because everything is unlocked during the recovery session? Don't misunderstand me.... I'll try just about anything, help where I can, but I'm getting kinda frustrated now ;) yup, i have the same sentiment. I'm not quite frustrated enough to part with my phone for 3 weeks (minimum) (i imported mine), so at the moment I'm happy to have my phoncalls work, internet work (3g+wifi). when i get totally sick of it, i'll put in RMA and get it exchanged/repaired (also need to pile up enough books for 2 hours per day x3 weeks - the time without my mobile) :) and yes, i think this happened because everything was unlocked. HOW it happened? Who knows!! if i remember correctly, everything booted (rootedupdate.zip + a2sd) fine... it was only when i swapped my SD card (goldcard 4gb) for my 8gb that it boot-looped. after a few loops, i thought "oh just need to repartition!" and then repartitioned via green recovery menu. but it still boot-looped. then i thought, "just reflash!!", THEN BAM! Linux gave "error device not found". So beats me, the act of swapping the cards = bootloop. Then repartition via green recovery menu = stuffed it completely. i know, failsauce. Link to comment Share on other sites More sharing options...
Guest xhemp Posted May 14, 2010 Report Share Posted May 14, 2010 yup, i have the same sentiment. I'm not quite frustrated enough to part with my phone for 3 weeks (minimum) (i imported mine), so at the moment I'm happy to have my phoncalls work, internet work (3g+wifi). when i get totally sick of it, i'll put in RMA and get it exchanged/repaired (also need to pile up enough books for 2 hours per day x3 weeks - the time without my mobile) :) and yes, i think this happened because everything was unlocked. HOW it happened? Who knows!! if i remember correctly, everything booted (rootedupdate.zip + a2sd) fine... it was only when i swapped my SD card (goldcard 4gb) for my 8gb that it boot-looped. after a few loops, i thought "oh just need to repartition!" and then repartitioned via green recovery menu. but it still boot-looped. then i thought, "just reflash!!", THEN BAM! Linux gave "error device not found". So beats me, the act of swapping the cards = bootloop. Then repartition via green recovery menu = stuffed it completely. i know, failsauce. There should be a way to restore everything. The same way we restored network + sd card with enableqxdm 0. Dont you think? Link to comment Share on other sites More sharing options...
Guest Biliskner Posted May 14, 2010 Report Share Posted May 14, 2010 i regret repartitioning - since my 8gb card was fine in my Hero. I should've just reflashed rootedupdate.zip and r1a2sd and see if it boot-looped. :) Link to comment Share on other sites More sharing options...
Guest Biliskner Posted May 14, 2010 Report Share Posted May 14, 2010 There should be a way to restore everything. The same way we restored network + sd card with enableqxdm 0. Dont you think? There SHOULD be. But now everything is locked down, so the chances aren't high (it's been over 3 weeks, so i'm losing hope)! :) Link to comment Share on other sites More sharing options...
Guest xhemp Posted May 14, 2010 Report Share Posted May 14, 2010 There SHOULD be. But now everything is locked down, so the chances aren't high (it's been over 3 weeks, so i'm losing hope)! :) Well, I believe it's time for HTC Customer Service then ;) Link to comment Share on other sites More sharing options...
Guest Biliskner Posted May 14, 2010 Report Share Posted May 14, 2010 Well, I believe it's time for HTC Customer Service then :) :| Link to comment Share on other sites More sharing options...
Guest ZiCoN Posted May 14, 2010 Report Share Posted May 14, 2010 There should be a way to restore everything. The same way we restored network + sd card with enableqxdm 0. Dont you think? I have thought of this constantly... But is there a command anywhere... I'm thinking sort of a "bios switch" If you can turn on network and storage again... then why not usb and bluetooth... Anyone with contacts in HTC development? ... anyone... anyone.. Link to comment Share on other sites More sharing options...
Guest jeckyllhavok Posted May 14, 2010 Report Share Posted May 14, 2010 (edited) I have thought of this constantly... But is there a command anywhere... I'm thinking sort of a "bios switch" If you can turn on network and storage again... then why not usb and bluetooth... Anyone with contacts in HTC development? ... anyone... anyone.. :) This can't be, my old phone won't survive longer than 2 hours without charging, so i won't send that damn thing to HTC. there has to be a way how we can reformat this Normaly this is Samsung Style but not HTC Edited May 14, 2010 by jeckyllhavok Link to comment Share on other sites More sharing options...
Guest eViL D: Posted May 14, 2010 Report Share Posted May 14, 2010 anyone seen these on their sdcard? qxdm_20100513_072807_1.dm qxdm_20100513_073326_1.dm qxdm_20100513_073635_1.dm qxdm_20100513_073726_1.dm All zero kb too. also, 5 days ago. Link to comment Share on other sites More sharing options...
Guest geek78 Posted May 14, 2010 Report Share Posted May 14, 2010 anyone seen these on their sdcard? qxdm_20100513_072807_1.dm qxdm_20100513_073326_1.dm qxdm_20100513_073635_1.dm qxdm_20100513_073726_1.dm All zero kb too. also, 5 days ago. yes when xdm is enabled :) Link to comment Share on other sites More sharing options...
Guest jeckyllhavok Posted May 14, 2010 Report Share Posted May 14, 2010 Mo, i only got DiskCacheIndex46210.tmp with 1KB there Link to comment Share on other sites More sharing options...
Guest eViL D: Posted May 14, 2010 Report Share Posted May 14, 2010 This might be useful. C:\SDK\tools>fastboot oem boot ... INFOsetup_tag addr=0xA0000100 cmdline add=0x8E07D98C INFOTAG:Ramdisk OK INFOTAG:smi ok, size = 0 INFOTAG:hwid 0x0 INFOTAG:skuid 0x21F04 INFOTAG:hero panel = 0x0 INFOTAG:engineerid = 0x0 INFOMCP dual-die INFOMCP dual-die INFOTAG:mono-die = 0x0 INFODevice CID is not super CID INFOCID is HTC__304 INFOsetting->cid::HTC__304 INFOserial number: HT03YPL08879 INFOcommandline from head: no_console_suspend=1 msmsdcc_sdioirq= INFO1 wire.search_count=5 INFOcommand line length =461 INFOactive commandline: board_bravo.disable_uart3=1 board_bravo. INFOusb_h2w_sw=1 board_bravo.disable_sdcard=0 diag.enabled=0 boa INFOrd_bravo.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e INFOmmc=false androidboot.baseband=4.05.00.30_2 androidboot.cid INFO=HTC__304 androidboot.carrier=HTC-SPA androidboot.mid=PB9920 INFO000 androidboot.keycaps=qwerty androidboot.mode=normal andro INFOidboot.serialno=HT03YPL08879 androidboot.bootloader=0.75.000 INFO0 no_console_suspend=1 msmsdcc_sdioirq=1 wire.search_count=5 INFOaARM_Partion[0].name=misc INFOaARM_Partion[1].name=recovery INFOaARM_Partion[2].name=boot INFOaARM_Partion[3].name=system INFOaARM_Partion[4].name=cache INFOaARM_Partion[5].name=userdata INFOpartition number=6 INFOValid partition num=6 INFOmpu_nand_acpu_rw A1E 1000 INFOjump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker INFOnel_addr(0x20008000) INFO-------------------hboot boot time:755075 msec FAILED (status read failed (Too many links)) Link to comment Share on other sites More sharing options...
Guest jeckyllhavok Posted May 14, 2010 Report Share Posted May 14, 2010 This might be useful. Is this from a bricked device? Link to comment Share on other sites More sharing options...
Guest eViL D: Posted May 14, 2010 Report Share Posted May 14, 2010 Is this from a bricked device? USB functionality is gone. bricked, no. Link to comment Share on other sites More sharing options...
Guest jeckyllhavok Posted May 14, 2010 Report Share Posted May 14, 2010 (edited) This is what i get (bricked Desire(no USB/BT/FM): \tools>fastboot oem boot ... INFOsetup_tag addr=0xA0000100 cmdline add=0x8E07D98C INFOTAG:Ramdisk OK INFOTAG:smi ok, size = 0 INFOTAG:hwid 0x0 INFOTAG:skuid 0x21F04 INFOTAG:hero panel = 0x0 INFOTAG:engineerid = 0x0 INFOMCP dual-die INFOMCP dual-die INFOTAG:mono-die = 0x0 INFODevice CID is not super CID INFOCID is HTC__102 INFOsetting->cid::HTC__102 INFOserial number: HT043PL11636 INFOcommandline from head: no_console_suspend=1 INFOcommand line length =421 INFOactive commandline: board_bravo.disable_uart3=1 board_bravo. INFOusb_h2w_sw=1 board_bravo.disable_sdcard=0 diag.enabled=0 boa INFOrd_bravo.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e INFOmmc=false androidboot.baseband=4.05.00.11 androidboot.cid=H INFOTC__102 androidboot.carrier=HTC-GER androidboot.mid=PB992000 INFO0 androidboot.keycaps=qwerty androidboot.mode=normal android INFOboot.serialno=HT043PL11636 androidboot.bootloader=0.75.0000 INFOno_console_suspend=1 INFOaARM_Partion[0].name=misc INFOaARM_Partion[1].name=recovery INFOaARM_Partion[2].name=boot INFOaARM_Partion[3].name=system INFOaARM_Partion[4].name=cache INFOaARM_Partion[5].name=userdata INFOpartition number=6 INFOValid partition num=6 INFOmpu_nand_acpu_rw A1E 1000 INFOjump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker INFOnel_addr(0x20008000) INFO-------------------hboot boot time:10373 msec FAILED (status read failed (Too many links)) Edited May 14, 2010 by jeckyllhavok Link to comment Share on other sites More sharing options...
Guest jeckyllhavok Posted May 14, 2010 Report Share Posted May 14, 2010 Ok, here are the differences (i don't take the different CID, cause i think it's due a different branding) evilD: INFOcommandline from head: no_console_suspend=1 msmsdcc_sdioirq= Mine: INFOcommandline from head: no_console_suspend=1 evilD: INFO1 wire.search_count=5 Mine: non existent evilD: INFOcommand line length =461 Mine: INFOcommand line length =421 evilD: INFOactive commandline: board_bravo.disable_uart3=1 board_bravo. INFOusb_h2w_sw=1 board_bravo.disable_sdcard=0 diag.enabled=0 boa INFOrd_bravo.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e INFOmmc=false androidboot.baseband=4.05.00.30_2 androidboot.cid INFO=HTC__304 androidboot.carrier=HTC-SPA androidboot.mid=PB9920 INFO000 androidboot.keycaps=qwerty androidboot.mode=normal andro INFOidboot.serialno=HT03YPL08879 androidboot.bootloader=0.75.000 INFO0 no_console_suspend=1 msmsdcc_sdioirq=1 wire.search_count=5 Mine: INFOactive commandline: board_bravo.disable_uart3=1 board_bravo. INFOusb_h2w_sw=1 board_bravo.disable_sdcard=0 diag.enabled=0 boa INFOrd_bravo.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e INFOmmc=false androidboot.baseband=4.05.00.11 androidboot.cid=H INFOTC__102 androidboot.carrier=HTC-GER androidboot.mid=PB992000 INFO0 androidboot.keycaps=qwerty androidboot.mode=normal android INFOboot.serialno=HT043PL11636 androidboot.bootloader=0.75.0000 evilD: INFO-------------------hboot boot time:755075 msec Mine:(at least mine is faster ;-) ) INFO-------------------hboot boot time:10373 msec Link to comment Share on other sites More sharing options...
Guest vastloper Posted May 14, 2010 Report Share Posted May 14, 2010 For the people with no adb connection. Just a wild guess and perhaps allready tried but i noticed adb is not working eventhough adb is enabled in the settings. After disabling and enabling it it starts to work Try this: goto settings then apps then development you see usb is selected so you expect adb to work unselect and select again then it should work when not working go into a terminal program and type: $ su # toolbox setprop persist.service.adb.enable 1 This should turn on the adb service Hope this works Greetings from a vastloper Link to comment Share on other sites More sharing options...
Guest jeckyllhavok Posted May 14, 2010 Report Share Posted May 14, 2010 For the people with no adb connection. Just a wild guess and perhaps allready tried but i noticed adb is not working eventhough adb is enabled in the settings. After disabling and enabling it it starts to work Try this: goto settings then apps then development you see usb is selected so you expect adb to work unselect and select again then it should work when not working go into a terminal program and type: $ su # toolbox setprop persist.service.adb.enable 1 This should turn on the adb service Hope this works Greetings from a vastloper Just tested this, but no success. :) Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now