Database Users

[Q] Tattoo Bricked

Hello,
I tried to update the radio and the SPL version on my Tattoo. Everything went fine until I had to reboot my phone. It shut down alright, but it never powered on again.
These are the following problems I am having with my Tattoo at the moment:
Cannot power on phone.
Cannot boot into recovery mode.
Cannot boot into FastBoot.
When I connect it to my computer via USB, nothing happens.
The only thing that it's responding to is when I connect my it to my charger.
Does anyone have a solution or is my phone dead forever?
Thanks ahead!

bump? anyone?

Send it back to HTC. If anyone can do anything about it they can. There's nothing else you can do. Sorry

boo.. that sucks..
Well, thanks anyway

Ehm, I don't want to post a New Thread so I'm gonna ask here:
Does anyone have the pinout for the Tattoo?

Take a look at this. I guess they fix such things (but you never know if they just are after your money. http://www.ort-jtag.com/index.php

Yeah I saw that already. Also, there is a file name Tattoo Jtag on their website in the Support section. However, to access that section you have to enter your products serial number (which is I'm guessing the phone's serial number). I have tried several serial numbers (including mine) and all of them were 'invalid' so I never checked the files out.
Also, they only have one thing in the shop which is a kit and it costs $330 so no thanks

I have a similar problem, I would like to share my knowledge although I must be completely out of way.
My experience is based on the BeagleBoard and Angstrom so I really don't know the HTC HW and Android at all...
- The device boots from an xloader that instructs the device how to proceed with the boot
- the bootloader takes place (great u-boot in the beagleboard ?? in the HTC phone) the bootloader allows for ROM or kernel+rootfs flashing and much more
- now the kernel is loaded.....
User mode applications do not allow to have access to the memory area where xloader and u-boot lie so they should be safe all the time to allow for device reflashing.
So we should have access to the device via bootloader anytime if we knew how... maybe somebody can help us further.
Fabio

Same here...Exact same issue...No Recovery mode...No USB Connectivity, Screen turns on but is blank, alhough I did see Tattoo popping up initially but not any more...All I can see is the LCD back light turns on...Battery does charge...Also when I try to enter Recovery mode screen keeps blinking as if it is trying to restart again and again...Someone help

similar problem here, but i get absolutely no response from the phone, it doesn't even recognize the charger. do i just throw it away and buy a decent one or is there a solution?

Sparky the only way for now to fix that click is to bring it to some service point that have that ort jtag, because only way to fix that is to writte new boot sector on phone . Im sure that i know at least 2 services that have ort jtag in Novi Sad . Look for marvel *Miroslav in Ns, or send me private message

same thing happened to me
just this morning, and in desperation I tried hard to remove the batt cover (prob pressed some of buttons, I felt a jerk and ho it was back in amon ra`s recovery, nect time I just removed the battery waited for 30 secs, then press off&home and hold it till recovery came back) but for good half hour NO REACTIONS , ABSOLUTE BRICK, nothing when I put the usb in PC or in socket, dead screen, no sounds and no reaction to ANY combination of keypress. I guess you could call me lucky (in last few days I flashed at least 3 versions of froyo roms, this afternoon I bought =8GB class4 Kingston, formated it in PC FAT32 default size, copied EVE. from my 2gig rom then just turned it down (yes I am brave) and put the 8gig in tattoo, it works like a charm (finger crossed it will continue)

So is there an available Jtag for the Tattoo yet?

I'm in the same situation. No recovery no fast boot, Damm!
I`ve update psfreedom with psgroove_hermes_v4 zip file then my tattoo reboot and now I only get the Tatto title screen but nothing happends.
Somebody have clue to give back life my phone.
Thanks!

if you can get to the title screen, that means you can connect it to your pc via USB and recover from a backup (I hope you made one)

Hello, I connect my tattoo to my pc, but usb connection is not available yet.
Is There is a way to activate usb when my phone blocks in tattoo logo??
Thanks for reply.

payasi35 said:
Hello, I connect my tattoo to my pc, but usb connection is not available yet.
Is There is a way to activate usb when my phone blocks in tattoo logo??
Thanks for reply.
Click to expand...
Click to collapse
You have to enter in fastboot.
Hold volume down and turn on phone.
Cheers

Sorry but as i said before, I can't access to recovery menu neither fast boot menu.

[Q] A little bit stuck, need ideas.

Turned my phone off and back on a couple of days ago and now the phone boot loops after showing the telstra logo.
I have Hboot and fastboot access but no recovery. (does the same thing, just boot loops), even though I had clockworkmod installed. It's as if everything just wiped itself.
My hboot is version 0.80.0008 and it says S-ON.
What could I do from here to revive my phone? Would a gold card be the only way?
I have created some other posts but none had been replied to, any help would be greatly appreciated.
Maxcima.

i've had one bootloop before, which was solved by removing sd card and booting up then replacing, hope it helps.

ephbee said:
i've had one bootloop before, which was solved by removing sd card and booting up then replacing, hope it helps.
Click to expand...
Click to collapse
Thanks for the suggestion but I've already tried booting without the SD card in with no success. It's quite frustrating because I was only playing music before I turned it off.
Any other suggestions? Anyone?

which rom are you using?
my h-boot is 0.80.0004 s on.
was there anything new loaded on phone prior to your bootloop problem?
i had another issue after loading some new tunes on sd card, even though they were fine on pc, they made my phone schitz out, kept on rebooting and made sd card read only, i know its a longshot but i'm trying to think of anything i can

I'm using SUnAaBh v1.1 which is quite ironic because it was renowned to be one of the most reliable and stable roms out there haha.
I did get fruit ninja but it had been a while since I reset it so I don't know for sure what it could be since I've put various things on, but none that I could think of that would potentially force a boot loop.
I do really appreciate your help. It provides some hope until I can get my hands on a gold card
Is there any other way that you know of to flash it while it is in the current state?

have you tried rooting using unrevoked again and installing clockworkmod?

What mode would I have to be in for unrevoked to recognise my phone?
As I cannot boot into the phone, USB debugging is a no go. Does unrevoked recognise a device in fastboot or something similar?
Thanks.

Boot into Clockmod Recovery and then try to clear cache & DALVIK cache. Then boot again and wait some Minutes.
Maxcima said:
Turned my phone off and back on a couple of days ago and now the phone boot loops after showing the telstra logo.
I have Hboot and fastboot access but no recovery. (does the same thing, just boot loops), even though I had clockworkmod installed. It's as if everything just wiped itself.
My hboot is version 0.80.0008 and it says S-ON.
What could I do from here to revive my phone? Would a gold card be the only way?
I have created some other posts but none had been replied to, any help would be greatly appreciated.
Maxcima.
Click to expand...
Click to collapse
Sent from my HTC Wildfire using XDA App

Deep-Knight said:
Boot into Clockmod Recovery and then try to clear cache & DALVIK cache. Then boot again and wait some Minutes.
Sent from my HTC Wildfire using XDA App
Click to expand...
Click to collapse
Hi Deep-Knight. That would have been my first option but as I stated, for some reason selecting recovery from HBOOT just makes the device loop boot after the telstra logo again, it doesn't boot into clockworkmod recovery anymore.
I don't understand why.
Thanks

Maxcima said:
What mode would I have to be in for unrevoked to recognise my phone?
As I cannot boot into the phone, USB debugging is a no go. Does unrevoked recognise a device in fastboot or something similar?
Thanks.
Click to expand...
Click to collapse
was your phone already with usb debugging enabled before this bootloop? if it was already enabled, unrevoked will work fine.
(i always keep it enabled)

Hmm, originally when I used unrevoked I would have had it enabled (obviously) but since then I've flashed other roms using clockworkmod. So everytime you flash a new rom, it gets rid of USB debugging unless you enable it again correct?
Therefore I don't think USB debugging is enabled on mine. Ahh, it's so annoying.
I have it on HBOOT and plugged into my pc but Unrevoked isn't picking it up, I assume it's because I don't have USB debugging enabled, or am I wrong?
Thanks guys, really appreciate it!

it shouldn't change usb debugging, all the roms i have flashed its still there after being turned on once. check your messages too, sent you some info on telstra

Oh okay, I still have no luck with unrevoked though. Tried it on a different PC with the HBOOT modified drivers. Just stuck on "Waiting for device..."
ADB commands also do NOT work, so I am lead to believe that usb debugging is NOT enabled?
Please correct me if I'm wrong.
Thanks.
EDIT: NEVER MIND, I got it working! I found a recovery zip (PC49IMG.zip) and renamed the cyanogenmod as update.zip, put them both on my SD card and booted into recovery!
Clockwork stated there wasnt enough room on E: (whatever drive that is) so I flashed all data and installed cyanogenmod.
Thanks heaps everyone, means a lot to me
PS - I dont know why clockwork mod decided to boot this time but it did. Maybe because it had to room, it couldnt boot? I don't know, I'm not that experienced with these things.

good to hear mate, now go and get some credit from telstra

Bootloop

Hi
I have an HTC Legend, but it's so buged
When i try to turn it on, it has to be connected to a cable, or else it goes into bootloop.
I've tried to make a factory reset, tried to install a different RUU, tried to downgrade it, but the adb shows no devices.
I've run out of ideas, so please help me

Somehow I managed to get the same issue. It goes into bootloop unless it's connected to a pc... I already went back to the stock 2.2 rom and deleted everything but nothing changed.
Funny thing is that after I got this problem I first installed the old 1.31 rom and that one worked without the usb cable. The 2.05 to. But as soon as I installed the 3.14 it started again with the bootloop thing...
Did you find any solutions?

Ok, after installing the stock rom I noticed that the usb is not working so I just needed to unbrick the phone and that solved a problem.
(I just did not think about that before because usb was still working when I installed cm7 but the bootloop problem was already there.)

CrWEE said:
Ok, after installing the stock rom I noticed that the usb is not working so I just needed to unbrick the phone and that solved a problem.
(I just did not think about that before because usb was still working when I installed cm7 but the bootloop problem was already there.)
Click to expand...
Click to collapse
What exactly means unbricking the phone?
I got simillar problems: since CM7 final I have bootloops when my phone isn't connected to power. Also I can't mount the sd card from a computer (when I press the button on the phone it works for like 5seconds and then unmounts again).
I already tried downgrading again to CM7 RC4 and other versions(I always wiped before), but the problem persists. Also upgrading to another radio version didn't work .

virus54 said:
I have this problem too
but i found one way to stop this rebot loop util u reboot your phone again...
enter into recovery mode and via adb write the command
adb devices
Click to expand...
Click to collapse
now press volume up and power button(when you see black screen with phone)
press on reboot system now and it will work for you for one time
each reboot you have to follow those steps
Click to expand...
Click to collapse
after this do a usb brick to use your usb http://android.modaco.com/content/h...com/309961/usb-brick-rickrolled-b0rked-fixed/

I had exactly the same problem, the USB unbrick linked to above solved the problem. If you need the image hex edited for you give me a shout

Desire Z bricked

So I've now got a bricked Desire Z and have had to go back to my reliable and fairly beaten up old G1 again.
The ROM it was running was Virtuous Unity 2.39.0 with a particular kernal that allowed me to record phone calls.
What was I attempting before it became a massive paperweight? A ROM backup via ClockworkMod Touch.
What does it do now? Absolutely nothing! When I plug it into an AC charger or the USB cable it gives absolutely no sign of life, trying a different battery makes no difference as the two I've tried, work in a dusty old faulty Desire Z.
I can no longer reach the bootloader.
Any ideas would be appreciated.

Plug it in with the phone off and turn the phone on while holding the volume down button it will go into fastboot mode.
From there you will have fastboot access and select recovery if it does not work then flash a new recovery by doing the following
1) Download the correct clockwork mod recovery image (should be something like recovery.img) I believe there is one on the first page of the development section which supports touch.
2) while on fastboot (first sentence of this post), type the following
fastboot flash recovery c:\recovery.img
where recovery.img is the location of your recovery, you will need to be inside of the android sdk tools directory where adb and fastboot commands are located.

