[Q] HTC EVO Not Functioning - EVO 4G General

I have messed up my phone, and not sure exactly how.
When I first got my evo in august, it came with Froyo. I tried to root it using the procedures for 2.1, not knowing that it was for 2.2. My mistake. I went through the procedures, and it never worked. Then when the rooting for 2.2 came out, i tried to do that, but it didn't work. I followed the instructions from here and followed allong with the video on youtube. When I was pushing those files using the command prompts, they all worked, but that biggest file never came through.
On Tuesday, i was able to use unrevoked 3.2 to root my evo. I know it was successful because unrevoked said done when i finished. I was able to do the wifi tether on it, plus the screen shots, and superuser was asking for permisions, so I know it was fully rooted.
Today I tried to do a rom, and I was unsuccessful from the start. The phone wont start the recovery mode.
This is what it says:
SD Checking....
Loading... [PC36DIAG.zip]
No image!
Loading... [PC36DIAG.nbh]
No image or wrong image!
Loading... [PC36IMG.zip]
And then it will go to the next screen, which says:
Parsing...[SD ZIP]
[1] BOOT
[2] BOOTLOADER
[3] MICROP
[4]RADIO_VZ
[5] RECOVERY
[6] SPLASH1
[7] SYSTEM
[8] TP
[9] TP
[10] USERDATA
[11] WIMAX
Do you want to start update?
So I've pressed yes once before. However, my phone will not move past these screens. I can select all the options, like clear storage, power down, etc. I can't go into recovery. When I do, it shows a black screen with a phone and a red triangle with an exclamation point.
I won't say that it is bricked, but I know something isn't right. Have I messed up my phone beyond repair?

What rom are you trying to load?
Sent from my PC36100 using XDA App

Your phone is fine.You just need to install a custom recovery.You can use Amon-Ra or Clockwork you can find instructions for both in the Development Forum.
Sent from my PC36100 using XDA App

Do you have a pc36img.zip file on you sd card? From your log it looks like the third zip file was found and opened. If so, delete the file from your sd card and try again.
Sent from my PC36100 using XDA App

Install rom manager and then flash a working clockwork recovery. I use rom manager to also flash the alternative amon ra, which is my preferred recovery. Easiest way to flash/update between the two recovery options, IMHO.

I was wanting to do the Fresh 3.3. This will be the first ROM I've loaded.
I can't delete the pc36img.zip file off the phone because I can't connect it to the computer as a usb drive. When I turn it on, it just stays at that booting screen with the text. I can't access apps, or phone, or anything...

Related

Dream rooting gone wrong

