Related
I decided to try and root my stock G1 this morning. The bootloader does not allow me to flash down to RC29. It gives the "Update Terminate" after it fully flashes it, but before it checks the flash. Then it only loads into the bootloader and stops.
However i just successfully flashed to RC30. None of the guides on here specify that I had to load another spl or bootloader first.... Am I missing something?? Thanks for your help.
Bootloader:
DREA100 PVT 32B RUUNBH
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.12.29
SEP 2 2008
Solved!!!: Apparently I was on the right track. My US T-Mobile G1 was locked somehow to only accept only RC30 and above. I made a goldcard for my SD card and the image no longer failed (same sd, same image file) at the flashing the .nbh. If anyone has been having issues flashing a US G1... try a goldcard... It instantly fixed the problem! I guess its not only for German and UK?!
BTW.. thanks to pk at codeandroid.org for his guide to make the goldcard without a WM device or linux... http://www.codeandroid.org/forum/?wpforumaction=viewtopic&t=9.2 (in broken english... lol)
Thanks to Viper and revskills.de for their work on goldcard images
Thanks to JesusFreke for this bada$$ ROM (1.5)
Thanks to Haykuro for his android 101 guide.
Great work everyone really...
you need to make sure that your sd card is formatted fat32 and checksum on the DREAIMG.NBH
then try again. should work.
thanks for replying did that. The md5 checksum matched perfectly I have 3 different sd cards all formatted in fat32 only. still no go. I have tried 3 different links to the dreaimg.nbh. made sure it was in all caps and everything. nothing.
It will find the file.
It will flash the file to 100%.
When it would normally check the integrity of each portion it says...
"dreaimg.nbh - FAIL"
"Update Terminate"
"Update FAIL".
The odd part is it will flash the RC30 nbh just fine... same sdcard, same instructions.
try a different sd card- my stock one didnt flash either, same error over and over.
use this nbh -
http://www.mediafire.com/?sharekey=78b87e4b3d9bce857f7ec40ada4772a691de501fd3b9a6eb5be6ba49b5870170
tried all 3 cards with your file. same thing. Why will it so willingly let me flash rc30 the exact same way?
you got me.....
this was the confusing part. so im sitting on rc 30 right now for the 5th time. i have had 30 or so unsuccessful flashes of RC29 and EVERY flash of RC30 was successsful... this is my barrier to Haykuros and/or JF roms...
The file names are case sensitive. It must be DREAIMG.nbh . All caps for the prefix, no caps in the suffix.
thanks for your response... i tried both ways. most of my 30 attempts was changing caps... no caps... on file name and extension. reformatting... downloading from new sources... clearing my temp folder so windows wasn't transferring the same file every time since they are names the same (trust me windows does that with same named and same sized files...)
The only thing I can come up with is a modded bootloader. My G1 is not the one i had from launch date... so this phone never had any lower than RC33 (got the phone 5 weeks ago, came pre-loaded with RC33). This maybe one of T-Mo's tactics in the "War on Root".
That may not be the issye... I had RC30 when I bought the phone. I was able to get to RC29 with no issues... I don't think tmobile did anything to the phone.
i wish it wasnt but how can this phone reject rc29 but accept rc30. does anyone have a rc28, rc19, or below .nbh?
Can you try flashing the engineering Bootloader or HARDSPL first, then fastboot?
I'm not sure if you can use those without having root first though.
ICBM said:
Can you try flashing the engineering Bootloader or HARDSPL first, then fastboot?
I'm not sure if you can use those without having root first though.
Click to expand...
Click to collapse
no i cant. from what i've seen the first step to installing any bootloader is accessing SU... which is root... which means i'm shot down again... getting depressed.
Has anyone tried loading HardSPL without root?
crushsuitandtie said:
no i cant. from what i've seen the first step to installing any bootloader is accessing SU... which is root... which means i'm shot down again... getting depressed.
Has anyone tried loading HardSPL without root?
Click to expand...
Click to collapse
You are right, you need root to be able to load a different boot loader. I got a replacement sent to me from T-Mobile with RC33 on it maybe 3 weeks ago and i had no problems with obtaining root. If i were you i would call up T-Mobile and tell them the Menu button is not working every time on your replacement. They may send you an express replacement...
makes me wish i had kept my launch phone... I got it with RC17 or 18... but i remember getting rc19 ota... this sucks. The only reason i traded it in is because GPS wouldnt ssync anymore unless i did a wipe... so i knew it was a software problem... if i had just rooted it I bet i wouldnt be in this crap. i couldbe on haykuros... right now...
Sounds like a hardware issue to me. The data from the SD card isn't being written to flash properly so the SPL can't verify it. I would try calling T-Mobile to see if they can send you another unit. Obviously don't tell them you tried to flash an unsupported ROM, just make up a story and they will likely believe it.
Just to exclude the obvious. Shouldn't the file be called DREAMIMG.nbh not DREAIMG.nbh as you've written.. Or is that just a typo in your posts?
crushsuitandtie said:
thanks for your response... i tried both ways. most of my 30 attempts was changing caps... no caps... on file name and extension. reformatting... downloading from new sources... clearing my temp folder so windows wasn't transferring the same file every time since they are names the same (trust me windows does that with same named and same sized files...)
The only thing I can come up with is a modded bootloader. My G1 is not the one i had from launch date... so this phone never had any lower than RC33 (got the phone 5 weeks ago, came pre-loaded with RC33). This maybe one of T-Mo's tactics in the "War on Root".
Click to expand...
Click to collapse
ok i received my phone like a month ago an it came with Rc33 install and my phone when try to flash Recovery, i get a error EveryTime, look at all My Topic you see
I just keep on trying and i get it on my 7th try lol I'm not lien
bp8575 said:
Just to exclude the obvious. Shouldn't the file be called DREAMIMG.nbh not DREAIMG.nbh as you've written.. Or is that just a typo in your posts?
Click to expand...
Click to collapse
The correct image name is DREAIMG.nbh. looks wrong but its right... I think it IS a hardware issue. The is writing but not verifying certain images... and its now giving me checksum errors on rc30 after 8 successful loads, but when i retried without doing anything to the file it completed. I would say its my card but I have 3 different cards...
bump for anyone else having trouble...
I am deciding to take the plunge and root my phone. what I am curious about is whether or not I can create a goldcard on a 1 gb sc card. I have scoured google and searched the forums and cannot find an explicit answer to this question. If anyone has some insight I would greatly appreciate it
youngalumni said:
I am deciding to take the plunge and root my phone. what I am curious about is whether or not I can create a goldcard on a 1 gb sc card. I have scoured google and searched the forums and cannot find an explicit answer to this question. If anyone has some insight I would greatly appreciate it
Click to expand...
Click to collapse
I believe that you can do it on anything upto 4gb? either way I used the 2gb card which came with my phone without a problem
i've created on 512mb
it doesn't matter the size, it must be fat32 formatted...and you have to follow instructions which you can find here
http://forum.xda-developers.com/showthread.php?t=572683
What I don't understand is - what's a goldcard?
Sorry for my stupid question, but I allways see "goldcard here, goldcard there"... but what's it??
Is it an SDCard which is able to self run flashing a particular radio/SPL? Can you use it with a perfected SPL? If yes, why don't all just use this method? And also, in case of brick, can it be used to unbrick it? (Dis)advantages?
Thanks
Excellent!!! I'm doing this today. the only other question I have is whether it would be easier for me to do this on windows 7 or my ubuntu partition?
elegos said:
What I don't understand is - what's a goldcard?
Sorry for my stupid question, but I allways see "goldcard here, goldcard there"... but what's it??
Is it an SDCard which is able to self run flashing a particular radio/SPL? Can you use it with a perfected SPL? If yes, why don't all just use this method? And also, in case of brick, can it be used to unbrick it? (Dis)advantages?
Thanks
Click to expand...
Click to collapse
Yep, it is. It doesn't work with every single perfected SPL though
People always use brick incorrectly. If you brick it, your phone is dead, gone, not usable. You effed it up completely and the only way to restore it is to like mess with hardware.
In the case though, where you soft brick it (for example: no ENG spl and you need to flash an RUU or w/e to get it working again) then you'll need a goldcard. Just do what you do and get an ENG SPL in and you won't need a goldcard. With ENG SPL, You can do fastboot commands, which does wonders =)
If it helps, you guys can only really brick your phone if you play with radio and SPL. So while your rooting it, I'll just let you know (This gave me peace of mind..) Don't be nervous, I was the first time! Then I found out you can only brick it if you don't follow instructions and put on the wrong spl/radio.
youngalumni said:
Excellent!!! I'm doing this today. the only other question I have is whether it would be easier for me to do this on windows 7 or my ubuntu partition?
Click to expand...
Click to collapse
Hmm.. I remember reading somewhere that windows 7 causes problems. But that may be for RUU stuff, so give it a try! If it doesn't work, move on over to ubuntu. It should work fine in windows 7 though!
yeah I figured out the windows 7 issue with hot sync and the adb...
im past that. the only isue i am having right now is with the goldcard. from the looks of it i am golden i have a serial but when i type the next command in the instructions
Code:
cat sys\class\mmc_host\mmc1\mmc1:*\cid
im getting a file not found error...
do i need to put my formatted sd card in my phone? or is the info i need physically on the phone?
ok sorry about wasting space and time by asking questions that I was able to figure out. but the only issue i have now is that i flashed the fender rom from theunlockr.com it gets to the android boot screen and now its blank. should i try another rom?
done. thank you
Hello! I'm a long-time lurk and this is my first post. Why? Because you folks at XDA are extremely knowledgeable and very helpful! I actually enjoy reading the forums and usually can find my answer using search. Call me a masochist, I guess. I just wish I had the chops to develop and not just be a continuous noobish sponge. I have successfully rooted my own Inspire with Bubby’s method and have flashed several radios and ROMs, no problem (knock on wood).
Anywho, I have searched and have seen similar issues to mine, but I have what I consider a more unique problem (which, if I’m wrong, I’m sure you fine folks will let me know). I attempted to root my brother’s Inspire over the weekend and it is currently showing a black screen with three vibrations and amber light (If I try to go to Hboot manually, I get five whole vibrations with a green light). I can, though, pull the battery for 5 minutes or so, then the phone will boot normally. Although I think it’s on the downgraded ROM, because it shows the funky AT&T splashscreen instead of HTC. What I did was attempt root with Bubby’s and got stuck at the boot screen when the phone was trying to flash the PD98IMG.zip (downgrade I believe) after making the goldcard. It would show that it was trying to read the zip, however I never would get the “volume up to upgrade” option. I tried this three times. When that failed, I tried rooting with the Ace Hack Kit and after creating the goldcard image, when the script tried to reboot the phone to install the downgrade, I got the black screen, amber light with the 3 vibrations. My problem is that I don’t have root, can’t get to recovery from the Hboot screen (shows red exclamation with triangle) and was unable to install Clockworks Mod thru ROM manager because I’m not rooted, so no SuperUser privileges.
What can I do at this point? Maybe off base, but I believe I have somehow corrupted the boot partition or the like, including screwing up Hboot. Is it possible to fix this if I am not able to reboot without pulling the battery? I have tried going thru Bubby’s and the Ace kit again, but always fail when the phone reboots.
Thanks for your help!
I am far from an expert, or even a novice, but to me it sounds like you have a corrupted download for the bubbys one click.... Have you checked the Md5 on the downloaded file?
Sent from my Inspire 4G using XDA App
I could lie and say yes, but no I didn't check md5 the first go around (although I did the 2nd time I reinstalled, after it screwed up). I did have all antivirus programs uninstalled and firewall turned off.
It does sound like you got the downgrade rom without root. Go back to the hack kit. With the gold card in the phone, turn on usb debugging and connect to the pc in the charge only mode. Run menu number 3 in the hack kit.
Sent from my Desire HD using Tapatalk
@OP:
Follow the files and instructions in this post to get back to stock so u can start fresh. I followed these to get back to stock only today evening, and it worked.
--------------------
TO RETURN TO STOCK:
Make sure you S-ON (if able) BEFORE you Unroot. The S-On tool needs root permissions to function.
--------------------
Turn the phone on, connect to computer, and perform step 1. Make sure USB debugging is enabled.
Step 1 (S-On):
Run Bubby323's S-On tool: S-On Tool
Step 2 (STOCK ROM in ZIP FORMAT):
Place this .zip file on the root of your SD card. Disable fast boot in settings > applications. Turn off your phone. Hold down the volume down button and the power button at the same time. The phone will reboot into hboot. It will load the ROM automatically. Follow the steps to flash the ROM.
http://www.multiupload.com/JELMZNSKDF
I did this like a couple hours back, and mine's back to stock.
Note: I consolidated the links here from various posts on this forum.
Diablo: Was posting the reply below, when I saw your message. Would you still recommend I follow your steps to unroot, return to stock and run hack again?
Update: Well, I went thru Bubby’s root process again and was able to get the phone rooted (had to pull battery and wait 4 minutes when it needed to reboot). And I have confirmed root was successful. I also used Bubby’s fix to Eng S-Off (couldn’t hurt, right?). The phone now has the latest Android Revolution with Sense and the radio has been flashed (including full wipe and EXT4 wipe). However, it STILL won’t reboot correctly. I can boot directly into Clockwork from ROM Manager, but if I try to reboot normally (hold down power button and select restart), I get the black screen, amber light and 3 vibrations. Again, pull battery and wait 4 minutes and either power button to boot normally or power and volume down to get to Hboot works fine and goes to Clockwork from Hboot fine also. I guess I can keep up with the batter pull only when I have to manually restart, but WTH? There has got to be a fix for the reboot issue. Any ideas?
fernandezhjr said:
It does sound like you got the downgrade rom without root. Go back to the hack kit. With the gold card in the phone, turn on usb debugging and connect to the pc in the charge only mode. Run menu number 3 in the hack kit.
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Thanks, but tried that earlier on and couldn't continue on with steps in hack kit.
ogarlen said:
...I also used Bubby's fix to Eng S-Off (couldn't hurt, right?)...
Click to expand...
Click to collapse
Well, actually, wrong, it could hurt. I'm not saying that's the cause of your problems, but you really should've read up a little more before clicking on stuff so nonchalantly.
Eng s-Off means the engineering bootloader. If that process were to fail while in the midst of performing it on your phone, it would most likely hard-brick it.
Not to mention it's unnecessary. It was only included in that rooting method at the time for flashing radios, I believe, and since then a safer method for doing so has come into standard usage that doesn't require eng s-Off.
It's also one method of resolving the cwr blackscreen people were having, where you're actually in cwr, but the screen is black so you can't see what your doing. Not the same black screen your seeing, I don't think, because you're able to at least get into cwr.
ogarlen said:
Thanks, but tried that earlier on and couldn't continue on with steps in hack kit.
Click to expand...
Click to collapse
The vibrations with the blinking led, I have seen a few posts with this. Sadly, I haven't seen anyone post a fix yet.
Sent from my Desire HD using Tapatalk
Fernandezhjir: I understand your sentiment, however my situation does seem to be a little different than the other posts, so there may be hope yet.
Scott: You're absolutely right (as if you need me to confirm that) that it could hurt. My sarcasm didn't come over very well without a wink-smiley or the like. As I mentioned before, I have read the forums and the other posts on the difference between radio s-off and eng s-off and how dangerous it can be. Actually Bubby's program fairly adequately describes that taking that step can possibly brick your phone and when you should consider taking the risk. I was desperate and dumb and poking fun at myself in my post.
Any advice with my current situation? Everything on the phone is working fine unless I try to normal restart, then I get the amber light with 3 vibrations. Again, battery pull for 4+ minutes then resinsert and power works and I can get to Hboot and Clockwork okay.
ogarlen said:
Fernandezhjir: I understand your sentiment, however my situation does seem to be a little different than the other posts, so there may be hope yet.
Scott: You're absolutely right (as if you need me to confirm that) that it could hurt. My sarcasm didn't come over very well without a wink-smiley or the like. As I mentioned before, I have read the forums and the other posts on the difference between radio s-off and eng s-off and how dangerous it can be. Actually Bubby's program fairly adequately describes that taking that step can possibly brick your phone and when you should consider taking the risk. I was desperate and dumb and poking fun at myself in my post.
Any advice with my current situation? Everything on the phone is working fine unless I try to normal restart, then I get the amber light with 3 vibrations. Again, battery pull for 4+ minutes then resinsert and power works and I can get to Hboot and Clockwork okay.
Click to expand...
Click to collapse
Heh. Now that you explain it, I can see the sarcasm. I'm usually good a picking up on it, but you know how these internet textual posts go....smilies are crucial...
As to your problem, there seem to be a few posts in recent days describing the led/vibrations type of symptom.
I don't know if they're interrelated or not. I don't have an answer, but I'm curious and will drop in if I manage to come across any pertinent information.
Thanks for the replies! I will continue to research and update this thread if I find a solution. I really believe that it has something to do with the startup processes or boot cache or some other $10 phrase related to what happens when the phone is attempting to startup normally. I appreciate all help.
Sent from my Inspire 4G using XDA App
Just wanted to add a quick update for anyone searching that comes across this post: The phone in question is now working flawlessly (knock on wood). Restarting, power down and battery pulls work with no problems (no vibrations or flashes). I am honestly unsure what I did to cause this error or what the resolution was and can only speculate. Since my last post, I have made a Nandroid backup and flashed a couple ROMs (namely AR with Sense, then Virtuous Unity with full wipes in between), so I assume that somewhere in there the corrupted boot files (or whatever) were corrected. All's well that ends well...
Here is just something to add to everyone's good advice that you received. Search for the RUU in the development section. It can fully restore your phone back to stock out of the box condition. In situations such as this it is worth having saved on your computer.
Wolf_2 said:
Here is just something to add to everyone's good advice that you received. Search for the RUU in the development section. It can fully restore your phone back to stock out of the box condition. In situations such as this it is worth having saved on your computer.
Click to expand...
Click to collapse
Not quite true. If you've rooted and have S-OFF, that will survive a complete RUU update. You have to S-ON your device before applying the RUU if you want true "out-of-the-box" restoration.
seems like you got yourself a good taste of rom flashing issues. that's a good thing. i know that you have everything working flawlessly now, BUT i would still HIGHLY recommend that you download the Super Wipe script from the Android revolution thread and use that to completely wipe and format your partitions, then do a FULL wipe through clockwork and then install whatever ROM you would like. but i cant stress enough, MAKE SURE that the Md5 sums match always. this can be the difference between a working rom and a bricked phone. also i would like to add that through my experience i usually find that the first time you root the inspire, the very first rom you install on it almost always has issues. that's how it is for me atleast. Ive rooted plenty of Inspire's and all of them have had some sort of issue on the first flash. and as always, follow the directions per rom to the T or else it might not work.
P.S. Some roms run better with matching Radio and RIL. flashing these is AWLAYS good practice to get your phone to tunr the best possible.
Wolf_2 said:
Here is just something to add to everyone's good advice that you received. Search for the RUU in the development section. It can fully restore your phone back to stock out of the box condition. In situations such as this it is worth having saved on your computer.
Click to expand...
Click to collapse
Gene Poole said:
Not quite true. If you've rooted and have S-OFF, that will survive a complete RUU update. You have to S-ON your device before applying the RUU if you want true "out-of-the-box" restoration.
Click to expand...
Click to collapse
Thats why I posted the full steps in the guide , to s-on and ruu back to stock. On a side note bubbies s-on tool does not always work.
On another side note, Genepoole would be interested in wrighting a script for the s-on/return t stock process to make it a little more automated? The steps right now are flashing back to stock then re rooting, then entering gfree s-off on then re running the ruu.
mudknot2005 said:
On another side note, Genepoole would be interested in wrighting a script for the s-on/return t stock process to make it a little more automated? The steps right now are flashing back to stock then re rooting, then entering gfree s-off on then re running the ruu.
Click to expand...
Click to collapse
I have actually considered this. The current methods require a complete downgrade just like rooting when all you really need for gfree to work is the radio and kernel from the downgrade ROM.
Gene Poole said:
Not quite true. If you've rooted and have S-OFF, that will survive a complete RUU update. You have to S-ON your device before applying the RUU if you want true "out-of-the-box" restoration.
Click to expand...
Click to collapse
You are correct. I should have re phrased that differently. I know that S-Off would survive the RUU procedure so I should have said "almost out of the box". The RUU is still a very handy thing to have.
Gene Poole said:
I have actually considered this. The current methods require a complete downgrade just like rooting when all you really need for gfree to work is the radio and kernel from the downgrade ROM.
Click to expand...
Click to collapse
Please, sir.
Seriously, this would be, imo, a profound contribution to this phone.
I didn't post this in the CM7 thread because I believe my problem was a glitch during rooting, not CM7 which seems to work fine.
I recently dropped my Insight 4G which had been rooted and was running the Revolution ROMs and cracked the screen. I purchased a replacement phone, which arrived with the Gingerbread ROM from AT&T.
I decided to try CM7 this time and followed the instruction on wiki.cyanogenmod.com/wiki/HTC_Ace to the letter on rooting, installing clockworkmod, and installing the CM7 roms. Everything worked perfectly with one exception.
Now the phone takes > 10 mins (closer to 20 actually) to boot every time it reboots. I have tried restoring a nandroid backup of the Revolution ROMS from my original phone and everything works fine, but reboot is still very, very long. Restored CM7 from nandroid backup and tried to install RUU file to restore the phone to AT&T, but the software times out due to the extremely long boot time. Everything seems fine on the phone except for the boot time and I don't know what to do next.
After reading a lot of posts it appears that the instructions I followed have a similar effect to using the outdated Ace Hack Kit here. (Wish I'd used the new one). I am well and truly "Jammed Up"
Anyone have a possible fix? I am happy to do whatever it takes... not worried about data.
tricotec said:
I didn't post this in the CM7 thread because I believe my problem was a glitch during rooting, not CM7 which seems to work fine.
I recently dropped my Insight 4G which had been rooted and was running the Revolution ROMs and cracked the screen. I purchased a replacement phone, which arrived with the Gingerbread ROM from AT&T.
I decided to try CM7 this time and followed the instruction on wiki.cyanogenmod.com/wiki/HTC_Ace to the letter on rooting, installing clockworkmod, and installing the CM7 roms. Everything worked perfectly with one exception.
Now the phone takes > 10 mins (closer to 20 actually) to boot every time it reboots. I have tried restoring a nandroid backup of the Revolution ROMS from my original phone and everything works fine, but reboot is still very, very long. Restored CM7 from nandroid backup and tried to install RUU file to restore the phone to AT&T, but the software times out due to the extremely long boot time. Everything seems fine on the phone except for the boot time and I don't know what to do next.
After reading a lot of posts it appears that the instructions I followed have a similar effect to using the outdated Ace Hack Kit here. (Wish I'd used the new one). I am well and truly "Jammed Up"
Anyone have a possible fix? I am happy to do whatever it takes... not worried about data.
Click to expand...
Click to collapse
What I would do is return to a full stock. Then run the hack kit. But that is just me as I have never donebit with the CM wiki instructions
This is a common issue with the latest batch of Inspires (post Aug, 2011 MFG). The hardware is different and not compatible with any hboot except the one that ships with the GB RUU. If you downgraded as per the CM wiki, then you necessarilly installed an older hboot and this is the root cause of your problem.
You can easily replace the hboot on an S-OFF Inspire once it finally does boot by simply writing the later hboot image to the hboot partition (partition 18). There's instructions here:
http://paste.pocoo.org/show/495273/
You can jump into the IRC channel if you need some one-on-one help:
http://webchat.freenode.net/?channels=#liberatedAria
Ok, after many hours of fiddling I finally got it back.
I used the hack kit to re-install the stock RUU using the alternate (hboot) method. It took a LONG time, but was successful. I then used the hack kit to re-root the phone and installed CM7 nightlies. The ace hack kit is a wonderful tool, and I thank the author for making it.
Gene Poole said:
This is a common issue with the latest batch of Inspires (post Aug, 2011 MFG). The hardware is different
Click to expand...
Click to collapse
Hey Gene so what your saying is all Inspire batches post Aug, 2011 must be rooted using the current acehack kit only right?
And older methods of rooting will cause intermittent booting?
Crazy Food For Thought....
jadeus0831 said:
Hey Gene so what your saying is all Inspire batches post Aug, 2011 must be rooted using the current acehack kit only right?
And older methods of rooting will cause intermittent booting?
Crazy Food For Thought....
Click to expand...
Click to collapse
That is correct. The new AHK uses an HTC signed interim firmware patch put out for the DHD which has only a boot.img, radio.img and recovery.img. Fortunately, the radio and boot images are ones that are compatible with gfree and the S-OFF routines can be run without disturbing the rest of the firmware (hboot, system and data mainly), but unfortunately, the kernel is not compatible with the Inspire's graphics hardware so the process literally runs in the dark, and because of the GB changes, it must run in two stages involving both adb and fastboot. USB issues rampant among PCs (so many PC programs assume they are the only program you're ever going to run and so hijack the USB bus thinking you're never going to plug in any other device but theirs) so it is very important that both adb and fastboot drivers can run unimpeded. Occasionally a situation arises where adb runs OK, but fastboot fails and this leave the device in an intermediate state which is not in itself bad, but because there is a blank screen, users freak out and do everything but the right thing (usually involving a "wipe" from hboot) which really screws things up.
Hi Tricotec.
Please, could you describe the steps for doing it. I have the same problem.
Thanks.
nlennis said:
Hi Tricotec.
Please, could you describe the steps for doing it. I have the same problem.
Thanks.
Click to expand...
Click to collapse
i also need those steps.
i tried with ruu but white rebooting bootloader it takes around 10 minutes due to which connection time out occurs b/w phone and wire thus ruu is not installing properly, is there any way we can edit ruu exe file to wait for accepting connect for 10 minutes or so
or please tell other steps
sandeep88822 said:
i also need those steps.
i tried with ruu but white rebooting bootloader it takes around 10 minutes due to which connection time out occurs b/w phone and wire thus ruu is not installing properly, is there any way we can edit ruu exe file to wait for accepting connect for 10 minutes or so
or please tell other steps
Click to expand...
Click to collapse
Nice!! you messed the bootloader for not reading all the warnings. The only fix for the issue is this one:
http://tau.shadowchild.nl/attn1/?p=188
glevitan said:
Nice!! you messed the bootloader for not reading all the warnings. The only fix for the issue is this one:
http://tau.shadowchild.nl/attn1/?p=188
Click to expand...
Click to collapse
i did not did this, i hv gingerbread 2.47 ruu, and i am aware not to downgrade it
its done by my ebay friend, lol he ha sonly that older ruu and he updated 100's of inspire with that, its the first time he got a newer inspire
anyways thanks a lot xda rocks
Hi, I've made a gold are for a second desire s I got for free as it wont boot and have been trying to revive.
The card works as it should and bypasses the cid although I think the desire is beyond help as i cant flash the bootloader no matter what process i try, my question is about keeping the card for future use in other devices.
Once made and used can it be re used over and over in different devices with different files for those specific phones or do you have to remake the card each time its used for a different phone?
My other question is does formatting it mean you have to re make the gold card or does the hex edit remain?
Thanks in advance,
Steve.
steve_htc_wizard said:
Hi, I've made a gold are for a second desire s I got for free as it wont boot and have been trying to revive.
The card works as it should and bypasses the cid although I think the desire is beyond help as i cant flash the bootloader no matter what process i try, my question is about keeping the card for future use in other devices.
Once made and used can it be re used over and over in different devices with different files for those specific phones or do you have to remake the card each time its used for a different phone?
My other question is does formatting it mean you have to re make the gold card or does the hex edit remain?
Thanks in advance,
Steve.
Click to expand...
Click to collapse
First try install RUU for that Desire S bc you have goldcard.
SKENER said:
First try install RUU for that Desire S bc you have goldcard.
Click to expand...
Click to collapse
I have tried every mothod going to try and flash that phone, it refuses to touch the bootloader.
Ruus won't even try cos it won't boot, official branded roms with the right cid the same android version give a same version error before it even tries to flash.
Different version roms that are right cid freeze on flashing bootloader be it in the form of a PG88IMG from SD or in fastboot.
And unbranded roms used with a gold card freeze on flashing bootloader.
The phone won't restart to bootloader from bootloader and any programs that try to restart the boot loader fail to managed it at the bootloader freezes with battery pull being the only way to shut phone down and try again.
When I got this phone from a friend it never booted past t-mobile screen and he says it just stopped working one day, its not keen messed with and as a result I think usb debugging was not enabled ether although fastboot does work for some commands strangely.
Basicly anything that trys to work with the bootloader gets told where to go by the phone lol
If it was s-off I could have used the work around from booting the o.s from the SD card but its not.
I think the emmc has corrupted from agressive multiple app updates from the marketplace and think its beyond help, I've spent hours trying everything lol. Now I just want to know if the gold card I made can be reused in other phones and what a format would do to the card.