Database Users

Root gone wrong

rooted phone. went well Installed rom
not so well.
Holding home and power brings me to a "Android System recovery Utility"
I think what i did wrong was i installed two different types of roms on to my G1 unwittingly. So now all that happens is it stays on the G1 screen and doesn't change. Left it charging overnight and stayed on that screen
Is there a way to access and rectify via console option.
Please help

If you have recovery, you should be fine. Just flash your favorite image and wipe your userdata.

DOD1 said:
rooted phone. went well Installed rom
not so well.
Holding home and power brings me to a "Android System recovery Utility"
I think what i did wrong was i installed two different types of roms on to my G1 unwittingly. So now all that happens is it stays on the G1 screen and doesn't change. Left it charging overnight and stayed on that screen
Is there a way to access and rectify via console option.
Please help
Click to expand...
Click to collapse
Holding Home + Power is supposed to take you into the recovery image.
At the bottom of your recovery image does it say Amon Ra 1.5.2 or 1.6.2 or something like that?

If your phones rooted then just wipe and reinstall you rom.
Like lets say your doing the new cyanmod
you apply zip
DR83
With out rebooting apply zip
Cyanmod-rom 1.4xxxx
If it boots back into Android System recovery Utility just hold home and back again.
Give it time to write its radio and its first time rebooting it says on the boot screen for a awhile some longer then others.
This site has always helped me its better to see the instructions rather then read them.
http://www.google.com/search?q=the+...s=org.mozilla:en-US:official&client=firefox-a

unbricking issue?

I tried to finally root my phone and install CM5.0.8. The rooting went fine, but getting CM to work, well it didn't. After repeated attempts, I decided to follow the instructions to get my phone back to stock so that I had a functional phone.
The result is that when powering on, it goes to the bootloader in less than a second. I have followed the instructions for downgrading/unbricking repeatedly, and it keeps booting to the bootloader. I have even tried to manually update to r33 and it seems to go fine, reboots a couple of times installing a new radio image I assume, but goes right back to the bootloader afterwards. The times I've tried the r33 update, when its all said and done, the bootloader reports the original radio version even though a new one is supposedly installed. Its like the installs goes fine, but nothing sticks.
I can still get to the bootloader(obviously) and recovery, so I know there's hope for my phone. Does anyone know whats going on and how to fix it?
EDIT: It seems that the radio image is changing, but its still booting straight to the bootloader. In case its not clear, DREAIMG.nbh flashing says that its successful every time and its still doing this.

Anyone?
I've now tried DREAIMG.nbh files from multiple places, every time they say that they're successful and yet it still boots to the bootloader. I'm almost at my wits end with this.

Your description is inaccurate.
You say that it is going to bootloader, but you are also saying that you can access recovery....
What RADIO is installed on it *right now*?
What SPL is installed on it *right now*?
What RECOVERY is installed on it *right now*?
Do you have ROOT?
HOW did you try to install CM?
At what point did it start booting straight to bootloader?
Note: boot to bootloader means one of two things;
1) The boot image it is trying to boot is somehow invalid,
2) The BACK or CAMERA button is broken or stuck (try pressing these buttons a few times to see if that fixes it).
DO NOT install 1.33.2005 SPL. It is REDUNDANT, and judging by the things you say you've done, I suspect that it will be EXTREMELY DANGEROUS for you.
This thread to install CM5 withOUT needing the deathSPL: http://forum.xda-developers.com/showthread.php?t=704560

You say that it is going to bootloader, but you are also saying that you can access recovery....
Click to expand...
Click to collapse
Correct. Just hitting power, I get the G1 logo screen for about a second and then the boot loader. If I start it while holding down home, it goes to the recovery mode. Camera + Power, bootloader checking for firmware on SD card. The other combinations you can use booting up also work as intended.
Radio - 1.22.12.29
SPL - 0.95.0000
Recovery - Stock that is installed by DREAIMG.nbh.4 options, reboot, toggle text, apply update.zip, and wipe data/factory reset
Root - not anymore
HOW did you try to install CM?
Click to expand...
Click to collapse
I followed the instructions on CM's wiki for starting from a vanilla G1, and then followed the instructions for DangerSPL and CM 5.0.8 that are linked from that page.
At what point did it start booting straight to bootloader?
Click to expand...
Click to collapse
After following the instructions to get the phone back to stock.
Note: boot to bootloader means one of two things;
1) The boot image it is trying to boot is somehow invalid,
2) The BACK or CAMERA button is broken or stuck (try pressing these buttons a few times to see if that fixes it).
Click to expand...
Click to collapse
I don't think that its #2, the buttons work since I can use them to boot into different modes, and I've pressed the buttons repeatedly trying to see if they're stuck. It seems that its #1, even though every time I try to flash the firmware, it says that its successful.