So, after following this forum on and off over the past few months, I finally decided to root my Rogers Dream.
I was one of the first customers to receive a phone with SPL 1.33.0010, as mine was shipped to me directly from rogers as a hardware upgrade. Because of this, rooting was a little more difficult for me than I had initially anticipated, however, after having found this thread (http://forum.xda-developers.com/showthread.php?t=558301), I was able to downgrade to SPL 1.33.2005.
From this point, I started following the instructions found here: http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod. I was able to re-flash the downgraded OS, and rebooted to a T-mobile G1 splash screen. After going through the various steps, I got stuck where it said to reboot into recovery mode. I held down the home key while powering up, as instructed, but instead of booting to the recovery screen, I was greeted with an image of an exclamation point inside a triangle, hovering over a cartoon of a G1.
I was able to reboot using the 3 fingered salute (send-menu-power), but I was unable to load the recovery screen. I then attempted to bring up the boot loader by holding down the camera button while powering on. The screen I was greeted with did not resemble the boot loader I was used to seeing. It is composed of four horizontal coloured bars, and lists the phone information as follows:
DREA210 PVT 32B
HBOOT-0.95.000
CPLD-4
RADIO-1.22.12.29
Sep 2 2008
I'm looking for suggestions on how I should proceed from here. Any help would be most appreciated. Although the phone does make phone calls, and will send and receive text messages, it will not send or receive data, unless connected to wifi.
Thanks,
Grant
So I'm a little rusty but let me give it a shot. While holding home + power it may seem to just get stuck after a minute, but have you tried pressing alt + L ? This makes the recovery text visable (if it's not by default).
hope this helps..
Looks like you've ended up on the stock g1 bootloader.. did you flash the rc29 DREAIMG?
goldenarmZ said:
Looks like you've ended up on the stock g1 bootloader.. did you flash the rc29 DREAIMG?
Click to expand...
Click to collapse
Yes. The phone thinks it's a T-mobile G1, but it still works with my Rogers SIM.
sonikamd said:
So I'm a little rusty but let me give it a shot. While holding home + power it may seem to just get stuck after a minute, but have you tried pressing alt + L ? This makes the recovery text visable (if it's not by default).
hope this helps..
Click to expand...
Click to collapse
I did this, and the recovery text did indeed become visible, however, I now have a new problem.
I hit Alt+W as per the instructions in the wiki, and it reset the phone. I then hit Alt+A, and nothing happens.
This is the text I see on the screen when I'm in recovery mode:
Androind system recovery utility
E:Can't open /cache/recovery/com
mand
Home+Back - reboot system now
Alt+L - toggle log text display
Alt+S - apply sdcard:update.zip
Alt+W - wipe data/factory reset
After attempting Alt+A, I hit Alt+S, just to see what would happen. Of course, it tried to update from package, but returned an error because there is no "update.zip" on the phone. I'm tempted to rename "update-cm-4.2.5-signed.zip" as "update.zip", just to see what happens. I'll post again once I've done this, but any suggestions from more experienced people would be most appreciated.
Grant
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod
Alright, so I renamed "update-cm-4.2.5-signed.zip" as "update.zip", and it aborted the installation because there was no signature. I did the same thing with "signed-dream_devphone_userdebug-ota-14721.zip", with the same result.
It sounds like you still have the stock recovery image
jackslim said:
It sounds like you still have the stock recovery image
Click to expand...
Click to collapse
When you say stock recovery image, are you referring to the one I have installed on the phone already, or the one I'm trying to install with no success?
The image currently on the phone is the DREAIMG.nbh (rc29), which I downloaded via the wiki. The images I am trying to load also came from links in the wiki.
By recovery I'm refering to what you access when you boot with home + power where you can apply your updates (where you're seeing your triangle & exclamation point)
I just looked at cyanogen's wiki and it seems like that particular part could stand to be updated androidandme has a decent guide on how you could do this though.
http://androidandme.com/2009/08/news/how-to-root-a-t-mobile-g1-and-mytouch-3g-android-phone/
I'm not sure if flashrec works with RC29 which is what version you should be on after flashing DREAIMG.nbh, but you can give parts A1, A2, & A3 a shot, that would probably be the easiest way to update your recovery. If you can't get flashrec to work skip down to B2 and that will show you how to do it using telnet which does work from RC29
Once you update you're recovery image you should be able to apply "update.zip" or without renaming them by selecting the "apply any zip from sd" option
Thanks, Jackslim. I did as you suggested, and was able to install the CM update, as per the wiki, however, when it boots up, it shows the blue cyanogen android, and then reverts to a completely blank screen. I'm going to try reinstalling everything to see if that fixes it. Thanks for your help though.
gmupps said:
Thanks, Jackslim. I did as you suggested, and was able to install the CM update, as per the wiki, however, when it boots up, it shows the blue cyanogen android, and then reverts to a completely blank screen. I'm going to try reinstalling everything to see if that fixes it. Thanks for your help though.
Click to expand...
Click to collapse
After you install that recovery image you still have to go through the steps to install the ADP image before you add the cyangen update, then you should be cookin' with crisco
So just start back up on cyanogen's wiki from the section called "File Download"
Just to clarify, even though it is not booting up properly, I am now able to install whatever I want using recovery mode, so it's just a matter of figuring out what will work. Thanks again for all your help.
jackslim said:
After you install that recovery image you still have to go through the steps to install the ADP image before you add the cyangen update, then you should be cookin' with crisco
So just start back up on cyanogen's wiki from the section called "File Download"
Click to expand...
Click to collapse
I did get it working, thanks. Now I just have to reload all my contacts and apps, but I have already noticed a difference in device responsiveness. It's like going from Windows Vista to Windows 7. Thanks again.

red triangle with exclamation point on recovery screen

