Related
First off im sorry im adding another rooting post to these boards.
So i decided to root my 32B magic today copyed the recovery.img over and update file from the rooting wiki, loaded recovery mode then updated, but now my phone when turned on loads to the vodafone screen and freezes id left it for afew hrs but still no luck.
Here is what i know so far:
I am able to get to fastboot and fastboot usb
I cant however get to recovery mode by pressing menu+power
I can get to the recovery mode using the sdk\tools
my problem is that im sure the fix is relativly simple i.e. load some files onto sd and start again, but the problem is that i have no other way to load the files onto the sd card than through the phone and my knowledge of adb isnt that great although has improved greatly today lol.
Im not sure how correct i am on this, but would it be a possible fix to load say a rom update.zip onto the sd card and load that through recovery mode to bring it up? If that would fix it could i possible get help on the adb code needed to pass the file from computer to the phone through fastboot usb or recovery.
Thank you very much for your help
Ok i think i have figured how to push files to my sd card however whenever i try it come up saying Failed ( remote:signature verify fail)
ok well i managed to move Cyanogen's newest rom over and update to that but its still hanging up at the vodafone screen upon booting, im lost for ideas.
Please any help how ever small would be amazing right now.
please help is desperatly needed.
i am having the same issue.... and it seems NO ONE has a bloody answer to why it is failing
I successfully update to 32A and root. Then i tried to update to MT3G OTA rom and now i'm stuck at Vodafone screen. Need help or ideas and how to recover..
i had the same problem, what i did was that i found a sd card adapter and hooked it up to my computer, its pretty quick and less hassle
waacow said:
I successfully update to 32A and root. Then i tried to update to MT3G OTA rom and now i'm stuck at Vodafone screen. Need help or ideas and how to recover..
Click to expand...
Click to collapse
take out your battery and after a few seconds put it back in, before it powers up go into fastboot(back+power) and that should do it
I still have a pretty red splash screen and stucked.
neoxtian said:
take out your battery and after a few seconds put it back in, before it powers up go into fastboot(back+power) and that should do it
Click to expand...
Click to collapse
I have same problem, but your solution didn't work for me.
I did as follows.
#1. typed following command in terminal.(well, I'm using Mac)
Code:
fastboot-mac flash recovery recovery-RAv1.2.0G.img
#2. pulled battery off from phone.
#3. pluged USB cable to phone and also Mac.
#4. pressed (ENTER) in the terminal, then fastboot-mac said '< waiting for device >'.
#5. put the battery in while pressing (back)+(power)
#6. then, pretty red vodafone splash screen come up.
#7. In the terminal, it still said '< waiting for device >'. Nothing was changed.
#8. On the phone, pretty red splash screen was still there. Nothing was changed.
Those are all I have done many times for last 2 days.
But, it didn't work.
Please let me know if there is something I missed.
I tried and stuck in the exactly same problem as [robotician]. I have MT3G.
robotician said:
#5. put the battery in while pressing (back)+(power)
#6. then, pretty red vodafone splash screen come up.
#7. In the terminal, it still said '< waiting for device >'. Nothing was changed.
Click to expand...
Click to collapse
THe red vodafone should not come up. You have to hold the back key longer perhaps, because it's supposed to go into the fastboot screen with all sorts of text and three androids on skateboards at the bottom.
@Niaski
was your rom made for the 32B or the 32A?
They are very diferent phones and mixing the roms causes the issue you are seeing.
I have searched for about 3 days now with no luck. does anyone know where I might be able to get a stock rom from a mytouch 3g with the new updates?
This is for the myTouch (from Dmaki650 on the T-Mobile forum): http://www.megaupload.com/?d=PER2DXQF
I also have the one for the G1.
i finally found what i needed thanx. no i have a different problem.
how can you install this update
1.) Download signed-opal-DRC92-from-COC10.1c9..zip from internet
2.) rename to update.zip and move to root directory on sdcard
3.) boot phone holding home+power button
4.) once picture is up, push home+power button again to bring up menu
5.) flash your device
6.) reboot
i tried your steps and downloaded the package from the link above, but it says verification failed?!
Worked for my mytouch (32B). Maybe your download got botched.
i have google ion 32b also
Ok I'm kinda a newbie...I've searched the forums and can't find my solution.
So I installed CM 7 on my nexus one from Rom manager. Everything is ok...so I decide to put google add ons ( froyo). This is what happens now... I get the Cyan logo animation , then the green google sign up logo then the phone reloops to the cyan logo and then the google sign in logo...I cant access nothing on my phone.
I boot into recovery ( power +trackball) , go to recovery option click on power and then I see the X (phone vibrates ) then I get a black screen...and nothing happens.
I did do 2 working rom recoveries from clockwork...I just cannot access them to recover my old working images....Can someone help or did I brick a new phone...
Thanks
just like basketball.......... brick
Maybe try to push a new recovery through ADB?
ok how to do that ADB?
What is ADB ...can someone please help
Thanks
You shouldn't be flashing pre-beta firmwares if you don't know how to use adb.
Use Google or the forum search to find out all about adb.
Also, if the phone is booting as far as the Cyanogen logo, then it's not even remotely "bricked", it does sound like you've managed to stuff up the recovery though, probably ROM Manager's fault, it has a habit of breaking things horribly.
Boot into fastboot and flash the latest Amon Ra recovery, then boot into recovery, do a full data wipe and flash a standard firmware back on.
Yep it's dead, send it to me because I'm building a house.
OK so I fastboot with sdk ...
Because the recovery option just send me to the dreaded X and then nothing
Not bricked. The best people to help you through it the fastest are on the Cyanogen Mod IRC Chat. Make a screenname and one of our amazing Devs will help you though the crisis. Been there, and you'll love them for it.
When I was a newbie in xda, I made sure to research thoroughly before blindly doing weird kinky stuff to my phone.
The xda wiki was one place that helped me in my dark noobish times.
Do yourself a favor and read up the wiki, you might find your answer there.
http://forum.xda-developers.com/wiki/index.php?title=File:Nexus_One.png
get yourself the android SDK, run a cmd window, while your phone is bootlooping;
type adb remount
you should get a message "remount successful"
now type; adb shell rm /system/app/NetworkLocation.apk
and also; adb shell rm /system/app/OneTimeInitializer.apk
your phone should now boot normally
thanks
I.ll try it when i come back from work
But it isn't bootlooping persay...I get the cyan guy and the cm7 logo screen (the arrow turns for awhile...then I get the Green Android guy and it says click to start...I can't even click ...the blue cyan screen starts ...then the green guy ...this loops for ever.
In bootloader mode ( power+trackball) when I try to recover...the the google X logo appears the phone shakes then black screen....nothing happens.
I think that either clockwork recovery is broken (because I saved 3 back-ups from rom manager)...or it works but I cant see screen (SLCD)...Anyway, is there a way to just flash en existing image on my sd card.....
Also my phone was soft rooted (androot) I don't have the big unlocked under the x...will this prevent me from using fast boot to flash???
Thanks guys I know I'm a newbie...Ive read alot...I'm sorry if I offend some of you guys...Thanks for the help....
Sounds like your bootloader is still locked... in that case, fastboot will not work for your phone.
Still read the section on flashing recovery in the xda wiki. There's a section on how to flash a recovery without fastboot but adb.
adB
Ok isn't ADB a driver for usb ...
Anyone know a step by step for morons ( like me)
That have a locked phone, a corrupted bootloader ( or recovery not working) and modified roms on the sd card...
Can i just erase the sd ( put stock image on it)
I will try this at 2pm I must go to work....thanks for the help
Yes.
Download: http://shipped-roms.com/shipped/Pas...le_WWE_2.16.1700.1_FRG33_MFG_Shipment_ROM.zip
Unzip it, and rename the extracted file passimg.zip
Place it on the root of your SD card and power the phone on holding Vol-
It will find the file and ask if you want to install, pick yes.
Ok
Ok heres what I did so far:
I used an empty sd card ( formated it and put followed what you said: put renamed image oanto sd card)
I power with the volume, here is what happens:
I click on bootloader
I get : recovery option , click the X comes back on shaked and then I get a black screen
Ive waited for 10 minutes nothing
Also: when I click on boot loader, I see ( in green) it saying wrong image, wrong something else.....
Can someone telle what I did wrong
Thanks
Did you extract the zip from within the zip, as instructed?
Sent from my Nexus One using XDA App
ok heres something else I tried:
Went to the original sd card with everything on it) went to the clockwork folder) went to an old back up folder ( copy pasted everything onto the empty sd card) put the sd card into the phone , press power + volume - , get the green guys with skateboards , click onto boot loader ( see the same errors that roll down quickly, funny why they fly down so fast...but I think it says bad image or wrong image or time ) . Anyway, still same thing when I press recover ( with power button) the X shows up , the phones vibrates and then the black screen.
I i do a normal power on ....still get the CM7 boot guy , the arrow that turns around him a few times , then the green guy that ask you to click on him, then you can't even click on him...the CM7 boot guy starts all over (this loops til infinity)
Just so you guys know, the phone was rooted with androot...so I don't know it its still rooted since the software dowsn't work....
Any ideas guys...thanks...
I will try the adb method late tonight...but Im not sure its works if the phone is soft rooted...
Thanks
Did you really rename the passimg.zip correctly? The bootloader should automatically detect the file and prompt you if u want to update. If it did not detect it, it could be the wrong file u renamed.
Remember that once you boot into bootloader using the vol down button, you have to wait for it to detect the passimg.zip before doing anything else.
And fastboot will not work on your phone. You need the roundabout method to flash recovery using cmd.
Ok heres what I did:
1-I download the link Rusty! supplied
2-I extract using winrar to the empty sd card ( a 2 gig card that has been formated using windows format tool to fat 32)..not the one that came with the phone)
3-Once the file in on the sd card, I rename is ( copy paste) exactly passimg.zip
4-I ask windows to eject
5-I insert the card
6-I press the power and volume down
7-I wait , so that fastboot is read.
8-I select fastboot wait a few seconds , select Fastboot ( is green letters) with the power button, it changes to bootloader( green letters), I see green text roll down( says ' i try to see, wrong....something)
9- nothing happens
10-I click recovery, the phone vibrates, get the X, phone goes black
****I tried reading that roll down message : wrong image is there with some other stuff
These are the steps...nothing
Thanks for the help
More info (when I boot in skateboard mode):
nexusone PVT SHIP S-ON
HBOOT-0.35.0017
MICROP-0c15
TOUCH PANEL-SYNT0103
my radio is : 5.12.00.08
June 14 2010,12:02:27
HBOOT
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
Its also a videotron phone....I did modify the radio from original stock
Dunno if this can help
Thanks
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.