I'm sorry for opening a thread on this.
Usualy I try to read up on things a lot more and try to solve things on my own.
Unfortunatly this time,the more I read the more confused I get.
Anyway ,today I updated from my desire to the desire s and as probably always when you get a new device you start to think that with the old one it was all much easier.
Well long story short...
I already S-Offed my phone using the revolutionary method which obviously changed the hboot from 0.98.00002 to 6.98.1002.
Now I read that it is beneficial, for phones that have a M4G2DE eMMC,to upgrade the hboot to 0.98.2000.
(I know there a other reasons to flash this hboot, like beeing able to flash radios and what not through fastboot).
So far so good...Later on I read that there is already a newer hboot( 2.00.2002 ) that should be considered ,cause it should "future proof" your device.
So my questions whould be...
What should I flash?
Should I flash the 0.98.2000 and stick with it.
Should I start with the 0.98.2000 and then upgrade to the 2.00.2002?
and...
Do I have to flash these hboot using a zip file?
With my old desire there were many different hboots that changed the partition tables and I always flashed them through fastboot.
Is this possible with the above mentioned hboots aswell?
I think that it should be,but all I read about was only updating with zip files or adb.
Well I know this has all probably been answerd before,but if someone could take the time to help me out a little I'd really appreciate it.
[armitage] said:
I'm sorry for opening a thread on this.
Usualy I try to read up on things a lot more and try to solve things on my own.
Unfortunatly this time,the more I read the more confused I get.
Anyway ,today I updated from my desire to the desire s and as probably always when you get a new device you start to think that with the old one it was all much easier.
Well long story short...
I already S-Offed my phone using the revolutionary method which obviously changed the hboot from 0.98.00002 to 6.98.1002.
Now I read that it is beneficial, for phones that have a M4G2DE eMMC,to upgrade the hboot to 0.98.2000.
(I know there a other reasons to flash this hboot, like beeing able to flash radios and what not through fastboot).
So far so good...Later on I read that there is already a newer hboot( 2.00.2002 ) that should be considered ,cause it should "future proof" your device.
So my questions whould be...
What should I flash?
Should I flash the 0.98.2000 and stick with it.
Should I start with the 0.98.2000 and then upgrade to the 2.00.2002?
and...
Do I have to flash these hboot using a zip file?
With my old desire there were many different hboots that changed the partition tables and I always flashed them through fastboot.
Is this possible with the above mentioned hboots aswell?
I think that it should be,but all I read about was only updating with zip files or adb.
Well I know this has all probably been answerd before,but if someone could take the time to help me out a little I'd really appreciate it.
Click to expand...
Click to collapse
Right now you do not need to change your hboot. Stay active on the forum...learn more about the peculiarities of this device and only contemplate changing core stuff after that. As of now, there is no distinct advantage of changing from the revolutionary hboot... You can try every ROM released yet, including yge ics ones just fine on your current hboot.
Beamed from the Dark Side using xda premium.
Alright then,thanks for your help.
Already tried the CM9,so did know that this works.
I just thought I'd be on the safe side when flashing the newer hboot as it was mentioned in many threads that I read today.
Anyway,sorry for bugging you with this... but could you please answer the question I had regarding,flashing these hboots via fastboot?
On the bravo I flashed radios,splash screens,hboots and all that via fastboot and never had any problems with that.
But it seems that in all threads that I read today,only the adb and zip method was mentioned when talking about flashing hboots.
[armitage] said:
Alright then,thanks for your help.
Already tried the CM9,so did know that this works.
I just thought I'd be on the safe side when flashing the newer hboot as it was mentioned in many threads that I read today.
Anyway,sorry for bugging you with this... but could you please answer the question I had regarding,flashing these hboots via fastboot?
On the bravo I flashed radios,splash screens,hboots and all that via fastboot and never had any problems with that.
But it seems that in all threads that I read today,only the adb and zip method was mentioned when talking about flashing hboots.
Click to expand...
Click to collapse
NP, you're not bugging anyone. The Desire S forums are generally a very friendly place, so don't sweat it. It's OK to ask questions.
As for your question, the answer is : Yes you can...
In general, for flashing anything on the DS, you have many options, like:
Fastboot
Android Flasher
PG88IMG.zip (must have been a different name on the bravo, but the concept is the same)
Read the INDEX thread by ben_pyett in the Dev Section and any and all guides you can. And please note the ONE thing you ABSOLUTELY should not do with the DS - Pulling Battery while the device is powered on. Trust me on this. If there's one thing that you remember from this conversation, i want it to be this one. Make this a sacred rule, and never break it. read more about this issue, do a search...you seem like a smart guy, you'll figure it out.
Cheers.
P.S. : Welcome to the Desire S family.
Ok thanks again and I will keep that in mind.
Although I already had to break this rule when I was checking for the hboot version,when the phone arrived.
In the original hboot,there were no options to power down the phone besides pulling the battery.
Hope that rule only counts when the phone is booting or completely booted into OS.
Whould the eMMC be immediately damaged,so that I whould have noticed a problem right away, or could I have already damaged it in someway that I will maybe notice later on?
So far I don't have any cache related error messages,so I hope/guess that didn't damage anything.
[armitage] said:
Ok thanks again and I will keep that in mind.
Although I already had to break this rule when I was checking for the hboot version,when the phone arrived.
In the original hboot,there were no options to power down the phone besides pulling the battery.
Hope that rule only counts when the phone is booting or completely booted into OS.
Whould the eMMC be immediately damaged,so that I whould have noticed a problem right away, or could I have already damaged it in someway that I will maybe notice later on?
So far I don't have any cache related error messages,so I hope/guess that didn't damage anything.
Click to expand...
Click to collapse
You won't be able to boot if your eMMC is fried. So you're obviously not there yet.
As for when it can happen, nobody knows, might even happen if you pull battery while in bootloader (remember, you're still powered on!)
To reboot from within hboot, select the option "RECOVERY" and then from there, power off or reboot. Alternately, you can use the three button combo (Volume up + Volume Down + Power button, press and hold all three simultaneously)
Well I didn't have any recovery on the phone then.
The recovery option was there but it only gave me a black screen with a warning sign on it.
I could have used (Volume up + Volume Down + Power button, press and hold all three simultaneously) method,but I didn't know about it back then.
In retrospect I should have read a little more before doing anything I guess.
But guess I got lucky that nothing bad happend so far.
Anyway,thanks again for you help I really appreciate it.
Have a good one,mate.
[armitage] said:
Well I didn't have any recovery on the phone then.
The recovery option was there but it only gave me a black screen with a warning sign on it.
I could have used (Volume up + Volume Down + Power button, press and hold all three simultaneously) method,but I didn't know about it back then.
In retrospect I should have read a little more before doing anything I guess.
But guess I got lucky that nothing bad happend so far.
Anyway,thanks again for you help I really appreciate it.
Have a good one,mate.
Click to expand...
Click to collapse
That "Black screen" with a warning sign IS the default stock HTC recovery (you weren't expecting to see a custom recovery there, were you!?)
If you wait a couple of seconds on that screen and then press the power and volume button, you'll be presented with recovery options, one of which is Reboot. It doesn't show up on its own, you need to coax it by hitting the volume and power button...
No lol,I wasn't expecting a custom recovery there.
But as I didn't know what the stock recovery locked like and I didn't know how to interact with it I just asumed that there simply were no real options to use.
Well guess that's just one more thing I learned today.
Related
Okay, here goes the story-
1.Got an Inspire
2.Did the Hack Kit and then installed the Rooted Stock ROM (Discontinued), everything went okay but when trying to reboot into CWM, I got the HTC Screen for a few seconds then blackness, I later determined it was working I just couldn't see it for whatever reason.
3.Okay, I thought I'd try Bubby's One Click and see if that would fix it, it went great too, but CWM still no workie, getting frustated now.
4.I thought I'd try flashing a non-AT&T ROM, since so many have been having issue running one and getting the working, but black screened CWM, I chose CoreDroid's.
5.I put CoreDroid's ZIP on my SD Card, went into ROM Manager and installed it, making sure clear memory and backup current ROM were checked.
6.It rebooted into CWM, which of course I couldn't see, then about 10 minutes later it rebooted, and the beautiful CoreDroid Animation came up, and a few minutes after that I had CoreDroid up and running.
7.Well, I thought, CWM should work fine now, EHHHHH Sorry Johnny (which sounded weird, since my name is Mike ), wrong answer, I rebooted into CWM and there it was again, total blackness.
8.Okay, I noticed in CoreDroid that to be able to flash new Radio's, you had to have Eng S-OFF, so I ran the One Click Eng S-Off Tool found here http://forum.xda-developers.com/showthread.php?t=855403 , making sure to check the box saying I already have S-Off.
9.It ran, and said it was successful, and I now had Eng S-Off, so I rebooted into Hboot to check, and at the top sure enough, it said Eng S-Off, I then hit PowerDown, which it did, but then....well, go to 10
10.It rebooted into...yep, CWM! Clear and beautiful, it looked wonderful! So booted back up, went into ROM Manager and told it to boot into CWM, it did so and it came up again, no problems! I did it again to make sure it wasn't a fluke, nope, all was well now in CWM Land!
So, how's that for a saga? Ahh, now I can kick back, it's Miller Time, or Dr.Pepper Time in my world, I don't drink
Use this at YOUR OWN RISK! I take no responsibility for bricked or ruined phones, I just posted this in hopes it might help out people having CWM issues. DO NOT send me hate mail because this didn't work for you
Good job bro!! I don't personally have the problem, but I've been following tons who have. Well done!
i did step 8 throu 10 and it works great thanks a mill!
No prob, I'm glad I could help you guys out!
congrads!!! i'm gonna try it out, i really wanna try some of these awesome roms available
Thanks Epic, let me know how it goes for you! I can't figure out what it did, other than maybe some files were corrupted or missing, and doing the Eng S-Off pushed and refreshed whatever was corruped or missing, either way I am glad to have it working again
Very nice discovery, I will in cooperate this into the next version of my program. Thanks a ton.
bubby323 said:
Very nice discovery, I will in cooperate this into the next version of my program. Thanks a ton.
Click to expand...
Click to collapse
No Prob Bubby, I'm glad I could help and give something back! I am in full support of you by the way, I think it's pretty slimy how they ganged up on you like that, when all you did was try and make things easier for the community. If I can help out in any way, let me know!
californiarailroader said:
No Prob Bubby, I'm glad I could help and give something back! I am in full support of you by the way, I think it's pretty slimy how they ganged up on you like that, when all you did was try and make things easier for the community. If I can help out in any way, let me know!
Click to expand...
Click to collapse
Will do.
I believe (if I'm not mistaken) that ENG S-OFF is the Engineering bootloader... it's not the best way to S-Off, because it puts the Engineer's Test HBOOT onto your phone, which causes some problems for other things. Also, to get back to complete stock, you'll now need to flash a stock HBOOT as well, if I remember correctly.
For that very reason, I would *NOT* incorporate this into your one-click, bubby... it worked for me perfectly the way it is, WITHOUT an Engineering HBOOT. I'd leave this as a possible solution for the ones that actually have the problem.
ClearD said:
I believe (if I'm not mistaken) that ENG S-OFF is the Engineering bootloader... it's not the best way to S-Off, because it puts the Engineer's Test HBOOT onto your phone, which causes some problems for other things. Also, to get back to complete stock, you'll now need to flash a stock HBOOT as well, if I remember correctly.
Click to expand...
Click to collapse
I haven't had any issues yet, so hopefully I'm good I wouldn't have even ran it except for the fact that to flash other radios, you need to have it on there. I don't mind doing whatever I have to do to go back to Stock, which I don't plan on doing unless I have to send it in for warranty or insurance.
That said, I just posted it so that it might be of help to others, so I guess try it if you are having problems with CWM showing up properly, otherwise leave it alone
californiarailroader said:
I haven't had any issues yet, so hopefully I'm good I wouldn't have even ran it except for the fact that to flash other radios, you need to have it on there. I don't mind doing whatever I have to do to go back to Stock, which I don't plan on doing unless I have to send it in for warranty or insurance.
Click to expand...
Click to collapse
No doubt. I hope I never have to, either... I just remember that with an engineer hboot on the desire, it was a LOT harder to get it back to stock, and had several other issues, and that's why they did away with it in favor of non-ENG HBOOT options. I like how it opens up the phone, though. This is indeed a great find that it works with ours!
EDIT: Ahh, I found it. It's in the G2 Wiki here.
"INSTALLING ENGINEERING HBOOT (DZ/G2/DHD) - OPTIONAL and UNNECESSARY!
Assuming you've backed up your phone with Clockwork's nandroid, you can install the engineering HBOOT (bootloader), which among other things allows you to use fastboot flash (or flashing-over-usb from your computer). This is unnecessary for most users but provides additional functionality for developers.
This is totally optional and dangerous - if the write to the phone partition fails the phone will be bricked. At the moment there is no cure for a phone that has been bricked by a failed hboot install."
That very last line is why Bubby should NOT include this in his one click... you think problems are bad now, wait till someone bricks a device and we can't unbrick it! D:
ClearD said:
No doubt. I hope I never have to, either... I just remember that with an engineer hboot on the desire, it was a LOT harder to get it back to stock, and had several other issues, and that's why they did away with it in favor of non-ENG HBOOT options. I like how it opens up the phone, though. This is indeed a great find that it works with ours!
EDIT: Ahh, I found it. It's in the G2 Wiki here.
"INSTALLING ENGINEERING HBOOT (DZ/G2/DHD) - OPTIONAL and UNNECESSARY!
Assuming you've backed up your phone with Clockwork's nandroid, you can install the engineering HBOOT (bootloader), which among other things allows you to use fastboot flash (or flashing-over-usb from your computer). This is unnecessary for most users but provides additional functionality for developers.
This is totally optional and dangerous - if the write to the phone partition fails the phone will be bricked. At the moment there is no cure for a phone that has been bricked by a failed hboot install."
That very last line is why Bubby should NOT include this in his one click... you think problems are bad now, wait till someone bricks a device and we can't unbrick it! D:
Click to expand...
Click to collapse
Thanks for posting that. I was just going by what they said to do in the CoreDroid thread, and it worked for me, thankfully
"
FAQ:
Again, it's recommended that you flash radio 26.04.02.17_M2 (Orange ES 1.75.75.2 / HTC WWE 1.72.405.3) or radio_26.06.03.24_M2 (TELUS WWE 1.84.661.1) or Radio 26.05.05.27_M3 - (Orange UK 1.84.61.2)
How do I flash a new radio?
In order to flash other radios you need to have ENG S-OFF. Once your device has that read this thread to learn how to flash a radio.img
How to get ENG S-OFF:
Download the attached "easy S-OFF.zip" at the botton of this FAQ.
Extract to a folder of your choice.
Connect your phone to a computer (make sure you have USB Debugging enabled. Connect charge only!)
Open my "Desire HD easy s-off.exe", click "S-OFF it"! Allow possible SuperUser request on your phone.
There could be force closes after the process, just reboot and everything will be fine.
Done. (in bootloader it should now show ENG S-OFF)"
http://forum.xda-developers.com/showthread.php?t=965207
No doubt, still a great find. It's definitely a temp cwm fix, so use as necessary, just be careful and DO NOT unplug your phone while it's flashing!
ClearD said:
No doubt, still a great find. It's definitely a temp cwm fix, so use as necessary, just be careful and DO NOT unplug your phone while it's flashing!
Click to expand...
Click to collapse
For me, it was a permanent CWM fix
Use this at YOUR OWN RISK! I take no responsibility for bricked or ruined phones, I just posted this in hopes it might help out people having CWM issues.
I just put that in my first post, hopefully it will do it's job
I could get into cwm, no black-screen for me though. Still couldnt do radios. Used this and bam new radio....Thanks for the info.
Lol Cali, remind me to "thank" you tomorrow I've been trying all night, but I'm at the 24 hr limit for "thanks". I appreciate the post update, and this really is a great find. I can't stress that enough lol. In the right hands, an engineering HBOOT is great.
btdt13 said:
I could get into cwm, no black-screen for me though. Still couldnt do radios. Used this and bam new radio....Thanks for the info.
Click to expand...
Click to collapse
You are very welcome!
ClearD said:
Lol Cali, remind me to "thank" you tomorrow I've been trying all night, but I'm at the 24 hr limit for "thanks". I appreciate the post update, and this really is a great find. I can't stress that enough lol. In the right hands, an engineering HBOOT is great.
Click to expand...
Click to collapse
No problemo, as the Terminator would say
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.
Well I decided to jump the hoop and go for rooting my mt4g slide. Was doing great and unlocked it using the lovely All-In-One tool kit and couldn't get the phone to show S-off. I figured I needed to get this done before installing a rom's as I tried 2 different ones and neither would work. Tried a few different things and still wouldn't work to get S-off. Long story short, now I'm in a boot loop where the phone automatically goes into the boot loader. It will start up and show the mytouch splash screen before going into the loader. It will scan the sdcard for files and say there isn't a image etc and go back to the main boot loader screen. I can't do anything beyond that. I hit recovery, factory reset, and nothing. Tried putting roms and see if it would out of the blue read one.
It's my fault for taking the risk but adding a bit of insult to my injury is my back up phone, G1, won't even turn on now. So now I'm kind of phone less. Any suggestions on how to restore hboot?
1st of all WRONG FORUM!!!!!! This is for Development, not questions. That's what general is for. Second, there's a couple threads in General about this. Just hit search.
Magical Mods, may we please have this moved. Thanks.
Sent from my MIUI V4
take out your sdcard and use an adapter to put a stock PG59IMG.zip on your sdcard (make sure its named PG59IMG.zip) and go back into the bootloader. It will confirm if you want to install the zip and in 10 mins you'll be back on stock. Oh and ^ plus one please next time post in general as this has nothing to do with developing.
wow ya'll so testy today. I found the roms and info here in development forgive me for asking the question when something goes wrong on the programing side. One would think developers/programers would be helpful when the thread isn't how great the device is or what the bench marks are. Take a chill pill people.
fsured said:
wow ya'll so testy today. I found the roms and info here in development forgive me for asking the question when something goes wrong on the programing side. One would think developers/programers would be helpful when the thread isn't how great the device is or what the bench marks are. Take a chill pill people.
Click to expand...
Click to collapse
Thread reported just for the use of "take a chill pill."
blackknightavalon said:
Thread reported just for the use of "take a chill pill."
Click to expand...
Click to collapse
Yes, the correct terminology is 'Take a chill pill, Bill.
Can't get chill without the Bill.
fsured said:
wow ya'll so testy today. I found the roms and info here in development forgive me for asking the question when something goes wrong on the programing side. One would think developers/programers would be helpful when the thread isn't how great the device is or what the bench marks are. Take a chill pill people.
Click to expand...
Click to collapse
Sorry I wasn't "helpful". I'll do better to assist you next time....or just ignore it
I can't help you and I expect you to get a satisfactory answer.
fsured said:
wow ya'll so testy today. I found the roms and info here in development forgive me for asking the question when something goes wrong on the programing side. One would think developers/programers would be helpful when the thread isn't how great the device is or what the bench marks are. Take a chill pill people.
Click to expand...
Click to collapse
XMC, a Dev. He helped you, we where all noobs once. You should check out the "Welcome to XDA Video". Just follow the Rules. That's all, follow the rules.
Sent from my MIUI V4
To supplement what Agent said the appropriate section for this would be the General section.
Additionally the development area is where devs post new roms, tools and hacks. Users can add observations to these threads to further development.
Hastily spouted for your befuddlement
fsured said:
Well I decided to jump the hoop and go for rooting my mt4g slide. Was doing great and unlocked it using the lovely All-In-One tool kit and couldn't get the phone to show S-off. I figured I needed to get this done before installing a rom's as I tried 2 different ones and neither would work. Tried a few different things and still wouldn't work to get S-off. Long story short, now I'm in a boot loop where the phone automatically goes into the boot loader. It will start up and show the mytouch splash screen before going into the loader. It will scan the sdcard for files and say there isn't a image etc and go back to the main boot loader screen. I can't do anything beyond that. I hit recovery, factory reset, and nothing. Tried putting roms and see if it would out of the blue read one.
It's my fault for taking the risk but adding a bit of insult to my injury is my back up phone, G1, won't even turn on now. So now I'm kind of phone less. Any suggestions on how to restore hboot?
Click to expand...
Click to collapse
"tried a few different things" to get S-Off?
There are two ways of getting S-off. One is done with Revolution if your HBOOT is earlier than 1.45. The other is juopunutbear if your HBOOT is 1.45. Did you check your HBOOT version before "trying a few things"?
Did you read the instructions for the all-in-one toolkit? Or possibly just follow the steps in order in the program? It's specifically designed so you don't need s-off.
I'm assuming you must have flashed CWM recovery since you said you did a factory reset. Did you do Juopunutbear or revolution, or are you planning on leaving S-ON? If S-ON, Did you flash a kernel(boot.img) using the toolkit? If you can get into HBOOT and get into recovery, there's no reason you should need to revert to stock. However, if your plan is to continue doing steps before reading the instructions, you should probably revert to stock anyway before you really do brick your device.
This link will provide you everything you need to get your device running. Just follow the spteps from the beginning. If your bootloader is already unlocked from HTCDev, then start at the step directly after unlocking the bootloader.
http://forum.xda-developers.com/showthread.php?t=1532809
The toolkit worked well for me (even though it was my first attempt at anything), so I guess I'd echo that. It also matched with the step-by-step guides on stuff I found elsewhere in the forum. BUT there is a real difference in the method and order of things for the two hboots, hence KarriOn's questions.
However, having rooted and S-Offed, I then got a bit cocky and managed to end up in a not dissimilar position to you! Total panic, but I managed to get out by thinking through what I'd done, researching, and the cause and hence solution became clear. Took a night sleeping on it, and 2 hours.
what HBOOT?
Did you unlock the boot loader?
Did you get recovery on
Did you do a backup before going any further?
Sent from my myTouch_4G_Slide using xda premium
I followed the all in one tool for everything. I've finally been able to get into cwm recovery. For awhile it wouldn't and I gave up for the night. Came back yesterday morning to tinker with it more and it worked. I've tried flashing the superSu.zip file in cwm and after it reboots it still reads s-on. But either way I can't get the phone to do anything other than boot into the bootloader screen. I'm going to check out the link about 2 posts up and tinker with it after work. Thanks for the replies!
http://forum.xda-developers.com/showthread.php?t=1532809[/QUOTE]
Oh yeah, that is the tread I used and the tool. After getting unlocked from HTC I tried flashing a rom and it wouldn't work. Figured I needed to get s-off for roms also. That is where my error started.
fsured said:
http://forum.xda-developers.com/showthread.php?t=1532809
Oh yeah, that is the tread I used and the tool. After getting unlocked from HTC I tried flashing a rom and it wouldn't work. Figured I needed to get s-off for roms also. That is where my error started.
Click to expand...
Click to collapse
You don't need S-Off for ROMs to work. It sounds like you didn't flash a kernel after installing a ROM. The instructions on doing this are listed in the all-in one tool thread, the "flash ics roms with s-on" thread, and even on the all-in one tool interface itself.
fsured said:
I followed the all in one tool for everything. I've finally been able to get into cwm recovery. For awhile it wouldn't and I gave up for the night. Came back yesterday morning to tinker with it more and it worked. I've tried flashing the superSu.zip file in cwm and after it reboots it still reads s-on. But either way I can't get the phone to do anything other than boot into the bootloader screen. I'm going to check out the link about 2 posts up and tinker with it after work. Thanks for the replies!
Click to expand...
Click to collapse
Flashing SuperUser won't get you to S-Off. Hasoon2000 has two different toolkits. One that will guide you through the rooting process and the other on how to gain S-Off using the Juopunutbear method. Having S-Off isn't necessary to root but it will take a few extra steps to flash a different ROM with S-ON. I was too much of a chicken to try the S-Off method since there is some risk involved but several have reported that it worked successfully for them.
Ok before I get skewered by the tenured members of this esteemed site, I just wanted to say that I did my research as many of you suggested, and I feel like I've read every thread about the following topic to no avail, my phone is in the same state, I digress;
Like many on here before me, I have been handed the "white screen of death" on my HTC Inspire 4G. Some call it a soft brick, even though that's a frowned upon term. Either way, I have it and I'd really like to get rid of it. I can access my Hboot no problem, my phone is S-OFF, so that's not an issue. I tried running an RUU on here to update the image, but when it rebooted, the HTC white screen of death reappeared. Tried running the PD98IMG.ZIP image and reflashing a custom pre-rooted stock rom, didn't work.
Threads I've tried:
http://forum.xda-developers.com/showthread.php?t=1286832
http://forum.xda-developers.com/showthread.php?t=1390677
http://forum.xda-developers.com/showthread.php?t=1396229
These were the three that ware most similar to the problem I had I felt like, yet neither had the solution I was looking for. Clearly, the phone isn't bricked since I can get into the HBoot, but besides that, I'm stuck. For all I know, I'm a complete idiot and missing a vital step, but I'm almost at my wits end and I really just need my smartphone back. Any assistance, regardless of how condescending it may be, will be received with immense gratification if it indeed helps my problem. Thank you, and please help me .
And little more info, please. Can you get into recovery from hboot? If so, is it a stock or custom recovery? What version of hboot are you running?
This thread will probably be moved to Q&A. Stick with it and we will try to help.
Sent using the power of the dark side.
fballplyr92 said:
Ok before I get skewered by the tenured members of this esteemed site, I just wanted to say that I did my research as many of you suggested, and I feel like I've read every thread about the following topic to no avail, my phone is in the same state, I digress;
Like many on here before me, I have been handed the "white screen of death" on my HTC Inspire 4G. Some call it a soft brick, even though that's a frowned upon term. Either way, I have it and I'd really like to get rid of it. I can access my Hboot no problem, my phone is S-OFF, so that's not an issue. I tried running an RUU on here to update the image, but when it rebooted, the HTC white screen of death reappeared. Tried running the PD98IMG.ZIP image and reflashing a custom pre-rooted stock rom, didn't work.
Threads I've tried:
http://forum.xda-developers.com/showthread.php?t=1286832
http://forum.xda-developers.com/showthread.php?t=1390677
http://forum.xda-developers.com/showthread.php?t=1396229
These were the three that ware most similar to the problem I had I felt like, yet neither had the solution I was looking for. Clearly, the phone isn't bricked since I can get into the HBoot, but besides that, I'm stuck. For all I know, I'm a complete idiot and missing a vital step, but I'm almost at my wits end and I really just need my smartphone back. Any assistance, regardless of how condescending it may be, will be received with immense gratification if it indeed helps my problem. Thank you, and please help me .
Click to expand...
Click to collapse
Can you get into recovery? If not, follow the Ace Think Tank guide on post #7 starting on the bottom of page 9, the section "S-OFF no recovery," to get a recovery back; then use that recovery to flash a ROM. If so, just flash a ROM from recovery.
bananagranola said:
Can you get into recovery? If not, follow the Ace Think Tank guide on post #7 starting on the bottom of page 9, the section S-OFF no recovery, to get a recovery back; then use that recovery to flash a ROM. If so, just flash a ROM from recovery.
Click to expand...
Click to collapse
This
Sent from my Inspire 4G using xda premium
Please post all questions in the Q & A section. Thanks. Thread moved.
Sent from my Galaxy Nexus using Tapatalk 2
Hello Guys.... M really new to XDA as well as HTC devices.... had a Sony and a Samsung before... Seems HTC is entirely different!
i just needed some expertise on following questions i had in my mind:
1) i have bought an HTC one xl (snapdragon version) that is unlocked.. will a "FACTORY DATA RESET" or flashing of a custom rom lock it again??
(does this phone need to have an unlocked bootloader)
2) what is the best and most secure way to root it? (link to any guides will be much appreciated)
3) things that can possibly brick the phone and i should AVOID?
4) the best custom rom in terms of speed?
5) any necessary mods for stock rom?
PLEASE i neeed some help!
You need to find the correct root method for your current hboot. If your phone is the at&t model, click the link in my signature, then find the right root method for you. If it's not, just go to htcdev.com and unlock your bootloader, then you can flash TWRP recovery, and flash a custom ROM.
Sent from my Evita
1)Factory data reset in bootloader just clears the /data partition but does not function correctly at all if you unlock the bootloader for this device.
The only way to relock the bootloader is to do fastboot oem lock
2)As timmaaa said, follow the index. You want to unlock bootloader, flash ROM with root, get supercid, s-off.
The catches are:
AT&T devices need to gain temp root to get supercid before they can unlock bootloader.
Newer HTC updates eg new 3.17 and 5.xx updates may prevent you from getting supercid even with root, you may need to investigate downgrading things to get supercid.
With an unlocked bootloader, you are well on your way. You should check if you have supercid and if you are s-off.
3)Do not attempt to install HTC updates after you modify the phone. OTA is particular can be dangerous but even RUU's can be dangerous under some circumstances. OTA have many rules which are easy to follow once you have an idea of what they do, best bet is to just ignore them, RUU is fine if you have both s-off and supercid.
4)You can not ask that question and we can not answer it. It is unfair for someone to rate ROM's over other ROMs as the devs put a lot of effort in to these things. Each ROM is special in its own way, you need to check them out yourself.
A typical vibe is HTC stock ROMs will typically give the most reliable experience, eg less crashes, less bugs, etc, but tend to also lack features.
Unlocking your phone and modding it requires you to read and understand what you are getting yourself in to. It is not a perfect smooth ride, it is not for the average "non technical" user.
5)Not really
twistedddx said:
1)Factory data reset in bootloader just clears the /data partition but does not function correctly at all if you unlock the bootloader for this device.
The only way to relock the bootloader is to do fastboot oem lock
2)As timmaaa said, follow the index. You want to unlock bootloader, flash ROM with root, get supercid, s-off.
The catches are:
AT&T devices need to gain temp root to get supercid before they can unlock bootloader.
Newer HTC updates eg new 3.17 and 5.xx updates may prevent you from getting supercid even with root, you may need to investigate downgrading things to get supercid.
With an unlocked bootloader, you are well on your way. You should check if you have supercid and if you are s-off.
3)Do not attempt to install HTC updates after you modify the phone. OTA is particular can be dangerous but even RUU's can be dangerous under some circumstances. OTA have many rules which are easy to follow once you have an idea of what they do, best bet is to just ignore them, RUU is fine if you have both s-off and supercid.
4)You can not ask that question and we can not answer it. It is unfair for someone to rate ROM's over other ROMs as the devs put a lot of effort in to these things. Each ROM is special in its own way, you need to check them out yourself.
A typical vibe is HTC stock ROMs will typically give the most reliable experience, eg less crashes, less bugs, etc, but tend to also lack features.
Unlocking your phone and modding it requires you to read and understand what you are getting yourself in to. It is not a perfect smooth ride, it is not for the average "non technical" user.
5)Not really
Click to expand...
Click to collapse
thanks a lot man....
i appreciate since u elaborated on every aspect...!! =)
btw m sorry if i am wrong but what i meant in my first question was does rooting or a reset or flashing affect the "sim unlock" (or the factory unlock or jailbreak)? [the vendor says its unlocked to work on all networks]
besides you are right i was wrong with the approach.. every developer puts in a lot of efforts in ROM development and its not fair to rate it!
the only reason i would possibly root is to remove bloatware.
and rvhaval
timmaaa said:
You need to find the correct root method for your current hboot. If your phone is the at&t model, click the link in my signature, then find the right root method for you. If it's not, just go to htcdev.com and unlock your bootloader, then you can flash TWRP recovery, and flash a custom ROM.
Sent from my Evita
Click to expand...
Click to collapse
thanks i will surely go through that!
the thing that actually haunts me is this phone doesn't have a removable battery so if anything goes wrong and i have some boot loops i would be in a very hopeless situation.. So I need to go through everything!
Sonone said:
thanks i will surely go through that!
the thing that actually haunts me is this phone doesn't have a removable battery so if anything goes wrong and i have some boot loops i would be in a very hopeless situation.. So I need to go through everything!
Click to expand...
Click to collapse
You can simulate a battery pull by holding volume down and power buttons together. When you do this the button lights will start flashing, when they stop flashing you can let go of the power button but keep holding volume down. This will take you to the bootloader.
Sent from my Evita
Sim unlock is unrelated to bootloader unlock, ROM flashing, etc etc.
The sim unlock should survive most everything you will do. Although I have not tested as my device was never locked.
thanks!! i hope it survives!
timmaaa said:
You can simulate a battery pull by holding volume down and power buttons together. When you do this the button lights will start flashing, when they stop flashing you can let go of the power button but keep holding volume down. This will take you to the bootloader.
Sent from my Evita
Click to expand...
Click to collapse
that sounds good!!
the people on this device forum seem very helpful:good::angel::highfive:
timmaaa said:
You can simulate a battery pull by holding volume down and power buttons together. When you do this the button lights will start flashing, when they stop flashing you can let go of the power button but keep holding volume down. This will take you to the bootloader.
Sent from my Evita
Click to expand...
Click to collapse
that sounds good!!
the people on this device forum seem very helpful:good::angel::highfive:
so Timaaaa i have done the following...
please i would like to give you a brief update of the following things..
1)Unlocked Bootloader
2)i have s-off
3)supercid is 11111111
4) installed twrp version 6.xx.xxx
5)my radio is 1.30a.32.45.18
6)hboot is 2.15.0000
7)device is now rooted
so m i good to flash custom roms like Cm,PAC,SLIM?
That all looks fine apart from two things.
The TWRP version you mentioned doesn't look right, the latest TWRP is 2.6.3, could you double check that?
Also, your hboot is 2.15 which will be ok for flashing cm, but I think PAC still has a restriction to hboot 2.14 and I'm not sure about Slim. Hboot 2.15 is perfect for running the latest Sense 5 ROMs though.
Sent from my Evita
timmaaa said:
That all looks fine apart from two things.
The TWRP version you mentioned doesn't look right, the latest TWRP is 2.6.3, could you double check that?
Also, your hboot is 2.15 which will be ok for flashing cm, but I think PAC still has a restriction to hboot 2.14 and I'm not sure about Slim. Hboot 2.15 is perfect for running the latest Sense 5 ROMs though.
Sent from my Evita
Click to expand...
Click to collapse
As u said i checked again its 2.5.0.0 how to update twrp?
it actually works well......
btw is it possible to change hboot version?
and thanks as always!
TWRP 2.5 is full of bugs, you should update to at least 2.6, here's how:
Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you'll have a much better version of TWRP.
You can upgrade and downgrade your hboot, there's a thread on our forum somewhere but I can't remember where, just search downgrade hboot within our forum and it should appear.
Sent from my Evita
did that... btw when i installed it... and tried to clear the cache partition and dalvik cache it said it "failed"...!!
Btw also i wanted to know..
since i had a Samsung before flashing a rom just meant copying the zip file and installing it through cwm followed by a resets (if needed)
is this the same way for HTC ONE xl. or like Sony do i have to first unzip the downloaded rom.. and flash the "boot.img" separately??
So even after putting TWRP 2.6 on your phone you get a failed message when trying to wipe?
With this phone all you need to do is copy the ROM zip onto the phone and install it, you are s-off so you don't need to worry about flashing the boot.img via fastboot.
Sent from my Evita
i tried it again mate and it works absolutely fine!
yay!!!! :laugh: flashing roms will be great!:good:
wish if we had a dual boot interface like we have on our computers installing every single app again becomes so inconvenient!:fingers-crossed:
btw m really sorry to bombard you with all the quetions:silly: i just needed to ask one thing that do we have a list of bloatware apps which are safe to remove..
i did google it but then it was very specific to carrier bloatware. as i have got an unlocked version there are no carrier bloatware apps but i do have some apps which seem useless at the moment.. i did freeze a few... but it would have helped if there would have been a list!
I'd love a dual boot setup too. In terms of bloatware, you can remove a fair bit but be careful while doing it. Removing anything that is integral to the running of the ROM will cause problems. Things like Stocks, Picasa, Talkback can be removed if you don't use them. Obviously don't remove anything like Phone or Messages lol.
Sent from my Evita
timmaaa said:
I'd love a dual boot setup too. In terms of bloatware, you can remove a fair bit but be careful while doing it. Removing anything that is integral to the running of the ROM will cause problems. Things like Stocks, Picasa, Talkback can be removed if you don't use them. Obviously don't remove anything like Phone or Messages lol.
Sent from my Evita
Click to expand...
Click to collapse
ya i wont ripp off phone or system ui etc :laugh:
m thinking of flashing clean rom 7.0.1 but den it seems it has an at&t bootscreen or something like that during start up which m not very inclined to have....
so i will stick to the rules not asking for any advice on which rom is preffered as every one of dem i great and i will check them out one by one.
I haven't tried the new Cleamrom, it's a very stock kind of ROM which isn't really my flavour but it's a very popular ROM.
Sent from my Evita