figured it all out.. thanks!
Means you don't have a recovery. Need to most likely run the 2.1 ruu and reroot with eris one click. Something went wrong and it didn't flash Ra recovery
i hope your ok buddy,try it again but check if the root me.zip file is in your sd card first before you go into recovery,if its their it should of flashed the recovery.
Sent from my Vanilla Tazz using Tapatalk
thank you. i googled and found instructions for flashing amon ra recovery. but it fails in the first couple steps. when it tells me to run "su" from the shell command it tells me permission denied. the phone is not rooted yet, so i can not allow superuser from the phone as most of my googling has suggested.
what now?
the rootme.zip is on the sd card.
did u reboot after you pressed the button? and then did u turn it off and go to recovery?
mindnumbinglyfun said:
trying to root my friends phone (using the one-click root for eris) ive run into a problem i havent seen before, and cant find answers for on google or this site.
when i reboot the phone into recovery holding volume up with powering on, i get a picture of the eris, with a red triangle and exclamation point. and thats it. i cant do anything.
any idea what it is or how to get rid of it?
Click to expand...
Click to collapse
That is the splash screen of the stock recovery.
It means that flashing of Amon_RA never happened.
[ For goofs, you can prove it is a stock recovery by pressing Vol-up+End again when that image is on the screen. (If you were rooting a Cupcake Eris, the key sequence would be Home+End) ]
As others have pointed out, the primary reason that OneClick fails is that the person using it fails to perform a normal reboot in between use of the app and cold-booting into the recovery. Just reboot your phone once normally, shut it down, and then cold-boot to recovery.
- install app
- run app
- shut down phone normally
- reboot phone normally
- shut down normally
- cold boot into recovery
One more thing; you know that this is not a development topic, yes?
bftb0

Ultimate Guide: How to root any myTouch/Magic and install custom recovery/ROM!!!

