Database Users

think i bircked my phone

ok so i just installed the JIT update on top of the Lightningbolt ROM and now i cannot do anything it is stuck on the android on skateboards picture, but it is responding adb commands and recovery is working. is there anything i should to fix this. should i just put a old nandroid update back on my phone and flash that?

ljbaumer said:
ok so i just installed the JIT update on top of the Lightningbolt ROM and now i cannot do anything it is stuck on the android on skateboards picture, but it is responding adb commands and recovery is working. is there anything i should to fix this. should i just put a old nandroid update back on my phone and flash that?
Click to expand...
Click to collapse
Go back to your NAND. DOesnt sound like you are bricked. Bricked is not being able to turn it back on.

ok thanks i will try that right now
rebooting..... (please work!!!!) (i really need my phone in the next few days)
HOLLY SHI it is actually booting the IC3 ROM right now !!!! thank you guys so much it just booted to the home screen!!! thanks for you help!

good news, btw just to let you know Ic3Rom has issues with JIT dont try to install it or you will most likely get a endless reboot cycle and have to nand restore again.

ljbaumer said:
ok thanks i will try that right now
rebooting..... (please work!!!!) (i really need my phone in the next few days)
HOLLY SHI it is actually booting the IC3 ROM right now !!!! thank you guys so much it just booted to the home screen!!! thanks for you help!
Click to expand...
Click to collapse
lol, didnt do anything. just rem, always nand before trying to flash anything. for reasons like this.
But thank you.

if you can get into your recovery..its not bricked...
honestly, its damn near impossible to brick your phone with the instructions that all devs provide...+ youtube videos make it even easier..

ljbaumer said:
ok so i just installed the JIT update on top of the Lightningbolt ROM and now i cannot do anything it is stuck on the android on skateboards picture, but it is responding adb commands and recovery is working. is there anything i should to fix this. should i just put a old nandroid update back on my phone and flash that?
Click to expand...
Click to collapse
Just to let you know the LightningBolt rom already has JIT enabled so no need to flash an update on it.

Major Brick!!

Hi all!
Seriously in need of some expert help from your kind selves. Basically my phone is rooted with custom roms. I'm needing to try to get it back to normal as it has developed a hardware fault in the way that the volume key doesn't work, more so the down volume. Sometimes the up volume works when it feels like it. The camera itself has also been playing up and not working at times (not sure if this would be hardware related). As you can guess I'm wanting to get the phone repaired under warranty. The major headache comes when I need to get into the bootloader and I can't with the down button not working. Earlier I flashed a different kernel and when the phone went to reboot all hell broke loose. I'm currently stuck on the white screen with HTC logo. So without getting into the bootloader to try to recover I'm in serious bother! I tried this link and followed all the steps but in the end it just kept giving me an unknown error message
http://forum.xda-developers.com/showthread.php?t=841890
I'm just trying to get the phone back up and running and then will take it from there to return it back to stock if possible. One thing I didn't try was the fact I have a 1.84 rom on and tried to flash with 1.72. May well try a 1.84 later on when I get the chance.
I hope you basically understand what I've done and what I'm trying to achieve and the problems I've got.
Thanks in advance if you can provide any solutions or ideas to try.

oooo boi thats gota hurt... but dont worry.. download "quickboot" from the market with it u can go to bootloader and cmw recovery .. about the rest.. i didnt get it.. u have 1.72 stock ruu and u want to get 1.84 ? why not just use 1.32 old rom and send it back repair guys ?

Find the downgrade thread in the Dev section, download the PD98IMG.zip from that thread. Put that on your SDcard.
Now you want to boot into bootloader which maybe difficult given your button predicament. I am sure there must be a fastboot/adb command to do this, possibly
fastboot reboot-bootloader
The bootloader should read and flash the PD98IMG.zip automatically, returning you to stock.

Hi mate. I had same problem my volume buttons don't work at all but i managed to flash latest recovery witch let's you scroll with home button don't no if this helps but try it

