I searched through the forums for hours and didn't find an example quite like mine (some were close)
Verizon HTC Eris. It's a hand me down.
My friend gave it to me because on normal start up it loads into the 3 Skating Androids screen and goes no further. I don't know how it ended up like that. I wanted to see if I could fix it. All the key combos work (soft boot reset, FASTBOOK start up, HBOOT start up, etc.)
Info:
PB00100 XC SHIP S-ON
MICROP-0111
TOUCH PANEL-MELFAS_45_17
RADIO-2.42.01.04.27
Feb 8 2010, 00:08:56
I can get the phone into stock recovery, don't know if it has the Amon_RA recovery installed.
HBOOT doesn't recognize the PB00IMG.zip (I downloaded the Eris_RootROM_v2.19.605.1_PB00IMG.zip, copied it to my sd and renamed it PB00IMG.zip) and can't get it to load.
I tried SDK but command line "adb devices" list nothing. "adb shell" doesn't work either.
I can run RUU_Desire_C_Verizon_WWE_2.36.605.1_release_signed_with_driver when my phone is in FASTBOOT mode. It's says I have 2.37.605.4 ROM on my phone but will not go any further than that.
When I hook the USB up to my computer, it makes the "USB attached" noise, but I can't see it listed in the removable drives.
Is this a brick??
Again, I searched and read, and searched some more for threads on this problem. Didn't wanna violate the noob rule, because I am a noob.
No Help from anyone? I'm really trying to bring this thing back from the dead
You don't mention if the HBOOT version is 1.49.0000, but I suspect that it is. If memory serves me well, I believe this is why the root ROM PB00IMG file will not load - it will only install over 1.46.0000 or 1.47.0000.
Since you S-ON, Fastboot mode isn't going to help you with much that's useful. That requires S-OFF (which, of course, the root ROM would give you, if you could install it.)
The RUU would not install, I think, because it recognized that you have a newer version of the Eris already installed. This is probably a good sign, though.
I assume that you tried the hard reset of the Eris? http://www.technipages.com/hard-reset-htc-droid-eris.html
With the phone turned off, press and hold the Volume Down, Send (green phone) and Power buttons. The device will turn on. Keep holding down the keys unto you see a screen to clear storage.
Press the track ball.
Follow the instructions to complete the hard reset.
Click to expand...
Click to collapse
See if that works.
doogald said:
You don't mention if the HBOOT version is 1.49.0000, but I suspect that it is. If memory serves me well, I believe this is why the root ROM PB00IMG file will not load - it will only install over 1.46.0000 or 1.47.0000.
Since you S-ON, Fastboot mode isn't going to help you with much that's useful. That requires S-OFF (which, of course, the root ROM would give you, if you could install it.)
The RUU would not install, I think, because it recognized that you have a newer version of the Eris already installed. This is probably a good sign, though.
I assume that you tried the hard reset of the Eris?
See if that works.
Click to expand...
Click to collapse
Did as instructed and got the following:
PB00100 XC SHIP S-ON
HBOOT-1.49.0000 (PB0010000)
MICROP-0111
TOUCH PANEL-MELFAS_45_17
RADIO-2.42.01.04.27
Feb 8 2010, 00:08:56
CLEARSTORAGE
Delete all user data?
<Action>Yes
[I pressed trackball]
Clear.....
Restore NV Okay.
Done
Reboot after 5 seconds
black screen (2 seconds or so)
Restart back to 3 skating androids..that it
I'm not sure if this will work, but in this thread: http://forum.xda-developers.com/showthread.php?t=909921
Find the PB00IMG.zip file for "[ 2.36.605.1 ] a.k.a. "Leak-V3" (or MR3/"Official" RUU)" (not the RUU, but the Eris_LeakV3_v2.36.605.1_PB00IMG.ZIP. Rename it to PB00IMG.zip, copy to the SD card, start HBOOT (hold VolDn while starting up - but I think you know how to do this already) and see if that installs. Since you have a later version on the phone already, it may not.
doogald said:
I'm not sure if this will work, but in this thread:
Find the PB00IMG.zip file for "[ 2.36.605.1 ] a.k.a. "Leak-V3" (or MR3/"Official" RUU)" (not the RUU, but the Eris_LeakV3_v2.36.605.1_PB00IMG.ZIP. Rename it to PB00IMG.zip, copy to the SD card, start HBOOT (hold VolDn while starting up - but I think you know how to do this already) and see if that installs. Since you have a later version on the phone already, it may not.
Click to expand...
Click to collapse
Looks like this one worked...or it got me farther than I've been before. I used the file above and got the progress bar to show up on the top left side. That's never happened before.
You were correct that the version above was too old.But there's good news. The update failed. I tried three (3) fixes:
1) Renamed the 2.36.605.1 file PB00IMG (load it on my laptop using SD adapter, then just rename it), and tried to use HBOOT. It started the blue progress bar in the top left (that's never happened for me so YAY), finished. But, when it was "Checking PB00IMG.zip", it said "Update Failed" and "Version Too Old" or something like that.
2) I tried using
#13 [ Converts 2.37.605.4 -> 2.41.605.6 ] - 5th Eris OTA
ba92bb2e5034.OTA_Desire_C_Verizon_WWE_2.41.605.6-2.37.605.4_release.zip
I renamed this file PB00IMG (did laptop rename process) and got the progress bar in the top left again, and the process finished. This time it went to "Checking PB00IMG" and finished no problem. The bar in the top left disappears, but it stays on the same screen with:
<SEND> FastBoot Mode
<VOL UP> Recovery
I didn't know what to do from here. So just pulled the battery and tried fix #3
3) Renamed the #13 File from Fix 2 above "update" (using laptop rename process). With phone off, held "VOL DWN" and "PWR" button to get into stock recovery mode. I navigated to "install sd update.zip", started it, and got this message:
E: can't open cache/recovery/command
--Install from sdcard...Finding update package...opening update package...verifying update package...installing update...file_getprop: failed to stat "/system/build.prop":No such file or directory
E:error in sdcard/update.zip
(Status 7)
Installation aborted
Do you think I just need a ROM file or something on the sd card too (besides just the PB00IMG file)? Or should it automatically load something after the PB00IMG status bar and check finishes?
Neither method worked, but I at least got something different. It's getting me farther than I had gotten before. So thanks for the recommendations. Ready to try your next suggestion when you get time.
Still needing help....is the tereg recovery the best shot...and how do you do that...
Cap'nO said:
Still needing help....is the tereg recovery the best shot...and how do you do that...
Click to expand...
Click to collapse
You could try getting the S-OFF bootloader installed using SoSicWiTiT's RUU+"rom.zip" swap-out trick
From there, flash a custom (Amon_RA or variant) recovery to the phone (using the fastboot utility from a PC), and try a ROM install.
BTW, using OTA update files will certainly never work renamed to PB00IMG.zip, and in general they will only work from a stock recovery as "update.zip" IF and ONLY IF the phone is in good working condition and with a precise stock OS version pre-existing on the phone. They can NEVER be used to "repair" a phone, as they are "patch kits" for a specific prior release - not a full installation.
bftb0
Yeah OTA updates are typically overlays for a previous update in order to keep the size down. I think you'll see a lot of patch files which is sort of like a .diff file and patches the differences.
The RUU when decompressed with a utility like universal extractor will have a real usable zip in it.
Don't worry about the radio at this point unless you suspect you have a damaged radio firmware which you probably shouldn't mess with unless your 110% sure.
Thanks bftb0..i thought no one would get back to me. I'm going to try your solution now. Full disclosure, I read it but will need some time to decipher it. I'm a self-admitted noob, but trying to become more proficient.
Cap'nO said:
Thanks bftb0..i thought no one would get back to me. I'm going to try your solution now. Full disclosure, I read it but will need some time to decipher it. I'm a self-admitted noob, but trying to become more proficient.
Click to expand...
Click to collapse
Scary_Alien posted a great step-by-step over at AndroidForums.com here: http://androidforums.com/eris-all-things-root/440288-eris-half-brick.html#post3423263
bftb0 said:
You could try getting the S-OFF bootloader installed using SoSicWiTiT's RUU+"rom.zip" swap-out trick
From there, flash a custom (Amon_RA or variant) recovery to the phone (using the fastboot utility from a PC), and try a ROM install.
BTW, using OTA update files will certainly never work renamed to PB00IMG.zip, and in general they will only work from a stock recovery as "update.zip" IF and ONLY IF the phone is in good working condition and with a precise stock OS version pre-existing on the phone. They can NEVER be used to "repair" a phone, as they are "patch kits" for a specific prior release - not a full installation.
bftb0
Click to expand...
Click to collapse
This may be funny, but I'm still trying to fix this thing. Trying the "swap method" you mention above. What's the exact file name (2.1) I'm using for this?
Possible solution (Troubleshooting)
Cap'nO said:
Looks like this one worked...or it got me farther than I've been before. I used the file above and got the progress bar to show up on the top left side. That's never happened before.
You were correct that the version above was too old.But there's good news. The update failed. I tried three (3) fixes:
1) Renamed the 2.36.605.1 file PB00IMG (load it on my laptop using SD adapter, then just rename it), and tried to use HBOOT. It started the blue progress bar in the top left (that's never happened for me so YAY), finished. But, when it was "Checking PB00IMG.zip", it said "Update Failed" and "Version Too Old" or something like that.
2) I tried using
#13 [ Converts 2.37.605.4 -> 2.41.605.6 ] - 5th Eris OTA
ba92bb2e5034.OTA_Desire_C_Verizon_WWE_2.41.605.6-2.37.605.4_release.zip
I renamed this file PB00IMG (did laptop rename process) and got the progress bar in the top left again, and the process finished. This time it went to "Checking PB00IMG" and finished no problem. The bar in the top left disappears, but it stays on the same screen with:
<SEND> FastBoot Mode
<VOL UP> Recovery
I didn't know what to do from here. So just pulled the battery and tried fix #3
3) Renamed the #13 File from Fix 2 above "update" (using laptop rename process). With phone off, held "VOL DWN" and "PWR" button to get into stock recovery mode. I navigated to "install sd update.zip", started it, and got this message:
E: can't open cache/recovery/command
--Install from sdcard...Finding update package...opening update package...verifying update package...installing update...file_getprop: failed to stat "/system/build.prop":No such file or directory
E:error in sdcard/update.zip
(Status 7)
Installation aborted
Do you think I just need a ROM file or something on the sd card too (besides just the PB00IMG file)? Or should it automatically load something after the PB00IMG status bar and check finishes?
Neither method worked, but I at least got something different. It's getting me farther than I had gotten before. So thanks for the recommendations. Ready to try your next suggestion when you get time.
Click to expand...
Click to collapse
If you get this kinda of message that the file_getprop then the update zip is corrupt. or its not compatible with the phone you are trying to mount. It took me a bit but I was able to find a good set up. Just take a breathe. If you can install from sdcard from recovery then your recovery is fine. if you can boot it up and at least get a splash screen your boot.img is right. I stress that you dont change those two if you are able to do both of those. All you need is a Good rom that is 1 compatible with your cell and 2 works with both your boot.img and recovery.img. I am guessing you forgot to backup your original settings. MIUI roms are really good and thats what i settled on.
Thanks for the reply. I actually got the phone working. Took a while but yes, the ROM was corrupt. And yup, it wax never backed up and was stock in the loop.
Not anymore
Sent from my SGH-T959 using xda app-developers app
Related
I've been asked this a few times and I actually had to get help the first time I tried it, so here's my tutorial on how to flash a ROM or Radio image using your microSD Card. I personally use this method because my own computer runs Linux. I could probably boot up to Windows from time to time, but that would be like cheating on my wife; I just can't bring myself to do it if I can avoid it at all
A few of us old-timers to HTC are so used to our personal little tricks we use that we forget that newer users haven't learned them yet. I'm expecting a few people to say, "Oh yeah, we already knew that!" but perhaps one or two will instead learn from it and appreciate it.
So, without further ado:
Different chefs use different methods when naming their ROM or Radio images. You must rename the image to "LEOIMG.nbh", since this is the only recognized file name the bootloader will accept. (note: Some people are reporting that the file name must be capitalized, or it will not work. When named exactly as above, it has always worked for me!)
Place the LEOIMG.nbh on a 8GB or smaller microSD card.
Remove the battery cover and press the Reset button.
Hold the Volume Down and End Call (power) buttons at the same time.
As soon as "Searching..." appears on the screen, release the Volume Down button.
ROM will flash. Be sure to hard-reset afterwards to prevent weird errors (as usual).
Now, in case you are wondering about the specifics:
Remember to put the file on the "root" of the device. This means you can't put it in a folder. I am using an 8GB Class 2 card for flashing. I would recommend using a 1GB Class 6, but it's not necessary. It may be possible with a higher class 16GB card, but I haven't tried. Our Class 2 that came with the phone never works, though I don't rightly know why. [update]souljaboy wrote in and said: "it doesn't work because a fat32 is needed and by default the card is formatted fat, I think you should mention that, it worked for me!" Thanks, souljaboy!
The reset button is a small red or yellow spot just below the slot for the microSD card. You could also remove and replace the battery; the important thing is to shut your phone off and restart it.
Pressing Volume Down and End Call (or Power) is the recommended way to enter the bootloader. If you press the Volume Up and Volume Down at the same time, you will enter the "Hard Reset" option instead.
If "Searching..." does not appear, you either do not have a compatible card in the phone, or you are not holding the right buttons. If you hold the "Volume Down" button past this point, you will see a message that says, "Press the Power Button to upgrade your phone." Releasing the "Volume Down" button at this point may or may not work, I had to release it before. If you release the "Power Button" now, your phone will simply reboot without flashing.
ROM flashing via SD is much safer than via USB, since you don't have to worry about accidentally unplugging the cord or an issue with your PC, such as a crash or power failure.
---Added 05/21/10 as suggested by zelendel (Thanks for the sticky!)
If you are flashing an "Official" ROM direct from HTC or T-Mobile, you will more than likely over-write your SPL (Second Program Loader). This means, even if you have HSPL installed now, you could be reverted back to SSPL, rendering you unable to flash custom ROMs.
To make matters worse, if you flash an ROM higher than 2.10 and you attempt to install the current (as of 5/21/10) HSPL, you will brick your phone. Yeah, it's bad.
So, assuming you have flashed an official ROM over 2.10 via the SD card and you decide you want a custom ROM, follow these simple directions:
(You do not have to have your phone connected to your PC for these steps)
Download the "Official" ROM from here. (Thanks to zelendel for the upload!)
Follow the instructions above to flash your phone with this image.
Once you phone has fully booted, I recommend doing an extra hard-reset.
Next, visit mskip's thread to download the latest HSPL and flash that (you can flash it either via RUU or via microSD).
If done properly you should now be able to once again flash custom ROMs. Congratulations!
Hopefully someone will find this useful. If you have any issues, reply to this thread and I or some other wonderful xda member will try and sort things out.
Happy Flashing!
Awesome guide man, keep 'em coming!!
Bump and sicky request!
nice plain guide, good job.
just worth adding a warning that flashing stock roms from sd card overwrites the hspl/spl, and some spl's aren't covered by hspl, so you can get stuck.
currently i think tmous 2.02 will flash an spl that will prevent further flashing, and 2.13 will require the spl to be downgraded using the 2.10 stock before you can re apply hspl.
samsamuel said:
nice plain guide, good job.
just worth adding a warning that flashing stock roms from sd card overwrites the hspl/spl, and some spl's aren't covered by hspl, so you can get stuck.
currently i think tmous 2.02 will flash an spl that will prevent further, flashing, and 2.13 will require the spl to be downgraded using the 2.10 stock before you can re apply hspl.
Click to expand...
Click to collapse
You are right, it's worth mentioning, thank you!
I thought about writing that in, but then I remembered the sticky "Read before posting" had the links to HSPL that shows how to restore stock SSPL by flashing via SD. I didn't want to re-write other guides that have been serving the newer users for some time now
But if the Mods decide this is sticky-worthy I'll paste your quote and a link to your post in the first post.
ok
i have a mac so im guessing the only way for me to reflash/upgrade my rom would be boot camp? i want to update to the new 2.13 dont really care about not flashing other roms ill wait and stick it out, but what do i need to do to the file once i down load the file do i unzip and send to my device after i rename it ?
You don’t have permission to view “T-Mobile_HD2_MR Software_2.13.531.1.exe”. is what i get from the website, so i guess im stuck waiting till i can do it ona pc ?
jiggahj said:
i have a mac so im guessing the only way for me to reflash/upgrade my rom would be boot camp? i want to update to the new 2.13 dont really care about not flashing other roms ill wait and stick it out, but what do i need to do to the file once i down load the file do i unzip and send to my device after i rename it ?
You don’t have permission to view “T-Mobile_HD2_MR Software_2.13.531.1.exe”. is what i get from the website, so i guess im stuck waiting till i can do it ona pc ?
Click to expand...
Click to collapse
Yeah, the problem here is that the "exe" is the way they packaged this one, which is unfortunate.
For me, I can use Wine to execute win32 apps. You could probably do it as well, since Mac is based on UNIX. I found a tutorial here, but I don't know how well it will work or how old it is. Give it a shot and holla back at us, to let us know how it went.
word
i been trying to get this update since the "leaked" release my friend didnt want me doing it on his comp for what ever reason. so i was gonna partition my hdd and start doing it that way but ill give this a shot ... ill be back soon
ok
i cant just unzip it in my root and do it from there after i download it ?
this is really long and doesnt tell me how to install this on my fone im just downloading and reading a bunch of crap that hardly makes any sense
waste of time
---> Computing dependencies for wine-devel
---> Building mesa
Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_mesa/work/Mesa-7.8.1" && /usr/bin/make -j2 default INSTALL_DIR=/opt/local RC_CFLAGS="-arch x86_64 -arch i386" CC="/usr/bin/gcc-4.2 " CXX="/usr/bin/g++-4.2 " " returned error 2
Command output: Making sources for darwin
make[3]: Nothing to be done for `default'.
make[3]: Nothing to be done for `default'.
make[3]: Nothing to be done for `default'.
/bin/sh ../../../bin/mklib -o GL -linker '/usr/bin/gcc-4.2 ' -ldflags ' -lXplugin -framework ApplicationServices -framework CoreFoundation' \
-major 1 -minor 2 \
-install ../../../lib -id /opt/local/lib/libGL.1.dylib \
-L/opt/local/lib -L/opt/local/lib -lX11 -lXext -lm -lpthread apple_cgl.o apple_glx.o apple_glx_context.o apple_glx_drawable.o apple_glx_pbuffer.o apple_glx_pixmap.o apple_glx_surface.o apple_visual.o apple_xgl_api.o apple_xgl_api_additional.o apple_xgl_api_read.o apple_xgl_api_stereo.o apple_xgl_api_viewport.o appledri.o ../clientattrib.o ../compsize.o ../glcontextmodes.o glx_empty.o glx_error.o ../glx_pbuffer.o ../glx_query.o ../glxcmds.o ../glxcurrent.o ../glxext.o ../glxextensions.o glxreply.o ../pixel.o ../xfont.o
mklib: Making Darwin shared library: libGL.1.2.dylib
ld: library not found for -lXplugin
collect2: ld returned 1 exit status
ld: library not found for -lXplugin
collect2: ld returned 1 exit status
lipo: can't open input file: /var/tmp//ccfmBffL.out (No such file or directory)
mklib: Installing libGL.1.2.dylib libGL.1.dylib libGL.dylib in ../../../lib
mv: rename libGL.1.2.dylib to ../../../lib/libGL.1.2.dylib: No such file or directory
make[2]: *** [../../../lib/libGL.dylib] Error 1
make[1]: *** [subdirs] Error 1
make: *** [default] Error 1
Error: The following dependencies failed to build: mesa ncurses ncursesw openssl xorg-libXcomposite xorg-compositeproto xorg-libXcursor xorg-renderproto xrender xorg-libXinerama xorg-xineramaproto xorg-libXrandr xorg-randrproto xorg-libXxf86vm xorg-xf86vidmodeproto
Error: Status 1 encountered during processing.
Before reporting a bug, first run the command again with the -d flag to get complete output.
is all i get when trying to install wine in terminal have downloaded everything i needed/it said too soo i dont know what the problem is
I'm sorry you are having trouble. Wish I had the answer for you, but I don't have a Mac.
I can definitely say that you are missing some crucial library files, which is what is causing the Wine fail. If you can find the Mac part of the Wine Forums, I am sure someone there has a solution to your problems.
On the bright side, a few of the chefs over on the T-Mobile USA HD2 ROM Development branch have been churning out custom ROMs based on the 2.13 release. Maybe you could give one of those a try?
Help
Help I Cant Connect To ActiveSync Via Usb ( But My Phone Still Is Able To Charge Via Usb Thru My Comp.) & I Want To Upgrage My Hd2 To The New Stock Rom 2.13 (Because All The Freezing!) I Want To Know Is There Any Way I Can Do This Thru My Sd Card Or ActiveSync Bluetooth??? Because I Have Been Seeing On The Internet That You Cant Do It Without HSPL But I Can Get HSPL Without Being Able To Connect My Hd2 Via Usb !
Okay, follow these directions:
Visit this page and grab the latest file (currently 2.13)
Unzip the file and open the *.exe that is inside
When you see "Welcome to the InstallShield Wizard for RUU" click "Next"
Minimize the Installation window
Depending on your version of Windows, the next part will be different, so I'll just tell you what you need to know:
Use the "Find Files" option in the "Start" menu to search for all files that end in .nbh
You should be able to locate "RUU_signed.nbh" in the C:\users\yourusername\Temp folder, but it will be inside a generated folder there. Depending on your version of Windows, the file may be located in a different temporary folder.
Once you have the file, rename it to "LEOIMG.nbh" and move it to your microSD card and follow the rest of the instructions from post #1.
This ROM will flash a new SPL, so if you plan to install custom ROMs in the future, you will need to re-install HSPL.
Because the forum only allows a normal user to upload .zip files 8MB or smaller, I can't attach the file I got using this method.
If someone would be willing to extract it and post it via RS or other, it would be greatly appreciated!
Just added an extra section to the first post detailing how to fix the problem with your SPL being over-written when flashing official ROMs via microSD.
Oh, and thanks to zelendel for the sticky!
(now i haz tu stickies! )
i update my tmo hd2 with the official rom from tmo because of my phone freezing so much and i just wanted to know if in the near future with there be a hspl compatible to the new update without out downgrading?thanks in advance
eckox09 said:
i update my tmo hd2 with the official rom from tmo because of my phone freezing so much and i just wanted to know if in the near future with there be a hspl compatible to the new update without out downgrading?thanks in advance
Click to expand...
Click to collapse
That's a question you'd have to ask the HSPL author (mskip), but I would have to say that I doubt it. The first one was very difficult to create and as long as the hardware stays the same there will be no need to start over.
Now if they do a hardware change and then release an upgraded version of the OS as well, I am sure that mskip or someone else could be persuaded to help out.
but do i need to have hspl to install any roms that are going to be released by anyone for the new update?
Snarksneeze said:
This means, even if you have HSPL installed now, you could be reverted back to SSPL, rendering you unable to flash custom ROMs.
Click to expand...
Click to collapse
do you mean 'reverted back to SPL'
SPL is Stock
SSPL is one shot hacked SPL
HSPL is permanently hacked SPL
Dont mean to sound picky, just trying to avoid confusion
To make matters worse, if you flash an ROM higher than 2.10 and you attempt to install the current (as of 5/21/10) HSPL, you will brick your phone. Yeah, it's bad.
Click to expand...
Click to collapse
no, you just get stuck at spl 2.10.0000 until you downgrade. HSPL1024 fails when you run it, but no problem, just an error.
Bricked is a very scary word, and should be avoided, especially when it isn't bricked.
(UNless something haschanged in teh past day or so? There are a few threads where poeple have tried to install HSPL1024 onto SPL 2.10.0000, , no one has said anything about a brick, only that HSPL fails.)
samsamuel said:
do you mean 'reverted back to SPL'
SPL is Stock
SSPL is one shot hacked SPL
HSPL is permanently hacked SPL
Dont mean to sound picky, just trying to avoid confusion
no, you just get stuck at spl 2.10.0000 until you downgrade. HSPL1024 fails when you run it, but no problem, just an error.
Bricked is a very scary word, and should be avoided, especially when it isn't bricked.
(UNless something haschanged in teh past day or so? There are a few threads where poeple have tried to install HSPL1024 onto SPL 2.10.0000, , no one has said anything about a brick, only that HSPL fails.)
Click to expand...
Click to collapse
I have not actually flashed a stock via SD, only customs, so I've never had a problem. Haven't read about anyone actually bricking their phones with HSPL yet, but I did read a thread where someone was asking about why it would.
Thanks for the clarifications
so you do
Extract the *.exe file inside and double-click to run
Click "Next" when it asks if you want to install
STOP, minimize the window
Using your computer's "Search" program, look in your temporary folder (mine was C:\users\shane\temp\xxxx) for any file with the extension *.nbh (the file should be named ruu_signed.nbh)
Copy this extracted file to a compatible microSD card and flash using the directions at the top of this post.
that then
You must rename the image to "LEOIMG.nbh", since this is the only recognized file name the bootloader will accept.
Place the LEOIMG.nbh on a 8GB or smaller microSD card.
Remove the battery cover and press the Reset button.
Hold the Volume Down and End Call (power) buttons at the same time.
As soon as "Searching..." appears on the screen, release the Volume Down button.
ROM will flash. Be sure to hard-reset afterwards to prevent weird errors (as usual).
that right?
and also im running windows 7 and when i run the install for the 2.10.0 it said extract RUU_signed but when i look at my temp folder, it isnt there
do you know why?
instead of running it and then looking in temp, just right click the .exe and choose"extract here"
Hello Everyone
I know, there are many How-To's and ways to achieve what I want. unfortunately non of those I tried have worked.
My goal. I want to unroot my Hero, to send it back to RMA, because the usb controller is not working. And this is the second biggest Problem atm.
All the How-To's to unroot the device an install the original RUU or at least most of them include the use of the USB function. (creating a gold card 4 example or flashing a different bootloader)
To the USB Controller. It is hopeless. I tried everything. I even set up a Linux VM but where ever I plug it in, the system won't recognise my hero. They don't even recognise something.
Lucky me, the Hero is still able to charge the battery.
*****
Ok lets give some details on the actual situation.
I'm able to boot to HBOOT/Fastboot (volume down)
I'm able to boot to Clockwork Mod Recovery 2.5.0.7 (home)
Right now, it's restoring the system to FroydVillain 1.7.1, because i formated the boot partition (After 5 hours, I was tired and did one big mistake)
> The restore worked. I have my old System again.
What I tried to do
1. I downloaded the actual RUU, ran it, got the rom.zip out of it.
2. Booted into Clockwork Mod and tried to install from zip, where i got [Error Message 1]
3. Renamed the rom to update.zip and tried to install toe "normal" way. Also got the same [Error Message 1]
4. Renamed the rom into HEROIMG.zip, ran HBOOT which checks the zip and led me to [Error Message 2]
Error Message 1
Code:
-- Installing: SDCARD:rom.zip
Finding update package ...
Opeing update package...
E:Can't open /sdcard/rom.zip (bad)
Installation aborted
Error Message 2
Code:
SD Checking...
Loading...[HERODIAG.zip]
No image!
Loading...[HERODIA3.nbh]
No image or wrong image!
Loading...[HERODIA2.nbh]
No image or wrong image!
Loading...[HERODIAG.nbh]
No image or wrong image!
Loading...[HEROIMG.zip] // takes about 3 minutes...
Checking HEROIMG.zip // takes about 1 minute...
Main Verion is older!
Update Fail!
I downloaded the actual Hero RUU three times from the website, in case something went wrong while dl.
I got an older RUU from a xda thread and tried it with tis one.
I am not able to create a goldcard, because you have to connect the phone via usb to a computer.
Well Any help is much appreciated.
Regards
mae`
Hey,
really sh*tty that usb ain't working..
having trouble from time to time myself, got a suggestion for ya though
1) find yourself a rom that is very close to a stock rom (suggesting stock WWE,
as can be found on this forum, mr bang, stock wwe rooted)
http://www.romraid.com/paul/hero/upd...5.5-signed.zip (maybe an option)
2) make sure it doesn't have a customized kernel (or flash the stock one )
3) make sure it doesn't have apps2sd
4) use universal androot => UNROOT
5) delete busybox from your phone
guess this should get as close as it can be to a stock sense rom
(meaning unrooted and minor customizations
grtz, [email protected]
Hey mattnmd
Thank you for the hints!
Actually I could not download the ROM because the link seems "wrong" but it pointed me in the right direction.
I found e repacked Stock ROM (1.5) which I was able to flash.
So... My base system is ok for the moment. BUT my recovery is not
There is still clockworkmod recovery installed and it won't let me install updates.
Now in the next step I need a way to flash a different recovery (the original) without the use of USB.
androot does work. btw =)
Thanks a lot
mae` said:
Now in the next step I need a way to flash a different recovery (the original) without the use of USB.
Thanks a lot
Click to expand...
Click to collapse
np man, but here i can't help
never got the problem
grtz
Put the Hero like stock without USB
Is there a solution for this already?!! I've exactly the same problem - USB doesn't works, not even for charge! And I need to make it stock-alike in order to send it to warranty. I managed to install the stock ROM but still, there's the AmonRa Bootloader installed... I created a goldcard without USB using this: w ww.mikesouthby.co.uk/2010/08/htc-desire-creating-goldcard-using-mac-or-linux/
but, when I try to apply the HEROIMG.zip trough Hboot, it says "Main version is older"
What am I missing?! Is the installed radio too recent for the stock image I'm trying to install?!
I have no solution jet. But I'll write as soon as I see a way.
_________________________
HTC Desire S - xda app
Worked for me!!!
Well, I found a way to solve my problem! I needed to put my GSM Hero as stock as possible (without root/custom ROMS/AmonRa/etc) without USB... The only solution, as far as I've read is to flash using a GoldCard the zip file from the RUU *.exe from HTC. I manage to create the GoldenCard without USB but when I tried to flash, it would say "Main Version is Older" after checking the HEROIMG.zip . It finally worked when I used this particular RUU version: RUU_Hero_HTC_WWE_2.73.405.38_WWE_release_signed_No Driver.exe from XDA thread #559622. Give it a try
Finally done
Hey dusturn
You are my (HTC) Hero
I just made the goldcard, and installed the new/old image (2.73.405.38) The Device got the old cupcake 1.5 on it and I was not able to get into recovery anymore!
It finally seems to be ok! Thank you very much!
dusturn said:
Well, I found a way to solve my problem! I needed to put my GSM Hero as stock as possible (without root/custom ROMS/AmonRa/etc) without USB... The only solution, as far as I've read is to flash using a GoldCard the zip file from the RUU *.exe from HTC. I manage to create the GoldenCard without USB but when I tried to flash, it would say "Main Version is Older" after checking the HEROIMG.zip . It finally worked when I used this particular RUU version: RUU_Hero_HTC_WWE_2.73.405.38_WWE_release_signed_No Driver.exe from XDA thread #559622. Give it a try
Click to expand...
Click to collapse
How did you make goldcard without USB? I have the same problem but cannot find a solution.
(i made sure to do a backup)
Let me sum up what I have done:
I've managed to follow a guide on a wiki(I lost the link however, since I ATTEMPTED to give up on this) that involved me downgrading my firmware, then do some steps to install cyanogen 1.4. Afterwards, I got to step that required me to rename some file to update.zip. I followed that step and noticed my computer didn't convert the file to a zip file(it remained as a img file) but continued anyway while finding that odd.
Afterwards, cyanogen tells me that it cannot find the zip file. I've search most of google and a bit of this site, and i've seen various solutions that failed me such as:
-renaming the update.zip to update
-using android sdk(which i have no clue on how to use)
Anyways, finding out that I was foolish to do all of this without prior knowledge, I decided to go back to my original firmware. However, on the phone's reboot, cyanogen came up again for some reason, and didn't let the update be applied.(I don't recall the error)
Anyways, I selected reboot and got to my phone's main menu then some music started playing automatically. I should note, before I did the update, I placed all of my backed up data(while still having the original copy on my pc) on my phone so it might've been some music that the original owner had. Now, on the menu, i'm getting this error "The process android.process.acore has stopped unexpectedly. Please try again." all the time. Since this error constantly pops up, I can't do anything.
So if you managed to read my long and boring story, let me ask one question:
How do I get my phone back to normal if rooting is impossible at this point?
First question is what firmware is your htc magic currently on? And by reading everything I guess your phone isnt rooted...
Dataslycer said:
First question is what firmware is your htc magic currently on? And by reading everything I guess your phone isnt rooted...
Click to expand...
Click to collapse
It's on 1.5 currently. Also as a little update:
I fixed the "not being able to do anything on the menu" problem by doing a factory reset. Afterwards, I learned the SDK a little bit more and have the tools, pc driver, and fastboot on my pc. However, i'm getting the error:
FAILED (remote: not allow)
Just a bump. I need all the help I can get on this one. Even a premade update.zip would help me GREATLY.
One last bump. I promise.
NOTE: IF YOU ARE ALREADY ON ICS OF EITHER PROVIDER, YOU CANNOT USE THE OTA FILE AS DIRECTED BELOW, SINCE THE UPDATE PROCESS CHECKS YOUR ANDROID/BOOTLOADER VERSION
Now we all have access to the Telus and T-Mobile OTA ICS files but we can't seem to find a way to install them, we only know how to install the modded files that the devs have supplied us with, well search no more.
I'll give you a step by step way to get it done and use the OTA files without the need of a dev modding it for us.
Requirements:
1. Stock GB of whichever provider you choose to install from be it Telus or T-Mobile
do note that you can only install the ICS OTA file of the exact providers who's stock GB you have installed.
2. The OTA corresponding file, I'll provide links to both below.
3. An SD card.
Procedure:
1. Flash back to stock GB of the provider you want to install be it TMO or Telus, if you're already on complete stock, skip this step and go to step 2.
2. Place the OTA file on the external sd card, you do not have to rename this file.
3. Reboot into bootloader and select recovery, it's gonna show the update icon then show you the icon some of you have been getting with the red triangle and exclamation mark, ignore this.
4. Hold your volume up button and press the power button, it's gonna say "can't open command/cache" then give you the default recovery menu.
5. select install update.zip from external
6. browse using the volume up or down buttons to the OTA file and press the power button to select it.
7. it's gonna ask you once to select reboot on the menu, do this and let it be for a few more minutes.
8. It's gonna reboot when it done, should reboot twice, once to the upgrade screen, second to android.
Voila! You're on official ICS via the ota file!
T-Mobile ICS OTA file here: http://www.4shared.com/zip/V4cIZsvx/OTA_RUBY_ICS_35_S_TMOUS_214531.html
Telus ICS OTA file here: http://www.4shared.com/zip/HTGslOiT/OTA_RUBY_ICS_35_S_TELUS_WWE_21.html
Credits to BoomBoom for the telus file upload.
Note to users, if you're getting an error when you try to select the update file as instructed, simply rename the OTA file to update, then try applying update from sd card, let me know if that works for you instead, so I can edit this tutorial accordingly.
An experimental though added, it's theory, too lazy to test it, but hoping someone else confirms it.
Hi!
It doesnt work for me
3. Reboot into bootloader and select recovery, it's gonna show the update icon then show you the icon some of you have been getting with the red triangle and exclamation mark, ignore this. (I did get the red triangle &exclamation).
4. Hold your volume up button and press the power button, it's gonna say "can't open command/cache" then give you the default recovery menu.
(it shows Android system recovery <3e> in blue at the top of the screen -> not sure if this is the default though?)
5. select install update.zip from external ( I have Apply update from sdcard. If I choose that option I get "invalid operation" shows the red triangle & exclamation and it restarts itself.)
Thanks in advance!
-=S=-
scream514 said:
Hi!
It doesnt work for me
3. Reboot into bootloader and select recovery, it's gonna show the update icon then show you the icon some of you have been getting with the red triangle and exclamation mark, ignore this. (I did get the red triangle &exclamation).
4. Hold your volume up button and press the power button, it's gonna say "can't open command/cache" then give you the default recovery menu.
(it shows Android system recovery <3e> in blue at the top of the screen -> not sure if this is the default though?)
5. select install update.zip from external ( I have Apply update from sdcard. If I choose that option I get "invalid operation" shows the red triangle & exclamation and it restarts itself.)
Thanks in advance!
-=S=-
Click to expand...
Click to collapse
What's your phone info?
Android version, what recovery are you using, are you rooted? Are you unlocked?? I can't work with nothing, gotta have some info.
I'm having the same problem as Scream. My amaze is complete stock, unrooted. Already running the Telus ota but wanted to reflash to try and fix the "time without signal" problem.
garysayer1976 said:
I'm having the same problem as Scream. My amaze is complete stock, unrooted. Already running the Telus ota but wanted to reflash to try and fix the "time without signal" problem.
Click to expand...
Click to collapse
There's no reflashing for Telus S-On users, your only option would be to install a custom recovery and restore the nandroid backup I made for telus users to return to stock, do a wipe before restoring, so any buggy files will be cleared.
Dark Nightmare said:
What's your phone info?
Android version, what recovery are you using, are you rooted? Are you unlocked?? I can't work with nothing, gotta have some info.
Click to expand...
Click to collapse
Sorry, you're quite right!
It's is as close to stock as i seem to be able to get it...
I tried "RUU_Ruby_TELUS_WWE_1.41.661.3_Radio_1.08.550L.19DC_30.66.550L.08D_release_222694_signed.exe", and relocked my bootloader, then while in fastboot I ran the EXE and it completed just fine.
System presently shows as andriod 2.34, sense 3.0 and software number 1.41.661.3. Baseband is 1.08.550L.19DC_30.66.550L.08D, build is 1.41.661.3 CL185373 release-keys.
I've tried using Hasoon2000;s all in one (V3.1)to flash the kernel and recovery to stock, but its not seeming to work... kernel is now 2.6.35.13-ga21d077 and the recovery screen shows a phone with a red triangle & exclamation with the words Andriod system recovery <3e> and always the same 4 options: reboot,apply from sdcard, factory reset and wipe cache.
(edited>) I'm also locked/unlocked & rooted!
Telus-1.41-Restore-Flasher also claimed to reflashed the recovery and didnt seem to do anything either :/
lo and behold! "There's no reflashing for Telus S-On users, your only option would be to install a custom recovery and restore the nandroid backup I made for telus users to return to stock, do a wipe before restoring, so any buggy files will be cleared."
If thats my oly solution, its no wonder everythings been failing :/ Would the above let me take the OTA? Or do I need some s-off action?
Thanks
scream514 said:
Sorry, you;re quite right!
It's is as close to stock as i seem to be able to get it...
I dtried "RUU_Ruby_TELUS_WWE_1.41.661.3_Radio_1.08.550L.19DC_30.66.550L.08D_release_222694_signed.exe", and relocked my bootloader, then while in fastboot I ran the EXE and it completed just fine.
System presently shows as andriod 2.34, sense 3.0 and software number 1.41.661.3. Baseband is 1.08.550L.19DC_30.66.550L.08D, build is 1.41.661.3 CL185373 release-keys.
I've tried using Hasoon2000;s all in one (V3.1)to flash the kernel and recovery to stock, but its not seeming to work... kernel is now 2.6.35.13-ga21d077 and the recovery screen shows a phone with a red triangle & exclamation with the words Andriod system recovery <3e> and always the same 4 options: reboot,apply from sdcard, factory reset and wipe cache.
Thanks
Click to expand...
Click to collapse
Rename the OTA file to update and place it on your external sd card, reboot into recovery, choose the apply update.zip option again and let me know what happens.
Firstly, I really appreciate the quick replies!
copied "OTA_RUBY_ICS_35_S_TELUS_WWE_2.14.661.2-1.41.661.3_release_258801lhwl8053lp8g5hcp.zip" and renamed to update.zip.
Standard "E:Cant open /cache/recovery/command" that ive been seening all day and when i choose update from sdcard it says "invalid operation, sucess rebooting reason code ___ (its a bit too qiuck for me to catch it all!)
What next?
Cheers/thanks
scream514 said:
Firstly, I really appreciate the quick replies!
copied "OTA_RUBY_ICS_35_S_TELUS_WWE_2.14.661.2-1.41.661.3_release_258801lhwl8053lp8g5hcp.zip" and renamed to update.zip.
Standard "E:Cant open /cache/recovery/command" that ive been seening all day and when i choose update from sdcard it says "invalid operation, sucess rebooting reason code ___ (its a bit too qiuck for me to catch it all!)
What next?
Cheers/thanks
Click to expand...
Click to collapse
So basically, you can't update via my methods or just normally via the phone, is your bootloader unlocked by chance? If so, please relock it, that's the reason why it won't update if it's unlocked, only s-off users can update with an unlocked bootloader.
scream514 said:
Sorry, you're quite right!
It's is as close to stock as i seem to be able to get it...
I tried "RUU_Ruby_TELUS_WWE_1.41.661.3_Radio_1.08.550L.19DC_30.66.550L.08D_release_222694_signed.exe", and relocked my bootloader, then while in fastboot I ran the EXE and it completed just fine.
System presently shows as andriod 2.34, sense 3.0 and software number 1.41.661.3. Baseband is 1.08.550L.19DC_30.66.550L.08D, build is 1.41.661.3 CL185373 release-keys.
I've tried using Hasoon2000;s all in one (V3.1)to flash the kernel and recovery to stock, but its not seeming to work... kernel is now 2.6.35.13-ga21d077 and the recovery screen shows a phone with a red triangle & exclamation with the words Andriod system recovery <3e> and always the same 4 options: reboot,apply from sdcard, factory reset and wipe cache.
(edited>) I'm also locked/unlocked & rooted!
Telus-1.41-Restore-Flasher also claimed to reflashed the recovery and didnt seem to do anything either :/
lo and behold! "There's no reflashing for Telus S-On users, your only option would be to install a custom recovery and restore the nandroid backup I made for telus users to return to stock, do a wipe before restoring, so any buggy files will be cleared."
If thats my oly solution, its no wonder everythings been failing :/ Would the above let me take the OTA? Or do I need some s-off action?
Thanks
Click to expand...
Click to collapse
You can't use the nandroid I made or the flashable zip I'm currently uploading due to you being on GB, only ICS users can use that option to return to stock.
Unfortunately nothing worked... But as i'm currently unlocked ( I did try your method locked) and HOLY CRAPCAKES!! It seems to finally see the update though telus!!!!
Will I get screwed if the BL is unlocked and i take this update? (im already 55% done Dl'ing thru telus)
Thanks!
---------- Post added 7th June 2012 at 12:04 AM ---------- Previous post was 6th June 2012 at 11:59 PM ----------
well, it dl'd and verified sucessfully... guess its a race now, wish me luck!!!
while wrting that a little yellow progress bar is showing instead of the error message under the update logo... bar is 30% complete...
almost hit 10 posts...
oh shizzle!!!
scream514 said:
Unfortunately nothing worked... But as i'm currently unlocked ( I did try your method locked) and HOLY CRAPCAKES!! It seems to finally see the update though telus!!!!
Will I get screwed if the BL is unlocked and i take this update? (im already 55% done Dl'ing thru telus)
Thanks!
Click to expand...
Click to collapse
Hopefully no, if it does give an error, simply relock and try again.
ok, yellow bar dissapeared.
Sexy green arrow pointing down showed up, restarted or went black and now I've got that green/teal arrows pointing down with a yellow bar...ok I'm a slow typer thats done.
Oh snap, its all black again... changes drawers.... green arrow pointing down, baber pole and now HTC logo.... holds breath...
now that sexy teal again telling me that andriod is upgrading... 44 of 44 and wow yea im a slow typer... Is that angels I hear singing???
' Says I'm 2.14.661.2 sucessfull!!!!!
I confirm all the numbers are bigger in systems info...holy smokes it finally worked.
Thanks for being patient with me
scream514 said:
ok, yellow bar dissapeared.
Sexy green arrow pointing down showed up, restarted or went black and now I've got that green/teal arrows pointing down with a yellow bar...ok I'm a slow typer thats done.
Oh snap, its all black again... changes drawers.... green arrow pointing down, baber pole and now HTC logo.... holds breath...
now that sexy teal again telling me that andriod is upgrading... 44 of 44 and wow yea im a slow typer... Is that angels I hear singing???
' Says I'm 2.14.661.2 sucessfull!!!!!
I confirm all the numbers are bigger in systems info...holy smokes it finally worked.
Thanks for being patient with me
Click to expand...
Click to collapse
Well you're on ICS officially, have fun.
n00b question
First post, and I'm sorry for asking an obvious question and posting in a relatively old thread. I just got an Amaze 4G yesterday, and after many calls and chats with both T-Mobile customer support and HTC support, the consensus is that my phone isn't getting the OTA ICS update because the IMEI block hasn't been activated, yet. Will this method allow me to get it early, while not voiding my warranty, etc? If I stuck with this method, would I still be able to get the usual OTA updates later on?
What I'm trying to ask is, does this method act exactly as if I had gotten it through T-Mobile?
Thanks, everyone! It's much appreciated!
ics ota update videotron on htc amaze from videotron
Hi guys, I was wondering if i was doing doing something wrong trying the method showed up on the frist page , I applied the steps for my videotron amaze 4g with the ota file, and yet i get what everyone seems getting, I get to the point where it cannot find the update file on the sd card. What if I were to put the update file in the internal memeory?. after all, if the OTA gets in via the regular way, wouldn't be placed in the internal memory to start with??
Still , I would require some help from someone who suceeded in upgrading to ICS..
Thanks
1. Sideloading only works with external sd
2. This method only seems to work with s-off devices on gb or a s-on device with a locked bootloader.
Sent from my SGH-T999 using xda app-developers app
Ota update
So i have to S-off the phone them... I wish i didn't have to rely on Jump starting the lock. I do not matter losing the contents od the SD card what I am afraid of is that I do not want to fry the phone ... Looks like i'll have to wait for my provider to send the OTA file by air. Why isnmt there some kind of an OTASP to trigger these OTA pushes? Thanks again.
I did click the button BTW.
Flynch3211 said:
So i have to S-off the phone them... I wish i didn't have to rely on Jump starting the lock. I do not matter losing the contents od the SD card what I am afraid of is that I do not want to fry the phone ... Looks like i'll have to wait for my provider to send the OTA file by air. Why isnmt there some kind of an OTASP to trigger these OTA pushes? Thanks again.
I did click the button BTW.
Click to expand...
Click to collapse
Lock your bootloader back if you're on gb and try this method again, do note that you have to have the stock recovery.
Before I get bashed for not posting in Hasoon2000's All-in-one toolkit thread (http://forum.xda-developers.com/showthread.php?t=1493905), I would just like to say that I just joined the forum and wasn't allowed to post in the thread for questions/problems. With that out of the way, I'll start by saying that I have a HTC Amaze 4G (T-Mobile USA) on android version 2.3.4 and software number 1.36.531.6, not rooted and completely stock.
Background info: The reason why I want to root is because for some odd reason my amaze didn't get receive the OTA ics update. I checked for it manually just about everyday and I also did not receive a notification for a new software update. I also contacted customer service and they were no help. I would just like to root my phone and install ICS for now and later in the future install a stable custom rom that has sense 4.0.
Questons:
1. Does the Amaze have to be connected to the PC before the start of the first step(Install HTC Drivers)? If so, what is the screen on the phone supposed to be on(Is the phone supposed to be turned off or on? Is it supposed to be in disc drive mode? bootloader? etc..)?
2. Which recovery should I use after my bootloader is unlocked? and also what is the phone supposed to be on (bootloader, regular screen, other)?
3. How do I install ICS after successfully rooting?
I apologize for the long post and noob questions. I had an iPhone before getting the htc amaze and jailbreaking/unlocking was very easy whereas this seems to be a bit more tricky. If there is a thorough and detailed STEP-BY-STEP tutorial anywhere else, please let me know.
Thank You!
Kashif92k said:
Before I get bashed for not posting in Hasoon2000's All-in-one toolkit thread (http://forum.xda-developers.com/showthread.php?t=1493905), I would just like to say that I just joined the forum and wasn't allowed to post in the thread for questions/problems. With that out of the way, I'll start by saying that I have a HTC Amaze 4G (T-Mobile USA) on android version 2.3.4 and software number 1.36.531.6, not rooted and completely stock.
Background info: The reason why I want to root is because for some odd reason my amaze didn't get receive the OTA ics update. I checked for it manually just about everyday and I also did not receive a notification for a new software update. I also contacted customer service and they were no help. I would just like to root my phone and install ICS for now and later in the future install a stable custom rom that has sense 4.0.
Questons:
1. Does the Amaze have to be connected to the PC before the start of the first step(Install HTC Drivers)? If so, what is the screen on the phone supposed to be on(Is the phone supposed to be turned off or on? Is it supposed to be in disc drive mode? bootloader? etc..)?
2. Which recovery should I use after my bootloader is unlocked? and also what is the phone supposed to be on (bootloader, regular screen, other)?
3. How do I install ICS after successfully rooting?
I apologize for the long post and noob questions. I had an iPhone before getting the htc amaze and jailbreaking/unlocking was very easy whereas this seems to be a bit more tricky. If there is a thorough and detailed STEP-BY-STEP tutorial anywhere else, please let me know.
Thank You!
Click to expand...
Click to collapse
First welcome..I use to be an iPhone user also...before even starting update to ics. It should be available ota. Yes it has to be connected to you pc make sure usb debugging is on. Hasoon has the instructions in his post. But you have to be in bootloader screen. Use 4ext for recovery. Then root....you should be good to go. Make sure you make a nandroid backup
Sent from my HTC_Amaze_4G using Tapatalk 2
Flipnfr3ak said:
First welcome..I use to be an iPhone user also...before even starting update to ics. It should be available ota. Yes it has to be connected to you pc make sure usb debugging is on. Hasoon has the instructions in his post. But you have to be in bootloader screen. Use 4ext for recovery. Then root....you should be good to go. Make sure you make a nandroid backup
Sent from my HTC_Amaze_4G using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the quick reply! Every time I manually search for the OTA update, it says "There are no updates available for your phone.", so I unfortunately can't update it OTA. I'm very new to all of this, so I don't know the terminology for a lot of the things on the forum. How do I make sure usb debugging is on and also what is a nandroid backup? Also, am I supposed to be on the bootloader screen the entire time?
Kashif92k said:
Before I get bashed for not posting in Hasoon2000's All-in-one toolkit thread (http://forum.xda-developers.com/showthread.php?t=1493905), I would just like to say that I just joined the forum and wasn't allowed to post in the thread for questions/problems. With that out of the way, I'll start by saying that I have a HTC Amaze 4G (T-Mobile USA) on android version 2.3.4 and software number 1.36.531.6, not rooted and completely stock.
Background info: The reason why I want to root is because for some odd reason my amaze didn't get receive the OTA ics update. I checked for it manually just about everyday and I also did not receive a notification for a new software update. I also contacted customer service and they were no help. I would just like to root my phone and install ICS for now and later in the future install a stable custom rom that has sense 4.0.
Questons:
1. Does the Amaze have to be connected to the PC before the start of the first step(Install HTC Drivers)? If so, what is the screen on the phone supposed to be on(Is the phone supposed to be turned off or on? Is it supposed to be in disc drive mode? bootloader? etc..)?
2. Which recovery should I use after my bootloader is unlocked? and also what is the phone supposed to be on (bootloader, regular screen, other)?
3. How do I install ICS after successfully rooting?
I apologize for the long post and noob questions. I had an iPhone before getting the htc amaze and jailbreaking/unlocking was very easy whereas this seems to be a bit more tricky. If there is a thorough and detailed STEP-BY-STEP tutorial anywhere else, please let me know.
Thank You!
Click to expand...
Click to collapse
Not sure if this helps...but this is what I did. I originally posted it on T-mo forum. At the very least it will put you in the ballpark...good luck. Just trying to help. These other guys know a lot more than myself. I'm sure the community will get you through it.
"Re: Leaked ICS in the wild!
Okay. Got it. Long story short:
1. Download file onto PC http://www.filefactory.com/f/40bba0821a54f264/
2. Put file on SD card (I recomend different SD card.)
3. After it is on SD card, rename file "PH85IMG" *** No ".zip." ***
4. Power down phone
5. Remove/replace SD card
6. Remove battery
7. Replace battery
8. Power up the phone hold "power button and volume down" at the same time.
9. Hboot will appear...let go of buttons. the phone will then start reading the SD card. "Checking PH85IMG"
10. After that instructions will appear. At the bottom of the info you will see the prompt: "Do you want to start update?" Now Volume up for "Yes."
11. Once you volume up for yes it will begin checking the files. (After some time it updated a few files and the screen went black. I hit the power button and and it started updating all files.
In closing you "WILL" lose all info, contacts, text, email and any other setting on the phone. It will be just like when you pulled it out of the box for the first time."
badgerdave made an excellent post and has it right - almost. I just want to clarify a couple of things.
First...he gave a link to the leaked RUU of the ICS OTA update. This file will install as he described WITHOUT requiring root and results in a phone in out-of-the-box condition - no root, with ICS 4.0:3 and Sense 3.6.
Second...the file must be named 'PH85IMG.zip' - WITH the .zip extension. A common mistake is to have file extensions hidden so when the file is renamed it is actually 'PH85IMG.zip.zip' resulting in installation failure.
Registered Linux user #266531. Android user since v1.0.
yes so first before rooting or unlcoking anything download your carriers ruu but it in you sd card and boot to boootloder (vol down + power button) it will install then use hasoon tool kit to unlock boot loader then flash 4ext recovery then root then flash rom
Crashdamage said:
badgerdave made an excellent post and has it right - almost. I just want to clarify a couple of things.
First...he gave a link to the leaked RUU of the ICS OTA update. This file will install as he described WITHOUT root and results in a phone in out-of-the-box condition - no root, with ICS 4.0:3 and Sense 3.6.
Second...the file must be named 'PH85IMG.zip' - WITH the .zip extension. A common mistake is to have file extensions hidden so when the file is renamed it is actually 'PH85IMG.zip.zip' resulting in installation failure.
Registered Linux user #266531. Android user since v1.0.
Click to expand...
Click to collapse
Crashdamage:can I use the same process to go back to the original stock ROM prior to any OTAs? And here is why I want to do that.
I got my phone in January 2012. I received a message about an OTA. I did the update. My Plantronics Voyager Pro and 2-Explorers came in. I tried them out on the phone and the reception and range were completely horrible. 1-2 Ft. the Explorers had slightly better sound quality.
After some research on t-mo forum I found that there were others with the same problem. (The first Product Review that complains about Bluetooth issue was December 17, 2011. The first OTA was released on December 12, 2012. Coincidence?) Some of the people said their BT worked fine prior to the first OTA. T-mo's corporate line was "ICS will fix everything." I waited for ICS as long as I could and did the "Leaked ICS."
ICS did not fix the problem....but it did improve it from 1-2 Ft. to 8-10 Ft. It still has quite a bit of static. Therefore because ICS did improve the problem, I want to test the theory that everything was fine with the original ROM. Kind of a "test the theory" and "process of elimination."
Any help form you and the community will be greatly appreciated. I hope at the end of this I can take my findings back to the others that are having this same problem...some of them that have done multiple handset exchanges and still have the problem. -THANKS-
My question to you guys is, why root if you want to update to ICS? You do know all the OTA files are available and I wrote a tutorial to update your device manually using them, right?
I want to say it, but I won't, I'm not up for the rants, etc.
badgerdave, if I remember correctly, you're from the tmo community fora, right? You had an issue with your BT and someone posted saying theirs worked great when they rooted their device. You can try a few custom roms, but nobody is definite on your end result until you do it.
Also you guys need to quit using those slow filefactory uploads, devs, RC's, myself included uploaded those files to dev-host accounts for faster, easier downloads, those links can be found in the stock ruu/ota thread, use those and PLEASE READ the dev section, there's updated post and links on the very first threads, I don't get why there's a need to dig up older threads with outdated files/info for something so simple.
Dark Nightmare said:
My question to you guys is, why root if you want to update to ICS? You do know all the OTA files are available and I wrote a tutorial to update your device manually using them, right?
I want to say it, but I won't, I'm not up for the rants, etc.
badgerdave, if I remember correctly, you're from the tmo community fora, right? You had an issue with your BT and someone posted saying theirs worked great when they rooted their device. You can try a few custom roms, but nobody is definite on your end result until you do it.
Also you guys need to quit using those slow filefactory uploads, devs, RC's, myself included uploaded those files to dev-host accounts for faster, easier downloads, those links can be found in the stock ruu/ota thread, use those and PLEASE READ the dev section, there's updated post and links on the very first threads, I don't get why there's a need to dig up older threads with outdated files/info for something so simple.
Click to expand...
Click to collapse
Yes DN that is me. But...I'm am not an anomaly where this BT issue is concerned. I have dated it back to the first posted product review
(December 17, 2011) that listed the BT as an issue...others came after. December 17 is 5 days after the first OTA. There are no bad BT reviews prior to that date.
I am not trying to be difficult. I actually downloaded the PDF for the Amaze Bible and installed it onto my rooted HP Touchpad. I read what you are talking about. (Keep in mind that you guy do this stuff all the time with multiple devices. This comes easy to you. Not so much for those of us that get directed to this forum because our questions and problems surpass the T-mo site.)
That being said..I'll just try my hand at using this link: http://d-h.st/8pm to get what I think I need and then try installing it like I did the first "Leaked ICS"
Thanks for your help.
New motto: Believe in oneself...because no else does.
badgerdave said:
Yes DN that is me. But...I'm am not an anomaly where this BT issue is concerned. I have dated it back to the first posted product review
(December 17, 2011) that listed the BT as an issue...others came after. December 17 is 5 days after the first OTA. There are no bad BT reviews prior to that date.
I am not trying to be difficult. I actually downloaded the PDF for the Amaze Bible and installed it onto my rooted HP Touchpad. I read what you are talking about. (Keep in mind that you guy do this stuff all the time with multiple devices. This comes easy to you. Not so much for those of us that get directed to this forum because our questions and problems surpass the T-mo site.)
That being said..I'll just try my hand at using this link: http://d-h.st/8pm to get what I think I need and then try installing it like I did the first "Leaked ICS"
Thanks for your help.
New motto: Believe in oneself...because no else does.
Click to expand...
Click to collapse
Not that no one believes in you, but think about this for a minute, many contributors, devs and regular users alike here saw the issue many were having, saw how complicated getting things done were, so we put as much time into making this all simple, I'm talking months of work, endless hours of typing and research to simplify things here, so for you to say you're unable to find things here, that kinda hurts, I myself worked on making the ICS update as simple as possible, I've posted multiple times, more than I can count on how to fix soft bricks and how to restore to complete stock, so you can tell how hard it is to believe when people say we're not helpful and we don't make things simple, if you have a question, ask it flat out, I'll be straight with you that I know what you read and did not read, I can tell you exactly where everything can be found for this device and I've been here a mere month or two, you know what? It's pointless, no point in me saying anything anymore, I guess I should just follow suit of every other contributor around here and just move on to another device like they all did/doing.
So have a nice day, if you can find what you're looking for in the amaze bible thread, PM one of the writers, sure they'd be glad to help, they always have been and always will be very nice helpful individuals.
New motto: I am officially out of the amaze forum.
badgerdave said:
Not sure if this helps...but this is what I did. I originally posted it on T-mo forum. At the very least it will put you in the ballpark...good luck. Just trying to help. These other guys know a lot more than myself. I'm sure the community will get you through it.
"Re: Leaked ICS in the wild!
Okay. Got it. Long story short:
1. Download file onto PC
2. Put file on SD card (I recomend different SD card.)
3. After it is on SD card, rename file "PH85IMG" *** No ".zip." ***
4. Power down phone
5. Remove/replace SD card
6. Remove battery
7. Replace battery
8. Power up the phone hold "power button and volume down" at the same time.
9. Hboot will appear...let go of buttons. the phone will then start reading the SD card. "Checking PH85IMG"
10. After that instructions will appear. At the bottom of the info you will see the prompt: "Do you want to start update?" Now Volume up for "Yes."
11. Once you volume up for yes it will begin checking the files. (After some time it updated a few files and the screen went black. I hit the power button and and it started updating all files.
In closing you "WILL" lose all info, contacts, text, email and any other setting on the phone. It will be just like when you pulled it out of the box for the first time."
Click to expand...
Click to collapse
Crashdamage said:
badgerdave made an excellent post and has it right - almost. I just want to clarify a couple of things.
First...he gave a link to the leaked RUU of the ICS OTA update. This file will install as he described WITHOUT requiring root and results in a phone in out-of-the-box condition - no root, with ICS 4.0:3 and Sense 3.6.
Second...the file must be named 'PH85IMG.zip' - WITH the .zip extension. A common mistake is to have file extensions hidden so when the file is renamed it is actually 'PH85IMG.zip.zip' resulting in installation failure.
Registered Linux user #266531. Android user since v1.0.
Click to expand...
Click to collapse
I tried the steps given and everything was going fine until step number 10. I never got a prompt asking to update my phone. Instead it just took me back to the hboot screen with the three androids skating at the bottom with the options: fastboot, recovery, factory reset, clear storage, simlock, image crc. I already had an ICS file downloaded from previous trials to install it, so I didnt use the link you posted, not sure if that matters or not. Anyways, I tried to hit recovery and then a picture of a phone with a red exclamation mark showed up. I then hit the volume up button and power at the same time. Then i went to "apply update from sd card" and then i got an invalid operation and the phone just rebooted normally without applying any update. Any ideas?
Kashif92k said:
I tried the steps given and everything was going fine until step number 10. I never got a prompt asking to update my phone. Instead it just took me back to the hboot screen with the three androids skating at the bottom with the options: fastboot, recovery, factory reset, clear storage, simlock, image crc. I already had an ICS file downloaded from previous trials to install it, so I didnt use the link you posted, not sure if that matters or not. Anyways, I tried to hit recovery and then a picture of a phone with a red exclamation mark showed up. I then hit the volume up button and power at the same time. Then i went to "apply update from sd card" and then i got an invalid operation and the phone just rebooted normally without applying any update. Any ideas?
Click to expand...
Click to collapse
First of all before getting to a solution, you need to point out your device info, that way nobody would be guessing, so provide the following and we'll work from there:
hboot version:
software version currently:
s-on or s-off:
bootloader unlocked: yes or no
carrier:
from there solving your problem would be very much more simple.
Dark Nightmare said:
First of all before getting to a solution, you need to point out your device info, that way nobody would be guessing, so provide the following and we'll work from there:
hboot version:
software version currently:
s-on or s-off:
bootloader unlocked: yes or no
carrier:
from there solving your problem would be very much more simple.
Click to expand...
Click to collapse
this is what is see on the hboot screen:
" ***LOCKED***
RUBY PVT SHIP S-ON RL
HBOOT-1.90.0004
eMMC-boot
Sep 15 2011, 18:13:11 "
The bootloader is locked, The carrier is T-Mobile USA. Im running on Android version 2.3.4 and the software version is 1.36.531.6. I also took a look at your tutorial for installation before I tried to do it myself.
Kashif92k said:
this is what is see on the hboot screen:
" ***LOCKED***
RUBY PVT SHIP S-ON RL
HBOOT-1.90.0004
eMMC-boot
Sep 15 2011, 18:13:11 "
The bootloader is locked, The carrier is T-Mobile USA. Im running on Android version 2.3.4 and the software version is 1.36.531.6. I also took a look at your tutorial for installation before I tried to do it myself.
Click to expand...
Click to collapse
And what exactly was your result of attempting to manually update via the OTA files? Answer asap, I'll just move you on to the next method of getting it done via the latest leaked file if you can't get it done via the ota file.
Dark Nightmare said:
And what exactly was your result of attempting to manually update via the OTA files? Answer asap, I'll just move you on to the next method of getting it done via the latest leaked file if you can't get it done via the ota file.
Click to expand...
Click to collapse
Whenever I would manually search for the ICS update OTA, it would just say that my phone was already up to date (even though I am running on GB). Should I try to re-download the T-Mobile OTA file on 4shared that is on your tutorial? And then rename it to "PH85IMG.zip"? If not, please guide me to the next option/step. I really appreciate the help!! :good:
Kashif92k said:
Whenever I would manually search for the ICS update OTA, it would just say that my phone was already up to date (even though I am running on GB). Should I try to re-download the T-Mobile OTA file on 4shared that is on your tutorial? And then rename it to "PH85IMG.zip"? If not, please guide me to the next option/step. I really appreciate the help!! :good:
Click to expand...
Click to collapse
Redownload the ota file from here: http://d-h.st/tdM
Once you download it, place the file on your external sd card, not in any folders, just on the sd card.
Turn your device off
volume down and power on to boot into hboot
select recovery and wait for it to reboot
it should give you a red triangle error, ignore it and press volume up then power button
a recovery menu should pop up, once you see that menu, use the volume buttons to scroll down to the install update from external and hit power to select
it should give you a list of all the files on your sd card, use the volume buttons to highlight the file you downloaded and hit power to select, it should begin updating your device.
Dark Nightmare said:
Redownload the ota file from here: http://d-h.st/tdM
Once you download it, place the file on your external sd card, not in any folders, just on the sd card.
Turn your device off
volume down and power on to boot into hboot
select recovery and wait for it to reboot
it should give you a red triangle error, ignore it and press volume up then power button
a recovery menu should pop up, once you see that menu, use the volume buttons to scroll down to the install update from external and hit power to select
it should give you a list of all the files on your sd card, use the volume buttons to highlight the file you downloaded and hit power to select, it should begin updating your device.
Click to expand...
Click to collapse
ok, I followed the steps and tried it just now and I get an error message like this:
E:Can't open /cache/recovery/command
-- Invalid operation. --
Success Rebooting by reason: oem-00...
Also the the background is black with the red triangle error and the text is in yellow.
Kashif92k said:
ok, I followed the steps and tried it just now and I get an error message like this:
E:Can't open /cache/recovery/command
-- Invalid operation. --
Success Rebooting by reasonem-00...
also the the background is back with the red triangle error and the text is in yellow.
Click to expand...
Click to collapse
Yeah I expected that, seems only s-off users can proceed with that method.
This one should work fine though.
Download this file here: http://d-h.st/3VD
rename it PH85IMG and place it on the root of your sd card the same way you did the last file, it has to be named exactly that and in caps
reboot into bootloader, volume up when the file finishes loading, it's gonna install the update and reboot itself, let it boot properly, first boot may take a few minutes.
Dark Nightmare said:
Yeah I expected that, seems only s-off users can proceed with that method.
This one should work fine though.
Download this file here: http://d-h.st/3VD
rename it PH85IMG and place it on the root of your sd card the same way you did the last file, it has to be named exactly that and in caps
reboot into bootloader, volume up when the file finishes loading, it's gonna install the update and reboot itself, let it boot properly, first boot may take a few minutes.
Click to expand...
Click to collapse
The file is downloading right now. When I put the ICS file on the microsd card, do I rename it to "PH85IMG" or "PH85IMG.zip"? I'm also assuming that I have to follow the same steps you gave me on my last attempt to install?
Kashif92k said:
The file is downloading right now. When I put the ICS file on the microsd card, do I rename it to "PH85IMG" or "PH85IMG.zip"? I'm also assuming that I have to follow the same steps you gave me on my last attempt to install?
Click to expand...
Click to collapse
just PH85IMG, don't worry about the .zip part, it's already there, just not visible, no do not use the same steps, follow the steps I outlined above when I specified the file and what to do with it.