AS OF RIGHT NOW THIS WILL NOT WORK FOR 32A DEVICES WITH THE 6.35 RADIO
I AM NO LONGER SUPPORTING THIS THREAD SINCE I HAVE MOVED ON TO THE HTC SENSATION AND NO LONGER HAVE A MYTOUCH 3G TO MESS WITH. THIS DOES NOT MEAN THAT YOU CAN NO LONGER POST ISSUES IN THE THREAD SINCE OTHER MEMBERS WILL HOPEFULLY STILL HELP OUT.
As Amon Ra put it:
"The following instructions :
will void all warranties of your phone!
will erase all your userdata!
will change your current ROM/SPL!
will change your current splash screen!
could brick your phone!
Proceed at your own risk!"
There's been a lot of questioning about how to root the new 2.2.1 updates that have rolled out for myTouch users to get a custom ROM loaded. So I decided to create an updated guide. I'm writing this as I'm rooting my own myTouch 1.2 so it should be pretty accurate, but we'll find out. Please please please read through this whole post before doing anything! Without further adu, let's begin.
1. First thing you need to know is what kind of myTouch you have. With the phone turned off, boot into fastboot by holding (back+power). You'll get something that looks like this:
Code:
Sapphire PVT 32A Ship S-on G
Hboot-1.33.0013 (Sapp31000)
CPLD-13
RADIO-2.22.23.02
Oct 21 2009
What your looking for is whether you have 32A or 32B in the first line and what you've got in the radio line. Write this down for reference later on. (If you have a myTouch with the headphone jack on top, you need to read this first.)
2. Let's go ahead and get all the downloads out of the way since this is probably the single longest step. Download each of the following items:
Everyone - AndroidSDK
Everyone - SuperOneClick, just download the latest version at the bottom of the first post.
Everyone - CyanogenMod 5.0.8-DS
Everyone - Google Add-on for CM 5.0.8
Only if the first line in fastboot says 32A and you DO NOT have a headphone jack - EBI1 Port for CM 5.0.8
Only if the radio line says 2.22.27.08 or 2.22.28.25 - New Kernel for New Radio's
It may make it easier to put all the files in the same folder once downloaded. For example, open "My Documents" and make a new folder called "Phone Stuff" and put everything in there.
3. Extract the contents of the "android-sdk_r08-windows.zip" files to any folder (just make sure you know where). After extracting, using file explorer find the file called "SDK Manager" and open it. When it starts up a window will pop-up with "Choose packages to install" in the upper left-hand corner, just click Cancel. In the left pane, select "Available Packages", then in the right pane, expand "Third party add-ons", then "Google Inc. add-ons", and finally check "Google USB Driver Package". In the bottom right-hand corner, click "Install Selected". In the window that opens, make sure "Accept" is selected, then click install. Select "Yes" in the next window and close everything out.
4. With the phone powered on and sitting at the home screen, press Menu->Settings->Applications->Development->Look at "USB Debuggin" and make sure it is turned on. Now, plug the phone into the computer with your USB cable. Mount your SD card to the computer using the option in the notification bar. Copy over the CM 5.0.8 and Google Add-on to the root of your SD card.
5. Back on the computer, locate the SuperOneClickv*.zip file and extract it to a folder (make sure you know where). Navigate to that folder, and open the SuperOneClick.exe. Once it starts up, hit the "Root" button.
Here's the tricky part, if you see a line saying "***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***" then do as it says and turn off "USB Debugging" on the phone. Wait until the program shows "Waiting for device..." and turn USB Debugging back on. It may take a few tries before the program finishes. Your phone may do some funky stuff, such as the screen going black showing "Android System" at the top, just let it sit and once it starts responding again, turn USB Debugging back on. Once the program finishes, it'll say "Root files have been installed! Would you like to run a test?" click yes. In the next prompt, click OK. Once you get a pop-up saying "Your device has been rooted! Would you like to donate?" click yes to donate to the program's creator or click no to continue on. If you get "failed" whenever running the root test from SuperOneClick, you need to run the program again.
5a. Reboot the phone.
6. Now, from the phone, download ROM Manager and SuperUser from the market and install them.
7. Once they both are installed, open ROM Manager. Click "OK" to both the prompts that come up. At the top, click the "Flash ClockworkMod Recovery" button. A prompt will come up asking you to confirm your phone model. If you have a 32B phone or the myTouch 1.2 (headphone jack), select "ION/MyTouch 3G". If you have a 32A phone without a headphone jack, select HTC Magic. Once it has finished flashing, click OK. Scroll to the bottom of the ROM Manager menu and select "Flash Alternate Recovery". If you have a 32B/1.2 phone you should see "RA Recovery v1.7.0G". If you have a 32A without a headphone jack, you should see "RA Recovery v1.7.0H". Once verified to be correct, select that option and then click OK. Once completed click OK again. Power off your phone.
NOTE: I use these steps to get Amon Ra's Recovery installed since the steps in this guide will be using it and not Clockwork Mod. If, after getting more familiar with using recovery, you want to use ClockworkMod recovery instead, the steps are the same, just don't select the "Flash alternate recovery" option.
8. With the phone powered off, hold down (home+power) to get into your new custom recovery. Here you'll use the trackball to navigate the menu's, press the trackball to select, and the back button to go back. From the main menu, select "Backup/Restore", then select Nand backup and press the home button to confirm. Once it's completed the backup, use the back button to get back to the main menu. Select the "Wipe" option, then select "Wipe data/factory reset", press home when prompt, then press "Wipe cache", hit home when prompted, then select "Wipe Dalvik-cache", hit home when prompted, and finally back out to the main menu. Select the "Flash zip from sdcard" option, first select the CM 5.0.8.zip and hit home to confirm, then the Google Add-on file and select home to confirm.
8a. If you have a 32A device WITHOUT a headphone jack, you'll now also flash the EBI1 port (boot-cm_2634.7_ds_32a-oc-uv-xtra-fp-091310) and hit home to confirm when prompted.
8b. If you have either of the new radios (2.22.27.08 or 2.22.28.25) then flash the new kernel (ezBiffTestKernel20110222-2708_S.zip) and hit home to confirm when prompted.
NOTE: If you don't get into the custome recovery (you get a picture with a phone and a triangle with exclamation mark) boot back up as normal and repeat step #7.
NOTE 2: The backup you make is in case anything goes wrong and the ROM doesn't boot. Go back into recovery, select the "Backup/Restore" option, then select the "Nand restore" option. Just click the trackball throught the menus and hit home to confirm when prompted, then reboot.
9. After flashing all the files, back out to the main menu again and select "Reboot system now". It will take about 5-10 minutes for your phone to boot the first time. Once your in, enjoy.
If you need help and I'm not on here, feel free to try and get up with me on Google Talk or MSN at [email protected].
Thanks to Amon Ra for his recovery images!
Thanks to the Cyanogen team for an awesome ROM!
Thanks to Pershoot for his awesome kernels!
Thanks to CLShortFuse for his awesome app!
Thanks to the ClockworkMod team for their awesome app!
Thanks to MarcAntonyy for pointing out I'm a retard!
Resources:
SuperOneClick
Kernels
CyanogenMod
OK, I've updated the original guide with ezTerry's kernel that will work with the 2708/2825 radio's, which should completely alleviate people running into bootloops.
Things I deem important.
1. CLShortFuse is rolling out updates for SuperOneClick, so now the link directs you to his post instead of being a direct download.
2. I updated the guide to flash CM 5.0.8 instead of CM 6.1. Some people are having issues getting CM 6.1 flashed, plus CM 5.0.8 (for me at least) is much more stable than CM 6.1.
3. Added steps to take if the first guide ends with you being in a boot loop in the second post.
4. First guide updated to hopefully keep users from running into the boot loop.
OK
Remounting system with read-only access...
OK
Running a SU test...
Test failed!
FAILED
Is this normal?
No, try running the program again.
Did you get my PM, the one I sent you isn't showing up in my "Sent" items. For some reason your /system partition is full, so SuperOneClick is failing trying to push the SuperUser.apk. Try installing SuperUser from the market and then running SuperOneClick.
Yeah. Still nothing. Could the update possibly lock me from rooting?
Sent from my T-Mobile myTouch 3G using XDA App
No, I did this guide from the 2.2.1 update. Did you pull it OTA or did you manually do the update? Just to be sure, it's still failing after installing SuperUser from the market, correct?
Got root, but cant install recovery
Used superoneclick and all went well. I cant get a alt recovery on my phone though. once i reset the phone, holding the home button I get the green screen with th fastboot usb in the right corner. I have full sdk with limited adb skills. I need Clockwork or preferably AmonRA. I get superuser permissions and all but I am trying to avoid re-partioning my card. Is there a way around this?
Installing a recovery will not repartition your SD card. Actually, nothing in this guide will partition or require that you partition your SD card.
It was the manual update.
Sent from my T-Mobile myTouch 3G using XDA App
Something might have been hosed. Do you have the 3.5mm jack? You may want to try booting into recovery, do a data wipe/factory reset, reapply the update, then try rooting again. You should be out of system memory. Another quick thing you can try is turn your phone off and start the program. When it gets to "waiting for device" turn your phone on with USB debugging on. Yeah...try that first, then reapplying the update.
On a side note, the developer of SuperOneClick is working on version 2.0, which will hopefully fix the issue your experiencing plus the issue with having to toggle USB debugging, but for the time being, let's get this figured out.
I am going to try this guide, this will be my first time rooting as i have a 2.2 fender mytouch will this guide work?
how long will this take? i have to work in an hour lol
Assuming everything goes smoothly, about 30 minutes. Honestly though, nothing in the guide will prevent you from using your phone until you start flashing the custom ROM. Furthermore, once you get rooted with the program and get ROM Manager working and move the files, you won't need a computer anymore.
Maybe print the directions and take them with if you can use your phone while at work. Yes this will work on a Fender with the new update. I made it using my 1.2 on the update, which is pretty much the exact same thing.
it would be hell of alot easier with a Youtube Video guide? that way we can follow exactly step by step without messing up the phone! also will i be able to sign in using WIFI? beause there is no data coverage in my area of living. if i user superoneclick will that reset my phone to factory settings and make me sign into google again? lol i dont wanna drive 2 hours to the nearest data coverage area. pain in the ass lol
SuperOneClick just roots the 2.2.1 ROM to allow you to use ROM Manager so no data reset in that part. You will be doing a factory reset when you flash CM 6.1, however CM 6.1 will allow you to update over wifi. Even if something happens when you start flashing CM 6.1, you can restore your backup that you make following the guide, which will still be activated. Are you living on the top of a mountain or something? I haven't been anywhere that gets a signal without data coverage (at least G).
lol check my zip code 50501 you'll see i have no data coverage for miles lol its ridic. and we use a partner web with t-mobile.
Dude, that sucks, I think you went with the wrong carrier, lol. Are you in the Army? Navy here.
Ahhh, your roaming on AT&T's network. You just need to enable roaming data. Go to Menu->Settings->Wireless & Networks->Mobile networks->And check "Data roaming". T-Mobile doesn't charge for domestic roaming, so as long as your in the US, you'll be good.
OK , cool but,
still an issue with recovery. I try to install a recovery image via fastbooot and it wont read it. wiping my card is redundant. but if I must? Then I willThat is an excellent tool though.