Thanks guys for trying to help. Leatherface I'm stuck on the white boot screen with htc logo and it won't go any further so can't get into market to download any apps. Or is the program you're talking about available for pc? I have custom roms on and not stock but want to put stock back on to send in for repair.
AndyHarney I will try your advice later but obviously as soon as I turn phone on it goes straight to the boot screen so I really can't see how I could get into the bootloader any other way but I may be wrong. Hopefully I am!!
Biggy I did flash with the latest CWM right before it went beserk but still no way of getting into bootloader.
I'm off for an Easter drink now to take my mind off it coz it's stressing me out and will return soon to butcher my phone a little more lol
Happy Easter

Of course, to use fastboot you need to be in fastboot in the bootloader.
Using the app Leather|Face mentioned, is there an option to boot into bootloader?
Anyways, enjoy your bank holiday.

thegeordiehunk said:
Thanks guys for trying to help. Leatherface I'm stuck on the white boot screen with htc logo and it won't go any further so can't get into market to download any apps. Or is the program you're talking about available for pc? I have custom roms on and not stock but want to put stock back on to send in for repair.
AndyHarney I will try your advice later but obviously as soon as I turn phone on it goes straight to the boot screen so I really can't see how I could get into the bootloader any other way but I may be wrong. Hopefully I am!!
Biggy I did flash with the latest CWM right before it went beserk but still no way of getting into bootloader.
I'm off for an Easter drink now to take my mind off it coz it's stressing me out and will return soon to butcher my phone a little more lol
Happy Easter
Click to expand...
Click to collapse
as long as the rom ur using is not cynogenmod7... ur warranty isnt void my friend
did u try to re-flash a rom ? trying flashing a fresh rom.. full wipe ur phone before.. bellow in atttachment is full wipe.. download it extact it and put "full wipe 1.3" in ur sd card.. and put a rom there too.. then boot into recovery.. 1st do a full wipe.. then flash the rom.. see if that solves ur problem doode..
Edit : aaa crap.. i forgot u cant go into bootloader.. :|
Edit 2 : the guy 2 posts above said that u can use ur home key to navigate thro recovery... maybe u could use it for booting it to boot loader too.. donno lemme try if that can happen
Edit 3 : no that didnt work... btw abt 6 months back... on my samsung galaxy s... volume keys wudnt work so i couldnt get into recovery to get make to stock rom because i was using custom roms... i cudnt do anything and i was still under warrantly. so i perposly bricked ma phone to the extent that no matter wat u do with it, it wudnt switch on.. and i was sent a new one

If you are trying to get into bootloader another way worked for me but maybe not every. Body is to flash a new splash with android flasher then pull cable at correct moment when it boots into fastboot briefly. He'll it works for me LOL

biggy81168 said:
If you are trying to get into bootloader another way worked for me but maybe not every. Body is to flash a new splash with android flasher then pull cable at correct moment when it boots into fastboot briefly. He'll it works for me LOL
Click to expand...
Click to collapse
thanks for letting me knw man... i cud use that if nothing else is possible lol

my down volume key does not work either, and i have had difficulty with this.
i have just tried to install a theme, and reboot and it was stuck on white htc screen.
plugged phone into computer, use adb reboot bootloader and load up recovery from there..

I flashed a full wipe zip by mistake and with no volume buttons i thought i was screwed but after two days trying i found i could only go back to stock 132 every thing else would fail?

For anyone who is in this predicament, if you can't or are unwilling to use adb, then if you download and install Droid Explorer, there is the option to boot into bootloader, flash other ROMs and loads more besides.

Nope... u just need. To. Root and eng s off and s off again...then ur back in business
Sent from my Desire HD using XDA Premium App

like someone said before, you can access the phone with adb and forget about touching the controls on the actual phone, it can go into bootloader, and from there i guess you can reflash or recover your stock rom
adb is more simple than it sounds, it's just sort of like remote control via the computer

I've tried adb fastboot as suggested but all it says is <waiting for device>. I've tried plugging device in and turning it on both before and after entering this command but the phone just immediately goes to the white HTC screen. Also tried Droid Explorer as suggested but I can't even get that to install as it throws up an error message during install!! I'm not having a good time with this phone at the moment lol

If you downloaded the PD98IMG.zip from the downgrade thread, and download Quick Boot from the market.
Put the zip on your SDcard and use Quick Boot to get to the bootloader. From there is should be an automated process, and your phone will be restored to HTC stock.

I'm unable to get into the market to download anything since the phone doesn't boot

