Okay, so to start off, my G1 was rooted RC33 with JF 1.42. Being a complete idiot, I left my G1 in my pocket and did the laundry.
Since that incident, my g1 was stuck at the G1/tmobile logo. I tried getting a new G1 but I didn't know they had a water sensor .
I did the multitouch hack so when I hold home + power, it shows lines of code and eventually to JF's recovery screen.
Any help?
Edit: Oh I also tried flashing my phone with different things several times but it says "Finding update package, opening update package, Can't open /sdcard/update.zip (bad), installation aborted. EVERY TIME!!
Factory reset isnt working either. OH! Okay, So factory reset does work but I can't tell since it's forever stuck at the G1 screen.
Idc if i lose my apps, i just want my G1 back. I'm willing to lose everything on my G1.
I tried making the update folder an actual zip and tried just renaming it. neither worked.
I think you might be a little off on the way you are doing the flashing. You are supposed to leave it zipped and just rename it to update. Do not unzip it by any means, just rename it update and transfer it to your sd card. Boot up into recovery by holding home + power, once in recovery press and hold alt and press W then press and hold alt and press S. Good luck.
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
I'm seeing some weird problems after rooting my phone. I just got a replacement Droid X after my last one's screen went bad. The replacement came with 2.2 installed.
I downloaded the `TDFOneClickRoot`, which uses the 'rageagainstthecage' explot. After rooting, I installed all the apps I had on my old phone. All the apps were installed via the marketplace. I also remounted /system as r/w and copped two sound files over (one to /system/media/audio/ringtones and one to /system/media/audio/ notifications). Then I rebooted and started having my problems.
- If I reboot normally, I get the moto logo, I hear the 'droid' sound and then it will sit there. It will replay the notification sound every so often, but it doesn't reboot.
- If I hold down the 'search' key, hold down power until the moto logo shows, and then release power the device will boot normally.
I'm worried about trying the different recovery methods described in the forums, because most of them talk about different scenarios than this one. Does anyone have thoughts?
EDIT: I've tried getting into the recovery menu without success.
I'm going to try putting custom ringtones in my /system/media/audio/notifications folder and let you know if it hoses my system. I'm suspect of that being your issue.
I'm making a nandroid right now and will let you know in a few minutes.
EDIT: I used ADB to stop my interface, copy the file to my /system/media/audio/notifications folder, then rebooted. Worked without a hitch. You might try a factory reset and go from there.
Thanks for the advice. I went ahead and did a factory reset from the settings/privacy menu. Unfortunately, I seem to have the same problem even after the reset.
What's the best way to do a factory reset? I've read a bit about the SBF, but I'm not sure if that's the right path. Before this, I had a Droid Eris, that was very easy to reflash. I'm worried that this is more complicated and easier to mess up.
If nothing seems to work a SBF would be your best bet. But do be careful though as if you are on 2.1 DO NOT flash the OTA 2.2 SBF, you will be bricked. Search around Google for the SBF file.
OK, so I want to do the SBF, but I want to make sure I'm using the right one.
Here's the package I downloaded:
rootzwiki.com/index.php/Main-Page/Droid-X-Full-2.2-SBF.html
VRZ_MB810_2.3.15_1FF_01.sbf is the SBF file. From what I can tell the procedure seems straight forward:
- hold down vol- and camera, then power up
- connect via usb
- run rsd lite
The drivers are installed, and the phone does show up on rsd
Code:
IMEI/ESN/MEID: N / A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: v0x003003
DRM Version: N / A
AP Die ID: <<number>>
BP Die ID: <<number>>
AP Public ID: <<number>>
BP Public ID: <<number>>
Is it normal that many of the fields return 'N/A'?
Just make sure you open up RSDLite 4.8 Go to Config>Device ID Options>Check the Box that says "First-Come-First-Serve Device ID Mode"
Then go ahead and click start and just wait it out.
I've gone ahead and done that. Now that I've done the SBF, all is back to normal.
Thanks!
Anytime! Have fun
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.