[Q] Got my phone stuck on TMOB my touch logo? Doesnt seem to boot at all need help!!

Hello everyone...
I have a newly bought HTC MT4G
Really need some help..
My phone got stuck with the tmob welcome logo after successfully temproot and permaroot...it does not seem to continue through the phones interface...I removed the battery and attempted to load factory reset and recovery reset..no luck at all..still got stuck...this is how my bootloader looks like:
GLACIER PVT ENG S-off
HBOOT-0.85.2007
MICROP-0429
RADIO-26.03.02.26_M
emmC-boot
OCT 11 2010 12:44:14
HBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
SYSTEM INFO
IMG CRC
I dont know what to do with the phone now...been reading a lot but it seems i get more confused..tnks really appreciate it
You must have the adb and fastboot binaries for this to work. There are several threads on xda to get those to work. Once you have that working, go to the clockwork recovery thread and download clockworkmod recovery 2.5.x.x. Then copy that to your /AndroidSDK/tools folder. Boot your phone into HBOOT mode. Select Fastboot. Plug your phone into your computer. Let it load the drivers. Open up a command window (DOS) by pressing the window button + R and typing cmd and press run. Change the directory to your /AndroidSDK/tools folder (cd /AndroidSDK/tools). Then type:
fastboot devices
It should return your phone's serial number. Then type:
fastboot flash recovery
DO NOT HIT ENTER YET! Put a space after recovery, then drag and drop the recovery file from your tools folder onto the command screen window. Now press enter.
It should say sending recovery....Okay. Then writing recovery.....Okay.
After that select bootloader from the fastboot screen. Then once it changes to HBOOT mode, just select recovery and it'll boot you into clockworkmod recovery where you can flash any rom you need to.
ok Im gonna try this step by step...hopefully I my phone aint bricked.. tnks so much!
Don't worry, your phone is far from bricked! As long as HBOOT mode is available to you you're fine! I'll try to find the link to the original ROM so that way you can just flash that through HBOOT if this process doesn't work. This process will allow you to keep your engineering bootloader (0.85.2007). Flashing the original ROM will make you have to go back through the rooting process. I really hope you get this to work! Good Luck! And by all means you can PM me with any questions you have. That way I can get back you faster. If you include your email, I can respond right away.
EDIT: Here is the link to the Stock 2.2.1 update. This will undo root. So use that as a last resort. But it will definitely work!
You want to download the PD15img.zip
http://forum.xda-developers.com/showpost.php?p=10781618&postcount=3
HI again!! so far so good...I do manage to understand and execute the process of adb flash recovery...but as soon as I choose recovery from HBOOT mode...my phone seems to freeze immediately to tmobMyT4g logo...and it seems to stay a while from there...1st question is..do I need to unplug my usb connection from pc then press recovery?! or do i keep it plugged in...for now...Im gonna try the original recovery.img for it...I'll just have to start all over again to permaroot the phone...
paolocab2000 said:
HI again!! so far so good...I do manage to understand and execute the process of adb flash recovery...but as soon as I choose recovery from HBOOT mode...my phone seems to freeze immediately to tmobMyT4g logo...and it seems to stay a while from there...1st question is..do I need to unplug my usb connection from pc then press recovery?! or do i keep it plugged in...for now...Im gonna try the original recovery.img for it...I'll just have to start all over again to permaroot the phone...
Click to expand...
Click to collapse
to reboot the phone while in fastboot just type
# fastboot reboot
Click to expand...
Click to collapse
same results still...ends up with the logo...BTW with the original ROM PD15... do I use it as an image file or follow the instructions on this thread?http://forum.xda-developers.com/showpost.php?p=10781618&postcount=3
can you show me exactly what the command window is telling you? From what I understand, you typed
fastboot devices
and got back your phone's serial. then typed
fastboot flash recovery C:/what/ever/the/path/is/to/recovery.img
and got back
sending recovery...okay
writing recovery...okay
and then went to bootloader
and attempted to reboot to recovery
if this is the exact process you used, i'm not sure what could be the issue.
and the pd15img.zip, you will follow the instructions in the post
Iriscience said:
can you show me exactly what the command window is telling you? From what I understand, you typed
fastboot devices
and got back your phone's serial. then typed
fastboot flash recovery C:/what/ever/the/path/is/to/recovery.img
and got back
sending recovery...okay
writing recovery...okay
and then went to bootloader
and attempted to reboot to recovery
if this is the exact process you used, i'm not sure what could be the issue.
and the pd15img.zip, you will follow the instructions in the post
Click to expand...
Click to collapse
no.1
Yup exactly what I did...seems frustrating...any method i use goes to the same logo freeze...but before this happened...in the first place...I tried to replace the (system/bin) folder on the root...coz i haD this issue of placing back my original WPA_supplicant becoz it seems that it wasnt detecting WIFI networks at all...then as soon as I restarted goes stuck with the logo...I was hoping that I could flash it back with the original ROM...then now its this...
no.2
Also when i try to use the older recovery.img, it goes to that red triangle with a exclamation mark angle...
no.3
I also tried to restore to factory settings from the HBOOT menu...it goes after wards to the logo after having that cellphone green cycling icon and a status bar...
No.4 as soon as try the steps on the PD15img.zip methods... I dont see any phone detect options or begin update options...it all ends up with the tmobile logo
paolocab2000 said:
No.4 as soon as try the steps on the PD15img.zip methods... I dont see any phone detect options or begin update options...it all ends up with the tmobile logo
Click to expand...
Click to collapse
When you do the PD15IMG method you store the PD15IMG on the root of the SD card and turn the phone on holding the power and volume down button. It should never get to the boot image.
neidlinger said:
When you do the PD15IMG method you store the PD15IMG on the root of the SD card and turn the phone on holding the power and volume down button. It should never get to the boot image.
Click to expand...
Click to collapse
Well like what the method instructed...as soon as I press the power+volume down..it goes straight ahead to my Hboot menu...THe options mentioned on the above method doesnt seem to appear.
paolocab2000 said:
Well like what the method instructed...as soon as I press the power+volume down..it goes straight ahead to my Hboot menu...THe options mentioned on the above method doesnt seem to appear.
Click to expand...
Click to collapse
as soon as you boot into the bootloader does the system check for the PD15IMG?
neidlinger said:
as soon as you boot into the bootloader does the system check for the PD15IMG?
Click to expand...
Click to collapse
yup it does check for it very quickly then after that...HBOOT menu...then as soon as I choose one from the menu..i get stuck with the Mytmob logo...
paolocab2000 said:
yup it does check for it very quickly then after that...HBOOT menu...then as soon as I choose one from the menu..i get stuck with the Mytmob logo...
Click to expand...
Click to collapse
when it searches for the image is it telling you "image not found", and did you extract the stuff to the SD card or leave it compressed?
neidlinger said:
when it searches for the image is it telling you "image not found", and did you extract the stuff to the SD card or leave it compressed?
Click to expand...
Click to collapse
I dont get to received any error message such as image not found...and yes I leave the PD15img.zip file as it is uncompressed..
AAAhhhh at last!>!! something worked!!! I followed this link/thread http://forum.xda-developers.com/showthread.php?t=919834
The only clockmod that worked for me is 3.0.0.0. reinstalling stock rom as of now...I guess I have to restore to defaults for now...and attempt to install custom roms some other day!! Tnks to all who helped...!! For now...
Just to let you know, you'll only be able to flash Gingerbread ROMs with ClockworkMod 3.0.x.x. You have to use CWM 2.5.x.x to use Froyo ROMs. Just wanted to make sure you knew that, so you don't get into another "brick" kind of situation.
Iriscience said:
Just to let you know, you'll only be able to flash Gingerbread ROMs with ClockworkMod 3.0.x.x. You have to use CWM 2.5.x.x to use Froyo ROMs. Just wanted to make sure you knew that, so you don't get into another "brick" kind of situation.
Click to expand...
Click to collapse
I do believe you are correct...it so happened that i have tried loading Clockworkmod
2.x.x.x and 3.0.0.5 and the only thing that passed through the logo and showed the menu is 3.0.0.0...
I also made a mistake in placing the PD15img.zip file on my SDCARD as "PD15img.zip.zip" because the extensions are already associated and it its these small things that one has to be really careful about the certainty of the process step by step.
Anyways as soon as I corrected the file name...my HBOOT loader automatically did the job..but I am back to square one...but this time IM gonna use the older clockwork MOD to install Froyo roms...which my main problem in the first place was losing my WPA_supplicant file..in which I lost the WIFI connection capabilities of the phone..in which it made it difficult for me to access key files to reflash and boot the phone again as a default factory phone...