Ok I'm back in business. Just managed to flash a clean rom. Some nice chappy on another thread was also having the exact same problems as me and he managed to sort it out and helped me. The commands are ADB REBOOT RECOVERY or ADB REBOOT-BOOTLOADER. I was typing FASTBOOT REBOOT-BOOTLOADER as mentioned in an earlier post and wasn't getting anywhere.
However I'd like to thank you all for your efforts and now I should be able to return the phone to stock and get it shipped off for repair with peace of mind that they won't whinge that the warranty is null and void.

Leather|Face said:
Edit 3 : no that didnt work... btw abt 6 months back... on my samsung galaxy s... volume keys wudnt work so i couldnt get into recovery to get make to stock rom because i was using custom roms... i cudnt do anything and i was still under warrantly. so i perposly bricked ma phone to the extent that no matter wat u do with it, it wudnt switch on.. and i was sent a new one
Click to expand...
Click to collapse
Luckly you didnt do above method..lol
Sent from my Desire HD using XDA App

naimmkassim said:
Luckly you didnt do above method..lol
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
ROFLMAO !

touch screen not working

Hey guys, a few days ago I finally decided to root my phone and flash cynagen mod 7...
However yesterday evening my touch screen suddenly stopped working, so I can't unlock my phone...
its still showing screen but its not responding when I press anything...
Things ive tried: removing battery for 20 sec, removing battery to turn off the phone and start it up again.
Is it possible to fix this?
or does anyone have the stock Vodafone firmware so I can try flashing it and return it for warranty?

Try reflashing the Rom from recovery again maybe that will help, I think I saw a thread on here about a fix for that problem a few months ago but not sure as I never needed it so didn't read it.
Sent from my HTC Wildfire using XDA Premium App

Scratch0805 said:
Try reflashing the Rom from recovery again maybe that will help, I think I saw a thread on here about a fix for that problem a few months ago but not sure as I never needed it so didn't read it.
Sent from my HTC Wildfire using XDA Premium App
Click to expand...
Click to collapse
You mean re flashing the stock Vodafone rom?
Any place where I can find it?
Btw even clockworldmod doesn't seem to respond to my buttons(the ones below the screen)
Only the physical buttons work...

Sorry I meant try reflashing your cm7 Rom again from recovery, use the volume buttons and the trackball to navigate in clockwork.
Sent from my HTC Wildfire using XDA Premium App

Scratch0805 said:
Sorry I meant try reflashing your cm7 Rom again from recovery, use the volume buttons and the trackball to navigate in clockwork.
Sent from my HTC Wildfire using XDA Premium App
Click to expand...
Click to collapse
ill give it a shot, by the way when I tried to flash with RUU it didn't detect my phone.
Also when I boot up my phone with charge cable it stops responding and only the red charging light will burn(even when the battery is full, because it did this for hours a few days ago)
Also in clockwork when I go to advanced and key test it doesn't do anything when I press a key, It doesn't show anything in the log.
So I think its really broken.
Update: reflashed with cyanogen didn't fix it
And when I try to flash with WUU it says my phone is not connected
ofc I can't access my usb settings on the phone...

The charging bug comes with clockwork, when the phone is off if you plug in the charger it happens so I always make sure to hit the power button first wait till the splash screen has gone and then plug it in, its annoying but just pop the battery out and then reboot the phone. There's a fix for that too but it didn't work for me.
As for the other problems I'm not sure as I've never come across them on my phone before, I would definitely try reflashing first before using an ruu. If that doesn't help hang fire till someone a bit smarter than me sees this.
Sent from my HTC Wildfire using XDA Premium App

Scratch0805 said:
The charging bug comes with clockwork, when the phone is off if you plug in the charger it happens so I always make sure to hit the power button first wait till the splash screen has gone and then plug it in, its annoying but just pop the battery out and then reboot the phone. There's a fix for that too but it didn't work for me.
As for the other problems I'm not sure as I've never come across them on my phone before, I would definitely try reflashing first before using an ruu. If that doesn't help hang fire till someone a bit smarter than me sees this.
Sent from my HTC Wildfire using XDA Premium App
Click to expand...
Click to collapse
I just tried re flashing and that didn't help, I think my screen is really broken.
Including those home, menu back and search button.
only the power and the volume buttons and track ball work...
Update: sometimes my screen seems to work for a few seconds and then it doesn't again...
Depends on how I hold my phone...

