Lets get together and try and un-brick these phones.
Ive been following the thread in the G1 forum and there is currently an un brick method using JTAG for the (G1), but currently no method for the Magic (G2) at present either with JTAG or the Serial console.
Ive been slowly working though the images extracting commands that work both with S-ON and S-OFF phones and gathering information from other threads.
I think it would be a good idea for us to get together and bring our knowledge into one place and solve this Recovery Image ARM11 Mode3 issue, what do u think ?
G.
Related
Do the instructions for rooting a Magic handset apply to retail versions?
http://android-dls.com/wiki/index.php?title=Magic_Rooting
I ask as the HTC info on fastboot states:
"you cannot flash these images to a retail devices such as the T-Mobile G1 because the images do not have the appropriate cryptographic signatures."
Does this mean only developer phones have bootloaders that can flash or that the ROMs available on this site have cryptographic signatures that allow the bootloader on retail handsets to run?
I know there is a "hacked SPL" later on at step 13 but I don't know if I can get past booting with fastboot at step 11.
Sorry if this seems obvious to you.
Thanks
Shawn
Not all Magic can be rooted as instructed. Mine with HBOOT 1.33.0010 cannot be rooted as fastboot will not work. Still waiting and searching for ways to root my Magic till now.
Shawn, which model do you have?
If you've got hboot 1.133.0009, you should be able to do it, but be careful as there're a lot of people who're putting their phones out of service (myself included) by attempting to do it with too little understanding of what to do first, and then next, and then next.
Caid.
444
I've got nothing right now. I'm trying to figure out which handset to get knowing I'll want to root it.
Options:
1) Hero (not available yet and not know if rootable)
2) Google Magic Dev. phone (via auction in Japan -- $$ ouch)
3) Retail DoComo Magic
Other ideas of handsets that are known to be rootable?
The htc magic, and the vodaphone magic are both rootable, if you follow the tutorials to do so.
Caid.
444.
how to know our HBOOT version?
Moderator, please do not delete/lock this topic, I know that there is a separate one for HardSPL however considering how many people with Mobilicity HTC Snap are encountering the same problem I think that we deserve a place to discuss this particular issue.
Here is how it goes for me:
1) Attempted creating a GOLDCARD (just in case, to avoid bricking my device which happened to other ppl here). Not possible, the new PSAS does not allow creating a Maple goldcard with a Maple device (why?). I created one for G1 from their website but I wouldn't risk using it unless I really have to.
2) Followed all the instructions for HardSPL using 1.17. Everything went well until the point where it asks to confirm USB Connectivity. The update utility was not able to find the device. I disconnected and reconnected it. Windows 7 installed a new driver. Then I ran ROMUpdateUtility again. This time it found the device but the screen was a bit weird (flashing from image empty to image version 1.0.00). Anyway, I proceeded and it finished with 100%. Then it restarted the device. In the bootloader the SPL is still 1.24 like everybody else is experiencing, no changes.
3) Repeated using 1.19 . Exactly the same results.
Questions: is it possible that this has something to view with the custom Mobilicity ROM (which is nowhere to be found on the HTC website)? May be JumpSPL only works with Generic/T-Mobile WinMo ROMs?
Given how many people here are having bricked devices and HTC/Mobilicity don't care to release the shipped ROM, would it be reasonable for us (as a group) to ask the PSAS guys to make a page like http: //psas.revskills.de/?q=goldcard for the Maple? My understanding is that if you have a goldcard you can load a ROM which doesn't match your CID, i.e. people with bricked Mobilicity devices will be able to load the Wind ROM and still have a usable HTC Snap 3G.
I second that!
Yes, Mobilicity users need some fix to this problem. Is there a workaround that will allow installing the Wind Mobile one (which is the exact exact same but sold as Maple instead of Snap) since the Mobilicity Snap is the like the only phone on htc canada's website with no ROM download.
But don't you need to HardSPL your device before you can install the Wind ROM?
I have broke it!
How can I can resurrect?
hi there, i recently bricked my sensation. i have the qpst tool and drivers installed i just dont have the phone image and boot image cannot find it anywhere:/
I have got the kernel source code from htcdev but the two files i need werent in there either.
is there a way of unbricking by rebuilding the source code if no one has the image files needed?
my htc sensation was running gb RUU_Pyramid_HTC_vodafone uk 1.50.161.1 but i unbranded it to this RUU_Pyramid_HTC_Europe_1.50.401.1_Radio_10.56.9035.00U_10.14.9035.01_M_release_223042_signed and then i couldnt update it or even update the boot loader due to not being able to write boot.img so then tried s-on and it now wont turn or or detect the charger. and i cant get it replaced under warranty due to it having a cracked external screen... help would be much appreciated.
thanks
Jonathan
Read the unbrick thread in the Dev forum
it wont let me post there as this is only my 2nd post.. and i have been following there instructions and have go to the point i need the image files to carry on and i cant find them posted anywhere:/
ORIGINAL START OF MY WORK THREAD:
http://forum.xda-developers.com/showthread.php?t=1576844
PORTAL WRITE UP:
http://www.xda-developers.com/android/simons-wildfires-utility-brings-intact-warranty-root-and-more/
Hello everyone, you may have heard of my unlocking tool for windows. It unlocks HTC devices and i am slowly but surely adding support for new devices. The sensation happened to be next on the list. I will be adding it to the official GUI app once this is confermed, so for now it is a batch file that needs testing. If you dont trust me for any reason, just open up the zip and view whats inside the batch file, i have nothing to hide Please report back any errors, not just "it dont work" I will ask the mods to look at those types of posts.
Download v1
TEST 1
unlock sim? Bootloader or else? Please provide more details
Bootloader without voiding the warranty (htc voids warranty apon unlock in countries that dont forbid it eg USA) original thread located here:
http://forum.xda-developers.com/showthread.php?t=1576844
ok if unlock hboot 1.27 is very good news for sensation users but i can't help because i already have unlocked bootloader. Thanks for your work
in theory this will unlock any device in which the s-off method's root works. Jupno bear i think its called? I can change root methods, but the method inside is definitively solid enough to unlock with root.
Thanks for wanting to include the Sensation with your tool simonsimons34 we can always use good utilities to make unlocking and modding our devices easier. But just to let you know the Sensation already has two great tools. Here is kgs1992's Super Utitlity and the article featuring it just yesterday in the Portal. The Sensation also has the HTC Sensation 4G All-In-One Toolkit by hasoon2000 that is stickied in the Sensation Android development forum.
This does something the others cant :/ which is why i included it. This works for any hboot revision and any rom as long as you have root (or can get it with the method i icluded -thanks jcase for finding it) This Unlocks the phone WITHOUT the need to contact htcdev and submit a token. Sure it doesnt S-off or anything, but for new phones or phones which there are no ways to install roms except by contacting HTCDEV.com and voiding your warranty, this is a life saver. Just check out what it does before you say its already been done please. I mean no offence to you, just however am annoyed you posted saying its been done before you looked into what it does
simonsimons34 said:
This does something the others cant :/ which is why i included it. This works for any hboot revision and any rom as long as you have root (or can get it with the method i icluded -thanks jcase for finding it) This Unlocks the phone WITHOUT the need to contact htcdev and submit a token. Sure it doesnt S-off or anything, but for new phones or phones which there are no ways to install roms except by contacting HTCDEV.com and voiding your warranty, this is a life saver. Just check out what it does before you say its already been done please. I mean no offence to you, just however am annoyed you posted saying its been done before you looked into what it does
Click to expand...
Click to collapse
Sorry man I did not mean to offend. I can not actually use your tool because I am already S-off with Revolutionary Hboot 1.17.1111. I downloaded your tool and yes this is awesome that your tool unlocks the bootloader. But did you actually look at the links I gave you? the Super Utitlity allows you to use Juopunutbear S-off without having to use HTC Dev Unlock first by utilizing the download from Unlimited.io (scroll to the bottom) wich is the website for the Juopunutbear S-off and it supports all Hboot versions, . So even though the Super Utility does not unlock the bootloader forsay, still the ability to not have to use HTC Dev has been done. But at the same time it has not been done. I am in no way trying to criticize you or your tool. What you have done is great and amazing work and most definitely has and deserves a place her. This tool will only make things easier for some users if not all. I just want to keep the facts staight is all.
Hi guys, something pretty bad happened tonight to my Htc One S.
I had maximusHD installed, so of course S-OFF and bootloader Unlocked. However, I was having some problems and decided to revert back to stock. I re-locked the bootloader, changed the CID back to the stock one and flashed the RUU. Everything went perfectly fine. Sort of. I noticed that the RUU I flashed was some kind of pre-release one (the whole interface was watermarked). I got that from androidruu.com
So I downloaded a newer RUU (yes, both of them were for the appropriate country) and flashed that one.
It went on normally for a while and then nothing. Black screen, no response, no charging light. It shows as QHSUSB_dload under Windows and as Qualcomm Gobi Wireless Modem under Linux.
Now, are RUUs so damn risky? Luckily the phone was Relocked and S-ON, so warranty should cover this. I read all kinds of threads about this problem but none of the proposed solutions worked... did I miss something or do really need to send it for repairs?
Thanks!
Camazza said:
Hi guys, something pretty bad happened tonight to my Htc One S.
I had maximusHD installed, so of course S-OFF and bootloader Unlocked. However, I was having some problems and decided to revert back to stock. I re-locked the bootloader, changed the CID back to the stock one and flashed the RUU. Everything went perfectly fine. Sort of. I noticed that the RUU I flashed was some kind of pre-release one (the whole interface was watermarked). I got that from androidruu.com
So I downloaded a newer RUU (yes, both of them were for the appropriate country) and flashed that one.
It went on normally for a while and then nothing. Black screen, no response, no charging light. It shows as QHSUSB_dload under Windows and as Qualcomm Gobi Wireless Modem under Linux.
Now, are RUUs so damn risky? Luckily the phone was Relocked and S-ON, so warranty should cover this. I read all kinds of threads about this problem but none of the proposed solutions worked... did I miss something or do really need to send it for repairs?
Thanks!
Click to expand...
Click to collapse
Hi,
I was stuck with the same issue. What threads have you tried I heard the only way is via JTAG but just wanna know if there is any other way
It seems like I could do something with the phone using QPST (which I have). What I'm missing are the device and chipset-specific files that need to be recovered from a working phone. There has been some talk about QPST and its usefulness here on xda, but I think they only made i work for some Samsung devices with Qualcomm chipsets.
Is there someone who is willing to help me, maybe by dumping the contents of his phone using QPST and posting them? I only need the SPL partition, which is the HBOOT i need to recover the phone.
Please, tell me I don't have to send it to HTC...
Camazza said:
It seems like I could do something with the phone using QPST (which I have). What I'm missing are the device and chipset-specific files that need to be recovered from a working phone. There has been some talk about QPST and its usefulness here on xda, but I think they only made i work for some Samsung devices with Qualcomm chipsets.
Is there someone who is willing to help me, maybe by dumping the contents of his phone using QPST and posting them? I only need the SPL partition, which is the HBOOT i need to recover the phone.
Please, tell me I don't have to send it to HTC...
Click to expand...
Click to collapse
QPST is just a software right... no hardware is required for it ha!!!!... I thought jtag is the only way to access a bircked phone.
our pc is able to detect QHSUSB_dload and via that itself will we be able to flash a mobile if we have a system dump??