[Q] my htc magic keeps rebooting after flashing an old recovery image

Hi
I had a problem with my htc magic after trying to flash the RA-sapphire-v1.0.0 recovery image into the phone. Before the problem occurred I rooted my phone and flashed RA-sapphire-v1.6.5, but because I had an issue with it I tried to flash an old version " RA-sapphire-v1.0.0".
Now my phone keeps rebooting endlessly and I can not access recovery mode, fastboot or anything else?
Is it bricked? Can I fix this issue?
The phone is 32A
Radio is 6.35 (I can not access fastboot so this is from my memory)
If you have no access to fastboot nor recovery, then you are pretty bricked!!!
Are you sure you can't get into fastboot? Pull the batter, press and hold down the back button, and put the battery back in. See if it goes into fastboot then. Do the same thing again, but holding the home button instead to see if you can get into recovery. I dunno why you used an old one and not the new one.
DonJuan692006 said:
Are you sure you can't get into fastboot? Pull the batter, press and hold down the back button, and put the battery back in. See if it goes into fastboot then. Do the same thing again, but holding the home button instead to see if you can get into recovery. I dunno why you used an old one and not the new one.
Click to expand...
Click to collapse
I tried both method and it did not work. The phone is still rebooting endlessly. I used the old recovery since the new one kept restarting the phone to the actual system after I go into recovery mode after 2-3 seconds.
1.6.5 isn't the new one. The newest version is 1.7.0. Well if that didn't work, then year your bricked.
so is there anything i can do to fix it?
JTAG is your only option.
Where are you from ?
usernome said:
Where are you from ?
Click to expand...
Click to collapse
I am from Australia
I have HTC Magic Vodafone (32B) and have a similar issue with phone in a reboot loop, however, i can get into fastboot but not sure what next to do. Is there a guide anywhere on what to recover my phone.
Depends, what is your current fastboot information?
Not sure what info you want from Fastboot screen so this is everything i can see
SAPPHIRE PVT 32B SHIP S-ON G
HBOOT-1.33.0013 (SAPP10000)
CPLD-10
RADIO-2.22.28.25
Oct 21 2009,22:33:27
Is this the right kind of information?
Two options. Downgrade to 1.5, then update to 1.6, then root, flash a custom ROM, reinstall the 1.33.0013 SPL and 2.22.28.25 radio, and then flash a new custom ROM. Optionally, you can downgrade to 1.5 and upgrade back up to 2.2.1. Either way just let me know and I can assist.
Thanks for you help with regards to the approach, is one easier than the other? If they are both roughly the same then would go for the Downgrade to 1.5 and upgrade back up to 2.2.1. route as it may be easier to sell in a few weeks when the Galaxy S2 out.
So, here we go, please read through all the steps before starting and then reading each step as you go along:
1. Go here and download "sappimg.nbh" and "update1-5.zip".
2. Put all of them on your SD card. I would suggest downloading to a folder on your computer, then copying them over. Have had issues in the pass with people downloading files directly to their SD card and it corrupting the file.
3. With the phone turn off and the SD card in it, boot holding (volume down+power) to get into hboot. The phone should detect the sappimg.nbh, check the file (you'll see a progress bar in the upper right-hand corner), and then ask you to hit "ACTION" to continue. (ACTION being pressing the trackball)
4. The phone will start flashing the different parts of the phones partitions. You'll see the progress bar in the upper right-hand corner a few more times, then after about 5 minutes, it'll ask you to hit "ACTION" again to reboot.
5. Let the phone boot all the way up (this may take a few minutes) and then turn it off without signing in.
NOTE: Unless you need the phone to access the SD card from the computer, in that case sign in and do the next step.
6. Access the SD card, find "update1.zip" and rename it to "update.zip".
7. With the phone off turn it back on by holding (home+power) to get into recovery. You'll see a triangle with an ! in it, press (home+power) again to bring up the menu.
8. Using the trackball, scroll to the "wipe data/factory reset" option and press the trackball to select it. After it completes, scroll to "apply update.zip from SD card" and select it. It should pickup the update file on the SD card and flash it, then reboot.
9. When you get to the login screen again, turn the phone off.
Note: Again, as before, you can optionally login to get into the ROM for access to the SD card from your computer.
10. Repeat steps 6-9 for the "update2-update5.zip" files. You will need to remove the old "update.zip" before renaming the next update file. When you get to the login screen the last time (after flashing "update5.zip") you can sign in and use the phone.
Thanks for the guide but I've hit a problem. The phone recognise the sappimg.nbh and starts to flash itself but when then a message:
model ID incorrect!
Update Fail!
appears and the flash has failed. I've tried this a few times now downloading the file again, formating the SD card etc but to no avail. Do you have any suggestion on how to get round this issue?
Geffen22 said:
Thanks for the guide but I've hit a problem. The phone recognise the sappimg.nbh and starts to flash itself but when then a message:
model ID incorrect!
Update Fail!
appears and the flash has failed. I've tried this a few times now downloading the file again, formating the SD card etc but to no avail. Do you have any suggestion on how to get round this issue?
Click to expand...
Click to collapse
Crap gave you the wrong sappimg. What country did you get the phone from?
Sent from my LG-P500 using Tapatalk
I got phone from Vodafone in the UK.
Geffen22 said:
I got phone from Vodafone in the UK.
Click to expand...
Click to collapse
Need the specific country.
United Kingdom or England to be exact.

Categories

Resources