gijs007 said:
I just tried re flashing and that didn't help, I think my screen is really broken.
Including those home, menu back and search button.
only the power and the volume buttons and track ball work...
Update: sometimes my screen seems to work for a few seconds and then it doesn't again...
Depends on how I hold my phone...
Click to expand...
Click to collapse
Especialy by saying that last thing, one would think about a bad contact in the cable that connects your motherboard with your screen. I could be wrong, but I think the softkeys belong to the screen as well, so that would explane it. But I'm not sure about that last one.
You can try opening up your phone and see if the connection of the cable to the motherboard is still good. To open up the phone, you can folow the guide for the htc desire, it is said that they are alike.
Keep in mind that the bad connection can be IN that cable as well. So perhaps you have to look if you can buy a seperate cable somewhere (don'y know if that is possible).
I must stress out that I never opened this phone myself, so all the things I say here are based on what I've read on this forum. It just seems logic to me
One more thing: this all sounds risky. But since you are out of waranty, and since your phone doesn't work, I personally would give it a try.
Erwin

ErwinP said:
Especialy by saying that last thing, one would think about a bad contact in the cable that connects your motherboard with your screen. I could be wrong, but I think the softkeys belong to the screen as well, so that would explane it. But I'm not sure about that last one.
You can try opening up your phone and see if the connection of the cable to the motherboard is still good. To open up the phone, you can folow the guide for the htc desire, it is said that they are alike.
Keep in mind that the bad connection can be IN that cable as well. So perhaps you have to look if you can buy a seperate cable somewhere (don'y know if that is possible).
I must stress out that I never opened this phone myself, so all the things I say here are based on what I've read on this forum. It just seems logic to me
One more thing: this all sounds risky. But since you are out of waranty, and since your phone doesn't work, I personally would give it a try.
Erwin
Click to expand...
Click to collapse
I would give it a try, but im not out of warranty, its just voided until I re flash a stock Vodafone firmware.
So if anyone could give me one id be really happy.
Preferably a Dutch/nl one with hboot 1.02

There's links to some ruu's in here, hope you find what your looking for.
http://forum.xda-developers.com/showthread.php?t=1029318
ErwinP said:
Especialy by saying that last thing, one would think about a bad contact in the cable that connects your motherboard with your screen. I could be wrong, but I think the softkeys belong to the screen as well, so that would explane it. But I'm not sure about that last one.
You can try opening up your phone and see if the connection of the cable to the motherboard is still good. To open up the phone, you can folow the guide for the htc desire, it is said that they are alike.
Keep in mind that the bad connection can be IN that cable as well. So perhaps you have to look if you can buy a seperate cable somewhere (don'y know if that is possible).
I must stress out that I never opened this phone myself, so all the things I say here are based on what I've read on this forum. It just seems logic to me
One more thing: this all sounds risky. But since you are out of waranty, and since your phone doesn't work, I personally would give it a try.
Erwin
Click to expand...
Click to collapse
I've changed the touchscreen on mine and can confirm the softkeys are attached to it, there's 2 separate cables though I think the one from the softkeys is only for the led's as mine broke, the buttons work fine but I have no lights behind them.
Sent from my HTC Wildfire using XDA Premium App

gijs007 said:
I would give it a try, but im not out of warranty, its just voided until I re flash a stock Vodafone firmware.
So if anyone could give me one id be really happy.
Preferably a Dutch/nl one with hboot 1.02
Click to expand...
Click to collapse
As you are looking for a ROM with hboot 1.02, I assume that before rooting you had the same hboot? Because then you must have gained root using AlphaRevX/Revolutionary, which installs a custom bootloader. This hboot can, to my knowleadge, not be downgraded to the original one. In other words: you have voided your waranty and there is no way to cover it up...
Erwin

ErwinP said:
As you are looking for a ROM with hboot 1.02, I assume that before rooting you had the same hboot? Because then you must have gained root using AlphaRevX/Revolutionary, which installs a custom bootloader. This hboot can, to my knowleadge, not be downgraded to the original one. In other words: you have voided your waranty and there is no way to cover it up...
Erwin
Click to expand...
Click to collapse
Damn, will they figure this out or is their a change they are just like oh yeah the screen is broken lets fix it?
As its clearly a hardware issue and not a software issue...
Other whys ill just fix it my self or go to a phone store...
update: I tried flashing SUU but it keeps giving me a message that my phone is not connected...
But the phone store told me rooting does not void my warranty as its a hardware issue and not a software issue.. they told me they could send it for me to a special company that repairs phones and is qualified by mayor factories like HTC,Samsung,etc.
But they also told me it would be easier to just contact Vodafone for repairs as that is free and if not I could always come back.

I'd send it back to Vodafone, best case they'll switch the touchscreen power it up for a quick test then send it back, worst case is they may check your software versions... then send it back unrepaired.
I used to fix iphones and ipads for an insurance company and hardly ever had enough time for checking software, just fix it, send it out and crack on with the next one!
Sent from my HTC Wildfire using XDA Premium App

dont panic your phone is all right
It also happened in my case.Go to the following link
http://shipped-roms.com/index.php?category=android&model=Buzz
and flash a suitable ruu rom .it will definitely fix ur phone.or u can just boot into recovery by pressing volume and power button simultaneously during the boot and flash cm 7 rom.

rashmifantasy said:
dont panic your phone is all right
It also happened in my case.Go to the following link
http://shipped-roms.com/index.php?category=android&model=Buzz
and flash a suitable ruu rom .it will definitely fix ur phone.or u can just boot into recovery by pressing volume and power button simultaneously during the boot and flash cm 7 rom.
Click to expand...
Click to collapse
I already re flashed cm7, and at first it didn't help then suddenly it did help and now its doing nothing all over again...
Update: re flashed again and still nothing.

AFAIK reflashing a custom rom from a custom recovery should not solve the issue.
But reflashing a stock ROM (= RUU) should solve that. Also reflashing a stock ota update will solve that. Ota update needs to be flashed from stock recovery. Do either of these things depending on what your hboot version is (if hboot is latest then ota will be option for most times) Also remember PC49IMG method if you presently have custom recovery.
P.S : what all I said is thinking that it is software issue. this shouldn't help if it is related to hardware.
Sent from my Blade using XDA App

I was wondering if there was a way to flash using that method, as I said I never needed to flash an ruu yet so don't know much about em. Just saw your other post explaining how to use PC49IMG to flash an ruu. Thought i'd copy it here as it may help.
bharatgaddameedi said:
If it still had the issue, then install the RUU by pc49img method. Download the correct ruu for your phone. Donot connect phone to PC. On windows PC click on start and type %temp% and enter. This opens the user temporary folder of your PC. Now run the ruu. Now if you observe the temp folder, there will be extra folders created which have folder name enclosed in {} brackets. Search in these folders for the file ROM.zip. Copy the ROM.zip to a safe location. Now format your memory card to fat32 (must) and put the ROM.zip to the root of memory card. You should use memory card reader. Then rename the ROM.zip to PC49IMG.ZIP . Then insert memory card in phone and reboot to hboot menu from where you can update/reflash the partitions. If still not working, clear storage again from hboot menu.
Sent from my Blade using XDA App
Click to expand...
Click to collapse

if ur stock screen is showing a date of 1980(after flashing a custom rom)
Just flash the RUU_Buzz_Froyo_hTC_Asia_WWE_2.24.707.1_Radio_13.55.55.24H_3.35.20.10_release_161113_signed.exe
it will help

Scratch0805 said:
I was wondering if there was a way to flash using that method, as I said I never needed to flash an ruu yet so don't know much about em. Just saw your other post explaining how to use PC49IMG to flash an ruu. Thought i'd copy it here as it may help.
Click to expand...
Click to collapse
Did that and now its on stock Vodafone firmware
But the touch screen still isn't working.
Oh well now I can send it back to Vodafone for repairs.
Thanks for the help
Btw: is their anyway to get the original hboot back?

For maybe some more like me that want to go back to what it use to be with the hboot S-OFF, S-ON issue.
I had my phone S-OFF with alpharevx beta. Used CM7 -stable for couple days but decided i wanted to go back to all original. I first RUU my phone with the RUU_Buzz_Froyo_HTC_WWE_2.22.405.1_Radio_13.55.55.2 4H_3.35.20.10_release_160191_signed.exe file. Boot it up, made sured it runs, then did what is instructed below here;
To be able to do this you need HTC USB drivers installed. Install the HTC pakage, reboot, uninstall the HTC-
Sync software, keep the drivers! reboot PC again.
Power off your phone. Plug in your USB cable to phone. Press volume down and powerup your phone. After it
settle navigate down and choose fastboot option.
1. Unpack these files to your c:\fastboot
2. Open up your windows command promt (WinVista/7 users rightclick choose run as Administrator)
3. in command promt type CD\ then press enter
4. then your should be in C:\
5. type cd fastboot
6. then you should now be in dir C:\fastboot
7. Im bored to death typing, look below. Beware of each command ends with enter. After success, reboot.
C:\fastboot>fastboot oem mb 9C068490 1 30
... OKAY
C:\fastboot>fastboot flash hboot hboot_buzz_7225_1.01.0001.nb0
sending 'hboot' (512 KB)... OKAY
writing 'hboot'... OKAY
Files needed (Windows version): megaupload.com/?d=UO9L74I9
Works perfectly for me.
* NOTE: Im not responsible for your phone if you brick/kill it. These steps worked for me!

DHD in trouble-any ideas?

So,the DHD was running perfectly fine till yesterday,when something strange started happening.The damn thing wouldn't show some widgets(all were non-HTC widgets btw) and a message about the SD card popped up,but I couldn't see what it was saying,as the phone rebooted.After it booted the battery had dropped from about 90% to 10% btw.What was strange?Well,as soon as screen went off,it wouldn't turn on again.Pulled battery,rebooted.The same again and again and again.I thought it had to do with my UV settings.Removed my scripts,rebooted.Still the same.I also removed some ram-optimization scripts I was testing,in case that was the problem.Again,nothing changed,the problem persisted.Then I changed kernels(LordClockan's Sense kernel v4,LeeDroid's kernel v4,RCMix Team's v11 and v10) to no avail.I also changed roms(RCMix3D to LordClockan's 0.8 ICS build and back),but STILL nothing.I even changed recoveries(From CWM 4.0.0.2 to 4EXT Touch 1.0.2 RC1) but it didn't fix the problem,even after a full wipe-format of ALL partitions.I tried removing the SD card and the SIM card in case one of them was causing the problem,but the same happened.
Then I thought "****,let's see what the hell happens".To better explain what happens,when I try to turn the screen back on(Even if it was off for like 1sec) it doesn't turn on.The buttons' lights turn on,but nothing responds.However,I can hear background notifications and stuff.While it's working,it also doesn't reboot or power off when prompted to do so,either through some app or through the power menu.
So,back to what I was saying,I decided to run a logcat to see what happens.But adb won't recognize the device at all.No matter if it's "adb reboot" or "adb logcat" or anything,it says "device not found".
So,what I haven't tried yet is changing radios,but:
i)I'm afraid it may finish it off in case something goes even more wrong
ii)I don't think it's in any way related to the problem
So,before I quit trying and call HTC for warranty purposes(IF I can still flash an official RUU for Christ's sake),do you guys have any ideas?I'm out of ideas right now.AND it sounds hardware related or something(Although I can still transfer files from my PC to the SD card).
Thanks in advance guys.

my phone wouldn't turn back on after a phone call ended, and it turns out the proximity sensor was playing up, so i used the recalibrator from here: http://forum.xda-developers.com/showthread.php?t=951858
this probably won't be the right solution for you, because this isn't the typical problem that the recalibrator solves, your problem sounds very strange. but it might be worth a shot anyway.
you should be able to get in to bootloader to flash a stock rom. If adb and the power menu are both not working, boot in to recovery from inside the 4ext recovery control app or Rom Manager app, then in recovery go to the power menu and there's the option to boot in to bootloader. and since you can put things on the SD still, put a PD98IMG.zip on the sd and away you go.
if that doesn't fix it, it's probably hardware unfortunately
good luck!

maatsby said:
my phone wouldn't turn back on after a phone call ended, and it turns out the proximity sensor was playing up, so i used the recalibrator from here: http://forum.xda-developers.com/showthread.php?t=951858
this probably won't be the right solution for you, because this isn't the typical problem that the recalibrator solves, your problem sounds very strange. but it might be worth a shot anyway.
you should be able to get in to bootloader to flash a stock rom. If adb and the power menu are both not working, boot in to recovery from inside the 4ext recovery control app or Rom Manager app, then in recovery go to the power menu and there's the option to boot in to bootloader. and since you can put things on the SD still, put a PD98IMG.zip on the sd and away you go.
if that doesn't fix it, it's probably hardware unfortunately
good luck!
Click to expand...
Click to collapse
Well,I know my way around the device,but sadly that's not enough this time.
Do you by any chance know what stock rom I should flash?I kinda lost track of things since I bought my Galaxy S II...
Thanks for the reply too pal.

Adb kill-server
Adb start-server
Then try and do other adb commands, see if that works
Sent from my HTC Desire HD A9191 using xda premium

tolis626 said:
Well,I know my way around the device,but sadly that's not enough this time.
Do you by any chance know what stock rom I should flash?I kinda lost track of things since I bought my Galaxy S II...
Thanks for the reply too pal.
Click to expand...
Click to collapse
No worries. I returned to stock last week for warranty, I flashed this: http://www.multiupload.com/BTJ8KY0KH9
from this thread: http://forum.xda-developers.com/showthread.php?t=905003
I used this one because it is easily re-rooted with visionary. So if you flash the stock rom and the problem is fixed you can head back in to rooting land straight away. But unfortunately, if you have to send it to HTC after all, they'll probably OTA upgrade it before giving it back

maatsby said:
No worries. I returned to stock last week for warranty, I flashed this: http://www.multiupload.com/BTJ8KY0KH9
from this thread: http://forum.xda-developers.com/showthread.php?t=905003
I used this one because it is easily re-rooted with visionary. So if you flash the stock rom and the problem is fixed you can head back in to rooting land straight away. But unfortunately, if you have to send it to HTC after all, they'll probably OTA upgrade it before giving it back
Click to expand...
Click to collapse
Thank you dude.Will try and report back.I hope everything goes too well.Or,in that aspect,too wrong in case I can get a new device.

So,after a downgrade to stock 1.32.xx version(the one maatsby posted) it seems to be solved...Strange indeed,but I'm happy!I love this phone.
I'm gonna check whether rerooting will make the problem reappear.I certainly hope not.
Anyway,thanks for the help,especially you maatsby!

tolis626 said:
So,after a downgrade to stock 1.32.xx version(the one maatsby posted) it seems to be solved...Strange indeed,but I'm happy!I love this phone.
I'm gonna check whether rerooting will make the problem reappear.I certainly hope not.
Anyway,thanks for the help,especially you maatsby!
Click to expand...
Click to collapse
no worries mate, and thanks for the update. I'm glad that fixed it!
It would be interesting to know what went wrong!

maatsby said:
no worries mate, and thanks for the update. I'm glad that fixed it!
It would be interesting to know what went wrong!
Click to expand...
Click to collapse
Yes,it would be interesting,but I even nandroid-ed back to my previous ROM(the one the problems first appeared on) and it's working flawlessly.If it does it again I'll make sure to post it here in case others have the same problem in the future.

Razr M XT 907 - Multiple Problems after flashing with RSD Light

Hey guys so I am facing weird problems. I have searched through the forums either I cant find anything or I am too scared to do any more experiments I really dont want to loose my Razr M XT 907.
Problems
Laggy performance at times
Camera gets stuck when I take pictures at times then I have to restart.
when I reboot my phone it shows AP Fast boot screen, then I have to access boot menu and select the second last option (Console something). It always shows Null:Null and when I change it back the phone reboots normally
Phone hangs sometimes and then responds with everthing I have clicked all at once.
The screen on off button responds a second late
I think you guys can help me better if I tell you what I did to this phone exactly since I got this phone.
What I did
I initially bought this phone with defaul OS 4.0.1 in Pakistan.
I then installed a Verizon system update of 250 MB that got my phone stuck on a boot loop (and made me cry almost)
I restored my phone to the settings it came in using this procedure
http://www.andromods.com/tips-trick/how-to-restore-unroot-droid-razr-m-xt907-stock-original-firmware.html
The phone worked fine for 2 days but then I got that update prompt again and it got annoying so I though maybe If i upgrade it to JB using the same RSD Lite method but a different ROM that may solve it.
So I applied the above Procedure using this ROM
http://forum.xda-developers.com/showthread.php?t=2250155
The method showed as Passed on RSD Lite but the phone got stuck on bootloop again so I paniced and tried restoring my phone abck to ICS using the method mention in the first link provided.
Then the phone got stuck on AP Boot Menu
Then I used DROID_RAZR_M_Utility_1.20 and used both methods 1 and two but it didnt work
Then out of the blue I went to the boot menu and I saw an option Switch Console (Null:null) I pressed up key on and null null changed to default:tty something it and the phone booted up just fine back to ICS
Now everytime I power off the phone it goes to AP Boot menu showing FASTBOOT REASON: Sticky bit factory_fastboot and I have to do the above to restart the phone.
What I need
Please help me restore my phone I dont want to brick it, I am a simple user I will need step by step guide
Anyone ?

Bump
Bump still looking for a solution

I have CM10 on mine and the camera is completely broken

Enter fastboot oem fb_mode_clear and problem gone.

v0ltage112 said:
Hey guys so I am facing weird problems. I have searched through the forums either I cant find anything or I am too scared to do any more experiments I really dont want to loose my Razr M XT 907.
Problems
Laggy performance at times
Camera gets stuck when I take pictures at times then I have to restart.
when I reboot my phone it shows AP Fast boot screen, then I have to access boot menu and select the second last option (Console something). It always shows Null:Null and when I change it back the phone reboots normally
Phone hangs sometimes and then responds with everthing I have clicked all at once.
The screen on off button responds a second late
I think you guys can help me better if I tell you what I did to this phone exactly since I got this phone.
What I did
I initially bought this phone with defaul OS 4.0.1 in Pakistan.
I then installed a Verizon system update of 250 MB that got my phone stuck on a boot loop (and made me cry almost)
I restored my phone to the settings it came in using this procedure
http://www.andromods.com/tips-trick/how-to-restore-unroot-droid-razr-m-xt907-stock-original-firmware.html
The phone worked fine for 2 days but then I got that update prompt again and it got annoying so I though maybe If i upgrade it to JB using the same RSD Lite method but a different ROM that may solve it.
So I applied the above Procedure using this ROM
http://forum.xda-developers.com/showthread.php?t=2250155
The method showed as Passed on RSD Lite but the phone got stuck on bootloop again so I paniced and tried restoring my phone abck to ICS using the method mention in the first link provided.
Then the phone got stuck on AP Boot Menu
Then I used DROID_RAZR_M_Utility_1.20 and used both methods 1 and two but it didnt work
Then out of the blue I went to the boot menu and I saw an option Switch Console (Null:null) I pressed up key on and null null changed to default:tty something it and the phone booted up just fine back to ICS
Now everytime I power off the phone it goes to AP Boot menu showing FASTBOOT REASON: Sticky bit factory_fastboot and I have to do the above to restart the phone.
What I need
Please help me restore my phone I dont want to brick it, I am a simple user I will need step by step guide
Anyone ?
Click to expand...
Click to collapse
I have solution but the android you will flash is android kitkat i don know if do u want reply me if u want to unbrick note: kitkat not supported root

lulz
Adriantech said:
I have solution but the android you will flash is android kitkat i don know if do u want reply me if u want to unbrick note: kitkat not supported root
Click to expand...
Click to collapse
Dude.. you know that you're responding to a thread that is literally a year old right?

cliMAKtic said:
Dude.. you know that you're responding to a thread that is literally a year old right?
Click to expand...
Click to collapse
And wath is the problem i cant help?

Adriantech said:
I have solution but the android you will flash is android kitkat i don know if do u want reply me if u want to unbrick note: kitkat not supported root
Click to expand...
Click to collapse
I also have a solution, but you would need another phone...
But as cliMAKtic said, it's most likely way too late now. Same goes for your replies in other threads.
Adriantech said:
And wath is the problem i cant help?
Click to expand...
Click to collapse
You can, but I'm afraid you won't. You'll rather achieve the opposite by bringing obsoleted threads back to the top.

lem22 said:
I also have a solution, but you would need another phone...
But as cliMAKtic said, it's most likely way too late now. Same goes for your replies in other threads.
You can, but I'm afraid you won't. You'll rather achieve the opposite by bringing obsoleted threads back to the top.
Click to expand...
Click to collapse
ok