Related
Hi All,
So I DID do a search, but I didn't find anything that seemed to match perfectly, or that would work for sure on the TB.
So what I have is the following:
rooted Thunderbolt running STOCK OTA update Gingerbread with clockworkMod recovery. So basically:
Android Version: 2.3.4
HTC Sense Version: 2.1
Software number: 2.11.605.3
PRI Version: 4.41_002, 1.64_002
PRL Version: 15027
ERI Version: 5
Kernel version: 2.6.35.13-nerozehl-dream-2.9.0-beta_SENSE
Baseband version: 1.48.00.0906w_1, 0.01.78.0906w_2
Build number: 2.11.605.3 CL147855 release-keys
Ok Here's the problem: my USB connection doesn't work (plug into PC, choose as mount to disk drive). This issue DID NOT HAPPEN WITH THE PHONE IN STOCK EVERYTHING, so I'd like to go back to the state. I need a fully working phone in case I decide to trade it in for a bionic :-(
Can someone please offer a noob link to restoring to stock that will work on both stock gingerbread 2.3.4 and the Thunderbolt?
Thanx for the help!
Can't really even tell you where to start until we know your bootloader.
How can I find out?
loonatik78 said:
Can't really even tell you where to start until we know your bootloader.
Click to expand...
Click to collapse
Thanx for the response. Please pardon my n00b-iness, but how do I find out which boot loader I'm on? Is this something I can find out in Settings or would I have to boot into recovery?
Thanx.
if the issue is not being able to get files on your phone via USB, there's always dropbox(it's free)
First things first, as posted above, you need to find out what bootloader you have.
First, you need to get into your bootloader. You can do so by doing the following steps:
1. Power down the devices.
2. Simultaneously hold down the volume down button and the power button until the screen turns on. This is the bootloader.
Now look at the second line of text. I should look like: HBOOT- with some numbers.
The numbers should be one of the following: 1.04.0000 or 1.05.0000
Also look at the top line and see if it says S-OFF. If it does, then this will be very easy.
If it's S-OFF simply download the ruu from here: http://forum.xda-developers.com/showthread.php?t=1312193
Put it on the root of your sdcard (make sure it's named PG05IMG.zip)
Power down the device and again boot into the bootloader. It should automatically start loading the RUU, just follow the directions on screen. Once that is done, you are 100% stock on the latest OTA.
So check what bootloader you have. If you DON'T have s-off, post back or shoot me a PM and I'll try to help you further.
I would double check your USB cable and maybe try a different USB port. On my home pc (old windows xp) the USB ports on the front don't work but the ones on the back work. Jut a thought before you go through all the work to unroot.
tomjhansen said:
I would double check your USB cable and maybe try a different USB port. On my home pc (old windows xp) the USB ports on the front don't work but the ones on the back work. Jut a thought before you go through all the work to unroot.
Click to expand...
Click to collapse
Very good point. Definitely a good starting troubleshooting step.
Sent from my HTC ThunderBolt powered by KillaSense 3.2
Thanx for the responses all.
As for the USB connectivity issues, please disregard. Its a Windows 8 issue. Works fine with Windows 7 (yes I'm kicking myself in the head for that one)
H-Boot info as follows:
MECHA XD SHIP S-OFF
HBOOT-6.04.1002
MICROP-/
RADIO-1.48.00.0906w_1
eMMC-boot
Feb 23 2011,20:42:55
I have also tried flashing the supposed "final" GB bits here --> http://forum.xda-developers.com/showthread.php?t=1312193
but now all that happens is I ONLY get 1X data that comes and goes (it does NOT activate neither 3G or 4G). I even tried *#*#4646#*#* and chose CDMA/LTE auto and that did NOT help.
Out of desperation I also tried flashing the following radios from --> http://forum.xda-developers.com/showthread.php?t=1048128&highlight=radio
•From the 2.11.605.3 RUU:
•CDMA: 1.48.00.0906
md5: c6a5a9eee78e0f33267fa80ced3c49b8
•LTE: 0.01.78.0906
md5: 6f33809cf2253c38a3c6bb970f030eee
and STILL either no data, or 1X.
I'm at a loss here. How the heck do you return the TB to FULL stock everything (ready for a warranty or a sale for example)?
Thanx!
You used revolutionary to get s-off. That is a protected bootloader that prevents an ruu from replacing it. You will have to follow certain instructions that can be found In the development section. I'd post a link but I'm on my phone. Just look for a "return to stock guide/how to" thread. It will have instructions for revolutionary users.
Sent from my HTC ThunderBolt powered by KillaSense 3.5.0
orkillakilla said:
You used revolutionary to get s-off. That is a protected bootloader that prevents an ruu from replacing it. You will have to follow certain instructions that can be found In the development section. I'd post a link but I'm on my phone. Just look for a "return to stock guide/how to" thread. It will have instructions for revolutionary users.
Sent from my HTC ThunderBolt powered by KillaSense 3.5.0
Click to expand...
Click to collapse
Thanx! Much appreciated. Do you know if this would solve the radio issue as well or just the bootloader?
OOps double post. Please disregard
shassouneh said:
Thanx! Much appreciated. Do you know if this would solve the radio issue as well or just the bootloader?
Click to expand...
Click to collapse
it will definitely fox your bootloader issue. As for the radio I'm not sure. Try flashing an earlier gb radio and see of that works. Also keep in mind that the battery cover has part of the antenna built into it, so be sure that cover is snapped on all the way.
Sent from my HTC ThunderBolt powered by KillaSense 3.5.0
orkillakilla said:
it will definitely fox your bootloader issue. As for the radio I'm not sure. Try flashing an earlier gb radio and see of that works. Also keep in mind that the battery cover has part of the antenna built into it, so be sure that cover is snapped on all the way.
Sent from my HTC ThunderBolt powered by KillaSense 3.5.0
Click to expand...
Click to collapse
You're a life saver man. ESPECIALLY the bolded above
I un-rooted and restored to stock using --> http://forum.xda-developers.com/showthread.php?t=1310014
in caps for emphasis (not yelling) --> THANK YOU SO MUCH EVERYONE ON XDA! MUCH APPRECIATED!
shassouneh said:
You're a life saver man. ESPECIALLY the bolded above
I un-rooted and restored to stock using --> http://forum.xda-developers.com/showthread.php?t=1310014
in caps for emphasis (not yelling) --> THANK YOU SO MUCH EVERYONE ON XDA! MUCH APPRECIATED!
Click to expand...
Click to collapse
No problem.
When I first bought the thunderbolt, the Verizon rep told me the phone wouldnt work right if the cover wasn't on, and I didn't understand until I look at the little metal pieces on it, and o realized that it was part of the antenna.
Glad everything worked out for you!
Sent from my HTC ThunderBolt powered by KillaSense 3.5.0
A few months ago I, posted a thread with a similar idea in mind however, the only answer I got was (I'm paraphrasing) "Why go back to stock,the custom ROMS are much better anyways". Well the time has come where I figure out the "why?". Yesterday I brought the phone into Wind for a check of why it's not sending MMS messages when the data is on (strangely enough it turns data on while sending the mms but, that's a story for another time). The people at Wind refused to look at my phone and told me to come back when it has stock firmware. (because, obviously I haven't returned to stock yet). Now from what I understand, from doing some research today on the forums, that the HTC Amaze (Wind Variant) has some weird software issues upon flashing a T-Mobile based ROM which I can link back to Speed Rom. So, I do the standard "Relock the bootloader and run the RUU.exe" and it just comes up with an error saying my hboot is the wrong version. The forums are pretty blank on ways to get around this (well besides going S-OFF which is a problem considering I need to bring my phone in to get the MMS issue checked. Also, I don't have that level of confidence in myself to insure I don't destroy my phone when going s-off). So, I was wondering if anyone has a fix for the issue. I'm confident that someone could possibly help me with my issue. (PS my current ROM is the latest Cyanogenmod 10 nightly, and I'm using 4ext recovery on the Amaze/Ruby).
Hope, I can get this issue resolved and thank you for helping me out with what ever problems I've had on my journey with this phone.
P.S: I didn't mean to double post the same question it's just I really needed this problem solved. I hope you can forgive me. (I fully understand if I can't return to stock under these circumstances.)
It's funny, I'm kind of in the same boat, except for 2 "minor" differences:
1) The "Smart Flash" on 4EXT never worked for me (and has consistently corrupted my internal SD card, but been able to fix it each time), so I have S-ON yet
2) I've rooted the phone itself and unlocked the bootloader, but the HBOOT is 1.93.0002, and from what I've seen, the latest firmware patch is .2222 although that really shouldn't matter
This is my 2nd HTC Amaze, and the first time I've gone through the rooting and that, took me at most an hour to complete, including time spent choosing a CMOD (I ended up with 7). This time around...I'm practically pulling my hair out because I cannot perform the S-OFF via Linux (LiveCD of course) nor starting from "square 1". I seem to be in limbo with 4EXT.
I installed Viper Amaze 1.7.2, but continually got stuck on the boot screen. Further investigation revealed that I needed to superCID the phone, which in turn would be to S-OFF first.
Additionally, I've downloaded and flashed the "stock ICS" ROM (since that was my stock ROM to begin with, naturally upgraded ICS), renamed to PH85IMG.zip yadda yadda. It recognizes and loads, but never "updates", more or less does anything after the loading bar on the bootloader.
So, just to try how much I've dug myself in with this, I've downloaded and tried 2 other ROMS, both saying "bad" (no status 7 error like the RUU flash).
I want to try out the Viper Amaze ROM since so much work and effort went into it, and it seriously looks awesome, but because my original tool that I used (HTC Super Tool) didn't require me all of these extra steps (and I didn't remember the program until now), I want to return back to stock so I can start over in a sense and complete those couple of steps that I inadvertently missed. I really feel like I'm missing something stupid.
Out of 7 Android phones that I've completed the custom ROM setup, it has to be this phone...
Anyways, tl;dr here's what I got:
Bootloader:
**Unlocked**
Ruby PVT SHIP S-ON RL
HBOOT 1.93.0002
eMMC-boot
Starting ROM: Wind Mobile ICS 4.0.3 Stock ROM
End ROM: Viper Amaze 1.7.2
Where I'm At: 4EXT, Status 7 error upon stock ROM flash. No other custom ROM works. PH85IMG.zip doesn't seem to do much upon loading via bootloader.
darkandshadow said:
Bootloader:
**Unlocked**
Ruby PVT SHIP S-ON RL
HBOOT 1.93.0002
eMMC-boot
Starting ROM: Wind Mobile ICS 4.0.3 Stock ROM
End ROM: Viper Amaze 1.7.2
Where I'm At: 4EXT, Status 7 error upon stock ROM flash. No other custom ROM works. PH85IMG.zip doesn't seem to do much upon loading via bootloader.
Click to expand...
Click to collapse
I actually have the same HBOOT version as you! I have never met a device which had more difficulties going back to stock than the Wind variant of the Amaze. Anyway best of luck on your issue, and just try to remember me if you find a way back to stock. I guess we are on the same boat and the Wind isn't helping us out *Budum Tssss* . (BTW if you manage to make it back to stock I suggest you use hasoon2000's toolkit for the Amaze. It's a good toolkit for the Amaze.)
Megapead said:
I actually have the same HBOOT version as you! I have never met a device which had more difficulties going back to stock than the Wind variant of the Amaze. Anyway best of luck on your issue, and just try to remember me if you find a way back to stock. I guess we are on the same boat and the Wind isn't helping us out *Budum Tssss* . (BTW if you manage to make it back to stock I suggest you use hasoon2000's toolkit for the Amaze. It's a good toolkit for the Amaze.)
Click to expand...
Click to collapse
I managed to install the Viper Amaze. I went back, relocked the bootloader, got a new
ID token unlock key, and reflashed (the hell out of) everything. It actually worked.
As for the Wind Rom push back, try the EXE found here on XDA:
http://forum.xda-developers.com/wiki/HTC_Amaze_4G/ROMs
darkandshadow said:
I managed to install the Viper Amaze. I went back, relocked the bootloader, got a new
ID token unlock key, and reflashed (the hell out of) everything. It actually worked.
As for the Wind Rom push back, try the EXE found here on XDA:
http://forum.xda-developers.com/wiki/HTC_Amaze_4G/ROMs
Click to expand...
Click to collapse
I tried, that EXE seems to only be for update from Gingerbread purposes or, was broke after I flashed a T-Mobile ROM on the device.
Hey everyone. After 22 logged hours of work on this phone and looking everywhere on XDA and AndroidForums I could really use some help guys. :crying: Since I cannot post links, please bear with my references.
HTC Evo 3D Shooter s-on hboot 1.58.0000 | device:HT17JHX02410 cid:SPCS_001 [sprint] mainver:2.95.651.6
Current status: stock rom successfully reloaded, relocked w/ security warning, stock rom stopped loading after relock. I can access 4ext as well as make commands from adb.
My goal is to flash PACMAN v 23.0.0 rom to my phone. I believe pacman uses Android 4.3. I tried flashing with 4ext, cwm, and twrp. As I recall the problem was an "error 7" across the board. Trying to solve this has lead me down the rabbit hole. I'm not even sure I'm on the right track anymore. I tried deleting the "assert getprop" lines from the beginning of the updater-script file as suggested by several users here, but that lead only to abortions. It may have something to do with 7zip asking whether to overwrite already existing files during extraction? I'm currently trying to return the phone to stock condition so I can downgrade to hboot 1.4 and get s-off, thus allowing me to flash PACMAN. This method was obtained from Unknownforce, Closeone, and RamJet73 all found on XDA.
Returning the phone to stock [in order to brick it via Unknownforce] has been a hassle because every tutorial requires that I lock the phone and then run the RUU update utility. I have tried several versions of this utility and they all drop the connection to my phone after restarting bootloader with an Error 170 [or 171]. There are several reasons for this error and one possible reason is that the software is incompatible. I think this is due to my mainver being 2.95 as opposed to 2.89 or lower. This is why I needed to find a .zip for the stock rom that would work, flash SetMainVersionLow, flash the rom zip, and then lock, bringing me to where I am now, which is a phone that will boot to bootloader and nothing more. This final method with setmainversionlow was obtained from remanifest on AndroidForums.com and I began using it because they mentioned something about 2.95 compatibility or something.
I can still lock/unlock the phone easily and flash any rom i wish, providing it is compatible. Where have I gone wrong? Is the PACMAN rom worth all of this!?
Thanks, all help is greatly appreciated.
-a
Update progress...
i can no longer get a recovery to load [4ext, twrp, cwm] and i think this is because i used a wonky verson of CWM. some have said CWM and htc 3vo don't play nicely together. all i have now is bootloader and adb. no rom loads either, just white screen with green HTC logo until battery dies. recovery programs flash successfully from adb but do not start.
my mainver has been reset to 1.00.000.0 and phone is relocked so i was trying to forget about the recovery and run a RUU. according to RamJet these are the two required items for running RUU. i've tried a 1.13 version as well as a 2.89 version. both of them act the same way as before -- immediately after the phone comes back and the program reads "erase user data" for one second, it fails and give me a 171 error.
please help. i'm a noob but i've looked EVERYWHERE for answers to these problems. if you have links to solutions i would appreciate that as well but i'd put money down that i've been there before.
i will never accept an OTA update again! all i need is hboot 1.4 and i'll be golden! how frustrating
Did you unlock again before trying to flash a recovery?
AFAIK there is no ruu that'll work for your phone until you get s off.
Sent from my Evo 3D CDMA using xda app-developers app
---------- Post added at 06:27 PM ---------- Previous post was at 06:25 PM ----------
Short story
You need to get recovery
Then you need to flash a ROM that works on 1.58 or 1.4/1.50 and then you can get s off and downgrade your hboot and flash pac
This is more updated
http://forum.xda-developers.com/showthread.php?t=2539241
Sent from my Evo 3D CDMA using xda app-developers app
it was a good call, but after unlocking again, recovery will still not start. i tried to erase the recovery flash partition but adb said that was not allowed. I have bootloader and adb, the ability to lock/unlock the phone, and flash recoveries unsuccessfully it would seem. there's got to be something that will fix this...
hanger-on said:
it was a good call, but after unlocking again, recovery will still not start. i tried to erase the recovery flash partition but adb said that was not allowed. I have bootloader and adb, the ability to lock/unlock the phone, and flash recoveries unsuccessfully it would seem. there's got to be something that will fix this...
Click to expand...
Click to collapse
The 1.58 bootloader apparently changes some formats in an incompatible way (I'm sure purely by chance and not to mess with custom roms).
This is what I did, alternatively there's this thread with alternate methods (more designed for windows I think).
Normal disclaimer: This is (to the best of my recent memory) what I did after mucking up my E3D. Follow at your own risk, my memory, your phone, or anything else could be faulty and you could permanently brick your phone trying the following steps.
Assuming you're CMDA and S-ON still:
If you need to fix your hboot/etc download the latest (2.89) PG86IMG.zip
Download the 1.13 PG86IMG.zip
Download SetMainVersionLow.zip (I think you already have that).
Make sure you have adb and fastboot installed and working.
Make sure you're at a stable hboot with a custom recovery.
If not flash the 2.89 RUU (see flashing RUU below).
Reunlock and apply custom recovery if needed.
Run SetMainVersionLOW.zip from a custom recovery.
Before downgrading your hboot you should be (hboot 1.89, custom recovery, "fastboot getvar mainver" = 1.00.0000)
Downgrade your hboot to 1.4.something (Possibly like this)
Flash the 1.13 RUU to get a bootable system
Optionally, Revolutionary to get Revolutionary S-OFF
Optionally (CDMA ONLY), if you got S-OFF you may update the radio (the 1.13 RUU downgraded the radio too). I used the 1.06 version, the 1.09 may work as well but IIRC it was a VM leak so I just stuck with what I think is the latest Sprint image.
From here you should be able to install whatever recovery and ROM (As well as any other partition like radio, hboot, etc) that you like. Good luck.
Flashing RUU
Either use the windows exe (requires windows and a phone that boots correctly), or:
get to your fastboot/bootloader (vol down + power or "adb reboot bootloader")
fastboot oem rebootRUU
fastboot flash zip RUUFile.zip
fastboot reboot (back to bootloader if you want to).
OR
Put the zip on the root directory of the sdcard
Make sure it's named PG86IMG.zip (CaSe sEnSiTiVe)
reboot to a locked/relocked bootloader and apply the zip
Lots of credit to all the devs that made the tools, without whom I'd have been stuck on boring, outdated stock roms.
These steps collected from various xda posts and pieced together for my particular situation, including but not limited to:
http://forum.xda-developers.com/showthread.php?t=1563342
http://forum.xda-developers.com/showthread.php?t=1547695
http://forum.xda-developers.com/showthread.php?t=1889438
http://forum.xda-developers.com/showthread.php?t=1193101
http://forum.xda-developers.com/showthread.php?t=2074181
http://forum.xda-developers.com/showthread.php?t=1447839
http://forum.xda-developers.com/showthread.php?t=1627917
http://forum.xda-developers.com/showthread.php?t=1653777
These guides should provide more background on why/how to do certain steps, as long as being better formatted and complete.
Thanks and Thanks
btharper said:
The 1.58 bootloader apparently changes some formats in an incompatible way (I'm sure purely by chance and not to mess with custom roms).
Click to expand...
Click to collapse
Thank you SO MUCH for your time and effort! After four or five weeks of making my phone worse, I was planning on giving up at the end of this week. I will thoroughly read and then try your suggestions in the morning and update you as to what happens. I hope flashing the RUU as you have suggested works because at this point I cannot flash a recovery.
This is very much appreciated!
-a
hanger-on said:
Thank you SO MUCH for your time and effort! After four or five weeks of making my phone worse, I was planning on giving up at the end of this week. I will thoroughly read and then try your suggestions in the morning and update you as to what happens. I hope flashing the RUU as you have suggested works because at this point I cannot flash a recovery.
This is very much appreciated!
-a
Click to expand...
Click to collapse
No problem, having had the same thing happen I know the frustration, and while there are several, slightly different S-OFF guides, there are fewer guides for what to do when **** hits the fan. As long as your hboot works you can still flash signed RUU.zip files as above, and even the emmc recovery if it's bricked, a little more care is required once you get S-OFF though.
310 26345564
btharper said:
No problem, having had the same thing happen I know the frustration, and while there are several, slightly different S-OFF guides, there are fewer guides for what to do when **** hits the fan. As long as your hboot works you can still flash signed RUU.zip files as above, and even the emmc recovery if it's bricked, a little more care is required once you get S-OFF though.
Click to expand...
Click to collapse
last time i worked on the phone bootloader was working but not the recovery. now that the phone has been off for several days, spent the last day on the charger in anticipation of working on it this morning, and now it won't boot into bootloader [vol down + pwr]. the trouble began weeks ago after flashing a CWM recovery. everything i've done since then to recover the phone has made it worse.
i'm going to leave it charging for several more hours and come back to it later. if it won't boot into bootloader, is it bricked?
CURRENT STATUS: red charge light stays on indefinitely after unplugging; light goes out if battery removed; same reactions if charging via USB on computer or from AC adapter; charge light reanimates when plugged back in; will not boot; will not boot into bootloader; will not respond to ADB [device not found].
hanger-on said:
last time i worked on the phone bootloader was working but not the recovery. now that the phone has been off for several days, spent the last day on the charger in anticipation of working on it this morning, and now it won't boot into bootloader [vol down + pwr]. the trouble began weeks ago after flashing a CWM recovery. everything i've done since then to recover the phone has made it worse.
i'm going to leave it charging for several more hours and come back to it later. if it won't boot into bootloader, is it bricked?
CURRENT STATUS: red charge light stays on indefinitely after unplugging; light goes out if battery removed; same reactions if charging via USB on computer or from AC adapter; charge light reanimates when plugged back in; will not boot; will not boot into bootloader; will not respond to ADB [device not found].
Click to expand...
Click to collapse
What were the last few steps you had done? The only time my hboot didn't come on was when I had my case on slightly off and the buttons didn't hold down correctly (try reseating your case as a last resort and make sure you can feel the buttons being pressed), at one point during the process you have to intentionally brick your phone as noted to corrupt the hboot, as long as you're S-ON it's okay and there are plenty of warnings that you must be S-ON, and one point right after recovering from that step where it's noted that you have to give it some time (I eventually just went to bed for the night because it wasn't working and I wasn't lucid enough to get it anywhere else). So probably just try pulling/replacing the battery and booting up hboot again and hopefully it works. If the red charging light is solid and dimly illuminated when plugged in then the hboot is corrupt and you can proceed to that part of the guide anyway http://forum.xda-developers.com/showthread.php?t=1547695
As well, adb only works when booted to recovery or once the normal system is booted, fastboot only works during hboot or right after rebootRUU (which is actually a part of the hboot, at least on the shooter), and emmc_recovery (used during hboot downgrade)/ultimate recovery tool should work and be able to unbrick the phone. Failing that are you on windows or linux? (revolutionary and some of the hboot downgrade steps require or work best on linux, there's a livedisc (bootable CD/USB stick that won't reset anything on your computer) you can use for the process made by closeone for the hboot downgrade process but you can use for the full process I would think (I did the whole thing on linux since that's my OS of choice) http://forum.xda-developers.com/showthread.php?t=1563342
They replaced my phone. :laugh: At the risk of sounding like a lunatic, I still would like this phone's hboot downgraded with s-off. What I ultimately want is Android 4.1 so I can use the Themer app, or at least some ROM that is similarly simplistic. Speedy and Simple, isn't that what everybody wants? haha! HTC Sense is a fugly abomination as I'm sure many would agree, and the bloatware is simply maddening!
CURRENT STATUS: mainver 2.95.651.6 710RD | Android 4.0.3 | Factory Locked | hboot 1.58.0000 | s-on | no recovery | stock rom
brand new, basically
Would you suggest I begin with this tutorial by UnknownForce along with this toolkit by CloseOne? I collected hundreds of links and plenty of downloads for the previous phone and became lost in the woods with that.
hanger-on said:
They replaced my phone. :laugh: At the risk of sounding like a lunatic, I still would like this phone's hboot downgraded with s-off. What I ultimately want is Android 4.1 so I can use the Themer app, or at least some ROM that is similarly simplistic. Speedy and Simple, isn't that what everybody wants? haha! HTC Sense is a fugly abomination as I'm sure many would agree, and the bloatware is simply maddening!
CURRENT STATUS: mainver 2.95.651.6 710RD | Android 4.0.3 | Factory Locked | hboot 1.58.0000 | s-on | no recovery | stock rom
brand new, basically
Would you suggest I begin with this tutorial by UnknownForce along with this toolkit by CloseOne? I collected hundreds of links and plenty of downloads for the previous phone and became lost in the woods with that.
Click to expand...
Click to collapse
Good luck with it, my advice is lots of nandoid backups and make sure you've got all the tools you need ready. The whole process can be done with linux tools (including the RUU flash). Feel free to let me know if you have any more questions.
Any luck?
Any luck on the new phone?
btharper said:
Any luck on the new phone?
Click to expand...
Click to collapse
I've just been using a themer called Homepack Buzz, Go SMS Pro, and other assorted apps. The embedded Sprint apps are really annoying, and the interface of HTC sense is ugly and inefficient, but I'm switching to Verizon in a couple of months and getting a galaxy 4 anyway, so I'll just wait and toy with it instead.
I realized that this HTC is not worth my time and effort, as it's main function is portable music player. Thanks for checking back in
I'm not sure if Sprint is going to let me keep the phone, but if they do I'll probably post it on Ebay, as it is brand new.
hanger-on said:
I've just been using a themer called Homepack Buzz, Go SMS Pro, and other assorted apps. The embedded Sprint apps are really annoying, and the interface of HTC sense is ugly and inefficient, but I'm switching to Verizon in a couple of months and getting a galaxy 4 anyway, so I'll just wait and toy with it instead.
I realized that this HTC is not worth my time and effort, as it's main function is portable music player. Thanks for checking back in
I'm not sure if Sprint is going to let me keep the phone, but if they do I'll probably post it on Ebay, as it is brand new.
Click to expand...
Click to collapse
If you pay all the fees/fines you can keep the phone. If not the esn will be marked as bad and it wont work on sprint.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Oh. Thanks for the heads up.
Just spent 3 days trawling through guides and totally stuck.
I am on a stock HTC EVO 3D SHOOTERU purchased from ASDA in the UK with current details as follows:
Code:
VERSION.RELEASE: 4.0.3
BRAND: htc_europe
DEVICE: shooteru
MODEL: HTC EVO 3D X515m
OS.VERSION: 3.0.16-ge733189
BOOTLOADER: 1.53.0007
HARDWARE: shooteru
FINGERPRINT: htc_europe/htc_shooteru/shooteru:4.0.3/IML74K/385730.1:user/release-keys
ID: IML74K
TAGS: release-keys
USER: unknown
PRODUCT: htc_shooteru
RADIO: 11.77.3504.00U_11.25.3504.06_M
Rooted: false
May 22 2012, 01:06:07
I want to put KitKat on it, so I decided on Cyanogenmod 11 which requires:
Do not use superwipes
Required HBOOT : 1.49.xxxx
S-OFF
Radio/baseband : 11.77.3504.00P_11.25.3504.06_M get it from HERE
4ext recovery
Click to expand...
Click to collapse
My radio is 11.77.3504.00U_11.25.3504.06_M however some people say P and U are both OK. For example, LiquidSmooth, apparently based on CM, says either are OK.
NEXT: S-OFF:
https://www.facebook.com/CyanogenMod/posts/10152887971775425
To put things in perspective (CyanogenMod's opinions); we're not particularly concerned about devices being S-OFF. Even if they were, we wouldn't want to (or be able to) make changes to the radio anyways. We do want our phones to be unlocked so we can flash custom firmware, and we can do that.
you don't need s-off to root your htc, it's only needed for flashing black box partitions. rooting generally requires an unlocked bootloader
Click to expand...
Click to collapse
http://www.htcdev.com/bootloader/about_unlock_process
You do not need to turn security off to accomplish the basic installation of a custom rom which even includes providing root access and remounting your system to be writable. Note: you shouldn’t really need to keep the system files writable across reboots as this is primarily useful only while developing.
Security is on by default for good reasons.
Click to expand...
Click to collapse
OK, so do I REALLY need S-OFF for CM11?
Next: 4ext recovery:
www.4ext.net/status_update.php
The current generation of 4EXT Recovery Touch has reached its end-of-life.
The old framework that was built 2 years ago in order to release a 100% touch Recovery is far too limited and static.
Click to expand...
Click to collapse
I also looked at CWM and TWRP and TWRP wins hands down everytime someone asks "which to use". But I need to get that HBOOT down to 1.49 version.
Incidentally, http://wiki.cyanogenmod.org/w/Install_CM_for_shooteru says:
If your HBOOT version is NOT 1.49.0007, 1.49.0008 then do not run Revolutionary and contact the Revolutionary team for support availability
Click to expand...
Click to collapse
And sure enough http://unrevoked.com/rootwiki/doku.php/public/revolutionary says:
HTC EVO 3D GSM (shooteru) 1.49.0007, 1.49.0008
Click to expand...
Click to collapse
and below in the changelog:
HTC Evo 3D GSM (shooteru) 1.49.0008
Click to expand...
Click to collapse
But the unlimitied.io hboot downloads, which seem to be the only way, have a ZIP file which is called but inside the zip file the filename is
Code:
hboot_SHR_U_1.49.0009_20110718_signedbyaa.nb0
but although I'm not too hot on binary, inside that file is 1.49.9999.
So how fussy is that version number, really?
I'm aware of the thread here:
how downgrade evo 3d hboot from 1.53.0007 to 1.49.0008
If you're already S-OFF, but on a higher version of hboot, you can just downgrade via a sdcard PG86IMG containing the lower hboot, being S-OFF will let it flash anything
The RUU ZIP image that MATCHES your current ROM version
Click to expand...
Click to collapse
< No explanation of what this is or where to get it.
Elsewhere I found
http://www.androidruu.com/?developer=Shooter and the closest I get is:
RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed.zip
But that still looks way off.
You'll also need the 1.20 or 1.22 RUU EXE (All the RUU's can be found here -> http://www.filefactory.com/f/4ef0ef536face67a/)
Click to expand...
Click to collapse
It's a broken link, so I come to a grinding halt there, too.
Plus I'm not entirely keen on following guides which require deliberate bricking, if I can avoid it.
So, my plan was:
1: UNLOCK - easy if following official HTCDEV site. DONE.
If only everything was as clear as their instructions...
2: Downgrade HBOOT from http://unlimited.io/jbhboots.[quote]htm
Instructions say:
Code:
Put your phone in fastboot mode
Type the following cmds into terminal:
sudo ./fastboot erase cache
sudo ./fastboot oem rebootRUU
sudo ./fastboot flash zip [/quote]jb_hboot.zip
sudo ./fastboot reboot
(OK, I'm using Windows so I didn't type in the sudo part, obviously!)
But all that happens is:
Code:
D:\HTC>fastboot.exe flash zip jb_hboot_shooteru_14999.zip
sending 'zip' (379 KB)...
OKAY [ 0.246s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 2.994s
My phone can reboot OK,.
Elsewhere on the site, it says:
Be using your original HTC USB cable.
Click to expand...
Click to collapse
Could this be the problem? I've looked for hours, but this phone is 3 years old - chances are it went in the trash ages ago.
Is there something special about the original cable? Could that be preventing it?
It seems that once I've cracked this HBOOT version problem I can use Revolutionary, as unlimited.io says:
"We encourage you to use the revolutionary tool if your device is on a supported HBOOT".
Click to expand...
Click to collapse
Which would save me messing around with shorting connections with paperclips (aka "the wire trick"). But yet again, I'm not on the "supported" HBOOT.
Feels like I've spent almost all free time of the last week watching grainy, shaky videos which don't explain clearly and would be far, far better condensed to 4 lines of text and a couple of images.
Right now I am so utterly confused - I have followed so many guides only to find that, for example, the tool at stage number 3 no longer available from 4shared, I have spent hours reading the xda forums, but again, almost all the posts assume you've got the older HBOOT. I've got 7 sides of dense A4 notes, acronyms, links, guides etc and there's a thread with 2,680 posts over at http://www.hotukdeals.com/ask/htc-evo-3d-owners-thread-1151797 but agai but again, it ALL seems to rely entirely on the HBOOT version being lower, and this seems to be a complete sticking point.
This is about the clearest video I've watched, http://www.youtube.com/watch?v=3Q3B9d_DraE, but again, he has HBOOT at the "correct" ie: 1.49xxx version.
Any help greatly appreciated.
digitaltoast said:
Just spent 3 days trawling through guides and totally stuck.
I am on a stock HTC EVO 3D SHOOTERU purchased from ASDA in the UK with current details as follows:
Code:
VERSION.RELEASE: 4.0.3
BRAND: htc_europe
DEVICE: shooteru
MODEL: HTC EVO 3D X515m
OS.VERSION: 3.0.16-ge733189
BOOTLOADER: 1.53.0007
HARDWARE: shooteru
FINGERPRINT: htc_europe/htc_shooteru/shooteru:4.0.3/IML74K/385730.1:user/release-keys
ID: IML74K
TAGS: release-keys
USER: unknown
PRODUCT: htc_shooteru
RADIO: 11.77.3504.00U_11.25.3504.06_M
Rooted: false
May 22 2012, 01:06:07
I want to put KitKat on it, so I decided on Cyanogenmod 11 which requires:
My radio is 11.77.3504.00U_11.25.3504.06_M however some people say P and U are both OK. For example, LiquidSmooth, apparently based on CM, says either are OK.
NEXT: S-OFF:
https://www.facebook.com/CyanogenMod/posts/10152887971775425
http://www.htcdev.com/bootloader/about_unlock_process
OK, so do I REALLY need S-OFF for CM11?
...
So, my plan was:
1: UNLOCK - easy if following official HTCDEV site. DONE.
If only everything was as clear as their instructions...
2: Downgrade HBOOT from http://unlimited.io/jbhboots.jb_hbo...rl]http://www.youtube.com/watch?v=3Q3B9d_DraE, but again, he has HBOOT at the "correct" ie: 1.49xxx version.
Any help greatly appreciated.
Click to expand...
Click to collapse
Read you can't fastboot flash a RUU if still s-on. (oh, I tried too, I'm sure I'm far from the only one who has.)
I was very unhapppy to have to use the wire trick to s-off so I could install another lower-rev bootloader (mine came with 1.58 and wouldn't run anything I was interested in.)
It was really easy though. I used a nice plastic-coated twist ties instead of a paperclip or network cable wire.
My Evo came with no cable. So I (bravely or stupidly) used my factory LG cable from my Optimus V. I had noticed that cheap usb cables wouldn't fastboot my Optimus but the stock LG cable would. I had also verified that my LG cable did fastboot functions ok on my Evo. I was in a hurry and hopeful, didn't want to order a proper cable.
It refused to stay booted with cm11 before changing (downgrading and getting the j-bear version of) hboot. S-on but HTC unlocked on 1.58.0 hboot, I got it to boot all the way to the first screen a couple times by flashing the boot.img to recovery and fastboot booting recovery, and once by fastboot booting the boot.img from the rom zip file... but the firmware rejected the kernel every time and started bootlooping.
But now, s-off, hboot 1.50.5050 I'm running cm11 ok.
What I read says your gsm evo isn't supposed to need s-off to flash the boot.img from recovery (unlike my cdma evo) but it does need s-off to change the hboot version.
Oh, in my 2 days of digging after rooting, hating stock ICS, I also found a reference to corrupting the bootloader by booting into fastboot with a PG86IMG.zip on the card, removing the battery, accepting the flash, and yanking the power cord while the orange bar flashes briefly on the screen...
I much preferred the wire gimmick. It took one failed try, then 3 tries where it didn't fail but didn't s-off either, before it worked. Smooth as butter, by my standards of MacGuyver-ing things, so much so that I donated the unlimited.io team a piddly 1 euro (hey, not much, but if every single person who used their tool kicked them that much they would be a bit richer.)
OK, I've attempted to write a "dummies guide" to unlocking, rooting and flashing a locked, stock UK EVO 3D which has never been modded before.
I did this because, as a new to flashing, rooting etc, I was having the following problems:
A lot of the guides were written before the EVO got the ICS update when the bootloader got update to 1.53.xxx
They assume a lot of knowledge about what rooting is.
Some of the guides are pointlessly dangerous - for example, the "deliberate bricking" trick.
Some of the "how to" forum threads are in excess of 3,000 posts.
Many of the videos on youtube are mindnumbingly tedious timewastes - of a typical ten minute video, the first 5 minutes is someone waving a blurry phone around while he says something like "hi guys, this is wnkr6617, ok guys, what I'm going to be doing today guys is showing you how to root your phone". Then a few minutes while he gives "shoutz" to his "crew", then the last 5 minutes could be far better explain by 4 lines of text and perhaps 1 image. If only everything was a clear as *can't post links* and *can't post links* !
So, I've started on what I hope to be a simple, clear newbies guide to everything from installing the required Linux, to all the steps needed to take a stock, unflashed, untouched HTC EVO 3D and putting a new ROM on.
Take a look *can't post links* gist dot github dot com slash digitaltoast slash 11364569 - if you've got a Github account, you can fork, edit, and push back changes and suggestions, or just comment correct. This way the guide will always stay up to date and clear without having to page through 180 pages of forum threads.
If no github account, just let me know which section the problem is.
You have to do the wire trick as described here.
Read the instructions carefully.
If you fail with the wire trick, no worries, just do it again.
Once you're S_OFF, you're free to flash anything (hboot, rom, etc.).
Installing latest 4Ext recovery is recommended for most custom roms.
Ok got it
Sent from my A110Q using XDA Premium 4 mobile app
So yesterday I had my Aria in my pocket and I guess the power button got nudged and the screen turned on, lo and behold I pull my phone out of my pocket to find the lovely words written on the screen that too many pattern attempts have been attempted and that the device is locked. Only problem is I use this phone for everything but the phone function, I don't even have a sim in there. So with WiFi off, and no mobile network I was stuck for a bit. But then I finally sat down with it and luckily I had kept USB debugging on so I used adb to hack it. And that is where my urgent problem starts. After finally unlocking it I decided to might as well upgrade it, it was running 2.0.2 I believe Liberated ROM with CWM. So I started browsing around because I haven't really worked with this phone before all that much, I ended up reflashing to stock rom and then was going to use a nifty tool to get my hboot to 1.02, well it worked, the nifty tool flashed my hboot alright, along with my ROM and everything else there was. I am now stuck with a brick, the phone goes to the boot logo and then reboots... over and over and over until I pull the battery. I was charging the phone the whole time while working on it and after the tool was done flashing the hboot I unplugged the phone and a long list of errors ran down the screen of files that the OS was missing. I can get into fastboot, haven't had luck with any reflashs, adb is dud (while in recovery computer recognizes the adb connection but adb only lists the device as inactive. Ever since I lost my Inspire 4G this was my only working mobile device. If you have any tips tricks or clues as to how or if it is possible to come back from this destruction I am all ears.
Thank you in advance :fingers-crossed:
To clarify a bit further, the part that screwed me was the Upgrade HTC Gratia HBOOT for AlpharevX S-OFF tool. It was chugging along just fine up until the very end. The original sites listed for making a gold card are all dead but I managed to find a working one. Now I am trying to figure out what went wrong and why.
LIBERTY PVT SHIP S-ON
HBOOT-1.02.0000
MICROP-031b
TOUCH PANEL-STN21_03
RADIO-7.13.35.13
Nov 4 2010,23:12:58
The time and date are frozen
First you should S-OFF your phone with revolutionary. Then you need to flash a working recovery image and reflash ROM from there. Should work. If this still doesn't work, flash a modified hboot from the Development forum and see if you have any luck with that...
dansou901 said:
First you should S-OFF your phone with revolutionary. Then you need to flash a working recovery image and reflash ROM from there. Should work. If this still doesn't work, flash a modified hboot from the Development forum and see if you have any luck with that...
Click to expand...
Click to collapse
I cannot get revolutionary to find the device, the system version is 2.37.709.11 and I cannot do anything, if I try flashing anything the sig verification always fails.
(EDIT: Well I got lucky, found an asian RUU with same version, reflashed phone, S-Off, flashed unofficial CWM recovery and unofficial cyanogen 11.)
The problem I was having with revolutionary not recognizing the device was because my hboot version was too old (0.57). I used this AT&T Update package to get back to stock 2.2 and revolutionary worked straight away.
HTC_Aria_for_ATT_Android_2.2_ROM_Update.exe
http://www.mediafire.com/download/mch2657rdy8aqct/HTC_Aria_for_ATT_Android_2.2_ROM_Update.exe