A_Elizondo said:
Plug it in with the phone off and turn the phone on while holding the volume down button it will go into fastboot mode.
Click to expand...
Click to collapse
There's a massive problem with your solution. It won't turn on AT ALL thus making said solution useless.
When plugged into either an AC adapter or a USB cable connected to the PC it gives zero sign of life.
As useless as the solution itself was in this instance, I've never actually used ADB to flash a recovery image before so it was still a little helpful.
Any other ideas?

Bricked - sounds like it may be only revived by flashing it via JTAG hardware interface. See if you find one around that is capable of this..
Mike

MIkeRD03 said:
Bricked - sounds like it may be only revived by flashing it via JTAG hardware interface. See if you find one around that is capable of this..
Mike
Click to expand...
Click to collapse
I'll leave the JTAG flashing up to the boys and girls at HTC since I'm not confident enough with a solder gun to attack it myself, even if no solder gun is necessary I still may have difficulty remembering what screws went where whilst re-assembling it.

Nexus 7 2012 hard bricked (can't boot)

I don't know where to start with my problem.
Firstly my Nexus 7, 2012 , 5.1.1 android , nakasi- grouper version tablet was very slow. Tried all the known recovery mode options etc. but nothing really changed. So I decided to Root it .
In order to root it properly I download the wugfresh root toolkit. I knew that my USB port was quite unstable but I thought I could risk it, since I didn't have anything serious in there, and at the end of the day I was trying a clean re-installation.
Before doing anything I decided to flash the stock rom and unroot it (since I didn't know if the device was at a correct- clean factory state.... Just for the sake of it) Unfortunatelly I might also have chosen the 2013 version because I didn't really know the differences)...
Everything went well, up to the point that a cmd said that there was no device and stuck there. It was in the bootloader mode and couldn't move. I disconnected the device from the USB, pressed hard and for more than 30 secs the power button, it switched off. Then I pressed hard the power button for a long time (and after that many more times) but it never came back to life.
I tried to press any combination of buttons many times. Disconnected the battery. Actually measured it for voltage and current (everything's fine). Charged it in an alternative way. Reconnected it (several times). To no result. Dead device. I can call it hard-bricked, but to me, it's more like dead.
Any idea what went wrong and if there's any chance for this tablet to come back to life? Is it worth it? No serious data in there. Haven't backed up anything related to it.
Thanks in advance.

Take the back off of thr device and carefully disconnect the battery. Wait 5 minutes, then plug battery back in and replace the back.
If you can get a pogo cable you can charge without using the USB. Either way, kust let it charge for a few hours, then try to power up.
The Root Kit has a recover from boot loop option you should use. It will download the last official rom and flash it unrooting your system. Just make sure you choose the right model of nexus when you start.
Good luck
Sent from my LGLS992 using Tapatalk

psiphi said:
Take the back off of thr device and carefully disconnect the battery. Wait 5 minutes, then plug battery back in and replace the back.
If you can get a pogo cable you can charge without using the USB. Either way, kust let it charge for a few hours, then try to power up.
The Root Kit has a recover from boot loop option you should use. It will download the last official rom and flash it unrooting your system. Just make sure you choose the right model of nexus when you start.
Good luck
Sent from my LGLS992 using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply.
No chance with solution number one.
As I said I 've left it charge for more than 10 hours. Measured the battery's poles.
Around4 volts, 2.7 amps. Everything's fine with the battery.
The tab won't boot at all. Can't enter bootloader, can't be recognised by the USB, can't use the Root Kit.

tedsorvino said:
I don't know where to start with my problem.
Firstly my Nexus 7, 2012 , 5.1.1 android , nakasi- grouper version tablet was very slow. Tried all the known recovery mode options etc. but nothing really changed. So I decided to Root it .
In order to root it properly I download the wugfresh root toolkit. I knew that my USB port was quite unstable but I thought I could risk it, since I didn't have anything serious in there, and at the end of the day I was trying a clean re-installation.
Before doing anything I decided to flash the stock rom and unroot it (since I didn't know if the device was at a correct- clean factory state.... Just for the sake of it) Unfortunatelly I might also have chosen the 2013 version because I didn't really know the differences)...
Everything went well, up to the point that a cmd said that there was no device and stuck there. It was in the bootloader mode and couldn't move. I disconnected the device from the USB, pressed hard and for more than 30 secs the power button, it switched off. Then I pressed hard the power button for a long time (and after that many more times) but it never came back to life.
I tried to press any combination of buttons many times. Disconnected the battery. Actually measured it for voltage and current (everything's fine). Charged it in an alternative way. Reconnected it (several times). To no result. Dead device. I can call it hard-bricked, but to me, it's more like dead.
Any idea what went wrong and if there's any chance for this tablet to come back to life? Is it worth it? No serious data in there. Haven't backed up anything related to it.
Thanks in advance.
Click to expand...
Click to collapse
Hi, tedsorvino...
I hate to be the bearer of bad news, but I suspect your Nexus 7's bootloader has become corrupted (possibly due to a faulty USB connection during your wugfresh reflash), or overwritten with an incompatible bootloader for your specific device type, vis-a-vis your reference to flashing the wrong ROM.
Either way, without a valid bootloader, your Nexus 7 will likely never boot again.
Or at least, not without a motherboard replacement, which is probably not worth the hassle or the cost for such an old device.
Flashing the bootloader (either on its own or as part of a full device reflash) was always one of the most risky aspects of reflashing the Nexus 7; it required a healthy battery charge and a solid, stable USB cable connection. It was something I approached with trepidation on my old Nexus 7, and if at all possible, it was something I tried to avoid.
The bootloader is a device critical component for booting the device and also for reflashing it with fastboot commands, because it's the bootloader that accepts and handles those fastboot commands, either directly via a Window's command prompt or with something like Wugresh's toolkit.
And when it gets corrupted or overwritten with something other than a valid bootloader image file, the Nexus 7 is hardbricked, and the only solution is a motherboard replacement.
Ged.

GedBlake said:
Hi, tedsorvino...
I hate to be the bearer of bad news, but I suspect your Nexus 7's bootloader has become corrupted (possibly due to a faulty USB connection during your wugfresh reflash), or overwritten with an incompatible bootloader for your specific device type, vis-a-vis your reference to flashing the wrong ROM.
Either way, without a valid bootloader, your Nexus 7 will likely never boot again.
Or at least, not without a motherboard replacement, which is probably not worth the hassle or the cost for such an old device.
Flashing the bootloader (either on its own or as part of a full device reflash) was always one of the most risky aspects of reflashing the Nexus 7; it required a healthy battery charge and a solid, stable USB cable connection. It was something I approached with trepidation on my old Nexus 7, and if at all possible, it was something I tried to avoid.
The bootloader is a device critical component for booting the device and also for reflashing it with fastboot commands, because it's the bootloader that accepts and handles those fastboot commands, either directly via a Window's command prompt or with something like Wugresh's toolkit.
And when it gets corrupted or overwritten with something other than a valid bootloader image file, the Nexus 7 is hardbricked, and the only solution is a motherboard replacement.
Ged.
Click to expand...
Click to collapse
Thank you. Even if the news are bad, it's a really valuable piece of information. At least now I know.