G1 Reverted to RC29 stuck at "Android system recovery utility"

I have a (formerly) rooted G1 that I've attempted to revert to stock RC29 by following the "Full Downgrade Guide" at the CyanogenMod wiki.
My device had HBOOT-1.33.2005, so I used the suggested fastboot command to roll it back to HBOOT-1.33.2003 from the g1boot.zip file linked on that page. This seemed to go well, after which I rebooted into the fastboot (which was still the skateboarding androids screen) again and saw the new (old) HBOOT in the information.
Powered off the phone, inserted the SD card loaded with the DREAIMG.nbh linked in the page, and reflashed the phone. Rebooted with Send+Menu+End, and the phone kept rebooting at the T-Mobile G1 logo screen.
So, I attempted the flash again from the bootloader menu, which is now the "rainbow" style, and shows HBOOT-0.95.(something). It immediately picked up the DREAIMG.nbh file on the SD card and asked if I wanted to flash, chose yes. Same result again: a boot loop at the G1 logo.
I redownloaded the DREAIMG.nbh file without the download accelerator I'd used before, placed it on the SD card, and booted into the bootloader again, flashed, and still the same looping.
So, I attempted to access the "recovery mode" by pressing and holding menu while powering on. I got the G1 logo, then a black screen... pressing Alt-L showed "Android system recovery utility", and nothing else.
Now, the phone will do nothing BUT Android system recovery utility, regardless of what buttons I press or do not press, and I have to remove the battery to turn the damn thing off. Pressing Alt-S, Alt-W, Alt-X, or anything else does nothing.
Where should I look to try to figure out how to recover this thing?

Is a simcard in the phone? Can you get into recovery and wipe incase the partitions are confused?
(Edit, the hint was the sim card)

There's no SIM in the phone at the moment. I can't do anything at the system recovery, except turn the log on or off with Alt-L (which I guess means it's not frozen).
It isn't recognized by ADB anymore, since it has some bastardized version of the stock T-Mobile image that has USB turned off (right? I'm new at this. ).

A bit more info:
I can get into "blue light" mode, and the light is amber/green when plugged into a charger. Sometimes, when I plug the charger in the phone will turn on immediately; but not always.
When I start the phone up and it boots into the broken recovery console, Windows does see an "HTC Dream" device, but ADB doesn't see it.

ezterry said:
(Edit, the hint was the sim card)
Click to expand...
Click to collapse
Should I, or should I not have the SIM in? For what its worth, the phone behaves exactly the same either way.
Thanks for the help.

I just had this exact experience; have you made any progress, goatlordbob?

same happened to me.
cant fastboot, loop at G1 screen, and all i can see in recovery is: Android system recovery utility
some1 find some solution?

why doesnt there seem to b any help for this matter, smh

bull.. s**t
I'm in the exact same boat now. I followed those directions *to the letter* and it put my G1 in this state. Thanks to the wiki maintainer for such wonderful attention to detail. /s
Is there NO way to recover from this?

try to flash this nbh file.... http://www.4shared.com/file/9izdCbvo/DREAIMG.html

ldrifta said:
try to flash this nbh file.... http://www.4shared.com/file/9izdCbvo/DREAIMG.html
Click to expand...
Click to collapse
How? None of the key commands work. Like the OP I can hit Alt+L and it shows ""Android system recovery utility" but that's as far as it goes.

Anyone bothered booting using home + power?

shadowch31 said:
Anyone bothered booting using home + power?
Click to expand...
Click to collapse
Yes - T-Mobile G1 logo, then blank screen forever.

[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.

HTC Tattoo bricked? Doesn't boot, goes to fastboot...

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.