Related
I have tried to root my HTC Magic, using the Hero 1.4 ROM found on this homepage.
But something has gone wrong. i have followed the instuctions and done the same as all the other times i have root'et my phone.But now the phone won't start, it's "frozen" and only show the HTC MAGIC startup picture, and stays that way until i take out the battery.
Im getting more and more affraid that the phone is broken.
So i was wondering if anyone here could help me with this problem.
I can enter the recovery menu, and its possible for me to push a new update.zip file, and flash that and i have tried it but that dosn't help so all suggestions are welcome
Per
Home + Back when power up so you could get into fastboot menu. You then can flash your nandroid backup back into your phone.
Or get a ROM that worked for you in the past and flash it in recovery menu (update.zip).
I think you flashed the ROM that is designed for 32B board (HTC Magics with Google experience) in your Magic, which has the 32A board.
I did exactly the same thing! i first tried the HTC hero firmware from this thread: http://forum.xda-developers.com/showthread.php?t=531617
But after reading bachviet's response i got the other version from this thread:
http://forum.xda-developers.com/showthread.php?t=534464
So thanks Bachviet
Hey, thx for the answers, but i found another way of getting my phone to work again, kind off.
I used the recovery .img file found here on this forum (http://forum.xda-developers.com/showthread.php?t=530492) and then i just Nandroid restore, and it restored my phone back to when i bought it.
Now i only have a problem with the camera. it restarts my phone when i press the camera button in the menu. So think ill need to drop it off for repair, damn.
hi, here is an other method to resolve this problem.
I dont have sd card adapter, that is way I use adb to push a right update.zip and I use fastboot to wipe and apply the update.
(Sorry for my english)
1. put the right update.zip on "...\android-sdk-windows-1.5_r2\tools"
2. connect your phone using usb and start it (if is not)
3. open terminal in "...\android-sdk-windows-1.5_r2\tools" and type:
adb rmount (if is not success wait 10s and repeat it )
adb push update.zip /sdcard/update.zip
adb shell reboot (at the same time hold volume down button)
4.type:
fastboot boot recovery-magic.img
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.
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.
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.
Hey!
This is the issue: when I try to turn the phone on by just pressing the red button it goes directly to the fastboor menu. If I try to go to the recovery from there shows "TATTOO" for hours. If i try to go to the recovery dirctly by pressing HOME+ red button, it firsto shows the fastmenu for a second and tries to boot unsuccessfully. During this boot tries, I try to get some info with adb logcat, but the device is not casting anything. And well, if a picture is worth a thousand words, I guess a video is way better:
youtube.com/watch?v=zAejyMIVNGk (newbie, no urls!)
sorry for my english
And well, I have no idea how I got to this, this used to be my phone, but I bought a Nexus One and gave this to my sister, who has no idea what happened (as usual). Oh, this morning somehow I managed to get to the recovery menu, and booted until the android bootscreen, then vibrated and died again. I got to the recovery again, made a nandroid backup and wiped all data, it booted successfully, but the rom had no home application and ran really bad.
I was about to try to make a goldcard and install the stock RUU rom, but if I have no adb I cannot make one...
Any idea?
PS: the rom was nFinity 1.18 (2.2 Froyo) and the recovery was the lastest Clockwork.
PS2: I just realized that in every place I say fastboot I mean HBOOT, sorry again
sounds like recovery is still there, if you hold home + menu when phone if off , and then click red power button you should get recovery menu.
Then hopefully you can try full wipe and install a rom , rember the first time u boot a rom might take a few minutes
let me know how it goes
Yup, not using that method but I can manage to get to recovery sometimes. I'm trying to flash another ROM, but for some reason it doesn't let me. I've tried KalimochoAz (gingerbread) and HDCR (donut) and says something about assertion failed when checking if the device was click on the first case and in the second, complains about unsupported stuff...
I was about to try another roms by random but the SD does not refresh or even mounts, there must be something really messed up with this phone...
You can try to flash your stock rom from fastboot.
You don't need a goldcard, just run the update utility on pc, go to your temp directory and take the rom.zip file, rename it to CLICIMG.zip, copy it to sd card, put card on device and on fastboot menu pres vol down to start flashing the rom. I is the same version with the rom that device has before rooting, you will not get any errors.
I think there's a little misunderstanding here, mainly because of my confusion, it's not the fastboot menu qhat I get, but the HBOOT menu, and pressing the back button in order to access fastboot doesn't work...
oh I managed to boot something, I renamed the RUU exe to CLICDIAG.zip, because I could not find anything in C:\temp (is there where I have to look for the file?)
anyway, the zip appears to load on the phone, but once the progress bar completes, nothing happens... In my computer, the zip contains a .txt file and boot.img, but appears to be corrupt, and cannot extract any file (obviously, it's an exe)
so what do I do?
manutenfruits said:
oh I managed to boot something, I renamed the RUU exe to CLICDIAG.zip, because I could not find anything in C:\temp (is there where I have to look for the file?)
anyway, the zip appears to load on the phone, but once the progress bar completes, nothing happens... In my computer, the zip contains a .txt file and boot.img, but appears to be corrupt, and cannot extract any file (obviously, it's an exe)
so what do I do?
Click to expand...
Click to collapse
Of course will not work like this.
You must first run the RUU utility on pc and while is open to search your temp directory(maybe is inside another folder) for rom.zip file. This is the rom, the executable is an installation program which contain the rom and the app to flash the rom from pc packaged. You need only the rom.zip for flashing from sd card.
I've looked in the whole hard disk for that rom.zip after executing the RUU (I cannot get further than the step that tries to detect the tattoo, failing, so maybe it's not even created).
Apart from that, I managed to boot twice to what seems to be gingerbread, nFinity 1.18, but says in the lower left corner "Safe Mode" and I have no home application, no action on any button, just the notification bar and the lock screen. ADB doesn't work either.
manutenfruits said:
I've looked in the whole hard disk for that rom.zip after executing the RUU (I cannot get further than the step that tries to detect the tattoo, failing, so maybe it's not even created).
Apart from that, I managed to boot twice to what seems to be gingerbread, nFinity 1.18, but says in the lower left corner "Safe Mode" and I have no home application, no action on any button, just the notification bar and the lock screen. ADB doesn't work either.
Click to expand...
Click to collapse
You don't need to go so far. Just run the ruu utility and when the first screen appears go to temp dir(c:\users\you user's name\local\appdata\temp on windows 7). The executable is an encrypted package and when you run it extracts all included files and then starts the installation program. These files will deleted after this program exits(when the installation complete or an error occurs)
Cool! I just renamed it to CLICLIMG.zip and I finally loaded. The problem now is that when it finishes, instead of asking me to flash it, says
"CID Incorrect!
Update Fail!
Do you want to reboot device?
<ACTION> Yes
<POWER> No"
While running the RUU I made sure that it was for HTC Tattoo since it showed me the device during the steps. And I got it from a post describing the steps to flash it using the goldcard.
Furthermore, this error is something similar to what happened when I tried to flash from the recovery. This is REALLY weird...
Probably this isn't the sama as your device's stock rom. I think goldcard needed for flashing any htc original rom, but without goldcard only the device's version will be flashed successfully. Try to download other original roms if you don't know which you had before.
Here is a site with shipped roms for tattoo:
http://www.shipped-roms.com/index.php?category=android&model=Click
The RUU wasn't a problem, I tried now with a goldcard and flashed successfully! I could not get ADB connection to make it, but I once made one and still had the .img in my mail inbox.
But still nothing has changed...
pressing on drives me to the HBOOT screen, whose only options that work are "simlock" to flash CLICIMG.zip, and recovery (freezes on "TATTOO")
EDIT: does not freeze, but goes back to HBOOT after a while... ¬¬
You say that now you have the stock HTC rom and again you cannot boot it and instead the device reboots again to HBOOT?
Then maybe you have a hardware problem which leads to this behaviour.
OK, now I guess it still has warranty, but the problem is that I rooted it.
But now that I flashed somehow the original rom, should be no problem right?
Yes, if you successfully flash the stock rom, you're not root any more.
had that problem to, but theres easy fix for it without doing all whats being sayd here
Even tho phone dont boot annymore and stays on logo plug in the usb cable
and work with adb shell and reflash recovery (to be good tattoo-hack.ko etc tricks need to be done before doing it or you get errors)
http://forum.xda-developers.com/showthread.php?t=716282 step 1.5 and tools from step 1.3
and ether get Amon RA recovery or clockworkmod and use
Code:
./flash_image recovery /sdcard/recovery.img
then reboot into recovery
HTML:
adb shell "reboot recovery"
mount usb put in a custom rom and flash it
if all done well should work (had same problem)
bascly adb still work even if you think you bricked phone just have to let it "startup"
Greetings
I'm afraid that won't work. I've been trying all the time with adb logcat and adb devices unsuccesfully. I thought that the TATTOO bootscreeb would give me some feedback in all cases, but now doesn't seem to work...
I've had similar problems when trying to flash nfinityGB.
My problem was that I missed something on the way from
- creating a gold card
- rooting device
- installing recovery
- flashing rom
All I did was to download and execute "RUU_Click_HTC_WWE_1.67.405.6_WWE_release_signed_NoDriver.exe" (or any other ruu).
Be shure to have SDK with all drivers installed properly.
After this your device is in unrooted (original) state as dancer_69 already told you.
Now you can decide whether to claim warranty or properly follow the guides on xda to get root and flash custom roms.
I think I know from long ago what is happening here, just couldn't believe it. Maybe the keys are sticked or something, that would explain the always going into fastboot mode without pressing the VOL DOWN key. Now it boots 1 out of each 5 tries, and when it gets to the home app, it's on "safe mode" (achieved by pressing MENU key while booting).
I think they will take care for it back in the HTC support (well, I hope)
manutenfruits said:
I think I know from long ago what is happening here, just couldn't believe it. Maybe the keys are sticked or something, that would explain the always going into fastboot mode without pressing the VOL DOWN key. Now it boots 1 out of each 5 tries, and when it gets to the home app, it's on "safe mode" (achieved by pressing MENU key while booting).
I think they will take care for it back in the HTC support (well, I hope)
Click to expand...
Click to collapse
Something like this thought when I said that maybe is a hardware problem.