Related
whilst attempting to unroot my phone via ruu the other day i hit a brick wall
on a fully charged battery, the process halted and gave me an error 120 (main battery low) the phone rebooted and now all i am left with is 2 screens- one is with a black screen that says htc and has triangles with exclamation points in corners (usb cable connected), the other is a white screen that looks like a fastboot screen but only says ruu and it is unselectable.
I have tried to ruu again, always get battery power error ( have tried several different batteries)
I have installed and unistalled htc sync, removed and reinstalled drivers
i have tried to boot into recovery with power and vol down ( does not work, brings to black htc screen)
tried my best with adb, but cant get it to "see" the phone
(funny enough if i connect it to my laptop pda net sees the phone and tries to connect but cannot)
Ive scoured this forum for solutions, and tried as many as i found all to no avail
I ask you, is my phone bricked? or is there hope still?
i was running koni elite rom,
my hboot is 2.10.0001
Try uninstalling pdanet and anything else that might try to connect to the phone automatically that you don't need for unrooting, like HTC Sync. It could be interrupting the connection somehow. I know that you're getting a low battery error, but it's worth trying.
Even though you cannot get into hboot, try putting a PC36IMG of the RUU on your SD card. Perhaps it'll detect it from the kindasortafastboot screen.
I don't know that either of these things will help, but it's all I've got.
Sent from my Evo + MIUI using Tapatalk!
I truly don't understand why people try to unroot their phones....
have to return phone to sprint, it is still under warranty.
falconlb45 said:
have to return phone to sprint, it is still under warranty.
Click to expand...
Click to collapse
So flash a stock ROM, remove any apps, including SU, and take it back. Is still have yet to see that they busted anyone with S-Off on Hboot. And the good news is, they refurbish it and send out already rooted to someone else.
Can you get into HBOOT after a battery pull and replace without connecting your phone to your computer? If so, you are likely not bricked.
Sent from my PC36100 using XDA Premium App
Hi there,
I had a very nice trip with my rooted desire with a miui rom on it for now maybe, 1 year smthg.
Recently, i bought a new µSD and wanted to prepare it for my phone ; i downloaded rom manager, and tried the "partition SD" functionality, which told me that i would have to update my clockworkmod, which i tried with the "update recovery" in it, which failed.
After a while, i found that i forgot to S-OFF my phone, and that was the reason why i couldn't update the recovery. So i decided to S-OFF. Unfortunately, my phone didn't went to the last step, and stayed stuck at the boot screen until its battery died, maybe an hour after.
I began a long journey trying to figure out if my phone was bricked or not, since i wasn't able to boot it up ; only the hboot was responding. I tried MANY ways, MANY posts, i tried to flash with a nand backup without success ('access denied'), i tried to flash just the recovery (same or 'signature failed'). I tried to put a PB99IMG.zip file from alpharev into my phone without any success...
BUT. I succeed in recovering my phone with putting a stock PB99IMG.zip from shipped-roms and it boots up very well on a crappy sense rom.
From that, i tried hard to root it again since i want to try again to S-OFF it, and after that, return back to my beloved miui rom. I'm stuck because of a mysterious problem into my phone. It looks like it doesn't like the third step which (i guess) requires a boot script. So nothing happens to it, it freezes to the bootscreen, while unrevoked says "waiting for reboot..." endlessly.
I succeeded once (only) in passing this step, but then unrevoked said to me something like : "Internal error: failed to unlock NAND flash?" which seems crazy since i'm in a 0.93 HBOOT (since the RUU reset). I hadn't any Superuser app nor signs of rooting ("su" command failed in terminal).
For now, i'm trying to root it via the Visionary app, but i don't think it will work.
If anyone has any suggestion in making things better, i'll be pleased to hear !
PS : I'm writing this post because i feel it could be full of useful infos for anyone else stuck with a "bricked" phone.
use this guide to S-OFF, install custom recovery and root.
read all the instructions, several times.
oh and rom manager is often not recommended for this phone as it can often cause usb bricks. once s-off you can flash different recoveries via fastboot or android flasher.
use gparted or 4EXT recovery to partition your sd card.
Unfortunately, it seems like the time for me to change phone has come.
While i was doing an other time a RUU reset because of loopboot created by an unrevoked related bug, my phone decided to stop, and die. The battery is still charged — i can feel the fuzz with putting my tongue on it — but the phone just doesn't turn on ; it doesn't show the charging led when i put it on charge...
I'm currently looking for an other device, such as the Desire S (because of the size, mainly ; others blockbusters are too big)
If someone has an idea to make my Desire turn on again, anything i can do, i will do.
Thx for the answer, the guide link, and all !
ynk said:
Unfortunately, it seems like the time for me to change phone has come.
While i was doing an other time a RUU reset because of loopboot created by an unrevoked related bug, my phone decided to stop, and die. The battery is still charged — i can feel the fuzz with putting my tongue on it — but the phone just doesn't turn on ; it doesn't show the charging led when i put it on charge...
I'm currently looking for an other device, such as the Desire S (because of the size, mainly ; others blockbusters are too big)
If someone has an idea to make my Desire turn on again, anything i can do, i will do.
Thx for the answer, the guide link, and all !
Click to expand...
Click to collapse
don't just go flashing RUU's randomly, you may get amoled/slcd incompatibility for instance, which is what this might be.
try reading the troubleshooting guide, you can probably save your phone.
read carefully before you do anything in future...this situation could probably have been avoided
Thanks a lot again
I should be more patient when trying to do things, but it's kinda annoying not to have it working...
Btw, i wasn't acting *that* randomly (at least, for me) : since anytime i was using unrevoked was blocking the phone onto the boot screen, the only way i found to restore it was flashing it again. But yeah, maybe it was done too randomly though...
The guide you gave me is full of good advices, but the only thing that could be matching for my case is a bad RUU flashing ; this doesnt look to be my case, since even if i put my phone on charge, the charging led doesn't turn on. The phone doesn't warm after pressing the power button... It looks like there's something related to electricity inside that have been broken somewhere... Don't you think so ?
[EDIT] I found some guys having my (new) problem here : http://www.htcdesireforum.com/htc-d...h-on-or-respond-to-a-charger-what's-happened/ I'm quite relax since it's not a "0day" problem : lots of people are talking about it, so i have some solutions : wait and pray, if not, try another battery, or let it dead.
ynk said:
Thanks a lot again
I should be more patient when trying to do things, but it's kinda annoying not to have it working...
Btw, i wasn't acting *that* randomly (at least, for me) : since anytime i was using unrevoked was blocking the phone onto the boot screen, the only way i found to restore it was flashing it again. But yeah, maybe it was done too randomly though...
The guide you gave me is full of good advices, but the only thing that could be matching for my case is a bad RUU flashing ; this doesnt look to be my case, since even if i put my phone on charge, the charging led doesn't turn on. The phone doesn't warm after pressing the power button... It looks like there's something related to electricity inside that have been broken somewhere... Don't you think so ?
[EDIT] I found some guys having my (new) problem here : http://www.htcdesireforum.com/htc-d...h-on-or-respond-to-a-charger-what's-happened/ I'm quite relax since it's not a "0day" problem : lots of people are talking about it, so i have some solutions : wait and pray, if not, try another battery, or let it dead.
Click to expand...
Click to collapse
that problem sounds different as that was posted ages ago, and they weren't messing around with rooting and RUUs...
i don't think you should 'wait and pray, try another battery, or let it dead'
can you get to recovery/bootloader/fastboot at all? please post more details. if you can then it's probably not bricked.
i'm unsure of whether you've actually tried anything in the troubleshooting guide. try [2] advanced boot problems, S-ON. create a goldcard and try the WWE RUU
if none of it makes sense ask directly in that thread
and if you get the RUU to boot, don't use unrevoked...follow my 1st reply...
I stopped all the things i was doing when i had your reply, trust me !
As i said, i can't get the device to be powered on ; since, i'm not able to have any access to hboot, fastboot, nor adb. The phone does not charge when plugged to a charger neither to a computer. The led stays black, and the battery doesn't get warm (which normally does when charging).
Since the phone doesn't turn on, the guide you gave me is useless (but i learnt a lot from it, so thanks for that). The only section which *could* have been useful was the one talking about wrong RUU flashing with SLCD off ; but since my screen was working, and the symptoms are different (my phone is not recognized by the computer), this is not describing my problem definitly.
Be sure that if i can boot that phone once again, i'll follow your 1st reply and won't use unrevoked on it ever...
I'm trying now to find an other battery, to know which from the battery xor the mobo of the phone is dead. If battery, i'll just buy a new one ; if mobo, i'll buy a Desire S, since my phone reached the warranty limit, and i would have to pay to repair it...
HI. Okay, so a couple weeks ago, I received a notification from HTC that said there was a new update available. Since I had S-Off and an unlocked bootloader (don't ask why, I just ****ing do.) I could not update, as it would give me errors, and cancel the update. So, earlier today I was fed-up with how slow my phone was being, and I wanted to fix it by updating. So I scoured XDA and found a thread about how to update by updating the HBoot or whatever. I followed those instructions and everything was fine, until I got to the initial part of installing the new **** through RUU. It was running fine, and then all of a sudden, the phone disconnected and ****ed the installation up. My battery was fully charged, and still has a charge as I am writing this. I digress. Whenever I would try to power my phone on, I would feel THREE (3) vibrations, and nothing would happen after. I tried booting into the stock recovery (fastboot, recovery, etc) and would still get THREE (3) vibrations. Bricked. So, I looked through a few threads on XDA, and found a few ways to fix it. Something about a Blind HBoot, or a Qualcomm Diagnostic Mode being stuck or something. Figured it was my best shot to try these. I tried them all. I put the PG76IMG.zip into my SD card, and booted up when holding Volume down, and only got THREE (3) vibrations. The tutorial said I was supposed to get FIVE (5) vibrations. So, I thought maybe it was something strange, and kept going through the tutorial. After five minutes, I'm supposed to press VOL UP, and should feel THREE (3) vibrations. Nothing happened. I waited and waited and tried again, and still, nothing. My phone is still lying here as a paperweight, and I want to get this working, so I can sell it because this phone is too much of a ****ing hassle for me. NOTHING HAS WORKED. ROMS, KERNELS, NOTHING. HAS. WORKED. I'M TIRED OF IT. I'm not a noob, I've been working with Android phones for a long time, and have never quite used an HTC device before. I had a Samsung Galaxy S Fascinate (CDMA) and it lost it's flash after I had moved to a different state. (The state I'm in does not have any towers for that carrier here.) SO. Can ANYONE give me a HIGHLY DETAILED tutorial, STEP BY STEP, to fix my phone?
HTC Wildfire S *Relocked* bootloader S-OFF CDMA METRO PCS.
I have tried everything I can find, and I have reached my wits end, man. Please, for the love of GOD, help me. I would really appreciate it.
I had 1000 rom flashes
3 Updates through RUU
Never had a brick
I hope someone can help you.
This is same as this thread http://forum.xda-developers.com/showthread.php?t=1522235
m1ndh4x8r said:
I had 1000 rom flashes
3 Updates through RUU
Never had a brick
I hope someone can help you.
This is same as this thread http://forum.xda-developers.com/showthread.php?t=1522235
Click to expand...
Click to collapse
I don't see how this helps me.
Help in the sense u have sent it to HTC for repair
Try this http://forum.xda-developers.com/showthread.php?t=1432425
Sent from my HTC_A510c using Tapatalk
kyleisah said:
HI. Okay, so a couple weeks ago, I received a notification from HTC that said there was a new update available. Since I had S-Off and an unlocked bootloader (don't ask why, I just ****ing do.) I could not update, as it would give me errors, and cancel the update. So, earlier today I was fed-up with how slow my phone was being, and I wanted to fix it by updating. So I scoured XDA and found a thread about how to update by updating the HBoot or whatever. I followed those instructions and everything was fine, until I got to the initial part of installing the new **** through RUU. It was running fine, and then all of a sudden, the phone disconnected and ****ed the installation up. My battery was fully charged, and still has a charge as I am writing this. I digress. Whenever I would try to power my phone on, I would feel THREE (3) vibrations, and nothing would happen after. I tried booting into the stock recovery (fastboot, recovery, etc) and would still get THREE (3) vibrations. Bricked. So, I looked through a few threads on XDA, and found a few ways to fix it. Something about a Blind HBoot, or a Qualcomm Diagnostic Mode being stuck or something. Figured it was my best shot to try these. I tried them all. I put the PG76IMG.zip into my SD card, and booted up when holding Volume down, and only got THREE (3) vibrations. The tutorial said I was supposed to get FIVE (5) vibrations. So, I thought maybe it was something strange, and kept going through the tutorial. After five minutes, I'm supposed to press VOL UP, and should feel THREE (3) vibrations. Nothing happened. I waited and waited and tried again, and still, nothing. My phone is still lying here as a paperweight, and I want to get this working, so I can sell it because this phone is too much of a ****ing hassle for me. NOTHING HAS WORKED. ROMS, KERNELS, NOTHING. HAS. WORKED. I'M TIRED OF IT. I'm not a noob, I've been working with Android phones for a long time, and have never quite used an HTC device before. I had a Samsung Galaxy S Fascinate (CDMA) and it lost it's flash after I had moved to a different state. (The state I'm in does not have any towers for that carrier here.) SO. Can ANYONE give me a HIGHLY DETAILED tutorial, STEP BY STEP, to fix my phone?
HTC Wildfire S *Relocked* bootloader S-OFF CDMA METRO PCS.
I have tried everything I can find, and I have reached my wits end, man. Please, for the love of GOD, help me. I would really appreciate it.
Click to expand...
Click to collapse
ok, im not saying i can get it going again but i`ll do my best to help. lets start from the beginning, what actually works atm? you say when you try boot up the phone in any way it just vibrates 3 times.
does it do anything else, does the screen light up?
does it even stay on?
when you connect it to the charger does the led still light up?
have you tried to connect it to the pc? have you tried to connect it too the pc with volume down first?
all seem very basic stuff obviously but if the pc can register it in hboot we might be able to get a ruu running on it.
Found this on a different thread...
Nevermind. Just realized you were still getting three vibrates. Sorry man. I'll keep an eye out if I see anything else that might help.
what is your hboot version? i was see 1.09.099 like in forum maybe you can start with update hboot.
you can use adb for all of this works. download a ruu and run it. after some steps you can find rom.zip in windows/temp extract it to a folder like c:\android\rom and use adb for install all *.img files. maybe it can fix that problem
hypercode said:
what is your hboot version? i was see 1.09.099 like in forum maybe you can start with update hboot.
you can use adb for all of this works. download a ruu and run it. after some steps you can find rom.zip in windows/temp extract it to a folder like c:\android\rom and use adb for install all *.img files. maybe it can fix that problem
Click to expand...
Click to collapse
seriously , adb can install img files ?!
Alright, well, I called htc and told them about my problem, and I might have to just send it in. BUT. I had my phone rooted, and had CM Recovery on it. So, since nothing is booting up at all, only the three vibrates when trying to enter either boot mode, will they be able to see that I had it rooted or anything? They said they'll charge 35$ just to ship it back in the same condition if it is. Can't really afford anything like that right now.
tl;dr I had my phone rooted, but nothing on my phone comes up, will they see my root or anything?
if you are rooted you are probably s-off or at least have unlocked bootloader. and both they will find out very easily.
Sorry for my bad it was fastboot.exe you can install .img files with fastboot.exe i was installed stock recovery with that
Sent from my HTC Wildfire S A510e using XDA App
Hello everyone, first of all I am a total newbie not just to rooting but also today was my first time ever using linux so please bear with me. Having said that, I have done my best to learn and understand the linux commands in the effin manual and followed all instructions as best as I could though I couldn't understand them well enough which is why I am here.
I am using Ubuntu 11.04 64 bit live cd but managed to install the i32-libs as stated in the effin manual. This is the only version of Ubuntu I could get from my friends as I have very slow internet connection and cannot download the new version or just the 32 bit one.
Anyway, on to the problem at hand.
I first ran the aahk, going through all the steps in the effin manual. My phone was originally on 2.3.5 and Sense 3 so I had to downgrade and the aahk downloaded the necessary rom(?) or RUU (?) to do this.
Once that was done, aahk carried on until the step where my phone rebooted.
This was where things started going wrong for me.
When the phone rebooted into 2.3.3 and started the wizard to set up my phone, I went through all that.
If I recall, at this point the aahk screen was up to “Once the downgrade is successful, press a key to return to the menu.... Otherwise, cut and paste the output to the screen into a text file for evaluation... then press a key. Press any key to continue...”
However, the step before that, “The phone will now reboot into HBOOT. If everything is okay, the phone will prompt you to continue by pressing VOLUME UP. It will reboot, flashing twice.”
PUSH POWER WHEN THIS STEP COMPLETES
I don't recall this happening for me or maybe it did but I did not notice. I did not press VOLUME UP nor see the flashing twice but surely it happened? Otherwise I would have been able to reboot into the phone environment correct? My head is spinning now...
Okay, this is where I may have gotten ahead of myself when reading the effin manual. You have to understand, I was just brimming with joy “thinking” I had successfully rooted my first ever and one and only smartphone.
I started looking for BusyBox or Superuser but couldn't find anything.
Not knowing what else to do, I rebooted the phone MANUALLY (hold power button and reset).
Then everything started going wrong.
Please don't get mad. I did not realise the aahk had to reboot several times. I thought once and that was it. I just found that out now.
However, between that time and when I found this out I believe I caused all sorts of damage.
When the phone rebooted, it got stuck on the white screen with HTC logo and aahk was no longer working.
The wrong things I did were to to go into HBOOT and RECOVERY and WIPE EVERYTHING (DATA, CACHE, DAVLIK, EVERYTHING) *SORRY!*
And so here I am, hoping someone can help me.
After searching around the forums some similarities I had with other users in the past was that the phone is still showing S-ON and because of what I had done, aahk did not get to work properly so my phone has no ROM and no RECOVERY.
And I also JUST realised I made things worse by deleting USB debugging when I WIPED everything!.
Please help.... (_ _”)
I can help you out. Can you still go in Hboot?
Sent from my Desire HD using XDA
dnplee said:
Hello everyone, first of all I am a total newbie not just to rooting but also today was my first time ever using linux so please bear with me. Having said that, I have done my best to learn and understand the linux commands in the effin manual and followed all instructions as best as I could though I couldn't understand them well enough which is why I am here.
I am using Ubuntu 11.04 64 bit live cd but managed to install the i32-libs as stated in the effin manual. This is the only version of Ubuntu I could get from my friends as I have very slow internet connection and cannot download the new version or just the 32 bit one.
Anyway, on to the problem at hand.
I first ran the aahk, going through all the steps in the effin manual. My phone was originally on 2.3.5 and Sense 3 so I had to downgrade and the aahk downloaded the necessary rom(?) or RUU (?) to do this.
Once that was done, aahk carried on until the step where my phone rebooted.
This was where things started going wrong for me.
When the phone rebooted into 2.3.3 and started the wizard to set up my phone, I went through all that.
If I recall, at this point the aahk screen was up to “Once the downgrade is successful, press a key to return to the menu.... Otherwise, cut and paste the output to the screen into a text file for evaluation... then press a key. Press any key to continue...”
However, the step before that, “The phone will now reboot into HBOOT. If everything is okay, the phone will prompt you to continue by pressing VOLUME UP. It will reboot, flashing twice.”
PUSH POWER WHEN THIS STEP COMPLETES
I don't recall this happening for me or maybe it did but I did not notice. I did not press VOLUME UP nor see the flashing twice but surely it happened? Otherwise I would have been able to reboot into the phone environment correct? My head is spinning now...
Okay, this is where I may have gotten ahead of myself when reading the effin manual. You have to understand, I was just brimming with joy “thinking” I had successfully rooted my first ever and one and only smartphone.
I started looking for BusyBox or Superuser but couldn't find anything.
Not knowing what else to do, I rebooted the phone MANUALLY (hold power button and reset).
Then everything started going wrong.
Please don't get mad. I did not realise the aahk had to reboot several times. I thought once and that was it. I just found that out now.
However, between that time and when I found this out I believe I caused all sorts of damage.
When the phone rebooted, it got stuck on the white screen with HTC logo and aahk was no longer working.
The wrong things I did were to to go into HBOOT and RECOVERY and WIPE EVERYTHING (DATA, CACHE, DAVLIK, EVERYTHING) *SORRY!*
And so here I am, hoping someone can help me.
After searching around the forums some similarities I had with other users in the past was that the phone is still showing S-ON and because of what I had done, aahk did not get to work properly so my phone has no ROM and no RECOVERY.
And I also JUST realised I made things worse by deleting USB debugging when I WIPED everything!.
Please help.... (_ _”)
Click to expand...
Click to collapse
Do not panic...although you did a factory reset and disabled usb debugging, you can solve your situation. Just flash the RUU (PD98IMG-GBx.zip) file you used to downgrade the phone. It has to be in the PD98IMG folder of the Hack Kit. Make sure that it is that file and no other. Rename it PD98IMG.zip and then put it in the root of the sdcard. Then boot in hboot and update pressing volume up. Let it finish....then you will have a working phone. Then re run the hack kit to Gain S-OFF and Root....if you can´t do it just hit the IRC Channel that is stated in the OP of the Hack Kit thread.
benydc, glevitan, thank you both for the offers of help and advice.
I eventually found my way to the IRC aahk support channel and was blessed to get the help of attn1, one of the ops there.
He helped me through my problem and now everything is as is should be. Thankfully I have a working rooted phone.
Everyone there was very friendly and helpful, not just attn1. He must have spent the last two hours or so juggling with helping out three users (probably more). We even got to make some friendly banter amongst ourselves.
Though I was freaked out initially, I am glad everything works now and from the support I got there, I am somehow not going to shy away from trying to learn about rooting.
I managed to save all the text during our conversation so when I get the time, I will try and build a simple but detailed walkthrough of how attn1 got my phone working again. I will post it here so that it may help others who find themselves in a similar position one day.
Many thanks you guys. This is a great community.
same problem,s-on,no recovery
hey there...ive got similar problem with u and i try putting the PG98IMG on the root of the SD card which i get from the folder from AAHK...but when i go to HBOOT and try to install the PG98IMG, it failed and it says MAIN VERSION IS OLDER ! what should i do?
hi
i have same phone whith you
2.3.5 sens 3.0
i used AAHK but the file name downloaded is "PD98IMG-GB2"
you can rename "PD98IMG" on "PD98IMG-GB2"
Hi All,
The story, I'm on vacation in Austria with my new HOX+ and suddenly I get an update for it. So I downloaded it and installed it. Suddenly I have no cell connection and cannot use wi-fi anymore. The phone is stuck in Airplane Mode and can not get out.
So I go looking on the web and spent hours reading on flashing, downgrading, rooting etc. So I decide to downgrade it to stock. Something went horribly wrong, as it didn't work. I unlocked it, every step correctly. Then I tried it again, and again, and again. Multiple different guides, video's everything. So then I thought I found a solution, install JB 4.1.2. So, following every step correctly I try this, no succes. But now suddenly I cannot see the sdcard, htc sync doesn't find my phone etc. Also, my phone doesn't go past the HTC bootlogo. I can now only run the bootloader by power vol-
So I try to flash the JB again, connection error, cannot find folder etc. So I start looking again, tried recovery, factory reset, nothing works. Flashed CWM 5.8.4.0 into the recovery, does not boot, only up to the HTC logo then powers down and reboots bootloader.
So here I go to the last resort: Stock RUU. I download the correct RUU for my HOX+ -in this case RUU_ENRC2B_U_JB_45_HTC_Europe_1.16.401.6_Radio_3.1204.168.32_release_297177_signed .... I start the programme and it works good and then it starts rebooting the bootloader and then I get the black background with silver HTC letters and then the RUU says Error 171 USB Connection Error.
I've tried about 10 times now in different USB slots, same thing every time.
Also, when I start the bootloader from scratch, it says Checking SD update... Failed to open usb master mode
Is there anybody who can help me? I have tried for 30 hours now, every single option (I think?)... I don't care what kind of ROM goes on there, stock, jb, evolution as long as it works!
Ran the RUU with admin rights?
Sent from my HTC One X
TToivanen said:
Ran the RUU with admin rights?
Sent from my HTC One X
Click to expand...
Click to collapse
Yes, I did, first without and then multiple times with as I read that advice somewhere as well.
Also, I did relock the phone first as I read that somewhere, forgot to state above.
Ok the twentieth time seems to be a charm, after 5 hours trying the RUU is succesfully installed and everything works perfectly fine now!
Many thanks! Not sure if I would have tried again and again after it kept failing!
Also, probably wrong forum? HoX+ should have it's own forum does it not?
Gerolamos said:
Ok the twentieth time seems to be a charm, after 5 hours trying the RUU is succesfully installed and everything works perfectly fine now!
Many thanks! Not sure if I would have tried again and again after it kept failing!
Click to expand...
Click to collapse
i have same problem should i try diffrent RUU or try 20th time ??
what should i do